From: Lawrence Gold <gold@shell.aros.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Oopses under 2.4.4pre8 with Tbird 1.2GHz/Epox 8kta3
Date: Mon, 30 Apr 2001 00:17:54 -0600 [thread overview]
Message-ID: <20010430001754.A96437@shell.aros.net> (raw)
I believe I've narrowed down the cause of my oopses/panics:
If I build with CONFIG_MK7 but comment out
define_bool CONFIG_X86_USE_3DNOW y
in the MK7 part of arch/i386/config.in, the 2.4.4 kernel appears to run
perfectly.
On a side note, if I leave arch/i386/config.h untouched but force the use
of the generic MMX implementations of fast_clear_page() and
fast_copy_page() in arch/i386/lib/mmx.c, then I get some odd behavior but
nothing as bad as I had been getting before. (For example, running awk
always produces the message "awk: cmd. line: 1: (FILENAME- FNR=1) fatal:
attempt to access field -2147483648".)
Could this be a sign of a faulty 3DNOW! core in my CPU? If so, do you
know of any utilities I could run that test these instructions? (For
Linux or Windows.)
The CPU is a 1.2GHz Athlon Thunderbird with a 266MHz frontside bus. In
case it's helpful, I've attached the contents of /proc/cpuinfo.
Thanks in advance to anyone who can help!
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 4
model name : AMD Athlon(tm) Processor
stepping : 2
cpu MHz : 1202.774
cache size : 256 KB
fdiv_bug : no
hlt_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 pae mce cx8 sep mtrr pge mca cmov
pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow
bogomips : 2398.61
next reply other threads:[~2001-04-30 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 6:17 Lawrence Gold [this message]
2001-04-30 17:07 ` Oopses under 2.4.4pre8 with Tbird 1.2GHz/Epox 8kta3 Alan Cox
2001-04-30 17:47 ` Lawrence Gold
2001-04-30 23:53 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-04-28 3:57 Lawrence Gold
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=20010430001754.A96437@shell.aros.net \
--to=gold@shell.aros.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.