That function then in libfreeipmi/locate/ipmi-locate-acpi-spmi.c is the same (due to patches on top of Bionic that were later part of upstream).
For better debug actually a debug build and then a core dump of it would be awesome (more knowledge, less guessing).
Please:
- use the package from this PPA [1] for further tests
- also install debug symbols from the PPA [2]
The interesting bits seem to happen in /lib/libfreeipmi.so.17 according to your dump.
To ensure we get a core dump this might be helpful:
$ apt install apport whoopsie
With the above in place trigger the crash:
- once as bryce showed with gdb and report the output file (hopefully with better info now)
- once without gdb which should create a /var/crash/ file
- use apport-retrace and report the output here
$ apport-retrace /var/crash/<yourfile>.crash --stdout
- attach the .crash file to this bug
P.S. @Jeff/Michael is there any chance we could get a login to such a system for an hour to do some debugging in place?
The log has no line numbers in most places.
So I guess we need debug packages.
I've looked at the bit we see, the call from ipmi-locate.c:283 is the same in Bionic and Focal.
275 static void locate_ acpi_spmi_ get_device_ info (ctx,
276 acpi_probe_display (ipmi_locate_ctx_t ctx)
277 {
278 struct ipmi_locate_info info;
279
280 assert (ctx);
281
282 printf ("Probing KCS device using ACPI... ");
283 if (!ipmi_
284 IPMI_INTERFACE_KCS,
285 &info))
That function then in libfreeipmi/ locate/ ipmi-locate- acpi-spmi. c is the same (due to patches on top of Bionic that were later part of upstream).
For better debug actually a debug build and then a core dump of it would be awesome (more knowledge, less guessing).
Please:
- use the package from this PPA [1] for further tests
- also install debug symbols from the PPA [2]
The interesting bits seem to happen in /lib/libfreeipm i.so.17 according to your dump.
Please install these: dbgsym freeipmi- tools-dbgsym
$ apt install libfreeipmi17-
To ensure we get a core dump this might be helpful:
$ apt install apport whoopsie
With the above in place trigger the crash: <yourfile> .crash --stdout
- once as bryce showed with gdb and report the output file (hopefully with better info now)
- once without gdb which should create a /var/crash/ file
- use apport-retrace and report the output here
$ apport-retrace /var/crash/
- attach the .crash file to this bug
P.S. @Jeff/Michael is there any chance we could get a login to such a system for an hour to do some debugging in place?
[1]: https:/ /launchpad. net/~ci- train-ppa- service/ +archive/ ubuntu/ 4237 /wiki.ubuntu. com/DebuggingPr ogramCrash# Installing_ dbgsym_ packages_ from_a_ PPA
[2]: https:/