From: Jeff Dike <jdike@addtoit.com>
To: Steven James <pyro@linuxlabs.com>
Cc: Phil Nadeau <phil@innercite.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Kernel idles in loop after loading IPv4
Date: Tue, 27 Jan 2004 23:39:30 -0500 [thread overview]
Message-ID: <200401280439.i0S4dUZw005532@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Tue, 27 Jan 2004 23:28:07 GMT." <Pine.LNX.4.58.0401272326020.25787@ucontrol.mobiledns.com>
pyro@linuxlabs.com said:
> I ran into that as well, but didn't have time to do much about it. As
> a further datapoint, if I disable all net support and pass it init=/
> bin/bash, I get the bash prompt (ubd filesystems do get checked/
> mounted) but then it goes into the idle loop and stays there.
Hmmm.
If you could get a stack trace from the last call to schedule, that would be
handy. You could automate it with
comm <n>
bt
c
end
with breakpoint <n> attached to schedule().
Jeff
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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-01-28 4:16 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 [this message]
2004-01-30 21:23 ` Phil Nadeau
2004-02-15 17:12 ` BlaisorBlade
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=200401280439.i0S4dUZw005532@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=phil@innercite.com \
--cc=pyro@linuxlabs.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