Re: Signal 11 when using 'ps'
Thanks guys for the help.
Ok first, my CPU is not overclocked. My hardware is all fairly new
though, so I'll list the major components:
Athlon "Thunderbird" CPU, 1Ghz
Asus A7V mobo
Adaptec Ultra160 SCSI card
18Gb Seagate SCSI drive
"Geforce 2 GTS" based video card, 64MB
PCI USR modem (not winmodem)
PCI Soundblaster Live! Value
EIDE CDROM drive
EIDE CDRW drive
EIDE LS120 drive
Second, my System.map is up-to-date. The correct one is being loaded
at boot up.
Third, someone pointed me to a "Sig11 FAQ", but it assumes the sig11
errors are happening during a compile of the kernel. I can compile the
kernel just fine.
Fourth, the sig11 errors are occuring at the same place every time.
100% consistent. (Although ps's output has changed, see below.)
Ok, I've been playing around with BIOS settings and noticed something
has changed, ps is now sending its output to the screen twice. ??? The
following is a fragment of an strace of ps, followed by a gdb session
showing the duplicated output and a backtrace, if that helps.
**************************************
open("/boot/System.map-2.2.17", O_RDONLY|O_NONBLOCK|O_NOCTTY) = -1
ENOENT (No such file or directory)
open("/boot/System.map", O_RDONLY|O_NONBLOCK|O_NOCTTY) = 6
fstat(6, {st_mode=S_IFREG|0664, st_size=141296, ...}) = 0
old_mmap(NULL, 141297, PROT_READ|PROT_WRITE, MAP_PRIVATE, 6, 0) =
0x401df000
close(6) = 0
mremap(0x401be000, 135168, 12288, MREMAP_MAYMOVE) = 0x401be000
--- SIGSEGV (Segmentation fault) ---
Starting program: /bin/ps
(no debugging symbols found)...
(no debugging symbols found)...
(no debugging symbols found)...
PID TTY TIME CMD
423 pts/0 00:00:00 bash
433 pts/0 00:00:00 gdb
434 pts/0 00:00:00 ps
PID TTY TIME CMD
423 pts/0 00:00:00 bash
433 pts/0 00:00:00 gdb
434 pts/0 00:00:00 ps
(no debugging symbols found)...
(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x40022d1f in tty_to_dev () from /lib/libproc.so.2.0.6
(gdb) backtrace
#0 0x40022d1f in tty_to_dev () from /lib/libproc.so.2.0.6
#1 0x4002300a in open_psdb () from /lib/libproc.so.2.0.6
#2 0x804fcbf in strcpy ()
#3 0x40047cfc in __libc_start_main () from /lib/libc.so.6
(gdb)
**************************************
This is an strace of console-apt which is also giving me sig11 errors
(same place, same time, 100% consistent):
**************************************
--- SIGCHLD (Child exited) ---
ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(1, TIOCGWINSZ, {ws_row=43, ws_col=132, ws_xpixel=0, ws_ypixel=0})
= 0
ioctl(1, SNDCTL_TMR_STOP, {B38400 opost isig -icanon -echo ...}) = 0
write(1, "\33[1;43r\33[?25h", 13) = 13
write(1, "\33[39;49m\33[0;10m\33[4l\33[H\33[J", 25) = 25
write(1, "\33[43;1H\r", 8) = 8
ioctl(1, SNDCTL_TMR_STOP, {B38400 opost isig icanon echo ...}) = 0
write(2, "Assertion failure: Window creati"..., 42) = 42
write(1, "\33[?25l", 6) = 6
ioctl(1, SNDCTL_TMR_STOP, {B38400 opost isig -icanon -echo ...}) = 0
--- SIGSEGV (Segmentation fault) ---
close(4) = 0
rt_sigaction(SIGTSTP, {SIG_DFL}, NULL, 8) = 0
rt_sigaction(SIGWINCH, {SIG_DFL}, NULL, 8) = 0
close(3) = 0
ioctl(1, SNDCTL_TMR_STOP, {B38400 opost isig icanon echo ...}) = 0
write(1, "\33[43;1H\33[?25h", 13) = 13
write(1, "\r", 1) = 1
ioctl(1, SNDCTL_TMR_STOP, {B38400 opost isig icanon echo ...}) = 0
open("/root/.captrc", O_WRONLY|O_CREAT|O_TRUNC|0x8000, 0664) = 3
fstat(3, {st_mode=S_IFREG|0664, st_size=0, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x40017000
write(3, "description=1\n", 14) = 14
write(3, "sort=4/2\n", 9) = 9
write(3, "view=verbose\n", 13) = 13
write(3, "captris=0\n", 10) = 10
write(3, "captris_score=0\n", 16) = 16
close(3) = 0
munmap(0x40017000, 4096) = 0
write(2, "Exit: \"Signal Handler (sig11)\"\n", 31) = 31
_exit(11) = ?
**************************************
As you can see it SIGSEVs on an ioctl() call. If "SNDCTL_TMR_STOP" has
anything to do with sound, note that I have no sound driver installed.
What should I do? Would compiling ps with debug info and stepping
through it help? Should I try something else?
--
It is dangerous to be right when the government is wrong. -- Voltaire
Reply to: