Messages in this thread | | | Date | Tue, 23 Jan 2007 09:31:54 +0100 | From | Stefan Priebe - FH <> | Subject | Re: XFS or Kernel Problem / Bug |
| |
Hi!
I can give you an idea of the workload :-) I have the same problem on an nearly idle Server. There runs only a few cronjobs (normal Debian System crons).
The load was not higher than 0.01 on this system the last 3 days and this morning it crashes with the same error.
I've not tested 2.6.19.x cause this one has some problems with SATA AHCI driver which we need. But i can manuelly update only this system with 2.6.19.x and wait some days.
There were no other messages in the log.
Cheers, Stefan
David Chinner schrieb: > On Mon, Jan 22, 2007 at 09:07:23AM +0100, Stefan Priebe - FH wrote: >> Hi! >> >> The update of the IDE layer was in 2.6.19. I don't think it is a >> hardware bug cause all these 5 machines runs fine since a few years with >> 2.6.16.X and before. We switch to 2.6.18.6 on monday last week and all >> machines began to crash periodically. On friday last week we downgraded >> them all to 2.6.16.37 and all 5 machines runs fine again. So i don't >> believe it is a hardware problem. Do you really think that could be? > > I was thinking more of a driver change that is being triggered on > that particular hardware. FWIW, did you test 2.6.19? > > I really need a better idea of the workload these servers are running > and, ideally, a reproducable test case to track something like > this down. At the moment I have no idea what is going on and no > real information on which to even base a guess. > > Were there any other messages in the log? > > On Mon, Jan 22, 2007 at 10:42:36AM +0100, Stefan Priebe - FH wrote: >> Hi! >> >> I've another idea... could it be, that it is a barrier problem? Since >> barriers are enabled by default from 2.6.17 on ... > > You could try turning it off. If it does fix the problem, then I'd be > pointing once again at hardware ;) > > Cheers, > > Dave.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |