Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Sep 2002 00:42:33 -0400
From:      Mike Tancsa <mike@sentex.net>
To:        Alain Fauconnet <alain@cscoms.net>, Frank Mayhar <frank@exit.com>, dschultz@uclink.Berkeley.EDU
Cc:        freebsd-stable@FreeBSD.ORG
Subject:   Re: Numerous hard hangs on TWO different ASUS P4T-E w/P4 1.6G
Message-ID:  <5.1.1.6.0.20020918004028.051eef50@marble.sentex.ca>
In-Reply-To: <20020918113436.B2542@cscoms.net>
References:  <20020610104015.D9887@cscoms.net> <20020607143308.A1030@HAL9000.wox.org> <200206072344.g57NiTwD033645@realtime.exit.com> <20020610104015.D9887@cscoms.net>

next in thread | previous in thread | raw e-mail | index | archive | help

There were some further commits to -STABLE this week to the ATA 
code.  Might be worth a try.

         ---Mike

At 11:34 AM 18/09/2002 +0700, Alain Fauconnet wrote:
>Hello,
>
>Well, these boxes have all been  upgraded  to  4.6.2  and  they  still
>freeze from time to time unless I disable DMA. If I put:
>
>hw.ata.ata_dma="0"
>
>in /boot/loader.conf they become totally stable. I've found a 3rd  box
>in the company, same motherboard, exhibiting the same problem.
>
>Has anyone found anything new about this ?
>
>Greets,
>_Alain_
>
>On Mon, Jun 10, 2002 at 10:40:15AM +0700, Alain Fauconnet wrote:
> > 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_
> >
> >
>
> > 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


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?5.1.1.6.0.20020918004028.051eef50>