Public bug reported:
With below commit in 5.16 upstream kernel, support for
mdev_set_iommu_device() kABI was removed from kernel as there were no
in-tree drivers making use of the kABI.
fda49d97f2c4 ("vfio: remove the unused mdev iommu hook")
This kABI is used by SRIOV based Nvidia vGPU on Ubunt
Public bug reported:
[Impact]
Packets sent by userland apps are rejected/dropped if the source address
is not specified and the corresponding route is using a connected
nexthop object.
This bug exists since linux v5.3 and has been fixed in v5.19 by the following
upstream commits:
- 747c1430721
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1988809
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Since kernel 5.19 is now released to Ubuntu 22.10, this bug is Fix
Released. But as mentioned in comment #87, we cannot fix Ubuntu 22.04
without further investigation done by those experiencing the bug.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ WiFi interfaces unsolicitedly down at resuming from s2idle.
+
+ [Fix]
+
Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN
POR is only for Windows project design. Please remove or disable
CONFIG_IWLMEI fro
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: hwe-next
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net
SRU: https://lists.ubuntu.com/archives/kernel-
team/2022-September/133010.html (oem-5.17/oem-6.0/kinetic/unstable)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1987312
Title:
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1861634
Title:
Dell XPS 9575 after resume from sleep/suspend, th
Thank you for your support.
I will take a look at drm-tip kernels. I wish they were available
through the Mainline application, it would make it much easier to
install.
I guess I'll need to wait for the fix in the kernel anyway.
Cheers!
--
You received this bug notification because you are a m
Public bug reported:
The steps:
* Going to settings -> Bluetooth
* Turn Bluetooth on. Seems to stay on, but can't connect anything to it
* Go to another place in Settings, go back to Bluetooth
* Result: Bluetooth is turned off
Thank you!
Alex
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package
Being machine-specific means this is almost certainly a kernel bug.
** Summary changed:
- Cannot turn Bluetooth on in Ubuntu 22.04.01
+ [ASUS ROG Flow X13] Cannot turn Bluetooth on in Ubuntu 22.04.01
** Package changed: bluez (Ubuntu) => linux (Ubuntu)
** Summary changed:
- [ASUS ROG Flow X13]
debdiff for Jammy (version 9858-0ubuntu6+22.04.1) and Kinetic
(9904-0ubuntu2). Need sponsoring.
** Attachment added: "backport-iwlwifi-dkms_9904-0ubuntu2.debdiff"
https://bugs.launchpad.net/bugs/1987312/+attachment/5613999/+files/backport-iwlwifi-dkms_9904-0ubuntu2.debdiff
** Attachment adde
This change was made by a bot.
** 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/1988825
Title:
[mt7921e] Cannot turn Bluetoot
SRU: https://lists.ubuntu.com/archives/kernel-
team/2022-September/133014.html (kernel-versions)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1987312
Title:
IWLMEI may cause d
Public bug reported:
[Impact]
* it is desired to have intel_iommu=on by default
* However this is causing many gpu bugs which are resolvable with igfx_off
parameter
* there is no Kconfig that can have intel_iommu=igfx_off behaviour
* introduce intel_iommu=igfx_on kernel command line
* intro
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1988831
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Summary changed:
- Allow configuring kernel with igfx_off by default, with userspace override
igfx_on
+ Allow configuring kernel with iommu=igfx_off by default, with cmdline
optional override to igfx_on
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
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/1988831
Title:
Allow configuring kernel with iommu=igfx_off by default,
Public bug reported:
The 515 series introduced open kernel modules for the NVIDIA driver.
They come with an open source licence, and should be provided as an
option for datacenter GPUs:
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-
kernel-modules/
** Affects: nvidia-graphics
Public bug reported:
On kinetic pi server daily images with the 5.19 linux-raspi kernel (e.g.
from http://cdimage.ubuntu.com/ubuntu-server/daily-
preinstalled/current/) there is no console output over HDMI. The
"rainbow" boot screen appears as usual, but then remains while the
system continues to
linux-generic 5.19.0.15.15 landed in kinetic
hence updating to Fix Released.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
linux-generic 5.19.0.15.15 landed in kinetic
hence updating to Fix Released.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
This bug was fixed in the package backport-iwlwifi-dkms - 9904-0ubuntu2
---
backport-iwlwifi-dkms (9904-0ubuntu2) kinetic; urgency=low
[ You-Sheng Yang ]
* Disable IWLMEI (LP: #1987312)
-- You-Sheng Yang Wed, 24 Aug 2022 21:39:38 +0800
** Changed in: backport-iwlwifi-dkms (Ub
The fix is here:
https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/log/?h=pci/pm
I'll do the backport once it's included in linux-next.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
You received this bug notification because you are a
Thanks, please give this kernel a try:
https://people.canonical.com/~khfeng/lp1988346/
--
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/1988346
Title:
cm32181 module error blocking suspen
After putting nvidia.NVreg_PreserveVideoMemoryAllocations=0 in the
kernel command line I don't remember any black screens after wake from
suspend. They certainly haven't happened in Ubuntu 22.04. The computer
is always usable immediately after waking.
However, I have gotten lockups some time later
Applied to:
- kinetic/linux:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next&id=04f71532747e18d2f7cb57f0d3cb66f6c00f3b24
- linux-unstable:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/unstable/commit/?id=b7efb6d15dea641b6944b
You have been subscribed to a public bug:
1) The release of Ubuntu you are using, via 'lsb_release -rd'
# lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04
2) The version of the package you are using, via 'apt-cache policy
pkgname'
# apt-cache policy
linux-headers-5.19.5
I upgraded from 20.04.2 to 22.04.1 over the weekend using the normal do-
release-upgrade process I've always used. Since then I notice Firefox
takes 30ish seconds to load. Telegram same. Libreoffice literally 3
minutes to open.
I've tried some of the suggestions in this ticket and the issue remain
** Package changed: ubuntu => linux (Ubuntu)
--
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/1988605
Title:
linux-tools and linux-cloud-tools for ppa mainline kernels
Status in linux pac
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1988605
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Hm, don't you still need kexec-tools installed to reboot with kexec via
systemd?
I think this bug should be more about asking to reboot using kexec with
systemd. The only problem is that for that to work, Ubuntu would need to
implement https://systemd.io/BOOT_LOADER_SPECIFICATION/ (or move to boot
Public bug reported:
problem with installation of this package
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-47-generic 5.15.0-47.51
ProcVersionSignature: Ubuntu 5.4.0-125.141-generic 5.4.195
Uname: Linux 5.4.0-125-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
A
This change was made by a bot.
** 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/1988877
Title:
package linux-image-5.15.0-47-
Update on the kernel 5.15.0-46 status.
The light sensor does work after resuming from suspend, however the numbers
reported are an order of magnitude greater than before.
During day light it maxes out at 16941, but at night it will report 0, then if
we shine light on it, return numbers > 1000 (
** 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/1988711
Title:
Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 f
I have removed the repository 5.15.0-48 kernel and installed the kernels you
linked to.
(using dpkg -i *.deb).
The system suspends successfully, but it does not wake from suspend.
Here is the log showing the end of the suspend.
At 23:10 I started suspend.
At 23:13 I attempted to wake the mach
** Description changed:
+ [IMPACT/Justification]
+
+
+ [FIX]
+
Please integrate the latest set of bug fix patches accepted in mkp/scsi
5.20/scsi-staging
b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
b21c9deb
Thanks for the testing. First, let's make sure the resume fail was
caused by cm32181.
So can you please run `sudo modprobe -r cm32181`, and see if your system
can resume successfully?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Tags added: originate-from-1983454
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1987312
Title:
IWLMEI may cause device down at resuming from s2idle
Status in HWE Next:
N
Hi KC,
Sure, Please share more details once you have more updates.
In case there is a ticket for No Signal issue, please do share.
Thanks and Best Regards,
Murali
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
41 matches
Mail list logo
