> Hi, we still encounter this error in the latest 4.4.0 kernel.
yes, unfortunately, the last patch seems to have helped reduce the
frequency, but i did recently get another report of it happening again.
So it seems to not be completely fixed.
To clarify, as I said before, this is an event generat
Hi, we still encounter this error in the latest 4.4.0 kernel. Our kernel
version is
```
$ uname -r
4.4.0-122
$ dpkg -l|grep linux-image-4.4.0-122-generic
ii linux-image-4.4.0-122-generic 4.4.0-122.146
amd64Linux kernel image for version 4.4.0 on 64 bit
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) // CVE-
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) // CVE-
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
This bug was fixed in the package linux - 4.4.0-121.145
---
linux (4.4.0-121.145) xenial; urgency=medium
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
Due to the nature of this bug, being very difficult to reproduce, real
verification could take weeks instead of only days. However, one reporter has
been running with a test kernel I built here
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1723127
which is the base 4.4.0-112 kernel plus the
This bug is awaiting verification that the 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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the 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-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verifica
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Description changed:
+ [impact]
+
+ The i40e driver sometimes causes a "malicious device" event that the
+ firmware detects, which causes the firmware to reset the nic, causing an
+ interruption in the network connection - which can cause further
+ problems, e.g. if the interface is in a bond;
As mentioned, upstream commit 248de22e638f10bd5bfc7624a357f940f66ba137
("i40e/i40evf: Account for frags split over multiple descriptors in
check linearize") appears to finally fix this. This commit is already
included in bionic, but is required in artful and earlier.
In xenial, the commit 5c4654d
Hello,
can anyone still experiencing this on the 4.4 kernel please test with the
kernel from this PPA:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1723127
Test kernel version is 4.4.0-112.135+hf1723127v20180206b2
If anyone would like to test with the 4.13 kernel please let me know and I c
Hi there. I can confirm this problem still exists in newest kernels and
with the latest intel drivers as of today:
Jan 19 16:05:19 osd9 kernel: [511271.581413] i40e :02:00.1: TX driver issue
detected, PF reset issued
Jan 19 16:09:08 osd9 kernel: [511500.919380] i40e :02:00.0: TX driver is
Sorry for the delay, I've not forgotten about this, just been swamped
with other things. Will hopefully have time to do the tests next week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723127
Title
> I'd say we go with option #2. Please provide information on how to proceed,
> and how to
> undo any changes we test :)
ok, so first, these instructions may cause the card to hang; the system
may need to be rebooted or the driver reloaded. The changes here can be
undone by resetting the card; r
No worries, we're not in a hurry.
I'd say we go with option #2. Please provide information on how to
proceed, and how to undo any changes we test :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17231
Sorry for the delay.
So we have 2 options on how to continue debugging here:
1. we can try a traditional git bisect. This would involve testing
various kernel builds, to try to eventually narrow down the issue to
being fixed by a specific commit. It's a long-ish process, depending on
how long t
kernel v4.10, (4.10.0-041000-generic) has been running fine, without any
issues since 24 hours. I'd say it's OK, as you suspected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723127
Title:
Intel
> one bug at a time, please.
Absolutely! I just mentioned the "GRO implementation" because I wondered
if it might have been related. I should have googled up better on it
beforehand, that would have enlightened me that it wasn't.
I've tested the v4.4-wily kernel in the first link
(4.4.0-040400-ge
> How do we proceed? :-)
one bug at a time, please. As this NIC's "MDD" behavior doesn't
indicate what happened that it disliked, I can't tell if that is related
or not to the MDD events, but I suspect not, especially if you have not
seen that happen for kernels when you did get MDD events.
sinc
As of now, we've been running HWE 4.10 for little more than 16 hours and
no problems so far. Previously we'd hit the problem within the hour.
There is however one new logmessage that we haven't seen before, neither
with 1.4.x driver or 2.0.x. But it might be unrelated, we can't see any
particular
> We'll test the regular hwe 4.10 also if you think that narrows the
bisect.
yes please it will help to look just between 4.4 and 4.10. thanks!
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Chan
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723127
Title:
Intel i40e PF reset due to incorrect MDD detection (co
We've been using hwe-edge 4.11 for almost 24 hours without problems.
We'll test the regular hwe 4.10 also if you think that narrows the
bisect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723127
Ti
continuing conversation from previous (fix released) bug.
@bjozet, it would help a lot of you could test with the hwe 4.10 kernel
and let me know if that fails also, or if it seems to be fixed there.
If it works, I can review the changes and possibly find something,
and/or work with you on a bisec
26 matches
Mail list logo
