[Kernel-packages] [Bug 2039339] [NEW] package linux-headers-generic-hwe-22.04 5.15.0.43.44 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Public bug reported: "Informats" ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-generic-hwe-22.04 5.15.0.43.44 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 823 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Oct 13 19:27:05 2023 DuplicateSignature: package:linux-headers-generic-hwe-22.04:5.15.0.43.44 Unpacking linux-headers-6.2.0-34-generic (6.2.0-34.34~22.04.1) ... dpkg-deb: error: '/tmp/apt-dpkg-install-qJZbJk/15-linux-headers-generic-hwe-22.04_6.2.0.34.34~22.04.11_amd64.deb' is not a Debian format archive dpkg: error processing archive /tmp/apt-dpkg-install-qJZbJk/15-linux-headers-generic-hwe-22.04_6.2.0.34.34~22.04.11_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 InstallationDate: Installed on 2023-10-13 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. ens33 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=900ff5dd-4fe8-42e4-a25e-21af89b01b2d ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 RfKill: SourcePackage: linux Title: package linux-headers-generic-hwe-22.04 5.15.0.43.44 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2015 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/02/2015:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check third-party-packages -- 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/2039339 Title: package linux-headers-generic-hwe-22.04 5.15.0.43.44 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 Status in linux package in Ubuntu: New Bug description: "Informats" ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-generic-hwe-22.04 5.15.0.43.44 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 823 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Oct 13 19:27:05 2023 DuplicateSignature: package:linux-headers-generic-hwe-22.04:5.15.0.43.44 Unpacking linux-headers-6.2.0-34-generic (6.2.0-34.34~22.04.1) ... dpkg-deb: error: '/tmp/apt-dpkg-install-qJZbJk/15-linux-headers-generic-hwe-22.04_6.2.0.34.34~22.04.11_amd64.deb' is not a Debian format archive dpkg: error processing archive /tmp/apt-dpkg-install-qJZbJk/15-linux-headers-generic-hwe-22.04_6.2.0.34.34~22.04.11_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 InstallationDate: Installed on 2023-10-13 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. ens33 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=900ff5dd-4fe8-42e4-a25e-21af89b01b2d ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A
Re: [Kernel-packages] [Bug 2036281] Re: activate bpf LSM by default
quick google search comes up with: https://falco.org/docs/event-sources/kernel/ https://medium.com/@lumontec/some-freshness-with-linux-security-modules-and-ebpf-676ac363a135 https://blog.aquasec.com/linux-security-with-tracee-and-ebpf https://www.infoq.com/presentations/facebook-google-bpf-linux-kernel/ https://kubearmor.io It's the generic hypothetical solutions that drives innovation to sw engineering. On Tue, Sep 26, 2023 at 6:30 PM Thadeu Lima de Souza Cascardo < 2036...@bugs.launchpad.net> wrote: > > BPF LSM is the only major LSM that has a potential platform available > for targeting generic sw security solutions and generic performance sw > solutions between multiple distros. > > So no specific software solution in mind? Only generic hypothetical > solutions? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2036281 > > Title: > activate bpf LSM by default > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > in Fedora/RHEL if I want to see if the bpf LSM is active/available in > the kernel I can go here: > > [root@virtualrocky]# cat /sys/kernel/security/lsm > lockdown,capability,yama,selinux,bpf[root@virtualrocky]# > > but if I do the same thing in Ubuntu 22.0.4 bpf is NOT there: > > root@virtual-ubuntu2204:/# cat /sys/kernel/security/lsm > lockdown,capability,landlock,yama,apparmorroot@virtual-ubuntu2204:/# > > Please add bpf LSM to the CONFIG_LSM > > See discourse for background info > > https://discourse.ubuntu.com/t/ask-us-anything-about-ubuntu- > kernels/27664/127?u=why2jjj > > root@virtual-ubuntu2204:/opt/# cat /proc/version_signature > Ubuntu 5.15.0-82.91-generic 5.15.111 > > THANK YOU! > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu82.5 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: jfreyensee 2526 F pulseaudio > CRDA: N/A > CasperMD5CheckResult: pass > CloudArchitecture: x86_64 > CloudID: none > CloudName: none > CloudPlatform: none > CloudSubPlatform: config > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 22.04 > InstallationDate: Installed on 2023-08-29 (17 days ago) > InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release > amd64 (20230810) > MachineType: Parallels Software International Inc. Parallels Virtual > Platform > NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg > Package: linux (not installed) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 virtio_gpudrmfb > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-82-generic > root=/dev/mapper/ubuntu--vg-ubuntu--lv ro > ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RebootRequiredPkgs: Error: path contained symlinks. > RelatedPackageVersions: >linux-restricted-modules-5.15.0-82-generic N/A >linux-backports-modules-5.15.0-82-generic N/A >linux-firmware > 20220329.git681281e4-0ubuntu3.18 > RfKill: > > Tags: jammy uec-images > Uname: Linux 5.15.0-82-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: N/A > _MarkForUpload: True > dmi.bios.date: 07/03/2023 > dmi.bios.release: 18.3 > dmi.bios.vendor: Parallels Software International Inc. > dmi.bios.version: 18.3.2 (53621) > dmi.board.name: Parallels Virtual Platform > dmi.board.vendor: Parallels Software International Inc. > dmi.board.version: None > dmi.chassis.type: 2 > dmi.chassis.vendor: Parallels Software International Inc. > dmi.ec.firmware.release: 18.3 > dmi.modalias: > dmi:bvnParallelsSoftwareInternationalInc.:bvr18.3.2(53621):bd07/03/2023:br18.3:efr18.3:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct2:cvr:skuUndefined: > dmi.product.family: Parallels VM > dmi.product.name: Parallels Virtual Platform > dmi.product.sku: Undefined > dmi.product.version: None > dmi.sys.vendor: Parallels Software International Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036281/+subscriptions > > -- 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/2036281 Title: activate bpf LSM by default Status in linux package in Ubuntu: Incomplete Bug description: in Fedora/RHEL if I want to see if the bpf LSM is active/available in the kernel I can go here: [root@virtualrocky]# cat /sys/kernel/security/lsm lockdown,capability,yama,selinux,bpf[root@virtualrocky]# but if I do the same
[Kernel-packages] [Bug 2031174] Re: booting into initramfs not importing zfs pool
[Expired for zfs-linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2031174 Title: booting into initramfs not importing zfs pool Status in zfs-linux package in Ubuntu: Expired Bug description: With root on zfs ubuntu boots into initramfs not finding the pool. No pool imported. Manually import the root pool at the command prompt an then exit Hint: Try: zpool import -N zpool import -N imports the pool: pool: rpool id: state: online status: Some supported features are not enabled on the pool. action: The pool can be imported using its name or nummeric identifier ... zpool list no pools available zpool import rpool zpool list rpool 232G 215G 17.4G 48% 92% 1.00x online - exiting the initramfs commandline makes the system boot further, then find: /dev/zvol/: no such file or directory find: /dev/zvol/: no such file or directory cannot open "/ROOT/ubuntu_sxcpx": No such file or directory ... mount: mounting /dev on /root/dev failed: no such file or directory mount; mouniing /run on /root/run failed: no such file or directory run-init: can't execute /sbin/init: no such file or directory [... further run-init messages about missing file or directory] No init found. Try passing init= bootarg A second ctrl-d leads to a kernel panik because of killing init. Seems update-grub generating grub-configurations unusable with root on zfs and /boot on ext4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2031174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
The issue won't occur in Lunar. It's only specifically a problem with gdm when a kernel has been configured this way. It's not a problem in Jammy yet, but will be a problem when such a kernel gets backported as HWE. ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Lunar) Status: New => Fix Released ** Changed in: linux (Ubuntu Lunar) Status: New => Won't Fix ** Changed in: gdm3 (Ubuntu Lunar) Status: New => Invalid ** Changed in: gdm3 (Ubuntu Jammy) Status: Incomplete => In Progress -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: In Progress Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Lunar: Invalid Status in linux source package in Lunar: Won't Fix Status in nvidia-graphics-drivers-470 source package in Lunar: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037087] Re: TCPDirect patches
** Changed in: linux-gcp-5.15 (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2037087
Title:
TCPDirect patches
Status in linux-gcp-5.15 package in Ubuntu:
New
Status in linux-gcp-5.15 source package in Focal:
Fix Committed
Bug description:
[Impact]
* Include patches to enable TCPDirect. This is considered a v1 implementation
while Google works to
upsteam a v2 implementation, hence the "UBUNTU: SAUCE: (no-up)"
classification.
[Fix]
d1016eee0b1a ("UBUNTU: SAUCE: (no-up) UPSTREAM: tcp: derive delack_max from
rto_min")
10364f0d83ee ("UBUNTU: SAUCE: (no-up) gve: Add retry logic for recoverable
adminq errors")
403fb6f43a7c ("UBUNTU: SAUCE: (no-up) tcp: defer regular ACK while processing
socket backlog")
be97d51d24da ("UBUNTU: SAUCE: (no-up) gve: Enable header-split without
gve_close/gve_open")
499a0ec31c74 ("UBUNTU: SAUCE: (no-up) gve: fix rx issues for skb free and
append frags")
89b4d1e69fac ("UBUNTU: SAUCE: (no-up) net: fix silent put_cmsg() failures")
d025ece61dab ("UBUNTU: SAUCE: (no-up) tcp: get rid of
sysctl_tcp_adv_win_scale")
d1380ff2f4e3 ("UBUNTU: SAUCE: (no-up) gve: Add tx watchdog to avoid race
condition on miss path")
a4bc2e0cd1a3 ("UBUNTU: SAUCE: (no-up) net-tcp_5k_mtu: force wscale >= 12 for
active flows")
bbe85e8e856c ("UBUNTU: SAUCE: (no-up) net-tcp_5k_mtu: force wscale >= 12 for
4K MTU TCP flows")
7d5f15f733e8 ("UBUNTU: SAUCE: (no-up) dma-buf: fix int overflow")
22668842a913 ("UBUNTU: SAUCE: (no-up) gve: add flow steering and rss reset
when teardown device resources")
18e66e5d9ac4 ("UBUNTU: SAUCE: (no-up) net: create skb_frags_not_readable()
helper")
5d81162de488 ("UBUNTU: SAUCE: (no-up) net: add missing skb->devmem checks")
cf0bcfdf9f87 ("UBUNTU: SAUCE: (no-up) net: remove devmem check from
__pskb_copy_fclone()")
9ca03b5c36c7 ("UBUNTU: SAUCE: (no-up) net: allow tcp coallapsing and
coallescing for devmem skbs")
030aef8b0fd2 ("UBUNTU: SAUCE: (no-up) net: skb_store_bits() should succeed on
devmem header")
6aaf939fb49e ("UBUNTU: SAUCE: (no-up) net: fix skb_split unnecessarily
setting skb->devmem")
51e12a8201a1 ("UBUNTU: SAUCE: (no-up) net: skb_copy_bits() should be able to
copy devmem header")
ea8a78e040f5 ("UBUNTU: SAUCE: (no-up) net: fix memory leaks due to
skb->devmem checks")
1fcd891606c0 ("UBUNTU: SAUCE: (no-up) net: fix snaplen for devmem packets")
e4a4e05f4831 ("UBUNTU: SAUCE: (no-up) net: keep track and avoid access of skb
containing dma-buf pages.")
424871c3c564 ("UBUNTU: SAUCE: (no-up) gve: implement device memory socket
data path")
4f8668ee4cdb ("UBUNTU: SAUCE: (no-up) gve: implement devmem socket stats")
abe1772b0e39 ("UBUNTU: SAUCE: (no-up) gve: add rss support")
c08a1adb6130 ("UBUNTU: SAUCE: (no-up) gve: add flow steering support")
ffa842923ad6 ("UBUNTU: SAUCE: (no-up) gve: Add header split support")
940527385c4c ("UBUNTU: SAUCE: (no-up) lakitu config: enable TCP Direct
configs")
ebfa162318f8 ("UBUNTU: SAUCE: (no-up) tcp, cos-only: revert changes to
skb_zerocopy_iter_stream")
b87d0b0e659a ("UBUNTU: SAUCE: (no-up) tcp: let sendmsg() take file
descriptors via cmsg to enable devmem Tx")
1d523c425a8c ("UBUNTU: SAUCE: (no-up) net: add SO_DEVMEM_DONTNEED setsockopt
to release pages")
3e34b0936884 ("UBUNTU: SAUCE: (no-up) net: backport fixes to devmem TCP rx")
446d7a742177 ("UBUNTU: SAUCE: (no-up) tcp: implement RX path for devmem
sockets")
109f2e3feb98 ("UBUNTU: SAUCE: (no-up) net: use get_file_rcu() instead of
get_file for __netdev_rxq_alloc_page_from_dmabuf_pool")
0d5117d4ea53 ("UBUNTU: SAUCE: (no-up) net: add netdev_rxq_alloc_page and
skb->devmem")
d0d273544148 ("UBUNTU: SAUCE: (no-up) dmabuf: add ioctl that binds dmabuf
pagepool to a netdevice")
05c81288f77b ("UBUNTU: SAUCE: (no-up) dma-buf: fix int overflow in addr
calculation")
46366a3326d9 ("UBUNTU: SAUCE: (no-up) dma-buf: create struct pages backing a
dma-bu")
[Test Case]
* Compile tested
* Boot tested
* Ran ubuntu_kernel_selftests and ubuntu_performance_stress_ng test suites
* Tested by Google
[Other Info]
* Bulk of patchset came from
https://cos.googlesource.com/third_party/kernel/+log/refs/heads/tcpd/R105,
but some backports were given in SalesForce case below.
* SF: #00359122
[Where things could go wrong]
* Most changes target Google gve driver specifically.
* Some required updates to dma and network implementation to enable new API.
* Could lead to DMA or network instabilities
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp-5.15/+bug/2037087/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 2039334] Re: Intel usb problem with gamepad device descriptor read/64, error -32
i try with linux-meta (5.15.0.88.85) kernel and the problem are present too -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2039334 Title: Intel usb problem with gamepad device descriptor read/64, error -32 Status in linux-hwe-6.2 package in Ubuntu: New Status in linux-meta package in Ubuntu: New Bug description: In last kernel my xbox chinese gamepad no are detected in other pc with other hardware work i think are releated with: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Because same occurs in other pc with intel processor uname -a Linux PC 6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux sudo dmesg [205166.753280] usb 1-1.5: new full-speed USB device number 124 using ehci-pci [205166.833286] usb 1-1.5: device descriptor read/64, error -32 [205167.021295] usb 1-1.5: device descriptor read/64, error -32 [205167.129410] usb 1-1-port5: attempt power cycle [205171.225516] usb 2-1.5: new full-speed USB device number 15 using ehci-pci [205171.305513] usb 2-1.5: device descriptor read/64, error -32 [205171.493528] usb 2-1.5: device descriptor read/64, error -32 [205171.681533] usb 2-1.5: new full-speed USB device number 16 using ehci-pci [205171.761545] usb 2-1.5: device descriptor read/64, error -32 [205171.949545] usb 2-1.5: device descriptor read/64, error -32 [205172.057822] usb 2-1-port5: attempt power cycle sudo cat /sys/kernel/debug/usb/usbmon/1u >bus1data.txt attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2039334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039334] Re: Intel usb problem with gamepad device descriptor read/64, error -32
** Attachment added: "lsub.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2039334/+attachment/5709309/+files/lsub.txt ** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039334 Title: Intel usb problem with gamepad device descriptor read/64, error -32 Status in linux-hwe-6.2 package in Ubuntu: New Status in linux-meta package in Ubuntu: New Bug description: In last kernel my xbox chinese gamepad no are detected in other pc with other hardware work i think are releated with: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Because same occurs in other pc with intel processor uname -a Linux PC 6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux sudo dmesg [205166.753280] usb 1-1.5: new full-speed USB device number 124 using ehci-pci [205166.833286] usb 1-1.5: device descriptor read/64, error -32 [205167.021295] usb 1-1.5: device descriptor read/64, error -32 [205167.129410] usb 1-1-port5: attempt power cycle [205171.225516] usb 2-1.5: new full-speed USB device number 15 using ehci-pci [205171.305513] usb 2-1.5: device descriptor read/64, error -32 [205171.493528] usb 2-1.5: device descriptor read/64, error -32 [205171.681533] usb 2-1.5: new full-speed USB device number 16 using ehci-pci [205171.761545] usb 2-1.5: device descriptor read/64, error -32 [205171.949545] usb 2-1.5: device descriptor read/64, error -32 [205172.057822] usb 2-1-port5: attempt power cycle sudo cat /sys/kernel/debug/usb/usbmon/1u >bus1data.txt attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2039334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036954] Re: Cannot turn Bluetooth on in Ubuntu 22.04.03 LTS
@daniel can you post the exit of command sudo lsusb -v please. I recently report this bug https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2039334 maybe are releated -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036954 Title: Cannot turn Bluetooth on in Ubuntu 22.04.03 LTS Status in linux-hwe-6.2 package in Ubuntu: New Bug description: [4.240300] kernel: usb 1-11: new high-speed USB device number 5 using xhci_hcd [9.440449] kernel: usb 1-11: device descriptor read/64, error -110 [ 25.056457] kernel: usb 1-11: device descriptor read/64, error -110 [ 25.360292] kernel: usb 1-11: new high-speed USB device number 6 using xhci_hcd [ 30.688469] kernel: usb 1-11: device descriptor read/64, error -110 [ 46.304457] kernel: usb 1-11: device descriptor read/64, error -110 [ 46.415300] kernel: usb usb1-port11: attempt power cycle [ 46.892291] kernel: usb 1-11: new high-speed USB device number 7 using xhci_hcd [ 51.692371] kernel: usb 1-11: Device not responding to setup address. [ 56.700369] kernel: usb 1-11: Device not responding to setup address. [ 56.908290] kernel: usb 1-11: device not accepting address 7, error -71 [ 57.104291] kernel: usb 1-11: new high-speed USB device number 8 using xhci_hcd [ 61.904358] kernel: usb 1-11: Device not responding to setup address. [ 66.912367] kernel: usb 1-11: Device not responding to setup address. [ 67.120289] kernel: usb 1-11: device not accepting address 8, error -71 [ 67.123280] kernel: usb usb1-port11: unable to enumerate USB device Today, I can't use bluetooth as it gives usb 1-11 error on boot. 1] Bluetooth device is attached on Mainboard "ASUS ROG STRIX B650E-I GAMING WIFI STCOM" 2] result of cat /proc/version_signature --> Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 3] result of cat /proc/version --> Linux version 6.2.0-32-generic (buildd@lcy02-amd64-076) (x86_64-linux-gnu-gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039334] [NEW] Intel usb problem with gamepad device descriptor read/64, error -32
Public bug reported: In last kernel my xbox chinese gamepad no are detected in other pc with other hardware work i think are releated with: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Because same occurs in other pc with intel processor uname -a Linux PC 6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux sudo dmesg [205166.753280] usb 1-1.5: new full-speed USB device number 124 using ehci-pci [205166.833286] usb 1-1.5: device descriptor read/64, error -32 [205167.021295] usb 1-1.5: device descriptor read/64, error -32 [205167.129410] usb 1-1-port5: attempt power cycle [205171.225516] usb 2-1.5: new full-speed USB device number 15 using ehci-pci [205171.305513] usb 2-1.5: device descriptor read/64, error -32 [205171.493528] usb 2-1.5: device descriptor read/64, error -32 [205171.681533] usb 2-1.5: new full-speed USB device number 16 using ehci-pci [205171.761545] usb 2-1.5: device descriptor read/64, error -32 [205171.949545] usb 2-1.5: device descriptor read/64, error -32 [205172.057822] usb 2-1-port5: attempt power cycle sudo cat /sys/kernel/debug/usb/usbmon/1u >bus1data.txt attached ** Affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: jammy kernel-bug ** Attachment added: "sudo cat /sys/kernel/debug/usb/usbmon/1u >bus1data.txt" https://bugs.launchpad.net/bugs/2039334/+attachment/5709308/+files/bus1data.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039334 Title: Intel usb problem with gamepad device descriptor read/64, error -32 Status in linux-hwe-6.2 package in Ubuntu: New Bug description: In last kernel my xbox chinese gamepad no are detected in other pc with other hardware work i think are releated with: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Because same occurs in other pc with intel processor uname -a Linux PC 6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux sudo dmesg [205166.753280] usb 1-1.5: new full-speed USB device number 124 using ehci-pci [205166.833286] usb 1-1.5: device descriptor read/64, error -32 [205167.021295] usb 1-1.5: device descriptor read/64, error -32 [205167.129410] usb 1-1-port5: attempt power cycle [205171.225516] usb 2-1.5: new full-speed USB device number 15 using ehci-pci [205171.305513] usb 2-1.5: device descriptor read/64, error -32 [205171.493528] usb 2-1.5: device descriptor read/64, error -32 [205171.681533] usb 2-1.5: new full-speed USB device number 16 using ehci-pci [205171.761545] usb 2-1.5: device descriptor read/64, error -32 [205171.949545] usb 2-1.5: device descriptor read/64, error -32 [205172.057822] usb 2-1-port5: attempt power cycle sudo cat /sys/kernel/debug/usb/usbmon/1u >bus1data.txt attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2039334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
This has been marked as fixed in mantic, but this bug does not say what the plan is for lunar, which is still the supported upgrade path from jammy. ** Changed in: gdm3 (Ubuntu Jammy) Status: In Progress => Incomplete -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: Incomplete Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031302] Re: test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore)
Paolo's merge request has been applied in qa-regression-testing, thanks! ** Changed in: qa-regression-testing Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031302 Title: test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore) Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: New Bug description: This test requires HARDENED_USERCOPY to be unset. Test log: Running 'python3 ./test-kernel-security.py -v KernelSecurityConfigTest.test_290_config_hardened_usercopy' Running test: './test-kernel-security.py' distro: 'Ubuntu 22.04' kernel: '6.5.0-1002.2 (Ubuntu 6.5.0-1002.2-oem 6.5.0-rc4)' arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu') test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest) Ensure CONFIG_HARDENED_USERCOPY is set ... (skipped: HARDENED_USERCOPY depends on the allocator and strict devmem) FAIL == FAIL: test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest) Ensure CONFIG_HARDENED_USERCOPY is set -- Traceback (most recent call last): File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 2724, in test_290_config_hardened_usercopy self.assertKernelConfigUnset(config_name) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 223, in assertKernelConfigUnset self.assertFalse(self._test_config(name), AssertionError: True is not false : HARDENED_USERCOPY option was expected to be unset in the kernel config -- Ran 1 test in 0.007s FAILED (failures=1) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/2031302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
The firmware-sof upload in lunar-proposed contains a sha256sum.txt with the checksums of all the firmware. But every line of this file is different from every line in the previous version, because the version number is encoded. Likewise, the file paths within the package encode the version. This makes it very difficult to review this package using a debdiff. Can you suggest a method of reviewing the package that confirms we have only firmware file additions here, and not changes to existing firmware files that could cause a regression? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Triaged Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: SRU Justification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] Install the fixes on the target platform(RPL Dell SKU 0BDA) and verify the audio function. 1. Install the firmware-sof on platform(RPL) with Audio Smart AMP IC ALC1319D 2. Make sure the audio works 3. Also try above steps on other platforms(ADL/TGL) to make sure the audio keep working. [Where problems could occur] New firmware may affect ADL, RPL, and TGL platforms, we need to verify it on not only the target platform, but other existing platforms. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
** Description changed: - SRU Jusitification for firmware-sof + SRU Justification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] Install the fixes on the target platform(RPL Dell SKU 0BDA) and verify the audio function. 1. Install the firmware-sof on platform(RPL) with Audio Smart AMP IC ALC1319D 2. Make sure the audio works 3. Also try above steps on other platforms(ADL/TGL) to make sure the audio keep working. [Where problems could occur] New firmware may affect ADL, RPL, and TGL platforms, we need to verify it on not only the target platform, but other existing platforms. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Triaged Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: SRU Justification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] Install the fixes on the target platform(RPL Dell SKU 0BDA) and verify the audio function. 1. Install the firmware-sof on platform(RPL) with Audio Smart AMP IC ALC1319D 2. Make sure the audio works 3. Also try above steps on other platforms(ADL/TGL) to make sure the audio keep working. [Where problems could occur] New firmware may affect ADL, RPL, and TGL platforms, we need to verify it on not only the target platform, but other existing platforms. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039325] [NEW] mmc: sdhci-of-dwcmshc: Intermittent data error under stress test
Public bug reported: sdhci-dwcmshc MLNXBF30:00: __mmc_blk_ioctl_cmd: data error -110 SRU Justification: [Impact] This change is needed to avoid intermittent "sdhci-dwcmshc MLNXBF30:00: __mmc_blk_ioctl_cmd: data error -110" error under stress test [Fix] The fix added a quirk for the BF3 sdhci driver to avoid such data error. [Test Case] 1. Same functionality and testing as on BlueField-1/2. 2. Install OS on NVME, and run the FIO test on EMMC. fio --name=mmcblk0_randrw_stress_round_1 \ --ioengine=libaio --direct=1 --time_based=1 \ --end_fsync=1 --ramp_time=5 --norandommap=1 \ --randrepeat=0 --group_reporting=1 --numjobs=8 \ --iodepth=128 --rw=randrw --overwrite=1 \ --runtime=3600 --bs=4K --filename=/dev/mmcblk0 & [Regression Potential] Same behavior from user perspective. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- 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/2039325 Title: mmc: sdhci-of-dwcmshc: Intermittent data error under stress test Status in linux-bluefield package in Ubuntu: New Bug description: sdhci-dwcmshc MLNXBF30:00: __mmc_blk_ioctl_cmd: data error -110 SRU Justification: [Impact] This change is needed to avoid intermittent "sdhci-dwcmshc MLNXBF30:00: __mmc_blk_ioctl_cmd: data error -110" error under stress test [Fix] The fix added a quirk for the BF3 sdhci driver to avoid such data error. [Test Case] 1. Same functionality and testing as on BlueField-1/2. 2. Install OS on NVME, and run the FIO test on EMMC. fio --name=mmcblk0_randrw_stress_round_1 \ --ioengine=libaio --direct=1 --time_based=1 \ --end_fsync=1 --ramp_time=5 --norandommap=1 \ --randrepeat=0 --group_reporting=1 --numjobs=8 \ --iodepth=128 --rw=randrw --overwrite=1 \ --runtime=3600 --bs=4K --filename=/dev/mmcblk0 & [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2039325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039324] [NEW] bcache UBSAN log spam
Public bug reported: The new 6.5 kernel in mantic causes a large amount of UBSAN warnings at boot when using bcache (see attached dmesg log, truncated after last error). The volume still mounts fine and I haven't observed any data corruption. There seems to have been some discussion about this on the LKML (although it was in reference to bcachefs but this seems to be coming out of the shared common code between that and bcache): https://lore.kernel.org/all/20230910015343.jmj4v2arenuxd...@moria.home.lan/T/ ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-lowlatency 6.5.0-9.9.1 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-lowlatency 6.5.3 Uname: Linux 6.5.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 13 17:40:55 2023 InstallationDate: Installed on 2018-08-03 (1897 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-lowlatency UpgradeStatus: Upgraded to mantic on 2023-10-13 (1 days ago) ** Affects: linux-signed-lowlatency (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic ** Attachment added: "dmesg log" https://bugs.launchpad.net/bugs/2039324/+attachment/5709273/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2039324 Title: bcache UBSAN log spam Status in linux-signed-lowlatency package in Ubuntu: New Bug description: The new 6.5 kernel in mantic causes a large amount of UBSAN warnings at boot when using bcache (see attached dmesg log, truncated after last error). The volume still mounts fine and I haven't observed any data corruption. There seems to have been some discussion about this on the LKML (although it was in reference to bcachefs but this seems to be coming out of the shared common code between that and bcache): https://lore.kernel.org/all/20230910015343.jmj4v2arenuxd...@moria.home.lan/T/ ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-lowlatency 6.5.0-9.9.1 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-lowlatency 6.5.3 Uname: Linux 6.5.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 13 17:40:55 2023 InstallationDate: Installed on 2018-08-03 (1897 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-lowlatency UpgradeStatus: Upgraded to mantic on 2023-10-13 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2039324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039313] Re: After installing latest version of linux-firmware system doesn't boot
Same release but GPU is a 7900 XTX -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2039313 Title: After installing latest version of linux-firmware system doesn't boot Status in linux-firmware package in Ubuntu: Confirmed Bug description: I've encountered the issue after installing a new kernel and so forth using apt-get upgrade. I've isolated the issue by rolling back the system and installing every package one by one. When I install linux- firmware it hangs I think when it wants to start the gpu. Can boot into safe mode just fine doesn't show any particular errors. The GPU is a Radeon 7900 XT 6.2.0-34-generic #34-Ubuntu SMP PREEMPT_DYNAMIC No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar Let me know what other specifics you might need and it's a desktop system with zfs so I can install a test package and rollback the system. If you want me to test something. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2039313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039280] Re: Support IP address protocol
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: iproute2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP address protocol
Status in iproute2 package in Ubuntu:
Confirmed
Status in iproute2 source package in Mantic:
Confirmed
Bug description:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
Two clean upstream cherry-picks, regression potential should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039313] Re: After installing latest version of linux-firmware system doesn't boot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2039313 Title: After installing latest version of linux-firmware system doesn't boot Status in linux-firmware package in Ubuntu: Confirmed Bug description: I've encountered the issue after installing a new kernel and so forth using apt-get upgrade. I've isolated the issue by rolling back the system and installing every package one by one. When I install linux- firmware it hangs I think when it wants to start the gpu. Can boot into safe mode just fine doesn't show any particular errors. The GPU is a Radeon 7900 XT 6.2.0-34-generic #34-Ubuntu SMP PREEMPT_DYNAMIC No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar Let me know what other specifics you might need and it's a desktop system with zfs so I can install a test package and rollback the system. If you want me to test something. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2039313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel
kernel log from boot ** Attachment removed: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2009952/+attachment/5709257/+files/kern.log ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2009952/+attachment/5709262/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009952 Title: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: 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 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The system is fully functional. No crashes, nothing breaks. Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks suspend/ resume on my laptop, see https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718. In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic (previous 22.04.1 LTS kernel) works well, with working suspend/ resume, and without screen flicker. But that's an 'old' kernel now, missing some nice improvements for the newer Ryzen APUs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04c 6.1.0.1007.7 ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6 Uname: Linux 6.1.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 13:09:20 2023 InstallationDate: Installed on 2023-02-06 (31 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-meta-oem-6.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039313] [NEW] After installing latest version of linux-firmware system doesn't boot
Public bug reported: I've encountered the issue after installing a new kernel and so forth using apt-get upgrade. I've isolated the issue by rolling back the system and installing every package one by one. When I install linux- firmware it hangs I think when it wants to start the gpu. Can boot into safe mode just fine doesn't show any particular errors. The GPU is a Radeon 7900 XT 6.2.0-34-generic #34-Ubuntu SMP PREEMPT_DYNAMIC No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 23.04 Release:23.04 Codename: lunar Let me know what other specifics you might need and it's a desktop system with zfs so I can install a test package and rollback the system. If you want me to test something. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2039313 Title: After installing latest version of linux-firmware system doesn't boot Status in linux-firmware package in Ubuntu: New Bug description: I've encountered the issue after installing a new kernel and so forth using apt-get upgrade. I've isolated the issue by rolling back the system and installing every package one by one. When I install linux- firmware it hangs I think when it wants to start the gpu. Can boot into safe mode just fine doesn't show any particular errors. The GPU is a Radeon 7900 XT 6.2.0-34-generic #34-Ubuntu SMP PREEMPT_DYNAMIC No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar Let me know what other specifics you might need and it's a desktop system with zfs so I can install a test package and rollback the system. If you want me to test something. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2039313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel
DRI device 0 DMCUB F/W version: 0x08002300 ○ PSR 2 with Y coordinates (eDP 1.4a) [3] ○ Sink OUI: Parade ○ resv_40f: 01 ○ ID String: 08-03 ○ PSR Status: 00-00-02 ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2009952/+attachment/5709257/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009952 Title: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: 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 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The system is fully functional. No crashes, nothing breaks. Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks suspend/ resume on my laptop, see https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718. In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic (previous 22.04.1 LTS kernel) works well, with working suspend/ resume, and without screen flicker. But that's an 'old' kernel now, missing some nice improvements for the newer Ryzen APUs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04c 6.1.0.1007.7 ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6 Uname: Linux 6.1.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 13:09:20 2023 InstallationDate: Installed on 2023-02-06 (31 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-meta-oem-6.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
I verified the issue on kernel linux/5.4.0-166.183, linux/5.15.0-88.98 and linux/6.2.0-36.37 and the issue is fixed. I was able to run enclave in debug mode in all 3 kernels. ** Tags removed: verification-needed-lunar-linux ** Tags added: verification-done-lunar-linux -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel
What is the easiest way to share kernel log :) ? dmesg > dmesg.log ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009952 Title: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: 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 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The system is fully functional. No crashes, nothing breaks. Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks suspend/ resume on my laptop, see https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718. In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic (previous 22.04.1 LTS kernel) works well, with working suspend/ resume, and without screen flicker. But that's an 'old' kernel now, missing some nice improvements for the newer Ryzen APUs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04c 6.1.0.1007.7 ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6 Uname: Linux 6.1.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 13:09:20 2023 InstallationDate: Installed on 2023-02-06 (31 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-meta-oem-6.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
** Tags removed: verification-needed-focal-linux ** Tags added: verification-done-focal-linux -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038516] Re: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11: seems to be a problem
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2038516 Title: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11: seems to be a problem with dkms update for nvidia drivers Status in dkms package in Ubuntu: New Bug description: Kernel updates seem not to work any more with nvidia drivers (dkms). This problem already occurred with every new kernel image since i reinstalled Ubuntu 23.04 on a new disk. Since this also affects kernel security updates, i guess this also implies a security vulnerability (thats why i selected this also). ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: helmut 1946 F wireplumber /dev/snd/controlC1: helmut 1946 F wireplumber /dev/snd/seq:helmut 1943 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Oct 5 09:33:30 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-06-24 (102 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) MachineType: ASUSTeK COMPUTER INC. G751JT ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-33-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro rootflags=subvol=@ quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G751JT.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G751JT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG751JT.206:bd01/23/2015:br4.6:svnASUSTeKCOMPUTERINC.:pnG751JT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG751JT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: G dmi.product.name: G751JT dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2038516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038542] Status changed to Confirmed
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/2038542 Title: package linux-tools-5.15.0-83 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-83', which is also in package linux- hwe-5.15-tools-5.15.0-83 5.15.0-83.92~20.04.1 Status in linux package in Ubuntu: Confirmed Bug description: No any more details ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-5.15.0-83 (not installed) ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: linux-tools-5.15.0-83:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: muqi 1614 F pulseaudio /dev/snd/controlC0: muqi 1614 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Thu Oct 5 20:33:10 2023 DpkgHistoryLog: Start-Date: 2023-10-05 20:33:10 Commandline: apt --fix-broken install Requested-By: muqi (1000) Install: linux-tools-5.15.0-83:amd64 (5.15.0-83.92, automatic) DpkgTerminalLog: Preparing to unpack .../linux-tools-5.15.0-83_5.15.0-83.92_amd64.deb ... Unpacking linux-tools-5.15.0-83 (5.15.0-83.92) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-5.15.0-83_5.15.0-83.92_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.5.15.0-83', which is also in package linux-hwe-5.15-tools-5.15.0-83 5.15.0-83.92~20.04.1 ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-83', which is also in package linux-hwe-5.15-tools-5.15.0-83 5.15.0-83.92~20.04.1 InstallationDate: Installed on 2023-04-27 (161 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HONOR HLYL-WXX9 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-41-generic root=UUID=9e0e7dda-6ab9-477f-8a79-ca3f9f4569d5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 SourcePackage: linux Title: package linux-tools-5.15.0-83 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-83', which is also in package linux-hwe-5.15-tools-5.15.0-83 5.15.0-83.92~20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 3.6 dmi.bios.vendor: HONOR dmi.bios.version: 3.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: HLYL-WXX9-PCB dmi.board.vendor: HONOR dmi.board.version: M1010 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HONOR dmi.chassis.version: M1010 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnHONOR:bvr3.06:bd09/13/2021:br3.6:efr3.6:svnHONOR:pnHLYL-WXX9:pvrM1010:rvnHONOR:rnHLYL-WXX9-PCB:rvrM1010:cvnHONOR:ct10:cvrM1010:skuC233: dmi.product.family: HONOR MagicBook dmi.product.name: HLYL-WXX9 dmi.product.sku: C233 dmi.product.version: M1010 dmi.sys.vendor: HONOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038542] Re: package linux-tools-5.15.0-83 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-83', which is also in package linux-hwe
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/2038542 Title: package linux-tools-5.15.0-83 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-83', which is also in package linux- hwe-5.15-tools-5.15.0-83 5.15.0-83.92~20.04.1 Status in linux package in Ubuntu: Confirmed Bug description: No any more details ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-5.15.0-83 (not installed) ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: linux-tools-5.15.0-83:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: muqi 1614 F pulseaudio /dev/snd/controlC0: muqi 1614 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Thu Oct 5 20:33:10 2023 DpkgHistoryLog: Start-Date: 2023-10-05 20:33:10 Commandline: apt --fix-broken install Requested-By: muqi (1000) Install: linux-tools-5.15.0-83:amd64 (5.15.0-83.92, automatic) DpkgTerminalLog: Preparing to unpack .../linux-tools-5.15.0-83_5.15.0-83.92_amd64.deb ... Unpacking linux-tools-5.15.0-83 (5.15.0-83.92) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-5.15.0-83_5.15.0-83.92_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.5.15.0-83', which is also in package linux-hwe-5.15-tools-5.15.0-83 5.15.0-83.92~20.04.1 ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-83', which is also in package linux-hwe-5.15-tools-5.15.0-83 5.15.0-83.92~20.04.1 InstallationDate: Installed on 2023-04-27 (161 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HONOR HLYL-WXX9 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-41-generic root=UUID=9e0e7dda-6ab9-477f-8a79-ca3f9f4569d5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 SourcePackage: linux Title: package linux-tools-5.15.0-83 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.15.0-83', which is also in package linux-hwe-5.15-tools-5.15.0-83 5.15.0-83.92~20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 3.6 dmi.bios.vendor: HONOR dmi.bios.version: 3.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: HLYL-WXX9-PCB dmi.board.vendor: HONOR dmi.board.version: M1010 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HONOR dmi.chassis.version: M1010 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnHONOR:bvr3.06:bd09/13/2021:br3.6:efr3.6:svnHONOR:pnHLYL-WXX9:pvrM1010:rvnHONOR:rnHLYL-WXX9-PCB:rvrM1010:cvnHONOR:ct10:cvrM1010:skuC233: dmi.product.family: HONOR MagicBook dmi.product.name: HLYL-WXX9 dmi.product.sku: C233 dmi.product.version: M1010 dmi.sys.vendor: HONOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035181] Re: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1043.49~20.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-focal-linux-
intel-iotg-5.15' to 'verification-done-focal-linux-intel-iotg-5.15'. If
the problem still exists, change the tag 'verification-needed-focal-
linux-intel-iotg-5.15' to 'verification-failed-focal-linux-intel-
iotg-5.15'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-intel-iotg-5.15-v2
verification-needed-focal-linux-intel-iotg-5.15
--
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/2035181
Title:
Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Confirmed
Bug description:
[Impact]
Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work
with CO-RE") from stable update breaks the ubuntu_bpf test build and
cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in
ubuntu_kernel_selftests stopped working, as they require bpf selftest
to be built first.
The following is extracted from the commit message:
The problem is the new offsetof() does not play nice with static asserts.
Given that the context is a static assert (and CO-RE relocation is not
needed at compile time), offsetof() usage can be replaced by restoring
the original offsetof() definition as __builtin_offsetof().
[Test Plan]
Build bpf selftest in tools/testing/selftests with the following command:
make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \
clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/
The build can finish successfully with patched kernel source code.
[Where problems could occur]
Fix limited to testing tool, if this fix is incorrect the bpf selftest
build will remain broken.
== Original bug report ==
Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04
This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
is a security cycle, in which the ubuntu_bpf test was not triggered
there)
Test build failed with:
CLNG-BPF [test_maps] test_btf_map_in_map.o
CLNG-BPF [test_maps] test_btf_newkv.o
CLNG-BPF [test_maps] test_btf_nokv.o
CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
CLNG-BPF [test_maps] test_cgroup_link.o
CLNG-BPF [test_maps] test_check_mtu.o
CLNG-BPF [test_maps] test_cls_redirect.o
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from
latest version at 'include/uapi/linux/bpf.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs
from latest version at 'include/uapi/linux/netlink.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at 'include/uapi/linux/if_link.h'
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
[Kernel-packages] [Bug 2034447] Re: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic
This bug is awaiting verification that the linux-intel- iotg-5.15/5.15.0-1043.49~20.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-focal-linux- intel-iotg-5.15' to 'verification-done-focal-linux-intel-iotg-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-intel-iotg-5.15' to 'verification-failed-focal-linux-intel- iotg-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-intel-iotg-5.15-v2 verification-needed-focal-linux-intel-iotg-5.15 -- 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/2034447 Title: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Seeing a panic on hidon (an Nvidia H100) after booting the 5.15.0-85-generic kernel: [ 58.935877] [ cut here ] [ 58.935893] refcount_t: underflow; use-after-free. [ 58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28 refcount_warn_saturate+0xf7/0x150 [ 58.935943] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp coretemp nls_iso8859_1 rapl irdma(+) i40e qat_4xxx(+) isst_if_mbox_pci intel_qat pmt_telemetry pmt_crashlog idxd(+) isst_if_mmio pmt_class isst_if_common authenc idxd_bus intel_th_gth mei_me intel_th_pci intel_th mei switchtec ipmi_ssif acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 multipath linear mlx5_ib ib_uverbs ib_core ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper raid0 mlx5_core syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ixgbe cec mlxfw ghash_clmulni_intel aesni_intel psample crypto_simd xfrm_algo ice rc_core cryptd tls nvme i2c_i801 dca xhci_pci intel_pmt drm [ 58.936077] pci_hyperv_intf i2c_ismt i2c_smbus [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936083] mdio [ 58.936096] xhci_pci_renesas nvme_core wmi pinctrl_emmitsburg [ 58.936106] CPU: 207 PID: 2985 Comm: systemd-udevd Not tainted 5.15.0-85-generic #95-Ubuntu [ 58.936115] Hardware name: NVIDIA DGXH100/DGXH100, BIOS 1.0.7 05/08/2023 [ 58.936119] RIP: 0010:refcount_warn_saturate+0xf7/0x150 [ 58.936130] Code: eb 9e 0f b6 1d 5e e6 b9 01 80 fb 01 0f 87 f4 63 6f 00 83 e3 01 75 89 48 c7 c7 88 c3 23 9e c6 05 42 e6 b9 01 01 e8 d8 e4 6b 00 <0f> 0b e9 6f ff ff ff 0f b6 1d 2d e6 b9 01 80 fb 01 0f 87 b1 63 6f [ 58.936135] RSP: 0018:ff4d5d94b2c7fa28 EFLAGS: 00010282 [ 58.936142] RAX: RBX: RCX: 0027 [ 58.936146] RDX: ff314dbbbf9e0588 RSI: 0001 RDI: ff314dbbbf9e0580 [ 58.936149] RBP: ff4d5d94b2c7fa30 R08: 0026 R09: ff4d5d94b2c7f9c0 [ 58.936153] R10: 0028 R11: 0001 R12: [ 58.936156] R13: ff314cbfdbcb6900 R14: ff314cbfdbcb67b8 R15: ff314cbfd24b4000 [ 58.936159] FS: 7fadd2f6c8c0() GS:ff314dbbbf9c() knlGS: [ 58.936163] CS: 0010 DS: ES: CR0: 80050033 [ 58.936167] CR2: 7fadd243b584 CR3: 00012972c006 CR4: 00771ee0 [ 58.936171] DR0: DR1: DR2: [ 58.936174] DR3: DR6: fffe07f0 DR7: 0400 [ 58.936177] PKRU: 5554 [ 58.936179] Call Trace: [ 58.936184] [ 58.936188] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936204] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936212] ? crypto_mod_put+0x6b/0x80 [ 58.936225] ? show_regs.part.0+0x23/0x29 [ 58.936232] ? show_regs.cold+0x8/0xd [ 58.936239] ? refcount_warn_saturate+0xf7/0x150 [ 58.936246] ? __warn+0x8c/0x100 [ 58.936255] ? refcount_warn_saturate+0xf7/0x150 [ 58.936263] ? report_bug+0xa4/0xd0 [ 58.936274] ? down_trylock+0x2e/0x40 [ 58.936285] ? handle_bug+0x39/0x90 [ 58.936296] ? exc_invalid_op+0x19/0x70 [
[Kernel-packages] [Bug 2036675] Re: 5.15.0-85 live migration regression
This bug is awaiting verification that the linux-intel- iotg-5.15/5.15.0-1043.49~20.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-focal-linux- intel-iotg-5.15' to 'verification-done-focal-linux-intel-iotg-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-intel-iotg-5.15' to 'verification-failed-focal-linux-intel- iotg-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-intel-iotg-5.15-v2 verification-needed-focal-linux-intel-iotg-5.15 -- 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/2036675 Title: 5.15.0-85 live migration regression Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Released Bug description: Fixes added for LP 2032164 [0] to resolve an issue in live migration have unfortunately introduced a regression, causing a previously working live migration pattern to fail when tested with the 5.15.0-85 kernel from -proposed. Specifically, live migration from a PKRU-enabled host running a kernel older than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail. The destination can be either with or without PKRU; both cases fail, although in different ways (one hangs, the other fails due to a PCID flag issue). The commits in question are commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0 Author: Dr. David Alan Gilbert Date: Mon Aug 21 14:47:28 2023 +0800 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES commit 27a189b881278c8ad9c16b0ee05668d724352733 Author: Leonardo Bras Date: Mon Aug 21 14:47:27 2023 +0800 x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 [0] https://bugs.launchpad.net/bugs/2032164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel
Can you please share your kernel log from a boot that had the failure, and without that parameter in place share the output of this script? https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009952 Title: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: 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 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The system is fully functional. No crashes, nothing breaks. Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks suspend/ resume on my laptop, see https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718. In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic (previous 22.04.1 LTS kernel) works well, with working suspend/ resume, and without screen flicker. But that's an 'old' kernel now, missing some nice improvements for the newer Ryzen APUs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04c 6.1.0.1007.7 ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6 Uname: Linux 6.1.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 13:09:20 2023 InstallationDate: Installed on 2023-02-06 (31 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-meta-oem-6.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel
I have a similar problem with Xubuntu and kernel version linux- image-6.5.0-9-generic. Adding "amdgpu.dcdebugmask=0x10" to /etc/default/grub fixes the flickering screen. OS: Xubuntu 23.10 x86_64 21F8003HMX ThinkPad T14s Gen 4 CPU: AMD Ryzen 7 PRO 7840U w/ Radeon -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009952 Title: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: 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 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The system is fully functional. No crashes, nothing breaks. Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks suspend/ resume on my laptop, see https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718. In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic (previous 22.04.1 LTS kernel) works well, with working suspend/ resume, and without screen flicker. But that's an 'old' kernel now, missing some nice improvements for the newer Ryzen APUs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04c 6.1.0.1007.7 ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6 Uname: Linux 6.1.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 13:09:20 2023 InstallationDate: Installed on 2023-02-06 (31 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-meta-oem-6.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039280] Re: Support IP address protocol
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP address protocol
Status in iproute2 package in Ubuntu:
New
Status in iproute2 source package in Mantic:
New
Bug description:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
Two clean upstream cherry-picks, regression potential should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039291] Re: Focal update: v5.4.254 upstream stable release
** 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 + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - 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 from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.254 upstream stable release + from git://git.kernel.org/ -v5.4.254 upstream stable release -from git://git.kernel.org/ - - + mmc: moxart: read scr register without changing byte order + ipv6: adjust ndisc_is_useropt() to also return true for PIO + dmaengine: pl330: Return DMA_PAUSED when transaction is paused + drm/nouveau/gr: enable memory loads on helper invocation on all channels + radix tree test suite: fix incorrect allocation size for pthreads + nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput + iio: cros_ec: Fix the allocation size for cros_ec_command + binder: fix memory leak in binder_init() + usb-storage: alauda: Fix uninit-value in alauda_check_media() + usb: dwc3: Properly handle processing of pending events + usb: common: usb-conn-gpio: Prevent bailing out if initial role is none + x86/cpu/amd: Enable Zenbleed fix for AMD Custom APU 0405 + x86/mm: Fix VDSO and VVAR placement on 5-level paging machines + x86: Move gds_ucode_mitigated() declaration to header + drm/nouveau/disp: Revert a NULL check inside nouveau_connector_get_modes + selftests/rseq: Fix build with undefined __weak + mISDN: Update parameter type of dsp_cmx_send() + net/packet: annotate data-races around tp->status + bonding: Fix incorrect deletion of ETH_P_8021AD protocol vid from slaves + dccp: fix data-race around dp->dccps_mss_cache + drivers: net: prevent tun_build_skb() to exceed the packet size limit + IB/hfi1: Fix possible panic during hotplug remove + wifi: cfg80211: fix sband iftype data lookup for AP_VLAN + dmaengine: mcf-edma: Fix a potential un-allocated memory access + net/mlx5: Allow 0 for total host VFs + ibmvnic: Handle DMA unmapping of login buffs in release functions + btrfs: don't stop integrity writeback too early + btrfs: set cache_block_group_error if we find an error + nvme-tcp: fix potential unbalanced freeze & unfreeze + nvme-rdma: fix potential unbalanced freeze & unfreeze + netfilter: nf_tables: report use refcount overflow + scsi: core: Fix legacy /proc parsing buffer overflow + scsi: storvsc: Fix handling of virtual Fibre Channel timeouts + scsi: 53c700: Check that command slot is not NULL + scsi: snic: Fix possible memory leak if device_add() fails + scsi: core: Fix possible memory leak if device_add() fails + alpha: remove __init annotation from exported page_is_ram() + sch_netem: fix issues in netem_change() vs get_dist_table() Linux 5.4.254 - sch_netem: fix issues in netem_change() vs get_dist_table() - alpha: remove __init annotation from exported page_is_ram() - scsi: core: Fix possible memory leak if device_add() fails - scsi: snic: Fix possible memory leak if device_add() fails - scsi: 53c700: Check that command slot is not NULL - scsi: storvsc: Fix handling of virtual Fibre Channel timeouts - scsi: core: Fix legacy /proc parsing buffer overflow - netfilter: nf_tables: report use refcount overflow - nvme-rdma: fix potential unbalanced freeze & unfreeze - nvme-tcp: fix potential unbalanced freeze & unfreeze - btrfs: set cache_block_group_error if we find an error - btrfs: don't stop integrity writeback too early - ibmvnic: Handle DMA unmapping of login buffs in release functions - net/mlx5: Allow 0 for total host VFs - dmaengine: mcf-edma: Fix a potential un-allocated memory access - wifi: cfg80211: fix sband iftype data lookup for AP_VLAN - IB/hfi1: Fix possible panic during hotplug remove - drivers: net: prevent tun_build_skb() to exceed the packet size limit - dccp: fix data-race around dp->dccps_mss_cache - bonding: Fix incorrect deletion of ETH_P_8021AD protocol vid from slaves - net/packet: annotate data-races around tp->status - mISDN: Update parameter type of dsp_cmx_send() - selftests/rseq: Fix build with undefined __weak - drm/nouveau/disp: Revert a NULL check inside nouveau_connector_get_modes - x86: Move gds_ucode_mitigated() declaration to header - x86/mm: Fix VDSO and VVAR placement on 5-level paging machines - x86/cpu/amd: Enable Zenbleed fix for AMD Custom APU 0405
[Kernel-packages] [Bug 2039291] [NEW] Focal update: v5.4.254 upstream stable release
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 from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.254 upstream stable release
from git://git.kernel.org/
Linux 5.4.254
sch_netem: fix issues in netem_change() vs get_dist_table()
alpha: remove __init annotation from exported page_is_ram()
scsi: core: Fix possible memory leak if device_add() fails
scsi: snic: Fix possible memory leak if device_add() fails
scsi: 53c700: Check that command slot is not NULL
scsi: storvsc: Fix handling of virtual Fibre Channel timeouts
scsi: core: Fix legacy /proc parsing buffer overflow
netfilter: nf_tables: report use refcount overflow
nvme-rdma: fix potential unbalanced freeze & unfreeze
nvme-tcp: fix potential unbalanced freeze & unfreeze
btrfs: set cache_block_group_error if we find an error
btrfs: don't stop integrity writeback too early
ibmvnic: Handle DMA unmapping of login buffs in release functions
net/mlx5: Allow 0 for total host VFs
dmaengine: mcf-edma: Fix a potential un-allocated memory access
wifi: cfg80211: fix sband iftype data lookup for AP_VLAN
IB/hfi1: Fix possible panic during hotplug remove
drivers: net: prevent tun_build_skb() to exceed the packet size limit
dccp: fix data-race around dp->dccps_mss_cache
bonding: Fix incorrect deletion of ETH_P_8021AD protocol vid from slaves
net/packet: annotate data-races around tp->status
mISDN: Update parameter type of dsp_cmx_send()
selftests/rseq: Fix build with undefined __weak
drm/nouveau/disp: Revert a NULL check inside nouveau_connector_get_modes
x86: Move gds_ucode_mitigated() declaration to header
x86/mm: Fix VDSO and VVAR placement on 5-level paging machines
x86/cpu/amd: Enable Zenbleed fix for AMD Custom APU 0405
usb: common: usb-conn-gpio: Prevent bailing out if initial role is none
usb: dwc3: Properly handle processing of pending events
usb-storage: alauda: Fix uninit-value in alauda_check_media()
binder: fix memory leak in binder_init()
iio: cros_ec: Fix the allocation size for cros_ec_command
nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput
x86/pkeys: Revert a5eff7259790 ("x86/pkeys: Add PKRU value to init_fpstate")
radix tree test suite: fix incorrect allocation size for pthreads
drm/nouveau/gr: enable memory loads on helper invocation on all channels
dmaengine: pl330: Return DMA_PAUSED when transaction is paused
ipv6: adjust ndisc_is_useropt() to also return true for PIO
mmc: moxart: read scr register without changing byte order
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/2039291
Title:
Focal update: v5.4.254 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
New
Bug description:
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 from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.254 upstream stable release
from git://git.kernel.org/
Linux 5.4.254
sch_netem: fix issues in netem_change() vs get_dist_table()
alpha: remove __init annotation from exported page_is_ram()
scsi: core: Fix possible memory leak if device_add() fails
scsi: snic: Fix possible memory leak if device_add() fails
scsi: 53c700: Check that command slot is not NULL
scsi: storvsc: Fix handling of virtual Fibre Channel timeouts
scsi: core: Fix legacy /proc parsing buffer overflow
netfilter: nf_tables: report use refcount overflow
nvme-rdma: fix potential unbalanced freeze & unfreeze
nvme-tcp: fix potential unbalanced freeze & unfreeze
btrfs: set cache_block_group_error if we find an error
btrfs: don't stop integrity writeback too early
ibmvnic: Handle DMA unmapping of login buffs in release functions
net/mlx5: Allow 0 for total host VFs
dmaengine: mcf-edma: Fix a potential
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
Can you test the newest from -proposed (166) to confirm it is not the same bug? It's not TCG indeed but for now, I don't have other ideas. Will continue looking into it. -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039280] Re: Support IP address protocol
** Also affects: iproute2 (Ubuntu Mantic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP address protocol
Status in iproute2 package in Ubuntu:
New
Status in iproute2 source package in Mantic:
New
Bug description:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
Two clean upstream cherry-picks, regression potential should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039288] Status changed to Confirmed
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/2039288 Title: package linux-headers-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: installed linux-headers-6.2.0-34-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: Installing updates ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-34-generic 6.2.0-34.34 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rich 4129 F wireplumber /dev/snd/seq:rich 4124 F pipewire CasperMD5CheckResult: pass Date: Fri Oct 13 15:54:19 2023 ErrorMessage: installed linux-headers-6.2.0-34-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-07-20 (85 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) MachineType: Apple Inc. MacBookPro14,3 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=7a24893e-8dbd-4508-9f0e-725105a2ea4d ro quiet splash vt.handoff=7 initrd=\initrd.img-6.2.0-33-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: installed linux-headers-6.2.0-34-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 515.0.0.0.0 dmi.board.name: Mac-551B86E5744E2388 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro14,3 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-551B86E5744E2388 dmi.modalias: dmi:bvnAppleInc.:bvr515.0.0.0.0:bd06/02/2023:br0.1:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro14,3 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039288] [NEW] package linux-headers-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: installed linux-headers-6.2.0-34-generic package post-installation script subprocess
Public bug reported: Installing updates ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-34-generic 6.2.0-34.34 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rich 4129 F wireplumber /dev/snd/seq:rich 4124 F pipewire CasperMD5CheckResult: pass Date: Fri Oct 13 15:54:19 2023 ErrorMessage: installed linux-headers-6.2.0-34-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-07-20 (85 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) MachineType: Apple Inc. MacBookPro14,3 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=7a24893e-8dbd-4508-9f0e-725105a2ea4d ro quiet splash vt.handoff=7 initrd=\initrd.img-6.2.0-33-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: installed linux-headers-6.2.0-34-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 515.0.0.0.0 dmi.board.name: Mac-551B86E5744E2388 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro14,3 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-551B86E5744E2388 dmi.modalias: dmi:bvnAppleInc.:bvr515.0.0.0.0:bd06/02/2023:br0.1:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro14,3 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package lunar need-duplicate-check -- 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/2039288 Title: package linux-headers-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: installed linux-headers-6.2.0-34-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: Installing updates ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-34-generic 6.2.0-34.34 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rich 4129 F wireplumber /dev/snd/seq:rich 4124 F pipewire CasperMD5CheckResult: pass Date: Fri Oct 13 15:54:19 2023 ErrorMessage: installed linux-headers-6.2.0-34-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-07-20 (85 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) MachineType: Apple Inc. MacBookPro14,3 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=7a24893e-8dbd-4508-9f0e-725105a2ea4d ro quiet splash vt.handoff=7 initrd=\initrd.img-6.2.0-33-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: installed linux-headers-6.2.0-34-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 515.0.0.0.0 dmi.board.name: Mac-551B86E5744E2388 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro14,3 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-551B86E5744E2388 dmi.modalias: dmi:bvnAppleInc.:bvr515.0.0.0.0:bd06/02/2023:br0.1:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro14,3 dmi.product.version: 1.0
[Kernel-packages] [Bug 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
Removing Jammy from nominations as jammy:linux-gcp-6.2 and jammy:linux- aws-6.2 will be getting the patch via lunar:linux-gcp and lunar:linux- aws respectively. ** No longer affects: linux-gcp (Ubuntu Jammy) ** No longer affects: linux-aws (Ubuntu Jammy) -- 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/2039191 Title: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization Status in linux-aws package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Triaged Status in linux-aws source package in Lunar: Triaged Status in linux-gcp source package in Lunar: Triaged Status in linux-aws source package in Mantic: In Progress Status in linux-gcp source package in Mantic: Triaged Bug description: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
** Changed in: linux-gcp (Ubuntu Jammy) Status: New => Triaged ** Changed in: linux-gcp (Ubuntu Lunar) Status: New => Triaged ** Changed in: linux-gcp (Ubuntu Mantic) Status: New => Triaged ** Changed in: linux-aws (Ubuntu Lunar) Status: New => Triaged ** Changed in: linux-aws (Ubuntu Jammy) Status: New => Triaged -- 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/2039191 Title: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization Status in linux-aws package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Triaged Status in linux-aws source package in Jammy: Triaged Status in linux-gcp source package in Jammy: Triaged Status in linux-aws source package in Lunar: Triaged Status in linux-gcp source package in Lunar: Triaged Status in linux-aws source package in Mantic: In Progress Status in linux-gcp source package in Mantic: Triaged Bug description: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1006.6 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-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- 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/2038567 Title: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Triaged Status in snapd package in Ubuntu: Confirmed Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038981] Re: No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1006.6 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-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038981 Title: No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] With ADM 6300 GPU, there is no external output when plug in a DP monitor after the monitor went to sleep [Fix] Mario provides a patch to fix the issue https://patchwork.kernel.org/project/linux-usb/list/?series=790399 And also below commit is required 134b8c5d8674 drm/amd: Fix detection of _PR3 on the PCIe root port [Test case] 1. Boot up the system with AMD 6300 GPU and plug DP monitor on the card 2. Unplug the DP cable and wait the monitor sleeps 3. Plug in the DP cable again and it should wake up the monitor correctly and output the screen to the monitor [Where problems could occur] The PR3 patch only affects AMD dGPU and should fix AMD BOCO detection logic, and UCSI patch try to set the correct power supply scope which should do no harm to the existing systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039280] Re: Support IP address protocol
** Patch added: "iproute2_6.1.0-1ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+attachment/5709212/+files/iproute2_6.1.0-1ubuntu3.debdiff
** Description changed:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
- Two clean upstream cherry-picks so regression potential is low.
+ Two clean upstream cherry-picks, low regression potential is low.
** Description changed:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
- Two clean upstream cherry-picks, low regression potential is low.
+ Two clean upstream cherry-picks, regression potential should be low.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP address protocol
Status in iproute2 package in Ubuntu:
New
Bug description:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
Two clean upstream cherry-picks, regression potential should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 2039280] Re: Support IP address protocol
** Description changed:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
-
+
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
-
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
- Alternativerly, you could download Linux v6.5 and run:
+ Alternativerly, you could download Linux v6.5 source code and run:
- $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t
- kci_test_address_proto
-
+ $ cd linux
+ $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
The cherry-picked patches are 2 upstream commits so regression potential
is low.
** Description changed:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
- The cherry-picked patches are 2 upstream commits so regression potential
- is low.
+ Two clean upstream cherry-picks so regression potential is low.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP address protocol
Status in iproute2 package in Ubuntu:
New
Bug description:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
Two clean upstream cherry-picks so regression potential is low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039280] [NEW] Support IP address protocol
Public bug reported:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 and run:
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t
kci_test_address_proto
[Regression potential]
The cherry-picked patches are 2 upstream commits so regression potential
is low.
** Affects: iproute2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP address protocol
Status in iproute2 package in Ubuntu:
New
Bug description:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 and run:
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t
kci_test_address_proto
[Regression potential]
The cherry-picked patches are 2 upstream commits so regression
potential is low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039278] [NEW] Consistent naming of onboard NIC on all Pi on all Ubuntu
Public bug reported: Consistent naming of onboard NIC on all Pi on all Ubuntu We should have the one distro config, to force consistent oboard NIC naming on all Pi on all Ubuntu in the one place. Let's find all the puzzle pieces and do it onces, and for all ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd-hwe (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-raspi-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-raspi-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd-hwe (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu) Milestone: None => later -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2039278 Title: Consistent naming of onboard NIC on all Pi on all Ubuntu Status in linux-raspi package in Ubuntu: New Status in systemd package in Ubuntu: New Status in systemd-hwe package in Ubuntu: New Status in ubuntu-raspi-settings package in Ubuntu: New Bug description: Consistent naming of onboard NIC on all Pi on all Ubuntu We should have the one distro config, to force consistent oboard NIC naming on all Pi on all Ubuntu in the one place. Let's find all the puzzle pieces and do it onces, and for all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2039278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
> Probably the version installed was 5.4.0-162. Yes, you are probably right. I was only looking at the date of the kernel file. The bug is reproducible with Linux 5.4.0-164.181, however. > I checked some discussions from here https://gitlab.com/qemu- project/qemu/-/issues/1696 and it seems it's similar. I have discusses the problem with Richard Jones here: https://bugzilla.redhat.com/show_bug.cgi?id=2241293 He claims the issue in this bug report is not the same bug as you refer to. Se his last comment. ** Bug watch added: Red Hat Bugzilla #2241293 https://bugzilla.redhat.com/show_bug.cgi?id=2241293 -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
** Attachment added: "dmesg_i8042.debug_i8042.nopnp_i8042.noaux_i8042.nomux.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+attachment/5709207/+files/dmesg_i8042.debug_i8042.nopnp_i8042.noaux_i8042.nomux.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
** Attachment added: "dmesg_i8042.debug_i8042.nopnp.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+attachment/5709206/+files/dmesg_i8042.debug_i8042.nopnp.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
** Attachment added: "dmesg_i8042.debug_i8042.nopnp_i8042.noaux.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+attachment/5709205/+files/dmesg_i8042.debug_i8042.nopnp_i8042.noaux.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
** Attachment added: "dmesg_i8042.debug.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+attachment/5709204/+files/dmesg_i8042.debug.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
I have this laptop (V15 AMN on R3 7320U / 16G RAM), have built 6.5.7 kernel with all I2C drivers. Uploading several of dmesg dump files with different parameters and xinput dump file. Hope we will see a fix soon. Also can notice, "extra buttons" kind of working, even can setup screen brightness. Also keyboard is responding to Numpad, Caps Lock states (duplicating it from USB keyboard) ** Attachment added: "xinput.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+attachment/5709203/+files/xinput.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
On the 1st of September, we started preparing 164, it was released last week. Probably the version installed was 5.4.0-162. Could you try this with the version from -proposed? It's 5.4.0-166.183. I checked some discussions from here https://gitlab.com/qemu-project/qemu/-/issues/1696 and it seems it's similar. The fix "tick/common: Align tick period during sched_timer setup" just landed in -proposed. To install a kernel from -proposed, I include -proposed to the apt-repository list: sudo add-apt-repository ppa:canonical-kernel-team/proposed And then install the desired version. You can also check this official page for more info on how to test from -proposed pocket. https://wiki.ubuntu.com/Testing/EnableProposed ** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #1696 https://gitlab.com/qemu-project/qemu/-/issues/1696 -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
** Changed in: ubuntu-release-notes Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in Release Notes for Ubuntu: Fix Released Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Invalid Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
We have live updates with unattended updates. Our first recording of this problem is Sept. 5th, so this points towards Linux 5.4.0-164.181 being the culprit unless you updated this package just a few days before. Linux 5.4.0-164.181 was installed on our systems Sept 1st, and this has been a problem ever since. We do thousands of runs each day, so if this bug had occurred earlier, we would have noticed. -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
Can you tell us from which version you upgraded to 164? It would be helpful to narrow down what changes happened in between. -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038248] Please test proposed package
Hello Chengen, or anyone else affected,
Accepted makedumpfile into jammy-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.7.0-1ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/2038248
Title:
Slab page exclusion issue on Linux 6.2-rc1
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Jammy:
Fix Committed
Status in makedumpfile source package in Lunar:
Fix Committed
Bug description:
[Impact]
The kernel crashdumps generated by makedumpfile on kernel 6.2
(affects Lunar, and Jammy with the HWE kernel) might not open
on crash, due to kernel changes not reflected in makedumpfile.
The Kernel commit 130d4df57390 ("mm/sl[au]b: rearrange struct slab fields to
allow larger rcu_head"), included in Linux 6.2-rc1 and later versions,
introduced a change that aligns the offset of slab.slabs with that of
page.mapping.
However, this modification unintentionally causes the makedumpfile command
with the -d 8 option, meant to exclude user data, to incorrectly exclude
certain slab pages.
Consequently, when utilizing dumpfiles generated in this manner, the "crash"
utility may encounter an error when attempting to initiate a session:
crash: page excluded: kernel virtual address: e269d428 type:
"xa_node shift"
[Fix]
An upstream fix is available.
==
commit 5f17bdd2128998a3eeeb4521d136a19fadb6
Author: Kazuhito Hagio
Date: Wed Dec 21 11:06:39 2022 +0900
[PATCH] Fix wrong exclusion of slab pages on Linux 6.2-rc1
==
[Test Plan]
1. Install the required packages and then proceed to reboot the machine.
# sudo apt install crash linux-crashdump -y
# reboot
2. To check the status of kdump, use the `kdump-config show` command.
# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_COREDIR:/var/crash
crashkernel addr: 0x6400
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to
/var/lib/kdump/initrd.img-6.2.0-33-generic
current state:ready to kdump
kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
3. To trigger a crash dump forcefully, execute the `echo c | sudo tee
/proc/sysrq-trigger` command.
4. Download the kernel .ddeb file, which will be used for analyzing the dump
file.
# sudo -i
# cd /var/crash
# pull-lp-ddebs linux-image-unsigned-$(uname -r)
# dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
5. Utilize the "crash" utility to parse and analyze the dump file.
# crash dbgsym-$(uname -r)/usr/lib/debug/boot/vmlinux-$(uname -r)
/dump.
...
please wait... (gathering task table data)
crash: page excluded: kernel virtual address: e269d428 type:
"xa_node shift"
[Where problems could occur]
The patch has altered the method for excluding slab pages, aligning with the
structural changes introduced in Linux 6.2-rc1.
This modification is essential for Linux kernel 6.2.
However, it's crucial to note that this change may impact the content of the
dump file, potentially leading to a situation where the "crash" utility is
unable to parse it in the worst-case scenario.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/2038248/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to :
[Kernel-packages] [Bug 2038248] Re: Slab page exclusion issue on Linux 6.2-rc1
Hello Chengen, or anyone else affected,
Accepted makedumpfile into lunar-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.7.2-1ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
lunar to verification-done-lunar. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-lunar. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: makedumpfile (Ubuntu Lunar)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-lunar
** Changed in: makedumpfile (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/2038248
Title:
Slab page exclusion issue on Linux 6.2-rc1
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Jammy:
Fix Committed
Status in makedumpfile source package in Lunar:
Fix Committed
Bug description:
[Impact]
The kernel crashdumps generated by makedumpfile on kernel 6.2
(affects Lunar, and Jammy with the HWE kernel) might not open
on crash, due to kernel changes not reflected in makedumpfile.
The Kernel commit 130d4df57390 ("mm/sl[au]b: rearrange struct slab fields to
allow larger rcu_head"), included in Linux 6.2-rc1 and later versions,
introduced a change that aligns the offset of slab.slabs with that of
page.mapping.
However, this modification unintentionally causes the makedumpfile command
with the -d 8 option, meant to exclude user data, to incorrectly exclude
certain slab pages.
Consequently, when utilizing dumpfiles generated in this manner, the "crash"
utility may encounter an error when attempting to initiate a session:
crash: page excluded: kernel virtual address: e269d428 type:
"xa_node shift"
[Fix]
An upstream fix is available.
==
commit 5f17bdd2128998a3eeeb4521d136a19fadb6
Author: Kazuhito Hagio
Date: Wed Dec 21 11:06:39 2022 +0900
[PATCH] Fix wrong exclusion of slab pages on Linux 6.2-rc1
==
[Test Plan]
1. Install the required packages and then proceed to reboot the machine.
# sudo apt install crash linux-crashdump -y
# reboot
2. To check the status of kdump, use the `kdump-config show` command.
# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_COREDIR:/var/crash
crashkernel addr: 0x6400
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to
/var/lib/kdump/initrd.img-6.2.0-33-generic
current state:ready to kdump
kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
3. To trigger a crash dump forcefully, execute the `echo c | sudo tee
/proc/sysrq-trigger` command.
4. Download the kernel .ddeb file, which will be used for analyzing the dump
file.
# sudo -i
# cd /var/crash
# pull-lp-ddebs linux-image-unsigned-$(uname -r)
# dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
5. Utilize the "crash" utility to parse and analyze the dump file.
# crash dbgsym-$(uname -r)/usr/lib/debug/boot/vmlinux-$(uname -r)
/dump.
...
please wait... (gathering task table data)
crash: page excluded: kernel virtual address: e269d428 type:
"xa_node shift"
[Where problems could occur]
The patch has altered the method for excluding slab pages, aligning with the
structural changes introduced in Linux 6.2-rc1.
This modification is essential for Linux kernel 6.2.
However, it's crucial to note that this change may impact the content of the
dump file, potentially leading to a situation where the "crash"
[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
Reply #2 ~~~ $ uname -a Linux 6.5.0-1005-oem #5-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 6 12:13:41 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec 0 $ sudo rtcwake -m mem -s 5 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Oct 13 11:09:41 2023 $ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec 4127220 ~~~ Reply #1 ~~~ $ uname -a Linux 6.1.0-1024-oem #24-Ubuntu SMP PREEMPT_DYNAMIC Wed Oct 4 10:18:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec [sudo] password for u: 4127220 $ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec 4127220 $ sudo rtcwake -m mem -s 5 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Oct 13 11:27:32 2023 $ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec 4800390 ~~~ ** Tags removed: verification-needed-jammy-linux-oem-6.1 ** Tags added: verification-done-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
Reply #2 ~~~ u@u-OptiPlex-SFF-7010:~$ uname -a Linux u-OptiPlex-SFF-7010 6.5.0-1005-oem #5-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 6 12:13:41 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux u@u-OptiPlex-SFF-7010:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec 0 u@u-OptiPlex-SFF-7010:~$ sudo rtcwake -m mem -s 5 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Oct 13 11:09:41 2023 u@u-OptiPlex-SFF-7010:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec 4127220 ~~~ ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
This is a successfull boot of qemu. ** Attachment added: "log89" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+attachment/5709154/+files/log89 -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
This is a failing boot of qemu that we killed after some time. ** Attachment added: "log90" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+attachment/5709155/+files/log90 -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709152/+files/acpidump.txt ** 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
We managed to reproduce the failure on a fresh install of Ubuntu 20.04
using this script. It occurred already on the 90th iteration.
---
for i in {1..1}
do
echo Run $i
guestfish -vx -a /dev/null run >& log$i
done
---
Here is what we did after booting a fresh install
apt update
apt upgrade
apt install qemu-system-x86
apt install libguestfs-tools
(rebooted the server and ran the script above)
--
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/2039258
Title:
qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
Status in linux package in Ubuntu:
Confirmed
Bug description:
We have a number of Ubuntu 20.04 servers that have recently been
upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27.
About 1/1000 boots of qemu results in a failed boot hanging at 100%
CPU indefinately. A number of our utilities are using qemu for
processing, so we get a lot of processes spinning at 100% that we need
to clean up regularly.
Ubuntu: 20.04
Linux: 5.4.0-164.181
Qemu: 4.2-3ubuntu6.27
This problem was not seen before the release of Linux. 5.4.0-164.181
on sept. 1.
What you expected to happen: Qemu boots linux reliably.
What happened instead: Qemu hangs at 100% indefinately.
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-164-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: linux (not installed)
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic
root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0
netcfg/do_not_use_netplan=true
ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248
RelatedPackageVersions:
linux-restricted-modules-5.4.0-164-generic N/A
linux-backports-modules-5.4.0-164-generic N/A
linux-firmware 1.187.39
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: focal
Uname: Linux 5.4.0-164-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-4.2
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-4.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709151/+files/WifiSyslog.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709150/+files/UdevDb.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709147/+files/ProcEnviron.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709148/+files/ProcInterrupts.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709149/+files/ProcModules.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709143/+files/Lsusb-v.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709145/+files/ProcCpuinfo.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709146/+files/ProcCpuinfoMinimal.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709144/+files/PciMultimedia.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709142/+files/Lspci-vt.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709140/+files/CurrentDmesg.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709139/+files/Card0.Codecs.codec.0.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709141/+files/Lspci.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709138/+files/CRDA.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
apport information ** Tags added: apport-collected focal ** Description changed: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. + --- + ProblemType: Bug + AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.27 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' + Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Lsusb-t: + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + ProcFB: 0 cirrusdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true + ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-164-generic N/A + linux-backports-modules-5.4.0-164-generic N/A + linux-firmware 1.187.39 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal + Uname: Linux 5.4.0-164-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 04/01/2014 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: 1.13.0-1ubuntu1.1 + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-i440fx-4.2 + dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: + dmi.product.name: Standard PC (i440FX + PIIX, 1996) + dmi.product.version: pc-i440fx-4.2 + dmi.sys.vendor: QEMU ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709137/+files/AlsaDevices.txt -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus
[Kernel-packages] [Bug 2036184] Re: Infinite systemd loop when power off the machine with multiple MD RAIDs
** Tags removed: verification-needed-jammy-linux-oem-6.1
** Tags added: verification-done-jammy-linux-oem-6.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2036184
Title:
Infinite systemd loop when power off the machine with multiple MD
RAIDs
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
The system with multiple MD RAIDs sometimes hangs while rebooting, that's
because of the systemd can't stop and close the MD disk.
[Fix]
This commit fixes the issue, and this issue has been introduced by
12a6caf27324 ("md: only delete entries from all_mddevs when the disk is freed")
after v6.0
https://patchwork.kernel.org/project/linux-
raid/patch/20230914152416.10819-1-mariusz.tkac...@linux.intel.com/
[Test case]
1. Reboot the system with multiple MD RAIDs at least 10 times.
2. Make sure the system can reboot successfully every time.
3. You should not see error messages like below.
[ 205.360738] systemd-shutdown[1]: Stopping MD devices.
[ 205.366384] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs
[ 205.373327] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus
[ 205.380427] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class
[ 205.388257] systemd-shutdown[1]: Stopping MD /dev/md127 (9:127).
[ 205.394880] systemd-shutdown[1]: Failed to sync MD block device /dev/md127,
ignoring: Input/output error
[ 205.404975] md: md127 stopped.
[ 205.470491] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126).
[ 205.770179] md: md126: resync interrupted.
[ 205.776258] md126: detected capacity change from 1900396544 to 0
[ 205.783349] md: md126 stopped.
[ 205.862258] systemd-shutdown[1]: Stopping MD /dev/md125 (9:125).
[ 205.862435] md: md126 stopped.
[ 205.868376] systemd-shutdown[1]: Failed to sync MD block device /dev/md125,
ignoring: Input/output error
[ 205.872845] block device autoloading is deprecated and will be removed.
[ 205.880955] md: md125 stopped.
[ 205.934349] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:7).
[ 205.947707] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or
resource busy
[ 205.957004] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:6).
[ 205.964177] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or
resource busy
[ 205.973155] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124).
[ 205.979789] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or
resource busy
[ 205.988475] systemd-shutdown[1]: Not all MD devices stopped, 4 left.
[Where problems could occur]
It fixes the data race issue, should not introduce any regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2036184/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Missing required logs.
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 2039258 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Incomplete Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] [NEW] qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
Public bug reported: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: New Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
On 23.04 the microphone is working already. I have tried to upgrade yesterday to 23.10, but the install windows are not appearing properly, so cannot see the steps. (With the updater tool the upgrade did not appear yet.) The other windows on the live DVD, like Libre Office, or the settings windows work properly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
** Changed in: linux-aws (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux-aws (Ubuntu Mantic) Status: New => In Progress -- 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/2039191 Title: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization Status in linux-aws package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: New Status in linux-aws source package in Jammy: New Status in linux-gcp source package in Jammy: New Status in linux-aws source package in Lunar: New Status in linux-gcp source package in Lunar: New Status in linux-aws source package in Mantic: In Progress Status in linux-gcp source package in Mantic: New Bug description: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
