From: Nathan Scott <nathans@sgi.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Huge problem with XFS/iCH7R
Date: Tue, 4 Jul 2006 08:47:40 +1000 [thread overview]
Message-ID: <20060704084740.A1462688@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <44A98A0B.8080203@tmr.com>; from davidsen@tmr.com on Mon, Jul 03, 2006 at 05:20:11PM -0400
On Mon, Jul 03, 2006 at 05:20:11PM -0400, Bill Davidsen wrote:
> >> My system crashes every few days, at the moment daily. The message shown
> >> is (the drive changes about every time, I do not see a pattern here):
> >> ---
> >> ata4: handling error/timeout
> >> ata4: port reset, p_is 0 is 0 pis 0 cmd c017 tf 7f ss 0 se 0
> >> ata4: status=0x50 { DriveReady SeekComplete }
> >> sdd: Current: sense key=0x0
> >> ASC=0x0 ASCQ=0x0
> >> Info fid=0x0
> >
> > FWIW, the above look like hardware/driver problems.
>
> If the problem doesn't occur before 2.6.16, that makes a hardware
> problem less likely. It's not impossible that some buggy feature is now
> used, but lower probability than the kernel change being the culprit.
*nod*.
> The bug fix you mention may solve the whole thing, or make it easier to
I'm certain it wont; that was an XFS problem, and I can see no way it
could cause device/driver issues also.
> General comment: if a kernel version made my system crash once a day I
> sure wouldn't be using it.
Heh, yes - by definition.
> New features are neat, but I wouldn't put up
> with that if it made my cat pee holy water.
Not sure what new features you're talking about here? Nor how your
cat fits into all this.. ;)
cheers.
--
Nathan
next prev parent reply other threads:[~2006-07-03 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 19:51 Carsten Otto
2006-07-02 19:56 ` Carsten Otto
2006-07-02 21:22 ` Jan Engelhardt
2006-07-03 6:32 ` Nathan Scott
2006-07-03 21:20 ` Bill Davidsen
2006-07-03 22:47 ` Nathan Scott [this message]
2006-07-05 12:29 ` Bill Davidsen
2006-07-16 8:45 ` Carsten Otto
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=20060704084740.A1462688@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=davidsen@tmr.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
all inboxes | Powered by JetHome®