From: Jens Axboe <axboe@suse.de>
To: bil@beeb.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: problems with Mandrake 10.0 + kernel 2.6.8-rc2
Date: Mon, 9 Aug 2004 08:43:22 +0200 [thread overview]
Message-ID: <20040809064321.GF10418@suse.de> (raw)
In-Reply-To: <200408061409.56670.bil@beeb.net>
On Fri, Aug 06 2004, bil@beeb.net wrote:
> Hi,
> I've recently moved to Mandrake 10.0 (prompted by a defunct hard disk
> which neccesitated a complete re-install) and have had several problems.
> As a result I have upgraded my kernel from 2.6.3 to 2.6.7 and then 2.6.8-rc2.
> Unfortunately the fire may be hotter than the frying-pan (Old English
> Proverb) and I'm now in a state where I can't mount CDroms. I can
> read the raw device OK, so the basic driver (ide-cd) is OK, or at least
> it seems to be. I've added traces to isofs.ko and established that this
> initialises OK, but when I attempt to mount the driver it gets a return
> code of -EINVAL when it tries to read the superblock (get_sb_bdev?()).
>
> I'm pretty sure that this must be something set up wrong somewhere as
> it's unlikely that 2.6.7 (or 2.6.8) would be released without someone
> somewhere needing to mount a cdrom, but I have no idea where to go from
> here. I am not a kernel-hacker, though I did some many moons ago, but
> I know enough to patch and rebuild modules and test them. I took a look at
> the source code of ide-cd.c but can't make much sense of the way things are
> done these days, and have too many other things to do....
> Can anyone give me advice (or even better a fix)?
First step in bug reporting is including a step-by-step way to reproduce
(ie what you do when it fails). Also please include a dmesg -s100000
from a booted system, and your .config from 2.6.7.
--
Jens Axboe
next prev parent reply other threads:[~2004-08-09 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 13:09 problems with Mandrake 10.0 + kernel 2.6.8-rc2 bil
2004-08-09 6:43 ` Jens Axboe [this message]
[not found] ` <200408061607.18040.bil@beeb.net>
[not found] ` <871xikuw0j.fsf@barad-dur.crans.org>
2004-08-09 8:22 ` bil
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=20040809064321.GF10418@suse.de \
--to=axboe@suse.de \
--cc=bil@beeb.net \
--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.