public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Parag Warudkar <kernel-stuff@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc2 ATA Errors
Date: Sun, 16 Jul 2006 13:55:46 -0400	[thread overview]
Message-ID: <200607161355.46517.kernel-stuff@comcast.net> (raw)
In-Reply-To: <200607161346.00352.kernel-stuff@comcast.net>

Before that error, there are a bunch of abnormal status messages - 

[44088.228000] ATA: abnormal status 0x58 on port 0x177
[44088.228000] ATA: abnormal status 0x58 on port 0x177
[44088.228000] ATA: abnormal status 0x58 on port 0x177
[44088.228000] ATA: abnormal status 0x58 on port 0x177

On Sunday 16 July 2006 13:46, Parag Warudkar wrote:
> Just saw the below error in dmesg - (ATA2 is my CD burner and I wasn't
> doing anything with it as far as I remember) . Drive seems to work fine
> after the error. What does it mean?
>
> $ dmesg |grep ata2
> [    1.496000] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xBFA8 irq
> 15 [    1.836000] ata2.00: ATAPI, max UDMA/33
> [    2.016000] ata2.00: configured for UDMA/33
> [44087.904000] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
> frozen
> [44087.904000] ata2.00: tag 0 cmd 0xa0 Emask 0x2 stat 0x50 err 0x0 (HSM
> violation)
> [44087.904000] ata2: soft resetting port
> [44088.340000] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x1)
> [44088.340000] ata2.00: revalidation failed (errno=-5)
> [44088.340000] ata2: failed to recover some devices, retrying in 5 secs
> [44093.344000] ata2: soft resetting port
> [44093.876000] ata2.00: configured for UDMA/33
> [44093.876000] ata2: EH complete

      reply	other threads:[~2006-07-16 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-16 17:46 2.6.18-rc2 ATA Errors Parag Warudkar
2006-07-16 17:55 ` Parag Warudkar [this message]

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=200607161355.46517.kernel-stuff@comcast.net \
    --to=kernel-stuff@comcast.net \
    --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