Comment 9 for bug 1875771
Revision history for this message
| Bryce Harrington (bryce) wrote Re: ipmi_locate segfault on Focal | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
I confirmed Paride's finding that it neither reproduces on my own hardware nor are forum/blog/google searches turn up anything useful. Bug #1893136 does indeed appear to be a dupe to this bug (once confirmed by the reporter it can be set as a dupe of this).
Given that the affected systems appear to all be Dell PowerEdge servers, and only Dell, if someone has a support contract with Dell it would be good to get them involved. Forwarding upstream also makes sense however they likely will not have the HW in question so will want additional detail.
A full stack trace is probably the most important first step, as that will reveal what is going on. Having stack traces for both iDRAC9 and iDRAC9 systems would allow confirming that it is indeed the same bug.
I would try installing debug packages for freeipmi, and then running the command while logged into the physical system, via `gdb ipmi-locate`, then:
(gdb) set logging file gdb-freeipmi.txt
(gdb) set logging on
(gdb) backtrace full
Then attach gdb-freeipmi.txt here.
I don't know for certain if the debug packages need to be installed in order to get symbols shown, but if so directions for installing them can be found online (e.g. at https:/