From: Mark Lord <lkml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: "\"J.A. Magallón\"" <jamagallon@ono.com>,
"Linux-Kernel, " <linux-kernel@vger.kernel.org>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [2.6.18-rc2-mm1] libata cdroms not automounted
Date: Fri, 04 Aug 2006 10:05:36 -0400 [thread overview]
Message-ID: <44D35430.2010600@rtr.ca> (raw)
In-Reply-To: <44D2F744.70302@gmail.com>
Tejun Heo wrote:
> J.A. Magallón wrote:
>> Hi...
>>
>> Following with my switch to libata for everything...
>> After latest patches, my burner and dvd work ok, apart from the fact that
>> they do not get auto-mounted in gnome environment.
>> udevmonitor shows nothing when a CD is inserted.
>
> Media insertion is not notified to user space via udev, so userspace
> implement cd automount by polling. IIRC, back when libata ATAPI support
> was premature, we had quite a few bug reports regarding error messages
> generated by those polling activities. Maybe your distribution disabled
> polling for SCSI cdroms for that reason. I seem to recollect the
> polling was done by some gnome daemon, not sure which though.
The problem at the time was that libata error handling was horribly broken
and would randomly lock up the system from time to time. Since CD autopolling
triggers a libata error each time it is done (1 or 2 times per second..),
it tended to trip over the libata EH bug and kill the system quite often.
I don't know what the distros did about it, other than patch the kernel
once we identified the issue.
Cheers
next prev parent reply other threads:[~2006-08-04 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 23:16 [2.6.18-rc2-mm1] libata cdroms not automounted J.A. Magallón
2006-08-04 7:29 ` Tejun Heo
2006-08-04 14:05 ` Mark Lord [this message]
2006-08-04 23:05 ` Jiri Slaby
2006-08-05 3:41 ` Tejun Heo
[not found] <fa.0fapZpsbPNwCajbQ53nT7FIKF1k@ifi.uio.no>
2006-08-03 2:37 ` Robert Hancock
2006-08-07 7:51 ` Robert Hancock
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=44D35430.2010600@rtr.ca \
--to=lkml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jamagallon@ono.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox