From owner-freebsd-stable  Mon May  6 11: 3:44 2002
Delivered-To: freebsd-stable@freebsd.org
Received: from ridge.aps.org (ridge.aps.org [149.28.1.5])
	by hub.freebsd.org (Postfix) with ESMTP id B628D37B404
	for <freebsd-stable@FreeBSD.ORG>; Mon,  6 May 2002 11:03:35 -0700 (PDT)
Received: from pcpaul.aps.org (lugnut.aps.org [149.28.3.182])
	by ridge.aps.org (8.9.3+Sun/8.9.3) with ESMTP id OAA18081;
	Mon, 6 May 2002 14:03:34 -0400 (EDT)
Received: from lugnut.aps.org (localhost [127.0.0.1])
	by pcpaul.aps.org (Postfix) with ESMTP
	id 9E22A7E; Mon,  6 May 2002 14:03:34 -0400 (EDT)
Content-Type: text/plain;
  charset="iso-8859-1"
From: Paul Dlug <paul@nerdlabs.com>
To: kendall@jedis.com
Subject: Re: fxp0: SCB timeout
Date: Mon, 6 May 2002 14:03:34 -0400
X-Mailer: KMail [version 1.4]
Cc: freebsd-stable@FreeBSD.ORG, kendall@jedis.com
References: <000a01c1f51f$5ea50970$2501a8c0@fmepro.com>
In-Reply-To: <000a01c1f51f$5ea50970$2501a8c0@fmepro.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200205061403.34537.paul@nerdlabs.com>
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

I have apm disabled in the kernel already. I have the same ServerWorks chipset 
you mentioned.



On Monday 06 May 2002 12:59 pm, Kendall Gifford wrote:
> I also have a Dell PowerEdge 1550 with 4.5-STABLE and had the same
> SCB timeout problem with the fxp driver. I never found much definitive
> info,
> but I did hear one suggestion that this was somehow related to advanced
> power management. I rebuilt a kernel without APM by removing the line:
>
> device	apm0	at nexus?...
>
> I have not had any problems with this since then, but I would only have
> the problem in periodic storms anyway. Thus there is no way for me to
> be sure if it is just coincidence that I haven't experience the problem
> since then. I would appreciate it if anyone else could/would shed some
> more light on this issue. It seems those of us with ServerWorks chipset
> motherboards and versions of Intel Pro cards w/ the fxp driver have
> this issue. Dmesg below:
>
> [...snip...]
> pcib0: <ServerWorks host to PCI bridge> on motherboard
> pci0: <PCI bus> on pcib0
> fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0xecc0-0xecff mem
> 0xfe100000-0xfe1f
> ffff,0xfe2ff000-0xfe2fffff irq 11 at device 1.0 on pci0
> [...snip...]
>
> > On Monday, May 06, 2002, Paul Dlug wrote:
> > I'm seeing these messages scroll past on the console quite rapidly:
> >
> > fxp0: device timeout
> > fxp0: DMA timeout
> > fxp0: DMA timeout
> > fxp0: SCB timeout: 0x10 0x0 0x80 0x0
> >
> > I searched the mailing list archive and came up with some
> > people having the
> > same problem, but no definitive answers. The hardware is a
> > Dell 1550 with
> > dual onboard Intel NIC's, running 4.5-STABLE (cvsup'd as of
> > two weeks ago).
> > There are four other identical servers on the same switch
> > that are not having
> > this problem, this occurs only on this one host. After are
> > reboot the box is
> > fine for an hour or so before it starts to die again.
> >
> > Any suggestions?
> >
> > Thanks,
> > Paul
>
> ____________
> Kendall Gifford
> http://kendall.jedis.com
> kendall@jedis.com
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message


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