[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP failed with Bionic/Focal/Hirsute
More test results, it will take about: * 50 minutes to run on F-gcp-5.11 g1.small * 38 minutes to run on B-gcp-4.15 g1.small * 40 minutes to run on H-gcp-5.11 g1.small * 36 minutes to run on X-gcp-4.15 g1.small Also, it will take about 7m30s on I-azure-5.13 Standard_B1ms So I think a 60 min timeout (LTP_TIMEOUT_MUL=12) should be OK. ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Summary changed: - memcg_test_3 from controllers in LTP failed with Bionic/Focal/Hirsute + memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute -- 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/1836694 Title: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux source package in Impish: Confirmed Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+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 1945369] Re: memory cgroup disabled on Ubuntu Core 18
How where you able to set the kernel command line args permanentely on ubuntu core? -- 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/1945369 Title: memory cgroup disabled on Ubuntu Core 18 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu Core 18, the memory cgroup is disabled, it seems that it needs to be manually enabled. I was able to enable it by adding `cgroup_enable=memory cgroup_memory=1` to the kernel command line, but on Ubuntu I think the memory cgroup should be enabled by default shouldn't it? $ cat /proc/cgroups #subsys_name hierarchy num_cgroups enabled cpuset2 1 1 cpu 4 100 1 cpuacct 4 100 1 blkio 5 100 1 memory0 109 0 devices 6 100 1 freezer 9 4 1 net_cls 3 1 1 perf_event10 1 1 net_prio 3 1 1 pids 8 107 1 rdma 7 1 1 I see this with Linux localhost 5.4.0-1043-raspi #47~18.04.1-Ubuntu SMP PREEMPT Mon Aug 23 14:39:46 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux on Ubuntu Core 18, but folks have informed me that the same is true on Ubuntu Core 20 as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945369/+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 1945868] Re: focal kvm virtio_net set_features failed (-22)
** Package changed: qemu-kvm (Ubuntu) => qemu (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/1945868 Title: focal kvm virtio_net set_features failed (-22) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Setup linux-modules-5.4.0-88-generic within focal guest on a (equal) ubuntu 20.04 kvm bare metal machine. When using virtio as network driver it is failing with: net eth0: Fail to set guest offload. virtio_net virtio1 eth0: set_features() failed (-22); wanted 0x008000174a29, left 0x0 0800017ca29 followed by further kern log entries: [ cut here ] netdevice: br0: failed to disable 0x8000 on eth0! WARNING: CPU: 0 PID: 1048 at net/core/dev.c:8683 __netdev_update_features+0x4d1/0x9f0 Modules linked in: macvlan virtio_gpu ttm drm_kms_helper fb_sys_fops input_leds syscopyarea joydev sysfillrect serio_raw sysimgblt mac_hid sch_fq_codel 9p fscache 9pnet_virtio 9pnet bridge stp llc drm virtio_rng ip_tables x_tables autofs4 dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c psmouse virtio_net i2c_piix4 virtio_blk net_failover failover pata_acpi floppy CPU: 0 PID: 1048 Comm: brctl Tainted: GW 5.4.0-88-generic #99-Ubuntu Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 RIP: 0010:__netdev_update_features+0x4d1/0x9f0 Code: c7 c2 9b 30 9b a0 4c 8b 4d 88 48 85 c0 4d 0f 44 d4 4d 89 f0 48 8d 4d b8 4c 89 ca 4c 89 d6 48 c7 c7 d0 94 a3 a0 e8 dc 2d 19 00 <0f> 0b e9 5b fe ff ff 8b 45 9c 85 c0 0f 84 96 00 00 00 8b 45 9c f7 RSP: 0018:bf1840e0ba98 EFLAGS: 00010282 RAX: RBX: 000f RCX: 0006 RDX: 0007 RSI: 0082 RDI: 9c2c13a178c0 RBP: bf1840e0bb10 R08: 02d1 R09: 0004 R10: R11: 0001 R12: 9c2c0b258000 R13: 9c2c0b2580c0 R14: 9c2c0615a000 R15: 000f FS: 7f98be558580() GS:9c2c13a0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fffc24a1080 CR3: 00030b3e4000 CR4: 06f0 Call Trace: netdev_update_features+0x25/0x60 br_device_event+0x20f/0x300 [bridge] notifier_call_chain+0x55/0x80 raw_notifier_call_chain+0x16/0x20 call_netdevice_notifiers_info+0x2e/0x60 netdev_update_features+0x59/0x60 dev_disable_lro+0x21/0xf0 br_add_if+0x301/0x650 [bridge] add_del_if+0x67/0x80 [bridge] br_dev_ioctl+0x54/0x80 [bridge] dev_ifsioc+0xe5/0x3e0 ? _cond_resched+0x19/0x30 dev_ioctl+0x2dd/0x470 sock_do_ioctl+0xa8/0x140 ? evict+0x14c/0x1b0 sock_ioctl+0x24f/0x3c0 ? _cond_resched+0x19/0x30 ? get_max_files+0x20/0x20 do_vfs_ioctl+0x407/0x670 ksys_ioctl+0x67/0x90 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f98be47c50b Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 RSP: 002b:7ffd783321e8 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 0002 RCX: 7f98be47c50b RDX: 7ffd78332210 RSI: 89a2 RDI: 0003 RBP: 7ffd78332210 R08: 0020 R09: fefefeff77686d74 R10: 7ffd78333e80 R11: 0246 R12: 7ffd78333e7e R13: 7ffd78333e7e R14: R15: ---[ end trace 240d361752e8f3f0 ]--- [ cut here ] Temporary solution is to return to the old rtl8139 driver and slow network down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945868/+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 1945211] Re: Fix cold plugged USB device on certain PCIe USB cards
** Changed in: linux (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Chris Chiu (mschiu77) -- 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/1945211 Title: Fix cold plugged USB device on certain PCIe USB cards Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Bug description: [SRU Justification] [Impact] Cold plugged USB device was not detected on certain PCIe USB cards (like Inateck card connected to AM64 EVM or connected to J7200 EVM). And also the root hub mentioned in https://bugs.launchpad.net/bugs/1939638. Re-plugging the USB device always gets it enumerated. [Fix] As soonprimary roothub is registered, port status change is handled even before xHC is running and leads to cold plug USB devices not detected. Register both root hubs along with the secondary hcd for xhci. [Test Case] 1. Plug the USB device to the ports of problematic root hub. 2. Power on the machine. 3. Check if the USB device can work or not after boot. [Regression Potential] Low. It simply make sure both primary and secondary roothubs are registered along with the second HCD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945211/+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 1934557] Re: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop
** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1934557 Title: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: Backlight does not change. Neither with the keys, nor with the slider. Values in /sys/class/backlight/amdgpu_bl0/brightness do change. However without effect on the actual brightness of the screen, which seems to be stuck at maximum brightness. Following the instructions from here: https://wiki.ubuntu.com/Kernel/Debugging/Backlight ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: simon 1886 F pulseaudio /dev/snd/pcmC2D0p: simon 1886 F...m pulseaudio /dev/snd/controlC1: simon 1886 F pulseaudio /dev/snd/controlC0: simon 1886 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 3 09:46:53 2021 InstallationDate: Installed on 2021-07-03 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 21A0CTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 1.5 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET35W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrR1MET35W(1.05):bd04/23/2021:br1.5:efr1.5:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0CTO1WW dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO == SRU justification: [Impact] backlight can't be controlled on AMD platform. [Fix] AUX doesn't work on HDR panel, fallback to PWM mode to make backlight be controlled. [Test] Verified on hardware, backlight brightness works fine. [Where problems could occur] It may break backlight control on AMD platform. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1934557/+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 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
** Description changed: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- - aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel. + aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html - But after successfully updating to the 4.15 without those patches - applied, I can then upgrade to a 4.15 kernel with the above patches - included, and the instance will boot properly. + With that being said, after successfully updating to the 4.15 without + those patches applied, I can then upgrade to a 4.15 kernel with the + above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. -- 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/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+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 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
A test kernel with the patch can be found here: https://people.canonical.com/~khfeng/lp1878279/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) 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: IdeaPad 5 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 1938893] Re: Network perpherals not detected
As per comment in #4 this issue has gone with 5.11.0-27, I will close this bug with fix-released. Thanks ** Changed in: linux-signed-hwe-5.11 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1938893 Title: Network perpherals not detected Status in linux-signed-hwe-5.11 package in Ubuntu: Fix Released Bug description: After updating the kernel to the version 5.11.0.22 all network peripherals stopped working. It appears they are not detected on lshw or lsusb. I've tried with the ethernet port on the motherboard and an external wifi board and also using USB tethering from a phone. None was detected and network is not working. Then I've tried to go back to kernel version 5.8 which is still working correctly. If you need more info, feel free to ask me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 4 13:17:14 2021 InstallationDate: Installed on 2021-06-11 (53 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 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.11/+bug/1938893/+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 1945556] Re: Fix missing HDMI audio on Intel RKL
** 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945556 Title: Fix missing HDMI audio on Intel RKL Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] HDMI audio is missing on Intel RKL. [Fix] Also use BIOS provided value for HDA link. [Test] HDMI audio is back after the fix gets applied. [Where problems could occur] Because this is a regression, this patch simply brings back the old behavior for RKL systems. There could be RKL systems get fixed by the offending commit, so this might break those hypothetical systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945556/+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 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
** Description changed: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html But after successfully updating to the 4.15 without those patches applied, I can then upgrade to a test kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot. + + I have been unable to capture a stack trace using 'aws get-console- + output'. I enabled kdump and was unable to replicate the failure. So + there must be some sort of race with either ext4 and/or nvme. ** Description changed: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html But after successfully updating to the 4.15 without those patches - applied, I can then upgrade to a test kernel with the above patches + applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot. I have been unable to capture a stack trace using 'aws get-console- output'. I enabled kdump and was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. ** Description changed: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html But after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 - kernel installation, but still wouldn't boot. + kernel installation, but still wouldn't boot after installing the 4.15 + kernel. I have been unable to capture a stack trace using 'aws get-console- - output'. I enabled kdump and was unable to replicate the failure. So + output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. -- 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/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html But after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling
[Kernel-packages] [Bug 1946174] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946174 Title: Trackpad not being detected Status in linux package in Ubuntu: Confirmed Bug description: Laptop model: HP Pavilion - 15-ec1052ax Touchpad manufacturer: Elan Ubuntu version: 21.04 hirsute Hippo ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: abhi 1921 F pulseaudio /dev/snd/controlC0: abhi 1921 F pulseaudio /dev/snd/controlC1: abhi 1921 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 6 08:38:29 2021 InstallationDate: Installed on 2021-09-21 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=c22aafea-3ec6-436e-a4d4-fd586965dd93 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2021 dmi.bios.release: 15.25 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87B1 dmi.board.vendor: HP dmi.board.version: 31.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.23 dmi.modalias: dmi:bvnAMI:bvrF.25:bd08/18/2021:br15.25:efr31.23:svnHP:pnHPPavilionGamingLaptop15-ec1xxx:pvr:sku1N1G0PA#ACJ:rvnHP:rn87B1:rvr31.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec1xxx dmi.product.sku: 1N1G0PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946174/+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 1946174] [NEW] Trackpad not being detected
Public bug reported: Laptop model: HP Pavilion - 15-ec1052ax Touchpad manufacturer: Elan Ubuntu version: 21.04 hirsute Hippo ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: abhi 1921 F pulseaudio /dev/snd/controlC0: abhi 1921 F pulseaudio /dev/snd/controlC1: abhi 1921 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 6 08:38:29 2021 InstallationDate: Installed on 2021-09-21 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=c22aafea-3ec6-436e-a4d4-fd586965dd93 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2021 dmi.bios.release: 15.25 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87B1 dmi.board.vendor: HP dmi.board.version: 31.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.23 dmi.modalias: dmi:bvnAMI:bvrF.25:bd08/18/2021:br15.25:efr31.23:svnHP:pnHPPavilionGamingLaptop15-ec1xxx:pvr:sku1N1G0PA#ACJ:rvnHP:rn87B1:rvr31.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec1xxx dmi.product.sku: 1N1G0PA#ACJ dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "Output of cat /proc/bus/input/devices" https://bugs.launchpad.net/bugs/1946174/+attachment/5530903/+files/devices -- 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/1946174 Title: Trackpad not being detected Status in linux package in Ubuntu: New Bug description: Laptop model: HP Pavilion - 15-ec1052ax Touchpad manufacturer: Elan Ubuntu version: 21.04 hirsute Hippo ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: abhi 1921 F pulseaudio /dev/snd/controlC0: abhi 1921 F pulseaudio /dev/snd/controlC1: abhi 1921 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 6 08:38:29 2021 InstallationDate: Installed on 2021-09-21 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=c22aafea-3ec6-436e-a4d4-fd586965dd93 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2021 dmi.bios.release: 15.25 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87B1 dmi.board.vendor: HP dmi.board.version: 31.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.23 dmi.modalias: dmi:bvnAMI:bvrF.25:bd08/18/2021:br15.25:efr31.23:svnHP:pnHPPavilionGamingLaptop15-ec1xxx:pvr:sku1N1G0PA#ACJ:rvnHP:rn87B1:rvr31.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec1xxx dmi.product.sku: 1N1G0PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946174/+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 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set
Additional helpful insights from osmoticum on the Nvidia forum: The Xorg modesetting DDX seems to be fighting with the Nvidia DDX for DRM nodes [ 463.657] (II) modeset(G0): using drv /dev/dri/card0 but [ 463.658] (II) Applying OutputClass "nvidia" options to /dev/dri/card0 Nvidia appears to be adding a lot of DRM related stuff to the kernel driver (so it looks a lot like a real DRM driver to userspace now) and the modesetting DDX is getting further into its initialization. In my case, pointing the modesetting DDX to only look at non-Nvidia devices (the kmsdev option) and ensuring all the Nvidia kernel modules are fully loaded (instead of having them load on-demand) before starting X worked around this. The latter is for some weird race condition where the Nvidia driver is only partially loaded and https://gitlab.freedesktop.org/xorg/xserver/-/blob/master/config/udev.c#L135 fails, which causes modesetting to load regardless (it’s hardcoded in xf86platformAddDevice) The WARN_ON itself can still be triggered by simply opening a Nvidia primary DRM node though, e.g. with https://gitlab.freedesktop.org/mesa/drm/-/blob/master/tests/drmdevice.c, when some other DRM client like X or fbcon already has master. Because of https://patchwork.freedesktop.org/patch/367748 the Nvidia kernel driver can no longer use its internal grabOwnership to report if DRM master can be taken. https://forums.developer.nvidia.com/t/kernel-oops-on-boot-5-9-13-with-455-45-01/163751 -- 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/1930903 Title: Frequent kernel oops related to nvidia / nv_drm_master_set Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: After upgrading yesterday from ubuntu 20 to 21.04 my machine now exhibits frequent involuntary restarts, related to a kernel oops of the form Jun 3 10:48:32 zotac kernel: [ 20.464926] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm] [...] Jun 3 10:48:32 zotac kernel: [ 20.464958] Call Trace: Jun 3 10:48:32 zotac kernel: [ 20.464964] drm_new_set_master+0x7e/0x100 [drm] Jun 3 10:48:32 zotac kernel: [ 20.464994] drm_master_open+0x6e/0xa0 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465017] drm_open+0xf8/0x250 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465044] drm_stub_open+0xba/0x140 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465070] chrdev_open+0xf7/0x220 Jun 3 10:48:32 zotac kernel: [ 20.465075] ? cdev_device_add+0x90/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465078] do_dentry_open+0x156/0x370 Jun 3 10:48:32 zotac kernel: [ 20.465081] vfs_open+0x2d/0x30 Jun 3 10:48:32 zotac kernel: [ 20.465084] do_open+0x1c3/0x340 Jun 3 10:48:32 zotac kernel: [ 20.465087] path_openat+0x10a/0x1d0 Jun 3 10:48:32 zotac kernel: [ 20.465090] do_filp_open+0x8c/0x130 Jun 3 10:48:32 zotac kernel: [ 20.465093] ? __check_object_size+0x1c/0x20 Jun 3 10:48:32 zotac kernel: [ 20.465096] do_sys_openat2+0x9b/0x150 Jun 3 10:48:32 zotac kernel: [ 20.465099] __x64_sys_openat+0x56/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465102] do_syscall_64+0x38/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465105] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 3 10:48:32 zotac kernel: [ 20.465108] RIP: 0033:0x7fe6ea270954 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-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..0a.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 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jun 4 17:00:45 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18-generic, x86_64: installed nvidia, 460.80, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-05-09 (391 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64
[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
Today's also report. ** Attachment added: "prevboot-2021-10-05-c.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939966/+attachment/5530864/+files/prevboot-2021-10-05-c.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-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 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.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:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0
** Changed in: linux Status: Confirmed => Unknown -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+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 1521173]
Created attachment 299109 attachment-15734-0.html Okay great. Thanks for the link to FirmwareTestSuite. Chris Get BlueMail for Android On Oct 5, 2021, 9:25 AM, at 9:25 AM, bugzilla-dae...@bugzilla.kernel.org wrote: >https://bugzilla.kernel.org/show_bug.cgi?id=109691 > >--- Comment #21 from Paul Menzel >(pmenzel+bugzilla.kernel@molgen.mpg.de) --- >[Please remove the quote next time from your reply. If you look at the >Web >interface, the comments get needlessly long because of that.] > >(In reply to cspadijer from comment #20) > >[…] > >> Okay yes. I will mark as fixed and open up new for other issues you >> clarified as linux. Thanks for your help. > >Thank you. > >> For the firmware issues should I be reaching out to the vendors? > >Yes, only the vendors can fix the firmware, unless you use FLOSS >firmware like >coreboot based firmware for example. > >Unfortunately, my track record of getting vendors to fix their firmware >is not >so good, as you are only one customer using this weird operating system >and not >Microsoft Windows. But fingers crossed. > >Additionally you might want to point them to the Firmware Test Suite >(FWTS) >[1]. > > >[1]: https://wiki.ubuntu.com/FirmwareTestSuite/ > >-- >You may reply to this email to add a comment. > >You are receiving this mail because: >You reported the bug. -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1521173]
An upstream kernel since 4.2.0-22-generic has resolved the issue with this make/model of laptop. Laptop successfully boots now without the pci=nommconf boot parameter. -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+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 1521173]
[Please remove the quote next time from your reply. If you look at the Web interface, the comments get needlessly long because of that.] (In reply to cspadijer from comment #20) […] > Okay yes. I will mark as fixed and open up new for other issues you > clarified as linux. Thanks for your help. Thank you. > For the firmware issues should I be reaching out to the vendors? Yes, only the vendors can fix the firmware, unless you use FLOSS firmware like coreboot based firmware for example. Unfortunately, my track record of getting vendors to fix their firmware is not so good, as you are only one customer using this weird operating system and not Microsoft Windows. But fingers crossed. Additionally you might want to point them to the Firmware Test Suite (FWTS) [1]. [1]: https://wiki.ubuntu.com/FirmwareTestSuite/ -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+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 1521173]
Created attachment 299107 attachment-9243-0.html Hi Paul. Okay yes. I will mark as fixed and open up new for other issues you clarified as linux. Thanks for your help. For the firmware issues should I be reaching out to the vendors? Chris Get BlueMail for Android On Oct 5, 2021, 7:13 AM, at 7:13 AM, bugzilla-dae...@bugzilla.kernel.org wrote: >https://bugzilla.kernel.org/show_bug.cgi?id=109691 > >--- Comment #19 from Paul Menzel >(pmenzel+bugzilla.kernel@molgen.mpg.de) --- >(In reply to cspadijer from comment #18) >> Are you good with me using kernel: 5.11.0-37-generic or would you >> prefer I use a different kernel? >> The X555U is currently running Linux Mint 20.2 Cinnamon. >> >> FYI: >> I tried removing pci=noaer and it does boot now (without your patch). >> It has been a while since I tried removing pci=noaer and new kernels >get >> installed all the time so not sure what kernel first started allowing >it >> to boot without needing that line. >> However, there are still many errors on boot. > >The original bug seems to be solved now. As there are over ten comments >already, could you mark it as fixed, and create new issues? > >> dmesg --level=err,warn >> [ 0.105337] x86/cpu: VMX (outside TXT) disabled by BIOS >> [ 0.110761] MDS CPU bug present and SMT on, data leak possible. >See >> https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html >for >> more details. > >Is GNU/Linux applying the latest microcode updates? > >> [ 0.110761] #3 > >Cosmetic error. > >> [ 0.114598] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' >> [ 0.135583] ACPI BIOS Error (bug): Could not resolve symbol >> [\_SB.PCI0.RP01.PXSX], AE_NOT_FOUND (20201113/psargs-330) >> [ 0.135597] ACPI Error: Skipping While/If block >(20201113/psloop-427) >> [ 0.527786] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does >not >> cover the entire command/response buffer. [mem 0xfed4-0xfed4087f >flags >> 0x200] vs fed40080 f80 >> [ 0.527874] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does >not >> cover the entire command/response buffer. [mem 0xfed4-0xfed4087f >flags >> 0x200] vs fed40080 f80 > >Firmware issues. > >> [ 0.736009] i8042: PNP: PS/2 appears to have AUX port disabled, if >this is >> incorrect please boot with i8042.nopnp > >Can be ignored. > >> [ 0.738042] platform eisa.0: EISA: Cannot allocate resource for >mainboard >> [ 0.738044] platform eisa.0: Cannot allocate resource for EISA >slot 1 >> [ 0.738045] platform eisa.0: Cannot allocate resource for EISA >slot 2 >> [ 0.738046] platform eisa.0: Cannot allocate resource for EISA >slot 3 >> [ 0.738048] platform eisa.0: Cannot allocate resource for EISA >slot 4 >> [ 0.738049] platform eisa.0: Cannot allocate resource for EISA >slot 5 >> [ 0.738050] platform eisa.0: Cannot allocate resource for EISA >slot 6 >> [ 0.738051] platform eisa.0: Cannot allocate resource for EISA >slot 7 >> [ 0.738052] platform eisa.0: Cannot allocate resource for EISA >slot 8 > >Is there an EISA slot? > >> [ 1.268806] r8169 :02:00.0: can't disable ASPM; OS doesn't >have ASPM >> control > >Can be ignored. > >> [ 1.329939] i2c_hid i2c-ELAN1000:00: supply vdd not found, using >dummy >> regulator >> [ 1.329973] i2c_hid i2c-ELAN1000:00: supply vddl not found, using >dummy >> regulator > >Please contact the Linux folks about this. But first try the latest >Linux >mainline version. > >> [ 1.611704] ata1.00: supports DRM functions and may not be fully >> accessible >> [ 1.613394] ata1.00: supports DRM functions and may not be fully >> accessible >> [ 5.726419] elan_i2c i2c-ELAN1000:00: supply vcc not found, using >dummy >> regulator >> [ 6.376762] nvidia: loading out-of-tree module taints kernel. >> [ 6.376775] nvidia: module license 'NVIDIA' taints kernel. >> [ 6.376776] Disabling lock debugging due to kernel taint >> >> [ 6.884240] NVRM: loading NVIDIA UNIX x86_64 Kernel Module >470.63.01 Tue >> Aug 3 20:44:16 UTC 2021 >> [ 6.958699] nvidia_uvm: module uses symbols from proprietary >module >> nvidia, inheriting taint. >> [ 8.533945] ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4 >type >> mismatch - Found [Buffer], ACPI requires [Package] >(20201113/nsarguments-61) > >Firmware issue. > >> Chris > >I do not see any AER messages, so please create new issues. > >> On 2021-10-03 2:03 a.m., bugzilla-dae...@bugzilla.kernel.org wrote: > >[…] > >Please remove the citation/quotes when replying by email in the future, >when >not using interleaved style when replying. > >-- >You may reply to this email to add a comment. > >You are receiving this mail because: >You reported the bug. -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source
[Kernel-packages] [Bug 1521173]
(In reply to cspadijer from comment #18) > Are you good with me using kernel: 5.11.0-37-generic or would you > prefer I use a different kernel? > The X555U is currently running Linux Mint 20.2 Cinnamon. > > FYI: > I tried removing pci=noaer and it does boot now (without your patch). > It has been a while since I tried removing pci=noaer and new kernels get > installed all the time so not sure what kernel first started allowing it > to boot without needing that line. > However, there are still many errors on boot. The original bug seems to be solved now. As there are over ten comments already, could you mark it as fixed, and create new issues? > dmesg --level=err,warn > [ 0.105337] x86/cpu: VMX (outside TXT) disabled by BIOS > [ 0.110761] MDS CPU bug present and SMT on, data leak possible. See > https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for > more details. Is GNU/Linux applying the latest microcode updates? > [ 0.110761] #3 Cosmetic error. > [ 0.114598] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' > [ 0.135583] ACPI BIOS Error (bug): Could not resolve symbol > [\_SB.PCI0.RP01.PXSX], AE_NOT_FOUND (20201113/psargs-330) > [ 0.135597] ACPI Error: Skipping While/If block (20201113/psloop-427) > [ 0.527786] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not > cover the entire command/response buffer. [mem 0xfed4-0xfed4087f flags > 0x200] vs fed40080 f80 > [ 0.527874] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not > cover the entire command/response buffer. [mem 0xfed4-0xfed4087f flags > 0x200] vs fed40080 f80 Firmware issues. > [ 0.736009] i8042: PNP: PS/2 appears to have AUX port disabled, if this is > incorrect please boot with i8042.nopnp Can be ignored. > [ 0.738042] platform eisa.0: EISA: Cannot allocate resource for mainboard > [ 0.738044] platform eisa.0: Cannot allocate resource for EISA slot 1 > [ 0.738045] platform eisa.0: Cannot allocate resource for EISA slot 2 > [ 0.738046] platform eisa.0: Cannot allocate resource for EISA slot 3 > [ 0.738048] platform eisa.0: Cannot allocate resource for EISA slot 4 > [ 0.738049] platform eisa.0: Cannot allocate resource for EISA slot 5 > [ 0.738050] platform eisa.0: Cannot allocate resource for EISA slot 6 > [ 0.738051] platform eisa.0: Cannot allocate resource for EISA slot 7 > [ 0.738052] platform eisa.0: Cannot allocate resource for EISA slot 8 Is there an EISA slot? > [ 1.268806] r8169 :02:00.0: can't disable ASPM; OS doesn't have ASPM > control Can be ignored. > [ 1.329939] i2c_hid i2c-ELAN1000:00: supply vdd not found, using dummy > regulator > [ 1.329973] i2c_hid i2c-ELAN1000:00: supply vddl not found, using dummy > regulator Please contact the Linux folks about this. But first try the latest Linux mainline version. > [ 1.611704] ata1.00: supports DRM functions and may not be fully > accessible > [ 1.613394] ata1.00: supports DRM functions and may not be fully > accessible > [ 5.726419] elan_i2c i2c-ELAN1000:00: supply vcc not found, using dummy > regulator > [ 6.376762] nvidia: loading out-of-tree module taints kernel. > [ 6.376775] nvidia: module license 'NVIDIA' taints kernel. > [ 6.376776] Disabling lock debugging due to kernel taint > > [ 6.884240] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue > Aug 3 20:44:16 UTC 2021 > [ 6.958699] nvidia_uvm: module uses symbols from proprietary module > nvidia, inheriting taint. > [ 8.533945] ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4 type > mismatch - Found [Buffer], ACPI requires [Package] (20201113/nsarguments-61) Firmware issue. > Chris I do not see any AER messages, so please create new issues. > On 2021-10-03 2:03 a.m., bugzilla-dae...@bugzilla.kernel.org wrote: […] Please remove the citation/quotes when replying by email in the future, when not using interleaved style when replying. -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [
[Kernel-packages] [Bug 1521173]
Are you good with me using kernel: 5.11.0-37-generic or would you prefer I use a different kernel? The X555U is currently running Linux Mint 20.2 Cinnamon. FYI: I tried removing pci=noaer and it does boot now (without your patch). It has been a while since I tried removing pci=noaer and new kernels get installed all the time so not sure what kernel first started allowing it to boot without needing that line. However, there are still many errors on boot. dmesg --level=err,warn [ 0.105337] x86/cpu: VMX (outside TXT) disabled by BIOS [ 0.110761] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. [ 0.110761] #3 [ 0.114598] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [ 0.135583] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.RP01.PXSX], AE_NOT_FOUND (20201113/psargs-330) [ 0.135597] ACPI Error: Skipping While/If block (20201113/psloop-427) [ 0.527786] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed4-0xfed4087f flags 0x200] vs fed40080 f80 [ 0.527874] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed4-0xfed4087f flags 0x200] vs fed40080 f80 [ 0.736009] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp [ 0.738042] platform eisa.0: EISA: Cannot allocate resource for mainboard [ 0.738044] platform eisa.0: Cannot allocate resource for EISA slot 1 [ 0.738045] platform eisa.0: Cannot allocate resource for EISA slot 2 [ 0.738046] platform eisa.0: Cannot allocate resource for EISA slot 3 [ 0.738048] platform eisa.0: Cannot allocate resource for EISA slot 4 [ 0.738049] platform eisa.0: Cannot allocate resource for EISA slot 5 [ 0.738050] platform eisa.0: Cannot allocate resource for EISA slot 6 [ 0.738051] platform eisa.0: Cannot allocate resource for EISA slot 7 [ 0.738052] platform eisa.0: Cannot allocate resource for EISA slot 8 [ 1.268806] r8169 :02:00.0: can't disable ASPM; OS doesn't have ASPM control [ 1.329939] i2c_hid i2c-ELAN1000:00: supply vdd not found, using dummy regulator [ 1.329973] i2c_hid i2c-ELAN1000:00: supply vddl not found, using dummy regulator [ 1.611704] ata1.00: supports DRM functions and may not be fully accessible [ 1.613394] ata1.00: supports DRM functions and may not be fully accessible [ 5.726419] elan_i2c i2c-ELAN1000:00: supply vcc not found, using dummy regulator [ 6.376762] nvidia: loading out-of-tree module taints kernel. [ 6.376775] nvidia: module license 'NVIDIA' taints kernel. [ 6.376776] Disabling lock debugging due to kernel taint [ 6.884240] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 [ 6.958699] nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint. [ 8.533945] ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20201113/nsarguments-61) Chris On 2021-10-03 2:03 a.m., bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=109691 > > Naveen Naidu (naveennaidu...@gmail.com) changed: > > What|Removed |Added > > Attachment #299043|0 |1 > is obsolete|| > > --- Comment #15 from Naveen Naidu (naveennaidu...@gmail.com) --- > Created attachment 299071 >--> https://bugzilla.kernel.org/attachment.cgi?id=299071=edit > Patch for the AER message spew > > This is the correct patch. Please use this and ignore the previous patch. > -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
[Kernel-packages] [Bug 1521173]
Created attachment 299081 attachment-4100-0.html Okay sounds good. I will try it soon. Chris Get BlueMail for Android On Oct 3, 2021, 2:03 AM, at 2:03 AM, bugzilla-dae...@bugzilla.kernel.org wrote: >https://bugzilla.kernel.org/show_bug.cgi?id=109691 > >Naveen Naidu (naveennaidu...@gmail.com) changed: > > What|Removed |Added > > Attachment #299043|0 |1 >is obsolete|| > >--- Comment #15 from Naveen Naidu (naveennaidu...@gmail.com) --- >Created attachment 299071 > --> https://bugzilla.kernel.org/attachment.cgi?id=299071=edit >Patch for the AER message spew > >This is the correct patch. Please use this and ignore the previous >patch. > >-- >You may reply to this email to add a comment. > >You are receiving this mail because: >You reported the bug. -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1942459] Re: Speakup modules not included in Hirsute kernel
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1942459 Title: Speakup modules not included in Hirsute kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [SRU Justification] [Impact] The kernel modules for the speakup screen reader are not available in Ubuntu 21.04/hirsute. $ modinfo speakup_ltlk modinfo: ERROR: Module speakup_ltlk not found. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-31-generic 5.11.0-31.33 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 3207 F pulseaudio /dev/snd/pcmC0D0p: john 3207 F...m pulseaudio /dev/snd/controlC1: john 3207 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Thu Sep 2 10:46:10 2021 InstallationDate: Installed on 2021-08-25 (8 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. enxf2766f074582 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=de5924a4-e0f6-4c11-a364-ea107efc1086 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2018 dmi.bios.release: 65.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd12/13/2018:br65.29:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.product.sku: 0617 dmi.sys.vendor: Dell Inc. [Fix] CONFIG_ACCESSIBILITY=y CONFIG_SPEAKUP=y [Test Plan] Extract modules from linux-modules-extra and verify that speakup* modules exist. [Where problems could occur] Enabling CONFIG_ACCESSIBILITY could affect console output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942459/+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 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
Have been unable to capture a stack trace using 'aws get-console- output'. Enabled kdump and was unable to replicate the failed boot, which makes this feel like a race condition with NVME. -- 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/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html But after successfully updating to the 4.15 without those patches applied, I can then upgrade to a test kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+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-meta-intel-5.13/5.13.0.1006.7)
All autopkgtests for the newly accepted linux-meta-intel-5.13 (5.13.0.1006.7) for focal have finished running. The following regressions have been reported in tests triggered by the package: openafs/1.8.4~pre1-1ubuntu2.2 (amd64) dm-writeboost/2.2.9-1ubuntu1.3 (amd64) rtl8821ce/5.5.2.1-0ubuntu4~20.04.3 (amd64) gost-crypto/0.3.2-2ubuntu0.2 (amd64) glibc/2.31-0ubuntu9.2 (amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) 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-meta-intel-5.13 [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1946154] Re: Touchpad, graphics and slow programs
** Attachment added: "Picture of the desktop after the battery shutdown" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1946154/+attachment/5530860/+files/Screenshot%20from%202021-10-05%2008-04-50.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946154 Title: Touchpad, graphics and slow programs Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: After computer turned off for battery saving, kernel is not able to access touchpad. Furthermore, desktop is not able to show a clean image and a lot of programs have become very slow (specially zoom and firefox). Problem persists after reboots, but is entirely new after the battery saving shut down event. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 14:12:09 2021 InstallationDate: Installed on 2021-01-08 (270 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 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.11/+bug/1946154/+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 1946154] [NEW] Touchpad, graphics and slow programs
Public bug reported: After computer turned off for battery saving, kernel is not able to access touchpad. Furthermore, desktop is not able to show a clean image and a lot of programs have become very slow (specially zoom and firefox). Problem persists after reboots, but is entirely new after the battery saving shut down event. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 14:12:09 2021 InstallationDate: Installed on 2021-01-08 (270 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946154 Title: Touchpad, graphics and slow programs Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: After computer turned off for battery saving, kernel is not able to access touchpad. Furthermore, desktop is not able to show a clean image and a lot of programs have become very slow (specially zoom and firefox). Problem persists after reboots, but is entirely new after the battery saving shut down event. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 14:12:09 2021 InstallationDate: Installed on 2021-01-08 (270 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 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.11/+bug/1946154/+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 1942633] Re: Can not boot impish in Cavium ThunderX
Also good in focal: ubuntu@doerfel:~$ cat /proc/version Linux version 5.13.0-17-generic (buildd@bos02-arm64-034) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #17~20.04.1-Ubuntu SMP Tue Sep 28 14:05:10 UTC 2021 -- 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/1942633 Title: Can not boot impish in Cavium ThunderX Status in linux package in Ubuntu: Fix Committed Bug description: Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits I tried 2 releases: - 20210817 ( https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ ) - 20210830 ( https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ ) 20210817: Ends the deploy successfully but fails to boot from disk: ``` [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11] [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc (Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1) [0.00] Machine model: Cavium ThunderX CN88XX board [ 139.896752] raid6: xor() 1224 MB/s, rmw enabled [ 139.957046] raid6: using neon recovery algorithm [ 140.020937] xor: measuring software checksum speed [ 140.085571]8regs : 2432 MB/sec [ 140.149834]32regs : 2687 MB/sec [ 140.212202]arm64_neon : 4390 MB/sec [ 140.271985] xor: using function: arm64_neon (4390 MB/sec) [ 140.335013] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 140.569847] Btrfs loaded, crc32c=crc32c-generic, zoned=yes Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. ``` 20210830 Fails the network boot: ``` [ 140.351066] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no find a nic with 1c:1b:0d:0d:52:7c done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: Interface BOOTIF did not appear in time done. ipconfig: BOOTIF: SIOCGIFINDEX: No such device ipconfig: no devices to configure ``` I will attach full logs of each try. JFYI, this is the same machine as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+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 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
** Description changed: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel. + + If I remove these patches the instance correctly boots the 4.15 kernel + + https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html + + But after successfully updating to the 4.15 without those patches + applied, I can then upgrade to a test kernel with the above patches + included, and the instance will boot properly. + + This problem only appears on metal instances, which uses NVME instead of + XVDA devices. + + AWS instances also use the 'discard' mount option with ext4, thought + maybe there could be a race condition between ext4 discard and journal + flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 + kernel installation, but still wouldn't boot. -- 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/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html But after successfully updating to the 4.15 without those patches applied, I can then upgrade to a test kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+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 1946152] [NEW] my touchpad is not detected. I don't see it when I run 'xinput list' in the terminal.
Public bug reported: Here is the output of the command line 'cat /proc/bus/input/devices' : I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:49/PNP0C09:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=60070290 8380207af040d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="MSI WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input7 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=13 B: KEY=10003 30 e 0 B: MSC=10 I: Bus=0019 Vendor=0001 Product=0001 Version=0100 N: Name="gpio-keys" P: Phys=gpio-keys/input0 S: Sysfs=/devices/platform/ACPI0011:00/gpio-keys.1.auto/input/input8 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=3 B: KEY=0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input17 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=5986 Product=211b Version=0302 N: Name="HD Webcam: HD Webcam" P: Phys=usb-:00:14.0-7/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input20 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=046d Product=c077 Version=0111 N: Name="Logitech USB Optical Mouse" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C077.0004/input/input32 U: Uniq= H: Handlers=mouse0 event16 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=903 B: MSC=10 When I run 'xinput list' : ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)] ↳ MSI WMI hotkeys id=12 [slave keyboard (3)] ↳ Sleep Button
[Kernel-packages] [Bug 1946149] [NEW] Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
Public bug reported: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel. ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Package changed: ubuntu => linux-aws (Ubuntu) -- 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/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+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 1940448] Re: CT state not reset when packet redirected to different port
This bug was fixed in the package linux-bluefield - 5.4.0-1019.22 --- linux-bluefield (5.4.0-1019.22) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1019.22 -proposed tracker (LP: #1942533) * Focal update: v5.4.134 upstream stable release (LP: #1939440) - [Config] bluefield: CONFIG_BATTERY_RT5033=m * Fix fragmentation support for TC connection tracking (LP: #1940872) - net/sched: act_ct: fix restore the qdisc_skb_cb after defrag - net/sched: act_ct: fix miss set mru for ovs after defrag in act_ct - net/sched: fix miss init the mru in qdisc_skb_cb - net/sched: act_ct: fix wild memory access when clearing fragments - Revert "net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow" - net/sched: act_mirred: refactor the handle of xmit - net/sched: The error lable position is corrected in ct_init_module - net/sched: sch_frag: add generic packet fragment support. - ipv6: add ipv6_fragment hook in ipv6_stub * Add the upcoming BlueField-3 device ID (LP: #1941803) - net/mlx5: Update the list of the PCI supported devices * CT state not reset when packet redirected to different port (LP: #1940448) - Revert "UBUNTU: SAUCE: net/sched: act_mirred: Reset ct when reinserting skb back into queue" - net: sched: act_mirred: Reset ct info when mirror/redirect skb * Export xfrm_policy_lookup_bytype function (LP: #1934313) - SAUCE: xfrm: IPsec Export xfrm_policy_lookup_bytype function [ Ubuntu: 5.4.0-85.95 ] * focal/linux: 5.4.0-85.95 -proposed tracker (LP: #1942557) * please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248) - [Config] Disable virtualbox dkms build * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.09.06) * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771) - Disable CONFIG_HISI_DMA - [Config] Record hisi_dma no longer built for arm64 * memory leaking when removing a profile (LP: #1939915) - apparmor: Fix memory leak of profile proxy * CryptoExpress EP11 cards are going offline (LP: #1939618) - s390/zcrypt: Support for CCA protected key block version 2 - s390: Replace zero-length array with flexible-array member - s390/zcrypt: Use scnprintf() for avoiding potential buffer overflow - s390/zcrypt: replace snprintf/sprintf with scnprintf - s390/ap: Remove ap device suspend and resume callbacks - s390/zcrypt: use fallthrough; - s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc - s390/ap: remove power management code from ap bus and drivers - s390/ap: introduce new ap function ap_get_qdev() - s390/zcrypt: use kzalloc - s390/zcrypt: fix smatch warnings - s390/zcrypt: code beautification and struct field renames - s390/zcrypt: split ioctl function into smaller code units - s390/ap: rename and clarify ap state machine related stuff - s390/zcrypt: provide cex4 cca sysfs attributes for cex3 - s390/ap: rework crypto config info and default domain code - s390/zcrypt: simplify cca_findcard2 loop code - s390/zcrypt: remove set_fs() invocation in zcrypt device driver - s390/ap: remove unnecessary spin_lock_init() - s390/zcrypt: Support for CCA APKA master keys - s390/zcrypt: introduce msg tracking in zcrypt functions - s390/ap: split ap queue state machine state from device state - s390/ap: add error response code field for ap queue devices - s390/ap: add card/queue deconfig state - s390/sclp: Add support for SCLP AP adapter config/deconfig - s390/ap: Support AP card SCLP config and deconfig operations - s390/ap/zcrypt: revisit ap and zcrypt error handling - s390/zcrypt: move ap_msg param one level up the call chain - s390/zcrypt: Introduce Failure Injection feature - s390/zcrypt: fix wrong format specifications - s390/ap: fix ap devices reference counting - s390/zcrypt: return EIO when msg retry limit reached - s390/zcrypt: fix zcard and zqueue hot-unplug memleak - s390/ap: Fix hanging ioctl caused by wrong msg counter * memfd from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1926142) - SAUCE: selftests/memfd: fix build when F_SEAL_FUTURE_WRITE is not defined * [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands (LP: #1939855) - ice: Fix bad register reads * ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() (LP: #1941829) - selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test * e1000e blocks the boot process when it tried to write checksum to its NVM (LP: #1936998) - e1000e: Do not take care about recovery NVM checksum * Focal
[Kernel-packages] [Bug 1931843] Re: Update mlx-bootctl to access new fields in EEPROM MFG
This bug was fixed in the package linux-bluefield - 5.4.0-1019.22 --- linux-bluefield (5.4.0-1019.22) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1019.22 -proposed tracker (LP: #1942533) * Focal update: v5.4.134 upstream stable release (LP: #1939440) - [Config] bluefield: CONFIG_BATTERY_RT5033=m * Fix fragmentation support for TC connection tracking (LP: #1940872) - net/sched: act_ct: fix restore the qdisc_skb_cb after defrag - net/sched: act_ct: fix miss set mru for ovs after defrag in act_ct - net/sched: fix miss init the mru in qdisc_skb_cb - net/sched: act_ct: fix wild memory access when clearing fragments - Revert "net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow" - net/sched: act_mirred: refactor the handle of xmit - net/sched: The error lable position is corrected in ct_init_module - net/sched: sch_frag: add generic packet fragment support. - ipv6: add ipv6_fragment hook in ipv6_stub * Add the upcoming BlueField-3 device ID (LP: #1941803) - net/mlx5: Update the list of the PCI supported devices * CT state not reset when packet redirected to different port (LP: #1940448) - Revert "UBUNTU: SAUCE: net/sched: act_mirred: Reset ct when reinserting skb back into queue" - net: sched: act_mirred: Reset ct info when mirror/redirect skb * Export xfrm_policy_lookup_bytype function (LP: #1934313) - SAUCE: xfrm: IPsec Export xfrm_policy_lookup_bytype function [ Ubuntu: 5.4.0-85.95 ] * focal/linux: 5.4.0-85.95 -proposed tracker (LP: #1942557) * please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248) - [Config] Disable virtualbox dkms build * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.09.06) * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771) - Disable CONFIG_HISI_DMA - [Config] Record hisi_dma no longer built for arm64 * memory leaking when removing a profile (LP: #1939915) - apparmor: Fix memory leak of profile proxy * CryptoExpress EP11 cards are going offline (LP: #1939618) - s390/zcrypt: Support for CCA protected key block version 2 - s390: Replace zero-length array with flexible-array member - s390/zcrypt: Use scnprintf() for avoiding potential buffer overflow - s390/zcrypt: replace snprintf/sprintf with scnprintf - s390/ap: Remove ap device suspend and resume callbacks - s390/zcrypt: use fallthrough; - s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc - s390/ap: remove power management code from ap bus and drivers - s390/ap: introduce new ap function ap_get_qdev() - s390/zcrypt: use kzalloc - s390/zcrypt: fix smatch warnings - s390/zcrypt: code beautification and struct field renames - s390/zcrypt: split ioctl function into smaller code units - s390/ap: rename and clarify ap state machine related stuff - s390/zcrypt: provide cex4 cca sysfs attributes for cex3 - s390/ap: rework crypto config info and default domain code - s390/zcrypt: simplify cca_findcard2 loop code - s390/zcrypt: remove set_fs() invocation in zcrypt device driver - s390/ap: remove unnecessary spin_lock_init() - s390/zcrypt: Support for CCA APKA master keys - s390/zcrypt: introduce msg tracking in zcrypt functions - s390/ap: split ap queue state machine state from device state - s390/ap: add error response code field for ap queue devices - s390/ap: add card/queue deconfig state - s390/sclp: Add support for SCLP AP adapter config/deconfig - s390/ap: Support AP card SCLP config and deconfig operations - s390/ap/zcrypt: revisit ap and zcrypt error handling - s390/zcrypt: move ap_msg param one level up the call chain - s390/zcrypt: Introduce Failure Injection feature - s390/zcrypt: fix wrong format specifications - s390/ap: fix ap devices reference counting - s390/zcrypt: return EIO when msg retry limit reached - s390/zcrypt: fix zcard and zqueue hot-unplug memleak - s390/ap: Fix hanging ioctl caused by wrong msg counter * memfd from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1926142) - SAUCE: selftests/memfd: fix build when F_SEAL_FUTURE_WRITE is not defined * [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands (LP: #1939855) - ice: Fix bad register reads * ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() (LP: #1941829) - selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test * e1000e blocks the boot process when it tried to write checksum to its NVM (LP: #1936998) - e1000e: Do not take care about recovery NVM checksum * Focal
[Kernel-packages] [Bug 1934819] Re: Fix err check for nf_conntrack_confirm
This bug was fixed in the package linux-bluefield - 5.4.0-1019.22 --- linux-bluefield (5.4.0-1019.22) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1019.22 -proposed tracker (LP: #1942533) * Focal update: v5.4.134 upstream stable release (LP: #1939440) - [Config] bluefield: CONFIG_BATTERY_RT5033=m * Fix fragmentation support for TC connection tracking (LP: #1940872) - net/sched: act_ct: fix restore the qdisc_skb_cb after defrag - net/sched: act_ct: fix miss set mru for ovs after defrag in act_ct - net/sched: fix miss init the mru in qdisc_skb_cb - net/sched: act_ct: fix wild memory access when clearing fragments - Revert "net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow" - net/sched: act_mirred: refactor the handle of xmit - net/sched: The error lable position is corrected in ct_init_module - net/sched: sch_frag: add generic packet fragment support. - ipv6: add ipv6_fragment hook in ipv6_stub * Add the upcoming BlueField-3 device ID (LP: #1941803) - net/mlx5: Update the list of the PCI supported devices * CT state not reset when packet redirected to different port (LP: #1940448) - Revert "UBUNTU: SAUCE: net/sched: act_mirred: Reset ct when reinserting skb back into queue" - net: sched: act_mirred: Reset ct info when mirror/redirect skb * Export xfrm_policy_lookup_bytype function (LP: #1934313) - SAUCE: xfrm: IPsec Export xfrm_policy_lookup_bytype function [ Ubuntu: 5.4.0-85.95 ] * focal/linux: 5.4.0-85.95 -proposed tracker (LP: #1942557) * please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248) - [Config] Disable virtualbox dkms build * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.09.06) * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771) - Disable CONFIG_HISI_DMA - [Config] Record hisi_dma no longer built for arm64 * memory leaking when removing a profile (LP: #1939915) - apparmor: Fix memory leak of profile proxy * CryptoExpress EP11 cards are going offline (LP: #1939618) - s390/zcrypt: Support for CCA protected key block version 2 - s390: Replace zero-length array with flexible-array member - s390/zcrypt: Use scnprintf() for avoiding potential buffer overflow - s390/zcrypt: replace snprintf/sprintf with scnprintf - s390/ap: Remove ap device suspend and resume callbacks - s390/zcrypt: use fallthrough; - s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc - s390/ap: remove power management code from ap bus and drivers - s390/ap: introduce new ap function ap_get_qdev() - s390/zcrypt: use kzalloc - s390/zcrypt: fix smatch warnings - s390/zcrypt: code beautification and struct field renames - s390/zcrypt: split ioctl function into smaller code units - s390/ap: rename and clarify ap state machine related stuff - s390/zcrypt: provide cex4 cca sysfs attributes for cex3 - s390/ap: rework crypto config info and default domain code - s390/zcrypt: simplify cca_findcard2 loop code - s390/zcrypt: remove set_fs() invocation in zcrypt device driver - s390/ap: remove unnecessary spin_lock_init() - s390/zcrypt: Support for CCA APKA master keys - s390/zcrypt: introduce msg tracking in zcrypt functions - s390/ap: split ap queue state machine state from device state - s390/ap: add error response code field for ap queue devices - s390/ap: add card/queue deconfig state - s390/sclp: Add support for SCLP AP adapter config/deconfig - s390/ap: Support AP card SCLP config and deconfig operations - s390/ap/zcrypt: revisit ap and zcrypt error handling - s390/zcrypt: move ap_msg param one level up the call chain - s390/zcrypt: Introduce Failure Injection feature - s390/zcrypt: fix wrong format specifications - s390/ap: fix ap devices reference counting - s390/zcrypt: return EIO when msg retry limit reached - s390/zcrypt: fix zcard and zqueue hot-unplug memleak - s390/ap: Fix hanging ioctl caused by wrong msg counter * memfd from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1926142) - SAUCE: selftests/memfd: fix build when F_SEAL_FUTURE_WRITE is not defined * [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands (LP: #1939855) - ice: Fix bad register reads * ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() (LP: #1941829) - selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test * e1000e blocks the boot process when it tried to write checksum to its NVM (LP: #1936998) - e1000e: Do not take care about recovery NVM checksum * Focal
[Kernel-packages] [Bug 1934499] Re: New BPF helpers to query conntrack and to generate/validate SYN cookies
This bug was fixed in the package linux-bluefield - 5.4.0-1019.22 --- linux-bluefield (5.4.0-1019.22) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1019.22 -proposed tracker (LP: #1942533) * Focal update: v5.4.134 upstream stable release (LP: #1939440) - [Config] bluefield: CONFIG_BATTERY_RT5033=m * Fix fragmentation support for TC connection tracking (LP: #1940872) - net/sched: act_ct: fix restore the qdisc_skb_cb after defrag - net/sched: act_ct: fix miss set mru for ovs after defrag in act_ct - net/sched: fix miss init the mru in qdisc_skb_cb - net/sched: act_ct: fix wild memory access when clearing fragments - Revert "net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow" - net/sched: act_mirred: refactor the handle of xmit - net/sched: The error lable position is corrected in ct_init_module - net/sched: sch_frag: add generic packet fragment support. - ipv6: add ipv6_fragment hook in ipv6_stub * Add the upcoming BlueField-3 device ID (LP: #1941803) - net/mlx5: Update the list of the PCI supported devices * CT state not reset when packet redirected to different port (LP: #1940448) - Revert "UBUNTU: SAUCE: net/sched: act_mirred: Reset ct when reinserting skb back into queue" - net: sched: act_mirred: Reset ct info when mirror/redirect skb * Export xfrm_policy_lookup_bytype function (LP: #1934313) - SAUCE: xfrm: IPsec Export xfrm_policy_lookup_bytype function [ Ubuntu: 5.4.0-85.95 ] * focal/linux: 5.4.0-85.95 -proposed tracker (LP: #1942557) * please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248) - [Config] Disable virtualbox dkms build * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.09.06) * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771) - Disable CONFIG_HISI_DMA - [Config] Record hisi_dma no longer built for arm64 * memory leaking when removing a profile (LP: #1939915) - apparmor: Fix memory leak of profile proxy * CryptoExpress EP11 cards are going offline (LP: #1939618) - s390/zcrypt: Support for CCA protected key block version 2 - s390: Replace zero-length array with flexible-array member - s390/zcrypt: Use scnprintf() for avoiding potential buffer overflow - s390/zcrypt: replace snprintf/sprintf with scnprintf - s390/ap: Remove ap device suspend and resume callbacks - s390/zcrypt: use fallthrough; - s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc - s390/ap: remove power management code from ap bus and drivers - s390/ap: introduce new ap function ap_get_qdev() - s390/zcrypt: use kzalloc - s390/zcrypt: fix smatch warnings - s390/zcrypt: code beautification and struct field renames - s390/zcrypt: split ioctl function into smaller code units - s390/ap: rename and clarify ap state machine related stuff - s390/zcrypt: provide cex4 cca sysfs attributes for cex3 - s390/ap: rework crypto config info and default domain code - s390/zcrypt: simplify cca_findcard2 loop code - s390/zcrypt: remove set_fs() invocation in zcrypt device driver - s390/ap: remove unnecessary spin_lock_init() - s390/zcrypt: Support for CCA APKA master keys - s390/zcrypt: introduce msg tracking in zcrypt functions - s390/ap: split ap queue state machine state from device state - s390/ap: add error response code field for ap queue devices - s390/ap: add card/queue deconfig state - s390/sclp: Add support for SCLP AP adapter config/deconfig - s390/ap: Support AP card SCLP config and deconfig operations - s390/ap/zcrypt: revisit ap and zcrypt error handling - s390/zcrypt: move ap_msg param one level up the call chain - s390/zcrypt: Introduce Failure Injection feature - s390/zcrypt: fix wrong format specifications - s390/ap: fix ap devices reference counting - s390/zcrypt: return EIO when msg retry limit reached - s390/zcrypt: fix zcard and zqueue hot-unplug memleak - s390/ap: Fix hanging ioctl caused by wrong msg counter * memfd from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1926142) - SAUCE: selftests/memfd: fix build when F_SEAL_FUTURE_WRITE is not defined * [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands (LP: #1939855) - ice: Fix bad register reads * ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() (LP: #1941829) - selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test * e1000e blocks the boot process when it tried to write checksum to its NVM (LP: #1936998) - e1000e: Do not take care about recovery NVM checksum * Focal
[Kernel-packages] [Bug 1934401] Re: Control netfilter flow table timeouts via sysctl
This bug was fixed in the package linux-bluefield - 5.4.0-1019.22 --- linux-bluefield (5.4.0-1019.22) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1019.22 -proposed tracker (LP: #1942533) * Focal update: v5.4.134 upstream stable release (LP: #1939440) - [Config] bluefield: CONFIG_BATTERY_RT5033=m * Fix fragmentation support for TC connection tracking (LP: #1940872) - net/sched: act_ct: fix restore the qdisc_skb_cb after defrag - net/sched: act_ct: fix miss set mru for ovs after defrag in act_ct - net/sched: fix miss init the mru in qdisc_skb_cb - net/sched: act_ct: fix wild memory access when clearing fragments - Revert "net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow" - net/sched: act_mirred: refactor the handle of xmit - net/sched: The error lable position is corrected in ct_init_module - net/sched: sch_frag: add generic packet fragment support. - ipv6: add ipv6_fragment hook in ipv6_stub * Add the upcoming BlueField-3 device ID (LP: #1941803) - net/mlx5: Update the list of the PCI supported devices * CT state not reset when packet redirected to different port (LP: #1940448) - Revert "UBUNTU: SAUCE: net/sched: act_mirred: Reset ct when reinserting skb back into queue" - net: sched: act_mirred: Reset ct info when mirror/redirect skb * Export xfrm_policy_lookup_bytype function (LP: #1934313) - SAUCE: xfrm: IPsec Export xfrm_policy_lookup_bytype function [ Ubuntu: 5.4.0-85.95 ] * focal/linux: 5.4.0-85.95 -proposed tracker (LP: #1942557) * please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248) - [Config] Disable virtualbox dkms build * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.09.06) * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771) - Disable CONFIG_HISI_DMA - [Config] Record hisi_dma no longer built for arm64 * memory leaking when removing a profile (LP: #1939915) - apparmor: Fix memory leak of profile proxy * CryptoExpress EP11 cards are going offline (LP: #1939618) - s390/zcrypt: Support for CCA protected key block version 2 - s390: Replace zero-length array with flexible-array member - s390/zcrypt: Use scnprintf() for avoiding potential buffer overflow - s390/zcrypt: replace snprintf/sprintf with scnprintf - s390/ap: Remove ap device suspend and resume callbacks - s390/zcrypt: use fallthrough; - s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc - s390/ap: remove power management code from ap bus and drivers - s390/ap: introduce new ap function ap_get_qdev() - s390/zcrypt: use kzalloc - s390/zcrypt: fix smatch warnings - s390/zcrypt: code beautification and struct field renames - s390/zcrypt: split ioctl function into smaller code units - s390/ap: rename and clarify ap state machine related stuff - s390/zcrypt: provide cex4 cca sysfs attributes for cex3 - s390/ap: rework crypto config info and default domain code - s390/zcrypt: simplify cca_findcard2 loop code - s390/zcrypt: remove set_fs() invocation in zcrypt device driver - s390/ap: remove unnecessary spin_lock_init() - s390/zcrypt: Support for CCA APKA master keys - s390/zcrypt: introduce msg tracking in zcrypt functions - s390/ap: split ap queue state machine state from device state - s390/ap: add error response code field for ap queue devices - s390/ap: add card/queue deconfig state - s390/sclp: Add support for SCLP AP adapter config/deconfig - s390/ap: Support AP card SCLP config and deconfig operations - s390/ap/zcrypt: revisit ap and zcrypt error handling - s390/zcrypt: move ap_msg param one level up the call chain - s390/zcrypt: Introduce Failure Injection feature - s390/zcrypt: fix wrong format specifications - s390/ap: fix ap devices reference counting - s390/zcrypt: return EIO when msg retry limit reached - s390/zcrypt: fix zcard and zqueue hot-unplug memleak - s390/ap: Fix hanging ioctl caused by wrong msg counter * memfd from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1926142) - SAUCE: selftests/memfd: fix build when F_SEAL_FUTURE_WRITE is not defined * [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands (LP: #1939855) - ice: Fix bad register reads * ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() (LP: #1941829) - selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test * e1000e blocks the boot process when it tried to write checksum to its NVM (LP: #1936998) - e1000e: Do not take care about recovery NVM checksum * Focal
[Kernel-packages] [Bug 1934822] Re: Possible memory leak of flow_block_cb
This bug was fixed in the package linux-bluefield - 5.4.0-1019.22 --- linux-bluefield (5.4.0-1019.22) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1019.22 -proposed tracker (LP: #1942533) * Focal update: v5.4.134 upstream stable release (LP: #1939440) - [Config] bluefield: CONFIG_BATTERY_RT5033=m * Fix fragmentation support for TC connection tracking (LP: #1940872) - net/sched: act_ct: fix restore the qdisc_skb_cb after defrag - net/sched: act_ct: fix miss set mru for ovs after defrag in act_ct - net/sched: fix miss init the mru in qdisc_skb_cb - net/sched: act_ct: fix wild memory access when clearing fragments - Revert "net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow" - net/sched: act_mirred: refactor the handle of xmit - net/sched: The error lable position is corrected in ct_init_module - net/sched: sch_frag: add generic packet fragment support. - ipv6: add ipv6_fragment hook in ipv6_stub * Add the upcoming BlueField-3 device ID (LP: #1941803) - net/mlx5: Update the list of the PCI supported devices * CT state not reset when packet redirected to different port (LP: #1940448) - Revert "UBUNTU: SAUCE: net/sched: act_mirred: Reset ct when reinserting skb back into queue" - net: sched: act_mirred: Reset ct info when mirror/redirect skb * Export xfrm_policy_lookup_bytype function (LP: #1934313) - SAUCE: xfrm: IPsec Export xfrm_policy_lookup_bytype function [ Ubuntu: 5.4.0-85.95 ] * focal/linux: 5.4.0-85.95 -proposed tracker (LP: #1942557) * please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248) - [Config] Disable virtualbox dkms build * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.09.06) * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771) - Disable CONFIG_HISI_DMA - [Config] Record hisi_dma no longer built for arm64 * memory leaking when removing a profile (LP: #1939915) - apparmor: Fix memory leak of profile proxy * CryptoExpress EP11 cards are going offline (LP: #1939618) - s390/zcrypt: Support for CCA protected key block version 2 - s390: Replace zero-length array with flexible-array member - s390/zcrypt: Use scnprintf() for avoiding potential buffer overflow - s390/zcrypt: replace snprintf/sprintf with scnprintf - s390/ap: Remove ap device suspend and resume callbacks - s390/zcrypt: use fallthrough; - s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc - s390/ap: remove power management code from ap bus and drivers - s390/ap: introduce new ap function ap_get_qdev() - s390/zcrypt: use kzalloc - s390/zcrypt: fix smatch warnings - s390/zcrypt: code beautification and struct field renames - s390/zcrypt: split ioctl function into smaller code units - s390/ap: rename and clarify ap state machine related stuff - s390/zcrypt: provide cex4 cca sysfs attributes for cex3 - s390/ap: rework crypto config info and default domain code - s390/zcrypt: simplify cca_findcard2 loop code - s390/zcrypt: remove set_fs() invocation in zcrypt device driver - s390/ap: remove unnecessary spin_lock_init() - s390/zcrypt: Support for CCA APKA master keys - s390/zcrypt: introduce msg tracking in zcrypt functions - s390/ap: split ap queue state machine state from device state - s390/ap: add error response code field for ap queue devices - s390/ap: add card/queue deconfig state - s390/sclp: Add support for SCLP AP adapter config/deconfig - s390/ap: Support AP card SCLP config and deconfig operations - s390/ap/zcrypt: revisit ap and zcrypt error handling - s390/zcrypt: move ap_msg param one level up the call chain - s390/zcrypt: Introduce Failure Injection feature - s390/zcrypt: fix wrong format specifications - s390/ap: fix ap devices reference counting - s390/zcrypt: return EIO when msg retry limit reached - s390/zcrypt: fix zcard and zqueue hot-unplug memleak - s390/ap: Fix hanging ioctl caused by wrong msg counter * memfd from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1926142) - SAUCE: selftests/memfd: fix build when F_SEAL_FUTURE_WRITE is not defined * [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands (LP: #1939855) - ice: Fix bad register reads * ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() (LP: #1941829) - selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test * e1000e blocks the boot process when it tried to write checksum to its NVM (LP: #1936998) - e1000e: Do not take care about recovery NVM checksum * Focal
[Kernel-packages] [Bug 1934304] Re: i2c-mlxbf.c: prevent stack overflow in mlxbf_i2c_smbus_start_transaction
This bug was fixed in the package linux-bluefield - 5.4.0-1019.22 --- linux-bluefield (5.4.0-1019.22) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1019.22 -proposed tracker (LP: #1942533) * Focal update: v5.4.134 upstream stable release (LP: #1939440) - [Config] bluefield: CONFIG_BATTERY_RT5033=m * Fix fragmentation support for TC connection tracking (LP: #1940872) - net/sched: act_ct: fix restore the qdisc_skb_cb after defrag - net/sched: act_ct: fix miss set mru for ovs after defrag in act_ct - net/sched: fix miss init the mru in qdisc_skb_cb - net/sched: act_ct: fix wild memory access when clearing fragments - Revert "net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow" - net/sched: act_mirred: refactor the handle of xmit - net/sched: The error lable position is corrected in ct_init_module - net/sched: sch_frag: add generic packet fragment support. - ipv6: add ipv6_fragment hook in ipv6_stub * Add the upcoming BlueField-3 device ID (LP: #1941803) - net/mlx5: Update the list of the PCI supported devices * CT state not reset when packet redirected to different port (LP: #1940448) - Revert "UBUNTU: SAUCE: net/sched: act_mirred: Reset ct when reinserting skb back into queue" - net: sched: act_mirred: Reset ct info when mirror/redirect skb * Export xfrm_policy_lookup_bytype function (LP: #1934313) - SAUCE: xfrm: IPsec Export xfrm_policy_lookup_bytype function [ Ubuntu: 5.4.0-85.95 ] * focal/linux: 5.4.0-85.95 -proposed tracker (LP: #1942557) * please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248) - [Config] Disable virtualbox dkms build * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.09.06) * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771) - Disable CONFIG_HISI_DMA - [Config] Record hisi_dma no longer built for arm64 * memory leaking when removing a profile (LP: #1939915) - apparmor: Fix memory leak of profile proxy * CryptoExpress EP11 cards are going offline (LP: #1939618) - s390/zcrypt: Support for CCA protected key block version 2 - s390: Replace zero-length array with flexible-array member - s390/zcrypt: Use scnprintf() for avoiding potential buffer overflow - s390/zcrypt: replace snprintf/sprintf with scnprintf - s390/ap: Remove ap device suspend and resume callbacks - s390/zcrypt: use fallthrough; - s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc - s390/ap: remove power management code from ap bus and drivers - s390/ap: introduce new ap function ap_get_qdev() - s390/zcrypt: use kzalloc - s390/zcrypt: fix smatch warnings - s390/zcrypt: code beautification and struct field renames - s390/zcrypt: split ioctl function into smaller code units - s390/ap: rename and clarify ap state machine related stuff - s390/zcrypt: provide cex4 cca sysfs attributes for cex3 - s390/ap: rework crypto config info and default domain code - s390/zcrypt: simplify cca_findcard2 loop code - s390/zcrypt: remove set_fs() invocation in zcrypt device driver - s390/ap: remove unnecessary spin_lock_init() - s390/zcrypt: Support for CCA APKA master keys - s390/zcrypt: introduce msg tracking in zcrypt functions - s390/ap: split ap queue state machine state from device state - s390/ap: add error response code field for ap queue devices - s390/ap: add card/queue deconfig state - s390/sclp: Add support for SCLP AP adapter config/deconfig - s390/ap: Support AP card SCLP config and deconfig operations - s390/ap/zcrypt: revisit ap and zcrypt error handling - s390/zcrypt: move ap_msg param one level up the call chain - s390/zcrypt: Introduce Failure Injection feature - s390/zcrypt: fix wrong format specifications - s390/ap: fix ap devices reference counting - s390/zcrypt: return EIO when msg retry limit reached - s390/zcrypt: fix zcard and zqueue hot-unplug memleak - s390/ap: Fix hanging ioctl caused by wrong msg counter * memfd from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1926142) - SAUCE: selftests/memfd: fix build when F_SEAL_FUTURE_WRITE is not defined * [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands (LP: #1939855) - ice: Fix bad register reads * ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() (LP: #1941829) - selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test * e1000e blocks the boot process when it tried to write checksum to its NVM (LP: #1936998) - e1000e: Do not take care about recovery NVM checksum * Focal
[Kernel-packages] [Bug 1934313] Re: Export xfrm_policy_lookup_bytype function
This bug was fixed in the package linux-bluefield - 5.4.0-1019.22 --- linux-bluefield (5.4.0-1019.22) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1019.22 -proposed tracker (LP: #1942533) * Focal update: v5.4.134 upstream stable release (LP: #1939440) - [Config] bluefield: CONFIG_BATTERY_RT5033=m * Fix fragmentation support for TC connection tracking (LP: #1940872) - net/sched: act_ct: fix restore the qdisc_skb_cb after defrag - net/sched: act_ct: fix miss set mru for ovs after defrag in act_ct - net/sched: fix miss init the mru in qdisc_skb_cb - net/sched: act_ct: fix wild memory access when clearing fragments - Revert "net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow" - net/sched: act_mirred: refactor the handle of xmit - net/sched: The error lable position is corrected in ct_init_module - net/sched: sch_frag: add generic packet fragment support. - ipv6: add ipv6_fragment hook in ipv6_stub * Add the upcoming BlueField-3 device ID (LP: #1941803) - net/mlx5: Update the list of the PCI supported devices * CT state not reset when packet redirected to different port (LP: #1940448) - Revert "UBUNTU: SAUCE: net/sched: act_mirred: Reset ct when reinserting skb back into queue" - net: sched: act_mirred: Reset ct info when mirror/redirect skb * Export xfrm_policy_lookup_bytype function (LP: #1934313) - SAUCE: xfrm: IPsec Export xfrm_policy_lookup_bytype function [ Ubuntu: 5.4.0-85.95 ] * focal/linux: 5.4.0-85.95 -proposed tracker (LP: #1942557) * please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248) - [Config] Disable virtualbox dkms build * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.09.06) * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771) - Disable CONFIG_HISI_DMA - [Config] Record hisi_dma no longer built for arm64 * memory leaking when removing a profile (LP: #1939915) - apparmor: Fix memory leak of profile proxy * CryptoExpress EP11 cards are going offline (LP: #1939618) - s390/zcrypt: Support for CCA protected key block version 2 - s390: Replace zero-length array with flexible-array member - s390/zcrypt: Use scnprintf() for avoiding potential buffer overflow - s390/zcrypt: replace snprintf/sprintf with scnprintf - s390/ap: Remove ap device suspend and resume callbacks - s390/zcrypt: use fallthrough; - s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc - s390/ap: remove power management code from ap bus and drivers - s390/ap: introduce new ap function ap_get_qdev() - s390/zcrypt: use kzalloc - s390/zcrypt: fix smatch warnings - s390/zcrypt: code beautification and struct field renames - s390/zcrypt: split ioctl function into smaller code units - s390/ap: rename and clarify ap state machine related stuff - s390/zcrypt: provide cex4 cca sysfs attributes for cex3 - s390/ap: rework crypto config info and default domain code - s390/zcrypt: simplify cca_findcard2 loop code - s390/zcrypt: remove set_fs() invocation in zcrypt device driver - s390/ap: remove unnecessary spin_lock_init() - s390/zcrypt: Support for CCA APKA master keys - s390/zcrypt: introduce msg tracking in zcrypt functions - s390/ap: split ap queue state machine state from device state - s390/ap: add error response code field for ap queue devices - s390/ap: add card/queue deconfig state - s390/sclp: Add support for SCLP AP adapter config/deconfig - s390/ap: Support AP card SCLP config and deconfig operations - s390/ap/zcrypt: revisit ap and zcrypt error handling - s390/zcrypt: move ap_msg param one level up the call chain - s390/zcrypt: Introduce Failure Injection feature - s390/zcrypt: fix wrong format specifications - s390/ap: fix ap devices reference counting - s390/zcrypt: return EIO when msg retry limit reached - s390/zcrypt: fix zcard and zqueue hot-unplug memleak - s390/ap: Fix hanging ioctl caused by wrong msg counter * memfd from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1926142) - SAUCE: selftests/memfd: fix build when F_SEAL_FUTURE_WRITE is not defined * [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands (LP: #1939855) - ice: Fix bad register reads * ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() (LP: #1941829) - selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test * e1000e blocks the boot process when it tried to write checksum to its NVM (LP: #1936998) - e1000e: Do not take care about recovery NVM checksum * Focal
[Kernel-packages] [Bug 1934923] Re: Sync up mlxbf-gige driver with upstreamed version
This bug was fixed in the package linux-bluefield - 5.4.0-1019.22 --- linux-bluefield (5.4.0-1019.22) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1019.22 -proposed tracker (LP: #1942533) * Focal update: v5.4.134 upstream stable release (LP: #1939440) - [Config] bluefield: CONFIG_BATTERY_RT5033=m * Fix fragmentation support for TC connection tracking (LP: #1940872) - net/sched: act_ct: fix restore the qdisc_skb_cb after defrag - net/sched: act_ct: fix miss set mru for ovs after defrag in act_ct - net/sched: fix miss init the mru in qdisc_skb_cb - net/sched: act_ct: fix wild memory access when clearing fragments - Revert "net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow" - net/sched: act_mirred: refactor the handle of xmit - net/sched: The error lable position is corrected in ct_init_module - net/sched: sch_frag: add generic packet fragment support. - ipv6: add ipv6_fragment hook in ipv6_stub * Add the upcoming BlueField-3 device ID (LP: #1941803) - net/mlx5: Update the list of the PCI supported devices * CT state not reset when packet redirected to different port (LP: #1940448) - Revert "UBUNTU: SAUCE: net/sched: act_mirred: Reset ct when reinserting skb back into queue" - net: sched: act_mirred: Reset ct info when mirror/redirect skb * Export xfrm_policy_lookup_bytype function (LP: #1934313) - SAUCE: xfrm: IPsec Export xfrm_policy_lookup_bytype function [ Ubuntu: 5.4.0-85.95 ] * focal/linux: 5.4.0-85.95 -proposed tracker (LP: #1942557) * please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248) - [Config] Disable virtualbox dkms build * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.09.06) * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771) - Disable CONFIG_HISI_DMA - [Config] Record hisi_dma no longer built for arm64 * memory leaking when removing a profile (LP: #1939915) - apparmor: Fix memory leak of profile proxy * CryptoExpress EP11 cards are going offline (LP: #1939618) - s390/zcrypt: Support for CCA protected key block version 2 - s390: Replace zero-length array with flexible-array member - s390/zcrypt: Use scnprintf() for avoiding potential buffer overflow - s390/zcrypt: replace snprintf/sprintf with scnprintf - s390/ap: Remove ap device suspend and resume callbacks - s390/zcrypt: use fallthrough; - s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc - s390/ap: remove power management code from ap bus and drivers - s390/ap: introduce new ap function ap_get_qdev() - s390/zcrypt: use kzalloc - s390/zcrypt: fix smatch warnings - s390/zcrypt: code beautification and struct field renames - s390/zcrypt: split ioctl function into smaller code units - s390/ap: rename and clarify ap state machine related stuff - s390/zcrypt: provide cex4 cca sysfs attributes for cex3 - s390/ap: rework crypto config info and default domain code - s390/zcrypt: simplify cca_findcard2 loop code - s390/zcrypt: remove set_fs() invocation in zcrypt device driver - s390/ap: remove unnecessary spin_lock_init() - s390/zcrypt: Support for CCA APKA master keys - s390/zcrypt: introduce msg tracking in zcrypt functions - s390/ap: split ap queue state machine state from device state - s390/ap: add error response code field for ap queue devices - s390/ap: add card/queue deconfig state - s390/sclp: Add support for SCLP AP adapter config/deconfig - s390/ap: Support AP card SCLP config and deconfig operations - s390/ap/zcrypt: revisit ap and zcrypt error handling - s390/zcrypt: move ap_msg param one level up the call chain - s390/zcrypt: Introduce Failure Injection feature - s390/zcrypt: fix wrong format specifications - s390/ap: fix ap devices reference counting - s390/zcrypt: return EIO when msg retry limit reached - s390/zcrypt: fix zcard and zqueue hot-unplug memleak - s390/ap: Fix hanging ioctl caused by wrong msg counter * memfd from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1926142) - SAUCE: selftests/memfd: fix build when F_SEAL_FUTURE_WRITE is not defined * [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands (LP: #1939855) - ice: Fix bad register reads * ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() (LP: #1941829) - selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test * e1000e blocks the boot process when it tried to write checksum to its NVM (LP: #1936998) - e1000e: Do not take care about recovery NVM checksum * Focal
[Kernel-packages] [Bug 1935584] Re: Fix host to pod traffic with ovn cluster using ovs internal port and tc offload
This bug was fixed in the package linux-bluefield - 5.4.0-1019.22 --- linux-bluefield (5.4.0-1019.22) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1019.22 -proposed tracker (LP: #1942533) * Focal update: v5.4.134 upstream stable release (LP: #1939440) - [Config] bluefield: CONFIG_BATTERY_RT5033=m * Fix fragmentation support for TC connection tracking (LP: #1940872) - net/sched: act_ct: fix restore the qdisc_skb_cb after defrag - net/sched: act_ct: fix miss set mru for ovs after defrag in act_ct - net/sched: fix miss init the mru in qdisc_skb_cb - net/sched: act_ct: fix wild memory access when clearing fragments - Revert "net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow" - net/sched: act_mirred: refactor the handle of xmit - net/sched: The error lable position is corrected in ct_init_module - net/sched: sch_frag: add generic packet fragment support. - ipv6: add ipv6_fragment hook in ipv6_stub * Add the upcoming BlueField-3 device ID (LP: #1941803) - net/mlx5: Update the list of the PCI supported devices * CT state not reset when packet redirected to different port (LP: #1940448) - Revert "UBUNTU: SAUCE: net/sched: act_mirred: Reset ct when reinserting skb back into queue" - net: sched: act_mirred: Reset ct info when mirror/redirect skb * Export xfrm_policy_lookup_bytype function (LP: #1934313) - SAUCE: xfrm: IPsec Export xfrm_policy_lookup_bytype function [ Ubuntu: 5.4.0-85.95 ] * focal/linux: 5.4.0-85.95 -proposed tracker (LP: #1942557) * please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248) - [Config] Disable virtualbox dkms build * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.09.06) * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771) - Disable CONFIG_HISI_DMA - [Config] Record hisi_dma no longer built for arm64 * memory leaking when removing a profile (LP: #1939915) - apparmor: Fix memory leak of profile proxy * CryptoExpress EP11 cards are going offline (LP: #1939618) - s390/zcrypt: Support for CCA protected key block version 2 - s390: Replace zero-length array with flexible-array member - s390/zcrypt: Use scnprintf() for avoiding potential buffer overflow - s390/zcrypt: replace snprintf/sprintf with scnprintf - s390/ap: Remove ap device suspend and resume callbacks - s390/zcrypt: use fallthrough; - s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc - s390/ap: remove power management code from ap bus and drivers - s390/ap: introduce new ap function ap_get_qdev() - s390/zcrypt: use kzalloc - s390/zcrypt: fix smatch warnings - s390/zcrypt: code beautification and struct field renames - s390/zcrypt: split ioctl function into smaller code units - s390/ap: rename and clarify ap state machine related stuff - s390/zcrypt: provide cex4 cca sysfs attributes for cex3 - s390/ap: rework crypto config info and default domain code - s390/zcrypt: simplify cca_findcard2 loop code - s390/zcrypt: remove set_fs() invocation in zcrypt device driver - s390/ap: remove unnecessary spin_lock_init() - s390/zcrypt: Support for CCA APKA master keys - s390/zcrypt: introduce msg tracking in zcrypt functions - s390/ap: split ap queue state machine state from device state - s390/ap: add error response code field for ap queue devices - s390/ap: add card/queue deconfig state - s390/sclp: Add support for SCLP AP adapter config/deconfig - s390/ap: Support AP card SCLP config and deconfig operations - s390/ap/zcrypt: revisit ap and zcrypt error handling - s390/zcrypt: move ap_msg param one level up the call chain - s390/zcrypt: Introduce Failure Injection feature - s390/zcrypt: fix wrong format specifications - s390/ap: fix ap devices reference counting - s390/zcrypt: return EIO when msg retry limit reached - s390/zcrypt: fix zcard and zqueue hot-unplug memleak - s390/ap: Fix hanging ioctl caused by wrong msg counter * memfd from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1926142) - SAUCE: selftests/memfd: fix build when F_SEAL_FUTURE_WRITE is not defined * [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands (LP: #1939855) - ice: Fix bad register reads * ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() (LP: #1941829) - selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test * e1000e blocks the boot process when it tried to write checksum to its NVM (LP: #1936998) - e1000e: Do not take care about recovery NVM checksum * Focal
[Kernel-packages] [Bug 1938818] Re: Add support for packet-per-second policing
This bug was fixed in the package linux-bluefield - 5.4.0-1019.22 --- linux-bluefield (5.4.0-1019.22) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1019.22 -proposed tracker (LP: #1942533) * Focal update: v5.4.134 upstream stable release (LP: #1939440) - [Config] bluefield: CONFIG_BATTERY_RT5033=m * Fix fragmentation support for TC connection tracking (LP: #1940872) - net/sched: act_ct: fix restore the qdisc_skb_cb after defrag - net/sched: act_ct: fix miss set mru for ovs after defrag in act_ct - net/sched: fix miss init the mru in qdisc_skb_cb - net/sched: act_ct: fix wild memory access when clearing fragments - Revert "net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow" - net/sched: act_mirred: refactor the handle of xmit - net/sched: The error lable position is corrected in ct_init_module - net/sched: sch_frag: add generic packet fragment support. - ipv6: add ipv6_fragment hook in ipv6_stub * Add the upcoming BlueField-3 device ID (LP: #1941803) - net/mlx5: Update the list of the PCI supported devices * CT state not reset when packet redirected to different port (LP: #1940448) - Revert "UBUNTU: SAUCE: net/sched: act_mirred: Reset ct when reinserting skb back into queue" - net: sched: act_mirred: Reset ct info when mirror/redirect skb * Export xfrm_policy_lookup_bytype function (LP: #1934313) - SAUCE: xfrm: IPsec Export xfrm_policy_lookup_bytype function [ Ubuntu: 5.4.0-85.95 ] * focal/linux: 5.4.0-85.95 -proposed tracker (LP: #1942557) * please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248) - [Config] Disable virtualbox dkms build * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.09.06) * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771) - Disable CONFIG_HISI_DMA - [Config] Record hisi_dma no longer built for arm64 * memory leaking when removing a profile (LP: #1939915) - apparmor: Fix memory leak of profile proxy * CryptoExpress EP11 cards are going offline (LP: #1939618) - s390/zcrypt: Support for CCA protected key block version 2 - s390: Replace zero-length array with flexible-array member - s390/zcrypt: Use scnprintf() for avoiding potential buffer overflow - s390/zcrypt: replace snprintf/sprintf with scnprintf - s390/ap: Remove ap device suspend and resume callbacks - s390/zcrypt: use fallthrough; - s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc - s390/ap: remove power management code from ap bus and drivers - s390/ap: introduce new ap function ap_get_qdev() - s390/zcrypt: use kzalloc - s390/zcrypt: fix smatch warnings - s390/zcrypt: code beautification and struct field renames - s390/zcrypt: split ioctl function into smaller code units - s390/ap: rename and clarify ap state machine related stuff - s390/zcrypt: provide cex4 cca sysfs attributes for cex3 - s390/ap: rework crypto config info and default domain code - s390/zcrypt: simplify cca_findcard2 loop code - s390/zcrypt: remove set_fs() invocation in zcrypt device driver - s390/ap: remove unnecessary spin_lock_init() - s390/zcrypt: Support for CCA APKA master keys - s390/zcrypt: introduce msg tracking in zcrypt functions - s390/ap: split ap queue state machine state from device state - s390/ap: add error response code field for ap queue devices - s390/ap: add card/queue deconfig state - s390/sclp: Add support for SCLP AP adapter config/deconfig - s390/ap: Support AP card SCLP config and deconfig operations - s390/ap/zcrypt: revisit ap and zcrypt error handling - s390/zcrypt: move ap_msg param one level up the call chain - s390/zcrypt: Introduce Failure Injection feature - s390/zcrypt: fix wrong format specifications - s390/ap: fix ap devices reference counting - s390/zcrypt: return EIO when msg retry limit reached - s390/zcrypt: fix zcard and zqueue hot-unplug memleak - s390/ap: Fix hanging ioctl caused by wrong msg counter * memfd from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1926142) - SAUCE: selftests/memfd: fix build when F_SEAL_FUTURE_WRITE is not defined * [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands (LP: #1939855) - ice: Fix bad register reads * ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() (LP: #1941829) - selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test * e1000e blocks the boot process when it tried to write checksum to its NVM (LP: #1936998) - e1000e: Do not take care about recovery NVM checksum * Focal
[Kernel-packages] [Bug 1940872] Re: Fix fragmentation support for TC connection tracking
This bug was fixed in the package linux-bluefield - 5.4.0-1019.22 --- linux-bluefield (5.4.0-1019.22) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1019.22 -proposed tracker (LP: #1942533) * Focal update: v5.4.134 upstream stable release (LP: #1939440) - [Config] bluefield: CONFIG_BATTERY_RT5033=m * Fix fragmentation support for TC connection tracking (LP: #1940872) - net/sched: act_ct: fix restore the qdisc_skb_cb after defrag - net/sched: act_ct: fix miss set mru for ovs after defrag in act_ct - net/sched: fix miss init the mru in qdisc_skb_cb - net/sched: act_ct: fix wild memory access when clearing fragments - Revert "net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow" - net/sched: act_mirred: refactor the handle of xmit - net/sched: The error lable position is corrected in ct_init_module - net/sched: sch_frag: add generic packet fragment support. - ipv6: add ipv6_fragment hook in ipv6_stub * Add the upcoming BlueField-3 device ID (LP: #1941803) - net/mlx5: Update the list of the PCI supported devices * CT state not reset when packet redirected to different port (LP: #1940448) - Revert "UBUNTU: SAUCE: net/sched: act_mirred: Reset ct when reinserting skb back into queue" - net: sched: act_mirred: Reset ct info when mirror/redirect skb * Export xfrm_policy_lookup_bytype function (LP: #1934313) - SAUCE: xfrm: IPsec Export xfrm_policy_lookup_bytype function [ Ubuntu: 5.4.0-85.95 ] * focal/linux: 5.4.0-85.95 -proposed tracker (LP: #1942557) * please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248) - [Config] Disable virtualbox dkms build * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.09.06) * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771) - Disable CONFIG_HISI_DMA - [Config] Record hisi_dma no longer built for arm64 * memory leaking when removing a profile (LP: #1939915) - apparmor: Fix memory leak of profile proxy * CryptoExpress EP11 cards are going offline (LP: #1939618) - s390/zcrypt: Support for CCA protected key block version 2 - s390: Replace zero-length array with flexible-array member - s390/zcrypt: Use scnprintf() for avoiding potential buffer overflow - s390/zcrypt: replace snprintf/sprintf with scnprintf - s390/ap: Remove ap device suspend and resume callbacks - s390/zcrypt: use fallthrough; - s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc - s390/ap: remove power management code from ap bus and drivers - s390/ap: introduce new ap function ap_get_qdev() - s390/zcrypt: use kzalloc - s390/zcrypt: fix smatch warnings - s390/zcrypt: code beautification and struct field renames - s390/zcrypt: split ioctl function into smaller code units - s390/ap: rename and clarify ap state machine related stuff - s390/zcrypt: provide cex4 cca sysfs attributes for cex3 - s390/ap: rework crypto config info and default domain code - s390/zcrypt: simplify cca_findcard2 loop code - s390/zcrypt: remove set_fs() invocation in zcrypt device driver - s390/ap: remove unnecessary spin_lock_init() - s390/zcrypt: Support for CCA APKA master keys - s390/zcrypt: introduce msg tracking in zcrypt functions - s390/ap: split ap queue state machine state from device state - s390/ap: add error response code field for ap queue devices - s390/ap: add card/queue deconfig state - s390/sclp: Add support for SCLP AP adapter config/deconfig - s390/ap: Support AP card SCLP config and deconfig operations - s390/ap/zcrypt: revisit ap and zcrypt error handling - s390/zcrypt: move ap_msg param one level up the call chain - s390/zcrypt: Introduce Failure Injection feature - s390/zcrypt: fix wrong format specifications - s390/ap: fix ap devices reference counting - s390/zcrypt: return EIO when msg retry limit reached - s390/zcrypt: fix zcard and zqueue hot-unplug memleak - s390/ap: Fix hanging ioctl caused by wrong msg counter * memfd from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1926142) - SAUCE: selftests/memfd: fix build when F_SEAL_FUTURE_WRITE is not defined * [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands (LP: #1939855) - ice: Fix bad register reads * ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() (LP: #1941829) - selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test * e1000e blocks the boot process when it tried to write checksum to its NVM (LP: #1936998) - e1000e: Do not take care about recovery NVM checksum * Focal
[Kernel-packages] [Bug 1941803] Re: Add the upcoming BlueField-3 device ID
This bug was fixed in the package linux-bluefield - 5.4.0-1019.22 --- linux-bluefield (5.4.0-1019.22) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1019.22 -proposed tracker (LP: #1942533) * Focal update: v5.4.134 upstream stable release (LP: #1939440) - [Config] bluefield: CONFIG_BATTERY_RT5033=m * Fix fragmentation support for TC connection tracking (LP: #1940872) - net/sched: act_ct: fix restore the qdisc_skb_cb after defrag - net/sched: act_ct: fix miss set mru for ovs after defrag in act_ct - net/sched: fix miss init the mru in qdisc_skb_cb - net/sched: act_ct: fix wild memory access when clearing fragments - Revert "net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow" - net/sched: act_mirred: refactor the handle of xmit - net/sched: The error lable position is corrected in ct_init_module - net/sched: sch_frag: add generic packet fragment support. - ipv6: add ipv6_fragment hook in ipv6_stub * Add the upcoming BlueField-3 device ID (LP: #1941803) - net/mlx5: Update the list of the PCI supported devices * CT state not reset when packet redirected to different port (LP: #1940448) - Revert "UBUNTU: SAUCE: net/sched: act_mirred: Reset ct when reinserting skb back into queue" - net: sched: act_mirred: Reset ct info when mirror/redirect skb * Export xfrm_policy_lookup_bytype function (LP: #1934313) - SAUCE: xfrm: IPsec Export xfrm_policy_lookup_bytype function [ Ubuntu: 5.4.0-85.95 ] * focal/linux: 5.4.0-85.95 -proposed tracker (LP: #1942557) * please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248) - [Config] Disable virtualbox dkms build * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.09.06) * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771) - Disable CONFIG_HISI_DMA - [Config] Record hisi_dma no longer built for arm64 * memory leaking when removing a profile (LP: #1939915) - apparmor: Fix memory leak of profile proxy * CryptoExpress EP11 cards are going offline (LP: #1939618) - s390/zcrypt: Support for CCA protected key block version 2 - s390: Replace zero-length array with flexible-array member - s390/zcrypt: Use scnprintf() for avoiding potential buffer overflow - s390/zcrypt: replace snprintf/sprintf with scnprintf - s390/ap: Remove ap device suspend and resume callbacks - s390/zcrypt: use fallthrough; - s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc - s390/ap: remove power management code from ap bus and drivers - s390/ap: introduce new ap function ap_get_qdev() - s390/zcrypt: use kzalloc - s390/zcrypt: fix smatch warnings - s390/zcrypt: code beautification and struct field renames - s390/zcrypt: split ioctl function into smaller code units - s390/ap: rename and clarify ap state machine related stuff - s390/zcrypt: provide cex4 cca sysfs attributes for cex3 - s390/ap: rework crypto config info and default domain code - s390/zcrypt: simplify cca_findcard2 loop code - s390/zcrypt: remove set_fs() invocation in zcrypt device driver - s390/ap: remove unnecessary spin_lock_init() - s390/zcrypt: Support for CCA APKA master keys - s390/zcrypt: introduce msg tracking in zcrypt functions - s390/ap: split ap queue state machine state from device state - s390/ap: add error response code field for ap queue devices - s390/ap: add card/queue deconfig state - s390/sclp: Add support for SCLP AP adapter config/deconfig - s390/ap: Support AP card SCLP config and deconfig operations - s390/ap/zcrypt: revisit ap and zcrypt error handling - s390/zcrypt: move ap_msg param one level up the call chain - s390/zcrypt: Introduce Failure Injection feature - s390/zcrypt: fix wrong format specifications - s390/ap: fix ap devices reference counting - s390/zcrypt: return EIO when msg retry limit reached - s390/zcrypt: fix zcard and zqueue hot-unplug memleak - s390/ap: Fix hanging ioctl caused by wrong msg counter * memfd from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1926142) - SAUCE: selftests/memfd: fix build when F_SEAL_FUTURE_WRITE is not defined * [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands (LP: #1939855) - ice: Fix bad register reads * ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() (LP: #1941829) - selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test * e1000e blocks the boot process when it tried to write checksum to its NVM (LP: #1936998) - e1000e: Do not take care about recovery NVM checksum * Focal
[Kernel-packages] [Bug 1946149] [NEW] Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
You have been subscribed to a public bug: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel. ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal https://bugs.launchpad.net/bugs/1946149 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws 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 1942633] Re: Can not boot impish in Cavium ThunderX
Verified: ubuntu@doerfel:~$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.13.0-18-generic root=UUID=36113164-ebf4-4fed-9d98-4b0b859bf98e ro acpi=force ubuntu@doerfel:~$ cat /proc/version Linux version 5.13.0-18-generic (buildd@bos02-arm64-027) (gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #18-Ubuntu SMP Mon Oct 4 14:52:32 UTC 2021 ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1942633 Title: Can not boot impish in Cavium ThunderX Status in linux package in Ubuntu: Fix Committed Bug description: Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits I tried 2 releases: - 20210817 ( https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ ) - 20210830 ( https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ ) 20210817: Ends the deploy successfully but fails to boot from disk: ``` [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11] [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc (Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1) [0.00] Machine model: Cavium ThunderX CN88XX board [ 139.896752] raid6: xor() 1224 MB/s, rmw enabled [ 139.957046] raid6: using neon recovery algorithm [ 140.020937] xor: measuring software checksum speed [ 140.085571]8regs : 2432 MB/sec [ 140.149834]32regs : 2687 MB/sec [ 140.212202]arm64_neon : 4390 MB/sec [ 140.271985] xor: using function: arm64_neon (4390 MB/sec) [ 140.335013] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 140.569847] Btrfs loaded, crc32c=crc32c-generic, zoned=yes Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. ``` 20210830 Fails the network boot: ``` [ 140.351066] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no find a nic with 1c:1b:0d:0d:52:7c done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: Interface BOOTIF did not appear in time done. ipconfig: BOOTIF: SIOCGIFINDEX: No such device ipconfig: no devices to configure ``` I will attach full logs of each try. JFYI, this is the same machine as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+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 1929889] Re: [TGL][ADL] Enable CET(Control-flow Enforcement Technology)
** 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-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929889 Title: [TGL][ADL] Enable CET(Control-flow Enforcement Technology) Status in intel: New Status in linux-intel package in Ubuntu: Triaged Status in linux-intel source package in Focal: New Bug description: Description Enable Tiger Lake ROP CET(Control-flow Enforcement Technology) An upcoming Intel® processor family feature that counters return/jump-oriented programming (ROP) attacks Hardware: Tiger Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929889/+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 1945462] Re: EHL graphics support for sprint 2
** 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-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945462 Title: EHL graphics support for sprint 2 Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Tracking bug, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945462/+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 1942633] Re: Can not boot impish in Cavium ThunderX
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- 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/1942633 Title: Can not boot impish in Cavium ThunderX Status in linux package in Ubuntu: Fix Committed Bug description: Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits I tried 2 releases: - 20210817 ( https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ ) - 20210830 ( https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ ) 20210817: Ends the deploy successfully but fails to boot from disk: ``` [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11] [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc (Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1) [0.00] Machine model: Cavium ThunderX CN88XX board [ 139.896752] raid6: xor() 1224 MB/s, rmw enabled [ 139.957046] raid6: using neon recovery algorithm [ 140.020937] xor: measuring software checksum speed [ 140.085571]8regs : 2432 MB/sec [ 140.149834]32regs : 2687 MB/sec [ 140.212202]arm64_neon : 4390 MB/sec [ 140.271985] xor: using function: arm64_neon (4390 MB/sec) [ 140.335013] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 140.569847] Btrfs loaded, crc32c=crc32c-generic, zoned=yes Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. ``` 20210830 Fails the network boot: ``` [ 140.351066] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no find a nic with 1c:1b:0d:0d:52:7c done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: Interface BOOTIF did not appear in time done. ipconfig: BOOTIF: SIOCGIFINDEX: No such device ipconfig: no devices to configure ``` I will attach full logs of each try. JFYI, this is the same machine as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+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 1943065] Re: mlxbf_gige: update driver version to 1.25
Hello Luke, Do you know when this Issue will be merged? Thank you, Meriton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1943065 Title: mlxbf_gige: update driver version to 1.25 Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] * The mlxbf_gige driver needs a version increase to identify a driver containing recent important bug fixes. [Fix] * The driver version implemented by the DRV_VERSION define and MODULE_VERSION macro will be incremented from 1.24 to 1.25 [Test Case] * To test this fix, need to check the driver version shown in the output of "modinfo mlxbf_gige" command. [Regression Potential] * There is low risk of this fix causing any problems. [Other] * The mlxbf_gige driver will display v1.25 in modinfo after these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1943065/+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 1934923] Re: Sync up mlxbf-gige driver with upstreamed version
Using Kernel 5.4.0-1019-bluefield, BlueField ATF version: v2.2(release):3.7.1-5-gac4b614, and BlueField UEFI version: 3.7.1-13-g743f036 this Issue has been fixed! ** 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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934923 Title: Sync up mlxbf-gige driver with upstreamed version Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] The mlxbf-gige driver has just been upstreamed so linux-bluefield needs to be synced up with what we have upstreamed. IMPORTANT: during testing, make sure the latest UEFI (bootloader) is loaded on top of these changes, otherwise both the gpio driver and mlxbf-gige driver will fail to load. [Fix] * reverted 20 commits related to the mlxbf-gige driver and 1 commit related to gpio-mlxbf2 driver since there are dependencies between them. * Cherry-picked f92e1869d74e1acc6551256eb084a1c14a054e19 from net-next branch. The upstreamed version of the GPIO driver removed the dependency between the mlxbf-gige driver and gpio-mlxbf2 driver. * added code that was left out of the upstreamed version. and added code that got reverted in gpio-mlxbf2.c * updated the UEFI ACPI table to reflect the above changes (so the bootloader and the linux drivers need to be in sync) [Test Case] * oob_net0 coming up after several SW_RESET or reboot * oob_net0 coming up after several powercycles * oob_net0 coming up after pushing a new Ubuntu/CentOS/Yocto * rmmod/modprove mlxbf_gige several times * OOB PXE boot multiple times from UEFI menu * automate OOB PXE boot and do reboot * automate OOB PXE boot and do powercycle * Test that GPIO7 reset still works on BlueSphere like boards [Regression Potential] Any of the test cases above could be impacted due to these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934923/+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 1945494] Re: [EHL] Quadrature Encoder Peripheral support for sprint 2
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945494 Title: [EHL] Quadrature Encoder Peripheral support for sprint 2 Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Tracking bug, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945494/+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 1945462] Re: EHL graphics support for sprint 2
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945462 Title: EHL graphics support for sprint 2 Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Tracking bug, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945462/+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 1929889] Re: [TGL][ADL] Enable CET(Control-flow Enforcement Technology)
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929889 Title: [TGL][ADL] Enable CET(Control-flow Enforcement Technology) Status in intel: New Status in linux-intel package in Ubuntu: Triaged Status in linux-intel source package in Focal: New Bug description: Description Enable Tiger Lake ROP CET(Control-flow Enforcement Technology) An upcoming Intel® processor family feature that counters return/jump-oriented programming (ROP) attacks Hardware: Tiger Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929889/+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 1929903] Re: [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929903 Title: [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver Status in intel: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description Time Coordinated Compute (TCC) Pseudo SRAM interface support on top of Cache Allocation Technology Hardware: Tiger Lake & Elkhart Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z --- [Update, 2021-08-26] Please find the Getting Started Guide for Intel TCC Tools here, has steps to download, install and verify: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top.html You can find the BIOS settings to enable TCC here: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top/step-6-configure- intel-tcc-tools-in-bios.html To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929903/+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 1943524] Re: [EHL] Intel ishtp VNIC driver
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1943524 Title: [EHL] Intel ishtp VNIC driver Status in intel: New Status in linux-intel-5.13 package in Ubuntu: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description The driver enables a virtual network interface for communicating with a dedicated low power chip over ISHTP Hardware: ElkhartLake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.13-yocto-210727T062416Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1943524/+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 1945461] Re: Integrated TSN controller for sprint 2
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945461 Title: Integrated TSN controller for sprint 2 Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Tracking bug, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945461/+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 1945464] Re: MEI (Intel Management Engine Interface) for sprint 2
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945464 Title: MEI (Intel Management Engine Interface) for sprint 2 Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Tracking bug, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945464/+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 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945548 Title: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board Status in intel: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: [Summary] I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board [Steps to reproduce] 1. Install https://cdimage.ubuntu.com/focal/daily-preinstalled/20210929/ to the system 2. Boot to desktop 3. Check if all Ethernet get IP address [Expected result] All Ethernet Port should up and runing and get the IP address. [Actual result] I225-IT Ethernet (8086:0d9f) does not work and did not get IP address [Failure rate] 100% [Additional information] CID: 202109-29492 SKU: N/A system-manufacturer: AAEON system-product-name: UPN-EHL01 bios-version: UNEHAM0D CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] (rev 01) kernel-version: 5.13.0-1004-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1945548/+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 1944417] Re: Add support for 5.14
Hello Timo, or anyone else affected, Accepted zfs-linux into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/2.0.2-1ubuntu5.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: zfs-linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944417 Title: Add support for 5.14 Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Focal: Invalid Status in zfs-linux source package in Hirsute: Fix Committed Bug description: == SRU Hirsute == [Impact] Add support for 5.14 kernels in Hirsute for zfs-linux dkms module. zfs-linux needs compat changes in order to build against 5.14 kernel like oem-5.14 in focal: - Linux-5.12-compat-bio-bi_disk-member-moved.patch - Linux-5.12-compat-replace-bio_-_io_acct-with-disk_-_.patch - Linux-5.12-compat-idmapped-mounts.patch - Linux-5.12-update-bio_max_segs-replaces-BIO_MAX_PAGE.patch - Remove-iov_iter_advance-for-iter_write.patch - linux-5.13-compat-bdevops-revalidate_disk-removed.patch - Linux-5.14-compat-blk_alloc_disk.patch - Linux-5.14-compat-explicity-assign-set_page_dirty.patch - Linux-5.14-compat-META.patch [Test Plan] Run the ubuntu ZFS regressions tests, these cover smoke testing core functionality, POSIX fs semantics, subset of xfs tests and all mount options with file system stress-ng stress tests. see git://kernel.ubuntu.com/ubuntu/autotest-client/tests/ubuntu_zfs* tests [Where problems could occur] in BIO and block allocation layers in ZFS. These are exercised extensively by the ZFS regression tests. The 5.12..5.14 compat options are dkms build time config checks, so build testing the zfs-dkms package with 5.11 and 5.14 kernels will ensure these dkms build-time options are exercised. [Other Info] These Linux 5.12..5.14 compat patches are in Ubuntu impish and have had some testing already, so the regression potential is low as these code paths have already had some exposure to real work loads. Tested on x86-64 with 5.11 and 5.14 kernels to exercise the build-time dkms config kernel detection paths. Exercised with the ubuntu zfs regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1944417/+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 1932157] Re: [21.10 FEAT] KVM: Use interpretation of specification exceptions
Upstream commit 7119decf47d9 "KVM: s390: Enable specification exception interpretation" landed in impish master-next as 14ba5a8c6744 and is part of Ubuntu-5.13.0-18.18: https://launchpad.net/ubuntu/+source/linux/5.13.0-18.18 And since 5.13.0-18.18 just landed in -proposed: linux | 5.13.0-18.18 | impish-proposed | source I'm updating this ticket to Fix Committed. ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- 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/1932157 Title: [21.10 FEAT] KVM: Use interpretation of specification exceptions Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: This allows KVM to let SIE interpret specification exceptions instead of doing this itself, leading to performance improvements. This feature will be made available with kernel >=5.15 A backport will be provided once available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932157/+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 1942633] Re: Can not boot impish in Cavium ThunderX
This bug is awaiting verification that the linux- hwe-5.13/5.13.0-17.17~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1942633 Title: Can not boot impish in Cavium ThunderX Status in linux package in Ubuntu: In Progress Bug description: Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits I tried 2 releases: - 20210817 ( https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ ) - 20210830 ( https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ ) 20210817: Ends the deploy successfully but fails to boot from disk: ``` [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11] [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc (Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1) [0.00] Machine model: Cavium ThunderX CN88XX board [ 139.896752] raid6: xor() 1224 MB/s, rmw enabled [ 139.957046] raid6: using neon recovery algorithm [ 140.020937] xor: measuring software checksum speed [ 140.085571]8regs : 2432 MB/sec [ 140.149834]32regs : 2687 MB/sec [ 140.212202]arm64_neon : 4390 MB/sec [ 140.271985] xor: using function: arm64_neon (4390 MB/sec) [ 140.335013] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 140.569847] Btrfs loaded, crc32c=crc32c-generic, zoned=yes Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. ``` 20210830 Fails the network boot: ``` [ 140.351066] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no find a nic with 1c:1b:0d:0d:52:7c done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: Interface BOOTIF did not appear in time done. ipconfig: BOOTIF: SIOCGIFINDEX: No such device ipconfig: no devices to configure ``` I will attach full logs of each try. JFYI, this is the same machine as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+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 1942160] Re: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
This bug is awaiting verification that the linux- hwe-5.13/5.13.0-17.17~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] VMD PCI-E bridges on ADL-M/P/S use new device IDs and therefore not covered by previous LTR reset fix in bug 1896598. [Fix] Additional entires to vmd_bridge_tbl in drivers/pci/quirks.c is requierd: * ADL-M: [8086:464d] * ADL-P: [8086:51b0] * ADL-S: [8086:7ab4] [Test Case] $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' ... 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ [Where problems could occur] This will reset zeroed PCI_LTR_MAX_SNOOP_LAT and PCI_LTR_MAX_NOSNOOP_LAT values to a fixed 3145728ns that is used on Windows. Devices might want to set itself to a smaller value, but while this is not yet correctly supported by VMD controller driver, so the device power consumption might be little worse than ideal. [Other Info] VMD ASPM was first supported for Tiger Lake cpus, so all kernel versions newer than 5.6 should have already the supporting function. This patch targets Alder Lake cpus that are supported since 5.10-oem and on. == original bug report == * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384, https://bugs.launchpad.net/bugs/1896598. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware
[Kernel-packages] [Bug 1942459] Re: Speakup modules not included in Hirsute kernel
This bug is awaiting verification that the linux- hwe-5.13/5.13.0-17.17~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1942459 Title: Speakup modules not included in Hirsute kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [SRU Justification] [Impact] The kernel modules for the speakup screen reader are not available in Ubuntu 21.04/hirsute. $ modinfo speakup_ltlk modinfo: ERROR: Module speakup_ltlk not found. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-31-generic 5.11.0-31.33 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 3207 F pulseaudio /dev/snd/pcmC0D0p: john 3207 F...m pulseaudio /dev/snd/controlC1: john 3207 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Thu Sep 2 10:46:10 2021 InstallationDate: Installed on 2021-08-25 (8 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. enxf2766f074582 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=de5924a4-e0f6-4c11-a364-ea107efc1086 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2018 dmi.bios.release: 65.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd12/13/2018:br65.29:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.product.sku: 0617 dmi.sys.vendor: Dell Inc. [Fix] CONFIG_ACCESSIBILITY=y CONFIG_SPEAKUP=y [Test Plan] Extract modules from linux-modules-extra and verify that speakup* modules exist. [Where problems could occur] Enabling CONFIG_ACCESSIBILITY could affect console output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942459/+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 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04
This bug is awaiting verification that the linux- hwe-5.13/5.13.0-17.17~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1935034 Title: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04 Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Status in linux source package in Hirsute: New Status in linux source package in Impish: Confirmed Bug description: [Impact] This is a feature request to update the mpt3sas driver to latest version in upstream 38.100.00.00 in Ubuntu 21.10 and Ubuntu 20.04. This will allow users to use fixes and enhancements that landed upstream in 5.14. For this reason, Broadcom and Dell have requested to pull these patches to update the mpt3sas driver to the current upstream version. I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver v36.100.00.00, following are the commit ID's to update to 38.100.00.00 [Fixes] 8b3c803529 scsi: mpt3sas: Signedness bug in _base_get_diag_triggers() 39718fe7ad scsi: mpt3sas: Fix spelling mistake in Kconfig "compatiblity" -> "compatibility" bfb3f00c06 scsi: mpt3sas: Simplify bool comparison d309ae0732 scsi: mpt3sas: Fix ReplyPostFree pool allocation 664f0dce20 scsi: mpt3sas: Add support for shared host tagset for CPU hotplug 688c1a0a13 scsi: mpt3sas: Additional diagnostic buffer query interface 446b5f3d3f scsi: mpt3sas: Update driver version to 37.100.00.00 8278807abd scsi: core: Add scsi_device_busy() wrapper 020b0f0a31 scsi: core: Replace sdev->device_busy with sbitmap e015e0ded1 scsi: mpt3sas: Fix misspelling of _base_put_smid_default_atomic() 2111ba8781 scsi: mpt3sas: Move a little data from the stack onto the heap cf9e575e62 scsi: mpt3sas: Fix a bunch of potential naming doc-rot 54cb88dc30 scsi: mpt3sas: Fix a couple of misdocumented functions/params 782a1ab33f scsi: mpt3sas: Fix some kernel-doc misnaming issues a50bd64616 scsi: mpt3sas: Do not use GFP_KERNEL in atomic context a1c4d77413 scsi: mpt3sas: Replace unnecessary dynamic allocation with a static one d6adc251dd scsi: mpt3sas: Force PCIe scatterlist allocations to be within same 4 GB region 7dd847dae1 scsi: mpt3sas: Force chain buffer allocations to be within same 4 GB region 970ac2bb70 scsi: mpt3sas: Force sense buffer allocations to be within same 4 GB region 58501fd937 scsi: mpt3sas: Force reply buffer allocations to be within same 4 GB region 2e4e858732 scsi: mpt3sas: Force reply post buffer allocations to be within same 4 GB region c569de899b scsi: mpt3sas: Force reply post array allocations to be within same 4 GB region 37067b9793 scsi: mpt3sas: Update driver version to 37.101.00.00 a8d548b0b3 scsi: mpt3sas: Fix a few kernel-doc issues 3401ecf7fc scsi: mpt3sas: Fix error return code of mpt3sas_base_attach() 206a3afa94 scsi: mpt3sas: Fix a typo 4c51f95696 scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES c0629d70ca scsi: mpt3sas: Fix endianness for ActiveCablePowerRequirement 3c8604691d scsi: mpt3sas: Block PCI config access from userspace during reset 16660db3fc scsi: mpt3sas: Fix out-of-bounds warnings in _ctl_addnl_diag_query 3ad0b1da0d scsi: mpt3sas: Fix two kernel-doc headers 2910a4a9e9 scsi: mpt3sas: Documentation cleanup e2fac6c44a scsi: mpt3sas: Fix deadlock while cancelling the running firmware event 19a622c39a scsi: mpt3sas: Handle firmware faults during first half of IOC init a0815c45c8 scsi: mpt3sas: Handle firmware faults during second half of IOC init f2b1e9c6f8 scsi: core: Introduce scsi_build_sense() 84a84cc6af scsi: mpt3sas: Fix fall-through warnings for Clang cf750be8e6 scsi: mpt3sas: Fix Coverity reported issue d6c2ce435f scsi: mpt3sas: Fix error return value in _scsih_expander_add() Note: We have already posted patch to update driver version to 38.100.00.00 Other patches are already available in upstream . [Testing] Load the driver Run IO [Regression Risk] No extra test cases are needed, normal regression test cases such as driver load & running IOs are enough. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1943935] Re: CirrusLogic/CS8409: No headset mic device when plugged earphone jack when HDMI/DP is used on Dolphin platform
This bug is awaiting verification that the linux- hwe-5.13/5.13.0-17.17~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1943935 Title: CirrusLogic/CS8409: No headset mic device when plugged earphone jack when HDMI/DP is used on Dolphin platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] When output device is set to HDMI/DP and headset plugged in, there is no Headset device available in sound settings. [Fix] Proposed fix in https://patchwork.kernel.org/project/alsa-devel/patch/20210916095646.7631-1-vita...@opensource.cirrus.com/ , already accepted as https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=94d508fa3186d0cbc63765aa94d5cf3bd847694c . This also depends on two commits which already in mainline kernel that refactor device init. [Test Case] 1. Set output device to HDMI/DP 2. Plug headset 3. Check Sound settings for a new headset device [Where problems could occur] The last patch simply makes the onboard audio jack to use phantom jack. No much potential risk introduced. The two prerequisites simplifies init procedures and may need to receive some more stress tests especially those for suspend/resume, plug/unplug. [Other Info] This is for the new oem Dolphin platform that is only available in oem-5.13/oem-5.14 and impish. See bug 1939541. == original bug report == [Steps to reproduce] 1. Check output device is HDMI/DP audio and it works 2. Plug headset 3. Check Sound settings for Input & Output [Expected result] Sound settings should have headset when plugging [Actual result] Sound settings has no headset To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1943935/+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 1946129] [NEW] package linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-36-generic package pre-removal script subproces
Public bug reported: i dont know what happened ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 AptOrdering: linux-image-5.11.0-36-generic:amd64: Purge linux-image-unsigned-5.11.0-36-generic:amd64: Install NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 5 20:00:15 2021 ErrorMessage: installed linux-image-5.11.0-36-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2021-09-28 (7 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-signed-hwe-5.11 Title: package linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-36-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946129 Title: package linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-36-generic package pre- removal script subprocess returned error exit status 1 Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: i dont know what happened ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 AptOrdering: linux-image-5.11.0-36-generic:amd64: Purge linux-image-unsigned-5.11.0-36-generic:amd64: Install NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 5 20:00:15 2021 ErrorMessage: installed linux-image-5.11.0-36-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2021-09-28 (7 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-signed-hwe-5.11 Title: package linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-36-generic package pre-removal script subprocess returned error exit status 1 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.11/+bug/1946129/+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 1946128] Re: ubuntu_lxc: Fails multiple tests
** Attachment added: "l1.txt" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946128/+attachment/5530799/+files/l1.txt ** Description changed: linux-aws-5.11 5.11.0-1020.21~20.04.2 - ubuntu_lxc test fails on 4 instances; a1.medium, c6g.8xlarge, i3en.24xlarge, - , t2.small - . All failures are identical: + ubuntu_lxc test fails on 4 instances; a1.medium, c6g.8xlarge, + i3en.24xlarge, t2.small + + All failures are identical: CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=2, Command returned non-zero exit status ** Description changed: linux-aws-5.11 5.11.0-1020.21~20.04.2 ubuntu_lxc test fails on 4 instances; a1.medium, c6g.8xlarge, i3en.24xlarge, t2.small All failures are identical: CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=2, Command returned non-zero exit status + + I do not see the same failures when run manually. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946128 Title: ubuntu_lxc: Fails multiple tests Status in ubuntu-kernel-tests: New Status in linux-aws-5.11 package in Ubuntu: New Bug description: linux-aws-5.11 5.11.0-1020.21~20.04.2 ubuntu_lxc test fails on 4 instances; a1.medium, c6g.8xlarge, i3en.24xlarge, t2.small All failures are identical: CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=2, Command returned non-zero exit status I do not see the same failures when run manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946128/+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 1946128] [NEW] ubuntu_lxc: Fails multiple tests
Public bug reported: linux-aws-5.11 5.11.0-1020.21~20.04.2 ubuntu_lxc test fails on 4 instances; a1.medium, c6g.8xlarge, i3en.24xlarge, t2.small All failures are identical: CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=2, Command returned non-zero exit status I do not see the same failures when run manually. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-aws-5.11 (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Description changed: - ubuntu_lxc test fails on 4 instances; a1.medium, c6g.8xlarge, i3en.24xlarge, + linux-aws-5.11 5.11.0-1020.21~20.04.2 + + ubuntu_lxc test fails on 4 instances; a1.medium, c6g.8xlarge, i3en.24xlarge, , t2.small . All failures are identical: CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=2, Command returned non-zero exit status -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946128 Title: ubuntu_lxc: Fails multiple tests Status in ubuntu-kernel-tests: New Status in linux-aws-5.11 package in Ubuntu: New Bug description: linux-aws-5.11 5.11.0-1020.21~20.04.2 ubuntu_lxc test fails on 4 instances; a1.medium, c6g.8xlarge, i3en.24xlarge, t2.small All failures are identical: CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=2, Command returned non-zero exit status I do not see the same failures when run manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946128/+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 1946109] Re: touchpad is not wokring at all, does not get recognized
*** This bug is a duplicate of bug 1946108 *** https://bugs.launchpad.net/bugs/1946108 ** This bug has been marked a duplicate of bug 1946108 touchpad is not wokring at all, does not get recognized -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946109 Title: touchpad is not wokring at all, does not get recognized Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Touchpad does not show after: cat /proc/bus/input/devices > ~/devices All drivers are up to date. Laptop is a: Fujitsu Lifebook U-7510 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 10:04:33 2021 InstallationDate: Installed on 2021-09-22 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 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.11/+bug/1946109/+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 1933359] Re: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request
I have created a test kernel at the following link: https://people.canonical.com/~mreed/mpi3mr/lp_1933359/ -- 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/1933359 Title: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: Broadcom is coming up with next generation high performance Storage IO and RAID controllers. For details, follow: https://www.spinics.net/lists/linux-scsi/msg147868.html This family of controllers is managed by "mpi3mr" Linux device driver(written from scratch). First patchset of the driver is accepted by Linux upstream. The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git The driver will be part of 5.14 mainline Linux kernel release. Here is the list of commit ids: 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints 74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support 28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check 2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume 44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of VD I/O timeout 71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging f061178e0762 scsi: mpi3mr: Complete support for soft reset 463429f8dd5c scsi: mpi3mr: Add support for threaded ISR 392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe drives 82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook 0ea177343f1f scsi: mpi3mr: Add change queue depth support e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks 8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook ff9561e910fc scsi: mpi3mr: Print IOC info for debugging 54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware fb9b04574f14 scsi: mpi3mr: Add support for recovering controller e36710dc06e3 scsi: mpi3mr: Additional event handling 8e653455547a scsi: mpi3mr: Add support for PCIe device event handling 13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling 672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread 023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair 824a156633df scsi: mpi3mr: Base driver code c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig Please include this driver in Ubuntu 21.10 release. Let me know for any questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933359/+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 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
Today's report. ** Attachment added: "prevboot-2021-10-05-b.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939966/+attachment/5530765/+files/prevboot-2021-10-05-b.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-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 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.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:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1945227] Re: drm/amdgpu: Add support for Yellow Carp
Verified on YC with the following combination all from -proposed: # dpkg -l | grep "linux-firmware\|linux-image-5.14.0-1005-oem\|21.0.3-0ubuntu0." ii libegl-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the EGL API -- Mesa vendor library ii libgbm1:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64generic buffer management API -- runtime ii libgl1-mesa-dri:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd6421.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the OpenGL API -- GLX vendor library ii linux-firmware 1.187.19 all Firmware for Linux kernel drivers ii linux-image-5.14.0-1005-oem5.14.0-1005.5 amd64Signed kernel image oem ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1945227 Title: drm/amdgpu: Add support for Yellow Carp Status in linux-firmware package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Bug description: [Impact] New hardware support for AMD's Yellow Carp need five commits backported to mesa and new firmware. This is only needed on focal, skipping hirsute (no kernel support there). [Test plan] Install updates, boot a YC machine and check that the desktop has full hardware acceleration. [Where problems could occur] The firmware is new, so it will simply add new files to l-f without any impact on others. Mesa adds five commits in total, and while some affect other chips, they mostly fix hw bugs or add a helper and such, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1946112] [NEW] Ubuntu Budgie 20.10 Raspi 4B 8GB. Frozzen Screen Video playing
Public bug reported: Ubuntu Budgie 21.10 ARM64. Raspberry 4B 8 GB. Newest updates till 10/05/2021. Proposed-Repo is activated, and all updates are newest. Mouse USB-wired. Keyboard USB-wired. Loudspeaker BT-connected. Screen HDMI1, no Speaker. I use kms. Tweak-Tool Budgie ARM Pi Setting 512 MB (Display) but default 128 MB the same Problem. There is a Problem with Video-Player. If I start a local Video, it plays 2-5 seconds and then Audio stops, Video freeze, Mouse Cursor freeze. Same by Playing Video from News-Letter N-TV in Mozilla Firefox 92.0. Moving Mouse Cursor, the System freeze suddenly during Video playing. System stops working and can’t shut down because Mouse don’t work. Hard Power-Off is the only way out! ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1946112 Title: Ubuntu Budgie 20.10 Raspi 4B 8GB. Frozzen Screen Video playing Status in linux-raspi package in Ubuntu: New Bug description: Ubuntu Budgie 21.10 ARM64. Raspberry 4B 8 GB. Newest updates till 10/05/2021. Proposed-Repo is activated, and all updates are newest. Mouse USB-wired. Keyboard USB-wired. Loudspeaker BT-connected. Screen HDMI1, no Speaker. I use kms. Tweak-Tool Budgie ARM Pi Setting 512 MB (Display) but default 128 MB the same Problem. There is a Problem with Video-Player. If I start a local Video, it plays 2-5 seconds and then Audio stops, Video freeze, Mouse Cursor freeze. Same by Playing Video from News-Letter N-TV in Mozilla Firefox 92.0. Moving Mouse Cursor, the System freeze suddenly during Video playing. System stops working and can’t shut down because Mouse don’t work. Hard Power-Off is the only way out! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946112/+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 1945757] Re: sysdig-dkms fails to build on arm64 - kernel 5.13
** Changed in: linux-oem-5.6 (Ubuntu Impish) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1945757 Title: sysdig-dkms fails to build on arm64 - kernel 5.13 Status in linux-oem-5.6 package in Ubuntu: Fix Committed Status in linux-oem-5.6 source package in Impish: Fix Committed Bug description: [Impact] sysdig-dkms fails to build on arm64 with the latest impish kernel (5.13): /var/lib/dkms/sysdig/0.27.1/build/main.c:1942:28: error: ‘SYSCALL_TABLE_ID0’ undeclared (first use in this function); did you mean ‘SYSCALL_TABLE_SIZE’? 1942 | table_index = id - SYSCALL_TABLE_ID0; |^ |SYSCALL_TABLE_SIZE /var/lib/dkms/sysdig/0.27.1/build/main.c:1942:28: note: each undeclared identifier is reported only once for each function it appears in /var/lib/dkms/sysdig/0.27.1/build/main.c: In function ‘syscall_exit_probe’: /var/lib/dkms/sysdig/0.27.1/build/main.c:2019:28: error: ‘SYSCALL_TABLE_ID0’ undeclared (first use in this function); did you mean ‘SYSCALL_TABLE_SIZE’? 2019 | table_index = id - SYSCALL_TABLE_ID0; |^ |SYSCALL_TABLE_SIZE [Test case] $ sudo apt install sysdig-dkms [Fix] SYSCALL_TABLE_ID0 needs to be properly defined for arm64. [Where problems could occur] If the syscall table base ID changes on arm64 we may experience kernel panics due to memory access violations or sysdig may report incorrect result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.6/+bug/1945757/+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 1946108] [NEW] touchpad is not wokring at all, does not get recognized
Public bug reported: Touchpad does not show after: cat /proc/bus/input/devices > ~/devices All drivers are up to date. Laptop is a: Fujitsu Lifebook U-7510 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 10:04:33 2021 InstallationDate: Installed on 2021-09-22 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946108 Title: touchpad is not wokring at all, does not get recognized Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Touchpad does not show after: cat /proc/bus/input/devices > ~/devices All drivers are up to date. Laptop is a: Fujitsu Lifebook U-7510 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 10:04:33 2021 InstallationDate: Installed on 2021-09-22 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 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.11/+bug/1946108/+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 1946109] [NEW] touchpad is not wokring at all, does not get recognized
Public bug reported: Touchpad does not show after: cat /proc/bus/input/devices > ~/devices All drivers are up to date. Laptop is a: Fujitsu Lifebook U-7510 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 10:04:33 2021 InstallationDate: Installed on 2021-09-22 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946109 Title: touchpad is not wokring at all, does not get recognized Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Touchpad does not show after: cat /proc/bus/input/devices > ~/devices All drivers are up to date. Laptop is a: Fujitsu Lifebook U-7510 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 10:04:33 2021 InstallationDate: Installed on 2021-09-22 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 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.11/+bug/1946109/+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 1836694] Re: memcg_test_3 from controllers in LTP failed with Bionic/Focal/Hirsute
** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836694 Title: memcg_test_3 from controllers in LTP failed with Bionic/Focal/Hirsute Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux source package in Impish: Confirmed Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+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-meta-hwe-5.13/5.13.0.16.16~20.04.5)
All autopkgtests for the newly accepted linux-meta-hwe-5.13 (5.13.0.16.16~20.04.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.31-0ubuntu9.2 (amd64) 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-meta-hwe-5.13 [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1945938] Re: [impish] Remove the downstream xr-usb-uart driver
** Changed in: linux (Ubuntu Impish) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945938 Title: [impish] Remove the downstream xr-usb-uart driver Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel to add support for USB UART chips: Family: USB UART Part Numbers: XR21V1410, XR21V1412, XR21V1414, XR21B1411, XR21B1420, XR21B1422, XR21B1424, XR22801, XR22802, XR22804 [Fix] In 5.13.x, support for these devices was added to the kernel via. following patch series: Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/ There have been long term maintenance challenges with the downstream vendor driver over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver supports most of the above part numbers, let's remove this redundant out-of-tree driver. [Test] The driver was functionally verified to work fine with XR21V1412. The support for other chips with part numbers mentioned above are also supported with the above patch series. [Where problems could occur] The downstream driver was designed to work with specific BIOS configs only defined on an IoT GW project which is locked to use only Xenial ESM and Bionic LTS kernels, there is a low chance of regression on the Impish series. [This is a tracking bug, please do not triage] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945938/+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 1942319] Re: When booting with UEFI, mokvar table and %:.platform keyring must be available
** Description changed: - When booting with UEFI, mokvar table and %:.platform keyring must be - available + [Impact] + + * When booting with UEFI, mokvar table and %:.platform keyring must be + available. These are required for builtin revocation certificates to be + present, shim builtin certificates to be present and thus support to + signed & verified kexec present. It also allows revocation of signed lrm + and livepatch drivers which are trusted by this kernel. + + * The kvm annotations are very minimal, v3 format, and the parent + kernel's annotations are not enforced. + + [Test Plan] + + * Check that /sys/firmware/efi/mok-variables/ is available + + * Check that %:.blacklist keyring is populated + +$ sudo keyctl list %:.blacklist + + + * Check that %:.platform keyring is populated + +$ sudo keyctl list %:.platform + + [Where problems could occur] + + * Given how small the kvm config is, it is not clear if all of lockdown + features are correctly enabled. Specifically measuring and appraising + things with integrity framework. It is possible further config changes + will be required to make kvm flavour as hardened as generic one. + + [Other Info] + + * This issue was discovered whilst working on https://bugs.launchpad.net/bugs/1928679 and https://bugs.launchpad.net/bugs/1932029 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1942319 Title: When booting with UEFI, mokvar table and %:.platform keyring must be available Status in linux-kvm package in Ubuntu: New Bug description: [Impact] * When booting with UEFI, mokvar table and %:.platform keyring must be available. These are required for builtin revocation certificates to be present, shim builtin certificates to be present and thus support to signed & verified kexec present. It also allows revocation of signed lrm and livepatch drivers which are trusted by this kernel. * The kvm annotations are very minimal, v3 format, and the parent kernel's annotations are not enforced. [Test Plan] * Check that /sys/firmware/efi/mok-variables/ is available * Check that %:.blacklist keyring is populated $ sudo keyctl list %:.blacklist * Check that %:.platform keyring is populated $ sudo keyctl list %:.platform [Where problems could occur] * Given how small the kvm config is, it is not clear if all of lockdown features are correctly enabled. Specifically measuring and appraising things with integrity framework. It is possible further config changes will be required to make kvm flavour as hardened as generic one. [Other Info] * This issue was discovered whilst working on https://bugs.launchpad.net/bugs/1928679 and https://bugs.launchpad.net/bugs/1932029 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1942319/+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 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
Please test a kernel build with this patch, combined with adding "pci=no_e820" added to the kernel commandline. See comment 133 for more details. ** Patch added: "[PATCH] x86/PCI: Add pci=no_e820 cmdline option to ignore E820 reservations for bridge windows" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1878279/+attachment/5530683/+files/0001-x86-PCI-Add-pci-no_e820-cmdline-option-to-ignore-E82.patch ** Patch removed: "[PATCH] PCI/ACPI: Make acpi_pci_root_validate_resources() reject IOMEM resources which start at address 0" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1878279/+attachment/5504784/+files/0001-PCI-ACPI-Make-acpi_pci_root_validate_resources-rejec.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) 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: IdeaPad 5 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
This is a follow-up to comment #123 Sorry for the long silence on this bug. I was hoping one of the upstream pci-subsys devs would help out with this... Since that did not happen I've been looking into fixing this myself now. I've come up with a solution which still involves a kernel cmdline option for now, but this one is a much smaller hammer (almost a scalpel) and once it is confirmed that this works I can enable this by default through a DMI quirk. I also hope that this option will not cause the stability issues seen when using pci=nocrs and that it will remove the need to specify i8042.nopnp=1 . I'll attach my patch here and then hopefully one of the Ubuntu devs can build a test-kernel for people who need pci=nocrs to test. Alternatively you can build your own kernel with this patch added, see the Ubuntu docs for how to do this. Once you have a kernel with this patch, remove pci=nocrs and i8042.nopnp=1 from the kernel-commandline and instead add only "pci=no_e820". If this helps please provide DMI strings for your laptop, so that I can add a quirk to the kernel to automatically enable "pci=no_e820" on your laptop model. Run the following command *as normal user* to collect the DMI strings for your laptop: grep . /sys/class/dmi/id/* 2> /dev/null And copy and paste the output here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) 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: IdeaPad 5 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 1933938] Re: Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P
** Tags added: verification-needed-focal -- 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/1933938 Title: Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P Status in HWE Next: New Status in intel: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-firmware source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [SRU Justfication] [Impact] Intel CNVi moves key elements of Wi-Fi and Bluetooth Technology into Intel processors. As a result, their driver may have to be revised across processor generations. [Fix] This depends on a few changes set to address all issues on supporting: * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.* (ADL-S) * BT: intel/ibt-0040-0041.* (ADL-P) * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: intel/ibt-1040-4150.* * BT: intel/ibt-0040-4150.* * PCI [8086:7af0] Subsystem [8086:0aaa] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* AX201 wifi firmware for ADL platforms will be available with FW API >= 64, so a patchset "iwlwifi: bump FW API to 64 for AX devices" will be required. Depending fixes are pulled as well. For reset of them, 3 additional commits for iwlwifi, also in mainline now, are required. The last patch for 9462 Bluetooth is still under review at the time of writing. This is the only patch that is not yet in unstable. [Test Case] Install these CRF on ADL-S/ADL-P platforms and check if WiFi/Bluetooth is working. [Where problems could occur] While this is a new generation, we may have common issues like power consumption, network throughput, suspend/resume issues. [Other Info] Intel is to release the corresponding firmware blobs next week. These are verified with pre-released firmware. == original bug report == * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.sfi * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: ibt-1040-4150.sfi * PCI [8086:7af0] Subsystem [8086:0264] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* * BT: intel/ibt-0040-1020.* To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933938/+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 1943713] Re: ubuntu_kvm_smoke_test failed on arm64 node scobee-kernel with Focal 5.4
Also observed on the same host for the sru-20210927 hirsute:linux (5.11) kernel. ** Tags added: 5.11 hirsute sru-20210927 -- 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/1943713 Title: ubuntu_kvm_smoke_test failed on arm64 node scobee-kernel with Focal 5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: ubuntu_kvm_smoke_test.kvm_smoke_test failed with focal/linux 5.4.0-85.95 on node scobee-kernel: 03:31:05 INFO | STARTubuntu_kvm_smoke_test.kvm_smoke_test ubuntu_kvm_smoke_test.kvm_smoke_testtimestamp=1631676664timeout=3600 localtime=Sep 15 03:31:04 [...] 03:31:05 ERROR| [stderr] ++ uvt-simplestreams-libvirt query 03:31:05 ERROR| [stderr] ++ grep -P 'focal.*arm64' 03:31:06 ERROR| [stderr] ++ true 03:31:06 ERROR| [stderr] + image= 03:31:06 ERROR| [stderr] + '[' -z '' ']' 03:31:06 ERROR| [stderr] + uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily release=focal arch=arm64 03:31:27 ERROR| [stderr] + uvt-kvm create bjf-test release=focal arch=arm64 03:31:33 ERROR| [stderr] + uvt-kvm wait bjf-test --insecure --ssh-private-key-file /home/ubuntu/.ssh/id_rsa 03:33:59 ERROR| [stderr] uvt-kvm: error: timed out waiting for ssh to open on 192.168.122.246. 03:33:59 ERROR| [stderr] + cleanup 03:33:59 ERROR| [stderr] + uvt-kvm destroy bjf-test 03:34:13 ERROR| [stderr] + '[' arm64 = ppc64el ']' This is not a regression, this is a new test machine and this test has been failing on this node since the first test run. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943713/+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 1945565] Re: [SRU] Revert amdgpu/renoir firmware
** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1945565 Title: [SRU] Revert amdgpu/renoir firmware Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] The USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Revert below change, this issue is gone. commit a543b9c1bfd12e60d962acd48108234481a8581f Author: Alex Deucher Date: Thu Jul 1 12:23:11 2021 +0800 amdgpu: update renoir firmware from 21.20 BugLink: https://bugs.launchpad.net/bugs/1934014 From internal git commit: 8b05e03570818d047d7ea0a7388c89c4192fd20b Signed-off-by: Alex Deucher Signed-off-by: Josh Boyer (backported from commit 56ef642160203f8be7e1334feca4a76852c74bc0) [khfeng: Squashed multiple updates into one commit] Signed-off-by: Kai-Heng Feng Signed-off-by: Timo Aaltonen [Test] Verify S3 on renoir's platforms. [Where problems could occur] Renoir based systems can't resume from s2idle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945565/+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 1943841] Re: svm from ubuntu_kvm_unit_tests interrupt with "Unhandled exception 13 #GP at ip 00000000004027e3" on F-intel-5.13
Also happens with hirsute:linux 5.11.0-38.42 for sru-20210927 on that host (gonzo). ** Tags added: 5.11 amd64 hirsute sru-20210927 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1943841 Title: svm from ubuntu_kvm_unit_tests interrupt with "Unhandled exception 13 #GP at ip 004027e3" on F-intel-5.13 Status in ubuntu-kernel-tests: New Status in linux-intel-5.13 package in Ubuntu: New Bug description: Failing with Focal Intel 5.13.0-1004.4 on node gonzo A bit like bug 1934939, but this time it looks like this has passed through more cases than that bug. Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/svm' BUILD_HEAD=1593e88a 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.8QIXdsXIyJ -smp 2 -cpu max,+svm -m 4g # -initrd /tmp/tmp.VvuuwXHRuX enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 10bf000 cr4 = 20 NPT detected - running all tests with NPT enabled PASS: null PASS: vmrun PASS: ioio PASS: vmrun intercept check PASS: rsm PASS: cr3 read intercept PASS: cr3 read nointercept PASS: cr3 read intercept emulate PASS: dr intercept check PASS: next_rip PASS: msr intercept check PASS: mode_switch PASS: asid_zero PASS: sel_cr0_bug PASS: npt_nx PASS: npt_np PASS: npt_us PASS: npt_rw PASS: npt_rw_pfwalk PASS: npt_l1mmio PASS: npt_rw_l1mmio PASS: tsc_adjust Latency VMRUN : max: 322434 min: 21233 avg: 36460 Latency VMEXIT: max: 298726 min: 16889 avg: 17717 PASS: latency_run_exit Latency VMRUN : max: 334040 min: 23446 avg: 36313 Latency VMEXIT: max: 310725 min: 16935 avg: 17618 PASS: latency_run_exit_clean Latency VMLOAD: max: 732466 min: 4675 avg: 4879 Latency VMSAVE: max: 60901 min: 4565 avg: 4850 Latency STGI: max: 43057 min: 3726 avg: 3862 Latency CLGI: max: 723675 min: 3644 avg: 3724 PASS: latency_svm_insn PASS: exception with vector 2 not injected PASS: divide overflow exception injected PASS: eventinj.VALID cleared PASS: exc_inject PASS: pending_event PASS: pending_event_cli PASS: direct interrupt while running guest PASS: intercepted interrupt while running guest PASS: direct interrupt + hlt PASS: intercepted interrupt + hlt PASS: interrupt PASS: direct NMI while running guest PASS: NMI intercept while running guest PASS: nmi PASS: direct NMI + hlt PASS: NMI intercept while running guest PASS: intercepted NMI + hlt PASS: nmi_hlt PASS: virq_inject PASS: No RIP corruption detected after 1 timer interrupts PASS: reg_corruption enabling apic PASS: svm_init_startup_test PASS: host_rflags PASS: CPUID.01H:ECX.XSAVE set before VMRUN PASS: svm_cr4_osxsave_test_guest finished with VMMCALL PASS: CPUID.01H:ECX.XSAVE set after VMRUN PASS: EFER.SVME: 1500 PASS: EFER.SVME: 500 PASS: Test EFER 9:8: 1700 PASS: Test EFER 63:16: 11500 PASS: Test EFER 63:16: 101500 PASS: Test EFER 63:16: 1001500 PASS: Test EFER 63:16: 10001500 PASS: Test EFER 63:16: 11500 PASS: Test EFER 63:16: 101500 PASS: Test EFER 63:16: 1001500 PASS: Test EFER 63:16: 10001500 PASS: Test EFER 63:16: 11500 PASS: Test EFER 63:16: 101500 PASS: Test EFER 63:16: 1001500 PASS: Test EFER 63:16: 10001500 PASS: EFER.LME=1 (1500), CR0.PG=1 (80010011) and CR4.PAE=0 (4) PASS: EFER.LME=1 (1500), CR0.PG=1 and CR0.PE=0 (80010010) PASS: EFER.LME=1 (1500), CR0.PG=1 (80010011), CR4.PAE=1 (40020), CS.L=1 and CS.D=1 (699) PASS: Test CR0 CD=1,NW=0: c0010011 PASS: Test CR0 CD=1,NW=1: e0010011 PASS: Test CR0 CD=0,NW=0: 80010011 PASS: Test CR0 CD=0,NW=1: a0010011 PASS: Test CR0 63:32: 180010011 PASS: Test CR0 63:32: 1080010011 PASS: Test CR0 63:32: 10080010011 PASS: Test CR0 63:32: 100080010011 PASS: Test CR0 63:32: 180010011 PASS: Test CR0 63:32: 1080010011 PASS: Test CR0 63:32: 10080010011 PASS: Test CR0 63:32: 100080010011 PASS: Test CR3 63:0: 10010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 20010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 40010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 80010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 100010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 200010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 400010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0:
[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP failed with Bionic/Focal/Hirsute
It will take about 1989 seconds (~34 min) to run on g1.small instance. -- 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/1836694 Title: memcg_test_3 from controllers in LTP failed with Bionic/Focal/Hirsute Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+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 1933938] Re: Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.19 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1933938 Title: Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P Status in HWE Next: New Status in intel: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-firmware source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [SRU Justfication] [Impact] Intel CNVi moves key elements of Wi-Fi and Bluetooth Technology into Intel processors. As a result, their driver may have to be revised across processor generations. [Fix] This depends on a few changes set to address all issues on supporting: * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.* (ADL-S) * BT: intel/ibt-0040-0041.* (ADL-P) * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: intel/ibt-1040-4150.* * BT: intel/ibt-0040-4150.* * PCI [8086:7af0] Subsystem [8086:0aaa] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* AX201 wifi firmware for ADL platforms will be available with FW API >= 64, so a patchset "iwlwifi: bump FW API to 64 for AX devices" will be required. Depending fixes are pulled as well. For reset of them, 3 additional commits for iwlwifi, also in mainline now, are required. The last patch for 9462 Bluetooth is still under review at the time of writing. This is the only patch that is not yet in unstable. [Test Case] Install these CRF on ADL-S/ADL-P platforms and check if WiFi/Bluetooth is working. [Where problems could occur] While this is a new generation, we may have common issues like power consumption, network throughput, suspend/resume issues. [Other Info] Intel is to release the corresponding firmware blobs next week. These are verified with pre-released firmware. == original bug report == * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.sfi * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: ibt-1040-4150.sfi * PCI [8086:7af0] Subsystem [8086:0264] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* * BT: intel/ibt-0040-1020.* To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933938/+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 1945438] Re: Update ADL-P dmc firmware
Hello Timo, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.19 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Focal) 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/1945438 Title: Update ADL-P dmc firmware Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] It's reported that 2.12 fixes some issues with DC6 power saving state on ADL-P [Test case] With a suitable kernel (oem-5.14 which knows about this fw version) test that DC6 power state works without issues. [Where things could go wrong] Using this version needs kernel support, so it does not affect other systems than Alder Lake P. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945438/+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 1945227] Re: drm/amdgpu: Add support for Yellow Carp
Hello Timo, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.19 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1945227 Title: drm/amdgpu: Add support for Yellow Carp Status in linux-firmware package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Bug description: [Impact] New hardware support for AMD's Yellow Carp need five commits backported to mesa and new firmware. This is only needed on focal, skipping hirsute (no kernel support there). [Test plan] Install updates, boot a YC machine and check that the desktop has full hardware acceleration. [Where problems could occur] The firmware is new, so it will simply add new files to l-f without any impact on others. Mesa adds five commits in total, and while some affect other chips, they mostly fix hw bugs or add a helper and such, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1945565] Re: [SRU] Revert amdgpu/renoir firmware
Hello Bin, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.19 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1945565 Title: [SRU] Revert amdgpu/renoir firmware Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] The USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Revert below change, this issue is gone. commit a543b9c1bfd12e60d962acd48108234481a8581f Author: Alex Deucher Date: Thu Jul 1 12:23:11 2021 +0800 amdgpu: update renoir firmware from 21.20 BugLink: https://bugs.launchpad.net/bugs/1934014 From internal git commit: 8b05e03570818d047d7ea0a7388c89c4192fd20b Signed-off-by: Alex Deucher Signed-off-by: Josh Boyer (backported from commit 56ef642160203f8be7e1334feca4a76852c74bc0) [khfeng: Squashed multiple updates into one commit] Signed-off-by: Kai-Heng Feng Signed-off-by: Timo Aaltonen [Test] Verify S3 on renoir's platforms. [Where problems could occur] Renoir based systems can't resume from s2idle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945565/+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 1940665] Re: Lenovo Carbon X1 9th gen no longer powers off
Can confirm that sudo apt install linux-generic-hwe-20.04 makes everything work. Didn't have to remove OEM. I've tried some earlier generic-kernels where the screen scaling (running 4k) would be off and the buttons for controlling the light (F5 F6) didn't work. But using the latest generic everything seems good. It is however the OEM which gets automatically installed during install and update and which breaks the system. So it really needs to be fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1940665 Title: Lenovo Carbon X1 9th gen no longer powers off Status in linux-oem-5.10 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.3 LTS linux-oem-5.10: 5.10.0-1044.46 Power off system, either through GUI or by shutdown -P now Expected result: System powers completely off What happens: System seems to be powering completely off. Screen goes black, but computer is still running, getting hot and using battery. Have to press power button for 4 seconds to power completely off. Solution so far: Use linux-generic-something To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1940665/+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 1940665] Re: Lenovo Carbon X1 9th gen no longer powers off
apport-collect 1940665 gives me a bunch of Python-errors in terminal. BTW the problem persists when running 5.10.0-1049-oem -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1940665 Title: Lenovo Carbon X1 9th gen no longer powers off Status in linux-oem-5.10 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.3 LTS linux-oem-5.10: 5.10.0-1044.46 Power off system, either through GUI or by shutdown -P now Expected result: System powers completely off What happens: System seems to be powering completely off. Screen goes black, but computer is still running, getting hot and using battery. Have to press power button for 4 seconds to power completely off. Solution so far: Use linux-generic-something To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1940665/+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 1913442] Re: [Ubuntu 20.04] Problem leading IUCV service down (on s390x)
Hi Harald, well, I'm a bit confused - probably because I don't see the entire discussion that you may have in bugzilla. I guess you are talking about the new/add issue that was mentioned in LP comment #7 ? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913442/comments/7 Well, since this is obviously not related to the original issue that was reported by this bug, I proceeded with the patch request (SRU) to focal and just requested to add a backport of this commit: https://github.com/torvalds/linux/commit/49f2d2419d60a103752e5fbaf158cf8d07c0d884 to focal master next (backport only because of changes in the context). And I agree with not seeing any relationship to AP and crypt (not sure why this assumption came up)?! -- 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/1913442 Title: [Ubuntu 20.04] Problem leading IUCV service down (on s390x) Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: SRU Justification: == [Impact] * Problems occur in IBM z/VM's IUCV (Inter User Communication Vehicle) environments and its communication. * Errors like "usercopy: Kernel memory overwrite attempt detected to SLUB object 'dma-kmalloc-1 k' (offset 0, size 11)!" pop up and cause failures. * This is because IUCV uses kmalloc() with __GFP_DMA because of memory address restrictions. * The solution is to mark dma-kmalloc caches as usercopy caches. [Fix] * 49f2d2419d60a103752e5fbaf158cf8d07c0d884 49f2d2419d60 "usercopy: mark dma-kmalloc caches as usercopy caches" * Due to changes in the context of the upstream patch, a cherry-pick was not possible and the following backport was created: https://bugs.launchpad.net/bugs/1913442/+attachment/5457885/+files/commit_49f2d2419d60_backport.patch [Test Case] * Setup Ubuntu Server 20.04 on s390x system as IBM z/VM guest aka virtual machine. * Setup IUCV on z/VM: Setting up the (IUCV TCPIP) service machine: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_t_iucv_tcpservice.html * Set up a Linux IUCV instance: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_t_iucv_scen1_guest.html * Set up an IUCV direct: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_c_iucv_connect.html * Make use of IUCV, for example using ssh on a direct connection. * Verify if the connections is stable and watch out for messages starting with "usercopy". [Regression Potential] * Problems could occur in case the create_kmalloc_cache call is done wrong, for example with wrong index, wrong size or just wrong comma separations. * Wrong size or index will probably lead to similar instability problems that exist today. * Problems in the syntax (commas etc.) will be detected at compile time. * But it's just a single line modification in function create_kmalloc_caches of /mm/slab_common.c, * so the change is very limited and quite traceable. * And it was in depth discussed here: https://lore.kernel.org/kernel-hardening/1515636190-24061-2-git-send-email-keesc...@chromium.org/ * a reviewed by a lot of kernel engineers (see provenance) * and it was already upstream accepted with kernel 5.8. [Other] * Since the commit is upstream accepted with 5.8, so it's already in impish and hirsute (and groovy). * Hence this kernel SRU submission is for Focal only and covers only the above single but common code commit/patch. __ When I deployed a Ubuntu20.04 instance with kernel version of 5.4.0-58-generic under z/VM, I saw below messages from kernel and the iucvserv program malfunctioned. Hence it caused some devices like network device configuration failure and deployment failure. Dec 14 22:02:26 ub2004img iucvserv: Receive OPNCLD4 0.0.0.1 pwd sent from IUCV client. Dec 14 22:02:26 ub2004img iucvserv: /etc/iucv_authorized_userid exists, check authorization. Dec 14 22:02:26 ub2004img iucvserv: senduserid=OPNCLD4, authuserid=OPNCLD4, len=7 Dec 14 22:02:26 ub2004img iucvserv: Current version is 0.0.0.1, upgraded version is 0.0.0.1 Dec 14 22:02:26 ub2004img iucvserv: Will execute the linux command pwd 2>&1; echo iucvcmdrc=$? sent from IUCV client. Dec 14 22:02:26 ub2004img iucvserv: result length=14, send message length=14,#012 /#012iucvcmdrc=0 Dec 14 22:02:26 ub2004img kernel: [63084.184649] [ cut here ] Dec 14 22:02:26 ub2004img kernel: [63084.184654] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'dma-kmalloc-1k' (offset 0, size 20)!
[Kernel-packages] [Bug 1946055] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946055 Title: Ubuntu 21.04 drivers/drm/i915 crashes on my laptop! Status in linux package in Ubuntu: Confirmed Bug description: [2.515353] Missing case (val == 65535) [2.515366] WARNING: CPU: 3 PID: 478 at drivers/gpu/drm/i915/intel_dram.c:96 skl_dram_get_dimm_info+0x79/0x1b0 [i915] [2.515433] Modules linked in: snd_hda_core kvm_intel snd_hwdep nvidia(PO+) libarc4 kvm joydev soundwire_bus nls_iso8859_1 mei_hdcp intel_rapl_msr i915(+) fjes(-) iwlwifi crct10dif_pclmul ghash_clmulni_intel snd_soc_core drm_kms_helper aesni_intel processor_thermal_device snd_compress cec processor_thermal_rfim ac97_bus crypto_simd snd_pcm_dmaengine rc_core i2c_algo_bit cryptd processor_thermal_mbox fb_sys_fops input_leds mei_me thinkpad_acpi glue_helper syscopyarea intel_cstate nvram efi_pstore sysfillrect snd_seq_midi serio_raw wmi_bmof cfg80211 ee1004 ledtrig_audio snd_pcm processor_thermal_rapl ucsi_acpi(+) sysimgblt snd_seq_midi_event mei intel_rapl_common typec_ucsi intel_soc_dts_iosf snd_rawmidi typec snd_seq snd_seq_device snd_timer snd int3403_thermal soundcore int340x_thermal_zone mac_hid intel_hid int3400_thermal sparse_keymap acpi_thermal_rel acpi_pad acpi_tad sch_fq_codel stp llc ip_vs_wrr ip_vs_sh ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c msr [2.515472] parport_pc ppdev lp drm parport ip_tables x_tables autofs4 crc32_pclmul sdhci_pci psmouse cqhci i2c_i801 i2c_smbus sdhci igc nvme thunderbolt xhci_pci nvme_core xhci_pci_renesas wmi video pinctrl_tigerlake [2.515484] CPU: 3 PID: 478 Comm: systemd-udevd Tainted: P O 5.11.0-37-generic #41-Ubuntu [2.515486] Hardware name: LENOVO 20YUCTO1WW/20YUCTO1WW, BIOS N37ET34W (1.15 ) 09/01/2021 [2.515487] RIP: 0010:skl_dram_get_dimm_info+0x79/0x1b0 [i915] [2.515534] Code: 0f 84 34 01 00 00 41 f7 c0 00 01 00 00 0f 84 27 01 00 00 41 0f b7 d0 48 c7 c6 b1 6b fd c0 48 c7 c7 b5 6b fd c0 e8 07 1e 7c e1 <0f> 0b 44 0f b7 0b b9 01 00 00 00 31 c0 31 f6 88 43 02 41 c1 ff 09 [2.515535] RSP: 0018:be36011b7980 EFLAGS: 00010282 [2.515537] RAX: RBX: be36011b79ec RCX: 9b27574d8ac8 [2.515538] RDX: ffd8 RSI: 0027 RDI: 9b27574d8ac0 [2.515539] RBP: be36011b79a8 R08: R09: be36011b7760 [2.515540] R10: be36011b7758 R11: a37535e8 R12: [2.515541] R13: 004c R14: 9b164558 R15: [2.515542] FS: 7fb8218a08c0() GS:9b27574c() knlGS: [2.515544] CS: 0010 DS: ES: CR0: 80050033 [2.515545] CR2: 7fb8213ae4e0 CR3: 000108a5e006 CR4: 00770ee0 [2.515546] PKRU: 5554 [2.515546] Call Trace: [2.515549] skl_dram_get_channel_info+0x2e/0x150 [i915] [2.515592] skl_dram_get_channels_info+0x6e/0x190 [i915] [2.515634] skl_get_dram_info+0x6e/0x100 [i915] [2.515667] intel_dram_detect+0x3e/0xd0 [i915] [2.515711] i915_driver_hw_probe+0x1cc/0x210 [i915] [2.515748] i915_driver_probe+0xe5/0x2f0 [i915] [2.515781] ? mutex_lock+0x13/0x40 [2.515785] ? acpi_dev_found+0x66/0x70 [2.515788] i915_pci_probe+0x58/0x140 [i915] [2.515822] local_pci_probe+0x48/0x80 [2.515824] pci_call_probe+0x53/0xf0 [2.515826] pci_device_probe+0xad/0xf0 [2.515827] really_probe+0x23a/0x4a0 [2.515830] driver_probe_device+0xe9/0x160 [2.515832] device_driver_attach+0xab/0xb0 [2.515833] __driver_attach+0x8f/0x150 [2.515835] ? device_driver_attach+0xb0/0xb0 [2.515836] bus_for_each_dev+0x7e/0xc0 [2.515837] driver_attach+0x1e/0x20 [2.515839] bus_add_driver+0x135/0x1f0 [2.515840] driver_register+0x95/0xf0 [2.515842] __pci_register_driver+0x54/0x60 [2.515843] i915_init+0x66/0x86 [i915] [2.515877] ? 0xc0c7 [2.515878] do_one_initcall+0x48/0x1d0 [2.515881] ? kmem_cache_alloc_trace+0xf6/0x200 [2.515883] ? do_init_module+0x28/0x290 [2.515886] do_init_module+0x62/0x290 [2.515887] load_module+0x6fd/0x780 [2.515888] __do_sys_finit_module+0xc2/0x120 [2.515890] __x64_sys_finit_module+0x1a/0x20 [2.515891] do_syscall_64+0x38/0x90 [2.515893] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [2.515894] RIP: 0033:0x7fb821d58f6d [2.515896] Code: 28 0d 00 0f 05 eb a9 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d cb de 0c 00 f7 d8 64 89 01 48 [2.515897] RSP: 002b:7ffdf53714c8 EFLAGS: 0246
[Kernel-packages] [Bug 1946055] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1946055/+attachment/5530637/+files/PulseList.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/1946055 Title: Ubuntu 21.04 drivers/drm/i915 crashes on my laptop! Status in linux package in Ubuntu: New Bug description: [2.515353] Missing case (val == 65535) [2.515366] WARNING: CPU: 3 PID: 478 at drivers/gpu/drm/i915/intel_dram.c:96 skl_dram_get_dimm_info+0x79/0x1b0 [i915] [2.515433] Modules linked in: snd_hda_core kvm_intel snd_hwdep nvidia(PO+) libarc4 kvm joydev soundwire_bus nls_iso8859_1 mei_hdcp intel_rapl_msr i915(+) fjes(-) iwlwifi crct10dif_pclmul ghash_clmulni_intel snd_soc_core drm_kms_helper aesni_intel processor_thermal_device snd_compress cec processor_thermal_rfim ac97_bus crypto_simd snd_pcm_dmaengine rc_core i2c_algo_bit cryptd processor_thermal_mbox fb_sys_fops input_leds mei_me thinkpad_acpi glue_helper syscopyarea intel_cstate nvram efi_pstore sysfillrect snd_seq_midi serio_raw wmi_bmof cfg80211 ee1004 ledtrig_audio snd_pcm processor_thermal_rapl ucsi_acpi(+) sysimgblt snd_seq_midi_event mei intel_rapl_common typec_ucsi intel_soc_dts_iosf snd_rawmidi typec snd_seq snd_seq_device snd_timer snd int3403_thermal soundcore int340x_thermal_zone mac_hid intel_hid int3400_thermal sparse_keymap acpi_thermal_rel acpi_pad acpi_tad sch_fq_codel stp llc ip_vs_wrr ip_vs_sh ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c msr [2.515472] parport_pc ppdev lp drm parport ip_tables x_tables autofs4 crc32_pclmul sdhci_pci psmouse cqhci i2c_i801 i2c_smbus sdhci igc nvme thunderbolt xhci_pci nvme_core xhci_pci_renesas wmi video pinctrl_tigerlake [2.515484] CPU: 3 PID: 478 Comm: systemd-udevd Tainted: P O 5.11.0-37-generic #41-Ubuntu [2.515486] Hardware name: LENOVO 20YUCTO1WW/20YUCTO1WW, BIOS N37ET34W (1.15 ) 09/01/2021 [2.515487] RIP: 0010:skl_dram_get_dimm_info+0x79/0x1b0 [i915] [2.515534] Code: 0f 84 34 01 00 00 41 f7 c0 00 01 00 00 0f 84 27 01 00 00 41 0f b7 d0 48 c7 c6 b1 6b fd c0 48 c7 c7 b5 6b fd c0 e8 07 1e 7c e1 <0f> 0b 44 0f b7 0b b9 01 00 00 00 31 c0 31 f6 88 43 02 41 c1 ff 09 [2.515535] RSP: 0018:be36011b7980 EFLAGS: 00010282 [2.515537] RAX: RBX: be36011b79ec RCX: 9b27574d8ac8 [2.515538] RDX: ffd8 RSI: 0027 RDI: 9b27574d8ac0 [2.515539] RBP: be36011b79a8 R08: R09: be36011b7760 [2.515540] R10: be36011b7758 R11: a37535e8 R12: [2.515541] R13: 004c R14: 9b164558 R15: [2.515542] FS: 7fb8218a08c0() GS:9b27574c() knlGS: [2.515544] CS: 0010 DS: ES: CR0: 80050033 [2.515545] CR2: 7fb8213ae4e0 CR3: 000108a5e006 CR4: 00770ee0 [2.515546] PKRU: 5554 [2.515546] Call Trace: [2.515549] skl_dram_get_channel_info+0x2e/0x150 [i915] [2.515592] skl_dram_get_channels_info+0x6e/0x190 [i915] [2.515634] skl_get_dram_info+0x6e/0x100 [i915] [2.515667] intel_dram_detect+0x3e/0xd0 [i915] [2.515711] i915_driver_hw_probe+0x1cc/0x210 [i915] [2.515748] i915_driver_probe+0xe5/0x2f0 [i915] [2.515781] ? mutex_lock+0x13/0x40 [2.515785] ? acpi_dev_found+0x66/0x70 [2.515788] i915_pci_probe+0x58/0x140 [i915] [2.515822] local_pci_probe+0x48/0x80 [2.515824] pci_call_probe+0x53/0xf0 [2.515826] pci_device_probe+0xad/0xf0 [2.515827] really_probe+0x23a/0x4a0 [2.515830] driver_probe_device+0xe9/0x160 [2.515832] device_driver_attach+0xab/0xb0 [2.515833] __driver_attach+0x8f/0x150 [2.515835] ? device_driver_attach+0xb0/0xb0 [2.515836] bus_for_each_dev+0x7e/0xc0 [2.515837] driver_attach+0x1e/0x20 [2.515839] bus_add_driver+0x135/0x1f0 [2.515840] driver_register+0x95/0xf0 [2.515842] __pci_register_driver+0x54/0x60 [2.515843] i915_init+0x66/0x86 [i915] [2.515877] ? 0xc0c7 [2.515878] do_one_initcall+0x48/0x1d0 [2.515881] ? kmem_cache_alloc_trace+0xf6/0x200 [2.515883] ? do_init_module+0x28/0x290 [2.515886] do_init_module+0x62/0x290 [2.515887] load_module+0x6fd/0x780 [2.515888] __do_sys_finit_module+0xc2/0x120 [2.515890] __x64_sys_finit_module+0x1a/0x20 [2.515891] do_syscall_64+0x38/0x90 [2.515893] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [2.515894] RIP: 0033:0x7fb821d58f6d [2.515896] Code: 28 0d 00 0f 05 eb a9 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d cb de 0c 00 f7 d8 64 89 01 48 [2.515897] RSP:
[Kernel-packages] [Bug 1946055] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1946055/+attachment/5530640/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946055 Title: Ubuntu 21.04 drivers/drm/i915 crashes on my laptop! Status in linux package in Ubuntu: New Bug description: [2.515353] Missing case (val == 65535) [2.515366] WARNING: CPU: 3 PID: 478 at drivers/gpu/drm/i915/intel_dram.c:96 skl_dram_get_dimm_info+0x79/0x1b0 [i915] [2.515433] Modules linked in: snd_hda_core kvm_intel snd_hwdep nvidia(PO+) libarc4 kvm joydev soundwire_bus nls_iso8859_1 mei_hdcp intel_rapl_msr i915(+) fjes(-) iwlwifi crct10dif_pclmul ghash_clmulni_intel snd_soc_core drm_kms_helper aesni_intel processor_thermal_device snd_compress cec processor_thermal_rfim ac97_bus crypto_simd snd_pcm_dmaengine rc_core i2c_algo_bit cryptd processor_thermal_mbox fb_sys_fops input_leds mei_me thinkpad_acpi glue_helper syscopyarea intel_cstate nvram efi_pstore sysfillrect snd_seq_midi serio_raw wmi_bmof cfg80211 ee1004 ledtrig_audio snd_pcm processor_thermal_rapl ucsi_acpi(+) sysimgblt snd_seq_midi_event mei intel_rapl_common typec_ucsi intel_soc_dts_iosf snd_rawmidi typec snd_seq snd_seq_device snd_timer snd int3403_thermal soundcore int340x_thermal_zone mac_hid intel_hid int3400_thermal sparse_keymap acpi_thermal_rel acpi_pad acpi_tad sch_fq_codel stp llc ip_vs_wrr ip_vs_sh ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c msr [2.515472] parport_pc ppdev lp drm parport ip_tables x_tables autofs4 crc32_pclmul sdhci_pci psmouse cqhci i2c_i801 i2c_smbus sdhci igc nvme thunderbolt xhci_pci nvme_core xhci_pci_renesas wmi video pinctrl_tigerlake [2.515484] CPU: 3 PID: 478 Comm: systemd-udevd Tainted: P O 5.11.0-37-generic #41-Ubuntu [2.515486] Hardware name: LENOVO 20YUCTO1WW/20YUCTO1WW, BIOS N37ET34W (1.15 ) 09/01/2021 [2.515487] RIP: 0010:skl_dram_get_dimm_info+0x79/0x1b0 [i915] [2.515534] Code: 0f 84 34 01 00 00 41 f7 c0 00 01 00 00 0f 84 27 01 00 00 41 0f b7 d0 48 c7 c6 b1 6b fd c0 48 c7 c7 b5 6b fd c0 e8 07 1e 7c e1 <0f> 0b 44 0f b7 0b b9 01 00 00 00 31 c0 31 f6 88 43 02 41 c1 ff 09 [2.515535] RSP: 0018:be36011b7980 EFLAGS: 00010282 [2.515537] RAX: RBX: be36011b79ec RCX: 9b27574d8ac8 [2.515538] RDX: ffd8 RSI: 0027 RDI: 9b27574d8ac0 [2.515539] RBP: be36011b79a8 R08: R09: be36011b7760 [2.515540] R10: be36011b7758 R11: a37535e8 R12: [2.515541] R13: 004c R14: 9b164558 R15: [2.515542] FS: 7fb8218a08c0() GS:9b27574c() knlGS: [2.515544] CS: 0010 DS: ES: CR0: 80050033 [2.515545] CR2: 7fb8213ae4e0 CR3: 000108a5e006 CR4: 00770ee0 [2.515546] PKRU: 5554 [2.515546] Call Trace: [2.515549] skl_dram_get_channel_info+0x2e/0x150 [i915] [2.515592] skl_dram_get_channels_info+0x6e/0x190 [i915] [2.515634] skl_get_dram_info+0x6e/0x100 [i915] [2.515667] intel_dram_detect+0x3e/0xd0 [i915] [2.515711] i915_driver_hw_probe+0x1cc/0x210 [i915] [2.515748] i915_driver_probe+0xe5/0x2f0 [i915] [2.515781] ? mutex_lock+0x13/0x40 [2.515785] ? acpi_dev_found+0x66/0x70 [2.515788] i915_pci_probe+0x58/0x140 [i915] [2.515822] local_pci_probe+0x48/0x80 [2.515824] pci_call_probe+0x53/0xf0 [2.515826] pci_device_probe+0xad/0xf0 [2.515827] really_probe+0x23a/0x4a0 [2.515830] driver_probe_device+0xe9/0x160 [2.515832] device_driver_attach+0xab/0xb0 [2.515833] __driver_attach+0x8f/0x150 [2.515835] ? device_driver_attach+0xb0/0xb0 [2.515836] bus_for_each_dev+0x7e/0xc0 [2.515837] driver_attach+0x1e/0x20 [2.515839] bus_add_driver+0x135/0x1f0 [2.515840] driver_register+0x95/0xf0 [2.515842] __pci_register_driver+0x54/0x60 [2.515843] i915_init+0x66/0x86 [i915] [2.515877] ? 0xc0c7 [2.515878] do_one_initcall+0x48/0x1d0 [2.515881] ? kmem_cache_alloc_trace+0xf6/0x200 [2.515883] ? do_init_module+0x28/0x290 [2.515886] do_init_module+0x62/0x290 [2.515887] load_module+0x6fd/0x780 [2.515888] __do_sys_finit_module+0xc2/0x120 [2.515890] __x64_sys_finit_module+0x1a/0x20 [2.515891] do_syscall_64+0x38/0x90 [2.515893] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [2.515894] RIP: 0033:0x7fb821d58f6d [2.515896] Code: 28 0d 00 0f 05 eb a9 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d cb de 0c 00 f7 d8 64 89 01 48 [2.515897]
[Kernel-packages] [Bug 1946055] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1946055/+attachment/5530641/+files/acpidump.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/1946055 Title: Ubuntu 21.04 drivers/drm/i915 crashes on my laptop! Status in linux package in Ubuntu: New Bug description: [2.515353] Missing case (val == 65535) [2.515366] WARNING: CPU: 3 PID: 478 at drivers/gpu/drm/i915/intel_dram.c:96 skl_dram_get_dimm_info+0x79/0x1b0 [i915] [2.515433] Modules linked in: snd_hda_core kvm_intel snd_hwdep nvidia(PO+) libarc4 kvm joydev soundwire_bus nls_iso8859_1 mei_hdcp intel_rapl_msr i915(+) fjes(-) iwlwifi crct10dif_pclmul ghash_clmulni_intel snd_soc_core drm_kms_helper aesni_intel processor_thermal_device snd_compress cec processor_thermal_rfim ac97_bus crypto_simd snd_pcm_dmaengine rc_core i2c_algo_bit cryptd processor_thermal_mbox fb_sys_fops input_leds mei_me thinkpad_acpi glue_helper syscopyarea intel_cstate nvram efi_pstore sysfillrect snd_seq_midi serio_raw wmi_bmof cfg80211 ee1004 ledtrig_audio snd_pcm processor_thermal_rapl ucsi_acpi(+) sysimgblt snd_seq_midi_event mei intel_rapl_common typec_ucsi intel_soc_dts_iosf snd_rawmidi typec snd_seq snd_seq_device snd_timer snd int3403_thermal soundcore int340x_thermal_zone mac_hid intel_hid int3400_thermal sparse_keymap acpi_thermal_rel acpi_pad acpi_tad sch_fq_codel stp llc ip_vs_wrr ip_vs_sh ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c msr [2.515472] parport_pc ppdev lp drm parport ip_tables x_tables autofs4 crc32_pclmul sdhci_pci psmouse cqhci i2c_i801 i2c_smbus sdhci igc nvme thunderbolt xhci_pci nvme_core xhci_pci_renesas wmi video pinctrl_tigerlake [2.515484] CPU: 3 PID: 478 Comm: systemd-udevd Tainted: P O 5.11.0-37-generic #41-Ubuntu [2.515486] Hardware name: LENOVO 20YUCTO1WW/20YUCTO1WW, BIOS N37ET34W (1.15 ) 09/01/2021 [2.515487] RIP: 0010:skl_dram_get_dimm_info+0x79/0x1b0 [i915] [2.515534] Code: 0f 84 34 01 00 00 41 f7 c0 00 01 00 00 0f 84 27 01 00 00 41 0f b7 d0 48 c7 c6 b1 6b fd c0 48 c7 c7 b5 6b fd c0 e8 07 1e 7c e1 <0f> 0b 44 0f b7 0b b9 01 00 00 00 31 c0 31 f6 88 43 02 41 c1 ff 09 [2.515535] RSP: 0018:be36011b7980 EFLAGS: 00010282 [2.515537] RAX: RBX: be36011b79ec RCX: 9b27574d8ac8 [2.515538] RDX: ffd8 RSI: 0027 RDI: 9b27574d8ac0 [2.515539] RBP: be36011b79a8 R08: R09: be36011b7760 [2.515540] R10: be36011b7758 R11: a37535e8 R12: [2.515541] R13: 004c R14: 9b164558 R15: [2.515542] FS: 7fb8218a08c0() GS:9b27574c() knlGS: [2.515544] CS: 0010 DS: ES: CR0: 80050033 [2.515545] CR2: 7fb8213ae4e0 CR3: 000108a5e006 CR4: 00770ee0 [2.515546] PKRU: 5554 [2.515546] Call Trace: [2.515549] skl_dram_get_channel_info+0x2e/0x150 [i915] [2.515592] skl_dram_get_channels_info+0x6e/0x190 [i915] [2.515634] skl_get_dram_info+0x6e/0x100 [i915] [2.515667] intel_dram_detect+0x3e/0xd0 [i915] [2.515711] i915_driver_hw_probe+0x1cc/0x210 [i915] [2.515748] i915_driver_probe+0xe5/0x2f0 [i915] [2.515781] ? mutex_lock+0x13/0x40 [2.515785] ? acpi_dev_found+0x66/0x70 [2.515788] i915_pci_probe+0x58/0x140 [i915] [2.515822] local_pci_probe+0x48/0x80 [2.515824] pci_call_probe+0x53/0xf0 [2.515826] pci_device_probe+0xad/0xf0 [2.515827] really_probe+0x23a/0x4a0 [2.515830] driver_probe_device+0xe9/0x160 [2.515832] device_driver_attach+0xab/0xb0 [2.515833] __driver_attach+0x8f/0x150 [2.515835] ? device_driver_attach+0xb0/0xb0 [2.515836] bus_for_each_dev+0x7e/0xc0 [2.515837] driver_attach+0x1e/0x20 [2.515839] bus_add_driver+0x135/0x1f0 [2.515840] driver_register+0x95/0xf0 [2.515842] __pci_register_driver+0x54/0x60 [2.515843] i915_init+0x66/0x86 [i915] [2.515877] ? 0xc0c7 [2.515878] do_one_initcall+0x48/0x1d0 [2.515881] ? kmem_cache_alloc_trace+0xf6/0x200 [2.515883] ? do_init_module+0x28/0x290 [2.515886] do_init_module+0x62/0x290 [2.515887] load_module+0x6fd/0x780 [2.515888] __do_sys_finit_module+0xc2/0x120 [2.515890] __x64_sys_finit_module+0x1a/0x20 [2.515891] do_syscall_64+0x38/0x90 [2.515893] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [2.515894] RIP: 0033:0x7fb821d58f6d [2.515896] Code: 28 0d 00 0f 05 eb a9 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d cb de 0c 00 f7 d8 64 89 01 48 [2.515897] RSP:
[Kernel-packages] [Bug 1946055] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1946055/+attachment/5530639/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946055 Title: Ubuntu 21.04 drivers/drm/i915 crashes on my laptop! Status in linux package in Ubuntu: New Bug description: [2.515353] Missing case (val == 65535) [2.515366] WARNING: CPU: 3 PID: 478 at drivers/gpu/drm/i915/intel_dram.c:96 skl_dram_get_dimm_info+0x79/0x1b0 [i915] [2.515433] Modules linked in: snd_hda_core kvm_intel snd_hwdep nvidia(PO+) libarc4 kvm joydev soundwire_bus nls_iso8859_1 mei_hdcp intel_rapl_msr i915(+) fjes(-) iwlwifi crct10dif_pclmul ghash_clmulni_intel snd_soc_core drm_kms_helper aesni_intel processor_thermal_device snd_compress cec processor_thermal_rfim ac97_bus crypto_simd snd_pcm_dmaengine rc_core i2c_algo_bit cryptd processor_thermal_mbox fb_sys_fops input_leds mei_me thinkpad_acpi glue_helper syscopyarea intel_cstate nvram efi_pstore sysfillrect snd_seq_midi serio_raw wmi_bmof cfg80211 ee1004 ledtrig_audio snd_pcm processor_thermal_rapl ucsi_acpi(+) sysimgblt snd_seq_midi_event mei intel_rapl_common typec_ucsi intel_soc_dts_iosf snd_rawmidi typec snd_seq snd_seq_device snd_timer snd int3403_thermal soundcore int340x_thermal_zone mac_hid intel_hid int3400_thermal sparse_keymap acpi_thermal_rel acpi_pad acpi_tad sch_fq_codel stp llc ip_vs_wrr ip_vs_sh ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c msr [2.515472] parport_pc ppdev lp drm parport ip_tables x_tables autofs4 crc32_pclmul sdhci_pci psmouse cqhci i2c_i801 i2c_smbus sdhci igc nvme thunderbolt xhci_pci nvme_core xhci_pci_renesas wmi video pinctrl_tigerlake [2.515484] CPU: 3 PID: 478 Comm: systemd-udevd Tainted: P O 5.11.0-37-generic #41-Ubuntu [2.515486] Hardware name: LENOVO 20YUCTO1WW/20YUCTO1WW, BIOS N37ET34W (1.15 ) 09/01/2021 [2.515487] RIP: 0010:skl_dram_get_dimm_info+0x79/0x1b0 [i915] [2.515534] Code: 0f 84 34 01 00 00 41 f7 c0 00 01 00 00 0f 84 27 01 00 00 41 0f b7 d0 48 c7 c6 b1 6b fd c0 48 c7 c7 b5 6b fd c0 e8 07 1e 7c e1 <0f> 0b 44 0f b7 0b b9 01 00 00 00 31 c0 31 f6 88 43 02 41 c1 ff 09 [2.515535] RSP: 0018:be36011b7980 EFLAGS: 00010282 [2.515537] RAX: RBX: be36011b79ec RCX: 9b27574d8ac8 [2.515538] RDX: ffd8 RSI: 0027 RDI: 9b27574d8ac0 [2.515539] RBP: be36011b79a8 R08: R09: be36011b7760 [2.515540] R10: be36011b7758 R11: a37535e8 R12: [2.515541] R13: 004c R14: 9b164558 R15: [2.515542] FS: 7fb8218a08c0() GS:9b27574c() knlGS: [2.515544] CS: 0010 DS: ES: CR0: 80050033 [2.515545] CR2: 7fb8213ae4e0 CR3: 000108a5e006 CR4: 00770ee0 [2.515546] PKRU: 5554 [2.515546] Call Trace: [2.515549] skl_dram_get_channel_info+0x2e/0x150 [i915] [2.515592] skl_dram_get_channels_info+0x6e/0x190 [i915] [2.515634] skl_get_dram_info+0x6e/0x100 [i915] [2.515667] intel_dram_detect+0x3e/0xd0 [i915] [2.515711] i915_driver_hw_probe+0x1cc/0x210 [i915] [2.515748] i915_driver_probe+0xe5/0x2f0 [i915] [2.515781] ? mutex_lock+0x13/0x40 [2.515785] ? acpi_dev_found+0x66/0x70 [2.515788] i915_pci_probe+0x58/0x140 [i915] [2.515822] local_pci_probe+0x48/0x80 [2.515824] pci_call_probe+0x53/0xf0 [2.515826] pci_device_probe+0xad/0xf0 [2.515827] really_probe+0x23a/0x4a0 [2.515830] driver_probe_device+0xe9/0x160 [2.515832] device_driver_attach+0xab/0xb0 [2.515833] __driver_attach+0x8f/0x150 [2.515835] ? device_driver_attach+0xb0/0xb0 [2.515836] bus_for_each_dev+0x7e/0xc0 [2.515837] driver_attach+0x1e/0x20 [2.515839] bus_add_driver+0x135/0x1f0 [2.515840] driver_register+0x95/0xf0 [2.515842] __pci_register_driver+0x54/0x60 [2.515843] i915_init+0x66/0x86 [i915] [2.515877] ? 0xc0c7 [2.515878] do_one_initcall+0x48/0x1d0 [2.515881] ? kmem_cache_alloc_trace+0xf6/0x200 [2.515883] ? do_init_module+0x28/0x290 [2.515886] do_init_module+0x62/0x290 [2.515887] load_module+0x6fd/0x780 [2.515888] __do_sys_finit_module+0xc2/0x120 [2.515890] __x64_sys_finit_module+0x1a/0x20 [2.515891] do_syscall_64+0x38/0x90 [2.515893] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [2.515894] RIP: 0033:0x7fb821d58f6d [2.515896] Code: 28 0d 00 0f 05 eb a9 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d cb de 0c 00 f7 d8 64 89 01 48 [2.515897] RSP:
