From owner-freebsd-stable@FreeBSD.ORG Fri Jun 22 00:48:02 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5D1CF1065674; Fri, 22 Jun 2012 00:48:02 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1-b.corp.bf1.yahoo.com (mrout1-b.corp.bf1.yahoo.com [98.139.253.104]) by mx1.freebsd.org (Postfix) with ESMTP id 2ADB78FC17; Fri, 22 Jun 2012 00:48:02 +0000 (UTC) Received: from [IPv6:::1] (rideseveral.corp.yahoo.com [10.73.160.231]) by mrout1-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q5M0ldEI071849; Thu, 21 Jun 2012 17:47:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1340326060; bh=ONV302FYM3hJLPl7QVop9lvTCNAOFW7i25VqkqtrurM=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=Q4/ALSlsxFWLm6Y55pAYL5joWYLbfgLcCawtxwwJbdhnDOJnYMxP4vWWKurFRqO/k Xyt6UQvHvXGrJ7KYGj2EkgUfOLnjmXE4VpnCdZU1wjtZJvcmOpYpvGfYrmQKKfJDSj 4lXtdDwMtjORntFluY9x9hNc2nxD0paLBpY20h1A= From: Sean Bruno To: Pedro Giffuni In-Reply-To: <4FE3707D.4040307@FreeBSD.org> References: <4FE3707D.4040307@FreeBSD.org> Content-Type: text/plain; charset="UTF-8" Date: Thu, 21 Jun 2012 17:47:39 -0700 Message-ID: <1340326059.3247.21.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Milter-Version: master.31+4-gbc07cd5+ X-CLX-ID: 326060001 Cc: "freebsd-stable@freebsd.org" Subject: Re: Network unavailable when booting directly to FreeBSD. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2012 00:48:02 -0000 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: port 0xcf8-0xcff on acpi0 > pcib0: Length mismatch for 4 range: 81 vs 7f > pci0: on pcib0 > pci0: at device 0.0 (no driver attached) > pci0: at device 0.1 (no driver attached) > pci0: at device 0.2 (no driver attached) > pci0: at device 0.3 (no driver attached) > pci0: at device 0.4 (no driver attached) > pci0: at device 0.5 (no driver attached) > pci0: at device 0.6 (no driver attached) > pci0: at device 0.7 (no driver attached) > pcib1: at device 2.0 on pci0 > pci1: on pcib1 > pcib2: at device 3.0 on pci0 > pci2: on pcib2 > bge0: 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: on bge0 > brgphy0: 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: at device 4.0 on pci0 > pci3: 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