This issue seems to be fixed with 5.19.0-40 this cycle (sru-20230320)
--
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/2000778
Title:
pmtu.sh in net from ubunut_kernel_selftests crash SUT
Checked with K-5.19, K-lowlatency-5.19, J-hwe-5.19 and J-hwe-
lowlatency-5.19. This issue does not exist anymore, therefore I am
closing this bug.
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete => Fix Released
I just noticed that we have this hint for Lunar as well, I will revert
the bug status to incomplete to verify it.
** Changed in: ubuntu-kernel-tests
Status: Fix Released => Incomplete
** Changed in: linux (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification
I can confirm that this issue does not exist in L / L-lowlatency.
Hints removed.
** Changed in: ubuntu-kernel-tests
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of
looks like a similar stack trace found here
https://www.spinics.net/lists/kernel/msg4555769.html
--
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/2000778
Title:
pmtu.sh in net from ubunut_
Still failing on baltar.ppc64el.9 during 2023.02.27 sru cycle. The
kuzzle and scobee (another arm64 server) passed.
** Tags added: sru-20230227
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
kuzzle and scobee are actually failing with 64k generic and 64k
lowlatency.
The only ARM64 box that can pass with 64k is ARM64 node starmie-kernel.
Others like dazzle, kuzzle, helo-kernel, kopter-kernel, scobee-kernel
are all failing with 64k. I wonder why we're having this difference.
--
You re
I could not reproduce this on baltar or kopter-kernel just by running
the kernel net selftest suite a few weeks ago, and no one else seems to
be experiencing similar problems that I can find.
I suspect there is some configuration of the vrfs from previous
tests/runs that might be influencing this
8 matches
Mail list logo
