|
Home > Archive > alt.os.linux > November 2002 > AMD bug?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| renato 2002-11-24, 5:24 am |
| Hi, my linux box is driving me mad, it freezes under loads. I normally use
it for compiling, Trying to compile QT31 ( that I use as benchmark now) I
succesfully compiled it once, otherwise the machine freezes randomly after
few seconds or after half an hour ( so I do not belive it is a temperature
problem) It seem to freeze sooner if I am running x (KDEas Wman) the only
time I was successfull I was compliing in text mode. My configuration is the
following:
AMD 1700+
Modem
Network card rtl 8139
Video card on ATI AGP All in wonder radeon
Video card NVIDIA TNT2 on PCI slot
RAID Highpoint 1370 (anused under linux, mandrake 8/9 sees it but not as a
raid)
DVD rom memorex
CD-RW yamaha
512 MB ram
Attemps made with no effect
playing around with all possible bios settings
append mem=nopentium
The box works fine under windows xp
any clever idea?
tx in advance
| |
| David Mills 2002-11-24, 5:24 am |
| On Sun, 24 Nov 2002 10:45:42 +0000, renato wrote:
>
> AMD 1700+
AMD K6 s and K6-2s were known to cause a system 11 under load, but I
haven't heard anything about AMD chips since, so I don't think it comes
from here...
> Modem
> Network card rtl 8139
> Video card on ATI AGP All in wonder radeon Video card NVIDIA TNT2 on PCI
> slot
> RAID Highpoint 1370 (anused under linux, mandrake 8/9 sees it but not as
> a raid)
> DVD rom memorex
> CD-RW yamaha
This lot would only play you up if you were using them (ie some usb
stuff can freeze the system if unplugged)
> 512 MB ram
Aha, you said you could compile in text mode, but not in graphic right?
It could well be a memory problem, personally, I'd get those chips
checked out, chances are you've got a duff chip near the top of that, so
that under normal usage it doesn't show, but when under heavy load (i
ie KDE's what's it, 120MB usage + compile) the machine uses the defective
address, and Bang.
>
> Attemps made with no effect
> playing around with all possible bios settings append mem=nopentium
>
Wouldn't change anything if it's a hardware fault
>
> The box works fine under windows xp
>
Doesn't mean much, unless you do massive compiles under XP...
Hope this Helps
David
--
David Mills
remove _nospam_ to reply
| |
| Martin Blume 2002-11-24, 6:24 am |
|
renato <TheCaptain@lycos.it> schrieb in im Newsbeitrag:
arqakj$6a0$1@lacerta.tiscalinet.it...
> Hi, my linux box is driving me mad, it freezes under loads. I normally use
> it for compiling, Trying to compile QT31 ( that I use as benchmark now) I
As David Mills has already said, this might be due to a memory problem.
Try a memory tester (memtest86), or remove one memory bank at a time and try
compiling again.
Compiling a large piece of software seems indeed to be an ideal stress test
for a machine ... :-)
> playing around with all possible bios settings
Did you play with memory access times in the BIOS?
Regards
Martin
| |
| renato 2002-11-24, 9:24 am |
| I must add that, a couple of time restarting the PC after the it froze, I
found out the bios settings had... changed, with the PCI slot coming up
first now....
"renato" <TheCaptain@lycos.it> wrote in message
news:arqakj$6a0$1@lacerta.tiscalinet.it...
> Hi, my linux box is driving me mad, it freezes under loads. I normally use
> it for compiling, Trying to compile QT31 ( that I use as benchmark now) I
> succesfully compiled it once, otherwise the machine freezes randomly after
> few seconds or after half an hour ( so I do not belive it is a temperature
> problem) It seem to freeze sooner if I am running x (KDEas Wman) the
only
> time I was successfull I was compliing in text mode. My configuration is
the
> following:
>
> AMD 1700+
> Modem
> Network card rtl 8139
> Video card on ATI AGP All in wonder radeon
> Video card NVIDIA TNT2 on PCI slot
> RAID Highpoint 1370 (anused under linux, mandrake 8/9 sees it but not as a
> raid)
> DVD rom memorex
> CD-RW yamaha
> 512 MB ram
>
> Attemps made with no effect
> playing around with all possible bios settings
> append mem=nopentium
>
>
> The box works fine under windows xp
>
>
> any clever idea?
>
> tx in advance
>
>
| |
| David Mills 2002-11-24, 9:24 am |
| On Sun, 24 Nov 2002 14:32:49 +0000, renato wrote:
> I must add that, a couple of time restarting the PC after the it froze,
> I found out the bios settings had... changed, with the PCI slot coming
> up first now....
Could you give some more info please, because normally the bios doesn't
do very much in the way of PCI configuration, and certainly doesn't move
the card addresses arround...
David
--
David Mills
remove _nospam_ to reply
| |
| D. Stussy 2002-11-24, 4:24 pm |
| On Sun, 24 Nov 2002, renato wrote:
>Hi, my linux box is driving me mad, it freezes under loads. I normally use
>it for compiling, Trying to compile QT31 ( that I use as benchmark now) I
>succesfully compiled it once, otherwise the machine freezes randomly after
>few seconds or after half an hour ( so I do not belive it is a temperature
>problem) It seem to freeze sooner if I am running x (KDEas Wman) the only
>time I was successfull I was compliing in text mode. My configuration is the
>following:
>
>AMD 1700+
>Modem
>Network card rtl 8139
>Video card on ATI AGP All in wonder radeon
>Video card NVIDIA TNT2 on PCI slot
>RAID Highpoint 1370 (anused under linux, mandrake 8/9 sees it but not as a
>raid)
>DVD rom memorex
>CD-RW yamaha
>512 MB ram
>
>Attemps made with no effect
>playing around with all possible bios settings
>append mem=nopentium
>
>The box works fine under windows xp
>
>any clever idea?
>
>tx in advance
Defective motherboard.
Example: Some PC Chips motherboards of the M810 series say that they support
CPU's greater than 1.2GHz or 266 MHz FSB, but they really do not.
| |
| renato 2002-11-25, 3:24 am |
| what meant is that a couple of times, after restarting the pc,, the bios
parameters were altered, for example the TNT card, on the pci slot was the
one showing up on the reboot ( before the setting was "agp first". in one
occasion I found all the bios parameters reset to factory setting
Renato
"David Mills" <dmills_nospam_@caramail.com> wrote in message
news an.2002.11.24.15.24.01.146965.10614@caramail.com...
> On Sun, 24 Nov 2002 14:32:49 +0000, renato wrote:
>
> > I must add that, a couple of time restarting the PC after the it froze,
> > I found out the bios settings had... changed, with the PCI slot coming
> > up first now....
>
> Could you give some more info please, because normally the bios doesn't
> do very much in the way of PCI configuration, and certainly doesn't move
> the card addresses arround...
>
> David
>
> --
> David Mills
> remove _nospam_ to reply
| |
| Jeroen Geilman 2002-11-28, 5:24 pm |
| renato wrote:
> what meant is that a couple of times, after restarting the pc,, the bios
> parameters were altered, for example the TNT card, on the pci slot was the
> one showing up on the reboot ( before the setting was "agp first". in one
> occasion I found all the bios parameters reset to factory setting
Power supply.
You have a cheap (bad quality) or simply insufficient powersupply.
This is one of the most diagnosed - but most underrated - sources of
"apparent" hardware failures - if the power supply can't deliver the load
to an AMD Athlon XP 1700+ then all sorts of things can start to go wrong.
I should know - I have one.
Are you aware that that little piece of silicon uses MORE THAN 70 WATTS
continuously ?
Heh didn't think so - this translates to a continuous current flow of 40
AMPS - you could fry your brains with that !
Seriously, you need a power supply that can deliver AT LEAST 300 actual
Watts on the +3.3, +5 and +12 V buses combined - all the time...
Then again, it might be the processor - it was with me ;-)
I had all sorts of never-reproducible errors under windows 2000 and XP, and
fewer under windows 98, and swapped out everything I could think of - MoBo,
memory, harddrives - all to no avail...until I simply put in a new Athlon
XP, and all the problems were *gone* - at once.
So yes, it *is* definitely possible that the processor is the cause of this,
but it's not a bug - I am very, very pleased with my AMD Athlon XP 1700 -
but it can be, say, faulty cache memory (yes, again, in my case...remember
the cache memory makes up for fully 1/3 of the 50 MILLION transistors on
this chip!), some reports suggest that up to 5% of all factory-delivered
AMD processors can be defective.
This is why burn-in testing is *crucial*...
And a good solid system compile (gentoo anyone ?) is most definitely a
burn-in test !
Widnose won't even come close to using that much CPU power...
HTH
J
|
|
|
|
|