BUG/ spinlock lockup, 2.6.24

2008-02-15 Thread Denys Fedoryshchenko
Server crashed(not responding over network), last line over netconsole was Feb 15 15:50:17 217.151.X.X [1521315.068984] BUG: spinlock lockup on CPU#1, ksoftirqd/1/7, f0551180 I have random crashes, at least once per week. It is very difficult to catch error message, and only recently i setup

Re: BUG/ spinlock lockup, 2.6.24

2008-02-15 Thread Bart Van Assche
2008/2/15 Denys Fedoryshchenko [EMAIL PROTECTED]: I have random crashes, at least once per week. It is very difficult to catch error message, and only recently i setup netconsole. Now i got crash, but there is no traceback and only single line came over netconsole, mentioned before. Did

Re: BUG/ spinlock lockup, 2.6.24

2008-02-15 Thread Denys Fedoryshchenko
This server was working fine under load under FreeBSD, and worked fine before with other tasks under Linux. I dont think it is RAM. Additionally it is server hardware (Dell PowerEdge) with ECC, MCE and other layers, who will report about any hardware issue most probably, and i think even better

Re: BUG/ spinlock lockup, 2.6.24

2008-02-15 Thread Jarek Poplawski
Jarek Poplawski wrote, On 02/15/2008 09:21 PM: Denys Fedoryshchenko wrote, On 02/15/2008 08:42 PM: ... I have similar crashes on completely different hardware with same job (QOS), so i think it is actually some nasty bug in networking. Maybe you could try with some other debugging

Re: BUG/ spinlock lockup, 2.6.24

2008-02-15 Thread Jarek Poplawski
Jarek Poplawski wrote, On 02/15/2008 10:03 PM: ... ...On the other hand this: Feb 15 15:50:17 217.151.X.X [1521315.068984] BUG: spinlock lockup on CPU#1, ksoftirqd/1/7, f0551180 seems to point just at spinlock lockup, so it's more about the full report. I wonder if this patch to prink

Re: BUG/ spinlock lockup, 2.6.24

2008-02-15 Thread Jarek Poplawski
Denys Fedoryshchenko wrote, On 02/15/2008 08:42 PM: ... I have similar crashes on completely different hardware with same job (QOS), so i think it is actually some nasty bug in networking. Maybe you could try with some other debugging options? E.g. since lockdep doesn't help - turn this off.