From: Kay Sievers <kay.sievers@vrfy.org>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Tejun Heo <tj@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [REGRESSION] cdrom drive doesn't detect removal
Date: Thu, 16 Sep 2010 08:51:28 +0200 [thread overview]
Message-ID: <AANLkTin37rbEbcGDejhcsnxZNYhhUWGy+x=v4Y=s0_Qx@mail.gmail.com> (raw)
In-Reply-To: <1284589207.4672.3.camel@maxim-laptop>
On Thu, Sep 16, 2010 at 00:20, Maxim Levitsky <maximlevitsky@gmail.com> wrote:
> So it makes the sense.
> It turns out that hal is still running on ubuntu systems, and yes, it
> still polls the drives, and yes I disabled that feature....
> So restoring that polling feature indeed fixes that problem for now.
> Yet, why without that commit detection did work?
Really, I have no idea how this can happen. You could only find out
with blocktrace, if something else is trying to open the device. The
state change in the drive should not be able to get known to the host
unless something is causing i/o with open().
Kay
next prev parent reply other threads:[~2010-09-16 6:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 9:49 [REGRESSION] cdrom drive doesn't detect removal Maxim Levitsky
2010-09-14 1:27 ` Maxim Levitsky
2010-09-14 7:39 ` Tejun Heo
2010-09-14 8:07 ` Kay Sievers
2010-09-14 23:38 ` Maxim Levitsky
2010-09-14 23:49 ` Kay Sievers
2010-09-15 0:37 ` Maxim Levitsky
2010-09-15 1:01 ` Kay Sievers
2010-09-15 13:27 ` Henrique de Moraes Holschuh
2010-09-15 13:44 ` Kay Sievers
2010-09-15 22:20 ` Maxim Levitsky
2010-09-16 6:51 ` Kay Sievers [this message]
2010-09-21 11:42 ` Maxim Levitsky
2010-09-21 23:09 ` Maxim Levitsky
2010-09-22 7:38 ` Tejun Heo
2010-09-22 13:41 ` Maxim Levitsky
2010-09-22 13:58 ` Maxim Levitsky
2010-09-23 8:47 ` Tejun Heo
2010-09-23 9:21 ` Kay Sievers
2010-09-30 6:30 ` Florian Mickler
2010-09-30 7:48 ` Kay Sievers
2010-09-30 11:38 ` Florian Mickler
2010-09-30 14:17 ` Maxim Levitsky
2010-09-30 14:49 ` Florian Mickler
2010-09-30 19:27 ` Kay Sievers
2010-09-30 20:14 ` Florian Mickler
2010-09-30 20:32 ` Kay Sievers
2010-09-30 20:47 ` Florian Mickler
2010-09-30 20:57 ` Kay Sievers
2010-10-01 5:55 ` Tejun Heo
2010-10-01 7:54 ` Florian Mickler
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='AANLkTin37rbEbcGDejhcsnxZNYhhUWGy+x=v4Y=s0_Qx@mail.gmail.com' \
--to=kay.sievers@vrfy.org \
--cc=axboe@kernel.dk \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.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 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.