general protection: 0000
EIP: 0010:00126e9c
EFLAGS: 00010286
eax: f000ff53 ebx: 00009540 ecx: 011889a0 edx: 0018d8ac
esi: 00000000 edi: 005ea000 ebp: bffff308 esp: 00865f80
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process color_xterm (pid: 125, process nr: 30, stackpage=00865000)
Stack: 0011d04c 011889a0 00000000 401b9404 00000002 011889a0 0011d162 005ea000
00000002 401b9404 009dac0c 401b92a4 0802811b 005ea000 0010a489 401b92a4
00000002 401b9404 401b92a4 0802811b bffff308 ffffffda 0000002b 0010002b
Call Trace: 0011d04c 0011d162 0010a489
Code: 39 48 30 75 0f f6 40 11 08 74 09 b8 e6 ff ff ff c3 90 90 90
Occasionally the process is bash instead. The ksymoops program
generated this output based on the dump above:
EIP: 126e9c T get_write_access+3c/70
Trace: 11d04c T do_open+9c/180
Trace: 11d162 T sys_open+32/60
Trace: 10a489 T system_call+59/a0
Just after this particular one, any processes which tried to start
seg-faulted, so I had to reboot.
/-----------------------------------------------------------------------\
| Daniel K. Schepler | The distinguishing mark of an |
| dks2@cec.wustl.edu | idiot is that he never thinks |
| http://www.artsci.wustl.edu/~dkschepl | he is one. |
\-----------------------------------------------------------------------/