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; --- Sab 23/6/12, YongHyeon PYUN <pyunyh@gmail.com> ha scritto: ... > > > amd64 > > > > From my dmesg > > ______ > > ... > > pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on > acpi0 > > pcib0: Length mismatch for 4 range: 81 vs 7f > > pci0: <ACPI PCI bus> on pcib0 > > pci0: <memory, RAM> at device 0.0 (no driver > attached) > > pci0: <memory, RAM> at device 0.1 (no driver > attached) > > pci0: <memory, RAM> at device 0.2 (no driver > attached) > > pci0: <memory, RAM> at device 0.3 (no driver > attached) > > pci0: <memory, RAM> at device 0.4 (no driver > attached) > > pci0: <memory, RAM> at device 0.5 (no driver > attached) > > pci0: <memory, RAM> at device 0.6 (no driver > attached) > > pci0: <memory, RAM> at device 0.7 (no driver > attached) > > pcib1: <ACPI PCI-PCI bridge> at device 2.0 on > pci0 > > pci1: <ACPI PCI bus> on pcib1 > > pcib2: <ACPI PCI-PCI bridge> at device 3.0 on > pci0 > > pci2: <ACPI PCI bus> on pcib2 > > bge0: <Broadcom NetXtreme Gigabit Ethernet > Controller, ASIC rev. > > 0x00b002> mem 0xfdef0000-0xfdefffff irq 16 at device > 0.0 on pci2 > > bge0: CHIP ID 0x0000b002; ASIC REV 0x0b; CHIP REV 0xb0; > PCI-E > > miibus0: <MII bus> on bge0 > > brgphy0: <BCM5754/5787 1000BASE-T media > interface> PHY 1 on miibus0 > > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, > 100baseTX-FDX, 1000baseT, > > 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, > auto, auto-flow > > bge0: Ethernet address: 00:18:8b:76:a4:1e > > pcib3: <ACPI PCI-PCI bridge> at device 4.0 on > pci0 > > pci3: <ACPI PCI bus> on pcib3 > > > > .... > > Cuse4BSD v0.1.23 @ /dev/cuse > > bge0: watchdog timeout -- resetting > > bge0: watchdog timeout -- resetting > > WARNING: attempt to domain_add(bluetooth) after > domainfinalize() > > fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 > > bge0: watchdog timeout -- resetting > > bge0: link state changed to DOWN > > bge0: link state changed to UP > > bge0: watchdog timeout -- resetting > > bge0: link state changed to DOWN > > bge0: link state changed to UP > > bge0: watchdog timeout -- resetting > > bge0: link state changed to DOWN > > bge0: link state changed to UP > > _____ > > > > Iff I boot Windows first and then reboot to start > > FreeBSD the network works fine. > > This looks strange and I can't narrow down what other > changes made > since 9.0-RELEASE broke the driver. Would you try reverting > r235821? > I reverted it manually but things didn't change. > If that does not solve the issue, would you try a WIP > version at > the following URL? It's mainly written to improve BCM5720 > with APE > firmware support and it exactly follows recommendations > suggested > by Broadcom so it may have some differences. > > http://people.freebsd.org/~yongari/bge/if_bge.c > http://people.freebsd.org/~yongari/bge/if_bgereg.h > http://people.freebsd.org/~yongari/bge/brgphy.c > No joy either :( Pedro.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1340481884.74911.YahooMailClassic>