From owner-freebsd-questions@freebsd.org Tue Oct 27 22:13:10 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3E285A1F07C for ; Tue, 27 Oct 2015 22:13:10 +0000 (UTC) (envelope-from jjohnstone.nospamfreebsd@tridentusa.com) Received: from mail.tridentusa.com (mail.tridentusa.com [96.225.19.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.tridentusa.com", Issuer "mail.tridentusa.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A9AE15D0 for ; Tue, 27 Oct 2015 22:13:09 +0000 (UTC) (envelope-from jjohnstone.nospamfreebsd@tridentusa.com) Received: (qmail 92852 invoked from network); 27 Oct 2015 18:06:27 -0400 Received: from john-j (HELO ?172.16.0.90?) (jjohnstone@tridentusa.com@172.16.0.90) by mail.tridentusa.com with AES128-SHA encrypted SMTP; 27 Oct 2015 18:06:27 -0400 From: John Johnstone Subject: Re: Bootup error To: freebsd-questions@freebsd.org References: <20151027104847.248ee7d6@seibercom.net> <562F9562.4060803@FreeBSD.org> Message-ID: <562FF538.8090104@tridentusa.com> Date: Tue, 27 Oct 2015 18:05:44 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <562F9562.4060803@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Oct 2015 22:13:10 -0000 On 10/27/2015 11:16 AM, Matthew Seaman wrote: > On 2015/10/27 14:48, Jerry wrote: >> nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) >> >> That will repeat on down the screen until I do a sequence >> and shut the pc down. Usually, but not always, it will start up correctly >> then. Sometime, I have had to leave the PC off for several minutes before it >> would reboot correctly. >> >> Can anyone tell me what is causing this and how to correct it? > > Something is emitting bogons[*] onto your LAN. It could well be your > nfe0 NIC, but it might be just about anything attached to your network. I've seen this occasionally on a HP DL360 with HP Broadcom based NIC's running pfSense 2.2 which is built from FreeBSD 10.1. It's always been after a cold boot, never while the system has been running. I've only seen it just a few times. It was a few months ago so I don't remember what fixed it but it was either just rebooting or removing and reconnecting the Ethernet cable. I have no idea what caused it but I'm thinking something link specific, meaning just the link between the NIC that reported and the Ethernet switch. Some odd driver bug, Ethernet switch interaction (possibly autonegotiate) problem perhaps? These same links run clean for many months otherwise. Maybe bad connector seating on the initial plug-in. It's important to realize that only a cut-through forwarding switch will propagate defective packets. Many recent Ethernet switches in the < $100 category are store-and-forward. They don't forward defective packets from one switch port to another. The better / expensive switches are store-and-forward even ones that are 15 years or more old. If there are errors and bad packets occurring on one port the trouble will remain on just that one port. - John J.