From owner-freebsd-stable Thu Jan 18 11:34:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (unknown [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 918CA37B402 for ; Thu, 18 Jan 2001 11:34:07 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0IJmXQ00714; Thu, 18 Jan 2001 11:48:34 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101181948.f0IJmXQ00714@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Derek Tattersall Cc: Drew Sanford , FreeBSD-stable@FreeBSD.org Subject: Re: Athlon and 4.2 Release In-reply-to: Your message of "18 Jan 2001 10:03:09 EST." <86wvbsrjgy.fsf@lorne.arm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Jan 2001 11:48:33 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I strongly suspect its an IRQ conflict. Every problem of this sort > > that I've seen with the A7V has been an IRQ conflict, including the > > problem I had with my own. Specificly I had to hard set the IRQ on my > > NIC through the PCI management section of the bios. ... > It certainly is an IRQ conflict between the 3C905B NIC and the promise > controller. I could install and reboot just fine with the NIC > removed. Er, folks, no. You can share IRQs just fine with PCI. You don't have "IRQ conflicts" just because two devices are driving the same interrupt. There are plenty of other possibilites for trouble, but having the same IRQ is not in and of itself going to do this. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message