From owner-freebsd-hackers Tue Mar 16 6:39:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 2FB4C1514E for ; Tue, 16 Mar 1999 06:39:48 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id HAA14741; Tue, 16 Mar 1999 07:39:43 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36EE6D2F.E6D9227F@softweyr.com> Date: Tue, 16 Mar 1999 07:39:43 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Andy Doran Cc: hackers@FreeBSD.ORG Subject: Re: fxp driver causing lockup References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andy Doran wrote: > > Hi all, > I've got weird problem with an Intel Etherexpress Pro 100. The cards work > fine, in fact great, with most of my FreeBSD boxes, all of which run > the 3.x branch updated weekly over cvsup. > > The trouble is, when I do an 'ifconfig fxp0 $some_address' on one > particular machine (a Tulip P-II, real junk) the machine locks up. The > keyboard still works (i.e. can toggle numlock light), and trying to switch > to another VT causes the machine to generate a never ending beep. I guess > it's getting stuck at spl???() somewhere. > > Setting the media type works, and the card works fine on other > machines. I've tried changing the slot, and using a generic 3.x kernel > too, but no luck. A 2.2.6 kernel works fine, no lockups. This card shares > an IRQ with a 3c905 and a S3 ViRGE/GX2. > > Unfortunately I can't hack at this because it's a production box, and has > to be up 24/7 almost always. Any ideas? I've seen the same problem on a Toshiba Equuium with on-board Pro 100+. The failure happens when the first DMA in the attach routine never completes. I'll be looking into it this week; I finally have some time to debug this problem and two other network cards for when it the machine has to work. I've saved a couple of recent messages about BIOS not initializing PCI cards; I'm wondering if that might be the cause of the problem. This machine worked fine with 2.2.x, so I'll be looking at what changed between 2.2.7 and 3.0/3.1. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message