From: Ralph Gesler <rgesler@pacificnet.net>
To: Ray Olszewski <ray@comarre.com>
Cc: Bryan Simmons <bsimmo1@gl.umbc.edu>,
linux-newbie <linux-newbie@vger.kernel.org>
Subject: Re: CD-ROM Hell
Date: Wed, 02 Oct 2002 14:35:57 -0700 [thread overview]
Message-ID: <3D9B66BD.101284FA@pacificnet.net> (raw)
In-Reply-To: 5.1.0.14.1.20020930220638.02c84c60@celine
Ray Olszewski wrote:
<snip>
> The mere act of putting a CD in a drive shouldn't cause Linux to try to
> read the CD. You normally have to execute a "mount" command for the device
> (or mount point, if it is in /etc/fstab). You should be able to kill the
> process running the mount command to halt attempts to access the CD. If
> that option isn't available to you, you'll need to tell us how you have the
> system set up to mount CDs.
>
> BTW, I assume we are talking about iso9660 CDs here, not music CDs. If I'm
> mistaken in that assumption, please tell us what app you are using to rip
> the music CD (and you should probably tell us the basics of which Linux
> distro and version you are using). Here too, you should be able to get free
> by killing the process, whatever it might be.
>
A little bit late to this thread, but some symptoms that I have recently
seen that may point to Bryan's problem ( assuming it is not a bad CDROM
drive )which may point to a misconfiguration, e.g. driver, device
linkage. Experimenting with the CD dump program cdda2wav I find that if
I carelessly misstep or omit a command line device parameter, the
process hangs and can not be killed with SIGKILL ,i.e.. -9, even by the
super user. I am making a wild guess that this condition is caused by
some kernel io process, as yet unidentified: it does time-out and the
calling process, cdda2wav, dies.
I make this assumption because of the large amount of cpu usage used by
system at this time as shown by top. So far I have only observed this
with a music cd in the drive, but I have no reason to believe that the
same problem would not occur with a data, iso9660, cd. It may be
possible that a misconfiguration could cause the same symptoms.
kernel 2.4.4, Pentium 133
Ralph Gesler
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs
next prev parent reply other threads:[~2002-10-02 21:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 3:35 CD-ROM Hell Bryan Simmons
2002-10-01 4:20 ` James Miller
2002-10-01 21:24 ` Jude DaShiell
2002-10-01 5:13 ` Ray Olszewski
2002-10-02 21:35 ` Ralph Gesler [this message]
2002-10-01 6:38 ` Wladimir Foo
2002-10-02 0:26 ` Bryan Simmons
2002-10-02 2:30 ` Chuck Gelm
2002-10-02 4:01 ` Ray Olszewski
2002-10-02 4:16 ` David Jones
-- strict thread matches above, loose matches on Subject: below --
2002-10-03 11:09 Calin Szonyi
2002-10-03 17:38 ` Ralph Gesler
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=3D9B66BD.101284FA@pacificnet.net \
--to=rgesler@pacificnet.net \
--cc=bsimmo1@gl.umbc.edu \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.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 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.