Re[2]: reproducible watchdog timeout in bge
- From: Wishmaster <wishmaster@xxxxxxxxx>
- Date: Tue, 23 Jan 2007 02:34:58 +0300
Hello Jeff,
Monday, January 22, 2007, 4:39:28 PM, you wrote:
JR> MQ wrote:
2007/1/22, Wishmaster <wishmaster@xxxxxxxxx>:
Hello LI,
Sunday, January 21, 2007, 12:52:55 AM, you wrote:
LX> Wishmaster wrote:
Hi,
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/92090
LX> Have you tried this one?
LX> http://people.freebsd.org/~delphij/misc/patch-bge-releng62
LX> Cheers,
Yes, i tried, but have no effect.
after reboot interface works, but if i try to ping with packet for
example 1500 bytes and interval 0.01s it looks like
answer
answer
answer
....
..... over 50 or less icmp answers then
ping: sendto: No buffer space available
ping: sendto: No buffer space available
ping: sendto: No buffer space available
ping: sendto: No buffer space available
ping: sendto: No buffer space available
ping: sendto: No buffer space available
ping: sendto: No buffer space available
in dmesg:
bge0: watchdog timeout -- resetting
bge0: link state changed to DOWN
bge0: link state changed to UP
--
Best regards,
Wishmaster mailto:wishmaster@xxxxxxxxx
What about other NIC chips from Broadcom? And how about the packets other
than icmp under the same load?
_______________________________________________
JR> I have been unable to produce time outs with my current setup in
JR> 6.2-Release.
JR> bge0@pci3:0:0: class=0x020000 card=0x81491043 chip=0x165914e4 rev=0x11
JR> hdr=0x00
JR> vendor = 'Broadcom Corporation'
JR> device = 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express'
JR> class = network
JR> subclass = ethernet
JR> Reading the PR, I attempted triggering this through CVSing and through
JR> the above mentioned ping tests.
JR> So far nothing.
JR> The only issue I have seen using these NICs in 6.2R is if I nail up the
JR> NIC at 100baseTX full-duplex I sometimes loose connectivity. Nothing
JR> in the logs indicate watchdog timeouts or any other issue. I simply
JR> brought the NIC back down to auto-neg and all seems fine. I am
JR> assuming this is a incompatibility between the BGE and my switch, RS8000.
JR> I have a Asus P5MT-S with dual BGE NIC's
JR> Cheers,
JR> Jeff
JR> _______________________________________________
JR> freebsd-net@xxxxxxxxxxx mailing list
JR> http://lists.freebsd.org/mailman/listinfo/freebsd-net
JR> To unsubscribe, send any mail to
JR> "freebsd-net-unsubscribe@xxxxxxxxxxx"
There are different types of broadcom chips on my hardware:
bge0: <Broadcom BCM5721 Gigabit Ethernet, ASIC rev. 0x4101>
mem 0xddef0000-0xddefffff irq 16 at device 0.0 on pci5
miibus0: <MII bus> on bge0
brgphy0: <BCM5750 10/100/1000baseTX PHY> on miibus0
brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
bge0: Ethernet address: 00:15:f2:cd:21:9a
I don't have any other type of broadcom NIC to test but all other
NICs, for example Intel works correctly.
p.s. MB: ASUSTeK P5M2 /2GBL
--
Best regards,
Wishmaster mailto:wishmaster-velnet@xxxxxxxxx
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- References:
- reproducible watchdog timeout in bge
- From: Wishmaster
- Re: reproducible watchdog timeout in bge
- From: LI Xin
- Re[2]: reproducible watchdog timeout in bge
- From: Wishmaster
- Re: Re[2]: reproducible watchdog timeout in bge
- From: MQ
- Re: reproducible watchdog timeout in bge
- From: Jeff Royle
- reproducible watchdog timeout in bge
- Prev by Date: Re[2]: reproducible watchdog timeout in bge
- Next by Date: Soldes -60% - Volnay 1er Cru 1992 - LIVRAISON 24H GRATUITE
- Previous by thread: Re: reproducible watchdog timeout in bge
- Next by thread: Re[2]: reproducible watchdog timeout in bge
- Index(es):
Relevant Pages
|