From owner-freebsd-stable Fri Jun 7 16:46: 6 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by hub.freebsd.org (Postfix) with ESMTP id EA63437B404 for ; Fri, 7 Jun 2002 16:45:54 -0700 (PDT) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.12.3/8.12.3) with ESMTP id g57Nigcn041671; Fri, 7 Jun 2002 16:44:43 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (localhost [127.0.0.1]) by realtime.exit.com (8.12.3/8.12.2) with ESMTP id g57Nibg0033700; Fri, 7 Jun 2002 16:44:38 -0700 (PDT) (envelope-from frank@realtime.exit.com) Received: (from frank@localhost) by realtime.exit.com (8.12.3/8.12.3/Submit) id g57NiTwD033645; Fri, 7 Jun 2002 16:44:29 -0700 (PDT) From: Frank Mayhar Message-Id: <200206072344.g57NiTwD033645@realtime.exit.com> Subject: Re: Numerous hard hangs on TWO different ASUS P4T-E w/P4 1.6G In-Reply-To: <20020607143308.A1030@HAL9000.wox.org> To: David Schultz Date: Fri, 7 Jun 2002 16:44:29 -0700 (PDT) Cc: Alain Fauconnet , freebsd-stable@FreeBSD.ORG Reply-To: frank@exit.com X-Copyright0: Copyright 2002 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL98b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Schultz wrote: > Don't rule out hardware problems until you've tried a different model > motherboard. Some old ASUS boards have a problem where, under intense > memory load, the voltage drops below the signalling threshhold and the > box locks up as you've described. (ASUS won't readily admit to this > or any of the other bugs in their boards, but ask them why they did > the third revision to the P2B-F.) That's just an example, but the > point is that both of your P4T-Es could have the same bug. Well, considering that many different people are seeing this on different hardware (I have in fact seen it on two different motherboards, a Tyan Thunder 2500 with dual PIIIs and my current 2466N-4M with dual AMD MPs, different SCSI controllers, too), I think it must be some new bug in FreeBSD. Perhaps in the interrupt handling? I don't really know where to begin to look; if someone could suggest some places, that would be very useful. So far, none of the various suggestions have made any difference at all. I have yet to turn off my IDE and parallel port to get IRQs back, I'll do that this weekend. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message