if_bge driver problem. - Upgrade to RELEASE :)

Sun Jan 29 06:44:52 PST 2006

On Sat, Jan 28, 2006 at 11:08:43AM +0300, Oleg Bulyzhin wrote:
> On Fri, Jan 27, 2006 at 06:29:04PM +0200, husnu demir wrote:
> > > Also it is important to know whether doing 'ifconfig bge0 -rxcsum -txcsum'
> > > fixes operation on 6.0-STABLE.
> > 
> > No, It does not fixed. I will go back to STABLE if you need further detail. 
> > 
> 
> Could you please provide following information:
> 1) boot with verbose mode on (boot -v or verbose_loading="YES" into your
> loader.conf) and check your console messages. Are there any
> "bge2: link UP/DOWN" messages? Unplug/plug cable and check those messages again.
> 
> 2) When you sniff bge2 with tcpdump which packets do you see (incoming, outgoing, both)?
> 
> -- 
> Oleg.

Hi Oleg,

I added ;

root@~# less /boot/loader.conf 
verbose_loading="YES

and reboot the machine;

root@~# uname -a
FreeBSD nrouter.cc.metu.edu.tr 6.0-STABLE FreeBSD 6.0-STABLE #1: Sun Jan 29 16:29:48 EET 2006     root at nrouter.cc.metu.edu.tr:/usr/obj/usr/src/sys/NON-GENERIC  i386

and dmesg shows nothing. After reboot I configured bge2 with ;

ifconfig bge2 xxx.yyy.2.2/24 up

root@~# dmesg | grep bge
bge0: <Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002> mem 0xf1020000-0xf102ffff irq 48 at device 1.0 on pci3
miibus0: <MII bus> on bge0
bge0: Ethernet address: 00:11:09:9b:6a:7d
bge1: <Broadcom BCM5701 Gigabit Ethernet, ASIC rev. 0x105> mem 0xf1000000-0xf100ffff irq 52 at device 2.0 on pci3
miibus1: <MII bus> on bge1
bge1: Ethernet address: 00:04:76:f7:99:6e
bge2: <Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002> mem 0xf1010000-0xf101ffff irq 56 at device 3.0 on pci3
bge2: Ethernet address: 00:10:18:00:4d:53
bge0: link state changed to UP

then I tried to remove the fiber optic connection from the card and reinsert but there was no error messages. I tried it a couple of times. It shows "no carrier" message in the ifconfig status but print no console message.

I also added the tcpdump; before starting out tcpdump I initiated a ping xxx.yyy.2.1 for the outgoing messages. No PF working .

root@~# pfctl -d
pfctl: pf not enabled

root@~# tcpdump -n -i bge2
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bge2, link-type EN10MB (Ethernet), capture size 96 bytes
16:47:01.823270 IP xxx.yyy.250.183.2050 > 239.255.255.250.1900: UDP, length 341
16:47:01.843742 IP xxx.yyy.2.58.52825 > xxx.yyy.2.253.514: SYSLOG local0.info, length: 150
16:47:01.933253 IP xxx.yyy.250.183.2050 > 239.255.255.250.1900: UDP, length 341
16:47:02.045289 IP xxx.yyy.250.183.2050 > 239.255.255.250.1900: UDP, length 341
16:47:02.153373 IP xxx.yyy.250.183.2050 > 239.255.255.250.1900: UDP, length 341
16:47:02.215242 IP xxx.yyy.250.98.2049 > 239.255.255.250.1900: UDP, length 300
16:47:02.319671 IP xxx.yyy.250.98.2049 > 239.255.255.250.1900: UDP, length 300
16:47:02.334737 IP xxx.yyy.2.102 > 224.0.0.13: PIMv2, Hello, length: 34
16:47:02.369839 IP xxx.yyy.213.243.57273 > 239.255.255.250.1900: UDP, length 325
16:47:02.371595 IP xxx.yyy.213.243.49011 > 239.255.255.250.1900: UDP, length 316
16:47:02.375399 IP xxx.yyy.213.243.65255 > 239.255.255.250.1900: UDP, length 356
16:47:02.378763 IP xxx.yyy.251.185.2049 > 239.255.255.250.1900: UDP, length 301
16:47:02.429663 IP xxx.yyy.250.98.2049 > 239.255.255.250.1900: UDP, length 306
16:47:02.482316 IP xxx.yyy.251.185.2049 > 239.255.255.250.1900: UDP, length 301
16:47:02.539651 IP xxx.yyy.250.98.2049 > 239.255.255.250.1900: UDP, length 306
16:47:02.592451 IP xxx.yyy.251.185.2049 > 239.255.255.250.1900: UDP, length 307
16:47:02.606931 IP xxx.yyy.250.99.2050 > 239.255.255.250.1900: UDP, length 300
16:47:02.649639 IP xxx.yyy.250.98.2049 > 239.255.255.250.1900: UDP, length 340
16:47:02.685620 IP xxx.yyy.2.72 > 224.0.0.5: OSPFv2, Hello, length: 276
16:47:02.702441 IP xxx.yyy.251.185.2049 > 239.255.255.250.1900: UDP, length 307
16:47:02.711217 IP xxx.yyy.250.99.2050 > 239.255.255.250.1900: UDP, length 300
16:47:02.759777 IP xxx.yyy.250.98.2049 > 239.255.255.250.1900: UDP, length 340
16:47:02.812431 IP xxx.yyy.251.185.2049 > 239.255.255.250.1900: UDP, length 341
16:47:02.821206 IP xxx.yyy.250.99.2050 > 239.255.255.250.1900: UDP, length 306
16:47:02.871813 IP xxx.yyy.250.98.2049 > 239.255.255.250.1900: UDP, length 340
16:47:02.909109 IP xxx.yyy.2.8 > 224.0.0.5: OSPFv2, Hello, length: 276
16:47:02.922420 IP xxx.yyy.251.185.2049 > 239.255.255.250.1900: UDP, length 341
16:47:02.931196 IP xxx.yyy.250.99.2050 > 239.255.255.250.1900: UDP, length 306
16:47:02.968347 IP xxx.yyy.2.235 > 224.0.0.5: OSPFv2, Hello, length: 276
16:47:02.979756 IP xxx.yyy.250.98.2049 > 239.255.255.250.1900: UDP, length 340
16:47:03.034605 IP xxx.yyy.251.185.2049 > 239.255.255.250.1900: UDP, length 341
16:47:03.041186 IP xxx.yyy.250.99.2050 > 239.255.255.250.1900: UDP, length 340
16:47:03.080531 IP xxx.yyy.249.99.2049 > 239.255.255.250.1900: UDP, length 300
16:47:03.142401 IP xxx.yyy.251.185.2049 > 239.255.255.250.1900: UDP, length 341
16:47:03.151176 IP xxx.yyy.250.99.2050 > 239.255.255.250.1900: UDP, length 340
16:47:03.184963 IP xxx.yyy.249.99.2049 > 239.255.255.250.1900: UDP, length 300
16:47:03.202075 IP xxx.yyy.2.32 > 224.0.0.13: PIMv2, Hello, length: 34
16:47:03.215386 IP xxx.yyy.2.98.55920 > xxx.yyy.2.253.514: SYSLOG local0.info, length: 141
16:47:03.263508 IP xxx.yyy.250.99.2050 > 239.255.255.250.1900: UDP, length 340
16:47:03.294952 IP xxx.yyy.249.99.2049 > 239.255.255.250.1900: UDP, length 306
16:47:03.312065 IP xxx.yyy.67.99.42982 > 239.255.255.250.1900: UDP, length 323
16:47:03.322158 IP xxx.yyy.67.99.53196 > 239.255.255.250.1900: UDP, length 314
16:47:03.332397 IP xxx.yyy.67.99.40856 > 239.255.255.250.1900: UDP, length 354
16:47:03.371302 IP xxx.yyy.250.99.2050 > 239.255.255.250.1900: UDP, length 340
16:47:03.400555 00:0e:38:a8:73:9c > 01:00:0c:cc:cc:cd sap aa ui/C
16:47:03.404944 IP xxx.yyy.249.99.2049 > 239.255.255.250.1900: UDP, length 306
16:47:03.515077 IP xxx.yyy.249.99.2049 > 239.255.255.250.1900: UDP, length 340
16:47:03.543599 IP xxx.yyy.2.55 > 224.0.0.5: OSPFv2, Hello, length: 276
16:47:03.613365 802.1d config 8000.00:d0:95:82:01:9a.73f0 root ffff.ff:ff:ff:ff:ff:ff pathcost 0 age 0 max 20 hello 2 fdelay 15 
16:47:03.625067 IP xxx.yyy.249.99.2049 > 239.255.255.250.1900: UDP, length 340
16:47:03.723207 IP xxx.yyy.2.250 > 224.0.0.13: PIMv2, Hello, length: 34
16:47:03.737102 IP xxx.yyy.249.99.2049 > 239.255.255.250.1900: UDP, length 340
16:47:03.845042 IP xxx.yyy.249.99.2049 > 239.255.255.250.1900: UDP, length 340
16:47:04.056826 IP xxx.yyy.2.11 > 224.0.0.1: igmp query v2
16:47:04.075108 IP xxx.yyy.60.42.1346 > 229.55.150.208.1345: UDP, length 180
16:47:04.129078 IP xxx.yyy.250.181.2050 > 239.255.255.250.1900: UDP, length 301
16:47:04.233068 IP xxx.yyy.250.181.2050 > 239.255.255.250.1900: UDP, length 301
16:47:04.327992 IP xxx.yyy.250.142.1346 > 229.55.150.208.1345: UDP, length 165
16:47:04.343056 IP xxx.yyy.250.181.2050 > 239.255.255.250.1900: UDP, length 307
16:47:04.367775 IP xxx.yyy.2.170 > 224.0.0.5: OSPFv2, Hello, length: 276
16:47:04.369384 IP xxx.yyy.213.243.57827 > 239.255.255.250.1900: UDP, length 325
16:47:04.373482 IP xxx.yyy.213.243.50118 > 239.255.255.250.1900: UDP, length 316
16:47:04.375091 IP xxx.yyy.213.243.34701 > 239.255.255.250.1900: UDP, length 356
16:47:04.453194 IP xxx.yyy.250.181.2050 > 239.255.255.250.1900: UDP, length 307
16:47:04.563181 IP xxx.yyy.250.181.2050 > 239.255.255.250.1900: UDP, length 341
16:47:04.657372 IP xxx.yyy.2.72 > 224.0.0.13: PIMv2, Hello, length: 34
16:47:04.673169 IP xxx.yyy.250.181.2050 > 239.255.255.250.1900: UDP, length 341
16:47:04.695255 IP xxx.yyy.2.39 > 224.0.0.13: PIMv2, Hello, length: 34
^C
68 packets captured
95 packets received by filter
0 packets dropped by kernel