Date: Mon, 10 Jun 2002 10:40:15 +0700 From: Alain Fauconnet <alain@cscoms.net> To: Frank Mayhar <frank@exit.com> Cc: David Schultz <dschultz@uclink.Berkeley.EDU>, freebsd-stable@FreeBSD.ORG Subject: Re: Numerous hard hangs on TWO different ASUS P4T-E w/P4 1.6G Message-ID: <20020610104015.D9887@cscoms.net> In-Reply-To: <200206072344.g57NiTwD033645@realtime.exit.com>; from frank@exit.com on Fri, Jun 07, 2002 at 04:44:29PM -0700 References: <20020607143308.A1030@HAL9000.wox.org> <200206072344.g57NiTwD033645@realtime.exit.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks to all who replied. I will consider doing a CVS upgrade (first I need to learn how to do it). I dislike the idea of a downgrade to 4.4 or whatever older than 4.5. For what it's worth, the box has *not* hung again since I have switched off DMA (forced PIO using sysctl). It's clearly not an option for long-term production mode though, and it has already happened that it had been stable for weeks, so that doesn't really tell much. Since the box freezes up solid and I can't enter DDB, I really wonder what I could do to help tracking down the problem. Suggestions are welcome. Greets, _Alain_ -- Alain FAUCONNET Sr. System Administrator CS Communications Co. Ltd. - Thailand On Fri, Jun 07, 2002 at 04:44:29PM -0700, Frank Mayhar wrote: > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020610104015.D9887>