John Marshall wrote:
I don't see this at all on 6.1 unless I use SCHED_ULE. (Although, I
haven't compiled all those additional drivers into a 6.1 system, so that
might not be a fair comparison.)
Wrong! I saw this last night for the first time on a production hp
ProLiant ML110 (6.1-RELEASE-p10)
On 2 Nov 2006, at 23:50, John Marshall wrote:
bge0: watchdog timeout -- resetting
bge0: link state changed to DOWN
bge0: link state changed to UP
I'm seeing similar behaviour on a HP DL360g4 running 6.1-RELEASE and
a GENERIC kernel. It had similar problems with 5.4. I have 2 other
similar
"John Marshall" <[EMAIL PROTECTED]> writes:
> rwsrv05> dmesg | grep bge
> bge0: mem 0xe820-0xe820
> irq 17 at device 4.0 on pci4
> miibus1: on bge0
> bge0: Ethernet address: 00:0b:cd:e7:70:19
> bge0: link state changed to UP
> bge0: watchdog timeout -- resetting
I have a Tyan S2850 wit
> Is it causing stuck connections or other messy problems? Also, is it
> any worse than 6.1?
I am also seeing the same thing - hard to tell if it is better or worse
under 6.2 than 6.1 as I dont have 6.2 out on any production webservers
so the only machine running it is a lot more lightly loaded (
> Is it causing stuck connections or other messy problems? Also, is it
> any worse than 6.1?
No. It's not causing lock-ups or anything else sinister. The network
activity resumes happily a couple of seconds after the reset.
Nov 3 00:33:07 rwsrv05 kernel: bge0: watchdog timeout -- resetting
Nov
Is it causing stuck connections or other messy problems? Also, is it
any worse than 6.1?
Scott
John Marshall wrote:
rwsrv05> dmesg | grep bge
bge0: mem 0xe820-0xe820
irq 17 at device 4.0 on pci4
miibus1: on bge0
bge0: Ethernet address: 00:0b:cd:e7:70:19
bge0: link state changed to
rwsrv05> dmesg | grep bge
bge0: mem 0xe820-0xe820
irq 17 at device 4.0 on pci4
miibus1: on bge0
bge0: Ethernet address: 00:0b:cd:e7:70:19
bge0: link state changed to UP
bge0: watchdog timeout -- resetting
bge0: link state changed to DOWN
bge0: link state changed to UP
bge0: watchdog timeo
