Re: Oops in 2.0.24, unknown cause

Jared Mauch (jared@wolverine.hq.cic.net)
Tue, 24 Dec 1996 21:16:18 -0500 (EST)


Please run this through ksymoops so that we can get a stack trace and
determine what caused this problem.

Read /usr/src/linux/Documentation/oops-tracing.txt

It will provide more data on how to provide more information about
the crash.

- Jared

William Burrow graced my mailbox with this long sought knowledge:
>
> Well, this morning I found the VC running a shell slowly typing out ``x''
> over the screen. I hit ctrl-C to see what would happen, and got a general
> protection fault. Pressing keys in that VC gives a wait_queue bad error.
> I don't believe that the symbol table exists for that kernel anymore, as
> Linux generally does not Oops on me. The machine is otherwise up and
> semi-functional (it was semi-functional before the Oops). The details
> follow, if anyone is deeply interested:
>
> 0000
> CPU: 0
> EIP: 0010:[<001105a1>]
> EFLAGS: 00010286
> eax: 0020b4e8 ebx: c3007006 ecx: 0020b4e8 edx: f4000000
> esi: bffff4e8 edi: 0020b4e4 ebp: 00013f28 esp: 00013f1c
> ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
> Process bash (pid: 5660, process nr: 5, stackpage=00013000)
> Stack: 00000001 bffff4e8 00000000 00ca0000 0018a76f 0020b4e8 00186ea3 00ca0000
> 00ca0000 00d03780 00ca6000 00000001 00ca092c 00183971 00000000 00000000
> 00000000 00000001 bffff4e8 00c62018 00ca0930 00183875 00ca0000 00d03780
> Call Trace: [<0018a76f>] [<00186ea3>] [<00183971>] [<00183875>]
> [<00121096>] [<0010a772>]
> Code: 8b 02 83 f8 01 75 5e 9c 5e fa c7 02 00 00 00 00 83 7a 4c 00
> wait_queue is bad (eip = 001864c3)
> q = 00ca0934
> *q = 00013f68
>
>
> --
> William Burrow -- Fredericton Area Network, New Brunswick, Canada
> Copyright 1996 William Burrow
> Canada's federal regulator says it may regulate content on the Internet to
> provide for more Canadian content. (Ottawa Citizen 15 Nov 96 D15)
>
>