Date: Wed, 01 Jun 2022 09:23:33 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 264179] 13.1-RELEASE hands in boot with Intel Alderlake GbE NIC Message-ID: <bug-264179-7501-Cq0QuV3dtw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264179-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-264179-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=264179 Tomoaki AOKI <junchoon@dec.sakura.ne.jp> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |junchoon@dec.sakura.ne.jp --- Comment #5 from Tomoaki AOKI <junchoon@dec.sakura.ne.jp> --- Can Bug 253172 [1] be related with this? Bug 253172 - Intel e1000 - Interface Stalls After Media Type is Changed With this bug, second if_em (em1) causes hang. And with Bug 253172, second attempt with ifconfig up (different media type used) causes interface stall. Just a thought, but if this affects even if the port is different (whichever port or media type is different on if_em driver causes same issue), and if the em1 is configured to use DHCP, possibly em1 wait for DHCP reply, which never comes into, and thus locks up. Not reading the if_em (e1000) codes nor iflib codes, I could be mis-understanding, of course. [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253172 -- You are receiving this mail because: You are the assignee for the bug. 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-264179-7501-Cq0QuV3dtw>