Date: Mon, 13 Jan 2020 20:02:15 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 243319] Panicked laptop & local network ARP flood Message-ID: <bug-243319-7501-OSedxzu8KM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-243319-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-243319-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243319 --- Comment #6 from Conrad Meyer <cem@freebsd.org> --- These are different requesters? It would help to spell out which IP(s) are= the panic'd laptop. 07:55:53.025959 ARP, Request who-has 10.6.112.1 tell 10.6.112.16, length 46 07:55:53.025980 ARP, Request who-has 10.6.112.1 tell 10.6.112.18, length 46 ^^ If you don't have debugnet enabled I don't see any obvious reason debugnet would be ARPing. Plus, debugnet isn't *that* spammy and the number of ARPs= it sends is bounded; it gives up after a few tries (like, 3?). You would see obvious prints as a side effect of debugnet-enabled dump being attempted af= ter the panic, and an obvious print when the ARP request failed. If anything, I suspect this is some NIC internal firmware/hardware behavior= due to the panic'd machine not processing RX queues or something. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243319-7501-OSedxzu8KM>