linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Georgi Chulkov <g.chulkov@jacobs-university.de>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: ATA device reset, shoud I be concerned?
Date: Tue, 15 Jan 2008 02:54:35 -0800	[thread overview]
Message-ID: <20080115025435.1e21b703.akpm@linux-foundation.org> (raw)
In-Reply-To: <200801140019.20668.g.chulkov@jacobs-university.de>

On Mon, 14 Jan 2008 00:19:20 +0200 Georgi Chulkov <g.chulkov@jacobs-university.de> wrote:

> Hello,
> 
> During heavy disk load on my laptop, sometimes the IDE disk will pause for a 
> second and then continue. I get this in my kernel log:
> 
> [ 9031.028000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 
> frozen
> [ 9031.028000] ata1.00: cmd c8/00:08:90:ca:ce/00:00:00:00:00/e0 tag 0 cdb 0x0 
> data 4096 in
> [ 9031.028000]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
> (timeout)
> [ 9036.068000] ata1: port is slow to respond, please be patient (Status 0xd0)
> [ 9041.052000] ata1: device not ready (errno=-16), forcing hardreset
> [ 9041.052000] ata1: soft resetting port
> [ 9041.232000] ata1.00: configured for UDMA/100
> [ 9041.232000] ata1: EH complete
> [ 9041.248000] sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)
> [ 9041.248000] sd 0:0:0:0: [sda] Write Protect is off
> [ 9041.248000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [ 9041.248000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
> doesn't support DPO or FUA
> 
> My question: What is this telling me, and do I need to be concerned? 
> Everything continues to work normally after the message: no I/O errors, no 
> fsck errors, etc.
> 
> I've seen some similar reports on the mailing list, but they include slightly 
> different messages. I would appreciate any information!
> 
> uname -a (on Kubuntu Gutsy, CPU is a single-core 32-bit Pentium M):
> 
> Linux superfly 2.6.22-14-386 #1 Tue Dec 18 07:34:24 UTC 2007 i686 GNU/Linux
> 

Has it done this in all kernel versions or did some earler version work OK?

  reply	other threads:[~2008-01-15 10:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13 22:19 ATA device reset, shoud I be concerned? Georgi Chulkov
2008-01-15 10:54 ` Andrew Morton [this message]
2008-01-15 11:35   ` Alan Cox
2008-01-21  7:56     ` Tejun Heo
2008-01-21 13:02       ` Alan Cox
2008-01-21 13:14         ` Tejun Heo
2008-01-21 14:14           ` Alan Cox
2008-01-21 14:31             ` Tejun Heo
2008-01-21 14:33               ` Tejun Heo
2008-01-21 16:44                 ` Alan Cox
2009-08-27  2:40                 ` Robert Hancock
2009-08-27  3:07                   ` Jeff Garzik
2009-08-27  8:37                   ` Alan Cox
2008-01-21 16:47               ` Alan Cox
2008-01-21 17:02                 ` Tejun Heo
2008-01-21 17:27                   ` Alan Cox
2008-01-22  0:31                     ` Tejun Heo
2008-01-22  1:31                   ` Bartlomiej Zolnierkiewicz
2008-01-22  1:36                     ` Tejun Heo
2008-01-22  2:08                       ` Tejun Heo
2008-01-22  1:39                     ` Alan Cox
2008-01-22 20:29   ` Georgi Chulkov

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=20080115025435.1e21b703.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=g.chulkov@jacobs-university.de \
    --cc=linux-ide@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).