Date: Tue, 27 Oct 2015 15:16:50 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: Bootup error Message-ID: <562F9562.4060803@FreeBSD.org> In-Reply-To: <20151027104847.248ee7d6@seibercom.net> References: <20151027104847.248ee7d6@seibercom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --5OpKmIvviCeeFBdbP1NIQM8MQvuGd86OQ Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015/10/27 14:48, Jerry wrote: > nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) >=20 > That will repeat on down the screen until I do a <CTRL> <ALT> <DEL> seq= uence > and shut the pc down. Usually, but not always, it will start up correct= ly > then. Sometime, I have had to leave the PC off for several minutes bef= ore it > would reboot correctly. >=20 > 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. The very first thing to do is to eliminate the embarrassingly obvious and cheap to repair possible causes: make sure all network cabling is in good repair, not kinked or tied in place too tightly, that ethernet jacks are firmly plugged into their sockets and that they aren't pulling off the ends of their cables, that NICs are properly seated in the slots on your motherboard. Make sure everything, including any switch ports, are using the correct media/duplex settings -- for Gb ethernet that's pretty much always going to be 1000baseT + autoneg'd Full Duplex. Make sure you don't have any cabling loops, (unless this is done deliberately for resilience and you are running RSTP or similar to prevent network storms). Running 'netstat -i' can frequently pinpoint problems: any interface and the attached cabling with a more than trivial number of packet errors or drops (especially if only on input or only on output) should be investigated. If that doesn't pinpoint the problem, then you're down to swapping out components or bits of network hardware in an attempt to discover the bogon emitter. Adept use of tcpdump(1) and maybe wireshark(1) will aid your diagnosis. Cheers, Matthew [*] Bogons defined in this instance as 'malformed network packets'. --5OpKmIvviCeeFBdbP1NIQM8MQvuGd86OQ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJWL5V0XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnRjMP/0UtNujkukyVfhNaupXE0bV5 BnpfCM0/BSSTz+D9mCjyuDI5R+uZprBdTqj3DUYZHWUrMMoBB85N8F5DFtVRn9LC cl8g9volFFwQVK+wr6PY9YJsN/B9noFu9oSmnqmKU3Y8TLBLDhkPcbm0MLaYKed9 mXrsCsYahqA1KQtL3OZj2hUNtwQuSO/r3B0OzIba4LIbtdSd3itMhTeUiVy9tDan ACxKGM2P88hHnKqWbVJCENh+A1KdvEEmPUEyLjeWsnDwNin2QxQiG8ded/BHHx+O WkDR3ZbtZOBtPmkKi4Aq3lmEnbIPAinb8yezbkSyjQq99+3ZPsWQPJvhoc7wKbRc PEZhWegvAW9VNJ+bWIIDu1A6gsxZ1SVmqZhyHws366jMXLi6pFuQDcuUh+QeojUk GQWNXCadr2YEKi40i8Mps4dWoBmKD04ppcmWif/ty0+MWsF/OgEl1phlSYGpNvlg BiD8sVYQOkbsh3UfdmJmsn3fa5JlShLY7kE8GqotVdFYRxYcQwt/ZtfbYaDHlv9g 2IKe9xiFz9nVkpdeBj1R7DLVqRLjPV3/TnDgoAKy5gt6EUcuKyd/biwiwZzvM2yi inSKpiFfbO508/4fA+GYHRpeeBLQ6SQidcpAi7XsCOOQYGIsYRl1lKmHlP6TmRbP Li5DOIAMeNjd/A4zH8k2 =S4PY -----END PGP SIGNATURE----- --5OpKmIvviCeeFBdbP1NIQM8MQvuGd86OQ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?562F9562.4060803>