Call for bge(4) testers

[Wanpeng Qian]

>On Thu, Sep 20, 2012 at 06:56:09AM +0900, Wanpeng Qian wrote:
>> Hi,
>> 
>> >On Mon, Sep 17, 2012 at 09:37:21PM +0900, Wanpeng Qian wrote:
>> >> Hi, here is the dmesg output.
>> >> 
>> >> bge0: <HP NC107i PCIe Gigabit Server Adapter, ASIC rev. 0x5784100> mem 
>> >> 0xfe9f0000-0xfe9fffff irq 18 at device 0.0 on pci4
>> >> bge0: CHIP ID 0x05784100; ASIC REV 0x5784; CHIP REV 0x57841; PCI-E
>> >> miibus0: <MII bus> on bge0
>> >> brgphy0: <BCM5784 10/100/1000baseT PHY> PHY 1 on miibus0
>> >> brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
>> >> 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
>> >> 
>> >
>> >It seems your controller is BCM5784 A1. The latest WIP have one
>> >change that may affect its DMA behavior. So it would be good to
>> >know how the WIP version works on your box.
>> 
>> I update my system to 9-STABLE and using your WIP files.
>> after I reboot the whole system. I cannot find bge anymore.
>> 
>> here is the pciconf -lv output.
>> 
>> none1 at pci0:4:0:0:	class=0x020000 card=0x705d103c chip=0x165b14e4 
>> rev=0x10 hdr=0x00
>>     vendor     = 'Broadcom Corporation'
>>     device     = 'NetXtreme BCM5723 Gigabit Ethernet PCIe'
>>     class      = network
>>     subclass   = ethernet
>
>Hmm, the WIP version didn't remove the chip id so bge(4) may have
>failed to attach.
>Could you check any message printed by bge(4) in dmesg output?

There is neither message related to bge in the dmesg output.
nor ifconfig -a output.

anything else I can try ?

>
>>     
>> Regards.
>> 
>> Qian
>> 
>> >
>> >> FreeBSD 9.0 RELEASE.
>> >> 
>> >> Regards.
>> >> 
>> >> Qian
>> >> 
>> >> >
>> >> >watchdog timeouts can be triggered by various issues so it's hard
>> >> >to guess the root cause of the issue.
>> >> >Would you show me the dmesg output(bge(4)/brgphy(4) output
>> >> >only)?
>> >> >