From: Tejun Heo <tj@kernel.org>
To: Evgeni Golov <sargentd@die-welt.net>
Cc: Elias Oltmanns <eo@nebensachen.de>, Mark Lord <liml@rtr.ca>,
linux-ide@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Odd behaviour of device in response to idleimmediate with unload
Date: Sun, 16 Nov 2008 18:39:08 +0900 [thread overview]
Message-ID: <491FEA3C.4090906@kernel.org> (raw)
In-Reply-To: <20081113113345.12E2D1FD80@chi.die-welt.net>
Hello,
Evgeni Golov wrote:
>> The first call to dmesg is only to make sure that it is in the cache so
>> the second won't be blocked by the park request.
>
> Okay, I get the following as soon I issue unload:
> ata1: exception Emask 0x10 SAct 0x0 SErr 0x50000 action 0xf
> ata1: SError: { PHYRdyChg CommWake }
> ata1: hard resetting link
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: SError: 0x0
>
> The rest comes a bit later.
So, this comes before actually issuing the park. It sounds like it has
nothing to do with park command itself. If you do "echo - - - >
/sys/class/scsi_host/host0/scan" right after boot, what does the kernel say?
Thanks.
--
tejun
next prev parent reply other threads:[~2008-11-16 9:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 10:31 Odd behaviour of device in response to idleimmediate with unload Elias Oltmanns
2008-11-04 10:40 ` Tejun Heo
2008-11-04 12:32 ` Evgeni Golov
2008-11-04 17:06 ` Mark Lord
2008-11-04 17:18 ` Mark Lord
2008-11-04 17:47 ` Mark Lord
2008-11-04 18:13 ` Mark Lord
2008-11-04 18:54 ` Evgeni Golov
2008-11-04 19:39 ` Mark Lord
2008-11-05 9:32 ` Tejun Heo
2008-11-05 13:47 ` Elias Oltmanns
2008-11-05 14:08 ` Tejun Heo
2008-11-05 18:55 ` Elias Oltmanns
2008-11-06 11:23 ` Evgeni Golov
2008-11-06 12:12 ` Elias Oltmanns
2008-11-05 19:34 ` Evgeni Golov
2008-11-06 11:41 ` Elias Oltmanns
2008-11-07 4:08 ` Tejun Heo
2008-11-07 7:48 ` Evgeni Golov
2008-11-10 9:00 ` Tejun Heo
2008-11-10 10:26 ` Evgeni Golov
2008-11-10 11:35 ` Elias Oltmanns
2008-11-13 11:33 ` Evgeni Golov
2008-11-13 12:29 ` Elias Oltmanns
2008-11-16 9:39 ` Tejun Heo [this message]
2008-11-17 7:15 ` Evgeni Golov
2008-11-17 7:19 ` Tejun Heo
2008-11-17 7:48 ` Evgeni Golov
2008-11-18 1:22 ` Tejun Heo
2008-11-18 7:37 ` Evgeni Golov
2008-11-21 6:41 ` Tejun Heo
2008-11-21 19:40 ` Evgeni Golov
2008-11-22 8:22 ` Tejun Heo
2008-11-22 9:51 ` Evgeni Golov
2008-11-22 9:58 ` Evgeni Golov
2008-11-23 18:09 ` Elias Oltmanns
2008-11-24 4:20 ` 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=491FEA3C.4090906@kernel.org \
--to=tj@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=eo@nebensachen.de \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=sargentd@die-welt.net \
/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).