Could my issue just be a failing Intel NIC? I do have another Intel PCI NIC to try out, but I will wait for the issue to repeat itself.
Thanks!
I searched around the net for SCB timeout and the best article I found was Rescuing Ethernet Interface after SCB timeout (
http://lists.freebsd.org/pipermail/freebsd-questions/2006-January/110364.htmlMy symptoms are much the same. Basically after about 3 day uptime (this has only happened once so far, but I thought it best to document it now) the WAN interface just seems to have shutdown. I went to the System->Interface page on monowall and I saw that it still had an IP and it even showed "Up" status. I went to the console of monowall and found all the SCB timeout errors filling the screen.
I've had a previous uptime of well over 90 days on this same hardware, although that was v1.3b15 or so. I have since upgraded to b16, b17, b18, and I am now on v1.3 when this SCB timeout issue occurred. I have not had this occur previously on any of the beta 1.3.
I have not changed the hardware on the monowall system. The onboard NIC (Shuttle PC, don't even know the motherboard, but the NIC shows up as NVIDIA nForce MCP2 Networking Adapter but its not this) is assigned to the LAN interface. The PCI NIC, Intel 82557 Pro/100 Ethernet, is the WAN NIC that is showing the SCB timeout issue.
Dec 6 00:20:57 kernel: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
Dec 6 00:20:57 kernel: fxp0: device timeout
Dec 6 00:20:53 last message repeated 68 times
Dec 6 00:20:38 kernel: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
Dec 6 00:20:38 kernel: fxp0: DMA timeout
Dec 6 00:20:38 kernel: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
Dec 6 00:20:38 kernel: fxp0: DMA timeout
Dec 6 00:20:38 kernel: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
Dec 6 00:20:38 kernel: fxp0: DMA timeout
Dec 6 00:20:38 last message repeated 2 times
Dec 6 00:20:38 kernel: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
Dec 6 00:20:38 kernel: fxp0: device timeout
Dec 6 00:20:37 last message repeated 6 times
Dec 6 00:20:24 kernel: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
Dec 6 00:20:24 kernel: fxp0: DMA timeout
Dec 6 00:20:24 kernel: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
Dec 6 00:20:24 kernel: fxp0: DMA timeout
Dec 6 00:20:24 kernel: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
Dec 6 00:20:24 kernel: fxp0: DMA timeout
Dec 6 00:20:24 last message repeated 2 times
Dec 6 00:20:24 kernel: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
Dec 6 00:20:24 kernel: fxp0: device timeout
Dec 6 00:20:20 last message repeated 6 times
Dec 6 00:20:10 kernel: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
Dec 6 00:20:04 kernel: fxp0: link state changed to DOWN
Dec 6 00:20:04 kernel: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
Dec 6 00:11:56 kernel: fxp0: device timeout
Dec 5 12:48:07 dhclient: bound to x.x.x.x (MY IP) -- renewal in 42221 seconds.
Dec 5 12:48:07 dhclient: New Broadcast Address: 255.255.255.255
Dec 5 12:48:07 dhclient: New Network Number: x.x.x.x (network at ISP)
Dec 5 12:48:07 dhclient: DHCPACK from x.x.x.x
Dec 5 12:48:07 dhclient: DHCPREQUEST on fxp0 to x.x.x.x (DHCP Server for ISP I assume) port 67
Dec 5 01:15:43 dhclient: bound to x.x.x.x (MY IP ADDRESS) -- renewal in 41544 seconds.
Dec 5 01:15:43 dhclient: New Broadcast Address: 255.255.255.255
Dec 5 01:15:43 dhclient: New Network Number: x.x.x.x (network at ISP)
Dec 5 01:15:43 dhclient: DHCPACK from x.x.x.x
Dec 5 01:15:43 dhclient: DHCPREQUEST on fxp0 to x.x.x.x port 67 (DHCP server for ISP I assume)
thought this might be useful:
Dec 6 00:38:51 kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Dec 6 00:38:51 kernel: inphy0: <i82555 10/100 media interface> on miibus1
Dec 6 00:38:51 kernel: miibus1: <MII bus> on fxp0
Dec 6 00:38:51 kernel: fxp0: <Intel 82557 Pro/100 Ethernet> port 0xd000-0xd01f mem 0xd0000000-0xd0000fff,0xd5000000-0xd50fffff irq 18 at device 6.0 on pci1
Dec 6 00:38:51 kernel: pci1: <ACPI PCI bus> on pcib1
Dec 6 00:38:51 kernel: pcib1: <ACPI PCI-PCI bridge> at device 8.0 on pci0