From: Frans Pop <elendil@planet.nl>
To: "Kay Sievers" <kay.sievers@vrfy.org>
Cc: "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 15:53:04 +0200 [thread overview]
Message-ID: <200810011553.05318.elendil@planet.nl> (raw)
In-Reply-To: <ac3eb2510809301302l7d966896tfb0e3d230598974@mail.gmail.com>
On Tuesday 30 September 2008, Kay Sievers wrote:
> >> 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.
Right. It happens with autoclose=0 too.
Any suggestions for the next step? Maybe add some instrumentation in the
cdrom or ide-cd drivers?
I think I'll also go back to 2.6.26 for a while to see if I can reproduce
it with that. I'm fairly sure it won't, but confirming that will be a
good data point.
I don't see myself bisecting this as long as I don't have a reliable way
to reproduce it.
BTW, I have considered a hardware problem like a short in the eject
button, but I don't think that's it. The eject button "feels" good and
I'd expect it to also spontaneously eject if that was the problem.
It also does feel like there is a pattern to it, even if I cannot see yet
what that pattern would be.
next prev parent reply other threads:[~2008-10-01 13:53 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
2008-10-01 10:17 ` Kay Sievers
2008-10-01 13:53 ` Frans Pop [this message]
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=200810011553.05318.elendil@planet.nl \
--to=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
Powered by JetHome