Re: kernel crash - no idea where ...

Jelle Foks (jelle@flying.demon.nl)
Wed, 5 Jan 2000 02:02:51 +0100 (CET)


On Mon, 3 Jan 100, Luis Kornblueh wrote:

> Dear kernel developers,

Well, I'm not one of the developers, but this is what I think.

> Jan 3 11:57:04 dailung kernel: Unable to handle kernel paging request at virtual address 41ebb8c0
> Jan 3 11:57:04 dailung kernel: current->tss.cr3 = 08c19000, %cr3 = 08c19000
> Jan 3 11:57:04 dailung kernel: *pde = 00000000
> Jan 3 11:57:04 dailung kernel: Oops: 0002
> Jan 3 11:57:04 dailung kernel: CPU: 1
> Jan 3 11:57:04 dailung kernel: EIP: 0010:[flush_signal_handlers+51/60]
> Jan 3 11:57:04 dailung kernel: EFLAGS: 00010206
> Jan 3 11:57:04 dailung kernel: eax: c1b68005 ebx: cca1a400 ecx: cca1be64 edx: 00000040
> Jan 3 11:57:04 dailung kernel: esi: cca1a2b2 edi: cb5da008 ebp: c1b68000 esp: cca1bca4
> Jan 3 11:57:04 dailung kernel: ds: 0018 es: 0018 ss: 0018
> Jan 3 11:57:04 dailung kernel: Process su (pid: 7440, process nr: 79, stackpage=cca1b000)
> Jan 3 11:57:04 dailung kernel: Stack: fffffff9 cca1bdc4 c0206b77 cff3cae0 cca1a000 c01369f4 cca1be64 c0246b90
> Jan 3 11:57:04 dailung kernel: fffffff8 cca1a000 cca1be64 c01dc4ac cfffa000 00000246 cca1a000 00000004
> Jan 3 11:57:04 dailung kernel: 00000001 c0269c20 c0457768 00000246 00000000 00000000 cff3a800 caa8c880
> Jan 3 11:57:04 dailung kernel: Call Trace: [cprt+887/34053] [load_elf_binary+1496/3404] [do_sd_request+460/472] [update_atime+94/100] [do_generic_file_read+1528/1540] [cprt+884/34053] [search_binary_handler+59/148]
> Jan 3 11:57:04 dailung kernel: [do_execve+417/480] [sys_execve+75/124] [system_call+52/56]
> Jan 3 11:57:04 dailung kernel: Code: 00 83 c0 14 4a 75 da c3 90 83 ec 08 55 57 31 ed 56 b9 00 e0

To my layman's eyes, this looks like the command 'su' is causing something
with address zero (jump to address zero? (???) null pointer?). It looks
like it happens when the process is being loaded from disk, or it could be
that is's happening when the 'su' process causes a particular process to
be loaded and started.

Is it somehow reproducable, or does it occur regularly? If so, how? Is the
system overclocked (if so, clock normally and see if the problem persists)?

Good luck,

Jelle.

> =======================================================================================================================================
>
> ksymoops output:
>
> Code: 00000000 Before first symbol 00000000 <_IP>: <===
> Code: 00000000 Before first symbol 0: 00 83 c0 14 4a 75 addb %al,0x754a14c0(%ebx) <===
> Code: 00000006 Before first symbol 6: da c3 fcmovb %st(3),%st
> Code: 00000008 Before first symbol 8: 90 nop
> Code: 00000009 Before first symbol 9: 83 ec 08 subl $0x8,%esp
> Code: 0000000c Before first symbol c: 55 pushl %ebp
> Code: 0000000d Before first symbol d: 57 pushl %edi
> Code: 0000000e Before first symbol e: 31 ed xorl %ebp,%ebp
> Code: 00000010 Before first symbol 10: 56 pushl %esi
> Code: 00000011 Before first symbol 11: b9 00 e0 00 00 movl $0xe000,%ecx
>
> - --

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/