From: xnor <xnoreq@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] Bug 216257 - igc: Detected Tx Unit Hang after losing carrier, sporadic resets and connectivity loss with Intel I225-V
Date: Tue, 18 Oct 2022 20:42:52 +0200 [thread overview]
Message-ID: <361c57ff-6b9f-bf39-c720-7dce7622941b@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 959 bytes --]
Hello,
I've reported this bug a while ago on bugzilla.kernel.org but haven't seen any
indication that the bug has even been looked at:
https://bugzilla.kernel.org/show_bug.cgi?id=216257
I have a router with multiple Intel I225-V (rev 03) ethernet controllers.
Three of them, namely eth0, eth1 and eth2 are bridged (br-lan).
Initially, I used Linux 5.18.11. After suspending a computer connected through
eth0, errors started showing up in dmesg and packet loss increased.
With different kernel versions (several 5.15 lts version, 6.0.1) I'm now only
seeing a sudden loss of connectivity on br-lan and a registers dump in dmesg.
The trigger for this seems almost random now, but happens once every couple of
days in the morning hours.
Some of the dmesg snippets at the time of the errors are attached to the bug
report, though I can also send them here if need be.
Same goes for kernel versions, configs and any other info needed.
Thank you for any help.
[-- Attachment #1.2: Type: text/html, Size: 1260 bytes --]
[-- Attachment #2: Type: text/plain, Size: 162 bytes --]
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
reply other threads:[~2022-10-18 18:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=361c57ff-6b9f-bf39-c720-7dce7622941b@gmail.com \
--to=xnoreq@gmail.com \
--cc=intel-wired-lan@osuosl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox