From: Joe Marzot <gmarzot@nortelnetworks.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] 2.4.24 Kernel panic (patch 2.4.24-1)
Date: Wed, 12 May 2004 13:29:44 -0400 [thread overview]
Message-ID: <40A25F08.3060004@nortelnetworks.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
<oops - forgot to attach the back trace>
The following has been seen for some time on an intermittent basis. less
than 1:20 runs. Having trouble debugging it so I added some code to
panic.c:panic() to abort() and dump core. Also attached is a back trace
from that.
Kernel panic: handle_trap - failed to wait at end of syscall, errno = 2,
status = 383
appreciate any tips or tricks to get more information about this problem.
I have a core if that helps.
regards, Giovanni
ps. The kernel I am running is slightly modified but I do not believe
that is related. I will look more on a vanilla kernel just to be sure.
[-- Attachment #2: uml_kernel_panic.txt --]
[-- Type: text/plain, Size: 726 bytes --]
(gdb) bt
#0 0xa01643d1 in kill ()
at /localdisk/builds/3pc/2.4.22-i686sim/2.4.22/include/linux/if_vlan.h:122
#1 0xa018cbcb in raise ()
at /localdisk/builds/3pc/2.4.22-i686sim/2.4.22/include/linux/if_vlan.h:122
#2 0xa01646bd in abort ()
at /localdisk/builds/3pc/2.4.22-i686sim/2.4.22/include/linux/if_vlan.h:122
#3 0xa00d01d5 in handle_trap () at process.c:88
#4 0xa00d042c in userspace (regs=0xade0827c) at process.c:166
#5 0xa00d0bee in fork_handler (sig=10) at process_kern.c:102
#6 <signal handler called>
#7 0xa01643d1 in kill ()
at /localdisk/builds/3pc/2.4.22-i686sim/2.4.22/include/linux/if_vlan.h:122
#8 0xa00d4728 in os_usr1_process (pid=Cannot access memory at address 0x8
) at process.c:95
next reply other threads:[~2004-05-12 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 17:29 Joe Marzot [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-12 17:22 [uml-devel] 2.4.24 Kernel panic (patch 2.4.24-1) Joe Marzot
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=40A25F08.3060004@nortelnetworks.com \
--to=gmarzot@nortelnetworks.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