Re: Oops 2.0.27

Thomas Woinke (woinke@schieder.de)
Mon, 20 Jan 1997 15:39:25 +0100


Dies ist eine mehrteilige Nachricht im MIME-Format.

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

Adam D. Bradley wrote:
>
> > I experienced two random Oopses which said something about
> > 'unable to handle kernel paging request'
> >
> > They occured when no special stuff was running on my system,
> > I just booted and logged in.
> >
> > I use Kernel release 2.0.27.
> >
> > What could be wrong?
>
> We have no idea. ;-)
>
> Run the OOPS through ksymoops (found in /usr/src/linux/scripts) and post
> the results to the list, maybe then we can do something about it. You also
> may want to read /usr/src/linux/Documentation/oops-tracing.txt and
> BUG-HUNTING
>
> Adam
> --
> He feeds on ashes; a deluded mind has led him Adam Bradley, UNCA Senior
> astray, and he cannot deliver himself or say, Computer Science
> "Is there not a lie in my right hand?" Isaiah 44:20
> bradley@cs.unca.edu http://www.cs.unca.edu/~bradley <><
Hi,

Sorry for the little information I submitted.
I was speculating that this could be a common problem, due to the many
reports of oopses. A crash as a common problem under Linux...
I'm an idiot.
I dont have the appropriate System.map nor the Kernel handy
where the Oopses occured with. Here's the oops, hope you can deal with
it.

If not, no matter, I just wait until the oops happens again, and then I
will examine it! :-)

Thomas

--------------1D3F744068D1
Content-Type: text/plain; charset=us-ascii; name="oops"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="oops"

Nov 21 05:17:30 nexus kernel: Unable to handle kernel NULL pointer dereference at virtual address c0000040
Nov 21 05:17:30 nexus kernel: current->tss.cr3 = 0117f000, ^_r3 = 0117f000
Nov 21 05:17:30 nexus kernel: *pde = 00102067
Nov 21 05:17:30 nexus kernel: *pte = 00000027
Nov 21 05:17:30 nexus kernel: Oops: 0000
Nov 21 05:17:30 nexus kernel: CPU: 0
Nov 21 05:17:30 nexus kernel: EIP: 0010:[<00147a49>]
Nov 21 05:17:30 nexus kernel: EFLAGS: 00010202
Nov 21 05:17:30 nexus kernel: eax: 00000001 ebx: 00000000 ecx: 001c6da8 edx: c0646401
Nov 21 05:17:30 nexus kernel: esi: 00000000 edi: 00000000 ebp: ffffffff esp: 011efee0
Nov 21 05:17:30 nexus kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Nov 21 05:17:30 nexus kernel: Process arp (pid: 89, process nr: 20, stackpage=011ef000)
Nov 21 05:17:30 nexus kernel: Stack: 00000000 bffff978 00000000 011eff28 bffff978 00008952 00000801 bfffe000
Nov 21 05:17:30 nexus kernel: 016464c0 0014808f 011eff28 00000000 bffff944 00008952 bffff978 0125c808
Nov 21 05:17:30 nexus kernel: 011eff28 00000000 00000002 016464c0 40009f18 4000f878 15080001 000003cc
Nov 21 05:17:30 nexus kernel: Call Trace: [<0014808f>] [<0014a3d3>] [<00133925>] [<0012b8cb>] [<0010a3d2>]
Nov 21 05:17:30 nexus kernel: Code: 66 83 7e 40 17 75 b5 83 7c 24 2c 00 75 32 6a 00 8b 7c 24 24

--------------1D3F744068D1--