Dual athlon XP 1800 problems
I am having problems with dual athlons and more than 512M RAM. I have compiled several kernels with either ATHLON, 1386, i686 support with the same affect, I get a kernel that will fail to boot properly. Sometimes I get a kernel panic that outs to kdb, sometimes I get a freeze, and sometimes I get failed to mount root partition, but never has this kernel successfully come up. I am quite certain it is not the memory or the system ( I can get windblows 2k to run successfully with upto 3.5G RAM).
Here is the configuration:
Tyan S2460
Dual Athlon XP 1800
512M DDR DIMMS (also used 128, 256, and 1G)
Western Digital 20G Drive
Kernels 2.4.9, 2.4.16, 2.4.17, 2.5.2
configured for 4G
configured as 1386, 1686, and Athlon processor support configured with XFS support
configured with kdb support
Is there a patch for this? Am I configuring something wrong in the kernel?
TIA
Chris Croswhite
Quoted 3 lines · On Mon, Dec 31, 2001 at 06:12:16PM -0800, [email protected] wrote:
I am having problems with dual athlons and more than 512M RAM. Here is the configuration:
Dual Athlon XP 1800
^^
Not a valid SMP configuration. Some people are getting away with running XP's in SMP boxes, others aren't. And soon, it looks like no new XP's will run in SMP at all.
Take one out/boot a UP kernel, and see if the problems go away.
Dave.
Signature · 2 lines
Dave Jones. http://www.codemonkey.org.uk SuSE Labs.
I'm using a pair of XP 1700's just fine in an SMP configuration, so it appears to be valid (and does infact function in SMP).
Jeffrey H. Ingber (jhingber _at_ ix.netcom.com)
Quoted 21 lines · Dave Jones
Quoted 3 lines · On Mon, Dec 31, 2001 at 06:12:16PM -0800, [email protected] wrote:
I am having problems with dual athlons and more than 512M RAM. Here is the configuration:
Dual Athlon XP 1800^^Not a valid SMP configuration. Some people are getting away with running XP's in SMP boxes, others aren't. And soon, it looks like no new XP's will run in SMP at all.
Take one out/boot a UP kernel, and see if the problems go away.
Dave.
Signature · 7 lines
Dave Jones. http://www.codemonkey.org.uk SuSE Labs. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
I missed the original message, I'm running a dual athlon 1800+ XP system (actually both CPU for some reason get identified as MPs, but they are retail XP chips).
I assume you are using a tyan tiger or thunder motherboard (as I dont know of any others in retail yet). Is your ram registered ecc ram? If it's not, that most likely is your problem.
Is your ram from tyan's approved list? Mine isn't (crucial, but I have never had bad luck with them, even though others seem to have had some problems), but I would see if it would change if you would get ram from suppliers tyan reccomends.
On the issue of future motherboards not supporting XPs at all, I've read in multiple places that the rumor to that effect was false, and that the motherboards will not lock out XPs, they just won't be supported (much like motherboard manufacturers don't support overclocking, but many give you the means to do it). If you have information direct from the manufacturers, than I have no reason to not believe you.
Quoted 21 lines · Dave Jones
Quoted 3 lines · On Mon, Dec 31, 2001 at 06:12:16PM -0800, [email protected] wrote:
I am having problems with dual athlons and more than 512M RAM. Here is the configuration:
Dual Athlon XP 1800^^Not a valid SMP configuration. Some people are getting away with running XP's in SMP boxes, others aren't. And soon, it looks like no new XP's will run in SMP at all.
Take one out/boot a UP kernel, and see if the problems go away.
Dave.
Signature · 7 lines
Dave Jones. http://www.codemonkey.org.uk SuSE Labs. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Quoted 3 lines · Jeffrey H. Ingber
I'm using a pair of XP 1700's just fine in an SMP configuration, so it appears to be valid (and does in fact function in SMP).
Irrelevant. This issue was discussed to death a couple weeks ago. Some people got it working, some don't. No discernible Stepping issues. Don't argue the facts. PLEASE
Quoted 3 lines · Shaya Potter
I missed the original message, I'm running a dual athlon 1800+ XP system (actually both CPU for some reason get identified as MPs, but they are retail XP chips).
The identification string is written by the BIOS. Yours didn't know about XPs so it misidentified them as MPs. Upgrade your BIOS if this bugs you.
If ID string contradicts what you think you bought, don't trust the ID string.
Signature · 1 line
Andreas Bombe <[email protected]> DSA key 0x04880A44
Quoted 6 lines · Andreas Bombe
The identification string is written by the BIOS. Yours didn't know about XPs so it misidentified them as MPs. Upgrade your BIOS if this bugs you.
If ID string contradicts what you think you bought, don't trust the ID string.
x86info, and 2.5.2-dj11 both have code to correctly determine XP / MP.
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs
Quoted 10 lines · Dave Jones
Quoted 6 lines · Andreas Bombe
The identification string is written by the BIOS. Yours didn't know about XPs so it misidentified them as MPs. Upgrade your BIOS if this bugs you.
If ID string contradicts what you think you bought, don't trust the ID string.
x86info, and 2.5.2-dj11 both have code to correctly determine XP / MP.
Just getting linux up and running on this machine, so with the original debian kernel (2.2.20 UP) and x86info from its unstable, these retail XPs were identified as MPs
trillian:/home/spotter# uname -a Linux trillian 2.2.20 #1 Sun Nov 4 15:44:23 EST 2001 i686 unknown trillian:/home/spotter# x86info x86info v1.7. Dave Jones 2001 Feedback to <[email protected]>.
Found 1 CPU, but found 2 CPUs in MPTable. /dev/cpu/0/cpuid: No such device
Family: 6 Model: 6 Stepping: 2 [Athlon MP] Processor name string: AMD Athlon(tm) MP Processor 1800+
PowerNOW! Technology information
Available features:
Temperature sensing diode present.
prehaps 2.4.17 (compiling now) will make a difference, or does one need your kernel + x86info to do it correctly?
thanks,
shaya
Signature · 2 lines
spotter@{cs.columbia.edu,yucs.org}
http://yucs.org/~spotter/Followup to: <[email protected]> By author: Andreas Bombe <[email protected]> In newsgroup: linux.dev.kernel
Quoted 8 lines
The identification string is written by the BIOS. Yours didn't know about XPs so it misidentified them as MPs. Upgrade your BIOS if this bugs you.
If ID string contradicts what you think you bought, don't trust the ID string.
This seems very odd. I thought in Athlon processors the ID string came from the *CPU* (via CPUID), not the BIOS...
-hpa
Signature · 3 lines
<[email protected]> at work, <[email protected]> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt <[email protected]>
Quoted 2 lines · H. Peter Anvin
This seems very odd. I thought in Athlon processors the ID string came from the *CPU* (via CPUID), not the BIOS...
Software overridable cpuid strings are getting quick commonplace in CPUs from several vendors.
I beleive the reasoning is that sometimes the lead time from manufacture to marketing is long enough that the default power-on string may not be correct, hence the BIOS can do the XP/MP descrimination, and set accordingly. (Unless you've got a crap BIOS).
If anyone believes they have a BIOS which doesn't do this correctly, (/proc/cpuinfo reports XP, and x86info reports MP or vice versa), let me know, and I'll see what I can dig up.
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs
Quoted 10 lines · Dave Jones
Quoted 3 lines · H. Peter Anvin
This seems very odd. I thought in Athlon processors the ID string came from the *CPU* (via CPUID), not the BIOS...
Software overridable cpuid strings are getting quick commonplace in CPUs from several vendors.
Not applicable here, though.
-hpa
Quoted 8 lines · H. Peter Anvin
Followup to: <[email protected]> By author: Andreas Bombe <[email protected]> In newsgroup: linux.dev.kernelQuoted 5 lines
The identification string is written by the BIOS. Yours didn't know about XPs so it misidentified them as MPs. Upgrade your BIOS if this bugs you.
Quoted 6 lines
Quoted 3 lines
If ID string contradicts what you think you bought, don't trust the ID string.
This seems very odd. I thought in Athlon processors the ID string came from the *CPU* (via CPUID), not the BIOS...
It comes from there, but it is written there by the BIOS for Athlon (and I guess Duron, too).
http://www.heise.de/newsticker/data/jow-18.10.01-000/ (in German)
I searched a bit with Google but couldn't find an English page with that info right now.
Signature · 1 line
Andreas Bombe <[email protected]> DSA key 0x04880A44