|To:||Mikael Wahlberg <mikael.wahlberg@xxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>|
|Subject:||Re: Filesystem kernel hangup, 2.6.3 (bad: scheduling while atomic!)|
|From:||Seth Mos <knuffie@xxxxxxxxx>|
|Date:||Mon, 23 Feb 2004 14:46:34 +0100|
|Cc:||linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx, Per Lejontand <pele@xxxxxxxxxx>, Jonas Engström <jonas@xxxxxxxxxx>|
|References:||<20040223121959.A8354@xxxxxxxxxxxxx> <20040222164941.D6046@xxxxxxxxxxxxxx> <20040223121959.A8354@xxxxxxxxxxxxx>|
At 14:08 23-2-2004 +0100, Mikael Wahlberg wrote:
On Mon, 2004-02-23 at 13:19, Christoph Hellwig wrote: > On Sun, Feb 22, 2004 at 04:49:41PM +0100, Mikael Wahlberg wrote: > did you run memtest86 on the box? do you some strange patches applied or > external modules loaded? What's your .config? No strange patches. Pure 2.6.3 dist kernel. We haven't run memtest86, but as I mentioned above, we have 4 equal machines with error correcting memory, so I find it unlikely to be a memory problem.
The memory might be fine, but the mainboard might still be borked. I have seen this once with Dell kit. Asuming can be dangerous. If you can spare the down time it is always a good idea to make sure.
In my experience XFS shows faulty memory quite fast. That's from personal experience.
Cheers -- Seth I don't make sense, I don't pretend to either. Questions?
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: Filesystem kernel hangup, 2.6.3 (bad: scheduling while atomic!), Mikael Wahlberg|
|Next by Date:||large allocation groups fix, Alexander Fisher|
|Previous by Thread:||Re: Filesystem kernel hangup, 2.6.3 (bad: scheduling while atomic!), Christoph Hellwig|
|Next by Thread:||Re: Filesystem kernel hangup, 2.6.3 (bad: scheduling while atomic!), Mikael Wahlberg|
|Indexes:||[Date] [Thread] [Top] [All Lists]|