Not reproducable crc error at boot :-(
Hi folks,
when booting pre5 I got a crc-error while uncompressing
the kernel this morning. (/usr/src/linux/lib/inflate.c:1166 AFAICS) Rebooting didn't trigger it again and it's the first time I ever saw it.
I've never had any SIG11 problems while compiling kernels so I wouldn't expect bad RAM. (Normal people probably run Seti@home,
I run "while make bzImage; do date >> /tmp/kcompile; make clean; done" ;-)
OTOH, it's not reproducable which seems an indicator for hardware trouble :-(
Does anybody have any ideas?
Linux version 2.4.0-test10-pre5 ([email protected]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Tue Oct 24 17:14:24 CEST 2000
processor : 0vendor_id : AuthenticAMD
cpu family : 5
model : 8
model name : AMD-K6(tm) 3D processor
stepping : 0
cpu MHz : 350.000809
cache size : 64 KBfdiv_bug : nohlt_bug : nosep_bug : nof00f_bug : nocoma_bug : no
fpu : yesfpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8 sep mmx 3dnow
bogomips : 699.60
Signature · 5 lines
Linux 2.4.0-test10-pre5 #1 Tue Oct 24 17:14:24 CEST 2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Hi,
I would suggest to increase the 8bit waitstates in the BIOS by +1 (or more). - you might have to increase the 16bit waitstates as well (or instead of the 8bit ones).
It cured such a problem for me: - A Intel Pentium PC that had run Netware 3.12 perfectly happily for years didn't boot up with a CRC error after installing RedHat 7.0 on it. - Increasing the 8bit waitstates from 1 to 2 cured the problem completely and the PC is rocksolid now. - The PC also ran Windows quite happily (I installed it after the trouble with Linux just to see if it would work - I was worried about the hardware having gone dodgy.)
Hope this helps.
Regards,
Anton
Quoted 46 lines · Remi Turk
Hi folks,
when booting pre5 I got a crc-error while uncompressing
the kernel this morning. (/usr/src/linux/lib/inflate.c:1166AFAICS) Rebooting didn't trigger it again and it's the first time I ever saw it.I've never had any SIG11 problems while compiling kernels so I wouldn't expect bad RAM. (Normal people probably run Seti@home,
I run "while make bzImage; do date >>/tmp/kcompile; make clean; done" ;-)OTOH, it's not reproducable which seems an indicator for hardware trouble :-(
Does anybody have any ideas?
Linux version 2.4.0-test10-pre5 ([email protected]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Tue Oct 24 17:14:24 CEST 2000
processor : 0
vendor_id: AuthenticAMD
cpu family : 5
model : 8
model name : AMD-K6(tm) 3D processor
stepping : 0
cpu MHz : 350.000809
cache size : 64 KBfdiv_bug: nohlt_bug: nosep_bug: nof00f_bug: nocoma_bug: no
fpu : yesfpu_exception: yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8 sep mmx 3dnow
bogomips : 699.60Signature · 5 lines
Linux 2.4.0-test10-pre5 #1 Tue Oct 24 17:14:24 CEST 2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Signature · 9 lines
Anton Altaparmakov Phone: +44-(0)1223-333541 (lab) Christ's College eMail: [email protected] Cambridge CB2 3BU WWW: http://www-stu.christs.cam.ac.uk/~aia21/ United Kingdom ICQ: 8561279 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/