From: viro@parcelfarce.linux.theplanet.co.uk
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Linus Torvalds <torvalds@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] removal of legacy cdrom drivers (Re: [PATCH] mcdx.c insanity removal)
Date: Mon, 3 May 2004 22:34:19 +0100 [thread overview]
Message-ID: <20040503213419.GH17014@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <4096B810.5060907@keyaccess.nl>
On Mon, May 03, 2004 at 11:22:24PM +0200, Rene Herman wrote:
> viro@parcelfarce.linux.theplanet.co.uk wrote:
>
> >>However, any "cp" from cd-rom oopses the box.
> >
> >oopses in driver, oopses by triggering BUG() or oopses in fs/*? The last
> >two would be more interesting - isofs _MUST_ be able to survive any IO
> >errors, simply because CDs get scratched, etc. and that shouldn't crash
> >the box.
>
> Doesn't actually look all driver. The CD is good; works fine in this
> same drive with its own 2.0 kernel (and on other drives). Please note,
> this is a 386. Memory is good. dmesg and .config attached.
>
> Very long crash, but in case it's helpful. Happens when copying anything
> from the sbpcd CD-ROM. In between the "do_exit, do_divide_error,
> do_page_fault, do_page_fault" oopses it seems to be attempting to give
> me back a prompt (it's not succeeding).
Almost certainly a driver-induced memory corruption.
next prev parent reply other threads:[~2004-05-03 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040502024637.GV17014@parcelfarce.linux.theplanet.co.uk>
[not found] ` <Pine.LNX.4.58.0405011953140.18014@ppc970.osdl.org>
2004-05-03 1:16 ` viro
2004-05-03 3:21 ` Rene Herman
2004-05-03 5:59 ` viro
2004-05-03 18:08 ` Rene Herman
2004-05-03 19:45 ` viro
2004-05-03 21:22 ` Rene Herman
2004-05-03 21:30 ` Linus Torvalds
2004-05-03 21:34 ` viro [this message]
2004-05-05 23:41 ` Adrian Bunk
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=20040503213419.GH17014@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@keyaccess.nl \
--cc=torvalds@osdl.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®