From: Alan <alan@clueserver.org>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, <asun@cobaltnet.com>
Subject: Re: Kernel oops with 2.4.18
Date: Thu, 28 Feb 2002 22:02:50 -0800 [thread overview]
Message-ID: <200203010838.g218cYL15967@clueserver.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0203010850240.26745-100000@netfinity.realnet.co.sz>
In-Reply-To: <Pine.LNX.4.44.0203010850240.26745-100000@netfinity.realnet.co.sz>
On Thursday 28 February 2002 22:59, Zwane Mwaikambo wrote:
> On Thu, 28 Feb 2002, Alan wrote:
> > >>EIP; c01344c8 <grow_buffers+38/f0> <=====
> >
> > Trace; c0132767 <getblk+27/40>
> > Trace; c0132988 <bread+18/80>
> > Trace; c01e3c0d <scsi_release_command+7d/90>
> > Trace; c016f1f6 <hfs_buffer_get+26/80>
> > Trace; c016dd9a <hfs_mdb_get+aa/400>
> > Trace; c01e5e01 <ioctl_internal_command+151/160>
> > Trace; c016f0a5 <hfs_read_super+65/190>
> > Trace; c0135636 <get_sb_bdev+206/270>
> > Trace; c0122738 <handle_mm_fault+58/c0>
> > Trace; c0135a28 <do_kern_mount+b8/140>
> > Trace; c0145173 <do_add_mount+23/d0>
> > Trace; c01123c0 <do_page_fault+0/4cb>
> > Trace; c0106ffc <error_code+34/3c>
> > Trace; c014541b <do_mount+15b/180>
> > Trace; c014526c <copy_mount_options+4c/a0>
> > Trace; c01454bc <sys_mount+7c/c0>
> > Trace; c0106f0b <system_call+33/38>
> > Code; c01344c8 <grow_buffers+38/f0>
>
> Looks like another didnt_consider_other_blocksizes bug (nb. you're
> using a CDROM which has a block size of 2048). Maintainer CC'd
I figured it was something like that...
I am willing to test patches on the discs I am trying to read.
Thanks!
next prev parent reply other threads:[~2002-03-01 7:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 1:10 Alan
2002-03-01 6:59 ` Zwane Mwaikambo
2002-03-01 6:02 ` Alan [this message]
2002-03-11 17:55 ` Alan
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=200203010838.g218cYL15967@clueserver.org \
--to=alan@clueserver.org \
--cc=asun@cobaltnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linux.realnet.co.sz \
/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®