public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Johannes Stezenbach <js@sig21.net>
Cc: Greg KH <greg@kroah.com>, Robert Hancock <hancockrwd@gmail.com>,
	Mikhail Malygin <mmalygin@ked.de>, Hans Werner <hwerner4@gmx.de>,
	Thomas Renninger <trenn@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Samsung N130 ATA exception after 5min uptime -- Phoenix FailSafe issue?
Date: Mon, 30 Nov 2009 17:52:59 +0900	[thread overview]
Message-ID: <4B1387EB.2090506@kernel.org> (raw)
In-Reply-To: <20091129005157.GA6487@sig21.net>

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.  Another factor is that windows uses shorter IO timeout
(I think it's 7 secs or 15, I'm not sure) so it's gonna be less
noticeable when it happens.  Hmmm.... there were talks about
shortening the timeout.  Maybe it's about time we actually do that.

Thanks.

-- 
tejun

  reply	other threads:[~2009-11-30  8:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-26 16:42 Samsung N130 ATA exception after 5min uptime -- Phoenix FailSafe issue? Johannes Stezenbach
2009-11-28 19:19 ` Greg KH
2009-11-28 20:30   ` Robert Hancock
2009-11-28 21:34     ` Greg KH
2009-11-28 22:22       ` Johannes Stezenbach
2009-11-29  0:17         ` Greg KH
2009-11-29  0:51           ` Johannes Stezenbach
2009-11-30  8:52             ` Tejun Heo [this message]
2009-11-30 10:21               ` Johannes Stezenbach
2009-11-30 11:06                 ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2009-12-30 12:04 Hans Werner
2010-01-03 22:11 ` Johannes Stezenbach
2010-01-03 22:59   ` Tejun Heo
2010-01-04  0:41     ` Johannes Stezenbach
2010-01-04  0:56       ` Tejun Heo

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=4B1387EB.2090506@kernel.org \
    --to=tj@kernel.org \
    --cc=greg@kroah.com \
    --cc=hancockrwd@gmail.com \
    --cc=hwerner4@gmx.de \
    --cc=js@sig21.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmalygin@ked.de \
    --cc=trenn@suse.de \
    /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