From: "Tom Spink" <tspink@gmail.com>
To: "Kay Sievers" <kay.sievers@vrfy.org>
Cc: "Frans Pop" <elendil@planet.nl>, "Tony Vroon" <tony@vroon.org>,
linux-kernel@vger.kernel.org, "Tejun Heo" <tj@kernel.org>,
"Jens Axboe" <jens.axboe@oracle.com>
Subject: Re: CD tray closes spontaneously after opening it
Date: Wed, 1 Oct 2008 08:48:19 +0100 [thread overview]
Message-ID: <7b9198260810010048q170c72f4wfc306505f1a6ac00@mail.gmail.com> (raw)
In-Reply-To: <ac3eb2510809301302l7d966896tfb0e3d230598974@mail.gmail.com>
2008/9/30 Kay Sievers <kay.sievers@vrfy.org>:
> On Tue, Sep 30, 2008 at 9:50 PM, Frans Pop <elendil@planet.nl> wrote:
>> On Tuesday 30 September 2008, Kay Sievers wrote:
>>> Does:
>>> /sbin/udevadm monitor --env
>>> print something while you see the tray closing?
>>
>> I was somewhat lucky to reproduce it with that running and there was no
>> output during the open or close. I guess that rules out udev?
>
> I think so, yes.
>
>> I still don't know how to reliably reproduce this. It seems that after it
>> has occurred once, it will not occur again unless the system is rebooted.
>> But I'm not 100% sure of that.
>>
>> Most times I've seen it was after playing a DVD when ejecting the disc to
>> put it back in its box, but not when the DVD was inserted earlier.
>> But I've also seen it shortly after the system is booted when just opening
>> the tray with no media inserted.
>>
>> Just to be clear: until recently the drive has always behaved perfectly in
>> the same situations.
>>
>>> Does this also happen when you set:
>>> /proc/sys/dev/cdrom/autoclose
>>> to 0?
>>
>> I'll set that on boot using /etc/sysctl.conf and will report if I can
>> still reproduce with that setting. I've checked that the "normal" value
>> is 1.
>
> That will prevent the closing, when something tries to open the device
> in blocking mode. If that solves the issue, you should start looking
> which process tries to access your drive.
>
> Kay
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Hi Kay,
If you can manage to reproduce this, can you try/have you tried
different kernel versions?
--
Tom Spink
next prev parent reply other threads:[~2008-10-01 7:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 10:47 Frans Pop
2008-09-30 11:18 ` Tony Vroon
2008-09-30 12:01 ` Frans Pop
2008-09-30 12:35 ` Frans Pop
2008-09-30 12:35 ` Kay Sievers
2008-09-30 12:47 ` Frans Pop
2008-09-30 13:55 ` Kay Sievers
2008-09-30 19:50 ` Frans Pop
2008-09-30 20:02 ` Kay Sievers
2008-10-01 7:48 ` Tom Spink [this message]
2008-10-01 10:17 ` Kay Sievers
2008-10-01 13:53 ` Frans Pop
2008-10-01 14:02 ` Boris Petkov
2008-10-07 22:47 ` Frans Pop
2008-10-01 14:44 ` Jiri Slaby
[not found] <bhKXZ-55E-11@gated-at.bofh.it>
[not found] ` <bhTyc-7OL-11@gated-at.bofh.it>
[not found] ` <bhTHP-8fv-7@gated-at.bofh.it>
[not found] ` <biapp-4PE-1@gated-at.bofh.it>
2008-10-01 19:43 ` Bodo Eggert
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=7b9198260810010048q170c72f4wfc306505f1a6ac00@mail.gmail.com \
--to=tspink@gmail.com \
--cc=elendil@planet.nl \
--cc=jens.axboe@oracle.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=tony@vroon.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
all inboxes | Powered by JetHome®