From owner-freebsd-questions Thu Jan 2 9:12:21 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04A8437B502 for ; Thu, 2 Jan 2003 09:12:20 -0800 (PST) Received: from portal.aphroland.org (portal.aphroland.org [216.39.174.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C62443EA9 for ; Thu, 2 Jan 2003 09:12:19 -0800 (PST) (envelope-from freebsd@aphroland.org) Received: by portal.aphroland.org (Postfix, from userid 1010) id 9488227801A; Thu, 2 Jan 2003 09:12:08 -0800 (PST) Received: from portal.aphroland.org (debian [127.0.0.1]) by portal.aphroland.org (Postfix) with SMTP id E0E4127800B for ; Thu, 2 Jan 2003 09:12:05 -0800 (PST) Received: from redhat.aphroland.org ([10.10.10.7]) (SquirrelMail authenticated user aphro) by webmail.linuxpowered.net with HTTP; Thu, 2 Jan 2003 09:12:05 -0800 (PST) Message-ID: <49355.10.10.10.7.1041527525.squirrel@webmail.linuxpowered.net> Date: Thu, 2 Jan 2003 09:12:05 -0800 (PST) Subject: Re: Followup to 'fallback to PIO mode' on dual processor AMD systems From: "nate" To: X-XheaderVersion: 1.1 X-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5 In-Reply-To: <1041526384.3e146e708b8e4@www.nexusmail.uwaterloo.ca> References: <1041368236.3e1204ac45da5@www.nexusmail.uwaterloo.ca> <025701c2b112$ddfbf580$1200a8c0@gsicomp.on.ca> <5.2.0.9.0.20030101100848.024838f0@192.168.0.12> <1041526384.3e146e708b8e4@www.nexusmail.uwaterloo.ca> X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.9) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=-0.7 required=5.0 tests=IN_REP_TO,MSG_ID_ADDED_BY_MTA_3,QUOTED_EMAIL_TEXT, REFERENCES,SPAM_PHRASE_01_02 version=2.42 X-Spam-Level: X-Sanitizer: This message has been sanitized! X-Sanitizer-URL: http://mailtools.anomy.net/ X-Sanitizer-Rev: $Id: Sanitizer.pm,v 1.54 2002/02/15 16:59:07 bre Exp $ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bruce Campbell said: > > - try UDMA100 with the drives directly attached (ie. no removable tray) - > maybe try a non onboard IDE controller yes I would reccomend a PCI ide controller, such as the Promise ATA/100, or Promise ATA/66. Also be sure your IDE cables are 18" and not 24" or 32" some people like to go crazy with overly long IDE cables. Sometimes for me longer then 18" and I get CRC errors(but nothing fatal). > - shuffle the disks to see if the problems follow the disks or not > > At present, I don't suspect bad media because the error message is "WRITE > command timeout tag=0 serv=0" which doesn't suggest a specific > sector/track etc, and running with UDMA33 instead of UDMA100 makes the > problem appear to vanish. I read your burn in procedures, a couple additions to throw in I'd reccomend: CPUBurn: http://users.ev1.net/~redelm/ I've only tried it on linux but the page lists *BSD too. This package also includes a memory tester, I usually run 1 CPUburn process per CPU and as many memory testers as I have RAM. If you try to load too many the newest process will segfault(since it can't allocate memory), harmless. Run this for at least 24 hours. memtest86: http://www.memtest86.com/ when you boot it, go to the options screen and turn on all tests, and run it through once or twice, with your system I'd expect 1 pass of all tests to be done in about 20 hours. most of my servers that run IDE have DMA/33 controllers, the few that have faster ones all use Promise ATA/100 cards or 3ware 6800 series raid cards. I haven't trusted recent AMD/VIA/Intel IDE chips for a while. nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message