From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: Phil Nadeau <phil@innercite.com>, roland <for_spam@gmx.de>,
UML Dev List <user-mode-linux-devel@lists.sourceforge.net>
Cc: Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Kernel idles in loop after loading IPv4
Date: Sun, 15 Feb 2004 18:12:22 +0100 [thread overview]
Message-ID: <200402151801.38113.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <1075497812.22009.41.camel@rocket.innercite.com>
Alle 22:23, venerdì 30 gennaio 2004, Phil Nadeau ha scritto:
> On Tue, 2004-01-27 at 20:39, Jeff Dike wrote:
> Here's the last part of a debug session that I ran which produced the
> error. The full transcript is attached. Thanks in advance.
Could you try to reproduce this bug running onto a 2.4 host-skas kernel with
the same guest kernel? Most people have no problem with the code; also, the
host-skas patch for 2.6 that you used has more than one bug (somebody even
reported kernel Oopses with that applied). Also, I'd like more info on the
host configuration: glibc/gcc version and distro used.
> NET: Registered protocol family 2
>
> Breakpoint 1, schedule () at kernel/sched.c:1489
> 1489 if (likely(!(current->state & (TASK_DEAD | TASK_ZOMBIE))))
> { #0 schedule () at kernel/sched.c:1489
> #1 0xa002db4e in wait_for_completion (x=0xa1fefb64) at kernel/sched.c:1758
> #2 0xa0041104 in synchronize_kernel () at kernel/rcupdate.c:262
> #3 0xa000b5dc in inet_init () at net/ipv4/af_inet.c:1144
An old message, "[uml-devel] wait queues broken?" on 19 November 2003, spoke
of something that could be related to this. Since everything is about
scheduling, this error message I got could be of interest:
Kernel panic: Kernel mode fault at addr 0x1f, ip 0x400d1397
Kernel panic: kernel BUG at kernel/exit.c:793!
The second message is of interest because the BUG line of interest reads as:
schedule();
BUG();
and this is fairly interesting.
To get this, I've run this command:
while /bin/true ; do /bin/true ; done
However, the kernel I was running went on after the "NET: Registered protocol
family 2" message.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&opÌk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-02-15 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 20:54 [uml-devel] Kernel idles in loop after loading IPv4 Phil Nadeau
2004-01-27 23:28 ` Steven James
2004-01-28 4:39 ` Jeff Dike
2004-01-30 21:23 ` Phil Nadeau
2004-02-15 17:12 ` BlaisorBlade [this message]
2004-02-16 16:48 ` Phil Nadeau
2004-02-16 18:16 ` Christopher Olson
2004-02-14 21:45 ` roland
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=200402151801.38113.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=for_spam@gmx.de \
--cc=jdike@addtoit.com \
--cc=phil@innercite.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).