Hi, I've recently experience mysterious shutdown on my AMD64 system. Just now, after the computer had been on, playing music (the only thing being done on it), it suddenly shut itself off. I have to "unplug and replug" the powersupply to have the computer start again. Is it possible, that some "hardware" in the system is causing this, the memory in the computer are two brand new ... two kingston 512Mb modules, the hard disk is also new, a SATA one. The CPU was bough earlier this year, the system being run is SuSE 9.2, with the latest upgrades from apt4rpm (gwdg.de). Personally, I'm thinking "powersupply" ... has anyone run into this behaviour? Örn
Looks like a hardware problem. Can you reproduce the shutdown? I would first test your memory since that is easiest to do. Brad Dameron SeaTab Software www.seatab.com On Thu, 2004-12-09 at 14:11, Örn Hansen wrote:
Hi,
I've recently experience mysterious shutdown on my AMD64 system. Just now, after the computer had been on, playing music (the only thing being done on it), it suddenly shut itself off. I have to "unplug and replug" the powersupply to have the computer start again.
Is it possible, that some "hardware" in the system is causing this, the memory in the computer are two brand new ... two kingston 512Mb modules, the hard disk is also new, a SATA one. The CPU was bough earlier this year, the system being run is SuSE 9.2, with the latest upgrades from apt4rpm (gwdg.de).
Personally, I'm thinking "powersupply" ... has anyone run into this behaviour?
Örn
torsdag 09 december 2004 23:28 skrev Brad Dameron:
Looks like a hardware problem. Can you reproduce the shutdown? I would first test your memory since that is easiest to do.
No, I'm running the machine now fine ... but the other day, it shutdown almost immediately after startup, and then I saw duplicate entries in the logfile, about the graphic card (see below), and "most" of the time this occurs is when I'm playing "Unreal Tournament, Red Orchestra" ... other times, I've had crashes when playing music. However, on my previous "Windoze" dual-boot, the hardware tool for the mobo, was alarming about the CPU core clock, not being at the 3.3 level and going below the 3.0 limit. In the BIOS, the Vcore is 1.540 V? -- part of log, prior to mysterious shutdown on Dec 9th (most recent) --- Dec 9 22:34:37 citadel gconfd (root-8590): startar (version 2.6.1), pid 8590 användare "root" Dec 9 22:34:37 citadel gconfd (root-8590): Slog upp adressen "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.mandatory" till en skrivskyddad konfigurationskälla på position 0 Dec 9 22:34:37 citadel gconfd (root-8590): Slog upp adressen "xml:readwrite:/root/.gconf" till en skrivbar konfigurationskälla på position 1 Dec 9 22:34:37 citadel gconfd (root-8590): Slog upp adressen "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.defaults" till en skrivskyddad konfigurationskälla på position 2 Dec 9 22:35:07 citadel gconfd (root-8590): GConf-servern används inte, stänger ner. Dec 9 22:35:08 citadel gconfd (root-8590): Avslutar Dec 9 22:40:33 citadel kernel: Losing some ticks... checking if CPU frequency changed. Dec 9 23:04:35 citadel syslogd 1.4.1: restart. -- part of log, prior to mysterious shutdown on Dec 8th --- Dec 8 19:29:00 citadel kernel: agpgart: Found an AGP 3.0 compliant device at 00 00:00:00.0. Dec 8 19:29:00 citadel kernel: agpgart: Device is in legacy mode, falling back to 2.x Dec 8 19:29:00 citadel kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode Dec 8 19:29:00 citadel kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode Dec 8 19:29:00 citadel /etc/dev.d/block/50-hwscan.dev[6681]: new block device /block/fd0 Dec 8 19:29:00 citadel /etc/dev.d/block/51-subfs.dev[6691]: mount block device /block/fd0 Dec 8 19:29:01 citadel kernel: agpgart: Found an AGP 3.0 compliant device at 00 00:00:00.0. Dec 8 19:29:01 citadel kernel: agpgart: Device is in legacy mode, falling back to 2.x Dec 8 19:29:01 citadel kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode Dec 8 19:29:01 citadel kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode Dec 8 19:31:12 citadel syslogd 1.4.1: restart.
Örn Hansen wrote:
Hi,
I've recently experience mysterious shutdown on my AMD64 system. Just now, after the computer had been on, playing music (the only thing being done on it), it suddenly shut itself off. I have to "unplug and replug" the powersupply to have the computer start again.
Is it possible, that some "hardware" in the system is causing this, the memory in the computer are two brand new ... two kingston 512Mb modules, the hard disk is also new, a SATA one. The CPU was bough earlier this year, the system being run is SuSE 9.2, with the latest upgrades from apt4rpm (gwdg.de).
Personally, I'm thinking "powersupply" ... has anyone run into this behaviour?
Örn
I'd been having a similar problem over a few weeks on my Mandrake box, I knew it wasn't power supply or motherboard as it happened with other ones in the box. yesterday when I was working on the box, it suddenly powered off, dead, but the power LED was on - as usual. Hit the power off button, then powered on again. Looking around the BIOS I noticed the CPU temperature was up at 44 Degs. C, went out and bought a new heatsink/fan, it's been up 34 hours now, the first time in weeks it's gone past 5 hours. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====
fredag 10 december 2004 01:13 skrev Sid Boyce:
I'd been having a similar problem over a few weeks on my Mandrake box, I knew it wasn't power supply or motherboard as it happened with other ones in the box. yesterday when I was working on the box, it suddenly powered off, dead, but the power LED was on - as usual. Hit the power off button, then powered on again. Looking around the BIOS I noticed the CPU temperature was up at 44 Degs. C, went out and bought a new heatsink/fan, it's been up 34 hours now, the first time in weeks it's gone past 5 hours. This was the first thing that I checked, the first time it happend. The temperature at that time was at 38° C, which is a bit high, but the system board was at the same temp. My system is water cooled, so I put in a new "pump", didn't change anything. The new pump, pumps 5l per minute, but the average temp has increased about 5° since I first put the system up, perhaps I should get a new CPU block.
However, I've been running this system now for over 3 hours without the water pump on :-), so I don't think it's the temperature. If only I had "sensors" working :-(
Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====
Örn
On 10 Dec 2004 at 0:13, Sid Boyce wrote:
Looking around the BIOS I noticed the CPU temperature was up at 44 Degs. C
My CPU is currently running with 42 degs C and will do so for the rest of the day, maybe even warmer. (Athlon64 3200+, Clawhammer-Core). I don't think this is too hot. AMD says 60 deg C (even 65? dunno exactly, sry) is max temp. Bye Andy
On Fri, 10 Dec 2004 00:13:39 +0000
Sid Boyce
ones in the box. yesterday when I was working on the box, it suddenly powered off, dead, but the power LED was on - as usual. Hit the power off button, then powered on again. Looking around the BIOS I noticed the CPU temperature was up at 44 Degs. C, went out and bought a new heatsink/fan, it's been up 34 hours now, the first time in weeks it's gone past 5 hours.
The temperature range for Athlon 64 processors up to the 3400+, and Athlon 64 FX processors up to the FX51 is 0 to 70C (158F), according to AMD. 40 - 50 would be well within range, surely. That's the range that my opteron has been running in for the last 6 months - Richard -- Richard Kimber http://www.psr.keele.ac.uk/
I have a little Shuttle PC with an AMD Athlon64, and it wouldn't shutdown on its own, but if I turned it off it would not come back on for at least 6 hours. I had the bios controlling the fan speed, (the Shuttle PC uses a heat pipe) set to automatic depending on CPU temp. The problem was the fan never went higher than low speed. The CPU temp was never reported being "hot". I set the fan to be high all the time and have not had a problem since. I would guess that the temperature is much higher than whats actually being reported, or that AMD Athlon chips are not really suited for the temps listed in their specs. R. On Thu, 2004-12-09 at 16:11 -0600, Örn Hansen wrote:
Hi,
I've recently experience mysterious shutdown on my AMD64 system. Just now, after the computer had been on, playing music (the only thing being done on it), it suddenly shut itself off. I have to "unplug and replug" the powersupply to have the computer start again.
Is it possible, that some "hardware" in the system is causing this, the memory in the computer are two brand new ... two kingston 512Mb modules, the hard disk is also new, a SATA one. The CPU was bough earlier this year, the system being run is SuSE 9.2, with the latest upgrades from apt4rpm (gwdg.de).
Personally, I'm thinking "powersupply" ... has anyone run into this behaviour?
Örn -- R.
Ron Lau wrote:
I have a little Shuttle PC with an AMD Athlon64, and it wouldn't shutdown on its own, but if I turned it off it would not come back on for at least 6 hours.
I had the bios controlling the fan speed, (the Shuttle PC uses a heat pipe) set to automatic depending on CPU temp. The problem was the fan never went higher than low speed. The CPU temp was never reported being "hot". I set the fan to be high all the time and have not had a problem since.
I would guess that the temperature is much higher than whats actually being reported, or that AMD Athlon chips are not really suited for the temps listed in their specs.
R.
I used to have an XP2000+ that similarly I had to remove the power plug, but only for a few seconds, eventually the CPU died, the heatsink just about fell into my hand, next time around I double checked it was securely in place. I have a feeling that the specs are not always to be relied on. Since I replaced the heatsink/fan on the Mandrake box, I've had no reoccurrence of the shutdown, I don't know what the temp was before it powered off, but the BIOS showed 44 degs when powered back on, so it may have cooled down by then. sensors return:- XP3000+ CPU Temp (AMD): +25°C (high = +80°C, hyst = +75°C) vid: +1.650 V (VRM Version 9.0) XP2800+ which had the problem, pity I didn't check sensors until after the new heatsink and fan was fitted. CPU Temp (AMD): +25°C (high = +60°C, hyst = +50°C) vid: +1.650 V (VRM Version 9.0) Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====
participants (6)
-
Brad Dameron -
h.andy＠gmx.de -
rkimber＠ntlworld.com -
Ron Lau -
Sid Boyce -
Örn Hansen