2.0.34pre11

Steve VanDevender (stevev@efn.org)
Tue, 21 Apr 1998 20:18:53 -0700 (PDT)

root@localhost.linux.org writes:
> Is it just me, or is tcp-networking totally fucked in 2.0.34pre11?

I can't start my X server under 2.0.34pre11, but I haven't quite
figured out why yet. These kernel messages are not
very enligtening, although in 2.0.X WTF is it doing going to
memory at 0xc0000008?

Apr 21 18:44:11 localhost kernel: Unable to handle kernel NULL pointer dereference at virtual address c0000008
Apr 21 18:44:11 localhost kernel: current->tss.cr3 = 00375000, ^\r3 = 00375000
Apr 21 18:44:11 localhost kernel: *pde = 00102067
Apr 21 18:44:11 localhost kernel: *pte = 00000000
Apr 21 18:44:11 localhost kernel: Unable to handle kernel NULL pointer dereference at virtual address c0000008
Apr 21 18:44:11 localhost kernel: current->tss.cr3 = 00101000, ^\r3 = 00101000
Apr 21 18:44:11 localhost kernel: *pde = 00102067
Apr 21 18:44:11 localhost kernel: *pte = 00000000
Apr 21 18:44:12 localhost kernel: Unable to handle kernel NULL pointer dereference at virtual address c0000008
Apr 21 18:44:12 localhost kernel: current->tss.cr3 = 00515000, ^\r3 = 00515000
Apr 21 18:44:12 localhost kernel: *pde = 00102067
Apr 21 18:44:12 localhost kernel: *pte = 00000000

I have strace output from the X server if anyone wants it, but
I'm going back to pre10.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu