From owner-freebsd-hardware Tue Jan 15 16: 8:46 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from prohosters.com (calcium.4ph.com [66.197.0.121]) by hub.freebsd.org (Postfix) with SMTP id 9EDC137B41A for ; Tue, 15 Jan 2002 16:08:37 -0800 (PST) Received: (qmail 41666 invoked from network); 15 Jan 2002 19:08:31 -0500 Received: from unknown (HELO laptop) (128.121.6.5) by 66.197.0.9 with SMTP; 15 Jan 2002 19:08:31 -0500 Message-ID: <04fc01c19e22$2974c640$6401a8c0@laptop> From: "Theodore D. Hickman Jr." To: Subject: Intel Ethernet Express Pro problem Date: Tue, 15 Jan 2002 19:10:10 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_04F9_01C19DF8.40834700" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_04F9_01C19DF8.40834700 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi,=20 My name is Ted Hickman and I run a company called ProHosters. I use = FreeBSD on all my machines. Just recently when i cvsuped to 4.4-STABLE = and now 4.5-RC fxp0 drivers have started at different intervals producing this error = message: fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: device timeout The box will issue these errors for about 20 seconds and then go back to = normal. The box for those 20 seconds is down. I greatly appreciate all = the work you do on the FreeBSD hardware side and would like to know as soon as possible = whether I should downgrade to 4.4-REL or there is some other answer. = This is happening on multiple machines on my network. Thank you for your attention to my = letter and please respond at your convience. Theodore D. Hickman Jr. President/CEO Pro Hosters L.L.C. ------=_NextPart_000_04F9_01C19DF8.40834700 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
    My name is Ted = Hickman and I run=20 a company called ProHosters.  I use FreeBSD on all my = machines.  Just=20 recently when i cvsuped to 4.4-STABLE and now 4.5-RC
fxp0 drivers have started at different = intervals=20 producing this error message:
 
fxp0: SCB timeout: 0x80 0x0 0x50 = 0x400
fxp0: SCB=20 timeout: 0x80 0x0 0x50 0x400
fxp0: SCB timeout: 0x80 0x0 0x50 = 0x400
fxp0:=20 SCB timeout: 0x80 0x0 0x50 0x400
fxp0: SCB timeout: 0x80 0x0 0x50=20 0x400
fxp0: SCB timeout: 0x80 0x0 0x50 0x400
fxp0: SCB timeout: = 0x80 0x0=20 0x50 0x400
fxp0: SCB timeout: 0x80 0x0 0x50 0x400
fxp0: SCB = timeout: 0x80=20 0x0 0x50 0x400
fxp0: SCB timeout: 0x80 0x0 0x50 0x400
fxp0: SCB = timeout:=20 0x80 0x0 0x50 0x400
fxp0: SCB timeout: 0x80 0x0 0x50 0x400
fxp0: = device=20 timeout
The box will issue these errors for = about 20=20 seconds and then go back to normal.  The box for those 20 seconds = is=20 down.  I greatly appreciate all the work you do
on the FreeBSD hardware side and would = like to know=20 as soon as possible whether I should downgrade to 4.4-REL or there is = some other=20 answer.  This is happening
on multiple machines on my = network.  Thank you=20 for your attention to my letter and please respond at your=20 convience.
 
 
Theodore D. Hickman Jr.
President/CEO
Pro Hosters = L.L.C.
 
------=_NextPart_000_04F9_01C19DF8.40834700-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message