Re: suspect bug in vge(4)

From: Thomas Lotterer <thomas+freebsd_at_lotterer.net>
Date: Thu, 11 Jun 2009 17:39:03 +0200
Pyun YongHyeon wrote:
> Could you show me dmesg output(only vge(4) related one)? 
> 
# dmesg | grep vge
vge0: <VIA Networking Gigabit Ethernet> port 0xec00-0xecff mem 
0xdf7ff000-0xdf7ff0ff irq 28 at device 0.0 on pci2
vge0: MSIX count : 0
vge0: MSI count : 1
vge0: Read request size : 512 bytes.
vge0: TLP payload size : 128 bytes.
miibus0: <MII bus> on vge0
vge0: Ethernet address: 00:40:63:xx:xx:xx
vge0: [FILTER]
vge0: link state changed to UP
vge0: watchdog timeout
vge0: unable to stop Rx/Tx MAC(0x09)!
vge0: soft reset timed out
vge0: link state changed to DOWN
vge0: link state changed to UP

And this time a link has been established

# ifconfig vge0
vge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
         ether 00:40:63:xx:xx:xx
         inet [...]
         media: Ethernet autoselect (1000baseT <full-duplex,flag0,flag1>)
         status: active

Unfortunately, no traffic could be sent and tcpdump(1) does not show any 
incoming packages either, not even broadcasts.

Interesting side effect is that after that test the kernel with my 
previous "original problem" vge(4) driver rebooted when initializing the 
network card. No logs at this stage, sorry. Reboot did not help. Hard 
reset did not help. Power cycle did help. Behavior was reproducible on a 
second attempt.

-- 
http://thomas.lotterer.net
Received on Thu Jun 11 2009 - 13:38:57 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:49 UTC