public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: John Goerzen <jgoerzen@complete.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.20 panic in scheduler
Date: Mon, 3 Feb 2003 13:35:06 -0800	[thread overview]
Message-ID: <20030203133506.A26686@figure1.int.wirex.com> (raw)
In-Reply-To: <87k7gh85pw.fsf@christoph.complete.org>; from jgoerzen@complete.org on Mon, Feb 03, 2003 at 02:33:15PM -0600

* John Goerzen (jgoerzen@complete.org) wrote:
> 
> Today I experienced a kernel panic running kernel 2.4.20 (plus the ctx
> vserver patch; otherwise vanilla) with a bcm5700 module added in.  It's

Have you tried this without the vserver patch?  Last I looked it touched
many of the code paths in your trace below.  Also, if possible, set up a
serial console, it'll be a lot easier to catch the full trace.

> Adhoc c01093ef <system_call+33/38>
> Adhoc c011a201 <schedule+501/530>

vserver touches this code

> Adhoc c01208c8 <release_task+e8/110>

vserver touches this code

> Adhoc c01218dc <sys_wait4+39c/410>
> Adhoc c01218de <sys_wait4+39e/410>
> Adhoc c012b419 <sys_release_ip_info+29/60>

this is vserver code which could be called from either release_task() or
inet_sock_destruct() (both are in this trace).

you get the idea...
cheers,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  reply	other threads:[~2003-02-03 21:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 20:33 Kernel 2.4.20 panic in scheduler John Goerzen
2003-02-03 21:35 ` Chris Wright [this message]
2003-02-03 21:48   ` John Goerzen
2003-02-04  6:57     ` Paul Rolland
2003-02-04 14:18       ` John Goerzen

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=20030203133506.A26686@figure1.int.wirex.com \
    --to=chris@wirex.com \
    --cc=jgoerzen@complete.org \
    --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