Date: Sat, 23 Jun 2012 13:04:44 -0700 (PDT) From: Pedro Giffuni <pfg@freebsd.org> To: pyunyh@gmail.com Cc: freebsd-stable@freebsd.org Subject: Re: Network unavailable when booting directly to FreeBSD. Message-ID: <1340481884.74911.YahooMailClassic@web113518.mail.gq1.yahoo.com> In-Reply-To: <20120623222746.GA14050@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello;=0A=0A--- Sab 23/6/12, YongHyeon PYUN <pyunyh@gmail.com> ha scritto:= =0A...=0A> =0A> > amd64=0A> > =0A> > From my dmesg=0A> > ______=0A> > ...= =0A> > pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on=0A> acpi0=0A> > pc= ib0: Length mismatch for 4 range: 81 vs 7f=0A> > pci0: <ACPI PCI bus> on pc= ib0=0A> > pci0: <memory, RAM> at device 0.0 (no driver=0A> attached)=0A> > = pci0: <memory, RAM> at device 0.1 (no driver=0A> attached)=0A> > pci0: <mem= ory, RAM> at device 0.2 (no driver=0A> attached)=0A> > pci0: <memory, RAM> = at device 0.3 (no driver=0A> attached)=0A> > pci0: <memory, RAM> at device = 0.4 (no driver=0A> attached)=0A> > pci0: <memory, RAM> at device 0.5 (no dr= iver=0A> attached)=0A> > pci0: <memory, RAM> at device 0.6 (no driver=0A> a= ttached)=0A> > pci0: <memory, RAM> at device 0.7 (no driver=0A> attached)= =0A> > pcib1: <ACPI PCI-PCI bridge> at device 2.0 on=0A> pci0=0A> > pci1: <= ACPI PCI bus> on pcib1=0A> > pcib2: <ACPI PCI-PCI bridge> at device 3.0 on= =0A> pci0=0A> > pci2: <ACPI PCI bus> on pcib2=0A> > bge0: <Broadcom NetXtre= me Gigabit Ethernet=0A> Controller, ASIC rev. =0A> > 0x00b002> mem 0xfdef00= 00-0xfdefffff irq 16 at device=0A> 0.0 on pci2=0A> > bge0: CHIP ID 0x0000b0= 02; ASIC REV 0x0b; CHIP REV 0xb0;=0A> PCI-E=0A> > miibus0: <MII bus> on bge= 0=0A> > brgphy0: <BCM5754/5787 1000BASE-T media=0A> interface> PHY 1 on mii= bus0=0A> > brgphy0:=A0 10baseT, 10baseT-FDX, 100baseTX,=0A> 100baseTX-FDX, = 1000baseT, =0A> > 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master,=0A= > auto, auto-flow=0A> > bge0: Ethernet address: 00:18:8b:76:a4:1e=0A> > pci= b3: <ACPI PCI-PCI bridge> at device 4.0 on=0A> pci0=0A> > pci3: <ACPI PCI b= us> on pcib3=0A> > =0A> > ....=0A> > Cuse4BSD v0.1.23 @ /dev/cuse=0A> > bge= 0: watchdog timeout -- resetting=0A> > bge0: watchdog timeout -- resetting= =0A> > WARNING: attempt to domain_add(bluetooth) after=0A> domainfinalize()= =0A> > fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8=0A> > bge0: watchdog time= out -- resetting=0A> > bge0: link state changed to DOWN=0A> > bge0: link st= ate changed to UP=0A> > bge0: watchdog timeout -- resetting=0A> > bge0: lin= k state changed to DOWN=0A> > bge0: link state changed to UP=0A> > bge0: wa= tchdog timeout -- resetting=0A> > bge0: link state changed to DOWN=0A> > bg= e0: link state changed to UP=0A> > _____=0A> > =0A> > Iff I boot Windows fi= rst and then reboot to start=0A> > FreeBSD the network works fine.=0A> =0A>= This looks strange and I can't narrow down what other=0A> changes made=0A>= since 9.0-RELEASE broke the driver. Would you try reverting=0A> r235821?= =0A> =0A=0AI reverted it manually but things didn't change.=0A=0A> If that = does not solve the issue, would you try a WIP=0A> version at=0A> the follow= ing URL? It's mainly written to improve BCM5720=0A> with APE=0A> firmware s= upport and it exactly follows recommendations=0A> suggested=0A> by Broadcom= so it may have some differences.=0A> =0A> http://people.freebsd.org/~yonga= ri/bge/if_bge.c=0A> http://people.freebsd.org/~yongari/bge/if_bgereg.h=0A>; = http://people.freebsd.org/~yongari/bge/brgphy.c=0A>; =0A=0ANo joy either :(= =0A=0APedro.=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1340481884.74911.YahooMailClassic>