From owner-freebsd-stable@FreeBSD.ORG Sat Jun 23 06:27:57 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 0ABF91065672; Sat, 23 Jun 2012 06:27:57 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id C80EB8FC0A; Sat, 23 Jun 2012 06:27:56 +0000 (UTC) Received: by dadv36 with SMTP id v36so3434359dad.13 for ; Fri, 22 Jun 2012 23:27:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=X93jzRfdjMxrc2kkW+JEg0pu2xACulniBFXyND00iLY=; b=fgrlT/FFtnh6pruLyXzeI7lBCqezrZspj48SXyfEksckp+ObfmoT3TggWkSASMpmQL /xF6WW86KKJqcjbtJazA116gLuxQ1TqLQyPGER84zx6LEdqPRweuwmL7V9Jrsdo1MA8z N0bhU+K8Y79iPpL71C4e4T22O85wAaFiYOjibnDf1ytDwf0Wn8OX20DYw4IGbYlWJe5P PgRWhd18vDgl3nfpTfhnowZCQYjeXpoLobisHdYwU5oJUBxW0hH/zmwAxSUWr1NEPI/E dK9Tnbdxvgu7hdnXKi9S3Ngez9RP+4TPuFlY+7ViUewc5u7vySWLLM5ITEQARks4omP9 BcPA== Received: by 10.68.223.138 with SMTP id qu10mr18126854pbc.50.1340432876336; Fri, 22 Jun 2012 23:27:56 -0700 (PDT) Received: from pyunyh@gmail.com ([114.111.62.249]) by mx.google.com with ESMTPS id vp4sm1441037pbc.61.2012.06.22.23.27.53 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 22 Jun 2012 23:27:55 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Sat, 23 Jun 2012 15:27:46 -0700 From: YongHyeon PYUN Date: Sat, 23 Jun 2012 15:27:46 -0700 To: Pedro Giffuni Message-ID: <20120623222746.GA14050@michelle.cdnetworks.com> References: <4FE3707D.4040307@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FE3707D.4040307@FreeBSD.org> User-Agent: Mutt/1.4.2.3i 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 Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jun 2012 06:27:57 -0000 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: 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. 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.