From: "Sebastian Böhm" <seb@exse.net>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] crash of 2.4.27-bs1
Date: Tue, 07 Dec 2004 02:09:35 +0100 [thread overview]
Message-ID: <41B502CF.2010901@exse.net> (raw)
Hi,
want to help you to fix this, but ont know to debug this ?
it happend only minutes after booting that machine. (apache is running
on this machine delivering graphics produced via librsvg on-the-fly, the
crash happed during a http request)
------------------------------------------------------------
Kernel panic: Kernel stack overflow
Detaching after fork from child process 7385.
---Type <return> to continue, or q <return> to quit---
Program exited with code 01.
(gdb) bt
No stack.
(gdb)
------------------------------------------------------------
/sebastian
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
reply other threads:[~2004-12-07 1:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41B502CF.2010901@exse.net \
--to=seb@exse.net \
--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