[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091130102104.GA13288@sig21.net>
Date: Mon, 30 Nov 2009 11:21:04 +0100
From: Johannes Stezenbach <js@...21.net>
To: Tejun Heo <tj@...nel.org>
Cc: Greg KH <greg@...ah.com>, Robert Hancock <hancockrwd@...il.com>,
Mikhail Malygin <mmalygin@....de>,
Hans Werner <hwerner4@....de>,
Thomas Renninger <trenn@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: Samsung N130 ATA exception after 5min uptime -- Phoenix
FailSafe issue?
On Mon, Nov 30, 2009 at 05:52:59PM +0900, Tejun Heo wrote:
> On 11/29/2009 09:51 AM, Johannes Stezenbach wrote:
> > On Sat, Nov 28, 2009 at 04:17:45PM -0800, Greg KH wrote:
> >> On Sat, Nov 28, 2009 at 11:22:03PM +0100, Johannes Stezenbach wrote:
> >>>
> >>> BTW, at 5min after boot it is 99% guaranteed that this ATA
> >>> exception will happen during the occasional fsck. That
> >>> doesn't feel right.
> >>
> >> Well, I've never been doing a fsck at 5 minutes into boot, and neither do
> >> most Windows users :)
> >
> > I've been through a lot of reboots with all the testing, and
> > the fsck took longer than 5min, and the ATA exception struck.
> > fsck continued after the 30 second stall and succeeded.
>
> The timeout will happen if the C state switching happens while ATA
> command is in flight so unless there's heavy IO load, it's not very
> likely to hit.
I've booted with rdinit=/bin/sh (busybox sh in initramfs), so
nothing accesses the disk. After 5min the C state switch
happens, but no ATA exception. I waited a few more miniutes
and then used dd if=/dev/sda of=/dev/null -> ATA exception.
There is no way to escape it.
Johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists