From: Tejun Heo <tj@kernel.org>
To: "Benjamin S." <sbenni@gmx.de>
Cc: "Huang, Shane" <Shane.Huang@amd.com>,
Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org, rjw@suse.com
Subject: Re: ahci sometimes fails to suspend controller
Date: Tue, 04 Aug 2009 16:02:52 +0900 [thread overview]
Message-ID: <4A77DD1C.9010505@kernel.org> (raw)
In-Reply-To: <20090803103016.4305e098@pluto-lenny.milky.way>
Hello, Benjamin.
Benjamin S. wrote:
>> Can you please attach full log? I'm curious what exactly went down.
>
> Sure. Do you think the system should still be able to resume although
> the revalidation failed while suspending (see line [299208.016116])?
Interesting. This is the first time I see it failing this way.
[--snip--]
> [299202.632167] ahci 0000:00:11.0: suspend
> [299203.016052] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [299208.016032] ata3.00: qc timeout (cmd 0xec)
> [299208.016078] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> [299208.016116] ata3.00: revalidation failed (errno=-5)
This shouldn't have happened. The kernel is visiting each device and
suspending it. The process is ordered such that dependent devices
always go to sleep first. For some reason, something bad happens to
the ATA controller while other parts of the system are going to sleep
and I don't think it's solely software given the problem happens only
after a lot of trials.
[--snip--]
> [299249.128051] ata2: SATA link down (SStatus 0 SControl 300)
> [299249.128117] ata4: SATA link down (SStatus 0 SControl 300)
> [299249.128183] ata1: SATA link down (SStatus 0 SControl 300)
> [299249.156033] sd 2:0:0:0: legacy resume
> [299249.156037] sd 2:0:0:0: [sda] Starting disk
> [299254.172018] ata3: link is slow to respond, please be patient (ready=0)
> [299255.964034] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
And it looks like the device could operate normally after resume.
The error messages are from SCSI layer which now realized that the ATA
device is gone.
>>> Does that mean the SATA MSI quirk won't solve my problem?
>> I think it's likely a different issue. Can you please try to
>> reproduce the problem and see how many tries it usually takes?
>
> This time it were 79 successful resumes and the 80th one did not
> succeed.
>
> Because I never shutdown my system I will reproduce it by force,
> but I am going to try to script a little bit to automatically
> suspend and resume in order to get the next results faster.
Does irqpoll help?
cc'ing Rafael. Rafael, is there any chance that we're suspending
things in the wrong order?
Thanks.
--
tejun
next prev parent reply other threads:[~2009-08-04 7:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 20:04 ahci sometimes fails to suspend controller Benjamin S.
2009-07-23 10:11 ` Tejun Heo
2009-07-27 12:06 ` Benjamin S.
2009-07-28 2:50 ` Tejun Heo
2009-07-28 3:06 ` Huang, Shane
2009-07-28 4:10 ` Benjamin S.
2009-07-28 5:04 ` Huang, Shane
2009-08-02 17:08 ` Benjamin S.
2009-08-03 0:06 ` Tejun Heo
2009-08-03 8:30 ` Benjamin S.
2009-08-04 7:02 ` Tejun Heo [this message]
2009-08-04 15:33 ` Rafael J. Wysocki
2009-08-07 8:50 ` Benjamin S.
2009-08-08 8:39 ` Benjamin S.
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=4A77DD1C.9010505@kernel.org \
--to=tj@kernel.org \
--cc=Shane.Huang@amd.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=rjw@suse.com \
--cc=sbenni@gmx.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;
as well as URLs for NNTP newsgroup(s).