From: Remi Turk <remi@a2zis.com>
To: linux-kernel@vger.kernel.org
Subject: Not reproducable crc error at boot :-(
Date: Fri, 27 Oct 2000 22:34:15 +0200 [thread overview]
Message-ID: <39F9E6C7.1C51B730@a2zis.com> (raw)
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 (src@localhost.localdomain)
(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 KB
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8 sep mmx 3dnow
bogomips : 699.60
--
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 majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-10-27 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 20:34 Remi Turk [this message]
2000-10-27 20:55 ` Not reproducable crc error at boot :-( Anton Altaparmakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39F9E6C7.1C51B730@a2zis.com \
--to=remi@a2zis.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox