[Kernel-packages] [Bug 2008050] Re: bmc virtual usb keyboard/mouse can't be detected when resting bmc
The dmesg for virutal keyboad/mouse when reset os: Feb 19 20:55:17 sysadmin kernel: [4.904530] usb 1-7.1: New USB device found, idVendor=046b, idProduct=ff10, bcdDevice= 1.00 Feb 19 20:55:17 sysadmin kernel: [4.904955] usb 1-7.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 19 20:55:17 sysadmin kernel: [4.905370] usb 1-7.1: Product: Virtual Keyboard and Mouse Feb 19 20:55:17 sysadmin kernel: [4.905779] usb 1-7.1: Manufacturer: American Megatrends Inc. Feb 19 20:55:17 sysadmin kernel: [4.916508] nouveau :17:00.0: fb: 15360 MiB GDDR6 Feb 19 20:55:17 sysadmin kernel: [4.917164] hidraw: raw HID events driver (C) Jiri Kosina Feb 19 20:55:17 sysadmin kernel: [4.922070] usbcore: registered new interface driver usbhid Feb 19 20:55:17 sysadmin kernel: [4.922534] usbhid: USB HID core driver Feb 19 20:55:17 sysadmin kernel: [4.924758] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci:00/:00:14.0/usb1/1-7/1-7.1/1-7.1:1.0/0003:046B:FF10. 0001/input/input1 Feb 19 20:55:17 sysadmin kernel: [4.925350] nouveau :17:00.0: DRM: VRAM: 15360 MiB Feb 19 20:55:17 sysadmin kernel: [4.925677] hid-generic 0003:046B:FF10.0001: input,hidraw0: USB HID v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-000 0:00:14.0-7.1/input0 Feb 19 20:55:17 sysadmin kernel: [4.926066] nouveau :17:00.0: DRM: GART: 536870912 MiB Feb 19 20:55:17 sysadmin kernel: [4.927045] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci:00/:00:14.0/usb1/1-7/1-7.1/1-7.1:1.1/0003:046B:FF10. 0002/input/input2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2008050 Title: bmc virtual usb keyboard/mouse can't be detected when resting bmc Status in linux-hwe-5.4 package in Ubuntu: New Bug description: In zte server, when reseting bmc or reload virtual keyboard/mouse driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume working after reboot host OS which is Ubuntu 20.04 ga-kernel. This wouldn't happen on CentOS with kernel of 3.10.0-1160.317.x86_64, the keyboard/mouse of KVM keeps working when resting ibm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2008050/+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 2008050] Re: bmc virtual usb keyboard/mouse can't be detected when resting bmc
We also tested virtual CD, it seems worked fine. Below is udevadm monitor output: KERNEL[310.544164] unbind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) KERNEL[310.544206] remove /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) KERNEL[310.544691] unbind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) KERNEL[310.544737] remove /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) UDEV [310.545677] unbind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) UDEV [310.546176] remove /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) UDEV [310.547452] unbind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) UDEV [310.547917] remove /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) KERNEL[324.302442] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) KERNEL[324.303754] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) KERNEL[324.304074] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14 (scsi) KERNEL[324.304193] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/scsi_host/host14 (scsi_host) KERNEL[324.304238] bind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) KERNEL[324.304384] bind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) UDEV [324.306827] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) UDEV [324.308683] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) UDEV [324.309922] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14 (scsi) UDEV [324.311232] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/scsi_host/host14 (scsi_host) UDEV [324.312534] bind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) UDEV [324.314064] bind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) KERNEL[325.337392] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0 (scsi) KERNEL[325.337466] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0 (scsi) UDEV [325.338773] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0 (scsi) UDEV [325.340412] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0 (scsi) KERNEL[325.388105] add /devices/virtual/bdi/11:0 (bdi) KERNEL[325.388215] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/block/sr0 (block) UDEV [325.388841] add /devices/virtual/bdi/11:0 (bdi) KERNEL[325.389407] add /kernel/slab/bdev_cache/cgroup/bdev_cache(310:systemd-udevd.service) (cgroup) KERNEL[325.389936] bind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0 (scsi) KERNEL[325.389997] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/scsi_device/14:0:0:0 (scsi_device) KERNEL[325.390106] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/scsi_generic/sg7 (scsi_generic) UDEV [325.390135] add /kernel/slab/bdev_cache/cgroup/bdev_cache(310:systemd-udevd.service) (cgroup) KERNEL[325.390209] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/bsg/14:0:0:0 (bsg) KERNEL[325.432910] change /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/block/sr0 (block) UDEV [326.956962] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/block/sr0 (block) UDEV [326.958339] bind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0 (scsi) UDEV [326.960110] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/scsi_device/14:0:0:0 (scsi_device) UDEV [326.960752] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/scsi_generic/sg7 (scsi_generic) UDEV [326.962490] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/bsg/14:0:0:0 (bsg) UDEV [329.655233] change /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/block/sr0 (block) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2008050 Title: bmc virtual usb keyboard/mouse can't be detected when resting bmc Status in linux-hwe-5.4 package in Ubuntu: New Bug description: In zte server, when reseting bmc or reload virtual keyboard/mouse driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume working after reboot host OS which is Ubuntu 20.04 ga-kernel. This wouldn't happen on CentOS with kernel of 3.10.0-1160.3
[Kernel-packages] [Bug 2008050] Re: bmc virtual usb keyboard/mouse can't be detected when resting bmc
During testing, we can found disconnect log in dmesg and not plugin/connect info: Feb 19 21:14:16 sysadmin kernel: [ 1156.328006] usb 1-7.1: USB disconnect, device number 3 Feb 19 21:17:01 sysadmin CRON[6201]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 19 21:22:15 sysadmin systemd-sysctl[1446]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Feb 19 21:22:15 sysadmin systemd-sysctl[1446]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Feb 19 21:22:15 sysadmin kernel: [0.00] Linux version 5.4.0-26-generic (buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 (Ubuntu 5.4.0-26.30-generic 5.4.30) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2008050 Title: bmc virtual usb keyboard/mouse can't be detected when resting bmc Status in linux-hwe-5.4 package in Ubuntu: New Bug description: In zte server, when reseting bmc or reload virtual keyboard/mouse driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume working after reboot host OS which is Ubuntu 20.04 ga-kernel. This wouldn't happen on CentOS with kernel of 3.10.0-1160.317.x86_64, the keyboard/mouse of KVM keeps working when resting ibm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2008050/+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 2008050] [NEW] bmc virtual usb keyboard/mouse can't be detected when resting bmc
Public bug reported: In zte server, when reseting bmc or reload virtual keyboard/mouse driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume working after reboot host OS which is Ubuntu 20.04 ga-kernel. This wouldn't happen on CentOS with kernel of 3.10.0-1160.317.x86_64, the keyboard/mouse of KVM keeps working when resting ibm. ** Affects: linux-hwe-5.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2008050 Title: bmc virtual usb keyboard/mouse can't be detected when resting bmc Status in linux-hwe-5.4 package in Ubuntu: New Bug description: In zte server, when reseting bmc or reload virtual keyboard/mouse driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume working after reboot host OS which is Ubuntu 20.04 ga-kernel. This wouldn't happen on CentOS with kernel of 3.10.0-1160.317.x86_64, the keyboard/mouse of KVM keeps working when resting ibm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2008050/+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 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
** Description changed: + == SRU Justification == + [Impact] + Audio playback becomes silent on some Intel SoF systems. + + [Fix] + Revert offending commit. + + [Test] + The speaker can always play sound after the commit gets reverted. + + [Where problems could occur] + Audio on linux 5.15 has been working fine without the patch for a long + time, so this only restore it to where it was. + + == Original Bug Report == [Summary] During the kernel SRU testing on focal-hwe, I found the audio output of some machines are broken. I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and haven't seen this happened. The volume bars in settings react to what sound is played correctly and device is detected as well. [Reproduce steps] 1. install focal 2. enable -proposed 3. run apt dist-upgrade. 4. reboot. 5. press fn keys to volume up then volume down or play a short youtube video. 6. after a while can't hear any sound from the speaker. [Failure rate] 10/10 [Additional info] If I run "sudo alsa force-reload" can make audio work again, but after a while it breaks again. These are machines that impacted by this bug: https://certification.canonical.com/hardware/202007-28045/ https://certification.canonical.com/hardware/201906-27109/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/202007-28047/ https://certification.canonical.com/hardware/202007-28055/ https://certification.canonical.com/hardware/202005-27899/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu 1303 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1303 F pulseaudio CasperMD5CheckResult: skip Date: Sun Feb 19 21:24:59 2023 InstallationDate: Installed on 2020-08-03 (930 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Feb 19 20:53:23 dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.product.sku: 0922 dmi.sys.vendor: Dell Inc. ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- 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/2007798 Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Confirmed Bug description: == SRU Justification == [Impact] Audio playback becomes silent on some Intel SoF systems. [Fix] Revert offending commit. [Test] The speaker can always play sound after the commit gets reverted. [Where problems could occur] Audio on linux 5.15 has been working fine without the patch for a long time, so this only restore it to where it was. == Original Bug Report == [Summary] During the kernel SRU testing on focal-hwe, I found the audio output of some machines are broken. I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and haven't seen this happened. The volume bars in settings react to what sound is played correctly and device is detected as well. [Reproduce steps] 1. install focal 2. enable -proposed 3. run apt dist-upgrade. 4. reboot. 5. press fn keys to volume up then volume down or play a
[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400
- Which mode does Windows use? PSR1 or PSR2? - Does the panel generate IRQ correctly under Windows? -- 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/2007516 Title: XPS 9320 screen flicker on UHD panel 3840x2400 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2007516/+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 2000404] Re: First time user trackpad not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000404 Title: First time user trackpad not working Status in linux package in Ubuntu: Expired Bug description: Hello, I'm a first time user and this is a new laptop. It seems my trackpad stop working after a really short time. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abonifacio 2134 F pulseaudio /dev/snd/controlC1: abonifacio 2134 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Fri Dec 23 18:10:55 2022 InstallationDate: Installed on 2022-12-23 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82RF ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=2a665ddf-863e-408f-a9b6-9fdf3373ae04 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 11/16/2022 dmi.bios.release: 1.48 dmi.bios.vendor: LENOVO dmi.bios.version: J2CN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 5 Pro 16IAH7H dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvrJ2CN48WW:bd11/16/2022:br1.48:efr1.48:svnLENOVO:pn82RF:pvrLegion5Pro16IAH7H:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegion5Pro16IAH7H:skuLENOVO_MT_82RF_BU_idea_FM_Legion5Pro16IAH7H: dmi.product.family: Legion 5 Pro 16IAH7H dmi.product.name: 82RF dmi.product.sku: LENOVO_MT_82RF_BU_idea_FM_Legion 5 Pro 16IAH7H dmi.product.version: Legion 5 Pro 16IAH7H dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000404/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Tested on machine with FM350 installed, with oem 6.0.0-1006 kernel, modem manager 1.20.0-1~ubuntu22.04.1, libmbim-glib4 1.28.0-1~ubuntu20.04 and libqmi-glib5 1.32.0-1~ubuntu0.22.04.1. System can connect to 5g network. --- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: b429ecd3cf5b14431f765b3a415cda29db1d504b --- Hardware | manufacturer: generic | model: MBIM [14C3:4D75] | firmware revision: 81600..00.29.21.24_GC | D47 | h/w revision: V1.0.6 | supported: gsm-umts, lte, 5gnr |current: gsm-umts, lte, 5gnr | equipment id: 358198520003138 --- System| device: /sys/devices/pci:00/:00:1c.0/:71:00.0 |drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 | ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) --- Status| lock: sim-pin2 | unlock retries: sim-pin2 (3) | state: connected |power state: on |access tech: lte, 5gnr | signal quality: 64% (cached) --- Modes | supported: allowed: 3g; preferred: none | allowed: 4g; preferred: none | allowed: 3g, 4g; preferred: none | allowed: 5g; preferred: none | allowed: 3g, 5g; preferred: none | allowed: 4g, 5g; preferred: none | allowed: 3g, 4g, 5g; preferred: none |current: allowed: 3g, 4g, 5g; preferred: none --- IP| supported: ipv4, ipv6, ipv4v6 --- 3GPP | imei: 358198520003138 | enabled locks: fixed-dialing |operator id: 46692 | operator name: Chunghwa Telecom | registration: home | packet service state: attached --- 3GPP EPS | ue mode of operation: csps-2 |initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 | initial bearer apn: internet | initial bearer ip type: ipv4v6 --- 3GPP 5GNR | mico mode: disabled --- SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 (active) | slot 2: /org/freedesktop/ModemManager1/SIM/1 --- Bearer| paths: /org/freedesktop/ModemManager1/Bearer/1 ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Jammy: Fix Committed Status in libqmi source package in Jammy: Fix Committed Status in linux source package in Jammy: New Status in modemmanager source package in Jammy: Fix Committed Bug description: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case - install modemmanager, libmbim, and libqmi from -proposed - reboot and try WWAN function to see if any regression there. - perform dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) The verification should be done on FM350 to ensure it's correctly handled but also on other hardware to verify that there are no regressions * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no regression. --- :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01)
[Kernel-packages] [Bug 2007840] 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 2007840 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/2007840 Title: Cheese camera needs update Status in linux package in Ubuntu: Incomplete Bug description: I have a nexigo N95OP web 4k camera it worked in previous editions of linux ubuntu. cheese simply provides an error in the newest version of ubuntu. Description: Ubuntu 22.10 Release: 22.10 Ubuntu 5.19.0-31.32-generic 5.19.17 cheese: Installed: 43~alpha-1 Candidate: 43~alpha-1 Version table: *** 43~alpha-1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3e0f] (rev 08) DeviceName: Onboard - Other Subsystem: Hewlett-Packard Company Device [103c:8446] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore Kernel modules: ie31200_edac 00:02.0 VGA compatible controller [0300]: Intel Corporation CoffeeLake-S GT1 [UHD Graphics 610] [8086:3e93] (prog-if 00 [VGA controller]) DeviceName: Onboard - Video Subsystem: Hewlett-Packard Company CoffeeLake-S GT1 [UHD Graphics 610] [103c:8446] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 10BitTagReq- OBFF Disabled, AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911] DeviceName: Onboard - Other Subsystem: Hewlett-Packard Company Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [103c:8446] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 RAM memory [0500]: Intel Corporation Cannon Lake PCH Shared SRAM [8086:a36f] (rev 10) DeviceName: Onboard - Other Subsystem: Intel Cor
[Kernel-packages] [Bug 2007840] Re: Cheese camera needs update
** 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/2007840 Title: Cheese camera needs update Status in linux package in Ubuntu: New Bug description: I have a nexigo N95OP web 4k camera it worked in previous editions of linux ubuntu. cheese simply provides an error in the newest version of ubuntu. Description: Ubuntu 22.10 Release: 22.10 Ubuntu 5.19.0-31.32-generic 5.19.17 cheese: Installed: 43~alpha-1 Candidate: 43~alpha-1 Version table: *** 43~alpha-1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3e0f] (rev 08) DeviceName: Onboard - Other Subsystem: Hewlett-Packard Company Device [103c:8446] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore Kernel modules: ie31200_edac 00:02.0 VGA compatible controller [0300]: Intel Corporation CoffeeLake-S GT1 [UHD Graphics 610] [8086:3e93] (prog-if 00 [VGA controller]) DeviceName: Onboard - Video Subsystem: Hewlett-Packard Company CoffeeLake-S GT1 [UHD Graphics 610] [103c:8446] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 10BitTagReq- OBFF Disabled, AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911] DeviceName: Onboard - Other Subsystem: Hewlett-Packard Company Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [103c:8446] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 RAM memory [0500]: Intel Corporation Cannon Lake PCH Shared SRAM [8086:a36f] (rev 10) DeviceName: Onboard - Other Subsystem: Intel Corporation Cannon Lake PCH Shared SRAM [8086:7270] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 SATA controller [0106]: Intel Corporation Cannon Lake PCH SATA AHCI Controller [8086:a352] (rev 10) (prog-if 01 [AHCI 1.0]) DeviceName: Onboard - SATA Subsystem: Hewlett-Packard Company Cannon Lake PCH SA
[Kernel-packages] [Bug 2008037] Re: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350
This was found at 20.04.1 ga-kernel of 5.15.0-60 which is lasted at the time and on a new intel cpu of Intel(R) Xeon(R) Gold 6438Y+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008037 Title: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: Kernel taitned 512 ude to warning of below: #grep taint /var/log/syslog -b2 235407-Feb 20 15:27:14 xfusion kernel: [3.779483] WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 235561-Feb 20 15:27:14 xfusion kernel: [3.779495] Modules linked in: 235627:Feb 20 15:27:14 xfusion kernel: [3.779499] CPU: 64 PID: 1 Comm: swapper/0 Not tainted 5.15.0-60-generic #66-Ubuntu 235746-Feb 20 15:27:14 xfusion kernel: [3.779505] Hardware name: XFUSION 2288 V7/BC15MBSC, BIOS 2.00.20.Btg 02/08/2023 235862-Feb 20 15:27:14 xfusion kernel: [3.779509] RIP: 0010:uncore_insert_box_info+0x134/0x350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2008037/+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 2008037] Re: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350
#grep -i 'call trace' /var/log/dmesg -b19 113581-[3.779479] kernel: [ cut here ] 113641-[3.779483] kernel: WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 113771-[3.779495] kernel: Modules linked in: 113813-[3.779499] kernel: CPU: 64 PID: 1 Comm: swapper/0 Not tainted 5.15.0-60-generic #66-Ubuntu 113908-[3.779505] kernel: Hardware name: XFUSION 2288 V7/BC15MBSC, BIOS 2.00.20.Btg 02/08/2023 114000-[3.779509] kernel: RIP: 0010:uncore_insert_box_info+0x134/0x350 114068-[3.779515] kernel: Code: c2 01 48 83 c0 04 39 d1 0f 8e c6 01 00 00 49 8b 4c 24 38 8b 0c 01 41 89 0c 07 49 8b 74 24 40 8b 34 06 41 89 34 06 39 f9 75 cf <0f> 0b 4c 89 ff e8 42 95 32 00 4c 89 f7 e8 3a 95 32 00 5b 41 5c 41 114291-[3.779521] kernel: RSP: :ff5bc606001fbc98 EFLAGS: 00010246 114358-[3.779527] kernel: RAX: 0008 RBX: RCX: 0003 114447-[3.779531] kernel: RDX: 0002 RSI: 00018000 RDI: 0003 114536-[3.779534] kernel: RBP: ff5bc606001fbcc0 R08: 0010 R09: ff456694ca656f20 114625-[3.779538] kernel: R10: ff456694ca32aec8 R11: e000 R12: ff4566984965a9c0 114714-[3.779541] kernel: R13: ff5bc606001fbcf8 R14: ff456694ca656000 R15: ff456694ca656f20 114803-[3.779545] kernel: FS: () GS:ff4566982f80() knlGS: 114903-[3.779549] kernel: CS: 0010 DS: ES: CR0: 80050033 114976-[3.779553] kernel: CR2: CR3: 0007ba610001 CR4: 00771ee0 115065-[3.779556] kernel: DR0: DR1: DR2: 115154-[3.779559] kernel: DR3: DR6: fffe07f0 DR7: 0400 115243-[3.779563] kernel: PKRU: 5554 115281:[3.779565] kernel: Call Trace: 115316-[3.779569] kernel: 115347-[3.779573] kernel: parse_discovery_table.isra.0+0x162/0x1a0 115412-[3.779580] kernel: intel_uncore_has_discovery_tables+0x19e/0x270 115482-[3.779585] kernel: ? type_pmu_register+0x1c/0x42 115536-[3.779593] kernel: intel_uncore_init+0xe3/0x226 115589-[3.779597] kernel: ? type_pmu_register+0x42/0x42 115643-[3.779601] kernel: do_one_initcall+0x46/0x1e0 115694-[3.779608] kernel: do_initcalls+0x12f/0x159 115743-[3.779615] kernel: kernel_init_freeable+0x162/0x1b5 115800-[3.779622] kernel: ? rest_init+0x100/0x100 115848-[3.779630] kernel: kernel_init+0x1b/0x150 115895-[3.779636] kernel: ? rest_init+0x100/0x100 115943-[3.779641] kernel: ret_from_fork+0x1f/0x30 115991-[3.779647] kernel: 116023-[3.779650] kernel: ---[ end trace 3503eae85cdd4085 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008037 Title: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: Kernel taitned 512 ude to warning of below: #grep taint /var/log/syslog -b2 235407-Feb 20 15:27:14 xfusion kernel: [3.779483] WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 235561-Feb 20 15:27:14 xfusion kernel: [3.779495] Modules linked in: 235627:Feb 20 15:27:14 xfusion kernel: [3.779499] CPU: 64 PID: 1 Comm: swapper/0 Not tainted 5.15.0-60-generic #66-Ubuntu 235746-Feb 20 15:27:14 xfusion kernel: [3.779505] Hardware name: XFUSION 2288 V7/BC15MBSC, BIOS 2.00.20.Btg 02/08/2023 235862-Feb 20 15:27:14 xfusion kernel: [3.779509] RIP: 0010:uncore_insert_box_info+0x134/0x350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2008037/+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 2008037] [NEW] kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350
Public bug reported: Kernel taitned 512 ude to warning of below: #grep taint /var/log/syslog -b2 235407-Feb 20 15:27:14 xfusion kernel: [3.779483] WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 235561-Feb 20 15:27:14 xfusion kernel: [3.779495] Modules linked in: 235627:Feb 20 15:27:14 xfusion kernel: [3.779499] CPU: 64 PID: 1 Comm: swapper/0 Not tainted 5.15.0-60-generic #66-Ubuntu 235746-Feb 20 15:27:14 xfusion kernel: [3.779505] Hardware name: XFUSION 2288 V7/BC15MBSC, BIOS 2.00.20.Btg 02/08/2023 235862-Feb 20 15:27:14 xfusion kernel: [3.779509] RIP: 0010:uncore_insert_box_info+0x134/0x350 ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008037 Title: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: Kernel taitned 512 ude to warning of below: #grep taint /var/log/syslog -b2 235407-Feb 20 15:27:14 xfusion kernel: [3.779483] WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 235561-Feb 20 15:27:14 xfusion kernel: [3.779495] Modules linked in: 235627:Feb 20 15:27:14 xfusion kernel: [3.779499] CPU: 64 PID: 1 Comm: swapper/0 Not tainted 5.15.0-60-generic #66-Ubuntu 235746-Feb 20 15:27:14 xfusion kernel: [3.779505] Hardware name: XFUSION 2288 V7/BC15MBSC, BIOS 2.00.20.Btg 02/08/2023 235862-Feb 20 15:27:14 xfusion kernel: [3.779509] RIP: 0010:uncore_insert_box_info+0x134/0x350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2008037/+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 2002285] Re: Alder Lake N-Series Enablement
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2002285 Title: Alder Lake N-Series Enablement Status in linux-intel-iotg package in Ubuntu: New Status in linux-intel-iotg source package in Focal: Invalid Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: [Summary] Alder Lake N-Series Enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2002285/+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 2006554] Re: [5G] Enable 5G support with Fibocom FM350
** Tags added: verification-testing-passed ** Tags removed: verification-needed-jammy verification-testing-passed ** Tags added: verification-done-jammy ** Tags added: verification-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2006554 Title: [5G] Enable 5G support with Fibocom FM350 Status in linux-intel-iotg package in Ubuntu: New Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: Enable 5G support with Fibocom FM350 module in intel iotg kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2006554/+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 2007328] Re: [ADL-N] HDMI port through type-c stops working after reboot
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2007328 Title: [ADL-N] HDMI port through type-c stops working after reboot Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: [Impact] HDMI port through type-c stops working after reboot [Fix] adding the correct ddc pin mapping and eliminate the warn log about ownership. [Test Case] 1.Connected the external monitor to the onboard HDMI port which comes from type-c. 2.Boot OS. 3.Check the monitor to see if it is working. [Where problems could occur] Low, the fix limits to adl-n (adl-p) series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2007328/+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 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
The offending commit:
commit 793e7ce5571a9213c7bc9bd5ea22a3394f4b4d6b
Author: Richard Fitzgerald
Date: Fri Nov 4 13:22:13 2022 +
ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
BugLink: https://bugs.launchpad.net/bugs/2003130
[ Upstream commit 39bd801d6908900e9ab0cdc2655150f95ddd4f1a ]
The DAI tx_mask and rx_mask are set by snd_soc_dai_set_tdm_slot()
and used by later code that depends on the TDM settings. So
__soc_pcm_open() should not be obliterating those mask values.
The code in __soc_pcm_hw_params() uses these masks to calculate the
active channels so that only the AIF_IN/AIF_OUT widgets for the
active TDM slots are enabled. The zeroing of the masks in
__soc_pcm_open() disables this functionality so all AIF widgets
were enabled even for channels that are not assigned to a TDM slot.
Signed-off-by: Richard Fitzgerald
Fixes: 2e5894d73789 ("ASoC: pcm: Add support for DAI multicodec")
Link:
https://lore.kernel.org/r/20221104132213.121847-1...@opensource.cirrus.com
Signed-off-by: Mark Brown
Signed-off-by: Sasha Levin
Signed-off-by: Kamal Mostafa
Signed-off-by: Stefan Bader
Kinetic 5.19 and OEM 6.1 are unaffected, only need to revert the
offending commit for Jammy 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/2007798
Title:
[Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a
while
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
In Progress
Bug description:
[Summary]
During the kernel SRU testing on focal-hwe, I found the audio output of some
machines are broken.
I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and
haven't seen this happened.
The volume bars in settings react to what sound is played correctly
and device is detected as well.
[Reproduce steps]
1. install focal
2. enable -proposed
3. run apt dist-upgrade.
4. reboot.
5. press fn keys to volume up then volume down or play a short youtube video.
6. after a while can't hear any sound from the speaker.
[Failure rate]
10/10
[Additional info]
If I run "sudo alsa force-reload" can make audio work again, but after a
while it breaks again.
These are machines that impacted by this bug:
https://certification.canonical.com/hardware/202007-28045/
https://certification.canonical.com/hardware/201906-27109/
https://certification.canonical.com/hardware/201903-26881/
https://certification.canonical.com/hardware/202007-28047/
https://certification.canonical.com/hardware/202007-28055/
https://certification.canonical.com/hardware/202005-27899/
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85
Uname: Linux 5.15.0-66-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1303 F pulseaudio
CasperMD5CheckResult: skip
Date: Sun Feb 19 21:24:59 2023
InstallationDate: Installed on 2020-08-03 (930 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog: Feb 19 20:53:23
dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system]
Activating via systemd: service name='org.freedesktop.RealtimeKit1'
unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
Symptom_Type: Sound works for a while, then breaks
Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/06/2019
dmi.bios.release: 1.5
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7590
dmi.product.sku: 0922
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007798/+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 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
Sometimes `/usr/lib/checkbox-provider-base/bin/audio_test.py` fails to catch the error at first run. Need to run it a second time to reproduce 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/2007798 Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Bug description: [Summary] During the kernel SRU testing on focal-hwe, I found the audio output of some machines are broken. I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and haven't seen this happened. The volume bars in settings react to what sound is played correctly and device is detected as well. [Reproduce steps] 1. install focal 2. enable -proposed 3. run apt dist-upgrade. 4. reboot. 5. press fn keys to volume up then volume down or play a short youtube video. 6. after a while can't hear any sound from the speaker. [Failure rate] 10/10 [Additional info] If I run "sudo alsa force-reload" can make audio work again, but after a while it breaks again. These are machines that impacted by this bug: https://certification.canonical.com/hardware/202007-28045/ https://certification.canonical.com/hardware/201906-27109/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/202007-28047/ https://certification.canonical.com/hardware/202007-28055/ https://certification.canonical.com/hardware/202005-27899/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1303 F pulseaudio CasperMD5CheckResult: skip Date: Sun Feb 19 21:24:59 2023 InstallationDate: Installed on 2020-08-03 (930 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Feb 19 20:53:23 dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.product.sku: 0922 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007798/+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 2007830] Re: [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade
OK, this probably wasn't a bug. I expect one of these to be true: * The Nvidia driver failed to DKMS rebuild for the Oracle kernel, which is not uncommon. Just try reinstalling the Nvidia driver. * linux-modules-extra-5.19.0-*-oracle wasn't installed * The Oracle kernel doesn't need to support DKMS, DRI or Nvidia. * No one actually needs the Oracle kernel to support the Nvidia driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2007830 Title: [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade Status in linux-oracle package in Ubuntu: Won't Fix Bug description: Display on the second screen does not work since last kernel upgrade. It works using the previous one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 20 10:16:57 2023 DistUpgraded: 2022-10-21 09:45:54,530 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/525.78.01, 5.19.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:0774] NVIDIA Corporation GP104BM [GeForce GTX 1080 Mobile] [10de:1be0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GeForce GTX 1080 Max-Q [1028:07c0] InstallationDate: Installed on 2022-10-12 (130 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (122 days ago) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2007830/+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 2007830] Re: [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade
** Changed in: linux-oracle (Ubuntu) Status: Incomplete => Won't Fix ** No longer affects: nvidia-graphics-drivers-525 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2007830 Title: [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade Status in linux-oracle package in Ubuntu: Won't Fix Bug description: Display on the second screen does not work since last kernel upgrade. It works using the previous one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 20 10:16:57 2023 DistUpgraded: 2022-10-21 09:45:54,530 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/525.78.01, 5.19.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:0774] NVIDIA Corporation GP104BM [GeForce GTX 1080 Mobile] [10de:1be0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GeForce GTX 1080 Max-Q [1028:07c0] InstallationDate: Installed on 2022-10-12 (130 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (122 days ago) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2007830/+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 1786013] Autopkgtest regression report (linux-restricted-modules-nvidia/5.15.0-1017.17+3)
All autopkgtests for the newly accepted linux-restricted-modules-nvidia (5.15.0-1017.17+3) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-nvidia [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use
Please give latest mainline kernel a try: https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.2/amd64/ -- 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/1987829 Title: LG Gram 12gen high CPU use when USB-C/TB is in use Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: LG Gram laptop 17Z90Q with a Core i7-1260P CPU. Whenever an external monitor is connected to USB-C/Thunderbolt 4, average load goes above 3.0 and the machine is getting very hot. Output from top -H shows a lot of kworker CPU usage: top - 11:45:06 up 33 min, 2 users, load average: 3,30, 3,08, 2,79 Threads: 1442 total, 2 running, 1440 sleeping, 0 stopped, 0 zombie %Cpu(s): 0,1 us, 3,7 sy, 0,0 ni, 96,1 id, 0,0 wa, 0,0 hi, 0,1 si, 0,0 st MiB Mem : 15684,6 total, 8510,2 free, 2580,8 used, 4593,6 buff/cache MiB Swap: 3815,0 total, 3815,0 free, 0,0 used. 11326,9 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ WCHAN COMMAND 7766 root 20 0 0 0 0 R 19,8 0,0 0:56.05 worker_th+ kworker/0:2-events 196 root 20 0 0 0 0 D 15,8 0,0 1:18.12 ec_guard kworker/u32:2+USBC000:00-con0 10237 root 20 0 0 0 0 I 12,9 0,0 0:26.44 worker_th+ kworker/0:0-events 1027 root 20 0 0 0 0 I 6,6 0,0 0:43.30 worker_th+ kworker/1:3-events 10971 root 20 0 0 0 0 I 4,0 0,0 0:00.20 worker_th+ kworker/15:0-events 175 root 20 0 0 0 0 I 2,3 0,0 0:03.24 worker_th+ kworker/11:1-events 2410 root 20 0 0 0 0 I 1,7 0,0 0:05.49 worker_th+ kworker/9:3-events Perf shows a lot of time spent inside handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read. Additionally, kernel log is getting spammed with these lines every 4 seconds (but also without any USB-C device attached): [ 223.514304] ACPI Error: No handler for Region [XIN1] (f2ad4f1f) [UserDefinedRegion] (20210730/evregion-130) [ 223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no handler (20210730/exfldio-261) [ 223.514337] Initialized Local Variables for Method [_TMP]: [ 223.514339] Local0: 21495082Integer 0034 [ 223.514349] No Arguments are initialized for method [_TMP] [ 223.514354] ACPI Error: Aborting method \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1678 F pulseaudio /dev/snd/controlC1: me 1678 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Aug 26 11:57:05 2022 InstallationDate: Installed on 2022-08-25 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LG Electronics 17Z90Q-G.AA78N ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=e2f96916-a67c-432e-b687-730071271216 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. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: A1ZG0380 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17Z90Q dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.ec.firmware.release: 33.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrA1ZG0380X64:bd07/06/2022:br0.1:efr33.0:svnLGElectronics:pn17Z90Q-G.AA78N:pvr0.1:rvnLGElectronics:rn17Z90Q:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:skuEVO: dmi.product.family: LG gram PC dmi.product.name: 17Z90Q-G.AA78N dmi.product.sku: EVO dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.ne
[Kernel-packages] [Bug 1990876] Re: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module
Please boot mainline kernel [0] with kernel parameter "usbcore.dyndbg xhci_pci.dyndbg log_buf_len=16M" and attach dmesg here. [0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.2/amd64/ ** Changed in: linux (Ubuntu) Status: Expired => 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/1990876 Title: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu 22.04, as of yesterday night upon rebooting the framework laptop (which had not been rebooted for several weeks), the fans come on strong and I see, with top, a kworker process at nearly 100% CPU utilization, which makes the laptop unusable. I have an early Framework laptop with an 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz. I removed all USB-c expansion cards except for one with an USB-c pass through, to no avail. With perf I have been able to determine that the xhci_hub_control and perhaps xhci_bus_suspend are at fault. As a matter of fact, the laptop cannot suspend any more, when it was working flawlessly until the reboot. $ sudo apt install linux-tools-common linux-tools-$(uname -r) $ sudo -i # echo -1 > /proc/sys/kernel/perf_event_paranoid # perf record control-c # perf report Samples: 125K of event 'cycles', Event count (approx.): 142991820424 Overhead Command Shared Object Symbol 54.11% kworker/5:2+usb [kernel.kallsyms] [k] xhci_hub_control ◆ 7.94% kworker/5:2+usb [kernel.kallsyms] [k] xhci_bus_suspend ▒ 0.98% kworker/5:2+usb [kernel.kallsyms] [k] kfree ▒ 0.86% kworker/5:2+usb [kernel.kallsyms] [k] _raw_spin_lock_irqsave ... What can be done to address this issue with a kworker? I suspect perhaps the new kernel is at fault. I tried rebooting to the prior kernel 5.15.0-47-generic and 5.15.0-46-generic, but with the same result. What has changed? What can be done about this kworker and the xchi_hub_control? A temporary solution: $ sudo modprobe -r xhci_pci … which results in the kworker process disappearing from `top` (reduced CPU usage to near zero), the fans wind down, and unfortunately the ethernet expansion bay doesn’t work anymore but at least wifi does. Keyboard and touchpad also work. And suspend with deep also work well, just tested it. I assume other expansion bays will stop working too, but the laptop is at least charging: the USB-c pass-through works. See also: https://community.frame.work/t/kworker-stuck-at-near-100-cpu-usage-with-ubuntu-22-04/23053/2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 4870 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 18:14:26 2022 InstallationDate: Installed on 2022-03-11 (199 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (150 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product
[Kernel-packages] [Bug 2007829] Re: USB keyboard not detected
Is this a regression? -- 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/2007829 Title: USB keyboard not detected Status in linux package in Ubuntu: Incomplete Bug description: I am currently testing the Nezha image according to http://iso.qa.ubuntu.com/qatracker/milestones/442/builds/271832/testcases/1755/results When I plugin a USB keyboard after the system is up it is correctly discovered. When I power up the device with a plugged in USB keyboard it is not detected. See the relevant kernel messages below. [ +0.000651] usbcore: registered new interface driver usbfs [ +0.000162] usbcore: registered new interface driver hub [ +0.000128] usbcore: registered new device driver usb [ +0.001479] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ +0.000489] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ +0.000532] uhci_hcd: USB Universal Host Controller Interface driver [ +0.000787] usbcore: registered new interface driver uas [ +0.000157] usbcore: registered new interface driver usb-storage [ +0.000300] usbcore: registered new interface driver usbserial_generic [ +0.000104] usbserial: USB Serial support registered for generic [ +0.000118] usbcore: registered new interface driver ch341 [ +0.94] usbserial: USB Serial support registered for ch341-uart [ +0.007873] ehci-platform 4101000.usb: EHCI Host Controller [ +0.005820] ehci-platform 4101000.usb: new USB bus registered, assigned bus number 1 [ +0.008338] ehci-platform 4101000.usb: irq 107, io mem 0x04101000 [ +0.014689] ehci-platform 4101000.usb: USB 2.0 started, EHCI 1.00 [ +0.006889] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.17 [ +0.008389] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ +0.007304] usb usb1: Product: EHCI Host Controller [ +0.004955] usb usb1: Manufacturer: Linux 5.17.0-1010-allwinner ehci_hcd [ +0.006776] usb usb1: SerialNumber: 4101000.usb [ +0.006016] hub 1-0:1.0: USB hub found [ +0.006124] ehci-platform 420.usb: EHCI Host Controller [ +0.005820] ehci-platform 420.usb: new USB bus registered, assigned bus number 2 [ +0.008177] ehci-platform 420.usb: irq 109, io mem 0x0420 [ +0.019500] ehci-platform 420.usb: USB 2.0 started, EHCI 1.00 [ +0.006924] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.17 [ +0.008406] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ +0.007308] usb usb2: Product: EHCI Host Controller [ +0.004956] usb usb2: Manufacturer: Linux 5.17.0-1010-allwinner ehci_hcd [ +0.006773] usb usb2: SerialNumber: 420.usb [ +0.006015] hub 2-0:1.0: USB hub found [ +0.030690] ohci-platform 4101400.usb: Generic Platform OHCI controller [ +0.006797] ohci-platform 4101400.usb: new USB bus registered, assigned bus number 3 [ +0.008115] ohci-platform 4101400.usb: irq 108, io mem 0x04101400 [ +0.069475] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.17 [ +0.008365] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ +0.007300] usb usb3: Product: Generic Platform OHCI controller [ +0.006002] usb usb3: Manufacturer: Linux 5.17.0-1010-allwinner ohci_hcd [ +0.006775] usb usb3: SerialNumber: 4101400.usb [ +0.005758] hub 3-0:1.0: USB hub found [ +0.006081] ohci-platform 4200400.usb: Generic Platform OHCI controller [ +0.006750] ohci-platform 4200400.usb: new USB bus registered, assigned bus number 4 [ +0.008506] ohci-platform 4200400.usb: irq 110, io mem 0x04200400 [ +0.068747] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.17 [ +0.008395] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ +0.007335] usb usb4: Product: Generic Platform OHCI controller [ +0.006003] usb usb4: Manufacturer: Linux 5.17.0-1010-allwinner ohci_hcd [ +0.006778] usb usb4: SerialNumber: 4200400.usb [ +0.006154] hub 4-0:1.0: USB hub found [ +0.016572] usb 2-1: new high-speed USB device number 2 using ehci-platform [ +0.613864] usb 4-1: new low-speed USB device number 2 using ohci-platform [ +0.207989] usb 4-1: device descriptor read/64, error -62 [ +0.304014] usb 4-1: device descriptor read/64, error -62 [ +0.29] usb 4-1: new low-speed USB device number 3 using ohci-platform [ +0.208012] usb 4-1: device descriptor read/64, error -62 [ +0.303984] usb 4-1: device descriptor read/64, error -62 [ +0.112175] usb usb4-port1: attempt power cycle [ +0.511829] usb 4-1: new low-speed USB device number 4 using ohci-platform [ +0.431956] usb 4-1: device not accepting address 4, error -62 [ +0.204043] usb 4-1: new low-speed USB device number 5 using ohci-platform [ +0.431959] usb 4-1: device not accepting address 5, error -
[Kernel-packages] [Bug 2006546] Re: Improve arp_ndisc_evict_nocarrier.sh test result processing
** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2006546 Title: Improve arp_ndisc_evict_nocarrier.sh test result processing Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Bug description: [Impact] The arp_ndisc_evict_nocarrier.sh in selftests/net didn't pass a proper return value for failed test cases. Thus we might get false negatives if the last command runs successfully. [Fix] * 1856628baa selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier This patch can be cherry-picked into affected kernels. Lunar has been patched already. J-hwe-5.17 will be deprecated thus it will be skipped. [Test] Run the patched test, this should not cause any regression as sub tests are good with our kernels (except there is a cleanup issue in bug 1968310) One can deliberately fail a test by hijacking the if statement for the return value check to make sure this patch is working as expected. [Where problems could occur] This patch improves the result interpretation, we might see new failures being reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006546/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock
Applied patches to kinetic:linux except the one ("Revert "PCI:
Distribute available resources for root buses, too"") patch that was
reverted upstream.
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1991366
Title:
Fix Thunderbolt device hotplug fail when connect via thunderbolt dock
Status in HWE Next:
New
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Some Dell laptops where booting with Thunderbolt/USB4 devices connected the
BIOS leaves some of
the PCIe devices unconfigured. The kernel message shows "No bus number
available for hot-added bridge". The connected devices can't be found.
[Fix]
Current linux PCI distribute the "spare" resources between hotplug ports on
hot-add but have not done that upon the initial scan. The patches make the
initial root bus scan path to do the same. The additional patches are just a
small cleanups that can be applied separately too.
[Test]
1. Power on the machine with Thunderbolt/USB4 devices connected.
2. Check the kernel message to see if "No bus number available for hot-added
bridge" shows up or not.
3. Check if the Thunderbolt/USB4 devices works or not.
[Where problems could occur]
The patches only apply the same procedures on initial root bus scan which was
not done. If the BIOS configures the PCI correctly, everything is OK. It only
takes effect for the BIOS w/ unconfigured PCIe devices.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1981773] Re: Make cm32181 sensor work after system suspend
** Changed in: linux (Ubuntu Kinetic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1981773 Title: Make cm32181 sensor work after system suspend Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] cm32181 ambient light sensor stops working after system suspend. [Fix] Add PM support for cm32181 so it can work after system suspend. [Test] The sysfs in_illuminance_input continues to change after system suspend. [Where problems could occur] This changeset is limited to a specific device, and it already lacks PM support - so the worst case is that it stops working after resume like it always has been. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981773/+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 2003226] Re: libvirt live migrate to a lower generation processor freeze the migrated vm
@Daniel testing rc versions might be ok, although typically at this point you'd want to consider switching to bisecting a git checkout of the kernel since there'll be a limited number of -rc's. -- 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/2003226 Title: libvirt live migrate to a lower generation processor freeze the migrated vm Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hi, i have several libvirt hosts servers with differents CPU generation, in particular : - older generation : Intel Xeon E5-2640 v4 2.40GHz - newer generation : Intel Xeon Gold 5215 2.50GHz i recently re-install all this servers into ubuntu server 22.04.1 and since, when i live migrate a VM from a new generation processor to older generation processor the migrated guest freeze without generating any error logs. if i migrate the opposite way ( older cpu to newer cpu ) it works perfectly. previous version of hosts ( same hardware on ubuntu 16.04 ) did not present the problem the live migration is done with the following command ( issued from a third server playing the role of 'virtual-center' ) : virsh -c qemu+ssh://root@new_server/system migrate --verbose --live --undefinesource --persistent --unsafe guest_name qemu+ssh://root@old_server/system this one freeze the guest while the opposite migration : virsh -c qemu+ssh://root@old_server/system migrate --verbose --live --undefinesource --persistent --unsafe guest_name qemu+ssh://root@new_server/system works without problem migrate between 2 servers with same generation CPU also works perfectly the cpu configuration of guest is generic : qemu64 i have tried several ( almost all ) other virtual cpu configuration , always with the same problem. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 févr. 16 12:39 seq crw-rw 1 root audio 116, 33 févr. 16 12:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-02-15 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: FUJITSU PRIMERGY RX2530 M2 Package: linux (not installed) PciMultimedia: ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=13e84e97-ad18-49ed-8050-c8f7293e5e7d ro ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=13e84e97-ad18-49ed-8050-c8f7293e5e7d ro ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 RelatedPackageVersions: linux-restricted-modules-5.15.0-60-generic N/A linux-backports-modules-5.15.0-60-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy Uname: Linux 5.15.0-60-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.release: 1.10 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.11 R1.10.0 for D3279-B1x dmi.board.name: D3279-B1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3279-B12 WGS03 GS02 dmi.chassis.asset.tag: System Asset Tag dmi.chassis.type: 23 dmi.chassis.vendor: FUJITSU dmi.chassis.version: RX2530M2R1 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.11R1.10.0forD3279-B1x:bd09/29/2016:br1.10:svnFUJITSU:pnPRIMERGYRX2530M2:pvrGS01:rvnFUJITSU:rnD3279-B1:rvrS26361-D3279-B12WGS03GS02:cvnFUJITSU:ct23:cvrRX2530M2R1:skuABNK1565-V101-236: dmi.product.family: SERVER dmi.product.name: PRIMERGY RX2530 M2 dmi.product.sku: ABN:K1565-V101-236 dmi.product.version: GS01 dmi.sys.vendor: FUJITSU --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 févr. 16 12:39 seq crw-rw 1 root audio 116, 33 févr. 16 12:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Caspe
[Kernel-packages] [Bug 1968310] Re: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K
** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1968310 Title: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-hwe-5.17 source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-hwe-5.17 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In selftests: net: arp_ndisc_evict_nocarrier.sh, even all of the sub-tests from this script have passed, the overall test result is still a fail. # selftests: net: arp_ndisc_evict_nocarrier.sh # run arp_evict_nocarrier=1 test # ok # run arp_evict_nocarrier=0 test # ok # run all.arp_evict_nocarrier=0 test # ok # run ndisc_evict_nocarrier=1 test # ok # run ndisc_evict_nocarrier=0 test # ok # run all.ndisc_evict_nocarrier=0 test # ok not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255 This is caused by the cleanup() in the script, as it's trying to access a non-existing file. [Fix] * 9c4d7f45d6 selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier This patch can be cherry-picked into all affected kernels. [Test] Run the patched test and the test will pass. [Where problems could occur] Change limited to testing tools, no impact to real kernel function or test performances. [Original Bug Report] Issue found on Jammy OEM 5.17.0-1003.3 It looks like all the sub-tests has passed, but the final return value is not 0. Running 'make run_tests -C net TEST_PROGS=arp_ndisc_evict_nocarrier.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: arp_ndisc_evict_nocarrier.sh # run arp_evict_nocarrier=1 test # ok # run arp_evict_nocarrier=0 test # ok # run all.arp_evict_nocarrier=0 test # ok # run ndisc_evict_nocarrier=1 test # ok # run ndisc_evict_nocarrier=0 test # ok # run all.ndisc_evict_nocarrier=0 test # ok not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255 make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968310/+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 1988836] Autopkgtest regression report (linux-restricted-modules-azure-cvm/5.4.0-1103.109+cvm1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-cvm (5.4.0-1103.109+cvm1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-azure-cvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1990621] Re: PXE Boot contains wrong suggested link to ISO for live file system
I talked today to Łukasz Zemczak (sil2100) about the redirection. He made some pretty good arguments that the name of the URL should match a user's expectations. E.g. a User could assume the URL "https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso"; will provide the initial version of 22.04 and not the latest point release. I suggested a URL style like this "https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-live-server- amd64.iso" (notice the "-latest" after the version id). -- 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/1990621 Title: PXE Boot contains wrong suggested link to ISO for live file system Status in casper package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in casper source package in Jammy: Triaged Status in linux source package in Jammy: Invalid Bug description: When PXE booting without pulling in squashfs correctly the system tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a link to the old version which is not present anymore. --- Unable to find a medium containing a live file system Attempt interactive netboot from a URL? yes no (default yes): Two methods available for IP configuration: * static: for static IP configuration * dhcp: for automatic IP configuration static dhcp (default 'dhcp'): vlan id (optional): https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default) https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso url: http_proxy (optional): [ 125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443) wget: server returned error: HTTP/1.1 404 Not Found done. Unable to find a medium containing a live file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1990621/+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 2003394] Re: [23.04 FEAT] Support for List-Directed IPL and re-IPL from ECKD DASD
Patch request submitted: https://lists.ubuntu.com/archives/kernel-team/2023-February/thread.html#137241 Updating status to 'In Progress'. In addition test builds in PPA were done for all major architectures with the unstable kernel that incl. the patches mentioned above. https://launchpad.net/~fheimes/+archive/ubuntu/lp2003394 ** Changed in: ubuntu-z-systems Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel Team (canonical-kernel-team) ** Information type changed from Private 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/2003394 Title: [23.04 FEAT] Support for List-Directed IPL and re-IPL from ECKD DASD Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: Feature Description: Support for List-Directed IPL and re-IPL from ECKD DASD. Required to enable Secure Boot from DASD. Business Case: Security, HW support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003394/+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 2007995] [NEW] package linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-32-generic package pre-removal script subproces
Public bug reported: Also, after sleep, my laptop can't resume. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: linux-generic-hwe-20.04:amd64: Remove linux-generic-hwe-22.04:amd64: Remove linux-image-generic-hwe-22.04:amd64: Remove linux-image-5.19.0-32-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 21 17:25:07 2023 ErrorMessage: installed linux-image-5.19.0-32-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-26 (605 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-signed-hwe-5.19 Title: package linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-32-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-05-01 (296 days ago) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007995 Title: package linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-32-generic package pre- removal script subprocess returned error exit status 1 Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Also, after sleep, my laptop can't resume. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: linux-generic-hwe-20.04:amd64: Remove linux-generic-hwe-22.04:amd64: Remove linux-image-generic-hwe-22.04:amd64: Remove linux-image-5.19.0-32-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 21 17:25:07 2023 ErrorMessage: installed linux-image-5.19.0-32-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-26 (605 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-signed-hwe-5.19 Title: package linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-32-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-05-01 (296 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2007995/+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 2007994] Re: Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering
The screencast tool cannot record the flickering, so I have to use my phone for capturing. ** Attachment added: "bug-2007994.mp4" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2007994/+attachment/5648974/+files/bug-2007994.mp4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007994 Title: Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Affected machine: Lenovo ThinkPad X13 Yoga Gen 2 OS: Ubuntu 22.04.2 LTS (64-bit) I did a dist-upgrade on Feb. 16th, and every boot after that results in screen flickering, I checked the dpkg history and assume that the kernel upgrade(5.19.0.32.33~22.04.9) is the one to blame. Then I tried to boot the machine with the former kernel(5.15.0.25.27), everything works fine again which confirms my assumption. The following line repeated to show up before entering the desktop: blacklist: Problem blacklisting hash (-13) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity Date: Wed Feb 22 00:11:10 2023 InstallationDate: Installed on 2022-08-29 (176 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 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-5.19/+bug/2007994/+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 2007994] [NEW] Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering
Public bug reported: Affected machine: Lenovo ThinkPad X13 Yoga Gen 2 OS: Ubuntu 22.04.2 LTS (64-bit) I did a dist-upgrade on Feb. 16th, and every boot after that results in screen flickering, I checked the dpkg history and assume that the kernel upgrade(5.19.0.32.33~22.04.9) is the one to blame. Then I tried to boot the machine with the former kernel(5.15.0.25.27), everything works fine again which confirms my assumption. The following line repeated to show up before entering the desktop: blacklist: Problem blacklisting hash (-13) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity Date: Wed Feb 22 00:11:10 2023 InstallationDate: Installed on 2022-08-29 (176 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy regression-update wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007994 Title: Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Affected machine: Lenovo ThinkPad X13 Yoga Gen 2 OS: Ubuntu 22.04.2 LTS (64-bit) I did a dist-upgrade on Feb. 16th, and every boot after that results in screen flickering, I checked the dpkg history and assume that the kernel upgrade(5.19.0.32.33~22.04.9) is the one to blame. Then I tried to boot the machine with the former kernel(5.15.0.25.27), everything works fine again which confirms my assumption. The following line repeated to show up before entering the desktop: blacklist: Problem blacklisting hash (-13) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity Date: Wed Feb 22 00:11:10 2023 InstallationDate: Installed on 2022-08-29 (176 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 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-5.19/+bug/2007994/+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 2006453] Re: Fix selftests/ftracetests/Meta-selftests in Focal
** Changed in: ubuntu-kernel-tests Status: New => Invalid -- 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/2006453 Title: Fix selftests/ftracetests/Meta-selftests in Focal Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [SRU Justification] == Impact == This subtest checks for bashisms in the test scripts of ftracetests. A recent stable change added such a case. This is harmless but causes the Meta-selftests to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer for test_event_enable" which adds: + if [ "$e" == $val ]; then == Fix == Replace the test with + if [ "$e" = $val ]; then == Testcase == Running the kernel selftests/ftracetest (done in ADT and RT) should no longer show "Meta-selftests" as FAILed. == Regression Potential == This affects only the selftest suite and only ftrace subtests. Any change would only be observable there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006453/+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 1786013] Autopkgtest regression report (linux-restricted-modules-lowlatency-hwe-5.19/5.19.0-1018.19~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency-hwe-5.19 (5.19.0-1018.19~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-lowlatency- hwe-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1988836] Autopkgtest regression report (linux-restricted-modules-lowlatency-hwe-5.19/5.19.0-1018.19~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency-hwe-5.19 (5.19.0-1018.19~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-lowlatency- hwe-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 2007904] Re: [Possible Regression] net:reuseaddr_ports_exhausted.sh in ubuntu_kernel_selftests failed on F-oem-5.14 / J-oem-5.17
@Timo, look for "UBUNTU: SAUCE: Fix inet_csk_listen_start after CVE-2023-0461" on the various distro kernels (5.15 for sure but I believe across all series). ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0461 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/2007904 Title: [Possible Regression] net:reuseaddr_ports_exhausted.sh in ubuntu_kernel_selftests failed on F-oem-5.14 / J-oem-5.17 Status in ubuntu-kernel-tests: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: New Bug description: Issue found on F-oem-5.14.0-1058.66, it looks like a regression. This failure cannot be reproduced with 5.14.0-1057.64 Test log: TAP version 13 1..3 # Starting 3 tests from 1 test cases. # RUN global.reuseaddr_ports_exhausted_unreusable ... #OK global.reuseaddr_ports_exhausted_unreusable ok 1 global.reuseaddr_ports_exhausted_unreusable # RUN global.reuseaddr_ports_exhausted_reusable_same_euid ... #OK global.reuseaddr_ports_exhausted_reusable_same_euid ok 2 global.reuseaddr_ports_exhausted_reusable_same_euid # RUN global.reuseaddr_ports_exhausted_reusable_different_euid ... # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:Expected -1 (-1) == ret (0) # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:should fail to listen because only one uid reserves the port in TCP_LISTEN. # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:Expected -1 (-1) == ret (0) # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:should fail to listen because only one uid reserves the port in TCP_LISTEN. # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:Expected -1 (-1) == ret (0) # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:should fail to listen because only one uid reserves the port in TCP_LISTEN. # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:Expected -1 (-1) == ret (0) # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:should fail to listen because only one uid reserves the port in TCP_LISTEN. # reuseaddr_ports_exhausted_reusable_different_euid: Test failed at step #13 # FAIL global.reuseaddr_ports_exhausted_reusable_different_euid not ok 3 global.reuseaddr_ports_exhausted_reusable_different_euid # FAILED: 2 / 3 tests passed. # Totals: pass:2 fail:1 xfail:0 xpass:0 skip:0 error:0 Test result with 5.14.0-1057.64 $ sudo ./reuseaddr_ports_exhausted.sh TAP version 13 1..3 # Starting 3 tests from 1 test cases. # RUN global.reuseaddr_ports_exhausted_unreusable ... #OK global.reuseaddr_ports_exhausted_unreusable ok 1 global.reuseaddr_ports_exhausted_unreusable # RUN global.reuseaddr_ports_exhausted_reusable_same_euid ... #OK global.reuseaddr_ports_exhausted_reusable_same_euid ok 2 global.reuseaddr_ports_exhausted_reusable_same_euid # RUN global.reuseaddr_ports_exhausted_reusable_different_euid ... #OK global.reuseaddr_ports_exhausted_reusable_different_euid ok 3 global.reuseaddr_ports_exhausted_reusable_different_euid # PASSED: 3 / 3 tests passed. # Totals: pass:3 fail:0 xfail:0 xpass:0 skip:0 error:0 tests done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2007904/+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 1990294] Re: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..."
I upgraded our Mt. Jade AltraMax with the latest firmware from Ampere, and then I can't reproduce this issue with the latest Ubuntu Focal, HWE kernel, and the latest upgraded firmware in the previous step[1] after rebooting a Mt. Jade wih AltraMax more than 900 times. Setting the bug as Invalid on linux. [1] More details of version number HWE kernel 5.15.0-58-generic Firmware Revision 2.17.104000 SCP Revision 2.10.20221028 UEFI Revision 2.10.20221028 ** Changed in: linux (Ubuntu) Status: In Progress => Invalid -- 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/1990294 Title: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..." Status in grub2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: Kernel trace happens when bringing up CPU with focal HWE kernel 5.15.0-43-generic Steps to reproduce: enable earlycon and run reboot loop Expected result: system boots and ready to use Actual result: kerenl trace happens when bringing up CPU. See the call trace below[1]. [1] (copy from comment #7) [ 3.321372] arch_timer: Enabling local workaround for ARM erratum 1418040 [ 3.321394] CPU245: Booted secondary processor 0x0100310100 [0x413fd0c1] [ 8.536939] CPU246: failed to come online [ 8.550338] Detected PIPT I-cache on CPU246 [ 8.555817] CPU246: failed in unknown state : 0x0 [ 8.555987] GICv3: CPU246: found redistributor 10037 region 1:0x500100f0 [ 8.562727] [ cut here ] [ 8.562809] GICv3: CPU246: using allocated LPI pending table @0x08000268 [ 8.569364] Dying CPU not properly vacated! [ 16.668834] WARNING: CPU: 0 PID: 1 at kernel/sched/core.c:9215 sched_cpu_dying+0x1d0/0x2a0 [ 16.681496] Modules linked in: [ 16.684597] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.15.0-43-generic #46~20.04.1-Ubuntu [ 16.693010] pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 16.700095] pc : sched_cpu_dying+0x1d0/0x2a0 [ 16.704432] lr : sched_cpu_dying+0x1d0/0x2a0 [ 16.708770] sp : 8881bbe0 [ 16.712132] x29: 8881bbe0 x28: cca930eada80 x27: [ 16.719390] x26: 7395107ce000 x25: 00f6 x24: 403e40ed6728 [ 16.726651] x23: cca930eb2618 x22: x21: 00f6 [ 16.733907] x20: cca930719100 x19: 403e40ee7100 x18: 0014 [ 16.741165] x17: 3836323030303830 x16: 3030303078304020 x15: 656c62617420676e [ 16.748425] x14: 69646e6570204950 x13: 3030303038363230 x12: 3030383030303030 [ 16.755683] x11: 78304020656c6261 x10: 7420676e69646e65 x9 : cca92e7e39a0 [ 16.762940] x8 : 6c6c6120676e6973 x7 : 205d393038323635 x6 : c000fffe [ 16.770198] x5 : 0017ffe8 x4 : x3 : 8881b8c8 [ 16.777457] x2 : x1 : x0 : [ 16.784717] Call trace: [ 16.787197] sched_cpu_dying+0x1d0/0x2a0 [ 16.791182] cpuhp_invoke_callback+0x14c/0x5a8 [ 16.795699] cpuhp_invoke_callback_range+0x5c/0xb8 [ 16.800568] _cpu_up+0x234/0x360 [ 16.803844] cpu_up+0xb8/0x110 [ 16.806945] bringup_nonboot_cpus+0x7c/0xb0 [ 16.811195] smp_init+0x3c/0x98 [ 16.814385] kernel_init_freeable+0x1a4/0x39c [ 16.818813] kernel_init+0x2c/0x158 [ 16.822359] ret_from_fork+0x10/0x20 [ 16.825992] ---[ end trace bb9ca924bc23dd10 ]--- [ 16.830685] CPU246 enqueued tasks (0 total): [ 16.835356] [ cut here ] [ 16.835431] GICv3: CPU246: found redistributor 10037 region 1:0x500100f0 [ 16.840045] Dying CPU not properly vacated! [ 16.847925] WARNING: CPU: 0 PID: 1 at kernel/sched/core.c:9215 sched_cpu_dying+0x1d0/0x2a == Original Description == When kernel test rebooted onto the 5.15.0-43-generic HWE kernel, no output appeared on the console after the EFI stub: Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint A0 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint AD EFI stub: Booting Linux Kernel... EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+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 2007972] Re: [UBUNTU 22.04] Podman play kube: brings in unwanted (untrusted) k8s pause
--- Comment From boris.m...@de.ibm.com 2023-02-21 07:56 EDT--- This is a more detailed description of the problem, including SRU relevant information SRU Justification: == [Problem Statement] * For IBM hyper protect virtual servers v2 (aka HPCR) we plan to leverage the `podman play kube` functionality to bring up OCI containers based on k8s pod definitions in a secure enclave * since this will be running in a secure enclave, our customers can control network connectivity, in particular connectivity to the container registries needed to pull images * the podman version available in Ubuntu 22.04 (podman v3.4.4) automatically pulls a `pause` image from `k8s.gcr.io/pause`. This has the disadvantage that connectivity is needed to `k8s.gcr.io` and in addition this pull in a potentially untrusted image * this behaviour has been fixed in a later version of podman via https://github.com/containers/podman/issues/12254 in favour of pre-packaging a podman specific version of a pause container [Impact] * with the current behaviour of podman HPCR cannot run in a private-only network configuration without access to `k8s.gcr.io`. Mitigation: HPCR could try to pre-package a copy of k8s.gcr.io/pause * HPCR relies on k8s.gcr.io/pause but we do not have open source approval for that container [Test Plan] * start any k8s payload using `podman play kube`. Then verify that `k8s.gcr.io/pause` is not part of the running containers [Where problems could occur] * the `k8s.gcr.io/pause` container is only needed to keep the cluster up, afaik there is no direct dependency on that container name by any other container or component ** Bug watch added: github.com/containers/podman/issues #12254 https://github.com/containers/podman/issues/12254 -- 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/2007972 Title: [UBUNTU 22.04] Podman play kube: brings in unwanted (untrusted) k8s pause Status in linux package in Ubuntu: New Bug description: There is a security problem (podman would try to pull an untrusted image, the pause image) that needs to be fixed in Ubuntu 22.04. The required fix is described & provided here: https://github.com/containers/podman/issues/12254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007972/+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 2007972] [NEW] [UBUNTU 22.04] Podman play kube: brings in unwanted (untrusted) k8s pause
Public bug reported: There is a security problem (podman would try to pull an untrusted image, the pause image) that needs to be fixed in Ubuntu 22.04. The required fix is described & provided here: https://github.com/containers/podman/issues/12254 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-201616 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-201616 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007972 Title: [UBUNTU 22.04] Podman play kube: brings in unwanted (untrusted) k8s pause Status in linux package in Ubuntu: New Bug description: There is a security problem (podman would try to pull an untrusted image, the pause image) that needs to be fixed in Ubuntu 22.04. The required fix is described & provided here: https://github.com/containers/podman/issues/12254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007972/+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 1837035] Re: memcg_stat_rss from controllers in ubuntu_ltp failed
Found on B-aws-5.4 (5.4.0-1097.105~18.04.1) a1.medium, c5n.large, t3.medium The memcg_move_charge_at_immigrate_test is failing with the same reason. These two are failing in pairs on this kernel this round. -- 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/1837035 Title: memcg_stat_rss from controllers in ubuntu_ltp failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Confirmed Bug description: This issue was spotted on an i386 node "pepe" with Disco kernel, it failed with: memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up <<>> tag=memcg_stat_rss stime=1563448062 cmdline="memcg_stat_rss.sh" contacts="" analysis=exit <<>> memcg_stat_rss 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_stat_rss 1 TINFO: Warming up pid: 1784 memcg_stat_rss 1 TINFO: Process is still here after warm up: 1784 memcg_stat_rss 1 TPASS: rss is 135168 as expected memcg_stat_rss 2 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 2 TINFO: Running memcg_process --mmap-file -s 4096 memcg_stat_rss 2 TINFO: Warming up pid: 1804 memcg_stat_rss 2 TINFO: Process is still here after warm up: 1804 memcg_stat_rss 2 TPASS: rss is 0 as expected memcg_stat_rss 3 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 3 TINFO: Running memcg_process --shm -k 3 -s 4096 memcg_stat_rss 3 TINFO: Warming up pid: 1825 memcg_stat_rss 3 TINFO: Process is still here after warm up: 1825 memcg_stat_rss 3 TPASS: rss is 0 as expected memcg_stat_rss 4 TINFO: Starting test 4 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 135168 memcg_stat_rss 4 TINFO: Warming up pid: 1845 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up memcg_stat_rss 5 TINFO: Starting test 5 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 5 TINFO: Running memcg_process --mmap-lock1 -s 135168 memcg_stat_rss 5 TINFO: Warming up pid: 1858 memcg_stat_rss 5 TINFO: Process is still here after warm up: 1858 memcg_stat_rss 5 TPASS: rss is 135168 as expected memcg_stat_rss 6 TINFO: Starting test 6 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 6 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_stat_rss 6 TINFO: Warming up pid: 1878 memcg_stat_rss 6 TINFO: Process is still here after warm up: 1878 memcg_stat_rss 6 TPASS: rss is 135168 as expected memcg_stat_rss 7 TPASS: rss is 0 as expected memcg_stat_rss 8 TINFO: Starting test 7 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 8 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 8 TINFO: Running memcg_process --mmap-file -s 4096 memcg_stat_rss 8 TINFO: Warming up pid: 1901 memcg_stat_rss 8 TINFO: Process is still here after warm up: 1901 memcg_stat_rss 8 TPASS: rss is 0 as expected memcg_stat_rss 9 TPASS: rss is 0 as expected memcg_stat_rss 10 TINFO: Starting test 8 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 10 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 10 TINFO: Running memcg_process --shm -k 8 -s 4096 memcg_stat_rss 10 TINFO: Warming up pid: 1925 memcg_stat_rss 10 TINFO: Process is still here after warm up: 1925 memcg_stat_rss 10 TPASS: rss is 0 as expected memcg_stat_rss 11 TPASS: rss is 0 as expected memcg_stat_rss 12 TINFO: Starting test 9 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 12 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 12 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 135168 memcg_stat_rss 12 TINFO: Warming up pid: 1948 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat
[Kernel-packages] [Bug 2007972] [NEW] [UBUNTU 22.04] Podman play kube: brings in unwanted (untrusted) k8s pause
You have been subscribed to a public bug: There is a security problem (podman would try to pull an untrusted image, the pause image) that needs to be fixed in Ubuntu 22.04. The required fix is described & provided here: https://github.com/containers/podman/issues/12254 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-201616 severity-high targetmilestone-inin--- -- [UBUNTU 22.04] Podman play kube: brings in unwanted (untrusted) k8s pause https://bugs.launchpad.net/bugs/2007972 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 2007328] Re: [ADL-N] HDMI port through type-c stops working after reboot
** Tags added: verification-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2007328 Title: [ADL-N] HDMI port through type-c stops working after reboot Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: [Impact] HDMI port through type-c stops working after reboot [Fix] adding the correct ddc pin mapping and eliminate the warn log about ownership. [Test Case] 1.Connected the external monitor to the onboard HDMI port which comes from type-c. 2.Boot OS. 3.Check the monitor to see if it is working. [Where problems could occur] Low, the fix limits to adl-n (adl-p) series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2007328/+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 2007967] [NEW] [UBUNTU 22.04] PCIe Mensa card: Automatic recovery on second port fails - operator intervention required
Public bug reported: ---Problem Description--- During PCIe recovery on Mensa card second port fails recovery. First port recovers, second requires users to recover Physical function. ---Additional Hardware Info--- No additional setup, only PF are defined before inject. No traffic was running. ---uname output--- Linux t249sb1 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:30:43 UTC 2023 s390x s390x s390x GNU/Linux Machine Type = 3932-AGZ ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Inject error on the PBU attach to the mensa card. miep pbu 1800 etu_txe_eir store 0020_. Will cause AIB Data Bus UE ECC Error. Checking Linux distro, port 0 recover but port 1 is in unusable state. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Schayne Bellrose/schayne.bellro...@ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. [ 3135.702386] [ cut here ] [ 3135.702387] refcount_t: underflow; use-after-free. [ 3135.702409] WARNING: CPU: 10 PID: 0 at lib/refcount.c:28 refcount_warn_saturate+0x138/0x210 [ 3135.702416] Modules linked in: binfmt_misc s390_trng chsc_sch vfio_ccw eadm_sch zcrypt_cex4 mdev vfio_iommu_type1 vfio sch_fq_codel drm i2c_core drm_panel_orientation_quirks ip_tables x_tables btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx5_ib ib_uverbs ib_core dm_service_time qeth_l2 bridge stp llc mlx5_core pkey zcrypt crc32_vx_s390 ghash_s390 prng chacha_s390 libchacha aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 tls sha1_s390 sha_common mlxfw psample zfcp ptp qeth pps_core qdio scsi_transport_fc ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 3135.702459] CPU: 10 PID: 0 Comm: swapper/10 Not tainted 5.15.0-60-generic #66-Ubuntu [ 3135.702461] Hardware name: IBM 3932 AGZ Z06 (LPAR) [ 3135.702462] Krnl PSW : 0404c0018000 000269ab050c (refcount_warn_saturate+0x13c/0x210) [ 3135.702465]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 3135.702468] Krnl GPRS: 8001 00070027 0026 00026a835560 [ 3135.702469]0380006fb710 0380006fb708 96b4c180 [ 3135.702470]0001 0401 96b4c200 00026a7c5578 [ 3135.702472]802f6c00 0001 000269ab0508 0380006fb930 [ 3135.702477] Krnl Code: 000269ab04fc: c020003b89f6larl %r2,00026a2218e8 000269ab0502: c0e50021f267brasl %r14,000269eee9d0 #000269ab0508: af00mc 0,0 >000269ab050c: a7f4ffabbrc 15,000269ab0462 000269ab0510: c0b00068a834larl %r11,00026a7c5578 000269ab0516: 43a0b00aic %r10,10(%r11) 000269ab051a: 42a0f0a7stc %r10,167(%r15) 000269ab051e: 9501f0a7cli 167(%r15),1 [ 3135.702488] Call Trace: [ 3135.702489] [<000269ab050c>] refcount_warn_saturate+0x13c/0x210 [ 3135.702492] ([<000269ab0508>] refcount_warn_saturate+0x138/0x210) [ 3135.702494] [<03ff80dd8930>] cmd_ent_put+0xf0/0x100 [mlx5_core] [ 3135.702598] [<03ff80dd9e52>] mlx5_cmd_comp_handler+0x382/0x590 [mlx5_core] [ 3135.702661] [<03ff80dda092>] cmd_comp_notifier+0x32/0x50 [mlx5_core] [ 3135.702723] [<0002694ea04e>] atomic_notifier_call_chain+0x4e/0x90 [ 3135.702727] [<03ff80de029c>] mlx5_eq_async_int+0x12c/0x320 [mlx5_core] [ 3135.702789] [<0002694ea04e>] atomic_notifier_call_chain+0x4e/0x90 [ 3135.702790] [<03ff80df3c4e>] irq_int_handler+0x2e/0x40 [mlx5_core] [ 3135.702850] [<00026953fb1c>] __handle_irq_event_percpu+0x6c/0x210 [ 3135.702853] [<00026953fcf0>] handle_irq_event_percpu+0x30/0x80 [ 3135.702854] [<000269545d28>] handle_percpu_irq+0x68/0x90 [ 3135.702857] [<00026953e79e>] generic_handle_irq+0x3e/0x60 [ 3135.702858] [<0002694aba9c>] zpci_floating_irq_handler+0xdc/0x170 [ 3135.702862] [<000269eb4de2>] do_airq_interrupt+0x92/0x100 [ 3135.702864] [<00026953fb1c>] __handle_irq_event_percpu+0x6c/0x210 [ 3135.702866] [<00026953fcf0>] handle_irq_event_percpu+0x30/0x80 [ 3135.702867] [<000269545d28>] handle_percpu_irq+0x68/0x90 [ 3135.702869] [<00026953e79e>] generic_handle_irq+0x3e/0x60 [ 3135.702870] [<000269435e26>] do_irq_async+0x56/0xb0 [ 3135.702872] [<000269ef836a>] do_io_irq+0xba/0x150 [ 3135.702875] [<000269f0592c>] io_i
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
Thanks for your support @giuliano69 With a broken heart, I ended up deciding to kiss Linux goodbye. At least for a while. This process of compiling and searching for solutions does not fit into my day-to-day life. In addition to the webcam problem, the headset microphone does not work, the video card depends on complex configuration to run on the notebook monitor and on the secondary monitor, the boot had to be corrected in txts, and even so it kept showing the annoying message " not enougth memory". I need to use MS Teams for my work, and it works with limitations on Linux. So, bye linux, at least for now. Today linux has -1 :( -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware
[Kernel-packages] [Bug 2007967] [NEW] [UBUNTU 22.04] PCIe Mensa card: Automatic recovery on second port fails - operator intervention required
You have been subscribed to a public bug: ---Problem Description--- During PCIe recovery on Mensa card second port fails recovery. First port recovers, second requires users to recover Physical function. ---Additional Hardware Info--- No additional setup, only PF are defined before inject. No traffic was running. ---uname output--- Linux t249sb1 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:30:43 UTC 2023 s390x s390x s390x GNU/Linux Machine Type = 3932-AGZ ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Inject error on the PBU attach to the mensa card. miep pbu 1800 etu_txe_eir store 0020_. Will cause AIB Data Bus UE ECC Error. Checking Linux distro, port 0 recover but port 1 is in unusable state. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Schayne Bellrose/schayne.bellro...@ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. [ 3135.702386] [ cut here ] [ 3135.702387] refcount_t: underflow; use-after-free. [ 3135.702409] WARNING: CPU: 10 PID: 0 at lib/refcount.c:28 refcount_warn_saturate+0x138/0x210 [ 3135.702416] Modules linked in: binfmt_misc s390_trng chsc_sch vfio_ccw eadm_sch zcrypt_cex4 mdev vfio_iommu_type1 vfio sch_fq_codel drm i2c_core drm_panel_orientation_quirks ip_tables x_tables btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx5_ib ib_uverbs ib_core dm_service_time qeth_l2 bridge stp llc mlx5_core pkey zcrypt crc32_vx_s390 ghash_s390 prng chacha_s390 libchacha aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 tls sha1_s390 sha_common mlxfw psample zfcp ptp qeth pps_core qdio scsi_transport_fc ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 3135.702459] CPU: 10 PID: 0 Comm: swapper/10 Not tainted 5.15.0-60-generic #66-Ubuntu [ 3135.702461] Hardware name: IBM 3932 AGZ Z06 (LPAR) [ 3135.702462] Krnl PSW : 0404c0018000 000269ab050c (refcount_warn_saturate+0x13c/0x210) [ 3135.702465]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 3135.702468] Krnl GPRS: 8001 00070027 0026 00026a835560 [ 3135.702469]0380006fb710 0380006fb708 96b4c180 [ 3135.702470]0001 0401 96b4c200 00026a7c5578 [ 3135.702472]802f6c00 0001 000269ab0508 0380006fb930 [ 3135.702477] Krnl Code: 000269ab04fc: c020003b89f6larl %r2,00026a2218e8 000269ab0502: c0e50021f267brasl %r14,000269eee9d0 #000269ab0508: af00mc 0,0 >000269ab050c: a7f4ffabbrc 15,000269ab0462 000269ab0510: c0b00068a834larl %r11,00026a7c5578 000269ab0516: 43a0b00aic %r10,10(%r11) 000269ab051a: 42a0f0a7stc %r10,167(%r15) 000269ab051e: 9501f0a7cli 167(%r15),1 [ 3135.702488] Call Trace: [ 3135.702489] [<000269ab050c>] refcount_warn_saturate+0x13c/0x210 [ 3135.702492] ([<000269ab0508>] refcount_warn_saturate+0x138/0x210) [ 3135.702494] [<03ff80dd8930>] cmd_ent_put+0xf0/0x100 [mlx5_core] [ 3135.702598] [<03ff80dd9e52>] mlx5_cmd_comp_handler+0x382/0x590 [mlx5_core] [ 3135.702661] [<03ff80dda092>] cmd_comp_notifier+0x32/0x50 [mlx5_core] [ 3135.702723] [<0002694ea04e>] atomic_notifier_call_chain+0x4e/0x90 [ 3135.702727] [<03ff80de029c>] mlx5_eq_async_int+0x12c/0x320 [mlx5_core] [ 3135.702789] [<0002694ea04e>] atomic_notifier_call_chain+0x4e/0x90 [ 3135.702790] [<03ff80df3c4e>] irq_int_handler+0x2e/0x40 [mlx5_core] [ 3135.702850] [<00026953fb1c>] __handle_irq_event_percpu+0x6c/0x210 [ 3135.702853] [<00026953fcf0>] handle_irq_event_percpu+0x30/0x80 [ 3135.702854] [<000269545d28>] handle_percpu_irq+0x68/0x90 [ 3135.702857] [<00026953e79e>] generic_handle_irq+0x3e/0x60 [ 3135.702858] [<0002694aba9c>] zpci_floating_irq_handler+0xdc/0x170 [ 3135.702862] [<000269eb4de2>] do_airq_interrupt+0x92/0x100 [ 3135.702864] [<00026953fb1c>] __handle_irq_event_percpu+0x6c/0x210 [ 3135.702866] [<00026953fcf0>] handle_irq_event_percpu+0x30/0x80 [ 3135.702867] [<000269545d28>] handle_percpu_irq+0x68/0x90 [ 3135.702869] [<00026953e79e>] generic_handle_irq+0x3e/0x60 [ 3135.702870] [<000269435e26>] do_irq_async+0x56/0xb0 [ 3135.702872] [<000269ef836a>] do_io_irq+0xba/0x150 [ 3135.702875] [<00
[Kernel-packages] [Bug 1990876] Re: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module
Expired? The bug is real. Experiencing it right now. -- 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/1990876 Title: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module Status in linux package in Ubuntu: Expired Bug description: Using Ubuntu 22.04, as of yesterday night upon rebooting the framework laptop (which had not been rebooted for several weeks), the fans come on strong and I see, with top, a kworker process at nearly 100% CPU utilization, which makes the laptop unusable. I have an early Framework laptop with an 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz. I removed all USB-c expansion cards except for one with an USB-c pass through, to no avail. With perf I have been able to determine that the xhci_hub_control and perhaps xhci_bus_suspend are at fault. As a matter of fact, the laptop cannot suspend any more, when it was working flawlessly until the reboot. $ sudo apt install linux-tools-common linux-tools-$(uname -r) $ sudo -i # echo -1 > /proc/sys/kernel/perf_event_paranoid # perf record control-c # perf report Samples: 125K of event 'cycles', Event count (approx.): 142991820424 Overhead Command Shared Object Symbol 54.11% kworker/5:2+usb [kernel.kallsyms] [k] xhci_hub_control ◆ 7.94% kworker/5:2+usb [kernel.kallsyms] [k] xhci_bus_suspend ▒ 0.98% kworker/5:2+usb [kernel.kallsyms] [k] kfree ▒ 0.86% kworker/5:2+usb [kernel.kallsyms] [k] _raw_spin_lock_irqsave ... What can be done to address this issue with a kworker? I suspect perhaps the new kernel is at fault. I tried rebooting to the prior kernel 5.15.0-47-generic and 5.15.0-46-generic, but with the same result. What has changed? What can be done about this kworker and the xchi_hub_control? A temporary solution: $ sudo modprobe -r xhci_pci … which results in the kworker process disappearing from `top` (reduced CPU usage to near zero), the fans wind down, and unfortunately the ethernet expansion bay doesn’t work anymore but at least wifi does. Keyboard and touchpad also work. And suspend with deep also work well, just tested it. I assume other expansion bays will stop working too, but the laptop is at least charging: the USB-c pass-through works. See also: https://community.frame.work/t/kworker-stuck-at-near-100-cpu-usage-with-ubuntu-22-04/23053/2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 4870 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 18:14:26 2022 InstallationDate: Installed on 2022-03-11 (199 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (150 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0B dmi.product.version: AB dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990876/+subscriptions -- Mailin
[Kernel-packages] [Bug 2002285] Re: Alder Lake N-Series Enablement
** Tags added: verification-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2002285 Title: Alder Lake N-Series Enablement Status in linux-intel-iotg package in Ubuntu: New Status in linux-intel-iotg source package in Focal: Invalid Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: [Summary] Alder Lake N-Series Enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2002285/+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 1968681] Re: rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with FAIL: RDPRU raises #UD
Verified on node riccioli with 4.15.0-206.217, this issue has gone. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1968681 Title: rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with FAIL: RDPRU raises #UD Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] RDPRU, the Read Processor Register instruction of AMD Zen 2 processors is used to give access to some processor registers that are typically only accessible when the privilege level is zero. rdpru test in ubuntu_kvm_unit_tests is to check if the RDPRU instruction can be intercepted by the Hypervisor. Without this patchset, this test will fail on our AMD Zen 2 system "riccioli" with: FAIL: RDPRU raises #UD [Fix] * fb64f293 x86/cpufeatures: Add feature bit RDPRU on AMD * 0cb8410b kvm: svm: Intercept RDPRU We have these patches in newer releases already, only Bionic 4.15 requires this fix. The first patch needs to be backported with some context adjustment, the second can be cherry-picked. [Test] Test kernel can be found here: https://people.canonical.com/~phlin/kernel/lp-1968681-rdpru/ With the patched kernel, this rdpru test will pass on the target AMD Zen 2 system. $ sudo ./rdpru BUILD_HEAD=d6421940 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot \ -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 \ -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel \ /tmp/tmp.XOMVxpyNnl -smp 1 -cpu max # -initrd /tmp/tmp.I2TbGXFiaZ enabling apic smp: waiting for 0 APs PASS: RDPRU raises #UD SUMMARY: 1 tests PASS rdpru (1 tests) And the rdpru flag will be available in cpuinfo: $ grep -o rdpru /proc/cpuinfo rdpru [Where problems could occur] This patchset will add a new feature bit RDPRU for AMD Zen 2. We can expect to see new issues coming up when using this bit in the future. [Original Bug Report] Issue found on B-ibm-gt-4.15.0-1116.127 This can be reproduced with B-4.15.0-175 as well. This failure is only visible on this node. Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/rdpru' BUILD_HEAD=16647354 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.qGIR5tvTw1 -smp 1 -cpu max # -initrd /tmp/tmp.8JuYRCFRUi enabling apic FAIL: RDPRU raises #UD SUMMARY: 1 tests, 1 unexpected failures FAIL rdpru (1 tests, 1 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968681/+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 2007823] Re: Mute/mic LEDs no function on a HP platfrom
** Changed in: oem-priority Status: Confirmed => Fix Committed -- 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/2007823 Title: Mute/mic LEDs no function on a HP platfrom Status in OEM Priority Project: Fix Committed Status in linux-oem-6.1 package in Ubuntu: New Status in linux-oem-6.1 source package in Jammy: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on a HP platform. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. Applied on oem-6.1 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2007823/+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 2007824] Re: Mute/mic LEDs and speaker no function on some HP platfroms
** Changed in: oem-priority Status: Confirmed => Fix Committed -- 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/2007824 Title: Mute/mic LEDs and speaker no function on some HP platfroms Status in OEM Priority Project: Fix Committed Status in linux-oem-6.1 package in Ubuntu: New Status in linux-oem-6.1 source package in Jammy: New Bug description: [Impact] The mic mute/audio mute LEDS and speaker are not work on some HP platforms. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs and speaker are working good. Applied on oem-6.1 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2007824/+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 2007853] Re: Intel video driver i915 - Repeated GPU HANG's - Xorg use a lot of CPU
In a txt file, more readable I think !
** Attachment added: "cat /proc/interrupts"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007853/+attachment/5648934/+files/cat-proc-intrrupts-message.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/2007853
Title:
Intel video driver i915 - Repeated GPU HANG's - Xorg use a lot of CPU
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hello,
I think my problem is link to firmware package or make hardware error.
Lot of people have problem with the i915. I have take lot of time to
configure it correctly.
Today my configuration is ok with 5.19.0-32-generic, it seem the same with
5.15.0-60.
I'm on Ubuntu 22.04 LTS ("The Jammy Jellyfish")
I'm not sure when the problem have really started, but I propose you to
firstly see the problem in the global way.
I'm not sure It wan really depend on a kernel or a configuration. My
BIOS is up to date and all the system .
So today my i915 integrated card work well with my 11th Gen Intel® Core™ i5.
I have configure it, all drivers seem to be ok. VMWare work with accelerate
3D graphics, VLC work with OpenGL Output and hardware VDPAU or VD-API. Mesa
seem to be ok, Firefox work with hardware video acceleration. glmark2 and
glxgears is ok to. Xorg use very few CPU.
ALT+TAB is very speed to change between applications. TAB changing on Firefox
is very speed to.
Videos are fluid and use few CPU.
Intel_GPU_top show that vlc use hardware.
But at an aleatory time or with using a lot of CPU/GPU a problem
arrive !
My test process is VLC with a 1080p movie with a good encoding 5Go for an 1
hours.
Firefox with a 720p or 1080 video on YouTube in incrustation
VMWare with a Windows XP VM testing Dxdiag.
The 3 is visible partially at the same time on my screen.
I'm launching the 3, and I launch dxdiag video test on the VM. When It arrive
to Direct 3D 7 or 8 or 9 the problem start.
Before this, all is ok, fluid. (DXDiag 7, 8 or 9 are never are fluid, but I'm
not sure VMWare work well with this old version)
I think it normal at a moment to saturate the CPU or GPU, here it seem to be
the case, the YouTube video and vlc video skip frame and freeze and jerk.
But when the test is finish, it will go back at a normally state few time
after, I think.
Now the system is not fluid, ALT+TAB lag, jerk, changing tab on firefox it
very long, system monitor is very long. All graphical software is very long.
Video are not fluid.
Xorg start taking a lot of CPU even if nothing is done.
If I suspend system and resume it, it is better but not fluid.
If I hibernate (suspend to disk) with an hardware reset it is very fluid.
Sometime it seem to be totally normal.
Before do anything I see with cat /proc/interrupts a lot of interrupts on
IR-PCI-MSI 327680-edge xhci_hcd. For example : 325180.
After an hibernation I have "only" 102178 for xhci_hcd.
When I restart before any suspend, I can have the bios screen very long to
appear and the grub menu not fluid, very slow. I thinks I'm keep the bug some
time after reset.
On forum people deal with lost of video sync. I think it can be anything that.
With a power off it work normally, so the hardware reset have an impact.
In dmesg I only have : (when the problem start)
[ 5546.086667] x86/split lock detection: #AC: main-svga/14494 took a
split_lock trap at address: 0x559ce0ea2e3d
[ 5546.291794] x86/split lock detection: #AC: vmx-svga/14491 took a
split_lock trap at address: 0x563fc34febb7
[ 5546.310412] x86/split lock detection: #AC: main-mks/14493 took a
split_lock trap at address: 0x559ce0ea30a7
nothing else.
VLC have this error :
[h264 @ 0x7fa854c9e300] get_buffer() failed
[h264 @ 0x7fa854c9e300] thread_get_buffer() failed
[h264 @ 0x7fa854c9e300] decode_slice_header error
[h264 @ 0x7fa854c9e300] no frame!
[h264 @ 0x7fa854d8f3c0] get_buffer() failed
[h264 @ 0x7fa854d8f3c0] thread_get_buffer() failed
[h264 @ 0x7fa854d8f3c0] decode_slice_header error
[h264 @ 0x7fa854d8f3c0] no frame!
[5560d6746a70] vlcpulse audio output error: digital pass-through stream
connection failure: Non pris en charge
[5560d6746a70] main audio output error: module not functional
[7fa854cebd50] main decoder error: failed to create audio output
[5560d6746a70] vlcpulse audio output error: digital pass-through stream
connection failure: Non pris en charge
[5560d6746a70] main audio output error: module not functional
[7fa854cebd50] main decoder error: failed to create audio output
[5560d6746a70] main audio output error: cannot add user visualization
"any" (skipped)
[7fa854c19430] avcodec decoder: Using Intel iHD driver for Intel(R) Gen
Graphics - 22.3.1 () for hardware decoding
I can see it on syslog nothing else.
Nothing in xorg log.
It surpris
[Kernel-packages] [Bug 2007853] Re: Intel video driver i915 - Repeated GPU HANG's - Xorg use a lot of CPU
Hello, I just retry with more information : Before the bug : launch 1 of cat /proc/interrupts : 150: 0 12500 0 0 0 0 0 0 IR-PCI-MSI 327680-edge xhci_hcd 130: 0 0 36 0 0 0 0 0 IR-PCI-MSI 212992-edge xhci_hcd 195: 0 0 0765 0 0 43917 0 IR-PCI-MSI 32768-edge i915 NMI: 3 3 2 3 1 1 2 1 Non-maskable interrupts LOC: 44084 45148 38917 43380 44347 39950 63891 41043 Local timer interrupts SPU: 1 0 0 0 0 0 0 0 Spurious interrupts PMI: 3 3 2 3 1 1 2 1 Performance monitoring interrupts IWI: 1983 1796 1016 1318 1958 1772 34849 1872 IRQ work interrupts RTR: 0 0 0 0 0 0 0 0 APIC ICR read retries RES: 3202 2551 2333 2750 2945 2053 2450 1637 Rescheduling interrupts CAL: 32361 34041 33199 33443 32830 38261 30730 34866 Function call interrupts TLB: 4600 6819 7900 4979 5689 4671 7387 5792 TLB shootdowns TRM: 2 2 2 2 2 2 2 2 Thermal event interrupts launch 2 : 150: 0 15248 0 0 0 0 0 0 IR-PCI-MSI 327680-edge xhci_hcd 195: 0 0 0765 0 0 71819 0 IR-PCI-MSI 32768-edge i915 130: 0 0 36 0 0 0 0 0 IR-PCI-MSI 212992-edge xhci_hcd LOC: 51305 53966 47267 51999 52140 47294 79287 48834 Local timer interrupts SPU: 1 0 0 0 0 0 0 0 Spurious interrupts PMI: 3 3 3 3 1 1 2 1 Performance monitoring interrupts IWI: 2723 2250 1249 1604 2447 2329 43610 2303 IRQ work interrupts RTR: 0 0 0 0 0 0 0 0 APIC ICR read retries RES: 3317 2567 2347 2847 2984 2073 2462 1660 Rescheduling interrupts CAL: 33566 35684 34317 34273 33811 39276 32427 35700 Function call interrupts TLB: 4673 7130 7953 5017 5757 4764 7442 5869 TLB shootdowns TRM: 2 2 2 2 2 2 2 2 Thermal event interrupts I stress and the bug start ! launch 1 after the bug : 195: 7550 0 0765 0 0 964697 0 IR-PCI-MSI 32768-edge i915 150: 7011 37888 0 0 0 0 0 10041 IR-PCI-MSI 327680-edge xhci_hcd 130: 10 0 36 0 0 0 0 9 IR-PCI-MSI 212992-edge xhci_hcd NMI: 4 6 6 4 1 1 4 3 Non-maskable interrupts LOC: 460124 453153 482067 473181 455918 460154 609368 463418 Local timer interrupts SPU: 1 0 0 0 0 0 0 0 Spurious interrupts PMI: 4 6 6 4 1 1 4 3 Performance monitoring interrupts IWI: 28098 23300 16538 19575 21421 22590 505527 24870 IRQ work interrupts RTR: 0 0 0 0 0 0 0 0 APIC ICR read retries RES: 23455 16173 11638 19702 12745 12816 11421 15952 Rescheduling interrupts CAL: 131999 114719 106123 98885 108117 112193 110945 100299 Function call interrupts TLB: 28703 24931 27732 24161 29120 27679 33927 25081 TLB shootdowns TRM: 18027 18039 18034 18040 18039 18038 18027 18032 Thermal event interrupts Launch 2 after the bug : 195: 7550 0 0765 0 0 975853 0 IR-PCI-MSI 32768-edge i915 150:
[Kernel-packages] [Bug 1968310] Re: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K
Test passed with J-oem-5.17.0-1028.29. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1968310 Title: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-hwe-5.17 source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-hwe-5.17 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In selftests: net: arp_ndisc_evict_nocarrier.sh, even all of the sub-tests from this script have passed, the overall test result is still a fail. # selftests: net: arp_ndisc_evict_nocarrier.sh # run arp_evict_nocarrier=1 test # ok # run arp_evict_nocarrier=0 test # ok # run all.arp_evict_nocarrier=0 test # ok # run ndisc_evict_nocarrier=1 test # ok # run ndisc_evict_nocarrier=0 test # ok # run all.ndisc_evict_nocarrier=0 test # ok not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255 This is caused by the cleanup() in the script, as it's trying to access a non-existing file. [Fix] * 9c4d7f45d6 selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier This patch can be cherry-picked into all affected kernels. [Test] Run the patched test and the test will pass. [Where problems could occur] Change limited to testing tools, no impact to real kernel function or test performances. [Original Bug Report] Issue found on Jammy OEM 5.17.0-1003.3 It looks like all the sub-tests has passed, but the final return value is not 0. Running 'make run_tests -C net TEST_PROGS=arp_ndisc_evict_nocarrier.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: arp_ndisc_evict_nocarrier.sh # run arp_evict_nocarrier=1 test # ok # run arp_evict_nocarrier=0 test # ok # run all.arp_evict_nocarrier=0 test # ok # run ndisc_evict_nocarrier=1 test # ok # run ndisc_evict_nocarrier=0 test # ok # run all.ndisc_evict_nocarrier=0 test # ok not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255 make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968310/+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 1990794] Re: ubuntu_bpf failed to build on F-azure-5.4 / B-azure-5.4 ( error: ‘bpf_object_open_opts’ undeclared)
Test passed on F-azure-cvm and F-azure-fips, hints removed, closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1990794 Title: ubuntu_bpf failed to build on F-azure-5.4 / B-azure-5.4 ( error: ‘bpf_object_open_opts’ undeclared) Status in ubuntu-kernel-tests: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Released Bug description: Issue found on B-azure-5.4.0-1092.97~18.04.1 This is a regression as the test can be built and run in the last cycle. Error log: prog_tests/tcp_estats.c prog_tests/obj_name.c prog_tests/map_lock.c prog_tests/xdp_noinline.c prog_tests/global_data.c prog_tests/pkt_access.c -lcap -lelf -lrt -lpthread -o /home/azure/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_progs ../lib.mk:146: recipe for target '/home/azure/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_progs' failed make[1]: Leaving directory '/home/azure/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' Makefile:143: recipe for target 'all' failed make: Leaving directory '/home/azure/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: 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' prog_tests/send_signal.c: In function ‘test_send_signal_common’: prog_tests/send_signal.c:52:3: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result] write(pipe_c2p[1], buf, 1); ^~ prog_tests/send_signal.c:55:3: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result] read(pipe_p2c[0], buf, 1); ^ prog_tests/send_signal.c:61:4: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result] write(pipe_c2p[1], "2", 1); ^~ prog_tests/send_signal.c:63:4: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result] write(pipe_c2p[1], "0", 1); ^~ prog_tests/send_signal.c:66:3: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result] read(pipe_p2c[0], buf, 1); ^ prog_tests/send_signal.c:109:2: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result] read(pipe_c2p[0], buf, 1); ^ prog_tests/send_signal.c:117:2: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result] write(pipe_p2c[1], buf, 1); ^~ prog_tests/send_signal.c:131:2: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result] write(pipe_p2c[1], buf, 1); ^~ prog_tests/stacktrace_build_id_nmi.c: In function ‘read_perf_max_sample_freq’: prog_tests/stacktrace_build_id_nmi.c:12:2: warning: ignoring return value of ‘fscanf’, declared with attribute warn_unused_result [-Wunused-result] fscanf(f, "%llu", &sample_freq); ^~~ prog_tests/probe_user.c: In function ‘test_probe_user’: prog_tests/probe_user.c:9:2: warning: implicit declaration of function ‘DECLARE_LIBBPF_OPTS’ [-Wimplicit-function-declaration] DECLARE_LIBBPF_OPTS(bpf_object_open_opts, opts, ); ^~~ prog_tests/probe_user.c:9:22: error: ‘bpf_object_open_opts’ undeclared (first use in this function); did you mean ‘bpf_object_open_attr’? DECLARE_LIBBPF_OPTS(bpf_object_open_opts, opts, ); ^~~~ bpf_object_open_attr prog_tests/probe_user.c:9:22: note: each undeclared identifier is reported only once for each function it appears in prog_tests/probe_user.c:9:44: error: ‘opts’ undeclared (first use in this function); did you mean ‘open’? DECLARE_LIBBPF_OPTS(bpf_object_open_opts, opts, ); ^~~~ open prog_tests/probe_user.c:9:50: error: expected expression before ‘)’ token DECLARE_LIBBPF_OPTS(bpf_object_open_opts, opts, );
[Kernel-packages] [Bug 2007823] Re: Mute/mic LEDs no function on a HP platfrom
** Changed in: linux-oem-6.1 (Ubuntu) Assignee: (unassigned) => Andy Chi (andch) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => Andy Chi (andch) -- 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/2007823 Title: Mute/mic LEDs no function on a HP platfrom Status in OEM Priority Project: Confirmed Status in linux-oem-6.1 package in Ubuntu: New Status in linux-oem-6.1 source package in Jammy: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on a HP platform. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. Applied on oem-6.1 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2007823/+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 2007824] Re: Mute/mic LEDs and speaker no function on some HP platfroms
** Tags added: oem-priority originate-from-2007662 stella ** Tags added: originate-from-2007663 ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) -- 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/2007824 Title: Mute/mic LEDs and speaker no function on some HP platfroms Status in OEM Priority Project: Confirmed Status in linux-oem-6.1 package in Ubuntu: New Status in linux-oem-6.1 source package in Jammy: New Bug description: [Impact] The mic mute/audio mute LEDS and speaker are not work on some HP platforms. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs and speaker are working good. Applied on oem-6.1 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2007824/+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 2007823] Re: Mute/mic LEDs no function on a HP platfrom
** Description changed: [Impact] The mic mute/audio mute LEDS are not work on a HP platform. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. + Applied on oem-6.1 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). -- 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/2007823 Title: Mute/mic LEDs no function on a HP platfrom Status in OEM Priority Project: Confirmed Status in linux-oem-6.1 package in Ubuntu: New Status in linux-oem-6.1 source package in Jammy: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on a HP platform. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. Applied on oem-6.1 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2007823/+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 2007824] Re: Mute/mic LEDs and speaker no function on some HP platfroms
** Description changed: [Impact] The mic mute/audio mute LEDS and speaker are not work on some HP platforms. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs and speaker are working good. + Applied on oem-6.1 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). -- 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/2007824 Title: Mute/mic LEDs and speaker no function on some HP platfroms Status in linux-oem-6.1 package in Ubuntu: New Status in linux-oem-6.1 source package in Jammy: New Bug description: [Impact] The mic mute/audio mute LEDS and speaker are not work on some HP platforms. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs and speaker are working good. Applied on oem-6.1 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2007824/+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 2007830] Re: [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade
Thanks a lot I didn't know this was not the last kernel 'for most users". No idea why it was installed.. I suppressed this kernel and everything is fine now :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2007830 Title: [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade Status in linux-oracle package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-525 package in Ubuntu: Incomplete Bug description: Display on the second screen does not work since last kernel upgrade. It works using the previous one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 20 10:16:57 2023 DistUpgraded: 2022-10-21 09:45:54,530 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/525.78.01, 5.19.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:0774] NVIDIA Corporation GP104BM [GeForce GTX 1080 Mobile] [10de:1be0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GeForce GTX 1080 Max-Q [1028:07c0] InstallationDate: Installed on 2022-10-12 (130 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (122 days ago) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2007830/+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 2007908] Re: [Possible Regression] powerpc/tm:tm-resched-dscr in ubuntu_kernel_selftests failed on P8
** Description changed: Issue found with Focal hwe-5.15.0-66.73~20.04.1 on Power8 node "gulpin". Test failed with: test: tm_resched_dscr tags: git_version:bfd31f0-dirty Binding to cpu 8 main test running as pid 2542 Check DSCR TM context switch: !! killing tm_resched_dscr !! child died by signal 15 failure: tm_resched_dscr Nothing interesting in dmesg / syslog: $ dmesg | tail [ 20.556968] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f0: link becomes ready [ 20.572182] tg3 0022:01:00.2 enP34p1s0f2: Link is up at 1000 Mbps, full duplex [ 20.572187] tg3 0022:01:00.2 enP34p1s0f2: Flow control is off for TX and off for RX [ 20.572191] tg3 0022:01:00.2 enP34p1s0f2: EEE is disabled [ 20.572201] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f2: link becomes ready [ 24.598633] kauditd_printk_skb: 19 callbacks suppressed [ 24.598640] audit: type=1400 audit(1676957767.768:31): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/snap/bin/" pid=2171 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 27.682671] loop3: detected capacity change from 0 to 8 [ 28.618195] fbcon: Taking over console [ 28.747706] Console: switching to colour frame buffer device 128x48 This issue does not exist with 5.15.0-60.66~20.04.1 test: tm_resched_dscr tags: git_version:bfd31f0-dirty Binding to cpu 8 main test running as pid 28806 Check DSCR TM context switch: OK success: tm_resched_dscr - We didn't see this issue in Jammy 5.15 as Power8 was not supported - there, and this test was skipped on the Power9 node (looks like because - of the lack of PPC_FEATURE2_HTM) + We didn't catch this issue in Jammy 5.15 as Power8 was not supported + there, and this test was skipped on the Power9 node that got tested with + Jammy (looks like because of the lack of PPC_FEATURE2_HTM) -- 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/2007908 Title: [Possible Regression] powerpc/tm:tm-resched-dscr in ubuntu_kernel_selftests failed on P8 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found with Focal hwe-5.15.0-66.73~20.04.1 on Power8 node "gulpin". Test failed with: test: tm_resched_dscr tags: git_version:bfd31f0-dirty Binding to cpu 8 main test running as pid 2542 Check DSCR TM context switch: !! killing tm_resched_dscr !! child died by signal 15 failure: tm_resched_dscr Nothing interesting in dmesg / syslog: $ dmesg | tail [ 20.556968] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f0: link becomes ready [ 20.572182] tg3 0022:01:00.2 enP34p1s0f2: Link is up at 1000 Mbps, full duplex [ 20.572187] tg3 0022:01:00.2 enP34p1s0f2: Flow control is off for TX and off for RX [ 20.572191] tg3 0022:01:00.2 enP34p1s0f2: EEE is disabled [ 20.572201] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f2: link becomes ready [ 24.598633] kauditd_printk_skb: 19 callbacks suppressed [ 24.598640] audit: type=1400 audit(1676957767.768:31): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/snap/bin/" pid=2171 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 27.682671] loop3: detected capacity change from 0 to 8 [ 28.618195] fbcon: Taking over console [ 28.747706] Console: switching to colour frame buffer device 128x48 This issue does not exist with 5.15.0-60.66~20.04.1 test: tm_resched_dscr tags: git_version:bfd31f0-dirty Binding to cpu 8 main test running as pid 28806 Check DSCR TM context switch: OK success: tm_resched_dscr We didn't catch this issue in Jammy 5.15 as Power8 was not supported there, and this test was skipped on the Power9 node that got tested with Jammy (looks like because of the lack of PPC_FEATURE2_HTM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2007908/+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 2007908] Re: [Possible Regression] powerpc/tm:tm-resched-dscr in ubuntu_kernel_selftests failed on P8
** Description changed: - Issue found with J-hwe-5.15.0-66.73~20.04.1 on Power8 node "gulpin". + Issue found with Focal hwe-5.15.0-66.73~20.04.1 on Power8 node "gulpin". Test failed with: - test: tm_resched_dscr - tags: git_version:bfd31f0-dirty - Binding to cpu 8 - main test running as pid 2542 - Check DSCR TM context switch: - !! killing tm_resched_dscr - !! child died by signal 15 - failure: tm_resched_dscr + test: tm_resched_dscr + tags: git_version:bfd31f0-dirty + Binding to cpu 8 + main test running as pid 2542 + Check DSCR TM context switch: + !! killing tm_resched_dscr + !! child died by signal 15 + failure: tm_resched_dscr Nothing interesting in dmesg / syslog: $ dmesg | tail [ 20.556968] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f0: link becomes ready [ 20.572182] tg3 0022:01:00.2 enP34p1s0f2: Link is up at 1000 Mbps, full duplex [ 20.572187] tg3 0022:01:00.2 enP34p1s0f2: Flow control is off for TX and off for RX [ 20.572191] tg3 0022:01:00.2 enP34p1s0f2: EEE is disabled [ 20.572201] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f2: link becomes ready [ 24.598633] kauditd_printk_skb: 19 callbacks suppressed [ 24.598640] audit: type=1400 audit(1676957767.768:31): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/snap/bin/" pid=2171 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 27.682671] loop3: detected capacity change from 0 to 8 [ 28.618195] fbcon: Taking over console [ 28.747706] Console: switching to colour frame buffer device 128x48 - - This issue does not exist with 5.15.0-60.66~20.04.1 - test: tm_resched_dscr - tags: git_version:bfd31f0-dirty - Binding to cpu 8 - main test running as pid 28806 - Check DSCR TM context switch: OK - success: tm_resched_dscr + This issue does not exist with 5.15.0-60.66~20.04.1 + test: tm_resched_dscr + tags: git_version:bfd31f0-dirty + Binding to cpu 8 + main test running as pid 28806 + Check DSCR TM context switch: OK + success: tm_resched_dscr We didn't see this issue in Jammy 5.15 as Power8 was not supported there, and this test was skipped on the Power9 node (looks like because of the lack of PPC_FEATURE2_HTM) -- 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/2007908 Title: [Possible Regression] powerpc/tm:tm-resched-dscr in ubuntu_kernel_selftests failed on P8 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found with Focal hwe-5.15.0-66.73~20.04.1 on Power8 node "gulpin". Test failed with: test: tm_resched_dscr tags: git_version:bfd31f0-dirty Binding to cpu 8 main test running as pid 2542 Check DSCR TM context switch: !! killing tm_resched_dscr !! child died by signal 15 failure: tm_resched_dscr Nothing interesting in dmesg / syslog: $ dmesg | tail [ 20.556968] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f0: link becomes ready [ 20.572182] tg3 0022:01:00.2 enP34p1s0f2: Link is up at 1000 Mbps, full duplex [ 20.572187] tg3 0022:01:00.2 enP34p1s0f2: Flow control is off for TX and off for RX [ 20.572191] tg3 0022:01:00.2 enP34p1s0f2: EEE is disabled [ 20.572201] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f2: link becomes ready [ 24.598633] kauditd_printk_skb: 19 callbacks suppressed [ 24.598640] audit: type=1400 audit(1676957767.768:31): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/snap/bin/" pid=2171 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 27.682671] loop3: detected capacity change from 0 to 8 [ 28.618195] fbcon: Taking over console [ 28.747706] Console: switching to colour frame buffer device 128x48 This issue does not exist with 5.15.0-60.66~20.04.1 test: tm_resched_dscr tags: git_version:bfd31f0-dirty Binding to cpu 8 main test running as pid 28806 Check DSCR TM context switch: OK success: tm_resched_dscr We didn't catch this issue in Jammy 5.15 as Power8 was not supported there, and this test was skipped on the Power9 node that got tested with Jammy (looks like because of the lack of PPC_FEATURE2_HTM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2007908/+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 2007830] Re: [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade
The "5.19.0-1015-oracle" kernel you mention isn't something most users should be using. If you found it by accident then just ignore it because the correct latest kernel for Ubuntu 22.10 is the one that works: 5.19.0-31.32-generic If however you have a good reason for wanting the Oracle kernel then those files are at https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/ppa/+build/25514914 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2007830 Title: [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade Status in linux-oracle package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-525 package in Ubuntu: Incomplete Bug description: Display on the second screen does not work since last kernel upgrade. It works using the previous one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 20 10:16:57 2023 DistUpgraded: 2022-10-21 09:45:54,530 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/525.78.01, 5.19.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:0774] NVIDIA Corporation GP104BM [GeForce GTX 1080 Mobile] [10de:1be0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GeForce GTX 1080 Max-Q [1028:07c0] InstallationDate: Installed on 2022-10-12 (130 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (122 days ago) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2007830/+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 2007830] Re: [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade
I'm not sure to know how to do that. It's not possible through ubuntu update manager ? Also I went on this page https://packages.ubuntu.com/search?keywords=linux-generic but was not able to find kernel 5.19.0-1017-oracle -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2007830 Title: [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade Status in linux-oracle package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-525 package in Ubuntu: Incomplete Bug description: Display on the second screen does not work since last kernel upgrade. It works using the previous one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 20 10:16:57 2023 DistUpgraded: 2022-10-21 09:45:54,530 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/525.78.01, 5.19.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:0774] NVIDIA Corporation GP104BM [GeForce GTX 1080 Mobile] [10de:1be0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GeForce GTX 1080 Max-Q [1028:07c0] InstallationDate: Installed on 2022-10-12 (130 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (122 days ago) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2007830/+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 2007745] Re: [hwe-5.15] CONFIG_PCI_MESON not enabled
No logs needed as this is purely kernel configuration ** 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/2007745 Title: [hwe-5.15] CONFIG_PCI_MESON not enabled Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.15 package in Ubuntu: New Bug description: The PCI driver for the amlogic-based Meson platforms (CONFIG_PCI_MESON) is not enabled as a module in the 5.15 HWE kernel configuration: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/tree/debian.hwe-5.15/config/config.common.ubuntu?h=Ubuntu- hwe-5.15-5.15.0-66.73_20.04.1#n7702 This driver is important for systems like the ODROID HC4, which uses a PCIE-SATA bridge to provide a storage interface. This system is fully supported by the kernel (including a device tree), except for the fact that this PCI driver is disabled. Please look into enabling this for future releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007745/+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 2007932] [NEW] package linux-image-5.15.0-40-generic 5.15.0-40.43 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
Public bug reported: ... ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-40-generic 5.15.0-40.43 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spidermau 1518 F pulseaudio CasperMD5CheckResult: pass Date: Tue Feb 21 01:43:44 2023 ErrorMessage: el subproceso instalado paquete linux-image-5.15.0-40-generic script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2022-04-16 (311 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 240 G7 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e470211d-69dd-4736-9d0d-95903643a055 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.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 SourcePackage: linux-signed Title: package linux-image-5.15.0-40-generic 5.15.0-40.43 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2020 dmi.bios.release: 15.58 dmi.bios.vendor: Insyde dmi.bios.version: F.58 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 852C dmi.board.vendor: HP dmi.board.version: 16.22 dmi.chassis.asset.tag: 5CG00256ZQ dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 16.22 dmi.modalias: dmi:bvnInsyde:bvrF.58:bd06/12/2020:br15.58:efr16.22:svnHP:pnHP240G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn852C:rvr16.22:cvnHP:ct10:cvrChassisVersion:sku8VB15LT#ABM: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 240 G7 Notebook PC dmi.product.sku: 8VB15LT#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2007932 Title: package linux-image-5.15.0-40-generic 5.15.0-40.43 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 Status in linux-signed package in Ubuntu: New Bug description: ... ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-40-generic 5.15.0-40.43 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spidermau 1518 F pulseaudio CasperMD5CheckResult: pass Date: Tue Feb 21 01:43:44 2023 ErrorMessage: el subproceso instalado paquete linux-image-5.15.0-40-generic script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2022-04-16 (311 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 240 G7 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e470211d-69dd-4736-9d0d-95903643a055 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.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 SourcePackage: linux-signed Title: package linux-image-5.15.0-40-generic 5.15.0-40.43 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2020 dmi.bios.release: 15.58 dmi.bios.vendor: Insyde dmi.bios.version: F.58 dmi.board.a
[Kernel-packages] [Bug 2007904] Re: [Possible Regression] net:reuseaddr_ports_exhausted.sh in ubuntu_kernel_selftests failed on F-oem-5.14 / J-oem-5.17
** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/2007904 Title: [Possible Regression] net:reuseaddr_ports_exhausted.sh in ubuntu_kernel_selftests failed on F-oem-5.14 / J-oem-5.17 Status in ubuntu-kernel-tests: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: New Bug description: Issue found on F-oem-5.14.0-1058.66, it looks like a regression. This failure cannot be reproduced with 5.14.0-1057.64 Test log: TAP version 13 1..3 # Starting 3 tests from 1 test cases. # RUN global.reuseaddr_ports_exhausted_unreusable ... #OK global.reuseaddr_ports_exhausted_unreusable ok 1 global.reuseaddr_ports_exhausted_unreusable # RUN global.reuseaddr_ports_exhausted_reusable_same_euid ... #OK global.reuseaddr_ports_exhausted_reusable_same_euid ok 2 global.reuseaddr_ports_exhausted_reusable_same_euid # RUN global.reuseaddr_ports_exhausted_reusable_different_euid ... # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:Expected -1 (-1) == ret (0) # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:should fail to listen because only one uid reserves the port in TCP_LISTEN. # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:Expected -1 (-1) == ret (0) # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:should fail to listen because only one uid reserves the port in TCP_LISTEN. # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:Expected -1 (-1) == ret (0) # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:should fail to listen because only one uid reserves the port in TCP_LISTEN. # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:Expected -1 (-1) == ret (0) # reuseaddr_ports_exhausted.c:153:reuseaddr_ports_exhausted_reusable_different_euid:should fail to listen because only one uid reserves the port in TCP_LISTEN. # reuseaddr_ports_exhausted_reusable_different_euid: Test failed at step #13 # FAIL global.reuseaddr_ports_exhausted_reusable_different_euid not ok 3 global.reuseaddr_ports_exhausted_reusable_different_euid # FAILED: 2 / 3 tests passed. # Totals: pass:2 fail:1 xfail:0 xpass:0 skip:0 error:0 Test result with 5.14.0-1057.64 $ sudo ./reuseaddr_ports_exhausted.sh TAP version 13 1..3 # Starting 3 tests from 1 test cases. # RUN global.reuseaddr_ports_exhausted_unreusable ... #OK global.reuseaddr_ports_exhausted_unreusable ok 1 global.reuseaddr_ports_exhausted_unreusable # RUN global.reuseaddr_ports_exhausted_reusable_same_euid ... #OK global.reuseaddr_ports_exhausted_reusable_same_euid ok 2 global.reuseaddr_ports_exhausted_reusable_same_euid # RUN global.reuseaddr_ports_exhausted_reusable_different_euid ... #OK global.reuseaddr_ports_exhausted_reusable_different_euid ok 3 global.reuseaddr_ports_exhausted_reusable_different_euid # PASSED: 3 / 3 tests passed. # Totals: pass:3 fail:0 xfail:0 xpass:0 skip:0 error:0 tests done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2007904/+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 2007830] Re: [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade
After installing kernel 5.19.0-1017-oracle, if the problem still isn't fixed then also run: sudo apt install --reinstall nvidia-dkms-525 nvidia-driver-525 and reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2007830 Title: [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade Status in linux-oracle package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-525 package in Ubuntu: Incomplete Bug description: Display on the second screen does not work since last kernel upgrade. It works using the previous one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 20 10:16:57 2023 DistUpgraded: 2022-10-21 09:45:54,530 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/525.78.01, 5.19.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:0774] NVIDIA Corporation GP104BM [GeForce GTX 1080 Mobile] [10de:1be0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GeForce GTX 1080 Max-Q [1028:07c0] InstallationDate: Installed on 2022-10-12 (130 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (122 days ago) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2007830/+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 2007830] Re: [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade
Thanks. The latest kernel in that series is 5.19.0-1017 so please try that one and make sure you haven't forgotten to install the driver packages too: linux-modules-5.19.0-1017-oracle linux-modules-extra-5.19.0-1017-oracle ** Summary changed: - [nvidia] Display issue after boot - secondary screen not working since last kernel upgrade + [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade ** Package changed: linux (Ubuntu) => linux-oracle (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007830 Title: [nvidia] Display issue after boot - secondary screen not working since last linux-oracle kernel upgrade Status in linux-oracle package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-525 package in Ubuntu: Incomplete Bug description: Display on the second screen does not work since last kernel upgrade. It works using the previous one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 20 10:16:57 2023 DistUpgraded: 2022-10-21 09:45:54,530 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/525.78.01, 5.19.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:0774] NVIDIA Corporation GP104BM [GeForce GTX 1080 Mobile] [10de:1be0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GeForce GTX 1080 Max-Q [1028:07c0] InstallationDate: Installed on 2022-10-12 (130 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (122 days ago) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2007830/+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 2007830] Re: [nvidia] Display issue after boot - secondary screen not working since last kernel upgrade
Thanks for digging the issue. Yes sure here are the details : Kernel not working : Linux 5.19.0-1015-oracle Kernel working: Linux 5.19.0-31-generic The previous report have been generated through Kernel 5.19.0-31-generic since as mentioned with the 5.19.0-1015-oracle version I am not able to connect to the Internet (wireless adapter not working) and to generate the bug report. -- 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/2007830 Title: [nvidia] Display issue after boot - secondary screen not working since last kernel upgrade Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-525 package in Ubuntu: Incomplete Bug description: Display on the second screen does not work since last kernel upgrade. It works using the previous one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 20 10:16:57 2023 DistUpgraded: 2022-10-21 09:45:54,530 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/525.78.01, 5.19.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:0774] NVIDIA Corporation GP104BM [GeForce GTX 1080 Mobile] [10de:1be0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GeForce GTX 1080 Max-Q [1028:07c0] InstallationDate: Installed on 2022-10-12 (130 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (122 days ago) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007830/+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
