From: Brian Gerst <bgerst@didntduck.org>
To: Mauricio Martinez <mauricio@coe.neu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS in read_cd... what to do?
Date: Mon, 27 Jan 2003 11:23:59 -0500 [thread overview]
Message-ID: <3E355D1F.1080007@didntduck.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0301270937370.18209-100000@Amps.coe.neu.edu>
Mauricio Martinez wrote:
> I reported twice (Jan 15 the last time) to this list a kernel oops when
> reading a CD in a SONY CDU-31A unit with kernels 2.4.18 - 2.4.20 (and
> probably all the 2.4 series), which works fine on 2.2.x (and even
> 1.2.x!!), maybe the maintainer of this part os the code is offline... Are
> there any alternatives to fix this problem? Thank you.
Drivers for older hardware like this are more than likely unmaintained,
and suffer from bit-rot. I don't have this hardware, but I can offer a
bit of analysis to help you debug this further. From the oops message
in your previous email, it looks like the oops occurred on line 1326 of
cdu31a.c. From the stack dump, I can see that input_data was called
with bytesleft=0x4000. This caused readahead_buffer + bytesleft to go
past the end of the module and oops.
--
Brian Gerst
next prev parent reply other threads:[~2003-01-27 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 14:43 OOPS in read_cd... what to do? Mauricio Martinez
2003-01-27 16:23 ` Brian Gerst [this message]
2003-01-28 12:51 ` Andreas Henriksson
2003-01-28 18:48 ` Alan Cox
2003-01-28 19:52 ` Andreas Henriksson
2003-01-29 4:07 ` Cabletron E2100 (e2100.c) Oops Andreas Henriksson
2003-01-29 21:25 ` OOPS in read_cd... what to do? Faik Uygur
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=3E355D1F.1080007@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mauricio@coe.neu.edu \
/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