Re: oops in 2.4.19-rc1

Alan Cox (alan@lxorguk.ukuu.org.uk)
Wed, 10 Jul 2002 15:09:02 +0100 (BST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Arjan Opmeer: "Re: Oops with kernel BUG at dcache.c:345"
Previous message: Dipankar Sarma: "[OLS] RCU latency measurements"

> Yes, the kernel is tainted, thanks to NVdriver
> I booted with it, changed X to use nv driver and restarted X, so kernel
> stayed tainted, but module is no longer loaded.

The module could have done the damage already. Do this from a cold
boot never loading the NV driver. The crash looks like memory corruption
so its important to do this and may also be worth running memtest86 a bit
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Arjan Opmeer: "Re: Oops with kernel BUG at dcache.c:345"
Previous message: Dipankar Sarma: "[OLS] RCU latency measurements"