Mathieu Alorent wrote: > Le mercredi 11 mars 2009 à 08:50 -0500, Corey Minyard a écrit : > >> Mathieu ALORENT wrote: >> >>> Hi, >>> >>> we've got this error on all our SUN V40Z systems. I don't know what does >>> it mean.. >>> >>> [kern.warning] kernel IPMI message handler: BMC returned incorrect >>> response, expected netfn 3b cmd 3c, got netfn 3a cmd 3c >>> >>> Can someone give me an explanation ? >>> >>> >> It appears to be a bug in the BMC. On responses, the netfn is supposed >> to have the 1 set in the lowest bit. So if it sends netfn 0x2c, it >> should get back netfn 0x2d. >> >> These appear to be for error responses, for instance the 2C/2D one is an >> ATCA probe (which your box won't support, since I don't think it's >> ATCA). So it appears to be returning incorrect responses for errors. >> You should report this to Sun, though if everything else is working >> correctly and it's not spewing out these errors it shouldn't affect >> normal operations very much. >> >> The last one is a little strange, it's doing a "Get SDR" request and >> that shouldn't fail. >> >> -corey >> >> >>> Regards >>> Mât >>> >>> --------------------------------------- >>> >>> # uname -a >>> Linux xxxxxxxxxxxxxx 2.6.24-standard #2 SMP Fri Jul 11 15:04:57 UTC 2008 >>> x86_64 GNU/Linux >>> >>> >>> # dmesg |grep -i IPMI >>> ipmi message handler version 39.1 >>> ipmi device interface >>> IPMI System Interface driver. >>> ipmi_si: Trying SMBIOS-specified kcs state machine at i/o address 0xca2, >>> slave address 0x20, irq 0 >>> ipmi: Found new BMC (man_id: 0x00002a, prod_id: 0x09ef, dev_id: 0x20) >>> IPMI kcs interface initialized >>> Copyright (C) 2004 MontaVista Software - IPMI Powerdown via sys_reboot. >>> IPMI message handler: BMC returned incorrect response, expected netfn 2d >>> cmd 1, got netfn 2c cmd 1 >>> IPMI poweroff: ATCA Detect mfg 0x2A prod 0x9EF >>> IPMI poweroff: Found a chassis style poweroff function >>> IPMI message handler: BMC returned incorrect response, expected netfn 3b >>> cmd 3c, got netfn 3a cmd 3c >>> IPMI message handler: BMC returned incorrect response, expected netfn b >>> cmd 23, got netfn 5 cmd 2d >>> >>> > > I've contacted SUN about this, a ticket is open... > > Today, I've found similar logs on another system "HP DL360 G6"... > here are the logs... > > IPMI message handler: BMC returned incorrect response, expected netfn 5 > cmd 27, got netfn 5 cmd 35 > IPMI message handler: BMC returned incorrect response, expected netfn 5 > cmd 27, got netfn 5 cmd 35 > IPMI message handler: BMC returned incorrect response, expected netfn 5 > cmd 27, got netfn 5 cmd 35 > > > what I've done is : > > $ watch -n1 "ipmitool sensor" > > > So this let me think that it's maybe not a bug in BMC... > > What is your opinion? > > I've let this run for a while on one of my systems and haven't seen the problem. Does this happen constantly, or is this a rare occurrence?
If the driver is getting confused, it's possible this is due to a conflict with a read event buffer, but that would not happen very often. If it's happening all the time, then it's probably a bug in the BMC. Also, if it's the same netfn and command getting messed up every time, then it's not likely to be the driver, as it doesn't care about those values beyond just verifying that the send and receive match. That would point to a problem in the BMC. If the it's different netfn/commands, then that might be the driver. -corey ------------------------------------------------------------------------------ _______________________________________________ Openipmi-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openipmi-developer
