Skip to contentSkip to conversation

DISCOVERED! Cause of Athlon/VIA KX133 Instability

DISCUSSION Seth Goldberg 7 participants 12 messages May 1, 2001 – May 3, 2001 1 message not in the archive

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive

Hi :)

And that's exactly what I did :)... I found that ONLY the combination
of USE_3DNOW and forcing the athlon mmx stuff in (by doing #if 1 in mmx.c)
results in this wackiness. I should alos repeat that I *DO* see that wierdness you described with 3DNOW (in my case, it was that kde locks up when i try to do something).

This is damn weird... Who thought channging motherboards would result
in this?

The other thing i was gunna try is to dump my chipset registers using
WPCREDIT and WPCRSET and compare them with other people on this list who have been having the problem. Maybe our BIOS'es are not initting/are initting something they should/should not be :). It this point, I haven't ruled anything out...

--Seth

Quoted 17 lines · Lawrence Gold

Hi, Seth,

Just wanted to let you know that I got similar results to yours with my Epox 8KTA3 motherboard + Thunderbird. (If you've already seen the thread on the kernel mailing list, then please ignore this. ;)

If I leave the 3DNOW stuff enabled in arch/i386/config.in, but disable the K7-specific MMX optimizations, then the system doesn't panic on startup or oops continually, but I do get odd behavior, such as awk breaking.

If I disable just the 3DNOW stuff, then everything works really smoothly. I was planning on disabling one-by-one the parts of the code which use 3DNOW optimizations to see if there's a particular one that brings about instability.

I'll be sure to cc you on anything I find...

#2 lore raw
Quoted 3 lines

And that's exactly what I did :)... I found that ONLY the combination
of USE_3DNOW and forcing the athlon mmx stuff in (by doing #if 1 in results in this wackiness. I should alos repeat that I *DO* see that

I doubt that USE_3DNOW is causing the problem, but rather when you USE_3DNOW, the kernel streams through your northbridge at roughly twice the bandwidth. if your dram settings are flakey, this could eaily trigger a problem.

this has nothing to do with the very specific disk corruption being discussed (which has to do with the ide controller, according to the most recent rumors.).

Quoted 2 lines

The other thing i was gunna try is to dump my chipset registers using
WPCREDIT and WPCRSET and compare them with other people on this list

why resort to silly windows tools, when lspci under Linux does it for you?

regards, mark hahn.

#3 lore raw
Quoted 5 lines · Mark Hahn
Quoted 4 lines

And that's exactly what I did :)... I found that ONLY the combination
of USE_3DNOW and forcing the athlon mmx stuff in (by doing #if 1 in results in this wackiness. I should alos repeat that I *DO* see that

Quoted 8 lines

I doubt that USE_3DNOW is causing the problem, but rather when you USE_3DNOW, the kernel streams through your northbridge at roughly twice the bandwidth. if your dram settings are flakey, this could eaily trigger a problem.

this has nothing to do with the very specific disk corruption being discussed (which has to do with the ide controller, according to the most recent rumors.).

Actually, I think there are 2 problems that have been discussed -- the
disk corruption and a general instability resulting in oops'es at various points shortly after boot up.

My memory system jas been set up very conservitavely and has been
rock solid in my other board (ka7), so I doubt it's that, but I sure am happy to try a few more cominations of bios settings. Anything I should look for in particular?

Thanks,
Seth

Quoted 8 lines
Quoted 3 lines

The other thing i was gunna try is to dump my chipset registers using
WPCREDIT and WPCRSET and compare them with other people on this list

why resort to silly windows tools, when lspci under Linux does it for you?

regards, mark hahn.

Because lspci does not display all 256 bytes of pci configuration
information.

--S

#4 lore raw
Quoted 2 lines · Seth

Because lspci does not display all 256 bytes of pci configuration
information.

Umm, "lspci -xxx"? At least, on lspci version 2.1.8 from RedHat 7.1.

Wayne

#5 lore raw
In reply to Seth Goldberg
Quoted 7 lines
Quoted 3 lines

this has nothing to do with the very specific disk corruption being discussed (which has to do with the ide controller, according to the most recent rumors.).

Actually, I think there are 2 problems that have been discussed -- the
disk corruption and a general instability resulting in oops'es at various points shortly after boot up.

I don't see this. specifically, there were scattered reports of a via-ide problem a few months ago; this is the issue that's gotten some press, and for which Alan has a fix. and there are reports of via-smp problems at boot (which go away with noapic). I see no reports of the kind of general instability you're talking about. and all the via-users I've heard of have no such stability problems -
me included (kt133/duron).

the only general issue is that kx133 systems seem to be difficult to configure for stability. ugly things like tweaking Vio. there's no implication that has anything to do with Linux, though.

Quoted 5 lines

My memory system jas been set up very conservitavely and has been
rock solid in my other board (ka7), so I doubt it's that, but I sure am happy to try a few more cominations of bios settings. Anything I should look for in particular?

how many dimms do you have? interleave settings? Vio jumper? already checked on cooling issues? and that you're not overclocking...

Quoted 4 lines
Quoted 1 line

why resort to silly windows tools, when lspci under Linux does it for you?

Because lspci does not display all 256 bytes of pci configuration
information.

sure it does: (from my kt133 hostbridge)

[root@crema /root]# lspci -s 00:00.0 -xxx
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 02) 00: 06 11 05 03 06 00 10 22 02 00 00 06 00 00 00 00
10: 08 00 00 e0 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 27 a4 0b b4 46 02 08 08 08 00 00 00 04 08 08 08
60: 0c 00 00 00 d5 d6 d5 00 50 5d 86 0d 08 01 00 00
70: c9 88 cc 0c 0e a0 d2 00 01 b4 01 02 00 00 00 00
80: 0f 40 00 00 f0 00 00 00 02 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 02 c0 20 00 07 02 00 1f 00 00 00 00 2b 02 04 00
b0: 7f 63 2a 65 31 33 c0 0c 00 00 00 00 00 00 00 00
c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 0e 22 00 00 00 00 00 00 00

[root@crema /root]# od -Ax -txC /proc/bus/pci/00/00.0 000000 06 11 05 03 06 00 10 22 02 00 00 06 00 00 00 00 000010 08 00 00 e0 00 00 00 00 00 00 00 00 00 00 00 00 000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000030 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000050 27 a4 0b b4 46 02 08 08 08 00 00 00 04 08 08 08 000060 0c 00 00 00 d5 d6 d5 00 50 5d 86 0d 08 01 00 00 000070 c9 88 cc 0c 0e a0 d2 00 01 b4 01 02 00 00 00 00 000080 0f 40 00 00 f0 00 00 00 02 00 00 00 00 00 00 00 000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000a0 02 c0 20 00 07 02 00 1f 00 00 00 00 2b 02 04 00 0000b0 7f 63 2a 65 31 33 c0 0c 00 00 00 00 00 00 00 00 0000c0 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 0000d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 *
0000f0 00 00 00 00 00 00 00 0e 22 00 00 00 00 00 00 00 000100

#11 lore raw
In reply to Seth Goldberg
Quoted 4 lines
Quoted 1 line

why resort to silly windows tools, when lspci under Linux does it for you?

Because lspci does not display all 256 bytes of pci configuration
information.

RTFM ;)

#6 lore raw
In reply to Mark Hahn
Quoted 11 lines · Mark Hahn
Quoted 4 lines

Actually, I think there are 2 problems that have been discussed -- the
disk corruption and a general instability resulting in oops'es at various points shortly after boot up.

I don't see this. specifically, there were scattered reports
of a via-ide problem a few months ago; this is the issue that's gotten some press, and for which Alan has a fix. and there are reports of via-smp problems at boot (which go away with noapic). I see no reports of the kind of general instability you're talking about. and all the via-users I've heard of have no such stability problems - me included (kt133/duron).

the only general issue is that kx133 systems seem to be difficult to configure for stability. ugly things like tweaking Vio. there's no implication that has anything to do with Linux, though.

When I reported my problem a couple weeks back another fellow said he and several others on the list had the same problem, and as far as I can tell it is *only* with the IWILL boards. When I compiled with k7 optimizations I'd get all kinds of oopses and panics and never fully boot. They were different every time. When any of the lesser optimizations are used I have no problems. My memory is one 256MB Corsair PC150 dimm, CPU is a Thunderbird 850, and mobo is an IWILL KK266 (KT133A). The CPU runs between 35°C and 40°C.

Quoted 8 lines
Quoted 5 lines

My memory system jas been set up very conservitavely and has been
rock solid in my other board (ka7), so I doubt it's that, but I sure am happy to try a few more cominations of bios settings. Anything I should look for in particular?

how many dimms do you have? interleave settings? Vio jumper? already checked on cooling issues? and that you're not overclocking...

#7 lore raw
Quoted 5 lines
Quoted 3 lines

the only general issue is that kx133 systems seem to be difficult to configure for stability. ugly things like tweaking Vio. there's no implication that has anything to do with Linux, though.

Quoted 9 lines

When I reported my problem a couple weeks back another fellow said he and several others on the list had the same problem, and as far as I can tell it is *only* with the IWILL boards. When I compiled with k7 optimizations I'd get all kinds of oopses and panics and never fully boot. They were different every time. When any of the lesser optimizations are used I have no problems. My memory is one 256MB Corsair PC150 dimm, CPU is a Thunderbird 850, and mobo is an IWILL KK266 (KT133A). The CPU runs between 35°C and 40°C.

I'm using an Abit KT7 board (KT133) and my new 1GHz T'bird (running 50-60°C in a warm room) is giving me no trouble. This is with the board and RAM pushed as fast as it will go without actually overclocking anything... and yes, I do have Athlon/K7 optimisations turned on in my kernel (2.4.3).

Out of interest, what FSB are you using for your machine? I understand the difference between the KT133 and the KT133A is that the latter supports a 266MHz FSB for the Athlon rather than 200MHz. Since your CPU is running cool, I doubt you've managed to accidentally o/c it, but nevertheless this is a possibility...

The 266MHz FSB does require considerably higher standards in board construction though, so it could be that IWILL have managed to do a shoddy job on that end.

--------------------------------------------------------------

from:     Jonathan "Chromatix" Morton
mail:     [email protected]  (not for attachments)
big-mail: [email protected]
uni-mail: [email protected]

The key to knowledge is not to rely on people to teach you it.

Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/

-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*) -----END GEEK CODE BLOCK-----

#12 lore raw
In reply to Seth Goldberg
Quoted 5 lines · Seth Goldberg
Quoted 3 lines
Quoted 2 lines

The other thing i was gunna try is to dump my chipset registers using
WPCREDIT and WPCRSET and compare them with other people on this list

why resort to silly windows tools, when lspci under Linux does it for you?

Because lspci does not display all 256 bytes of pci configuration
information.

Say what?

Try lspci -vvxxx

-Dan

#8 lore raw
In reply to Mark Hahn

Thanks moses -- this is the instability that I have as well.
I tried compiling on 1/2 of the k7 optimized mmx routines. So far, running with JUST the fast_clear_page using k7 streaming (and not
fast_copy_page), the system is still stable. I'll try adding fast_copy _page, but I think that's where our problems lie (of course I could be full of crap, too).

--S

Quoted 44 lines · Moses McKnight
Quoted 13 lines · Mark Hahn
Quoted 4 lines

Actually, I think there are 2 problems that have been discussed -- the
disk corruption and a general instability resulting in oops'es at various points shortly after boot up.

I don't see this. specifically, there were scattered reports of a via-ide problem a few months ago; this is the issue that's gotten some press, and for which Alan has a fix. and there are reports of via-smp problems at boot (which go away with noapic). I see no reports of the kind of general instability you're talking about. and all the via-users I've heard of have no such stability problems -
me included (kt133/duron).

Quoted 3 lines

the only general issue is that kx133 systems seem to be difficult to configure for stability. ugly things like tweaking Vio. there's no implication that has anything to do with Linux, though.

When I reported my problem a couple weeks back another fellow said he and several others on the list had the same problem, and as far as I can tell it is *only* with the IWILL boards. When I compiled with k7 optimizations I'd get all kinds of oopses and panics and never fully boot. They were different every time. When any of the lesser optimizations are used I have no problems. My memory is one 256MB Corsair PC150 dimm, CPU is a Thunderbird 850, and mobo is an IWILL KK266 (KT133A). The CPU runs between 35°C and 40°C.

Quoted 8 lines
Quoted 5 lines

My memory system jas been set up very conservitavely and has been
rock solid in my other board (ka7), so I doubt it's that, but I sure am happy to try a few more cominations of bios settings. Anything I should look for in particular?

how many dimms do you have? interleave settings? Vio jumper? already checked on cooling issues? and that you're not overclocking...

-
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/

#9 lore raw
In reply to Mark Hahn
Quoted 6 lines · Jonathan Morton

I'm using an Abit KT7 board (KT133) and my new 1GHz T'bird (running 50-60°C in a warm room) is giving me no trouble. This is with the board and RAM pushed as fast as it will go without actually overclocking anything... and yes, I do have Athlon/K7 optimisations turned on in my kernel (2.4.3).

I wonder if the KT133A (which is what the IWILL KK266 is based on)
differences
a could be a source of the problem. My FSB is at plain old 100 MHz since I
have regular PC100 SDRAM. Overclocked, or not, I get the same results. I,
too, had an ABIT KA7[-RAID] and it was rock solid. So much for "if it's not broke, don't fix it" -- I should have listened to my gf, but that's the life of an upgrader ;)... In general the IWILL got great reviews at a
number of reliable hardware review sites, and hey, it doesn't lock up in windows ;) (ok don't flame me for that ;)).

--Seth

#10 lore raw
Quoted 6 lines
Quoted 5 lines

I'm using an Abit KT7 board (KT133) and my new 1GHz T'bird (running 50-60°C in a warm room) is giving me no trouble. This is with the board and RAM pushed as fast as it will go without actually overclocking anything... and yes, I do have Athlon/K7 optimisations turned on in my kernel (2.4.3).

Quoted 12 lines

I wonder if the KT133A (which is what the IWILL KK266 is based on)
differences
a could be a source of the problem. My FSB is at plain old 100 MHz since I
have regular PC100 SDRAM. Overclocked, or not, I get the same results. I,
too, had an ABIT KA7[-RAID] and it was rock solid. So much for "if it's not broke, don't fix it" -- I should have listened to my gf, but that's the life of an upgrader ;)... In general the IWILL got great reviews at a
number of reliable hardware review sites, and hey, it doesn't lock up in windows ;) (ok don't flame me for that ;)).

Maybe, but the IWILL board is the only one we've heard about problems with. The Abit KT7A (which also has the KT133A chipset and is otherwise identical to the KT7) would appear to run smoothly, although I don't actually *have* one of those. Probably the Windows drivers turn off some feature of the IWILL board which is known to be flaky.

I suggest setting *everything* in the BIOS to the "most conservative" settings and seeing if the problem persists. If so, then it can't be a hardware-speed-limitation problem, and there's clearly something we have to turn off "manually". Also, try running memtest86 and see if that is capable of triggering the problem.

--------------------------------------------------------------

from:     Jonathan "Chromatix" Morton
mail:     [email protected]  (not for attachments)
big-mail: [email protected]
uni-mail: [email protected]

The key to knowledge is not to rely on people to teach you it.

Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/

-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*) -----END GEEK CODE BLOCK-----