From: Stefan Priebe - FH <studium@profihost.com>
To: David Chinner <dgc@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: XFS or Kernel Problem / Bug
Date: Mon, 22 Jan 2007 09:07:23 +0100 [thread overview]
Message-ID: <45B470BB.8000208@profihost.com> (raw)
In-Reply-To: <20070122080306.GW33919298@melbourne.sgi.com>
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?
Stefan
David Chinner schrieb:
> On Mon, Jan 22, 2007 at 08:51:10AM +0100, Stefan Priebe - FH wrote:
>> Hi!
>>
>> I'm not shure but perhaps it isn't an XFS Bug.
>>
>> Here is what i find out:
>>
>> We've about 300 servers at the momentan and 5 of them are "old" Intel
>> Pentium 4 Machines with a DFI PM-12 Mainboard with VIA chipset. It only
>> happens on THESE Machines.
>
> Hmmm - that points more to a hardware problem than a software problem;
> crashes in generic_file_buffered_write() are relatively uncommon, and
> to have them all isolated to a specific type of hardware is suspicious....
>
> Wasn't there a major update of the IDE layer in 2.6.18? or was that
> 2.6.19 that I'm thinking of? BTW, have you run memtest86 on these
> boxes to rule out dodgy memory?
>
> Cheers,
>
> Dave.
next prev parent reply other threads:[~2007-01-22 8:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060801141545.B2326184@wobbly.melbourne.sgi.com>
[not found] ` <44CED76B.20507@profihost.com>
[not found] ` <20060801142755.C2326184@wobbly.melbourne.sgi.com>
[not found] ` <44CED8F4.9080208@profihost.com>
[not found] ` <20060801143212.D2326184@wobbly.melbourne.sgi.com>
[not found] ` <44CEDA1D.5060607@profihost.com>
[not found] ` <20060801143803.E2326184@wobbly.melbourne.sgi.com>
[not found] ` <44CF36FB.6070606@profihost.com>
[not found] ` <20060802090915.C2344877@wobbly.melbourne.sgi.com>
[not found] ` <44D07AB7.3020409@profihost.com>
[not found] ` <20060802201805.A2360409@wobbly.melbourne.sgi.com>
2007-01-21 12:30 ` XFS or Kernel Problem / Bug Stefan Priebe - FH
2007-01-22 6:18 ` David Chinner
2007-01-22 7:51 ` Stefan Priebe - FH
2007-01-22 8:03 ` David Chinner
2007-01-22 8:07 ` Stefan Priebe - FH [this message]
2007-01-23 1:10 ` David Chinner
2007-01-23 8:31 ` Stefan Priebe - FH
2007-01-22 9:42 ` Stefan Priebe - FH
2007-01-23 19:49 ` Chuck Ebbert
2007-01-24 7:40 ` Stefan Priebe - FH
2007-01-24 14:57 ` Chuck Ebbert
2007-01-24 15:03 ` Stefan Priebe - FH
2007-01-24 15:13 ` Chuck Ebbert
2007-01-24 15:34 ` Stefan Priebe - FH
2007-01-24 16:51 ` Chuck Ebbert
2007-01-24 17:16 ` Stefan Priebe - FH
2007-01-24 17:56 ` Chuck Ebbert
2007-01-24 19:27 ` Stefan Priebe - FH
2007-01-25 20:52 ` Chuck Ebbert
2007-01-25 21:29 ` Stefan Priebe - FH
2007-01-30 10:44 ` Stefan Priebe - FH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45B470BB.8000208@profihost.com \
--to=studium@profihost.com \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox