Hi,
Not sure this is useful (since it might be obvious), but adding `nopti` to
kernel parameters works around the issue, indicating this is indeed related to
kpti.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi, Dann,
Thanks for looking into this!
One more thing: we blacklisted the module "vhost_net", and that bypasses the
issue.
I know it's not the right direction for finding a fix, but maybe it helps with
the debug.
--
You received this bug notification because you are a member of Kernel
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1674837
Title:
thunder nic: RX_PACKET_DIS fix regression with Extreme
Hi, Dann,
I created a new bug and pasted the same info as above at [1].
Afaict, there is no useful information in the logs when link training fails.
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674837
--
You received this bug notification because you are a member of Kernel
Let me know if I should attach any logs, although there are *no* traces
anywhere, at least with default log levels (without recompiling).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Upstream backport [3] introduced a regression with ThunderX nodes (CRB-1S,
CRB-2S) and our 10G switch (Extreme Networks x670 10GE L3).
We have opened a downstream bug report [1], where we temporarily bypassed this
by pinning the kernel to 4.4.0-45.
I also tested 4.8
Hi, Dann,
First of all, I think the bug title is misleading, as this issue happens on all
kernels we tested (4.4.0-45..66, 4.8.0-x, 4.10.0-x etc).
To be fair, we haven't this exact bug (or at least I don't think we did)
in practice, i.e. without running stress-ng, 4.4.0-x never ever crashed.
Hi,
1) We tested different models (CRB-1S, CRB-2S) - all behave the same.
2) Please check the logs "ThunderX 4.11-rc1 console log" in [2] linked above. I
don't think firmware version makes a difference for this issue (we saw the same
bug with firmwares: T22, T27, T31).
All in all, this issue
Hi,
This fix introduced a regression with ThunderX nodes (CRB-1S, CRB-2S) and our
10G switch (Extreme Networks x670 10GE L3).
We have opened a downstream bug report [1], where we temporarily bypassed this
by pinning the kernel to 4.4.0-45.
I also tested 4.8 (multiple builds), 4.10 and 4.11-rc1
4.11-rc1 console log attached.
Board firmware is latest available on Gigabyte's site (T31).
1. Install 4.11-rc1 (`make modules_install install`) and reboot
2. Observe networking driver issues in boot log
Dmesg: 4.11-rc1_dmesg_on_clean_boot.log [3]
3. Try `ping google.com`, obviously not
Hi,
I tried out 4.11-rc1 a few days ago. Unfortunately, I did not get the board to
boot properly from the start, since ThunderX networking drivers failed to
allocate MSI-X/MSI interrupts, and polling on some registers also failed ...
So, with 4.11-rc1, at least one networking interfaces was
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1672521/+attachment/4837215/+files/Lspci.txt
--
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/1672521
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1672521/+attachment/4837217/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1672521/+attachment/4837221/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1672521/+attachment/4837216/+files/Lsusb.txt
--
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/1672521
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1672521/+attachment/4837220/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1672521/+attachment/4837213/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1672521/+attachment/4837214/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1672521/+attachment/4837219/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1672521/+attachment/4837218/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected xenial
** Description changed:
I have been trying to easily reproduce this for days.
We initially observed it in OPNFV Armband, when we tried to upgrade our
Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8).
In
Public bug reported:
I have been trying to easily reproduce this for days.
We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu
Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8).
In our environment, this was easily triggered on compute nodes, when
22 matches
Mail list logo