From owner-freebsd-hackers  Wed Mar 17 14:22:26 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from lamb.sas.com (lamb.sas.com [192.35.83.8])
	by hub.freebsd.org (Postfix) with ESMTP id 3EBAF152FE
	for <freebsd-hackers@freebsd.org>; Wed, 17 Mar 1999 14:22:23 -0800 (PST)
	(envelope-from sascht@unx.sas.com)
Received: from mozart (mozart.unx.sas.com [192.58.184.8])
	by lamb.sas.com (8.9.1/8.9.1) with SMTP id RAA00582;
	Wed, 17 Mar 1999 17:21:59 -0500 (EST)
Received: from loki.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90)
	id AA03266; Wed, 17 Mar 1999 17:21:58 -0500
From: Charles Tudor <sascht@unx.sas.com>
Received: by loki.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93)
	id AA00704; Wed, 17 Mar 1999 17:21:57 -0500
Message-Id: <199903172221.AA00704@loki.unx.sas.com>
Subject: Re: fxp driver causing lockup
To: wes@softweyr.com (Wes Peters)
Date: Wed, 17 Mar 1999 17:21:57 -0500 (EST)
Cc: jwd@unx.sas.com, freebsd-hackers@freebsd.org, sascht@unx.sas.com
In-Reply-To: <36EF5749.2B1A8D21@softweyr.com> from "Wes Peters" at Mar 17, 99 00:18:33 am
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
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
> 

I am trying to contact Intel to see if I can get the information needed
to fix the problem.  I will let you know if I receive the information.

                                                           Charles


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message