linux-um archives
 help / color / mirror / Atom feed
From: Peter <peter.repliesignored@rimuhosting.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Kernel panic: Kernel stack overflow
Date: Thu, 02 Dec 2004 16:57:20 +1300	[thread overview]
Message-ID: <41AE92A0.4020401@rimuhosting.com> (raw)
In-Reply-To: <20041130193047.3370F8D743@zion.localdomain>

Hi.  I get a "Kernel panic: Kernel stack overflow" error message on the 
UML instance console.  Then the UML instance exits.

I am running a test where I start up then stop a JBoss server.  (This 
does a bit of network, file and thread related stuff).  The stack 
overflow happens every 3-8 JBoss restarts.  i.e. it is relatively 
reproducible.

The guest kernel is a 2.4.27-bs1.  The host is a 2.6.8.1.  With 
host-skas3-2.6.7-v1.patch.  (Hmmm, maybe that's it?  Try v7?)

What can I do to gather some more useful information about the error for 
you all?

Or, better still, is there a known fix?

Cheers, Peter


-------------------------------------------------------
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-02  3:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30 19:30 [uml-devel] [patch 1/1] uml: add stack content to dumps blaisorblade_spam
2004-12-02  3:57 ` Peter [this message]
2004-12-02 20:19   ` [uml-devel] Kernel panic: Kernel stack overflow Jeff Dike
2004-12-04  6:13     ` Peter

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=41AE92A0.4020401@rimuhosting.com \
    --to=peter.repliesignored@rimuhosting.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