From: "D. Bahi" <dbahi@enterasys.com>
To: uml devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] panic on shutdown bt for 2.4.26+ UML
Date: Mon, 23 May 2005 12:04:45 -0400 [thread overview]
Message-ID: <4291FF1D.70505@enterasys.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2244 bytes --]
any hints for where to look for a fix for this odd crash on shutdown?
i must admit, lately, i've been rather frustrated with the lack of
either maintainance or backporting in the 2.4 UML series. of course
this frustration is mostly because of my lack of ability to move forward
past issues such as these. but also the UML web-site + blaise's + other
patches out there along with all kinds of instructions on combinations
on what to use....
the mechanisims UML uses, jmps ptrace and the like, are not terribly
familar to generic programmers. Is there a UML: How it Works for
Developers - document somewhere? or must we be so dedicated that we
browse the mailing list archives and look for explainations piecemeal as
responses to queries (as we've seen recently on the list)?
appoligies for any toes i'm stepping on here - i want to help - i just
need help to get there...
(gdb) bt
#0 0x08161351 in kill ()
#1 0x0817d662 in raise ()
#2 0x0816163d in abort ()
#3 0x080dac3e in panic_coreonpanic (self=0x81fec3c, unused1=0,
unused2=0x8216d60) at um_arch.c:425
#4 0x0805e46a in notifier_call_chain (n=0x0, val=0, v=0x8216d60) at
sys.c:148
#5 0x080533d9 in panic (fmt=0x81d1780 "switch_mm_skas -
PTRACE_SWITCH_MM failed, errno = %d\n") at panic.c:77
#6 0x080dbf5a in switch_mm_skas (mm_fd=107) at process.c:353
#7 0x08050b17 in schedule () at mmu_context.h:29
#8 0x080d6d6e in cpu_idle () at process_kern.c:206
#9 0x0805047a in rest_init () at init/main.c:353
#10 0x080494e6 in start_kernel () at init/main.c:447
#11 0x080dc437 in start_kernel_proc (unused=0x0) at process_kern.c:179
#12 0x080d6979 in run_kernel_thread (fn=0x80dc410 <start_kernel_proc>,
arg=0x0, jmp_ptr=0x81fec3c) at process.c:231
#13 0x080dc162 in new_thread_handler (sig=10) at process_kern.c:72
#14 <signal handler called>
#15 0x08161351 in kill ()
#16 0x08160fe5 in siglongjmp ()
#17 0x080dbdc1 in start_idle_thread (stack=0x81f0000,
switch_buf_ptr=0x81f0578, fork_buf_ptr=0x0) at process.c:303
#18 0x080dc48a in start_uml_skas () at process_kern.c:193
#19 0x080daae3 in linux_main (argc=19, argv=0x30000000) at um_arch.c:393
#20 0x08050286 in main (argc=19, argv=0xbfffd0b4, envp=0xbfffd104) at
arch/um/main.c:149
#21 0x08160d13 in __libc_start_main ()
--
db
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
next reply other threads:[~2005-05-23 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 16:04 D. Bahi [this message]
2005-06-01 16:51 ` [uml-devel] panic on shutdown bt for 2.4.26+ UML Blaisorblade
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=4291FF1D.70505@enterasys.com \
--to=dbahi@enterasys.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 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.