Bug#770472: Acknowledgement (libfreeipmi12: programs using libfreeipmi2 crash the first time after a system boot)

Ok, it's not exactly how I described it, bmc-config (and some other commands) will crash *until* ipmi-sensors is run, at which point it will start working. Until the next reboot. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble?

Bug#770472: Info received (Bug#770472: Acknowledgement (libfreeipmi12: programs using libfreeipmi2 crash the first time after a system boot))

The bug only happens when running under xen, not on the bare metal. So I guess it's a xen bug really. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#770472: Info received (Bug#770472: Acknowledgement (libfreeipmi12: programs using libfreeipmi2 crash the first time after a system boot))

thanks for digging into it... not sure if I should do anything about it, but let's at least ask upstream Dear Albert, User reported some kernel trap hit upon initial boot in Xen instances, see more detail : Package: libfreeipmi12 Version: 1.1.5-3 http://bugs.debian.org/770472 Is that something

Bug#770472: Info received (Bug#770472: Acknowledgement (libfreeipmi12: programs using libfreeipmi2 crash the first time after a system boot))

I imagine the bug is somewhere in xen's memory mapped I/O area if it's happening the first time after boot. Since I'm just using the normal in() and out() calls, not sure there's much I can do. If there is a way to massage freeipmi to not trigger the bug we could work around it, but I have no