linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Linux-ide <linux-ide@vger.kernel.org>
Subject: Re: ata1: soft resetting port
Date: Thu, 05 Jul 2007 03:01:17 +0900	[thread overview]
Message-ID: <468BE06D.4010507@gmail.com> (raw)
In-Reply-To: <1183545657.22999.15.camel@localhost>

Soeren Sonnenburg wrote:
> On Tue, 2007-07-03 at 15:40 +0900, Tejun Heo wrote:
>> Soeren Sonnenburg wrote:
>>> Dear List,
>>>
>>> since the switch to 
>>>
>>> CONFIG_ATA=y
>>> CONFIG_ATA_ACPI=y
>>> CONFIG_ATA_PIIX=y,
>>>
>>> the ATA_PIIX driver manages both, internal sata disk aswell as cd/dvd
>>> rom. However I am being flooded with the error messages below (well they
>>> appear from time to time, dominating dmesg). 
>>>
>>> This happens on kernel 2.6.22-rc5, I am copying relevant parts from dmesg:
>> Does 2.6.22-rc7 fare better?
> 
> Yes indeed. The only thing I've seen in the last two days was the
> following on resume:
> 
> pci_express 0000:00:1c.2:pcie03: resuming
> sr 0:0:0:0: resuming
> sd 2:0:1:0: resuming
> sd 2:0:1:0: [sda] Starting disk
> ata1.00: configured for UDMA/33
> ata3.01: revalidation failed (errno=-2)
> ata3: failed to recover some devices, retrying in 5 secs
> ata3.01: configured for UDMA/133

Hmmm... That's NODEV_HINT being triggered after resume.  Probably the
device isn't ready to respond yet at that point.  How reproducible is
the problem?

-- 
tejun

  reply	other threads:[~2007-07-04 18:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 13:48 ata1: soft resetting port Soeren Sonnenburg
2007-07-03  6:40 ` Tejun Heo
2007-07-04 10:40   ` Soeren Sonnenburg
2007-07-04 18:01     ` Tejun Heo [this message]
2007-07-04 19:22       ` Soeren Sonnenburg
2007-07-05  2:21         ` 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=468BE06D.4010507@gmail.com \
    --to=htejun@gmail.com \
    --cc=kernel@nn7.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).