Unable to handle kernel NULL pointer dereference at vir

Unable to handle kernel NULL pointer dereference at vir

Post by Petr Vandrove » Wed, 12 Dec 2001 02:40:16




Quote:

> I try to use VMWARE 3.0 under 2.4.16 and had problems, so I try under
> 2.4.17-pre7, with same results:

> ble to handle kernel NULL pointer dereference at virtual address 00000004
>  printing eip:
> Process vmnet-dhcpd (pid: 3209, stackpage=ce951000)
> Stack: d6275ca0 cf7cd7e0 d9106be2 cf7cd7e0 d6275d24 ce951f50 00000000 d91053d6

Known problem. Your kernel was compiled with different gcc than your
modules were. VMware 3.0 tries 'kgcc', 'egcs' and 'gcc' in this order
of preferrence - so you should do 'CC=gcc vmware-config.pl' if you
have kgcc/egcs installed and you compiled kernel yourself. Verify
that 'cat /proc/version' and
'objdump -s -j .comment /lib/modules/`uname -r`/misc/vmmon.o' both
report same gcc version.
                                            Petr Vandrovec

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. INFO: kernel: Unable to handle kernel NULL pointer dereference

Out of the blue today I received this message across the system from the
kernel:

Kernel: Unable to handle NULL pointer dereference at virtual address c0000030
kernel: current->tss.cr3 = 075c0000,
kernel: *pde = 00102067
kernel: *pte = 00000027

-------------

I am running v2.0.14 w/ SMP enabled on a Tyan S1668 MB.  Kernel compiled
with pentium pro optimization.  Anyone have any ideas?  I've never seen
this before.

Stephen Costaras

2. pointer swizzling

3. "Unable to handle kernel null pointer dereference"

4. CTX1562-CLR mode timings help...plz

5. Unable to handle kernel NULL pointer dereference at virtual address

6. Kernel 2.1.28 Networking problems

7. dsl and uswest

8. Unable to handle kernel NULL pointer dereference...

9. CRASH: Unable to handle kernel NULL pointer dereference...

10. Unable to handle kernel NULL pointer dereference... and others!

11. Problem with 2.4.20: Unable to handle kernel NULL pointer dereference at virtual address 00000004

12. Unable to handle kernel NULL pointer dereference