Solid hang with bge interface

[Lawrence Farr]

> -----Original Message-----
> From: Remy Nonnenmacher [mailto:remy.nonnenmacher at activnetworks.com]
> Sent: 21 August 2007 10:45
> To: Lawrence Farr
> Cc: freebsd-current at freebsd.org
> Subject: Re: Solid hang with bge interface
> 
> Lawrence Farr wrote:
> > I have a Supermicro H8DAR-T based server, that was happily
> > running 6-stable from last year sometime. I swapped it out and
> > have been trying to get -CURRENT installed on it but it hangs
> > solid as soon as you configure the bge0 interface. The bge1
> > interface will work occasionally tho. To try and rule out a
> > hardware fault I booted an AMD64-6.0RC1 cd that I had, which
> > had no problems at all with the interface:
> >
> > http://www.epcdirect.com/bootlog/6boot.txt
> >
> > But the current snapshot from June, and from todays source
> > hangs solid as soon as you try to set up the bge0 interface.
> >
> > http://www.epcdirect.com/bootlog/currentboot.txt
> >
> > As you can see, it hangs solid at "Setting hostname".
> >
> > I've also removed the 3ware card "just in case" but it made
> > no difference. Latest BIOS too. I found some references to
> > a similar problem with bge recently too:
> >
> > http://lists.freebsd.org/pipermail/freebsd-current/2007-
> August/075998.html
> >
> >
> > Anyone else seeing this?
> >
> 
> Same here with a Supermicro H8SSL-I2 (Serverworks HT1000 based).
> 
> bge0 locks the system hard when going up, bge1 OK (but goes down a few
> hours after start). Also, an ifconfig indicates:
> 
> bge0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
>          options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
>          ether 00:30:48:5e:6e:56
>          media: Ethernet autoselect (none <hw-loopback>)
>                                      ^^^^^^^^^^^^^^^^^^
>          status: no carrier
> bge1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
> 1500
>          options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
>          ether 00:30:48:5e:6e:57
>          inet 192.168.1.49 netmask 0xffffff00 broadcast 192.168.1.255
>          media: Ethernet autoselect (1000baseTX <full-duplex>)
>          status: active
> 
> An the dmesg shows: (see "^^^^..")
> 
> 	.
> 	.
> bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev.
> 0x2100> mem 0xff4f0000-0xff4fffff irq 24 at device 3.0 on pci2
> miibus0: <MII bus> on bge0
> brgphy0: <BCM5704 10/100/1000baseTX PHY> PHY 1 on miibus0
> brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> 1000baseT-FDX, auto
> bge0: Ethernet address: 00:30:48:5e:6e:56
> bge0: [ITHREAD]
> pci2:3:1: bad VPD cksum, remain 14
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev.
> 0x2100>
> mem 0xff4e0000-0xff4effff irq 25 at device 3.1 on pci2
> miibus1: <MII bus> on bge1
> brgphy1: <BCM5704 10/100/1000baseTX PHY> PHY 1 on miibus1
> brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> 1000baseT-FDX, auto
> bge1: Ethernet address: 00:30:48:5e:6e:57
> bge1: [ITHREAD]
> 	.
> 	.
> 
> (I also have strange problems with the SATA controller and recent
> kernels (that works fine on other machines) that seems to read random
> sectors (at least not those requested) causing core-dumps, compiler
> internal errors, trashed sources and false positives about corrupted
> filesystems.I don't know what is going on on this platform but it
> smells^Gdoesn't looks very sane.)
> 
> RN.
> IeM
> 
> 

This is still hanging with yesterdays current in i386 and AMD64, is it worth
opening a PR?