octave klaba <oles@ovh.net> writes:
> Hi,
> We had 2.2.14 kernel panic. We have lot of logs
> with lots of informations we do not understand.
>
> What have we do to know what was wrong ?
>
> Thnkas
> Octave
>
> exemple:
>
> Unable to handle kernel paging request at virtual address 0000217b
> current->tss.cr3 = 0b9e9000, %cr3 = 0b9e9000
> *pde = 00000000
> Oops: 0000
> CPU: 0
> EIP: 0010:[<c015f1d6>]
> EFLAGS: 00010282
> eax: 0000217b ebx: c1081d20 ecx: d69ea114 edx: d69ea114
> esi: ca3740b0 edi: c1081d20 ebp: d0a21e30 esp: d0a21e1c
> ds: 0018 es: 0018 ss: 0018
> Process ban_pub.pl (pid: 8178, process nr: 86, stackpage=d0a21000)
> Stack: 00000218 d69ea114 d3f0cf20 c014e4d1 d3f0cf20 ca374000 c015f51f ca374000
> c1081d20 00000218 ca374000 ca3740b0 ca374054 ca374000 c015f645 ca374000
> c1081d20 ca3740b0 c1081402 0000000e c015ca35 ca374000 ca3740b0 ca374000
> Call Trace: [<c014e4d1>] [<c015f51f>] [<c015f645>] [<c015ca35>] [<c015dd91>] [<c016281b>] [<c0162bb6>]
> [<c0155ed6>] [<c01561bd>] [<c014fcfd>] [<c0117811>] [<c010a097>] [<c0109d64>]
> Code: 83 38 01 0f 95 c0 25 ff 00 00 00 85 c0 0f 85 a2 01 00 00 8b
> Aiee, killing interrupt handler
> Scheduling in interrupt
>
> Amicalement,
> oCtAvE
>
> Connexion terminée par expiration du délai d'attente
>
Just save the oops in a file and run ksymoops on it.
Then post the result on lkml ( with, if possible a small description on
how to repeat, how it happen, etc... )
see /usr/src/linux/Documentation/oops-tracing.txt for more detail.
-- -- Yoann http://www.mandrakesoft.com/~yoann/ It is well known that M$ product don't make a free() after a malloc(), the unix community wish them good luck for their future developement.- 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/
This archive was generated by hypermail 2b29 : Sun May 07 2000 - 21:00:21 EST