From owner-freebsd-stable  Sat May 18 17: 2:26 2002
Delivered-To: freebsd-stable@freebsd.org
Received: from alogis.com (firewall.solit-ag.de [212.184.102.1])
	by hub.freebsd.org (Postfix) with SMTP id 79A2F37B404
	for <freebsd-stable@FreeBSD.ORG>; Sat, 18 May 2002 16:49:54 -0700 (PDT)
Subject: 4.6-RC1 fxp0: device timeout
Message-Id: <20020518234954.79A2F37B404@hub.freebsd.org>
Date: Sat, 18 May 2002 16:49:54 -0700 (PDT)
From: Holger.Kipp@alogis.com
To: undisclosed-recipients:;
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG

Hi,
I type this directly with no mailer-agent in between, so sorry for all the
errors...

I own a Toshiba MAGNIA 3000 with the following components:
- SCSI: Symbios 53C875
- NIC:  Intel 82558    (fxp0)

With SMP I easily get fxp0: device timeout errors. The system then allows
only operations that don't require disk- or network access. To provoke
this error, a simple ping -f is sufficient. nic and sym are on the server
board.

Looks like this error is identical to kern/32478. Any chance of this being
solved before 4.6-RELEASE?

Same error is in 4.5-RELEASE, only that network is less stable, but the
system managed to log "fxp0: device timeout" otoh.

Everything works just fine if I don't use SMP. The only hint I found so 
far is to disable device ncr, but I already have that.

Any help appreciated.

Regards,
Holger

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