From owner-freebsd-questions Thu Jan 31 12:41: 9 2002 Delivered-To: freebsd-questions@freebsd.org Received: from web20103.mail.yahoo.com (web20103.mail.yahoo.com [216.136.226.40]) by hub.freebsd.org (Postfix) with SMTP id D0F7837B402 for ; Thu, 31 Jan 2002 12:41:00 -0800 (PST) Message-ID: <20020131204100.55113.qmail@web20103.mail.yahoo.com> Received: from [198.135.242.14] by web20103.mail.yahoo.com via HTTP; Thu, 31 Jan 2002 12:41:00 PST Date: Thu, 31 Jan 2002 12:41:00 -0800 (PST) From: Chad Subject: fxp0: SCB timeout errors To: questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greetings. I am using FreeBSD 4.4-RELEASE on a Dell PowerEdge 1550 with a dual onboard Intel NIC. Every few days, and with no indication why it is happening, the system's response time suddenly gets very slow. A web page that normally loads in a fraction of a second suddenly takes 15 seconds, as an example. When running top, it shows the CPU usage at 100%, where normally it hovers between 25%-50% utilized. The syslogd process seems to be the problem, since it shows up with a high percentage of the CPU. Checking var/log/messages, I get this: bob# tail /var/log/messages Jan 23 16:55:12 bob /kernel: fxp0: SCB timeout: 0x70 0x0 0x50 0x0 Jan 23 16:55:12 bob /kernel: fxp0: SCB timeout: 0x80 0x0 0x50 0x0 Jan 23 16:55:13 bob last message repeated 5 times Jan 23 16:55:13 bob /kernel: fxp0: SCB timeout: 0x70 0x0 0x50 0x0 Jan 23 16:55:13 bob /kernel: fxp0: SCB timeout: 0x80 0x0 0x50 0x0 Jan 23 16:55:16 bob last message repeated 29 times Jan 23 16:55:16 bob /kernel: fxp0: SCB timeout: 0x70 0x0 0x50 0x0 Jan 23 16:55:17 bob /kernel: fxp0: SCB timeout: 0x80 0x0 0x50 0x0 Jan 23 16:55:19 bob last message repeated 15 times Jan 23 16:55:19 bob /kernel: fxp0: SCB timeout: 0x70 0x0 0x50 0x0 And it just goes on and on, generating a ton of messages until a reboot, after which the system comes up and runs just fine for a few more days, until suddenly this problem crops up again. Relevant parts of the "dmesg" command show: FreeBSD 4.4-RELEASE #0: Sat Dec 22 00:05:08 EST 2001 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 3, version: 0x000f0011, at 0xfec01000 fxp0: port 0xecc0-0xecff mem 0xfe100000-0xfe1fffff,0xfe2ff000-0xfe2fffff irq 2 at device 1.0 on pci0 fxp0: Ethernet address 00:06:5b:3a:03:68 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: port 0xec80-0xecbf mem 0xfe000000-0xfe0fffff,0xfe2fe000-0xfe2fefff irq 5 at device 2.0 on pci0 fxp1: Ethernet address 00:06:5b:3a:03:69 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Can anyone tell me what might be the problem, or give me a gentle nudge in the right direction to diagnose it myself? Thanks in advance for your help. Chad __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message