All of lore.kernel.org
 help / color / mirror / Atom feed
* [uml-devel] 2.4.24 Kernel panic (patch 2.4.24-1)
@ 2004-05-12 17:29 Joe Marzot
  0 siblings, 0 replies; 2+ messages in thread
From: Joe Marzot @ 2004-05-12 17:29 UTC (permalink / raw)
  To: user-mode-linux-devel

[-- 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

^ permalink raw reply	[flat|nested] 2+ messages in thread
* [uml-devel] 2.4.24 Kernel panic (patch 2.4.24-1)
@ 2004-05-12 17:22 Joe Marzot
  0 siblings, 0 replies; 2+ messages in thread
From: Joe Marzot @ 2004-05-12 17:22 UTC (permalink / raw)
  To: user-mode-linux-devel

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.



-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-05-12 17:29 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-05-12 17:29 [uml-devel] 2.4.24 Kernel panic (patch 2.4.24-1) Joe Marzot
  -- strict thread matches above, loose matches on Subject: below --
2004-05-12 17:22 Joe Marzot

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.