apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657757/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657758/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657756/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657759/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
The issue doesn't show when using the 525 driver.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2012908
Title:
nvidia driver 515 fails to boot on kernel 6.2
Status in
** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-23.04
--
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/2011817
Title:
Intel Alder Lake GPU performance much lower in 6.1/6.2
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux-aws-5.19 -
5.19.0-1022.23~22.04.1
---
linux-aws-5.19 (5.19.0-1022.23~22.04.1) jammy; urgency=medium
* jammy/linux-aws-5.19: 5.19.0-1022.23~22.04.1 -proposed tracker
(LP: #2011999)
[ Ubuntu: 5.19.0-1022.23 ]
* kinetic/linux-aws:
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
Public bug reported:
Hello. bluetooth does not work on my HONOR MagicBook 16 Series.
Bluetooth does not turn on through the settings
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic
Public bug reported:
Mar 27 12:50:37 juliuswork kernel: [ 9754.386159] amdgpu :05:00.0: amdgpu:
[mmhub0] no-retry page fault (src_id:0 ring:40 vmid:1 pasid:32781, for process
spotify pid 23781 thread spotify:cs0 pid 23841)
Mar 27 12:50:37 juliuswork kernel: [ 9754.386161] amdgpu
** Changed in: linux-bluefield (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2008136
Title:
netfilter: flowtable:
** Changed in: linux-bluefield (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2007581
Title:
gpio: Restrict usage
Public bug reported:
No installed 5.19 because not support Nvidia GT210
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-38-generic (not installed)
ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
Uname: Linux 5.15.0-69-generic x86_64
NonfreeKernelModules:
Same Issue with my Sound Blaster Recon3D / Z-Series
I have tried 5.19.0-35 and 5.19.0-38
Works only for kernel 5.19.0-32
--
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/2009243
--- Comment From gcwil...@us.ibm.com 2023-03-27 11:56 EDT---
This was fixed and closed on the Canonical side. Moving to closed on ours.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The following kernel incl. the needed patches for jammy:
5.15.0.70.68 | jammy-proposed
--
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/1639924
Title:
Kernel livepatch support for for
Confirming the proposed 5.4.0-1099 packages resolve the NFS bug on
Bionic running in AWS.
--
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/2009325
Title:
NFS deathlock with last
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 2012953
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
after mentioned updates screens flickers to complete black and back... system
near unusable (sorry for typos but cant see much so i write here mostly blind
whilst i have about half a second a view of my desktop )
I attach here some outputs from the logs (jopurnal -xe) and
All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.19
(5.19.0-1020.22~22.04.2+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
All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.19
(5.19.0-1020.22~22.04.2+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
Public bug reported:
Hi
I have a XMG Focus 17 laptop.
i7-12700H with Intel Iris Xe Graphics
Nvidia RTX 3060.
Dualboot LinuxMint 21.1 (based on Ubuntu 22.04) / Windows 10
Kernel 5.15.0-67-generic
HDMI output (2nd screen, TV) works fine with :
-Windows
-LinuxMint with Nvidia card activated
BUT
Can confirm that 5.15.0-1033 seems to have resolved the NFS bug on Jammy
running on AWS.
Is there a timeframe for the same patch to be applied to the 5.19 kernel
train?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
Same Issue with my Sound Blaster Recon3D / Z-Series
I have tried 5.19.0-35 and 5.19.0-38
Works only for kernel 5.19.0-32
--
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/2009243
Ok, thx Thorsten - closing it form this side too as Fix Released.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: ubuntu-z-systems
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
--- Comment From thorsten.di...@de.ibm.com 2023-03-27 04:16 EDT---
(In reply to comment #6)
> It looks to me that the automatic debug-symbols package generation and
> publication for the various linux-generic kernels works again.
> Would you agree if this LP bug gets closed?
Oops, I lost
This bug was fixed in the package linux-oracle-5.15 -
5.15.0-1032.38~20.04.1
---
linux-oracle-5.15 (5.15.0-1032.38~20.04.1) focal; urgency=medium
* focal/linux-oracle-5.15: 5.15.0-1032.38~20.04.1 -proposed tracker
(LP: #2012656)
[ Ubuntu: 5.15.0-1032.38 ]
*
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-23.04
** Changed in: plymouth (Ubuntu)
Milestone: None => ubuntu-23.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** 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/2009063
Title:
Consistent autopkgtest failures in xdp-tools
Hello Stefan, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.21 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Kleber, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.21 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657754/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657753/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657747/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657750/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657749/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657751/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657755/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657752/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package nvidia-graphics-drivers-525 -
525.89.02-0ubuntu0.22.04.1
---
nvidia-graphics-drivers-525 (525.89.02-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #2006937):
- Fixed a bug that could cause banding or flickering of color
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
** Description changed:
- Migrate oem-5.14 to hwe-5.15 now that there should be no functional
- regressions left anymore.
+ [Impact]
+ Migrate oem-5.14 to hwe-5.15 now that there should be no functional
regressions left anymore.
+
+ [Test case]
+ Update a machine with oem-5.14 metapackages to
** Also affects: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-intel-iotg
The issue is also present in Jammy distro kernel (linux-
image-5.15.0-67-generic) and e2fsprofs 1.46.5-2ubuntu1.1
How to reproduce :
* Create an openstack instance and user virtio-scsi as block device controller
* Add a Cinder volume (backed by PureStorage/iSCSI)
* format the whole volume :
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
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/2012698
Title:
Plymouth is just a plain black
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/2012918
Title:
Spotify completely freezes
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux-aws - 5.4.0-1099.107
---
linux-aws (5.4.0-1099.107) focal; urgency=medium
* focal/linux-aws: 5.4.0-1099.107 -proposed tracker (LP: #2012000)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct
This bug was fixed in the package linux-aws - 5.15.0-1033.37
---
linux-aws (5.15.0-1033.37) jammy; urgency=medium
* jammy/linux-aws: 5.15.0-1033.37 -proposed tracker (LP: #2011997)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657746/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657748/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657744/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657745/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657743/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
Public bug reported:
I just updated my Lunar install, which brought me the 6.2 kernel, and it
failed to start, stalling after enumerating my USB devices, until
something times out with a message saying that the udev event queue
failed to be drained.
When attempting to move on to the normal
This bug was fixed in the package linux-kvm - 6.2.0-1002.2
---
linux-kvm (6.2.0-1002.2) lunar; urgency=medium
* lunar/linux-kvm: 6.2.0-1002.2 -proposed tracker (LP: #2012486)
* Miscellaneous Ubuntu changes
- [Config] inherit debian.master annotation
- [Config]
Public bug reported:
Ubuntu 23.04 running linux-image-6.2.0-18-generic panics at boot.
Complains about not finding a boot filesystem.
System boots normally with linux-image 6.1.15
Don't know how to collect data on this apart from taking a photo of the
assert.
** Affects: linux-signed (Ubuntu)
Updated to Jammy 1.2.6.3-1ubuntu1.5, Mic-mute LED works as expected.
** Tags removed: verification-needed verification-needed-jammy
verification-needed-kinetic
** Tags added: verification-done verification-done-jammy
verification-done-kinetic
--
You received this bug notification because you
Thanks to @seb128 for your kindly help.
** Changed in: alsa-ucm-conf (Ubuntu Kinetic)
Importance: Undecided => Critical
** Changed in: hwe-next
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Also kinetic 1.2.6.3-1ubuntu4.2
** Description changed:
[Impact]
- Mic-mute LED is broken on some AMD ACP DMIC.
+ Sometimes Mic-mute LED is not working after press (Mic-mute/F4) key on
Thinkpad AMD platform with AMD ACP DMIC.
[Fix]
- Update Mic LED settings for ACP DMIC,
+ Update Mic
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle
I just got bit by this, too. Was transferring ~40T via rsync to a new
NAS setup... got about 12T in and it just stopped. Eventually realized
the mountpoint was unresponsive. Rebooting and kicking rsync back off
resulted in the same scenario almost immediately. The machine in
question is
Re-opening as until linux-kvm is deprecated or the CPC team moves over
to using linux-virtual for KVM images, this is the kernel we're dealing
with and that kernel should be functional.
** Changed in: linux-kvm (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification
Public bug reported:
[Impact]
Adding these patches address a number of differences between the Ubuntu
kernel and the internal NVIDIA kernel.
[Fix]
These patches do not constitute a single fix or a set of fixes for bugs but
instead enable kernel functionality as well as fix kernel bugs
5.15.0-69-generic -no change as far I can tell.
--
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/1998285
Title:
5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
Status in linux package in
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1013.13
---
linux-oem-6.0 (6.0.0-1013.13) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1013.13 -proposed tracker (LP: #2008351)
* CVE-2023-1281
- net/sched: tcindex: update imperfect hash filters respecting rcu
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle
This bug was fixed in the package lttng-modules -
2.12.5-1ubuntu2~20.04.5
---
lttng-modules (2.12.5-1ubuntu2~20.04.5) focal; urgency=medium
* Backport fixes to jbd2 format in 5.4.229 (LP: #2004644)
- d/p/0013-fix-jbd2-use-the-correct-print-format.patch
-
1 - 100 of 141 matches
Mail list logo