Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #72181 > unrolled thread
| Started by | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| First post | 2021-06-13 21:20 +0200 |
| Last post | 2021-06-14 21:00 +0200 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#932996: linux-image-4.19.0-5-amd64: e1000e driver crashes under high TX load; `ethtool -K eno1 tso off` resolves issue. Salvatore Bonaccorso <carnil@debian.org> - 2021-06-13 21:20 +0200
Bug#932996: linux-image-4.19.0-5-amd64: e1000e driver crashes under high TX load; `ethtool -K eno1 tso off` resolves issue. John <john@narbondel.org> - 2021-06-14 20:00 +0200
Bug#932996: linux-image-4.19.0-5-amd64: e1000e driver crashes under high TX load; `ethtool -K eno1 tso off` resolves issue. Salvatore Bonaccorso <carnil@debian.org> - 2021-06-14 21:00 +0200
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2021-06-13 21:20 +0200 |
| Subject | Bug#932996: linux-image-4.19.0-5-amd64: e1000e driver crashes under high TX load; `ethtool -K eno1 tso off` resolves issue. |
| Message-ID | <CpDOh-7QS-1@gated-at.bofh.it> |
Control: tags -1 + moreinfo On Thu, Jul 25, 2019 at 09:58:33AM -0700, John wrote: > Package: src:linux > Version: 4.19.37-6 > Severity: normal > > Dear Maintainer, > > Observed flaky network interface under high TX load with guest OS > bridging across eno1 interface. Issue only manifested under load, and > exhibited flapping in dmesg, e.g.: > e1000e 0000:00:1f.6 eno1: Reset adapter unexpectedly > br0: port 1(eno1) entered disabled state). > > Issue appears to be resolved by disabling TSO with: > `ethtool -K eno1 tso off` > > Googling around suggests this may be a common problem with this driver > -- possibly should default to tso off? See possibly related links: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 > https://serverfault.com/questions/616485/e1000e-reset-adapter-unexpectedly-detected-hardware-unit-hang Is this issue still triggerable for you with a recent kernel from either unstable, buster-backports or even mainline without needing to set tso off? Regards, Salvatore
[toc] | [next] | [standalone]
| From | John <john@narbondel.org> |
|---|---|
| Date | 2021-06-14 20:00 +0200 |
| Message-ID | <CpZ2p-3zp-5@gated-at.bofh.it> |
| In reply to | #72181 |
[Multipart message — attachments visible in raw view] — view raw
Hi, I've turned TSO back on to test, and I'm currently on 5.10.0-7-amd64 ($ uname -a -> Linux myrkul 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1 (2021-05-28) x86_64 GNU/Linux). I could not readily reproduce it using a netcat tunnel to push higher load from VM to host, or from VM to external networks, so it looks likely that something in the last two years cleaned this up. Feel free to close, and I can reopen with more details if it comes back. Thanks! - John On Sun, Jun 13, 2021 at 12:11 PM Salvatore Bonaccorso <carnil@debian.org> wrote: > Control: tags -1 + moreinfo > > On Thu, Jul 25, 2019 at 09:58:33AM -0700, John wrote: > > Package: src:linux > > Version: 4.19.37-6 > > Severity: normal > > > > Dear Maintainer, > > > > Observed flaky network interface under high TX load with guest OS > > bridging across eno1 interface. Issue only manifested under load, and > > exhibited flapping in dmesg, e.g.: > > e1000e 0000:00:1f.6 eno1: Reset adapter unexpectedly > > br0: port 1(eno1) entered disabled state). > > > > Issue appears to be resolved by disabling TSO with: > > `ethtool -K eno1 tso off` > > > > Googling around suggests this may be a common problem with this driver > > -- possibly should default to tso off? See possibly related links: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 > > > https://serverfault.com/questions/616485/e1000e-reset-adapter-unexpectedly-detected-hardware-unit-hang > > Is this issue still triggerable for you with a recent kernel from > either unstable, buster-backports or even mainline without needing to > set tso off? > > Regards, > Salvatore >
[toc] | [prev] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2021-06-14 21:00 +0200 |
| Message-ID | <CpZYt-47C-1@gated-at.bofh.it> |
| In reply to | #72191 |
Source: linux Source-Version: 5.10.40-1 Hi On Mon, Jun 14, 2021 at 10:55:08AM -0700, John wrote: > Hi, > > I've turned TSO back on to test, and I'm currently on 5.10.0-7-amd64 ($ > uname -a -> Linux myrkul 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1 > (2021-05-28) x86_64 GNU/Linux). > > I could not readily reproduce it using a netcat tunnel to push higher load > from VM to host, or from VM to external networks, so it looks likely that > something in the last two years cleaned this up. Feel free to close, and I > can reopen with more details if it comes back. Thank you for coming back, much appreciated. So I'm closing as per above with 5.10.41-1 but feel free to reopen if you despite will be able to reproduce/trigger the issue again. Regards, Salvatore
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web