From: Bernd Nottelmann <nottelm@uni-muenster.de>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org.nottelm@uni-muenster.d
Subject: Re: Oops with 2.4.0-test10 during ripping an audio cd with cdda2wav
Date: Tue, 14 Nov 2000 11:32:50 +0100 [thread overview]
Message-ID: <00111411325000.02019@pt2037> (raw)
In-Reply-To: <00111022341900.16665@pt2037> <20001111051829.A484@suse.de>
In-Reply-To: <20001111051829.A484@suse.de>
On Saturday 11 November 2000 05:18, you wrote:
Hi Jens,
(Sorry for the delay)
> This looks like cdrom.c:mmc_ioctl, CDROMREADAUDIO, kmalloc'ing too
> much memory, which triggers the BUG() in slab.c. I'm not quite sure
> how this is happening though, unless cdda2wav sets a negative ra.nframes
> (a quick browse on a version I have here shows it does not, maybe you
> have a different version).
>
> Is it reproducable? If so, could you try with this patch?
Yes, it is. But unfortunately I cannot apply your patch. A --dry-run
gave no errors, but when I really patched 2.4.0-test10, it came to
some weird error message (patch tells me, that some files are
already patched???). [Why not 2.4.0-test11p2? I use this machine
for some numerical calculations which take long time runs and
they are at the moment not restartable after a break. For this reasons
I do not prefer pre-kernels (but I use the 2.4.0-beta series because
it is more stable for my hardware than the 2.2-series).]
Bernd
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-14 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 21:34 Oops with 2.4.0-test10 during ripping an audio cd with cdda2wav Bernd Nottelmann
2000-11-11 4:18 ` Jens Axboe
2000-11-14 10:32 ` Bernd Nottelmann [this message]
2000-11-22 14:10 ` Success with 2.4.0-test11(-final) [was: Re: Oops with 2.4.0-test10 during ripping an audio cd with cdda2wav] Bernd Nottelmann
2000-11-22 15:27 ` Jens Axboe
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=00111411325000.02019@pt2037 \
--to=nottelm@uni-muenster.de \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org.nottelm \
/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