From: "jds" <jds@soltis.cc>
To: Lou Langholtz <ldl@aros.net>, jds <jds@soltis.cc>
Cc: linux-kernel@vger.kernel.org, akpm@digeo.com
Subject: Re: Kernel Panic in 2.5.73-mm1 OOps part.
Date: Tue, 24 Jun 2003 15:27:13 -0600 [thread overview]
Message-ID: <20030624212347.M30881@soltis.cc> (raw)
In-Reply-To: <3EF8B15C.8030808@aros.net>
Hi Andrew, lou:
Diseable the # CONFIG_BLK_DEV_NBD is not set, in .config, compile again
kernel and working good.
Thanks .... :)
Iam testings my new kernel mm1
Regards.
---------- Original Message -----------
From: Lou Langholtz <ldl@aros.net>
To: jds <jds@soltis.cc>
Sent: Tue, 24 Jun 2003 14:15:24 -0600
Subject: Re: Kernel Panic in 2.5.73-mm1 OOps part.
> jds wrote:
>
> >Hi Andrew:
> >
> >
> > I have kernel panic when boot with kernel 2.5.73-mm1, in kernel 2.5.73
> >working good.
> >
> > Anex part the OOps: . . .
> >
> > [< c020f503>] kobject_register+0x23/0x60
> > [< blk_register_queue+0x80/0xb0
> > nbd_init+0x1df/0x220
> > do_initcalls+0x2b/0xa0
> > init_workqueues+0x12/0x30
> > init+0x28/0x150
> > init+0x0/0x150
> > kernel_thread_helper+0x50/0xc
> >. . .
> >
> I think this is my fault. I introduced a patch to nbd that
> apparantly doesn't use the block layer quite the way the block layer
> developers expect. As you found, it works on 2.5.73 but not in
> 2.5.73-mm1. I'm looking into why exactly this is so I can get a fix
> ASAP. In the meantime, if you take out the network block driver you
> shouldn't get this oops anymore.
------- End of Original Message -------
next prev parent reply other threads:[~2003-06-24 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 19:31 Kernel Panic in 2.5.73-mm1 OOps part jds
2003-06-24 20:09 ` Andrew Morton
2003-06-24 20:15 ` Lou Langholtz
2003-06-24 21:27 ` jds [this message]
2003-06-24 21:58 ` Lou Langholtz
2003-06-24 22:00 ` Lou Langholtz
2003-06-24 23:21 ` jds
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=20030624212347.M30881@soltis.cc \
--to=jds@soltis.cc \
--cc=akpm@digeo.com \
--cc=ldl@aros.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox