[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
All autopkgtests for the newly accepted linux-meta-aws (5.15.0.1032.31) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
dm-writeboost/2.2.13-1ubuntu2 (amd64, arm64)
systemd/249.11-0ubuntu3.7 (arm64)
This bug is awaiting verification that the linux-
hwe-5.4/5.4.0-145.162~18.04.1 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-bionic' to
'verification-done-bionic'. If the problem
It's the kernel driver itself: mt7921
It's missing BLE support for this device.
On Windows BLE is working.
I really don't know witch one is the driver for bluetooth function for this
device, because it's Wi-fi + BT 5.2 combo. Found in AMD Wi-Fi 6E RZ608
(MediaTek MT7921K)
In this MB: X570S
You have been subscribed to a public bug:
Hi,
i have MT7921K BT chip that BLE function is not working with linux, but normal
BT is working.
I try several distros and some live-iso and get same effect. BLE just not
working with this device.
I have other BT adapters and BLE is working for them.
To proceed with this SRU, I would like to have some analysis of what
makes this an armhf-only failure. Is it to do with the fact that armhf
autopkgtests run in a container and others do not? If so, it seems to
me that a more correct fix for the test is to detect that we're running
in a container
All autopkgtests for the newly accepted linux-meta-gke (5.15.0.1029.28) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-gke/5.15.0-1029.34 (amd64, arm64)
lttng-modules/2.13.1-1ubuntu0.22.04.3 (amd64, arm64)
Please visit the
** Description changed:
- [Impact]
- Adding this patch addresses a specific audio issue with the nvidia-tegra
kernel.
+ [Impact]
+ Adding this patch addresses USB and PWM cooling fan issues as described
in the following bugs:
- https://bugs.launchpad.net/riverside/+bug/2009867
-
If that (not being able to use the new desktop installer with bcmwl) is
the case then we should document this in the release notes for Lunar
Lobster.
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
All autopkgtests for the newly accepted linux-meta-gkeop (5.15.0.1017.16) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
lttng-modules/2.13.1-1ubuntu0.22.04.3 (amd64)
Please visit the excuses page listed below and investigate
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.15.0-1032.36+1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-meta-nvidia (5.15.0.1018.18) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-nvidia/5.15.0-1018.18 (amd64)
Please visit the excuses page listed below and investigate the
Public bug reported:
[Impact]
Adding this patch addresses a specific audio issue with the nvidia-tegra
kernel.
https://bugs.launchpad.net/riverside/+bug/2009867
https://bugs.launchpad.net/riverside/+bug/2002173
[Fix]
The PR is made up of a revert of one commit and the
Kernel logging shows that the vmwgfx driver encounters an error when
loading. The error indicates that a memory range could not be acquired
by the driver. The error is eerily similar to
https://bugzilla.kernel.org/show_bug.cgi?id=215678 which was fixed in
kernel source in 5.19.
The behavior seen
All autopkgtests for the newly accepted linux-meta-aws (5.15.0.1032.30) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
lttng-modules/2.13.1-1ubuntu0.22.04.3 (amd64, arm64)
Please visit the excuses page listed below and
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.15.0-1032.36) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.15.0-1032.36) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page
** Description changed:
+ [Impact]
+
+ CONFIG_SERIAL_8250_MID=y is required to properly use the serial console
+ on some platforms that are using the "mid" serial driver (such as some
+ Intel SoC platforms).
+
+ The generic kernel should build this driver statically to make sure we
+ properly
** Also affects: linux (Ubuntu Lunar)
Importance: Critical
Status: 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/2009355
Title:
linux-libc-dev is no longer
I have validated this fix for kinetic:linux-kvm - from proposed:
# selftests: net: fib_nexthop_nongw.sh
# TEST: nexthop: get route with nexthop without gw[ OK ]
# TEST: nexthop: ping through nexthop without gw [ OK ]
ok 1 selftests: net:
I've applied this change to lunar. Next lunar 6.2 kernel will have
CONFIG_SERIAL_8250_MID=y.
--
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/2009283
Title:
linux:
It looks like this problem has been introduce by this commit:
a5ddd0de7d8b ("UBUNTU: [Packaging] install headers to debian/linux-libc-
dev directly")
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/lunar/commit/?id=a5ddd0de7d8b2159fc5f8df55527e0e447328953
It seems to include
This bug is awaiting verification that the linux-gke/5.15.0-1029.34
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-gkeop/5.15.0-1017.22
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
All autopkgtests for the newly accepted linux-restricted-modules-nvidia
(5.15.0-1018.18) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page
** Package changed: ubuntu => linux-signed-hwe-5.15 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2009963
Title:
Ubuntu 20.04.5 Touchpad not recognized with
The work-around identified in comment #9 can be used to bypass this. It
delays further services from starting up an attempting to interact with
the mlnx cards which appears to cause kernel hung tasks due to the
kernel hung task timeout of 120 seconds. I'm not convinced at this
moment in time that
You have been subscribed to a public bug:
I updated Ubuntu on my Lenovo Thinkpad P1 to 20.04.5 and suddenly, by
touchpad does not work anymore. The hardware is fine. I can use it when
running Windows 11 on my laptop. But when I run "cat
/proc/bus/input/devices" or "xinput list" I do not see any
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.
seems to be a nouveau issue , please install nvidia official drivers
from ubuntu repos and blacklist nouveau driver at boot
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1939966
** Description changed:
+ [Impact]
+
Kerberized NFS mounts stopped working on Raspberry Pi starting with Ubuntu
21.10. In 22.10 the issue still exists.
The reason is that the kernel module rpcsec_gss_krb5 which is needed for
establishing a kerberos protected NFS connection to the server
However, it will probably take some time to resolve bug 1988018 so we
should probably look into what interim solutions the charm could provide
until we get there.
** Changed in: charm-ovn-chassis
Status: New => Triaged
** Changed in: charm-ovn-chassis
Importance: Undecided => High
--
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This was fixed during the regular rebase with upstream. We can close
this one now.
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member
** Changed in: linux-firmware (Ubuntu Kinetic)
Status: Incomplete => Confirmed
** Description changed:
+ [Impact]
+
Intel has been adding support for Wi-Fi 6E (6GHz band) to additional
countries as they get regulatory approval.
With the base install of Ubuntu 22.10, I do not
I also found this:
To use a serial port as console you need to compile the support into
your kernel - by default it is not compiled in. For PC style serial
ports it’s the config option next to menu option:
Character devices ‣ Serial drivers ‣ 8250/16550 and compatible serial
support ‣ Console on
Hello Dimitri!
Unfortunately, if it's not built-in we have no console and system cannot
be installed. Same change was made on debian years ago to solve the
same problem, as you can see at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368
https://salsa.debian.org/kernel-
Screen flickering/ tear bug filed in
https://bugs.launchpad.net/ubuntu/+source/linux-meta-
oem-6.1/+bug/2009952.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2007718
Title:
** 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/2009283
Title:
linux: CONFIG_SERIAL_8250_MID=y
Status in linux
Public bug reported:
After upgrading from kernel 5.19.0-35-generic to 6.1.0-1007-oem there is
occasional screen flicker/ tear. It happens around every minute; it
seems connected to window/ pointer movement, but I have no clear way of
reproducing. Disruption is minor, but annoying.
I'm running
I understand that having it in the root filesystem is too late.
However, I would have thought it would be good enough to have it early
in the initrd, or do you also require output prior to initrd starting?
having it built-in trades wasting RAM for all billions of Ubuntu
instances, and the module
Why the importance of that bug has not been set yet?
This is a very serious issue because I cannot lock my screen at all if I need
to walk away from the laptop as this will trigger the bug.
Every time I must put the laptop to sleep.
--
You received this bug notification because you are a member
** Description changed:
[SRU Justification]
== Impact ==
See original description. The goal is to adjust the behavior of the balanced
governor for certain Xeon CPUs (those are CPUs rather seen in servers so there
should be no impact on laptop users). While the initial request was
Excellent work on finding more information about the cause and a
workaround, thank you for that!
I think it would be appropriate to tackle this as part of the resolution
of netplan.io bug 1988018 though, so the charm task would still be
invalid unfortunately.
--
You received this bug
@Pragyansri, if you could point out one of the test loads usable to
check the difference we would have it documented here. Right now not
sure whether we have access to a Sapphire Rapids directly. But best to
have all details in one place.
--
You received this bug notification because you are a
** Description changed:
+ [SRU Justification]
+
+ == Impact ==
+ See original description. The goal is to adjust the behavior of the balanced
governor for certain Xeon CPUs (those are CPUs rather seen in servers so there
should be no impact on laptop users). While the initial request was
After more investigations, I've found the root cause that triggers the
issue.
#
# The TL,DR:
#
With many VFs to initialise, systemd-networkd-wait-online.service's timeout of
2 minutes is reached.
Meaning services like Nova, Neutron and OVN/OVS will start while the kernel is
still creating and
#
# The tested workaround
#
Current workaround on ovn-chassis with is to override
systemd-networkd-wait-online.service to extend the timeout, here to 4 minutes :
(The 2 lines of ExecStart are mandatory, this is not a typo)
```
juju run --model openstack --app ovn-chassis \
"sudo mkdir
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Lunar)
Status:
** Tags added: sru-20230227
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1837543
Title:
crypto_user02 in crypto from ubuntu_ltp failed
Status in ubuntu-kernel-tests:
Triaged
The requested change is now upstream (v6.3-rc1) as
commit 60675225ebeecea248035fd3a0efc82ae9038a98
Author: Srinivas Pandruvada
Date: Tue Feb 21 22:45:26 2023 -0800
cpufreq: intel_pstate: Adjust balance_performance EPP for Sapphire
Rapids
** Also affects: linux (Ubuntu Jammy)
I didn't see this udpgso_bench.sh test failed with "./udpgso_bench_tx:
sendmsg: Connection refused" on Kinetic.
A side note there is a similar issue in net:udpgro_fwd.sh test with
specific combinations:
* J-lowlatency 5.15.0-68.75 with node rizzo
* K-ibm 5.19.0-1019.21 with node onibi
Maybe we
60 matches
Mail list logo
