On Mon, 10 Jan 2011 19:48:33 -0800 Corey Minyard <[email protected]> wrote:
> This is almost certainly a bug in the BMC. The change in your patch > should have no effect, this is the start of a send, and the BMC > interface should be idle at that point, so doing an smi_timeout will > only result in another extraneous read from the IPMI interface (and > of course a slightly longer delay). > This is bad news, then. I already have another outstanding issue for this platform that hasn't been resolved and probably never will be, so I'm not particularly hopeful about putting in a ticket for this one. Matthew Garrett mentioned that he had a reproduction case, but it wasn't clear if he had found the same platform that I'm using or if it's reproducible on other hardware. > I would guess that adding an extra read is working around the > problem. Before polling was reduced, it read a whole lot more from > the interface and probably covered the BMC bug. You can test this by > replacing that "smi_timeout()" added in your patch with > "smi_info->io->inputb(smi_info->io, 1)", > which will do the read from the status register. > I replaced "smi_timeout()" in the previous patch with "smi_info->io.inputb(&smi_info->io, 1);" (adjusted from your version, but I assume it's what you meant), and it still breaks: Jan 11 13:45:40 stephen watchdog[4743]: starting daemon (5.6): Jan 11 13:45:40 stephen watchdog[4743]: int=30s realtime=yes sync=no soft=no mla=0 mem=0 Jan 11 13:45:40 stephen watchdog[4743]: ping: no machine to check Jan 11 13:45:40 stephen watchdog[4743]: file: no file to check Jan 11 13:45:40 stephen watchdog[4743]: pidfile: no server process to check Jan 11 13:45:40 stephen watchdog[4743]: interface: no interface to check Jan 11 13:45:40 stephen watchdog[4743]: test=none(0) repair=none alive=/dev/watchdog heartbeat=none temp=none to=root no_act=no Jan 11 13:45:40 stephen kernel: IPMI message handler: BMC returned incorrect response, expected netfn 7 cmd 35, got netfn 7 cmd 24 Jan 11 13:45:40 stephen kernel: IPMI message handler: BMC returned incorrect response, expected netfn 7 cmd 22, got netfn 7 cmd 35 Jan 11 13:45:40 stephen kernel: IPMI Watchdog: response: Error ff on cmd 22 Jan 11 13:45:40 stephen watchdog[4743]: write watchdog device gave error 22 = 'Invalid argument'! This also caused ipmievd to start breaking too though: Jan 11 13:45:34 stephen ipmievd: Reading sensors... Jan 11 13:45:35 stephen kernel: IPMI message handler: BMC returned incorrect response, expected netfn b cmd 20, got netfn 7 cmd 1 Jan 11 13:45:35 stephen ipmievd: Error obtaining SDR info: Unspecified error Jan 11 13:45:35 stephen ipmievd: Unable to open SDR for reading Jan 11 13:45:35 stephen kernel: IPMI message handler: BMC returned incorrect response, expected netfn 7 cmd 2f, got netfn b cmd 20 Jan 11 13:45:35 stephen ipmievd: Get BMC Global Enables command failed: Unspecified error Jan 11 13:45:35 stephen ipmievd: Could not enable event message buffer Jan 11 13:45:35 stephen ipmievd: Error setting up Event Interface open ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Openipmi-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openipmi-developer
