Re: Kernel Crash on Shutdown

Menaka Lashitha Bandara (lashi@alphalink.com.au)
Mon, 14 Jun 1999 12:20:26 +1000

--------------3735BBDCFB252D1B27E55422
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Alan Cox wrote:

> > This is the dump I get on the screen when the kernel crashes:
> >
> > 80650058 803afef2 0000800d 00060000 00487f76 c241bfbc c01076b3 00000010
> > c241bfbv fee1dead c01e0018 00000018 00000000 bffffef2 fee1dead 00000282
> >
> > Call Trace: [<c0107665>] [<c01077a8>] [<c010850d>] [<c00113f93>]
>
> Is it still in a state you can scroll back to see the first EIP: value in
> the report above ?
>
> Can you also try a kernel that matches your existing one but has APM disabled
> and see if that also dies on shutdown
>
> Alan

Yes I am in a state where I can see the original EIP value. Here is the full
crash:

general protection fault: f000
CPU: 0
EIP: 0050:[<00008826>]
EFLAGS: 00010046
eax: 00005301 ebx: 00000001 ecx: 00000000 edx: 00000000
esi: bfff8076 edi: fee1dead ebp: 67890000 esp: c22d7e14
ds: 0058 es: 0000 ss: 0018
Process halt (pid: 1049, process nr:11, stackpage=c22d7000)
Stack: 0000bfff 7e2e6789 0001c22d 00000000 00030000 53070000 00000000 00000000
80650058 803afef2 0000800d 00060000 00487f76 c241bfbc c01076b3 00000010
c241bfbv fee1dead c01e0018 00000018 00000000 bffffef2 fee1dead 00000282
Call Trace: [<c0107665>] [<c01077a8>] [<c010850d>] [<c00113f93>] [<c01a3f8a>]
[<c01108c2>] [c010f80d>] [<c010fa28>] [<c01100ef>] [<c012efcb>] [<c0124e5b>]
[<c0124e7e>]
[<c0110deb>] [<cd09afc>]
Code: <1>Unable to handle kernel paging request at virtual address 00008826
Current -> tss.cr3 = 039bc000, %cr3 = 039bc000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c0109f5d>]
EFLAGS: 00010046
eax: 00000000 ebx: 00000000 ecx: 00008826 edx: 00000001
esi: 0000002b edi: c241c000 ebp: c4800000 esp: c241bc64
ds: 0018 es: 0018 ss: 0018
Process halt (Pid: 1049, process nr: 9, stackpage=c241b000)
Stack: fee1dead 67890000 c01e5d62 bfff8076 fee1dead 67890000 00005301 00000001
00000000 00000000 00008826 00010046 04000000 c5000000 c0109fc0 c241bdd8
c01a2578 c01a246d 0000f000 c241bdd8 c010a4c4 c01a264d c241bdd8 0000f000
Call Trace: [<c5000000>] [<c019fc0>] [<c01a2578>] [<c01a264d>] [<c010a4c4>]
[<c01a264d>] [<c0109c01>]
[<c0170058>] [<c01076b5>] [<c01077a8>] [<c01077cb>] [<c01077e9>] [<c01085od>]
[<c0113f93>] [<c01a3f8a>]
[<c01108c2>] [<c010f80d>] [<c010fa28>] [<c01100ef>] [<c012efcb>] [<c0123dd6>]
[<c0124e5b>] [<c0124e7e>]
[<c0110deb>] [<c0109afc>]
Code: 8a 04 0b 89 44 24 38 50 68 70 25 1a c0 e8 f5 97 00 00 83 c4

--------------3735BBDCFB252D1B27E55422
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
Alan Cox wrote:

> This is the dump I get on the screen when the kernel crashes:
>
> 80650058 803afef2 0000800d 00060000 00487f76 c241bfbc c01076b3 00000010
>  c241bfbv fee1dead c01e0018 00000018 00000000 bffffef2 fee1dead 00000282
>
> Call Trace: [<c0107665>] [<c01077a8>] [<c010850d>] [<c00113f93>]

Is it still in a state you can scroll back to see the first EIP: value in
the report above ?

Can you also try a kernel that matches your existing one but has APM disabled
and see if that also dies on shutdown

Alan

Yes I am in a state where I can see the original EIP value. Here is the full crash:

general protection fault: f000
CPU: 0
EIP: 0050:[<00008826>]
EFLAGS: 00010046
eax: 00005301 ebx: 00000001 ecx: 00000000 edx: 00000000
esi: bfff8076 edi: fee1dead ebp: 67890000 esp: c22d7e14
ds: 0058 es: 0000 ss: 0018
Process halt (pid: 1049, process nr:11, stackpage=c22d7000)
Stack: 0000bfff 7e2e6789 0001c22d 00000000 00030000 53070000 00000000 00000000
       80650058 803afef2 0000800d 00060000 00487f76 c241bfbc c01076b3 00000010
       c241bfbv fee1dead c01e0018 00000018 00000000 bffffef2 fee1dead 00000282
Call Trace: [<c0107665>] [<c01077a8>] [<c010850d>] [<c00113f93>] [<c01a3f8a>]
 [<c01108c2>] [c010f80d>] [<c010fa28>] [<c01100ef>] [<c012efcb>] [<c0124e5b>] [<c0124e7e>]
 [<c0110deb>] [<cd09afc>]
Code: <1>Unable to handle kernel paging request at virtual address 00008826
Current -> tss.cr3 = 039bc000, %cr3 =  039bc000
*pde = 00000000
Oops: 0000
CPU:  0
EIP: 0010:[<c0109f5d>]
EFLAGS: 00010046
eax: 00000000 ebx: 00000000 ecx: 00008826 edx: 00000001
esi: 0000002b edi: c241c000 ebp: c4800000 esp: c241bc64
ds: 0018 es: 0018 ss: 0018
Process halt (Pid: 1049, process nr: 9, stackpage=c241b000)
Stack: fee1dead 67890000 c01e5d62 bfff8076 fee1dead 67890000 00005301 00000001
       00000000 00000000 00008826 00010046 04000000 c5000000 c0109fc0 c241bdd8
       c01a2578 c01a246d 0000f000 c241bdd8 c010a4c4 c01a264d c241bdd8 0000f000
Call Trace: [<c5000000>] [<c019fc0>] [<c01a2578>] [<c01a264d>] [<c010a4c4>] [<c01a264d>] [<c0109c01>]
 [<c0170058>] [<c01076b5>] [<c01077a8>] [<c01077cb>] [<c01077e9>] [<c01085od>] [<c0113f93>] [<c01a3f8a>]
 [<c01108c2>] [<c010f80d>] [<c010fa28>] [<c01100ef>] [<c012efcb>] [<c0123dd6>] [<c0124e5b>] [<c0124e7e>]
 [<c0110deb>] [<c0109afc>]
Code: 8a 04 0b 89 44 24 38 50 68 70 25 1a c0 e8 f5 97 00 00 83 c4
  --------------3735BBDCFB252D1B27E55422-- - 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/