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 idea how one might massage it. On Fri, 2014-11-21 at 15:01 -0500, Yaroslav Halchenko wrote: > 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 familiar/resolvable at freeipmi level? > > Cheers! > > On Fri, 21 Nov 2014, John Hughes wrote: > > > The bug only happens when running under xen, not on the bare metal. > > > So I guess it's a xen bug really. > > -- Albert Chu ch...@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
