From: Shaun Ruffell <sruffell@digium.com>
To: Jens Axboe <jaxboe@fusionio.com>
Cc: linux-kernel@vger.kernel.org
Subject: [2.6.39-rc2][bisected] Constant DISK_MEDIA_CHANGE_EVENTS from CDROM drive.
Date: Fri, 8 Apr 2011 15:15:13 -0500 [thread overview]
Message-ID: <20110408201513.GA3040@digium.com> (raw)
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.
next reply other threads:[~2011-04-08 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 20:15 Shaun Ruffell [this message]
2011-04-15 17:13 ` [2.6.39-rc2][bisected] Constant DISK_MEDIA_CHANGE_EVENTS from CDROM drive Maciej Rutecki
2011-04-16 18:25 ` Jens Axboe
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=20110408201513.GA3040@digium.com \
--to=sruffell@digium.com \
--cc=jaxboe@fusionio.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.