This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1029.33 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1056.61+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws/5.15.0-1056.61
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-raspi/5.15.0-1048.51
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug is awaiting verification that the linux-kvm/5.15.0-1052.57
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-kvm' to 'verification-done-jammy-
linux-kvm'. If the
This bug is awaiting verification that the linux-oracle/5.15.0-1053.59
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-oracle' to 'verification-done-
jammy-linux-oracle'.
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1050.56 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
This bug was fixed in the package linux - 5.15.0-100.110
---
linux (5.15.0-100.110) jammy; urgency=medium
* jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616)
* i915 regression introduced with 5.5 kernel (LP: #2044131)
- drm/i915: Skip some timing checks on BXT/GLK
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-25.25~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
hwe-6.5' to
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036239
Title:
Intel E810-XXV - NETDEV
LP update:
Mantic update:
Due to lack of reproduction environment I have been performing following
regression test:
1. Setup:
nic: 2port E810-C
both interfaces set up in bonding
kernel: 6.5.0-25-generic
2. Test cases:
0) verified that code from the change is used during driver
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1055.58+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-ibm-gt-fips' to
Hi Roxana,
Mantic verification is still not finished.
I did some touch tests without stress traffic.
I'm trying to get my hands on E810 device to finish testing, I'll update ticket
once it's done.
Wishful ETA EOW 09.
--
You received this bug notification because you are a member of Kernel
Hi Robert! Thanks for testing this on jammy. I marked the tag as verified
('verification-done-jammy-linux') to reflect that.
Could you share the results from mantic? we need to release this next week and
we need a confirmation this works as expected.
If your test looks fine, please remove
Jammy update:
Due to lack of reproduction environment I have been performing following
regression test:
1. Setup:
nic: 2port E810-XXV
both interfaces set up in bonding
kernel: 5.15.0-100-generic
2. Test cases:
0) verified that code from the change is used during driver init
This bug is awaiting verification that the linux/6.5.0-25.25 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
Houston, we have a problem...
This bug is notoriously difficult to reproduce. The only environment
that presented it is now in production and will not be available for
testing anymore. Which means that this cannot be tested, unless anyone
can suggest a new way of reproducing it.
--
You received
This bug is awaiting verification that the linux/5.15.0-100.110 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still
Yes, HWE kernels based on the Jammy/Mantic/Noble kernels should get this
fix automatically when the GA versions get released.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036239
Title:
Thx a log Heitor! With no mention of some new package fixing this I did not
correlate that to any patch to the kernel.
Will the be fixed in the HWE kernel as well then?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@christian-rhomann "Fix committed" here means that the patches have been merged
into Ubuntu's kernel tree for that specific release. The patch Robert submitted
is the one from upstream, not the test patch from the comments here.
E.g. for Jammy:
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036239
Title:
Intel E810-XXV - NETDEV WATCHDOG: (ice):
@Robert thanks for keeping this bug alive and updated!
1) More debug info required?
@Robert, reading your post
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/50 again,
I am wondering if you asked me to provided more debug info with NVM 4.4 on my
E810 NICs? Would this
Switching status for Noble to In Progress.
Target release for Noble is 6.8 (which includes fix) but it's not out yet,
status will be changed once 6.8 will be introduced.
** Changed in: linux (Ubuntu Noble)
Status: Invalid => In Progress
--
You received this bug notification because you
Fix already included in 6.8
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036239
Title:
Intel E810-XXV -
Hey Christian, Intel proposed change [1]
which is targeting this problem and based on our testing in fact it solves the
problem.
This change is currently added to Ubuntu Kernels.
I'm also keeping an eye on [2] but right now I don't yet see "business need" to
incorporate it to Ubuntu Kernel.
@Stefan Could you kindly elaborate on the "Fix Commmited"? Was there any
change to the kernel that would fix this issue? Is this fixed with 4.40
NVM from Intel?
Reading Roberts post
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/50)
again, it seems that he is only guessing
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036239
Title:
Intel E810-XXV - NETDEV WATCHDOG: (ice):
** Also affects: linux (Ubuntu Noble)
Importance: Medium
Assignee: Robert Malz (rmalz)
Status: In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036239
Title:
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Robert Malz (rmalz)
** Changed
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New =>
Hey @Christian,
1a) No need, AQ 0x000A returns NVM capabilities regardless of configuration
applied (it's done during driver init)
1b) That's the point, I noticed you upgraded to 4.3 which I currently don't
have access to and I wanted to verify capabilities on 4.3. NVM caps should be
similar on
@Robert,
first thanks a lot for pursuing this issue!
1) I certainly can provide the debugging info. May I ask if ...
a) the system in question would need to have an active LAG (LACP) for
this to be helpful? We did switch to active-backup on all our machines
due to this very issue.
b) this
@Christian,
Can you verify your device capabilities returned from 0x000A looking for SRIOV
lag?
I have attached a script "parse_aq_0xA.py" you need to load driver with
dyndbg=+p and replace a buffer in script.
Note: buffer has to come from CQ CMD: opcode 0x000A
Expected result:
(...)
resp cap:
Script to verify AQ 0x000A capabilities
** Attachment added: "parse_aq_0xA.py"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/+attachment/5736421/+files/parse_aq_0xA.py
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Description changed:
+ [Impact]
+ * Issue is causing transmit hang on E810 ports with bonding enabled.
+ * Based on the provided logs, TX hang can last for even a couple of
minutes, but in most scenarios, the network will be recovered after the ice
driver performs a PF reset
FWIW, we updated our NICs to 4.30 as they were individually purchased
and not part of pre-built servers and also have this issue.
So in essence the issue also exists with the latest firmware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Yeah, I knew about that 4.30 update in Intel website, but it is not present on
Dell tools yet and the customer did not want to void their warranty
(potentially), so I did not try it. That is something to keep in mind while we
debug it.
--
You received this bug notification because you are a
@Andre,
I successfully installed on the machines with NVMUpdate64 tool. That is
on HPE machines.
$ sudo ./nvmupdate64e
Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.39.56.8
Copyright(C) 2013 - 2023 Intel Corporation.
WARNING: To avoid damage to your device, do not stop the update or
@Bartosz
$ ethtool -i enp65s0f0 |grep firmware-version
firmware-version: 4.20 0x8001784b 22.0.9
This is the latest firmware supported by Dell. You will find 4.3
available on Intel website, but it is not available yet through dell
firmware tools.
--
You received this bug notification because
What is the cards firmware ?
$ ethtool -i |grep firmware-version
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036239
Title:
Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue
I have tried this (patches suggested in comment #40) and the problem
seems to have gone away. It may be too soon to say but my test scenario
(which never gave me a false negative before) finished without issues.
Of course this is not a 'fix', so I'm curious to see what the OP has to
say about
1) Andre, after I switched to active-backup the issue is gone (so far).
But yeah, we are looking for a reproducer as well. It's hard to narrow
down some random issue - also likely for Intel.
2) But I just received an email from an Intel developer with a suggested
change to the driver to narrow
Hi Christian
In my tests, I also saw the same issues with active-backup too.
Do you know a way to reproduce this issue? I'm having a hard time to
find a consistent reproducer, currently I need to deploy a complete
openstack, run a ser of load tests on it and eventually the problem
shows up, but
I ran into this issue on 22.04 LTS (using HWE kernel 6.2) on a 100G dual-port
E810 NIC.
Also with LACP only, active-backup works without issues.
To bring this more to the attention of the driver devs, I posted to the
intel-wired-lan ML: https://lists.osuosl.org/pipermail/intel-wired-
Removing lacp bonding (using just one interface without any kind of bonding)
seemed to help, I'm not seeing the issue anymore. Still testing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Disabling TSO on both legs of the bond in all hosts did not help. After 2h30min
working well, it happened again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036239
Title:
Intel
Got a suggestion to try disabling TSO which helped in similar cases (same queue
timeout error) in e1000e driver. Will report back soon.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://www.mail-
archive.com/e1000-de...@lists.sourceforge.net/msg12747.html
similar issue
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036239
Title:
Intel E810-XXV - NETDEV
I have not tested without the bond, but I believe this issue probably is not
directly related to the fact that the interface is bonded, which would mean
removing the bond will not help. While I will try to test this if possible
(depends on customer doing reconfiguration of switch side), I
I added logs from a machine that I'm not sure was affected (infra01),
adding more logs below for the one that is certainly affected
(cloud002).
** Description changed:
I'm having issues with an Intel E810-XXV card on a Dell server under Ubuntu
Jammy.
Details:
- hardware -->
** Tags added: apport-collected jammy uec-images
** Description changed:
I'm having issues with an Intel E810-XXV card on a Dell server under Ubuntu
Jammy.
Details:
- hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
Controller E810-XXV for SFP (rev 02)
This is the log from the HWE kernel:
[33219.508873] [ cut here ]
[33219.508877] NETDEV WATCHDOG: enp161s0f1 (ice): transmit queue 35 timed out
[33219.508932] WARNING: CPU: 48 PID: 0 at net/sched/sch_generic.c:525
dev_watchdog+0x21f/0x230
[33219.508940] Modules linked in:
60 matches
Mail list logo
