From owner-freebsd-bugs@FreeBSD.ORG Mon May 4 17:16:36 2015 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 157FDE8 for ; Mon, 4 May 2015 17:16:36 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DA0A219E8 for ; Mon, 4 May 2015 17:16:35 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t44HGZeA051158 for ; Mon, 4 May 2015 17:16:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 199933] re0 fails on boot, but works after manual intervention Date: Mon, 04 May 2015 17:16:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: cen5848@louisiana.edu X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 May 2015 17:16:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199933 Bug ID: 199933 Summary: re0 fails on boot, but works after manual intervention Product: Base System Version: 10.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: cen5848@louisiana.edu Hello all, I have an issue with networking on a fresh vanilla install of FreeBSD 10.1 amd64. I've been trying to use the built in wired networking on a Gigabyte GA-F2A55M and when using a static IP any sort of network activity fails on boot. However, if I wait 15 seconds, and manually\script restart networking (netif and routing) everything works as expected. The problem with this temp solution is that this breaks my jails and nfs client. I first noticed this issue in FreeBSD 10.0 and I have not tried earlier versions, and anytime I've reinstalled this problem is consistent. This does seem similar to Bug 180852, but there has been no activity for a year on that bug. It is because of that previously filed bug that I'm using the second level severity. If there is any additional information that I can provide to help solve this problem, please let me know. Thanks! useful information: ---- uname -a: FreeBSD freebsd.host.tld 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 sysctl -a | grep re0: re0: port 0xe000-0xe 0ff mem 0xfea00000-0xfea00fff,0xd0000000-0xd0003fff irq 16 at device 0.0 on pci1 re0: Using 1 MSI-X message re0: Chip rev. 0x2c800000 re0: MAC rev. 0x00100000 miibus0: on re0 re0: Ethernet address: 74:d4:35:9b:3f:28 <118>Starting Network: lo0 re0. <118>re0: flags=8843 metric 0 mtu 1500 <5>re0: link state changed to UP <5>re0: link state changed to DOWN <5>re0: link state changed to UP dev.miibus.0.%parent: re0 -- You are receiving this mail because: You are the assignee for the bug.