Re: 2.2.13 kernel oops

Eric Lowe (synrg@bgpc.dymaxion.ca)
Mon, 22 Nov 1999 20:59:22 -0400 (AST)

On Tue, 23 Nov 1999, Keith Owens wrote:
> There are three critical fields for an oops, the EIP, the call trace
> and the code. With only the eip it is almost impossible to determine
> the cause of the problem.

I'm afraid that's all there is. The system hung hard after that and
was unable to write anything else to the log.

We can see something in general, anyway ...

Nov 20 06:25:39 bgpc kernel: VM: Removing swap cache page with wrong inode hash on page c2105000
Nov 20 06:25:39 bgpc kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000004
Nov 20 06:25:39 bgpc kernel: current->tss.cr3 = 00b61000, %cr3 = 00b61000
Nov 20 06:25:39 bgpc kernel: *pde = 00000000
Nov 20 06:25:39 bgpc kernel: Oops: 0002

Seems to be a VM problem, doesn't it? And if so, are there VM
problems in 2.2.13 that could cause such an Oops and are there patches
I should try?

Ben

--
    nSLUG       http://www.nslug.ns.ca      synrg@sanctuary.nslug.ns.ca
    Debian      http://www.debian.org       synrg@debian.org
    Chebucto    http://www.chebucto.ns.ca   aa458@chebucto.ns.ca
[ pgp key fingerprint = 7F DA 09 4B BA 2C 0D E0  1B B1 31 ED C6 A9 39 4F ]




-
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/