linux-um archives
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] skas3-related crash of the week
Date: Wed, 19 Nov 2003 20:23:30 +0000	[thread overview]
Message-ID: <877k1w85vh.fsf@amaterasu.srvr.nix> (raw)

Using unmodified 2.4.22-6. sshed in through the firewall on the UML
instance, with tty logging enabled: typing exit on the last sshed-in
console froze the box yielded this on the console before UML died:

Kernel panic: switch_mm_skas - PTRACE_SWITCH_MM failed, errno = 9

Kernel panic: switch_mm_skas - PTRACE_SWITCH_MM failed, errno = 9

Kernel panic: Kernel mode fault at addr 0x4, ip 0x400e64ce
Kernel panic: Kernel mode fault at addr 0x4, ip 0x400e64ce
Kernel panic: Kernel mode fault at addr 0x4, ip 0x400e64ce
Kernel panic: Kernel mode fault at addr 0x4, ip 0x400e64ce
Kernel panic: switch_mm_skas - PTRACE_SWITCH_MM failed, errno = 9

Kernel panic: Kernel mode fault at addr 0x4, ip 0x400e64ce
Kernel panic: Kernel mode fault at addr 0x4, ip 0x400e64ce
Kernel panic: Kernel mode fault at addr 0x4, ip 0x400e64ce
Kernel panic: Kernel mode fault at addr 0x4, ip 0x400e64ce
Kernel panic: Segfault with no mm
Kernel panic: Segfault with no mm
Kernel panic: Segfault with no mm
Kernel panic: Segfault with no mm
Kernel panic: Segfault with no mm
Kernel panic: Segfault with no mm
Kernel panic: Segfault with no mm
Kernel panic: Segfault with no mm
Kernel panic: Segfault with no mm
Kernel panic: Segfault with no mm
Kernel panic: Segfault with no mm
Kernel panic: Segfault with no mm
In idle task - not syncing
 <0>Kernel panic: Segfault with no mm
In idle task - not syncing

EBADF is a rather odd error to get from ptrace(): I wonder if this has
the same root cause as the EMFILE error I got a couple of weeks ago? It
looks like the error came from proc_mm_get_mm(), so something like
running out of fhs might explain it. Whatever it is, it's pretty
persistent: it looks like it panic-kills every process in turn until
it runs out.

As before, post-crash the box isn't remotely close to running out of
fhs:

1437    208     8192


(Now that the instance has crashed, I have an excuse to rebuild it with
debugging turned on, so the next report like this should have
backtraces.)

-- 
`Me, I want exploding spaceships and pulverized worlds and clashes of
 billion-year-old empires *and* competently written sentences.'
                                                    --- Matt Austern


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
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:[~2003-11-19 20:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 20:23 Nix [this message]
2003-11-19 20:59 ` [uml-devel] skas3-related crash of the week Nuno Silva
2003-11-19 21:42   ` Nix
2003-11-19 23:54     ` Nuno Silva
2003-11-20 11:34   ` Nuno Silva
2003-11-20 12:56     ` Jeff Chua
2003-11-20 15:23     ` Nix
2003-11-21  2:28       ` Jeff Dike
2003-11-21  3:41         ` [uml-devel] Host Oops with 2.4.22-6um on 2.6.0-test9-bk24 Christopher S. Aker

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=877k1w85vh.fsf@amaterasu.srvr.nix \
    --to=nix@esperi.org.uk \
    --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