Date: Tue, 02 Dec 2025 22:08:06 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 279245] igc(4) I226 (and I225) TX hangups Message-ID: <bug-279245-7501-umnHXf4vYp@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-279245-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-279245-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=279245 --- Comment #10 from Michael Adler <madler@tapil.com> --- I've seen cases where the bug was in power management in the HW, where the real solution short of modifying the HW was working around the power management bug. In that case it was a PCIe core purchased from a major IP vendor that would go into micro sleep states based on the traffic pattern sent to it from the device. The time required to wake up caused major loss of bandwidth. There's nothing the kernel or driver could have done to fix it short of preventing the mode that allowed sleep. Given that everyone reporting problems fixes it with the same solution and Intel hasn't worked around it even in the latest firmware, doesn't it seem reasonable to conclude that the driver should deal with this quirk/bug and that Intel won't? -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279245-7501-umnHXf4vYp>