From: "D. Bahi" <dbahi@enterasys.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Expected SIGSTOP persists in 2.4.26-3um
Date: Tue, 17 Aug 2004 11:43:32 -0400 [thread overview]
Message-ID: <412227A4.6060005@enterasys.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
launching UMLs with nice seems to aggravate this problem --
but it also has been seen w/o adding that irritant.
status is 0x1c7f - which maps to 0x1c (SIGWINCH 28 right?)
here it is trying to panic and generates a segfault
#4 0x08051270 in main (argc=11, argv=0xbfffd3e4, envp=0xbfffd414) at
arch/um/main.c:148
#3 0x080dd2f4 in linux_main (argc=11, argv=0xbfffd3e4) at um_arch.c:332
#2 0x080d9154 in can_do_skas () at process.c:255
#1 0x080d9058 in stop_ptraced_child (pid=21301, stack=0x40001000,
exitcode=1) at process.c:182
#0 0x0805628c in panic (fmt=0x81c8080 "check_ptrace : child exited with
status 0x%x") at panic.c:67
values for locals and parameters in stop_ptraced_child are:
(gdb) print errno
$1 = 0
(gdb) print n
$2 = -1073774592
(gdb) print pid
$3 = 21301
(gdb) print status
$4 = 7295
(gdb) print exitcode
$5 = 1
(gdb) set radix 16
(gdb) print status
$6 = 0x1c7f
(gdb) print n
$7 = 0xbfff8000
also have seen:
2.4.24-1um + reboot-signals
Checking for the skas3 patch in the host...found
Checking for /proc/mm...found
CONFIG_HIGHMEM not enabled - physical memory shrunk to 499122176 bytes
Kernel virtual memory size shrunk to 32505856 bytes
capture_stack : Expected SIGSTOP, got status = 0x1c7f
2.4.26-3um
Checking for the skas3 patch in the host...found
Checking for /proc/mm...found
capture_stack : Expected SIGSTOP, got status = 0x1c7f
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
next reply other threads:[~2004-08-17 22:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 15:43 D. Bahi [this message]
2004-08-18 20:22 ` [uml-devel] No Bug Here: [Was: Expected SIGSTOP persists in 2.4.26-3um ] D. Bahi
2004-08-18 23:46 ` Jeff Dike
2004-08-19 2:23 ` D. Bahi
2004-08-19 3:53 ` D. Bahi
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=412227A4.6060005@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox