RE: [Openipmi-developer] oops under 2.4.26

[Courchesne, A. <And...@ca...>]

Hi,

  Looks like it is working. The new path was taken a few times during
overnight testing.

	IPMI message handler: BMC returned incorrect response, expected
netfn 7 cmd 35, got netfn 7 cmd 31

  Now I got a SIGSEGV in my code (which happened overnight) to debug :-(

  Thanks for the help.

-----Original Message-----
From: Corey Minyard [mailto:mi...@ac...]
Sent: Monday, August 09, 2004 12:53 PM
To: Courchesne, Andre
Cc: ope...@li...
Subject: Re: [Openipmi-developer] oops under 2.4.26


Courchesne, Andre wrote:

>Ok, got the exact same thing with the "si" driver:
>
>  
>
Ok.  It looks like your BMC is hosed and is returning a bad response.  
The IPMI driver does not protect itself from this.  It assumes that the 
BMC responses are always good.

The fix is fairly straightforward; I've attached a patch to try.  You 
should get errors and kernel logs instead of a panic.

-Corey