From owner-freebsd-hackers Tue Mar 16 23:18:25 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 335571510B for ; Tue, 16 Mar 1999 23:18:16 -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 AAA16526; Wed, 17 Mar 1999 00:18:34 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36EF5749.2B1A8D21@softweyr.com> Date: Wed, 17 Mar 1999 00:18:33 -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: "John W. DeBoskey" Cc: freebsd-hackers@freebsd.org, Charles Tudor Subject: Re: fxp driver causing lockup References: <199903170620.BAA54317@bb01f39.unx.sas.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John W. DeBoskey" wrote: > > Hi, > > I beleive you are correct. The following code fragment from > if_fxp.c is the lockup: > > /* > * Start the config command/DMA. > */ > fxp_scb_wait(sc); > CSR_WRITE_4(sc, FXP_CSR_SCB_GENERAL, vtophys(&cbp->cb_status)); > CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_START); > /* ...and wait for it to complete. */ > while (!(cbp->cb_status & FXP_CB_STATUS_C)); Yup, that's it. I initially tracked this down under 3.0, but moved the machine back to 2.2.7 because I needed it to get work done. I've now stuffed two 3c905Bs into it for my main and test network, and can play with the Pro 100B without losing a network connection. > according to doc at Dell's website (they have a machine with this > problem), the bios is not enabling dma on the adapter board. I beleive > the person I copied on this mail can provide the precise web page > that documents this. > > According to them, it is possible to discreetly turn on dma on > the adapter. This is were someone with the appropriate doc needs > to jump in... > > Basically, the driver needs to check that dma is enabled and > enable it if not. Any hints as to how to do that? I've got the machine, the lockups, and a (little) bit of driver knowlege. Plus a fair bit of tenacity. The Linux 2.2 driver exhibits the same problem on these machines, so I can either share the fix with them or just convince them to upgrade to FreeBSD once I get this nailed. ;^) -- "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