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

2012-07-13 Thread Ian Crowther
On 12/07/12 21:21, Jonathan Nieder wrote: Ian Crowther wrote: I'm not sure what 2.6.32.y means. I've installed 2.6.32-5-686, which seems to be recent. Am I correct in assuming you mean version 2.6.32-45? You can check with dpkg-query -W linux-image-$(uname -r) to see the v

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

2012-07-12 Thread Jonathan Nieder
Ian Crowther wrote: > I'm not sure what 2.6.32.y means. I've installed 2.6.32-5-686, which > seems to be recent. Am I correct in assuming you mean version 2.6.32-45? You can check with dpkg-query -W linux-image-$(uname -r) to see the version number of the installed kernel, or

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

2012-07-12 Thread Ian Crowther
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. I'm not sure what 2.6.32.y means. I've installed 2.6.32-5-686, which seems to be recent. That has the same

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

2012-07-10 Thread Jonathan Nieder
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 of

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

2012-07-10 Thread Xavier Bestel
Le lundi 09 juillet 2012 à 16:12 -0500, Jonathan Nieder a écrit : > Thanks to both of you. Do you still have access to this hardware? If so, > what kernel do you use, and how does it behave? 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

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

2012-07-09 Thread Jonathan Nieder
Hi, In 2010, i...@comtek.co.uk wrote: > Any use of ipmi on a stock IBM 326m results, after a period of maybe a > few minutes, in a kernel oops, after which I'm unable to run any > programs or use anything really and the only option remaining is to restart. > > If I type: >modprobe ipmi_devi

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

2010-03-27 Thread Xavier Bestel
Le jeudi 25 mars 2010 à 22:59 +0100, maximilian attems a écrit : > please report upstream on bugzilla.kernel.org with oops dmesg there > and let us know bug nr so that it can be tracked. https://bugzilla.kernel.org/show_bug.cgi?id=15638 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lis

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

2010-03-25 Thread maximilian attems
On Thu, Mar 25, 2010 at 10:08:19AM +0100, Xavier Bestel wrote: > Package: linux-2.6 > Version: 2.6.33-1~experimental.4 > Followup-For: Bug #571980 please report upstream on bugzilla.kernel.org with oops dmesg there and let us know bug nr so that it can be tracked. thanks. -- To UNSUBSCRIBE, e

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

2010-03-25 Thread Xavier Bestel
Package: linux-2.6 Version: 2.6.33-1~experimental.4 Followup-For: Bug #571980 Here's the oops: [ 16.507977] IPMI System Interface driver. [ 16.508187] general protection fault: [#1] SMP [ 16.508189] last sysfs file: /sys/module/ipmi_msghandler/initstate [ 16.508191] CPU 0 [ 16.50