Bug#571980: /boot/vmlinuz-2.6.33-2-amd64: impi oops on intel motherboard

[Jonathan Nieder <jrnieder@gmail.com>]

fixed 571980 linux/3.2.21-3
quit

Ian Crowther wrote:
> On 10/07/12 10:30, Xavier Bestel wrote:

>> Yes, it runs 3.2.0-2-amd64, it seems to behave like a champ. At least I
>> didn't spot an IPMI-related Oops recently (but I don't reboot it that
>> often).
>
> Ours are sitting on a shelf, powered off. I can use one to test a
> specific kernel if wanted.

Thanks, both.

If either of you gets a chance to try the latest 2.6.32.y kernel from
squeeze (it should work fine on a squeeze or wheezy/sid system), then
that would be interesting.

Hope that helps,
Jonathan

(A few upstream commits between 2.6.32.y and 3.0.y for reference:

  9e368fa011d4 ipmi: add PNP discovery (ACPI namespace via PNPACPI)
  c7df670bf702 sysfs: fix sysfs lockdep warning in ipmi code
  56480287f977 ipmi: make sure drivers were registered before
               unregistering them
  561f8182dbf2 ipmi: fix hardcoded ipmi device exit path warning
  de5e2ddf9bb3 ipmi: proper spinlock initialization
  d2478521afc2 char/ipmi: fix OOPS caused by pnp_unregister_driver on
               unregistered driver (as corrected by 0dcf334c44d9)
)