** Tags added: oem-priority originate-from-2071758 stella
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268
Title:
Phantom "Unknown Display" shown in Settings after installing the
Nvidia
Thanks for the bug report and the reproducer!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071756
Title:
dev test from ubuntu_stress_smoke_tests cause VM crash with
N-oem-6.10
To manage
Fix released and no other hints is using this bug. Closing this.
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953287
Title:
Hi Christian,
sorry for the late reply, I saw the following failure with Noble-lowlatency
6.8.0-36.36.1 AMR64 instances on openstack:
ERROR: test_0 (__main__.TestLogprof.test_0)
test 'ping'
--
Traceback (most recent call
This issue can be found with Oracular 6.10.0-4.4 AMD64 openstack
instance as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071756
Title:
dev test from ubuntu_stress_smoke_tests cause VM
This issue can be found with Oracular 6.10.0-4.4 AMD64 openstack
instance as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071776
Title:
pty07 from ubuntu_ltp cause VM crash with N-oem-6.10
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.10 (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.10 (Ubuntu
Public bug reported:
The pty07 test from ubuntu_ltp will cause test interrupt with Noble OEM
6.10 VM on openstack since 6.10.0-1003.3
This issue can be reproduced with a VM on a bare-metal. When this
happens the VM will be terminated. (Test passed on a Bare-metal with
6.10.0-1005-oem).
Test
The respined Xenial kernel 4.4.0-256.290 works fine with this test.
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Released
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: linux-oem-6.10 (Ubuntu)
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/2071756
Title:
dev test from ubuntu_stress_smoke_tests cause VM
** Summary changed:
- cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on amd64/ARM64
+ cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on amd64/ARM64 (TFAIL:
Could not offline cpuXX)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Issue reported by ubuntu_qrt_kernel_security test with N-oem-6.10
These two kernel configs are expected to be set to satisfy the test:
FAIL: test_260_config_PTI
(__main__.KernelSecurityConfigTest.test_260_config_PTI)
Ensure kernel page table isolation is set
Public bug reported:
This DKMS failed to build with Noble OEM 6.10.0-1005
Error! Bad return status for module build on kernel: 6.10.0-1005-oem (x86_64)
Consult /var/lib/dkms/lttng-modules/2.13.11/build/make.log for more
information.
dpkg: error processing package lttng-modules-dkms
Public bug reported:
This DKMS is required for ubuntu_sysdig_smoke_test.
Build log:
DKMS make.log for scap-0.15.1 for kernel 6.10.0-1005-oem (x86_64)
Thu Jun 27 04:29:18 UTC 2024
make: Entering directory '/usr/src/linux-headers-6.10.0-1005-oem'
warning: the compiler differs from the one used to
> Where can be such a "update request" placed?
As Ubuntu is a feature-freeze distribution, it won't accept new features
to the software archive after the freeze date.
However, there are still some ways of shipping such things to the users:
* If you have a direct/indirect contract with
Didn't see this issue anymore with 6.8.0-38.38.
** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: 6.8 arm64 noble sru-20240429 ubuntu-kselftests-ftrace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067291
Title:
ftrace:test.d--dynevent--add_remove_btfarg.tc in
It will need this set as well:
https://lore.kernel.org/stable/20240614065820.865974-1-po-hsu@canonical.com/T/#t
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067464
Title:
udpgro_fwd.sh /
Fix sent to stable 6.6
https://lore.kernel.org/stable/20240614065820.865974-1-po-hsu@canonical.com/T/#t
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069127
Title:
net:unicast_extensions.sh
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
: No such file or directory
# ./pmtu.sh: line 941: cleanup_all_ns: command not found
# ./pmtu.sh: line 536: setup_ns: command not found
# Error: argument "type" is wrong: Invalid "netns" value
** Changed in: ubuntu-kernel-tests
Assignee: Po-Hsu Lin (cypressyew) => (unassign
Public bug reported:
Issue found on Mantic 6.5.0-44.44 in cycle 2024.06.10
Running 'make run_tests -C net TEST_PROGS=unicast_extensions.sh
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
make: Entering directory
Attached is an annotated copy of my system log with the relevant update
from 107 to 112, the failed boots with 112, a successful boot with the
last good kernel 107, and a boot with 112 using the workaround. Search
for BOOT in capital letters to find the start of each boot. I hope this
might be
I am also affected by this bug. Booting to kernel 5.15.0-112 produces a
black screen. Kernel 5.15.0-107 works correctly. Here is information
about my system:
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version:
Found with jammy-lowlatency-hwe-64k 6.5.0-41.41.1~22.04.1 on node wright-kernel.
Failing with "Exceeded execution time, requesting exit" as well.
Maybe we need to extend the execution time.
** Tags added: 6.5 jammy sru-20240429
--
You received this bug notification because you are a member of
Hello Garcia,
thanks for add that patch, I can see that we're now using this 0.3 seconds
timeout now.
However we have found there are still some exceptions that will still fail with
this 0.3 seconds timeout:
* M-lowlatency-64k 6.5.0-41.41.1 openstack ARM64 instance
* M-lowlatency 6.5.0-41.41.1
*** This bug is a duplicate of bug 2067865 ***
https://bugs.launchpad.net/bugs/2067865
With Ike's help, I am now testing on doerfel with 5.4.0-186-generic.
And yes this issue can be reproduced with the command mentioned in #2, I
have also verified that the stress-ng update from upstream is
6.10.0-061000rc2-generic on Azure Standard_A2_v2 is OK.
** Description changed:
This issue can be found on:
* N-Azure-6.8.0-1008.8
* N-geneirc-6.8.0-35.35
* J-Azure-6.8.0-1008.8~22.04.1
With 100% reproduced rate on Azure Standard_A2_v2 instance, (reproduce
rate 100%), it can
** Description changed:
This issue can be found on:
- * N-Azure-6.8.0-1008.8
- * N-geneirc-6.8.0-35.35
- * J-Azure-6.8.0-1008.8~22.04.1
+ * N-Azure-6.8.0-1008.8
+ * N-geneirc-6.8.0-35.35
+ * J-Azure-6.8.0-1008.8~22.04.1
- With 100% reproduced rate on Standard_A2_v2 instance,
Hi Dann,
I would like to know how lone does it take to reproduce this issue? I am trying
to reproduce this with a ThunderX Cavium ARM64 box (wright-kernel). But I can't
trigger this panic with a 35 minutes test.
BTW We have found another af-alg test hang issue on that wright-kernel
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
** Changed in: linux (Ubuntu Oracular)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Masahiro Yamada
** Changed in: oem-priority
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about
Hints removed, closing this bug.
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2008085
Title:
net:veth.sh in
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: linux (Ubuntu)
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/2066332
Title:
net:fib_rule_tests.sh in ubuntu_kselftests_net fails on
Failed with -97 + test code from -106.
Failed with -94 + test code from -106.
Passed with -92 + test code from -106.
So it looks like this issue happens between -92 and -94.
We didn't catch this becuase scobee-kernel was added to the pool since
2024.04.01 cycle but at that time the
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
--
You received this bug notification because
** Description changed:
- Issue found on xilinx-ZCU102, xilinx-ZCU104 and xilinx-ZCU106 with
- 5.15.0-1029-xilinx-zynqmp
+ Issue found on xilinx-ZCU104 and xilinx-ZCU106 with 5.15.0-1029-xilinx-
+ zynqmp
$ sudo ./tls
TAP version 13
1..179
# Starting 179 tests from 6 test cases.
#
My bad not realizing that non-LTS versions are not maintained on salsa.
This is the debdiff for mantic.
** Patch added: "libfprint_1.94.6+tod1-0ubuntu3.1~testing1.debdiff"
Patch applied, failed test restarted.
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061107
Title:
shiftfs-lxd.sh in
LXD team got this issue resolved by pushing a version that supports ZFS
0.8 to 5.21/stable channel.
Please find the detailed comment in the discourse post above.
I have the MP updated.
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Chan
** Changed in: ubuntu-kernel-tests
Status: Confirmed => In Progress
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Focal)
Note that with LTP test suite update this test is not causing failure to
cgroup_fj_* anymore.
Now it's only failing on GCP g1-small instance. This test will take over
an hour (1h2m) which is slightly above our current threshold (120x,
actual timeout is 60m).
I think we can bump it to 150x (75m).
This issue can be found on openstack ARM64 instance with M/M-lowlatency
as well.
** Changed in: apparmor (Ubuntu)
Status: New => Fix Released
** Tags added: sru-20240401 sru-s20240304
** Tags added: ubuntu-qrt-apparmor
--
You received this bug notification because you are a member of
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Mantic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
LXD release note:
https://discourse.ubuntu.com/t/lxd-5-21-1-lts-has-been-released/43823/5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061107
Title:
shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test
Comment from Simon Déziel:
5.21 and later require ZFS 2.1 or later. This means if you are using Ubuntu
20.04, you need the HWE kernel.
So this failure is expected. We should either hint it or skip it from
the test.
** Changed in: lxd (Ubuntu)
Status: New => Invalid
--
You received this
I tried the same command with Focal 5.4.0-1089-gkeop in 2024.03.04
cycle, and it's failing with the same issue.
$ sudo lxc storage create zfs zfs size=2GiB
Error: Required tool 'zpool' is missing
$ uname -a
Linux f-lgkeop-gkeop-5-4-e2hcpu8-u-overlayfs-smk-test 5.4.0-1089-gkeop
#93-Ubuntu SMP Wed
Public bug reported:
Issue found in cycle 2024.04.01 with F-gkeop (5.4.0-1091.95), F-oracle
(5.4.0-1123.132)
Test log
Running 'sudo -iu ubuntu
/home/ubuntu/autotest/client/tmp/ubuntu_overlayfs_smoke_test/src/overlay-shiftfs-tests/tests/shiftfs-lxd.sh'
Error: Required tool 'zpool' is missing
With snapd 2.61.3 now in -update, this issue no longer appear.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this bug
** Description changed:
- This is a new test case, issue found on M/J/F/B when testing LTP update
- 20240312
+ [Impact]
+ The updated LTP has added proc_sched_rt01 testcase which can't pass
+ since several commits are missed from kernel side.
+
+ Test log:
+ INFO: Test start time: Tue Mar 12
** Changed in: linux (Ubuntu Focal)
Status: Won't Fix => Confirmed
** Changed in: linux (Ubuntu Jammy)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Milestone: noble-updates => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057734
Title:
proc_sched_rt01 from ubuntu_ltp failed
To manage notifications about
Hints removed. Closing this bug.
This issue cannot be found on J-azure, J-azure-fips, J-gcp-fips, J-mtk,
J-nvidia-tegra, J-xilinx.
We don't run this test on J-raspi, J-bluefield.
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
** Tags removed:
Tested on the machines with the said fingerprint hardware using the
following procedures:
1. Enable the -proposed channel
2. Install 1:1.94.3+tod1-0ubuntu2~22.04.07 version of libfprint-2-2, which is
the one in the -proposed channel
3. Reboot the machine
4. After the reboot, confirm that
** Tags added: mantic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1999589
Title:
net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x 5.19
/ J-hwe-6.5
To manage notifications about
This is affecting J-hwe-6.5 openstack s390x instances since
6.5.0-14.14~22.04.1
** Tags added: 6.5 jammy
** Tags added: sru-20240205 sru-20240304
** Summary changed:
- net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x Kinetic
+ net:tls in ubuntu_kernel_selftest fails sm4_*
** Tags added: originate-from-2058698
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this bug go to:
Installed the 2.0-1ubuntu4.7 version of firmware-sof-signed on the
previously failed HP platform. Confirmed that now the LEDs can toggle
accordingly.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member
** Tags added: originate-from-2058620
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this bug go to:
@mschiu77 the firmware-sof provided in your PPA works! The LEDs can
toggle accordingly after installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049569
Title:
Enable the mic-mute led on
** Tags added: originate-from-2058002
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this bug go to:
The firmware-sof-signed in -proposed doesn't seem to fix the LEDs at
least on one HP platform. Reading the file from /sys/class/sound/ctl-
led/mic/card0/list shows nothing.
The md5sum of sof-ace-tplg/sof-hda-generic-2ch.tplg also doesn't match
the one in upstream v2023.12.1 release.
# From
Hints removed, closing this bug.
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886790
Title:
lxc 3.0.3-0ubuntu1~18.04.1 ADT
Public bug reported:
[Impact]
LEDs on both mute and mic-mute key are not working on a HP platform.
[Fix]
The quirk in the commit b2d6a1fd0e3e513f5ebfc152d6fedae093df8e21 (ALSA:
hda/realtek: Add quirks for HP G11 Laptops using CS35L56) in linux-next can
make it work.
[Test]
1. Install the
Salsa MP: https://salsa.debian.org/ubuntu-dev-
team/libfprint/-/merge_requests/14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058193
Title:
Support Synaptics fingerprint device with ID
` and enable `Fingerprint Login`
* Enroll finger and then logout
* Login system with enrolled finger
[Where problems could occur]
* If the vendor uses the same ID for other devices, the new device may
not work properly.
** Affects: oem-priority
Importance: Critical
Assignee: Leo Lin
** Tags added: originate-from-2057727
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this bug go to:
** Tags added: originate-from-2057476 somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this bug go to:
** Tags added: oem-priority originate-from-2057436 stella
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this bug go to:
** Attachment added: "oemlogs-ubuntu-20240313104942+0800.apport.gz"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2057491/+attachment/5755407/+files/oemlogs-ubuntu-20240313104942+0800.apport.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Currently in /lib/systemd/system/smokeping.service:
```
After=network.target
```
But smokeping requires network is actually up to query hostname via DNS.
A better improvement is:
```
After=network-online.target
Wants=network-online.target
```
Reference:
Public bug reported:
Running the debsums over snapd:
$ debsums snapd
will show the file io.snapcraft.Prompt.service missing:
debsums: missing file
/usr/share/dbus-1/services/io.snapcraft.Prompt.service (from snapd
package)
The snapd versions:
$ snap version
snap2.61.2
Verified that the GAP/CONN/CPUP/BV-05-C could pass on 5.15.0-102.112
kernel using the following procedure:
1. On PTS, switch to the LE-only dongle
2. On the IUT, run bluetoothctl
3. On PTS, start the test case.
4. On the IUT, in the bluetoothctl shell, start scanning by entering "scan on".
5.
Public bug reported:
Our ADT test for virtualbox-hwe DKMS failed on F-aws ARM64
Based on our hint database we can see this failure at least since
5.4.0-1072.77 from commit 9333a4a0 [1]
Test failed when trying to build the DKMS:
Loading new virtualbox-guest-6.1.50 DKMS files...
Building for
** Merge proposal unlinked:
https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/461647
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881643
Title:
pmtu.sh net selftest fail
** Merge proposal unlinked:
https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/461647
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055483
Title:
net:pmtu.sh
Public bug reported:
E:can not open
/var/lib/apt/lists/ppa.launchpadcontent.net_cappelikan_ppa_ubuntu_dists_jammy_InRelease
- fopen (13: Permission denied), E:The package lists or status file
could not be parsed or opened.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: update-manager
** Description changed:
- net:pmtu.sh fails on openstack cpu2 lowlatency-64k
+ net:pmtu.sh fails on openstack cpu2 M-lowlatency-64k
ubuntu_kselftests_net. It fails with:
DEBUG| [stdout] # TEST: IPv4, bridged geneve6: PMTU exceptions
[FAIL]
DEBUG| [stdout] # File
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Tags added: 6.5 arm64 mantic sru-20240205 ubuntu-kselftests-net
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal unlinked:
https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/461647
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881643
Title:
pmtu.sh net selftest fail
** Merge proposal unlinked:
https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/461647
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055483
Title:
net:pmtu.sh
** Description changed:
+ Issue found on J-gcp-6.5.0-1015.15~22.04.1 and M-gcp-6.5.0-1015.15 in
+ cycle sru-20240205
+
+ And can be reproduced with generic kernel on GCP cloud.
+
+ This is not a regression but something emerges after the pmtu.sh result
+ parsing logic update, which landed via
** Summary changed:
- mtu.sh net selftest fail with PMTU exception wasn't created after exceeding
MTU
+ pmtu.sh net selftest fail with PMTU exception wasn't created after exceeding
MTU
** Tags added: 6.5 mantic sru-20240108 ubuntu-kselftests-net
** Tags removed: sru-20240108
** Tags added:
** Changed in: oem-priority
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049838
Title:
Mute/mic LEDs no function on HP ZBook
To manage notifications
Hello,
thanks for the bug report,
I have built some test kernels with this patch:
https://people.canonical.com/~phlin/kernel/lp-1967493-pl2303/
Can you give them a try? Thank you.
The kernel version for F-5.13 should be:
5.13.0-47-generic #52~20.04.1+lp1967493
Thanks.
--
You received this
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Incomplete
--
You received this bug notification
** Package changed: linux-signed-hwe-5.13 (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967493
Title:
pl2303 serial adapter not recognized
To manage notifications about
I got some more accessories to try yesterday, turns out the problem is related
to micro usb to usb type-A/tupe-C adapter, only one of the five I tried worked
both in armhf and arm64 images.
With that one, everything looks fine now.
--
You received this bug notification because you are a member
Found on node vought with F-OEM 5.14.0-1040.44
** Tags added: 5.14 focal oem sru-20220509
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959215
Title:
unshare test in ubuntu_stress_smoke_tests
This issue does not exist in mainline 5.16-rc1 [1] but exist in 5.15
[1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.16-rc1/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969624
Title:
** Description changed:
[Impact]
test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests
will fail on 5.13 kernel with:
# selftests: net: test_vxlan_under_vrf.sh
# Checking HV connectivity [ OK ]
# Check VM connectivity through VXLAN (underlay in the default
https://lists.ubuntu.com/archives/kernel-team/2022-May/130739.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975691
Title:
Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
** Description changed:
[Impact]
- test_vxlan_under_vrf.sh should not be failing anymore (unless it's a
- kernel config related issue) with patches submitted for fixing this
- test in bug 1871015.
+ test_vxlan_under_vrf.sh should not be failing anymore with patches
+ submitted to fix it in bug
Public bug reported:
UBUNTU RELEASE
Ubuntu 22.04 LTS (Kubuntu but I think that's irrelevant)
PACKAGES AND VERSIONS
libsdl2-dev 2.0.20+dfsg-2build1
libsdl2-2.0-0 2.0.20+dfsg-2build1
STEPS TO REPRODUCE
(This is how I discovered the issue, but there is probably a much more minimal
reproduction
** Description changed:
[Impact]
- test_vxlan_under_vrf.sh should not be failing anymore (except if it's a
config related issue) with patches submitted for I-5.13 / F-oem-5.14 in bug
1871015
+ test_vxlan_under_vrf.sh should not be failing anymore (unless it's a
+ kernel config related issue)
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Kinetic)
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.14 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu Kinetic)
Just realized that Focal need this patch as well.
** Changed in: linux (Ubuntu Focal)
Status: Fix Released => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
--
You received this bug notification because you are a member of
** Summary changed:
- Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of
ubuntu_kernel_selftests
+ Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
ubuntu_kernel_selftests
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
1 - 100 of 13813 matches
Mail list logo
