Hello; I noticed a regression from 9.0 and I cannot boot directly FreeBSD and access the network. Unfortunately I cannot recall the exact commit where this started happening. uname -a FreeBSD pcbsd-8555 9.0-STABLE FreeBSD 9.0-STABLE #12: Wed May 30 11:16:35 PDT 2012 root@build9x64.pcbsd.org:/usr/obj/builds/amd64/pcbsd-build90/fbsd-source/9.0/sys/GENERIC 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. Pedro.
On Thu, 2012-06-21 at 12:05 -0700, Pedro Giffuni wrote:> Hello; > > I noticed a regression from 9.0 and I cannot boot directly FreeBSD > and access the network. Unfortunately I cannot recall the exact > commit where this started happening. > > uname -a > FreeBSD pcbsd-8555 9.0-STABLE FreeBSD 9.0-STABLE #12: Wed May 30 > 11:16:35 PDT 2012 > root@build9x64.pcbsd.org:/usr/obj/builds/amd64/pcbsd-build90/fbsd-source/9.0/sys/GENERIC > 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. > > Pedro.I wonder if this is the one that caused your problems? http://svnweb.freebsd.org/base?view=revision&revision=233495 Can you post the full verbose dmesg and the output of pciconf -lvb for review? Sean
--- Gio 21/6/12, Sean Bruno <seanbru@yahoo-inc.com> ha scritto:> On Thu, 2012-06-21 at 12:05 -0700, Pedro Giffuni wrote: > > Hello; > > > > I noticed a regression from 9.0 and I cannot boot > directly FreeBSD > > and access the network. Unfortunately I cannot recall > the exact > > commit where this started happening. > > > > uname -a > > FreeBSD pcbsd-8555 9.0-STABLE FreeBSD 9.0-STABLE #12: > Wed May 30 > > 11:16:35 PDT 2012 > > root@build9x64.pcbsd.org:/usr/obj/builds/amd64/pcbsd-build90/fbsd-source/9.0/sys/GENERIC > > > amd64 > >...> > I wonder if this is the one that caused your problems? > > http://svnweb.freebsd.org/base?view=revision&revision=233495 >I will have a look at reverting it locally.> Can you post the full verbose dmesghttp://people.freebsd.org/~pfg/dmesg-bge-error.txt> and the output of pciconf -lvbhttp://people.freebsd.org/~pfg/pciconf.txt> for review? >Thanks! Pedro.
YongHyeon PYUN
2012-Jun-23 06:28 UTC
Network unavailable when booting directly to FreeBSD.
On Thu, Jun 21, 2012 at 02:05:33PM -0500, Pedro Giffuni wrote:> Hello; > > I noticed a regression from 9.0 and I cannot boot directly FreeBSD > and access the network. Unfortunately I cannot recall the exact > commit where this started happening. > > uname -a > FreeBSD pcbsd-8555 9.0-STABLE FreeBSD 9.0-STABLE #12: Wed May 30 > 11:16:35 PDT 2012 > root@build9x64.pcbsd.org:/usr/obj/builds/amd64/pcbsd-build90/fbsd-source/9.0/sys/GENERIC > 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? 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> > Pedro.