On Sat, 22 Dec 2001, David S. Miller wrote:
> What compiler are you using to build these kernels? To be honest
> the assertion you have triggered ought to be impossible and this is
> the first report I've ever seen of it triggering.
Ok, i switched to kernel 2.4.17 and it happened again tonight.
Here's the output of ver_linux:
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux asterix 2.4.17-a1 #1 Sam Dez 22 13:39:51 CET 2001 i686 unknown
Gnu C 2.95.4
Gnu make 3.79.1
Linux C Library 2.2.4
Dynamic linker (ldd) 2.2.4
Modules Loaded nfs lockd sunrpc parport_pc lp parport
matroxfb_maven matroxfb_crtc2 cs46xx ac97_codec soundcore i2c-matroxfb
i2c-algo-bit i2c-core apm ide-scsi rtc
asterix:/usr/src/linux/scripts# gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
gcc version 2.95.4 20011006 (Debian prerelease)
Note that the kernel was compiled on asterix (another machine).
I also installed memtest86 and ran it a few days ago.
I still need to read up on its doc. but here is one error that came up
after HOURS of memtest86 running.
Address: 190fe988; 400.90MiB
Does it mean there's a one-bit error in the first (400.90<512) 512MB Module?
(This machine has 1GB memory in 2x512MB modules)
If so, I will remove this module and try again with only 512 MiB
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/