From: Elias Oltmanns <eo@nebensachen.de>
To: Tejun Heo <tj@kernel.org>
Cc: Evgeni Golov <sargentd@die-welt.net>, 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, 23 Nov 2008 19:09:50 +0100 [thread overview]
Message-ID: <878wrapb4h.fsf@denkblock.local> (raw)
In-Reply-To: <4927C14F.6050707@kernel.org> (Tejun Heo's message of "Sat, 22 Nov 2008 17:22:39 +0900")
Tejun Heo <tj@kernel.org> wrote:
> Evgeni Golov wrote:
>> On Fri, 21 Nov 2008 15:41:22 +0900 Tejun Heo wrote:
>
>>
>>> Something strange is going on there. Can you please apply the attached
>>> patch and post resulting kernel log?
>>
>> Wow, that one is spammy :)
>> See relevant part of /var/log/messages attached.
>
> Eh... you have ALPM enabled.
Quite. The thing that's puzzling me, though, is this: There are a lot of
phy events occurring during normal operation that get cleared by the
interrupt handler. However, during link autopsy, phyrdy and comwake are
set in SError even though event notification has not been disabled yet
at this point. This suggests to me that not all changes to those bits in
SError are brought to our attention through event notification, at least
as long as ALPM is enabled. Besides, I'm wondering whether that many phy
events are to be expected (i.e. observed on other controllers too) when
ALPM is enabled.
Regards,
Elias
next prev parent reply other threads:[~2008-11-23 18:10 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
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 [this message]
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=878wrapb4h.fsf@denkblock.local \
--to=eo@nebensachen.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=sargentd@die-welt.net \
--cc=tj@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).