Another data point here:
kernel: [5150033.094216] kernel BUG at lib/string.c:1149!
kernel: [5150033.094224] invalid opcode: [#1] SMP NOPTI
kernel: [5150033.094229] CPU: 1 PID: 2940890 Comm: mount.ocfs2 Tainted: P
OE 5.13.12-051312-generic #202108181219-Ubuntu
kernel: [5150033.0
After a reboot of the whole fabric (switches and machines), this problem
has not resurfaced. Conceivably this could have been a transient error
state, so I will close this with "invalid".
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification beca
** Changed in: linux (Ubuntu)
Status: New => 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/1898057
Title:
Infiniband transmit queue timeouts after upgrading to linux-hw
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1898057/+attachment/5416159/+files/WifiSyslog.txt
** Description changed:
After upgrading 3 servers from linux-image-5.3.0-40-generic to linux-
image-5.4.0-48-generic I have started seeing the follow
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1898057/+attachment/5416152/+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/1898057
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1898057/+attachment/5416157/+files/ProcModules.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/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1898057/+attachment/5416154/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1898057/+attachment/5416151/+files/CurrentDmesg.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
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1898057/+attachment/5416158/+files/UdevDb.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/1898057
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1898057/+attachment/5416155/+files/ProcEnviron.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/b
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1898057/+attachment/5416153/+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/1898057
apport information
** Package changed: linux-hwe-5.4 (Ubuntu) => linux (Ubuntu)
** Tags added: apport-collected bionic
** Description changed:
After upgrading 3 servers from linux-image-5.3.0-40-generic to linux-
image-5.4.0-48-generic I have started seeing the following queue
timeouts fr
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1898057/+attachment/5416156/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
# apt update
[...]
# apt install linux-image-4.10.0-23-generic
N: Unable to locate package linux-image-4.10.0-23-generic
(yes I know it is in proposed)
However, 4.10.0-24 does exist and gets installed with -edge. And it is
known broken. Why push it out at all? Am I wrong to assume that a later
nu
The MTU problem affecting OpenvSwitch bridges still exists (or
resurfaced) in linux-generic-hwe-16.04-edge (4.10.0.24.17).
# grep -i mtu /var/log/syslog
[...] br-int: Invalid MTU 9000 requested, hw max 1500
[...] lxcbr0: Invalid MTU 9000 requested, hw max 1500
Pretty please STOP BREAKING things.
Ok, so the fix is rather trivial. I've verified that building 4.10.0-22
kernel from Ubuntu sources with the following patch fixes the
OpenvSwitch MTU issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/openvswitch
/vport-internal_dev.c?id=425df17ce3a26d98f76e2b6b0a
4.10 series (hwe-edge) kernel doesn't seem to have gotten these fixes
yet, as 4.10.0-22-generic #24~16.04.1-Ubuntu still fails to set
openvswitch MTU correctly. When can we expect a fix to be released for
-edge?
--
You received this bug notification because you are a member of Kernel
Packages, wh
17 matches
Mail list logo
