From: Tejun Heo <tj@kernel.org>
To: Matthijs Kooijman <matthijs@stdin.nl>
Cc: "Jameson Graef Rollins" <jrollins@finestructure.net>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"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>,
"Nacho Barrientos Arias" <nacho@debian.org>
Subject: Re: [regression] CD-ROM polling blocks suspend on some machines (Re: [PATCH 1/2] cdrom: always check_disk_change() on open)
Date: Sun, 11 Sep 2011 13:08:26 +0900 [thread overview]
Message-ID: <20110911040826.GP29319@htj.dyndns.org> (raw)
In-Reply-To: <20110907085037.GX10237@login.drsnuggles.stderr.nl>
On Wed, Sep 07, 2011 at 10:50:37AM +0200, Matthijs Kooijman wrote:
> Hi Tejun,
>
> > Also, can you please explain the steps needed to trigger this problem?
> I'm not the one that supplied the backtraces, but I'm having the same
> problem. I did a fairly extensive writeup on the Debian bug report,
> perhaps this could (help to) answer your question:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628600#23
>
> I'll leave the other questions to Jameson for now.
Hmm... so, hibernation, disk event or udev isn't the cause. Device
removal somehow ends up with stalled request queue hanging event check
which eventually propagates as failed freeze during hibernation
attempt.
Can someone please attach dmesg output cdrom_id is hung after dock
removal and also the output of sysrq-t?
Thanks.
--
tejun
next prev parent reply other threads:[~2011-09-11 4:08 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 ` [regression] CD-ROM polling blocks suspend on some machines (Re: [PATCH 1/2] cdrom: always check_disk_change() on open) Jonathan Nieder
2011-09-04 2:42 ` 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 [this message]
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=20110911040826.GP29319@htj.dyndns.org \
--to=tj@kernel.org \
--cc=amit.shah@redhat.com \
--cc=axboe@kernel.dk \
--cc=jean@schurger.org \
--cc=jluebbe@debian.org \
--cc=jrnieder@gmail.com \
--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=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
all inboxes | Powered by JetHome®