Al Chu <ch...@llnl.gov> writes: > Hi Dave, > > Huh ... I'm sorta at a loss. The state_data->prog_data data structure > is pretty core. It's set once near the beginning in main and never > written to again once the main code is executed,
The stack trace did suggest something had stomped on it. I'll try to find time to have a proper look at it sometime. > which may include > threads if you're doing hostranges. Dunno if the threading could be > part of the problem for your unique system. This was just the one host, and gdb only showed one thread. > For kicks, another fellow on the mailing recently had a segv problem and > it appeared it was related to this. Possible for you too? > > http://www.gnu.org/software/freeipmi/freeipmi-faq.html#Why-am-I-seeing-so-many-_0027internal-IPMI-error_0027-or-_0027driver-busy_0027-messages_003f I got the same thing out-of-band, which I assume would be independent of the kernel. That's useful information, though, as I tend to turn off the ipmi service. _______________________________________________ Freeipmi-devel mailing list Freeipmi-devel@gnu.org https://lists.gnu.org/mailman/listinfo/freeipmi-devel
