Re: Any way to solve watchdog timeout on network-IF?

2007-01-12 Thread KAWAGUTI Ginga
Thank you for patch information.

I'm going to test with this patch for one or two weeks.

In Wed, Jan 10, 2007 at 10:51:27PM +0800,
LI Xin [EMAIL PROTECTED] wrote:
  I'm using FreeBSD/i386 6-stable on HP DL360G5 server,
  and getting Watchdog timeout  link state changed to DOWN/UP
  messages shown below.
.snip.
 Try this patch, it solved some problems we have observed in China community.
 
 For -CURRENT:
 http://people.freebsd.org/~delphij/for_review/patch-bce-watchdog-rewrite-HEAD.20070109
 
 For -STABLE:
 http://people.freebsd.org/~delphij/misc/patch-bce-watchdog-rewrite
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Any way to solve watchdog timeout on network-IF?

2007-01-10 Thread KAWAGUTI Ginga
Hi.

I'm using FreeBSD/i386 6-stable on HP DL360G5 server,
and getting Watchdog timeout  link state changed to DOWN/UP
messages shown below.

bce0: /usr/src/sys/dev/bce/if_bce.c(5000): Watchdog timeout occurred, resetting!
bce0: link state changed to DOWN
bce0: link state changed to UP

[System I'm using:]

  * CPU Xeon 51xx, 
  * Intel 5000X chipset
  * NIC:  bce (1.2.2.6 2006/10/24)
 bce0: Broadcom NetXtreme II BCM5708 1000Base-T (B1), v0.9.6 
   mem 0xf800-0xf9ff irq 16 at device 0.0 on pci3
 bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz
 miibus0: MII bus on bce0
 brgphy0: BCM5708C 10/100/1000baseTX PHY on miibus0
 brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 
1000baseTX-FDX, auto
 bce0: Ethernet address: 00:18:71:73:c5:5a

[Tests]
Give UDP generating load (ports/net/rude was used).

  Test configuration:
  [FreeBSD]-(bce)--- 100BaseTX-switch ---(em)[FreeBSD]
   packet genarator   --packet receiver
   70Mbps UDP, 1400Byte packet * 6000pps.

Then, the above Watchdog timeout message occurs _SOMETIMES_.
Maybe once a week, sometimes 10times/day.
I've tested with 3 hardware(all HP DL3x0 server with BCM5708 chip),
and all of them seems to suffer with this.

I've suspected new bce-NIC, and tried with bge cards
(also with FreeBSD 6-stable).
However, similar message also happens with bge(other network IFs also).
Next, I've tried with other cable, other ether-switch, but 
they still seems to happen _sometimes_.


Are these Watchdog timeout events common and happening everywhere else?
Or am I doing something wrong?


Searching the -stable archive, there seems some other people
suffering with this:

2006.11.29 [Re: Dell PE 1950 bce NICs revisited]
http://lists.freebsd.org/pipermail/freebsd-stable/2006-November/031116.html
2006.12.14 [em watchdog timeout]
http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031416.html


Thank you.
-- 
KAWAGUTI Ginga
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Any way to solve watchdog timeout on network-IF?

2007-01-10 Thread LI Xin
KAWAGUTI Ginga wrote:
 Hi.
 
 I'm using FreeBSD/i386 6-stable on HP DL360G5 server,
 and getting Watchdog timeout  link state changed to DOWN/UP
 messages shown below.
 
 bce0: /usr/src/sys/dev/bce/if_bce.c(5000): Watchdog timeout occurred, 
 resetting!
 bce0: link state changed to DOWN
 bce0: link state changed to UP
 
 [System I'm using:]
 
   * CPU Xeon 51xx, 
   * Intel 5000X chipset
   * NIC:  bce (1.2.2.6 2006/10/24)
  bce0: Broadcom NetXtreme II BCM5708 1000Base-T (B1), v0.9.6 
mem 0xf800-0xf9ff irq 16 at device 0.0 on pci3
  bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz

Try this patch, it solved some problems we have observed in China community.

For -CURRENT:
http://people.freebsd.org/~delphij/for_review/patch-bce-watchdog-rewrite-HEAD.20070109

For -STABLE:
http://people.freebsd.org/~delphij/misc/patch-bce-watchdog-rewrite

Note that the -STABLE version is an old, but tested one.  The -CURRENT
version is optimized, but I have not stress tested yet.  Both should
apply to the different branch cleanly, though.

I would appreciate if you would test the -HEAD patch, even with RELENG_6
and report if it solves your problem.  But if the server is important to
you then just use the latter.

Cheers,
-- 
Xin LI [EMAIL PROTECTED]  http://www.delphij.net/
FreeBSD - The Power to Serve!



signature.asc
Description: OpenPGP digital signature