Ok. I have tested this, and I know others are using this, so it may be some type of hardware-specific interaction the driver is not doing correctly.
Replying so eveyone can see this, I seem to have chosen the wrong mailing list option with your address and it got discarded there. Martin Hicks wrote: > On Thu, Aug 13, 2009 at 09:24:06PM -0500, Corey Minyard wrote: > >> I haven't seen this, but I don't use KDB. >> >> If you remove KDB, does the problem go away? >> > > No difference. I think it's totally unrelated. Without KDB the kernel > still halts inside send_panic_events function() > > >> I assume you can turn off CONFIG_IPMI_PANIC_EVENT in the kernel config and >> you can work properly. There's not actually a lot of value in having IPMI >> panic events and KDB enabled at the same time. >> > > Yes, but I felt it was worth reporting this bug. > > The IPMI notifier is the first to run and prevents all other notifiers > from running... > > I thought it might be due to a full SEL, but clearing the SEL had no > effect. I see the message that this driver is presumably writing to the > SEL: > > 400 | 08/07/2009 | 20:42:01 | OS Stop/Shutdown #0x70 | Run-time critical > stop | Asserted > That actually means that the first message went out and it's stuck in a later message. -corey > > mh > > >> -corey >> >> >> Martin Hicks wrote: >> >>> Hi, >>> >>> I've been playing with the KDB kernel debugger, and trying to figure out >>> why it doesn't enter into the debugger during a kernel panic. I tracked >>> the problem to the IPMI panic handler. >>> >>> When I have the Sytem Interface option enabled in the kernel (or the >>> ipmi_si module loaded), I don't get to KDB and the system just hangs in >>> the first i_ipmi_request() in the send_panic_events() function. >>> >>> Without the SI loaded, the rest of the panic handlers run and eventually >>> the KDB panic handler is invoked. >>> >>> I'm not sure if this is device-specific, but here are the ipmi-related >>> dmesg: >>> >>> [ 5.356557] ipmi message handler version 39.2 >>> [ 5.369593] ipmi device interface >>> [ 5.379627] IPMI System Interface driver. >>> [ 5.391644] ipmi_si: Trying SMBIOS-specified kcs state machine at i/o >>> address 0xca2, slave address 0x20, irq 0 >>> [ 5.503192] ipmi: Found new BMC (man_id: 0x000157, prod_id: 0x0028, >>> dev_id: 0x20) >>> [ 5.525939] IPMI kcs interface initialized >>> >>> >>> I've reproduced this on the SuSE sles11 kernel as well as upstream >>> kernels (2.6.28 and up to 2.6.31-rc2). >>> >>> Any ideas? >>> mh >>> >>> >>> > > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Openipmi-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openipmi-developer
