From owner-freebsd-hackers Sat Jan 5 1: 2:50 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.27in.tv (roc-66-24-112-7.rochester.rr.com [66.24.112.7]) by hub.freebsd.org (Postfix) with ESMTP id 1E59C37B41B; Sat, 5 Jan 2002 01:02:32 -0800 (PST) Received: (from root@localhost) by mail.27in.tv (8.11.6/8.11.6) id g0592VP29126; Sat, 5 Jan 2002 04:02:31 -0500 (EST) (envelope-from cjm2@earthling.net) Received: from maxpower (trilluser@maxpower.lan.27in.tv [10.0.0.250]) by mail.27in.tv (8.11.6/8.11.6av) with SMTP id g0592Bj29112; Sat, 5 Jan 2002 04:02:29 -0500 (EST) (envelope-from cjm2@earthling.net) From: "C J Michaels" To: "Greg Lehey" Cc: "FreeBSD Questions" , "FreeBSD Hackers" Subject: RE: Does FreeBSD have a problem with some AMD processors? Date: Sat, 5 Jan 2002 04:02:27 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: <20011228181009.F95692@monorchid.lemis.com> X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greg, One question... are you using the latest mobo BIOS? My friend purchased that board and threw a 1.2GHz TBird in it. It was quite unstable until he upgraded the BIOS. When I purchased my board, it was the 1st thing I did and I haven't have any trouble with it yet. I've got a 1.1GHz and 3 128MB PC133 (mixed brands on top of it all) DIMMs in there. Lots-o-ATA devices, and I'm currently running 4.4-STABLE. The box is solid as a rock, have yet to cause it to panic/crash/etc... --Chris -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Greg Lehey Sent: Friday, December 28, 2001 2:40 AM To: FreeBSD Questions; FreeBSD Hackers Subject: Does FreeBSD have a problem with some AMD processors? I've been using AMD processors almost exclusively in my main work machines for over 4 years, and I've been very happy with them. I'm currently running a K6/233, a K6/333, an Athlon 750, a Duron 850 and an Athlon XP 1700. Last August, though, I bought a machine which gave me a lot of trouble, the Duron 850 mentioned above. I found that it would freeze for no apparent reason. I established that it wasn't the memory by taking the memory of another machine and running it like that; it made no difference. I ended up also changing the motherboard and the processor, but the hangs continued. I could expect a hang within 8 hours when doing 'make release' Just for the fun of it, I tried running Linux on it. I've been running a kernel build and 'make clean' on it now for 36 hours, and it's still running fine. Yesterday some Linux friends of mine came around and looked at it and told me that the Linux kernel I was running on the machine (2.4.16) had had a number of AMD-specific fixes put in. He didn't go into more detail, unfortunately, but I'll ask him again when I have time: it could be something relating to chipset bugs we have seen and fixed. It would help to know, though, if other people are experiencing similar problems. Please let me know if you're having problems with AMD processors which seem to be specific to FreeBSD, especially if they're hangs (i.e. the machine stops reacting, but the display still shows the last state, it doesn't reboot or panic). Information that could be interesting is (here my values): Processor: AMD Duron 850 Motherboard: ECS K7VZA Memory: 1 128 MB SIMM, 100 MHz. Greg -- For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message