From owner-freebsd-stable Sat Jun 22 3:27:31 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.tpgi.com.au (mail.tpgi.com.au [203.12.160.57]) by hub.freebsd.org (Postfix) with ESMTP id 5DCDA37B40E for ; Sat, 22 Jun 2002 03:27:16 -0700 (PDT) Received: from tpgi.com.au (muras-remote145.ocs.mq.edu.au [137.111.7.159]) (authenticated (0 bits)) by mail1.tpgi.com.au (8.11.6/8.11.6) with ESMTP id g5MARCP17704 for ; Sat, 22 Jun 2002 20:27:13 +1000 Message-ID: <3D1450E2.9CEFE8E1@tpgi.com.au> Date: Sat, 22 Jun 2002 20:26:42 +1000 From: eirvine X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: Re: Status of fxp / smp problem? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Hi, Another "me too". I've noticed that gcc often fails with a signal 11 on my athlon smp system when I'm about half way through making world. It fails consistently when I make world like so: bash# nohup make world 2>&1 & But not when I make world like this: bash# make world There have been a few times when the whole system wedged as well. I'm using an ata disk and fxp network card, 4.6 release ... Eddie. Pete French wrote: > > > You have two drivers who have to react to the same IRQ, so maybe its some > > sort of race condition... But thats more for developers, who know their > > IRQs by heart . > > :-) is there any guide to how IRQ's are handled ? I had a thought - as > I have a machine I can reproduce this on, plus I know exactly what IRQ > it is and how many things should be run then maybe I could code in some very > specific debugging code for my kernel and generate a panic the first time sym > isnt checked when IRQ 15 is fired. Could do that by counting number of > checked in the interrupt loop possibly ? > > > Hmm, looks like Gerard didn't have the time to polish his code yet > > and commit it. I'd suggest we give him some more time before we complain, > > as he also has a living ;-) > > Sorry, wasnt intended as a complaint - more that I didnt know if the > workaround was actually intended to be committed or not, as the better > solution would be to find and the actual bug, and not put a workaround > into the code. > > -pcf. > > 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