linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: "maciej.rutecki@gmail.com" <maciej.rutecki@gmail.com>
Cc: Shaun Ruffell <sruffell@digium.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Tejun Heo <tj@kernel.org>
Subject: Re: [2.6.39-rc2][bisected] Constant DISK_MEDIA_CHANGE_EVENTS from CDROM drive.
Date: Sat, 16 Apr 2011 20:25:25 +0200	[thread overview]
Message-ID: <4DA9DF15.80603@fusionio.com> (raw)
In-Reply-To: <201104151913.38841.maciej.rutecki@gmail.com>

On 2011-04-15 19:13, Maciej Rutecki wrote:
> I created a Bugzilla entry at 
> https://bugzilla.kernel.org/show_bug.cgi?id=33342
> for your bug report, please add your address to the CC list in there, thanks!
> 
> On piątek, 8 kwietnia 2011 o 22:15:13 Shaun Ruffell wrote:
>> Running with 2.6.39-rc2 on a CentOS 5.5 installation with a "IDE interface:
>> Intel Corporation 82801CA Ultra ATA Storage Controller (rev 02)"
>> (8086:248b), I've noticed constant DISK_MEDIA_CHANGE uevents.  In my
>> kernel log:
>>
>> [ 1107.530699] kobject: 'hda' (f5372610): fill_kobj_path: path =
>> '/block/hda' [ 1109.580559] kobject: 'hda' (f5372610): kobject_uevent_env
>> [ 1109.580594] kobject: 'hda' (f5372610): fill_kobj_path: path =
>> '/block/hda' [ 1111.630560] kobject: 'hda' (f5372610): kobject_uevent_env
>> [ 1111.630595] kobject: 'hda' (f5372610): fill_kobj_path: path =
>> '/block/hda' [ 1113.680560] kobject: 'hda' (f5372610): kobject_uevent_env
>>
>> And from udevmonitor --env:
>>
>> UEVENT[1302291995.789487] change@/block/hda
>> ACTION=change
>> DEVPATH=/block/hda
>> SUBSYSTEM=block
>> DISK_MEDIA_CHANGE=1
>> MAJOR=3
>> MINOR=0
>> DEVNAME=hda
>> DEVTYPE=disk
>> SEQNUM=1318
>>
>> I bisected it down to 929e27252e8ca69363f81f26af5eaba62cb4c572 'ide:
>> ide_requeue_and_plug() reinstate "always plug" behaviour'
>>
>> I haven't yet looked into how that change would result in the change in
>> behavior I'm seeing but I thought I would let you know sooner rather than
>> leter in case this is something that is already known.

Tejun, why would something like that trigger and endless stream of media
change events? I bet this is what is cauing ide-cd to hang the system as
well now. What I know:

- It only triggers on UP
- And then it only triggers when PREEMPT is completely turned off

-- 
Jens Axboe


      reply	other threads:[~2011-04-16 18:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 20:15 [2.6.39-rc2][bisected] Constant DISK_MEDIA_CHANGE_EVENTS from CDROM drive Shaun Ruffell
2011-04-15 17:13 ` Maciej Rutecki
2011-04-16 18:25   ` Jens Axboe [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=4DA9DF15.80603@fusionio.com \
    --to=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    --cc=sruffell@digium.com \
    --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).