From: Jonathan Nieder <jrnieder@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Jens Axboe" <axboe@kernel.dk>,
"Amit Shah" <amit.shah@redhat.com>,
"David Zeuthen" <zeuthen@gmail.com>,
"Martin Pitt" <martin.pitt@ubuntu.com>,
"Kay Sievers" <kay.sievers@vrfy.org>,
linux-kernel@vger.kernel.org, "Jean Schurger" <jean@schurger.org>,
"Jan Lübbe" <jluebbe@debian.org>,
"Matthijs Kooijman" <matthijs@stdin.nl>,
"Jameson Graef Rollins" <jrollins@finestructure.net>,
"Nacho Barrientos Arias" <nacho@debian.org>
Subject: [regression] CD-ROM polling blocks suspend on some machines (Re: [PATCH 1/2] cdrom: always check_disk_change() on open)
Date: Sat, 3 Sep 2011 17:14:56 -0500 [thread overview]
Message-ID: <20110903221456.GA2877@elie> (raw)
In-Reply-To: <20110406121920.GC4142@mtj.dyndns.org>
Hi,
Various people[1] have been noticing a race (or races?) in which the
cdrom_id and scsi_id programs from udev can get stuck in the D state
if udev doesn't sleep a little while before running them. This
prevents the machine from suspending. The problem was discovered with
Debian kernels
2.6.39-1
2.6.39-2
3.0.0-1
and was not experienced with kernel
2.6.38-5
(These kernels are closely based on v2.6.39, v2.6.39.1, v3.0, and
v2.6.38.5, respectively.) Reverting commit bf2253a6f00e (cdrom:
always check_disk_change() on open, 2011-04-29) seems to avoid
trouble.
One common theme seems to be DVD drives. Details at [1].
Known problem? Any ideas for tracking it down?
Looking forward to your thoughts,
Jonathan
[1] <http://bugs.debian.org/628600>. Submitters cc-ed.
next prev parent reply other threads:[~2011-09-03 22:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 12:20 [PATCH 1/2] cdrom: always check_disk_change() on open Tejun Heo
2011-04-06 12:22 ` [PATCH 2/2] block: rescan partitions on invalidated devices on -ENOMEDIA too Tejun Heo
2011-04-29 6:57 ` [PATCH 1/2] cdrom: always check_disk_change() on open Amit Shah
2011-04-29 8:15 ` Tejun Heo
2011-04-29 8:15 ` Jens Axboe
2011-04-29 8:16 ` Tejun Heo
2011-04-29 8:28 ` Jens Axboe
2011-05-10 6:42 ` Amit Shah
2011-05-10 7:44 ` Jens Axboe
2011-05-10 8:13 ` Amit Shah
2011-09-03 22:14 ` Jonathan Nieder [this message]
2011-09-04 2:42 ` [regression] CD-ROM polling blocks suspend on some machines (Re: [PATCH 1/2] cdrom: always check_disk_change() on open) Tejun Heo
2011-09-04 15:05 ` [regression] CD-ROM polling blocks suspend on some machines Jonathan Nieder
2011-09-05 1:49 ` [regression] CD-ROM polling blocks suspend on some machines (Re: [PATCH 1/2] cdrom: always check_disk_change() on open) Jameson Graef Rollins
2011-09-06 17:45 ` Tejun Heo
2011-09-07 8:50 ` Matthijs Kooijman
2011-09-11 4:08 ` Tejun Heo
2011-10-24 20:25 ` Gaudenz Steinlin
2011-10-26 18:26 ` Matthijs Kooijman - Brevidius
2011-10-26 22:25 ` Tejun Heo
2011-10-28 13:47 ` Matthijs Kooijman
2011-10-30 20:35 ` Tejun Heo
2011-10-31 9:28 ` Matthijs Kooijman
2011-10-31 15:26 ` Tejun Heo
2011-12-19 11:12 ` Matthijs Kooijman
2011-12-19 16:44 ` 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=20110903221456.GA2877@elie \
--to=jrnieder@gmail.com \
--cc=amit.shah@redhat.com \
--cc=axboe@kernel.dk \
--cc=jean@schurger.org \
--cc=jluebbe@debian.org \
--cc=jrollins@finestructure.net \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.pitt@ubuntu.com \
--cc=matthijs@stdin.nl \
--cc=nacho@debian.org \
--cc=tj@kernel.org \
--cc=zeuthen@gmail.com \
/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).