From: Jens Axboe <axboe@suse.de>
To: Jonathan Hudson <jonathan@daria.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.[234] kernel panic, DMA Pool, CDROM Mount Failure
Date: Sat, 28 Apr 2001 21:10:47 +0200 [thread overview]
Message-ID: <20010428211047.E11698@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0104281935560.687-100000@rfhome.fietze.de> <Pine.LNX.4.21.0104281935560.687-100000@rfhome.fietze.de> <20010428195742.C11698@suse.de> <1e14.3aeb0dc8.44a42@trespassersw.daria.co.uk>
In-Reply-To: <1e14.3aeb0dc8.44a42@trespassersw.daria.co.uk>; from jonathan@daria.co.uk on Sat, Apr 28, 2001 at 06:36:56PM +0000
On Sat, Apr 28 2001, Jonathan Hudson wrote:
> In article <20010428195742.C11698@suse.de>,
> Jens Axboe <axboe@suse.de> writes:
> JA> On Sat, Apr 28 2001, Roman Fietze wrote:
> >> Hello,
> >>
> >> I reported this before and the bug still exists in 2.4.4. The problem can
> >> be circumvented by using drivers/scsi/sr.c from kernel 2.4.[01]. This
> >> "fix" did not help just me, but somebody else I had contact with on the
> >> net.
> JA>
> JA> Is the CDROM on the 1542?
> JA>
> JA> And could you include full panic info, please?
> JA>
>
> In my case, with AHA 1542 (as reported here earlier), I get:
>
> Apr 26 22:36:13 kanga kernel: sr: ran out of mem for scatter pad
> Apr 26 22:36:13 kanga kernel: Kernel panic: scsi_free:Bad offset
>
> Hope this is of some help.
Yes this one is known, and I have a partial fix already. I was just
curious as to whether Roman's problems are related or not.
--
Jens Axboe
next prev parent reply other threads:[~2001-04-28 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 17:42 Kernel 2.4.[234] kernel panic, DMA Pool, CDROM Mount Failure Roman Fietze
2001-04-28 17:57 ` Jens Axboe
2001-04-28 18:36 ` Jonathan Hudson
2001-04-28 19:10 ` Jens Axboe [this message]
2001-04-28 22:55 ` Roman Fietze
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=20010428211047.E11698@suse.de \
--to=axboe@suse.de \
--cc=jonathan@daria.co.uk \
--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 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.