[Kernel-packages] [Bug 1987618] Re: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways
The patch highlighted in #5 does not fix this issue for me without other patches from the refactor, so it may be we need to wait for the 5.19 hwe kernel to arrive to fix this issue. ** Changed in: linux (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987618 Title: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways Status in linux package in Ubuntu: Incomplete Bug description: Charmed OpenStack on Jammy. Hardware offloaded instances that reside on the hypervisor which is also the active OVN gateway for their network have degraded connectivity. $ time wget --debug -O /dev/null http://nova.clouds.archive.ubuntu.com/ubuntu/ Setting --output-document (outputdocument) to /dev/null DEBUG output created by Wget 1.21.2 on linux-gnu. Reading HSTS entries from /home/ubuntu/.wget-hsts URI encoding = ‘UTF-8’ --2022-08-25 07:16:54-- http://nova.clouds.archive.ubuntu.com/ubuntu/ Resolving nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)... 91.189.91.121, 185.125.190.38, 185.125.190.41, ... Caching nova.clouds.archive.ubuntu.com => 91.189.91.121 185.125.190.38 185.125.190.41 91.189.91.122 2001:67c:1562::29 2620:2d:4000:1::1b 2620:2d:4000:1::18 2001:67c:1562::26 Connecting to nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)|91.189.91.121|:80... connected. Created socket 4. Releasing 0x55ef05654490 (new refcount 1). ---request begin--- GET /ubuntu/ HTTP/1.1 Host: nova.clouds.archive.ubuntu.com User-Agent: Wget/1.21.2 Accept: */* Accept-Encoding: identity Connection: Keep-Alive ---request end--- HTTP request sent, awaiting response... ---response begin--- HTTP/1.1 200 OK Date: Thu, 25 Aug 2022 07:16:54 GMT Server: Apache/2.4.29 (Ubuntu) Vary: Accept-Encoding Content-Length: 1779 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: text/html;charset=UTF-8 ---response end--- 200 OK Registered socket 4 for persistent reuse. URI content encoding = ‘UTF-8’ Length: 1779 (1.7K) [text/html] Saving to: ‘/dev/null’ /dev/null 100%[>] 1.74K --.-KB/sin 0.07s 2022-08-25 07:16:59 (24.3 KB/s) - ‘/dev/null’ saved [1779/1779] real 0m5.591s user 0m0.000s sys 0m0.005s $ sudo tcpdump -nevi ens3 not port 22 07:16:54.017265 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 50207, offset 0, flags [DF], proto TCP (6), length 60) 10.42.1.8.43060 > 91.189.91.121.80: Flags [S], cksum 0xc296 (incorrect -> 0x4190), seq 2905559525, win 62314, options [mss 8902,sackOK,TS val 4081686695 ecr 0,nop,wscale 7], length 0 07:16:54.091378 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto TCP (6), length 60) 91.189.91.121.80 > 10.42.1.8.43060: Flags [S.], cksum 0x809d (correct), seq 3404088064, ack 2905559526, win 65160, options [mss 1460,sackOK,TS val 932285789 ecr 4081686695,nop,wscale 7], length 0 07:16:54.091402 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 64, id 50208, offset 0, flags [DF], proto TCP (6), length 52) 10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc28e (incorrect -> 0xabc0), ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], length 0 07:16:54.091512 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 218: (tos 0x0, ttl 64, id 50209, offset 0, flags [DF], proto TCP (6), length 204) 10.42.1.8.43060 > 91.189.91.121.80: Flags [P.], cksum 0xc326 (incorrect -> 0x7d0c), seq 1:153, ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], length 152: HTTP, length: 152 GET /ubuntu/ HTTP/1.1 Host: nova.clouds.archive.ubuntu.com User-Agent: Wget/1.21.2 Accept: */* Accept-Encoding: identity Connection: Keep-Alive 07:16:54.166170 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 58, id 15660, offset 0, flags [DF], proto TCP (6), length 52) 91.189.91.121.80 > 10.42.1.8.43060: Flags [.], cksum 0xaac7 (correct), ack 153, win 508, options [nop,nop,TS val 932285865 ecr 4081686770], length 0 07:16:59.171924 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 58, id 15669, offset 0, flags [DF], proto TCP (6), length 52) 91.189.91.121.80 > 10.42.1.8.43060: Flags [F.], cksum 0x8f61 (correct), seq 2008, ack 153, win 508, options [nop,nop,TS val 932290871 ecr 4081686770], length 0 07:16:59.171956 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 78
[Kernel-packages] [Bug 1987618] Re: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987618 Title: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways Status in linux package in Ubuntu: Expired Bug description: Charmed OpenStack on Jammy. Hardware offloaded instances that reside on the hypervisor which is also the active OVN gateway for their network have degraded connectivity. $ time wget --debug -O /dev/null http://nova.clouds.archive.ubuntu.com/ubuntu/ Setting --output-document (outputdocument) to /dev/null DEBUG output created by Wget 1.21.2 on linux-gnu. Reading HSTS entries from /home/ubuntu/.wget-hsts URI encoding = ‘UTF-8’ --2022-08-25 07:16:54-- http://nova.clouds.archive.ubuntu.com/ubuntu/ Resolving nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)... 91.189.91.121, 185.125.190.38, 185.125.190.41, ... Caching nova.clouds.archive.ubuntu.com => 91.189.91.121 185.125.190.38 185.125.190.41 91.189.91.122 2001:67c:1562::29 2620:2d:4000:1::1b 2620:2d:4000:1::18 2001:67c:1562::26 Connecting to nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)|91.189.91.121|:80... connected. Created socket 4. Releasing 0x55ef05654490 (new refcount 1). ---request begin--- GET /ubuntu/ HTTP/1.1 Host: nova.clouds.archive.ubuntu.com User-Agent: Wget/1.21.2 Accept: */* Accept-Encoding: identity Connection: Keep-Alive ---request end--- HTTP request sent, awaiting response... ---response begin--- HTTP/1.1 200 OK Date: Thu, 25 Aug 2022 07:16:54 GMT Server: Apache/2.4.29 (Ubuntu) Vary: Accept-Encoding Content-Length: 1779 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: text/html;charset=UTF-8 ---response end--- 200 OK Registered socket 4 for persistent reuse. URI content encoding = ‘UTF-8’ Length: 1779 (1.7K) [text/html] Saving to: ‘/dev/null’ /dev/null 100%[>] 1.74K --.-KB/sin 0.07s 2022-08-25 07:16:59 (24.3 KB/s) - ‘/dev/null’ saved [1779/1779] real 0m5.591s user 0m0.000s sys 0m0.005s $ sudo tcpdump -nevi ens3 not port 22 07:16:54.017265 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 50207, offset 0, flags [DF], proto TCP (6), length 60) 10.42.1.8.43060 > 91.189.91.121.80: Flags [S], cksum 0xc296 (incorrect -> 0x4190), seq 2905559525, win 62314, options [mss 8902,sackOK,TS val 4081686695 ecr 0,nop,wscale 7], length 0 07:16:54.091378 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto TCP (6), length 60) 91.189.91.121.80 > 10.42.1.8.43060: Flags [S.], cksum 0x809d (correct), seq 3404088064, ack 2905559526, win 65160, options [mss 1460,sackOK,TS val 932285789 ecr 4081686695,nop,wscale 7], length 0 07:16:54.091402 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 64, id 50208, offset 0, flags [DF], proto TCP (6), length 52) 10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc28e (incorrect -> 0xabc0), ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], length 0 07:16:54.091512 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 218: (tos 0x0, ttl 64, id 50209, offset 0, flags [DF], proto TCP (6), length 204) 10.42.1.8.43060 > 91.189.91.121.80: Flags [P.], cksum 0xc326 (incorrect -> 0x7d0c), seq 1:153, ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], length 152: HTTP, length: 152 GET /ubuntu/ HTTP/1.1 Host: nova.clouds.archive.ubuntu.com User-Agent: Wget/1.21.2 Accept: */* Accept-Encoding: identity Connection: Keep-Alive 07:16:54.166170 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 58, id 15660, offset 0, flags [DF], proto TCP (6), length 52) 91.189.91.121.80 > 10.42.1.8.43060: Flags [.], cksum 0xaac7 (correct), ack 153, win 508, options [nop,nop,TS val 932285865 ecr 4081686770], length 0 07:16:59.171924 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 58, id 15669, offset 0, flags [DF], proto TCP (6), length 52) 91.189.91.121.80 > 10.42.1.8.43060: Flags [F.], cksum 0x8f61 (correct), seq 2008, ack 153, win 508, options [nop,nop,TS val 932290871 ecr 4081686770], length 0 07:16:59.171956 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 78: (tos 0x0, ttl 64, id 50210, offset 0, flags [DF], proto TCP (6), length 64) 10.42.1.8.43060 > 91.18
[Kernel-packages] [Bug 1996250] [NEW] OEM machine can't install newer version of Nvidia-driver by ubuntu-drivers install
Public bug reported: During the SRU testing, I found a dependency issue when running "ubuntu-drivers install". Although OEM image has preloaded nvidia driver already, but when user want to install newer version of nvidia driver will hit this issue. Using 202002-27718 as an example, after installing oem image, I ran "ubuntu-drivers install" then I saw following message. This not only happens on 202002-27718, I checked few oem machines, all have this issue. ubuntu-drivers autoinstall WARNING:root:_pkg_get_support nvidia-driver-515-server: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-515: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-510: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-510-server: package has invalid Support PBheader, cannot determine support level Reading package lists... 0% Reading package lists... 100% Reading package lists... Done Building dependency tree... 0% Building dependency tree... 0% Building dependency tree... 50% Building dependency tree... 50% Building dependency tree Reading state information... 0% Reading state information... 0% Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: nvidia-driver-520 : Depends: libnvidia-gl-520 (= 520.56.06-0ubuntu0.20.04.1) but it is not going to be installed Depends: libnvidia-compute-520 (= 520.56.06-0ubuntu0.20.04.1) but it is not going to be installed Depends: libnvidia-extra-520 (= 520.56.06-0ubuntu0.20.04.1) but it is not going to be installed Depends: nvidia-compute-utils-520 (= 520.56.06-0ubuntu0.20.04.1) but it is not going to be installed Depends: libnvidia-decode-520 (= 520.56.06-0ubuntu0.20.04.1) but it is not going to be installed Depends: libnvidia-encode-520 (= 520.56.06-0ubuntu0.20.04.1) but it is not going to be installed Depends: nvidia-utils-520 (= 520.56.06-0ubuntu0.20.04.1) but it is not going to be installed Depends: xserver-xorg-video-nvidia-520 (= 520.56.06-0ubuntu0.20.04.1) but it is not going to be installed Depends: libnvidia-cfg1-520 (= 520.56.06-0ubuntu0.20.04.1) but it is not going to be installed Depends: libnvidia-fbc1-520 (= 520.56.06-0ubuntu0.20.04.1) but it is not going to be installed Recommends: libnvidia-compute-520:i386 (= 520.56.06-0ubuntu0.20.04.1) Recommends: libnvidia-decode-520:i386 (= 520.56.06-0ubuntu0.20.04.1) Recommends: libnvidia-encode-520:i386 (= 520.56.06-0ubuntu0.20.04.1) Recommends: libnvidia-fbc1-520:i386 (= 520.56.06-0ubuntu0.20.04.1) Recommends: libnvidia-gl-520:i386 (= 520.56.06-0ubuntu0.20.04.1) E: Unable to correct problems, you have held broken packages. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Tags: cert-sru oem-priority ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996250 Title: OEM machine can't install newer version of Nvidia-driver by ubuntu- drivers install Status in ubuntu-drivers-common package in Ubuntu: New Bug description: During the SRU testing, I found a dependency issue when running "ubuntu-drivers install". Although OEM image has preloaded nvidia driver already, but when user want to install newer version of nvidia driver will hit this issue. Using 202002-27718 as an example, after installing oem image, I ran "ubuntu-drivers install" then I saw following message. This not only happens on 202002-27718, I checked few oem machines, all have this issue. ubuntu-drivers autoinstall WARNING:root:_pkg_get_support nvidia-driver-515-server: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-515: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-510: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-510-server: package has invalid Support PBheader, cannot determine support level Reading package lists... 0% Reading pac
[Kernel-packages] [Bug 1995894] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1995894 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995894 Title: no HDMI sound output in 22.10 (works in 22.04.1 and kernel-6.1rc3) Status in linux package in Ubuntu: Incomplete Bug description: There is no sound output via HDMI on 22.10. It worked in 22.04.1 and it works in 22.10 when I installed kernel 6.1rc3. I think it has to do with the snd_hda_intel driver not attaching to Device-1: AMD Kabini HDMI/DP. Doesn't work on 22.10: # inxi -SMA System: Host: lubuntu Kernel: 5.19.0-21-generic arch: x86_64 bits: 64 Desktop: LXQt v: 1.1.0 Distro: Ubuntu 22.10 (Kinetic Kudu) Machine: Type: Desktop Mobo: Acer model: Aspire TC-281 serial: DBE0E110018010680230A1 UEFI: American Megatrends v: R01-A2 date: 07/18/2017 Audio: Device-1: AMD Kabini HDMI/DP Audio driver: N/A Device-2: AMD Family 15h Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.19.0-21-generic running: yes Sound Server-2: PulseAudio v: 16.1 running: yes Works on 22.04.1: # inxi -SMA System: Host: lubuntu Kernel: 5.15.0-43-generic x86_64 bits: 64 Desktop: LXQt 0.17.1 Distro: Ubuntu 22.04.1 LTS (Jammy Jellyfish) Machine: Type: Desktop Mobo: Acer model: Aspire TC-281 serial: DBE0E110018010680230A1 UEFI: American Megatrends v: R01-A2 date: 07/18/2017 Audio: Device-1: AMD Kabini HDMI/DP Audio driver: snd_hda_intel Device-2: AMD Family 15h Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.15.0-43-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Works on 22.10 with kernel-6.1rc3: # inxi -SMA System: Host: me-aspiretc281 Kernel: 6.1.0-060100rc3-generic arch: x86_64 bits: 64 Desktop: LXQt v: 1.1.0 Distro: Ubuntu 22.10 (Kinetic Kudu) Machine: Type: Desktop Mobo: Acer model: Aspire TC-281 serial: DBE0E110018010680230A1 UEFI: American Megatrends v: R01-A2 date: 07/18/2017 Audio: Device-1: AMD Kabini HDMI/DP Audio driver: snd_hda_intel Device-2: AMD Family 15h Audio driver: snd_hda_intel Sound Server-1: ALSA v: k6.1.0-060100rc3-generic running: yes Sound Server-2: PulseAudio v: 16.1 running: yes Sound Server-3: PipeWire v: 0.3.58 running: yes ubuntu-bug thinks pulse-audio crashed but I don't know if that is correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995894/+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 1992468] Re: segfault in ld-linux-x86-64.so
The change to omit DT_HASH was only in 2.36 and so was only present in kinetic/22.10, and then only briefly as we patched it before release. I doubt it's that. Have you reported this upstream at https://sourceware.org/bugzilla/ ? Have you tried building glibc 2.35 from source? (would be interesting to know if this is the fault of Ubuntu patches, although that seems unlikely tbh). -- 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/1992468 Title: segfault in ld-linux-x86-64.so Status in linux package in Ubuntu: Incomplete Bug description: My manually built elf x64 file has started crashing on load, within the last month or so. It worked fine on Ubuntu 20.04.x, but fails on 22.04 - same problem on Mint 19.3 and Fedora 36. dmesg ... gives this: [ 107.121214] p[4370]: segfault at 0 ip 7f3d725b8350 sp 7ffea111fba0 error 4 in ld-linux-x86-64.so.2[7f3d72598000+2a000] [ 107.121230] Code: ff ff 00 45 31 db 48 8d 15 c9 ac 00 00 4c 8d 05 46 8f 01 00 4c 8d 2d 1f 8f 01 00 49 89 c2 48 8d 58 ff 48 89 f8 49 f7 da 66 90 <8b> 08 83 f9 07 77 19 85 c9 74 45 83 f9 07 77 40 48 63 0c 8a 48 01 You can download the offending file (a single plain 4MB ELF x64) from http://phix.x10.mx/p64 It almost certainly contains older/rarer forms of relocations and suchlike, but only about ten or so and meant to be as simple as possible. If I need to change the binary content of that file, I can, but might need a wee bit of help. Of course, if/once it gets through ld-linux-x86-64.so and complains about something else, ignore it, or should you be at all intrigued you can visit http://phix.x10.mx/download.php to get the full package. References, just in case you need them, or to ask a wider set than just me for more details direct: https://openeuphoria.org/forum/136972.wc?last_id=136973 https://github.com/petelomax/Phix/issues/13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992468/+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 1995894] Re: no HDMI sound output in 22.10 (works in 22.04.1 and kernel-6.1rc3)
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995894 Title: no HDMI sound output in 22.10 (works in 22.04.1 and kernel-6.1rc3) Status in linux package in Ubuntu: New Bug description: There is no sound output via HDMI on 22.10. It worked in 22.04.1 and it works in 22.10 when I installed kernel 6.1rc3. I think it has to do with the snd_hda_intel driver not attaching to Device-1: AMD Kabini HDMI/DP. Doesn't work on 22.10: # inxi -SMA System: Host: lubuntu Kernel: 5.19.0-21-generic arch: x86_64 bits: 64 Desktop: LXQt v: 1.1.0 Distro: Ubuntu 22.10 (Kinetic Kudu) Machine: Type: Desktop Mobo: Acer model: Aspire TC-281 serial: DBE0E110018010680230A1 UEFI: American Megatrends v: R01-A2 date: 07/18/2017 Audio: Device-1: AMD Kabini HDMI/DP Audio driver: N/A Device-2: AMD Family 15h Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.19.0-21-generic running: yes Sound Server-2: PulseAudio v: 16.1 running: yes Works on 22.04.1: # inxi -SMA System: Host: lubuntu Kernel: 5.15.0-43-generic x86_64 bits: 64 Desktop: LXQt 0.17.1 Distro: Ubuntu 22.04.1 LTS (Jammy Jellyfish) Machine: Type: Desktop Mobo: Acer model: Aspire TC-281 serial: DBE0E110018010680230A1 UEFI: American Megatrends v: R01-A2 date: 07/18/2017 Audio: Device-1: AMD Kabini HDMI/DP Audio driver: snd_hda_intel Device-2: AMD Family 15h Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.15.0-43-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Works on 22.10 with kernel-6.1rc3: # inxi -SMA System: Host: me-aspiretc281 Kernel: 6.1.0-060100rc3-generic arch: x86_64 bits: 64 Desktop: LXQt v: 1.1.0 Distro: Ubuntu 22.10 (Kinetic Kudu) Machine: Type: Desktop Mobo: Acer model: Aspire TC-281 serial: DBE0E110018010680230A1 UEFI: American Megatrends v: R01-A2 date: 07/18/2017 Audio: Device-1: AMD Kabini HDMI/DP Audio driver: snd_hda_intel Device-2: AMD Family 15h Audio driver: snd_hda_intel Sound Server-1: ALSA v: k6.1.0-060100rc3-generic running: yes Sound Server-2: PulseAudio v: 16.1 running: yes Sound Server-3: PipeWire v: 0.3.58 running: yes ubuntu-bug thinks pulse-audio crashed but I don't know if that is correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995894/+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 1995894] [NEW] no HDMI sound output in 22.10 (works in 22.04.1 and kernel-6.1rc3)
You have been subscribed to a public bug: There is no sound output via HDMI on 22.10. It worked in 22.04.1 and it works in 22.10 when I installed kernel 6.1rc3. I think it has to do with the snd_hda_intel driver not attaching to Device-1: AMD Kabini HDMI/DP. Doesn't work on 22.10: # inxi -SMA System: Host: lubuntu Kernel: 5.19.0-21-generic arch: x86_64 bits: 64 Desktop: LXQt v: 1.1.0 Distro: Ubuntu 22.10 (Kinetic Kudu) Machine: Type: Desktop Mobo: Acer model: Aspire TC-281 serial: DBE0E110018010680230A1 UEFI: American Megatrends v: R01-A2 date: 07/18/2017 Audio: Device-1: AMD Kabini HDMI/DP Audio driver: N/A Device-2: AMD Family 15h Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.19.0-21-generic running: yes Sound Server-2: PulseAudio v: 16.1 running: yes Works on 22.04.1: # inxi -SMA System: Host: lubuntu Kernel: 5.15.0-43-generic x86_64 bits: 64 Desktop: LXQt 0.17.1 Distro: Ubuntu 22.04.1 LTS (Jammy Jellyfish) Machine: Type: Desktop Mobo: Acer model: Aspire TC-281 serial: DBE0E110018010680230A1 UEFI: American Megatrends v: R01-A2 date: 07/18/2017 Audio: Device-1: AMD Kabini HDMI/DP Audio driver: snd_hda_intel Device-2: AMD Family 15h Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.15.0-43-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Works on 22.10 with kernel-6.1rc3: # inxi -SMA System: Host: me-aspiretc281 Kernel: 6.1.0-060100rc3-generic arch: x86_64 bits: 64 Desktop: LXQt v: 1.1.0 Distro: Ubuntu 22.10 (Kinetic Kudu) Machine: Type: Desktop Mobo: Acer model: Aspire TC-281 serial: DBE0E110018010680230A1 UEFI: American Megatrends v: R01-A2 date: 07/18/2017 Audio: Device-1: AMD Kabini HDMI/DP Audio driver: snd_hda_intel Device-2: AMD Family 15h Audio driver: snd_hda_intel Sound Server-1: ALSA v: k6.1.0-060100rc3-generic running: yes Sound Server-2: PulseAudio v: 16.1 running: yes Sound Server-3: PipeWire v: 0.3.58 running: yes ubuntu-bug thinks pulse-audio crashed but I don't know if that is correct. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- no HDMI sound output in 22.10 (works in 22.04.1 and kernel-6.1rc3) https://bugs.launchpad.net/bugs/1995894 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Hi jhubuntu20, First, hopefully I can do you a solid and tell you how I fixed my brightness control at least (cause mine is a Galaxy Book2 Pro also, but with the ARC graphics). What worked for me was: -Created /etc/modprobe.d/i915.conf with options i915 enable_dpcd_backlight=3 - Regenerated the initramfs: sudo update-initramfs -u -k all Hope that helps, unless you already tried. On my side, I am running kernel 6.0.0-1006-oem (which I got from the linux-oem-22.04b package, as opposed to the mainline tool, which i may try though). I tried that in hopes it would help, in addition to many other things (disabling windows fast boot on my other drive, disabling secure boot and fast bios, setting probe_mask=1, iommu=off, and others). Also tried playing with hdajackretask, because I'd be happy with retasking / giving up my working headphone jack for the speakers, but haven't figured that out. Also, when I tried your TO912.sh script (the first thing I tried actually), I was doing it following the instructions here -- https://forum.manjaro.org/t/howto-set-up-the-audio-card-in-samsung-galaxy-book/37090 This includes also blacklisting snd-hda-intel, removing alsa-conf, plus more. Should I not be doing that? (I've tried both ways though). The problem is I just don't have the right mental model for what's going on, so trying everything too blindly... but I'm trying to understand more. Most things have no effect (i.e., headphones work, speakers don't). However, the one tweak that has made the most effect is: options snd-intel-dspcfg dsp_driver=## - When I set this to "3", or leave the setting out (i.e., as it was on fresh install), alsamixer shows "sof-hda-dsp" for "Card" and "Realtek ALC298" for "Chip". When I use hdajackretask, it hangs completely when applying the retasking (and I've stopped pulseaudio, etc.), and the machine will hang on next shutdown. - But if I set it to "1", alsamixer then shows "HDA Intel PCH" for "Card", and still "Realtek..." for chip. I can use hdajackretask without it hanging up. And when I plug in headphones, I see a new "Headset or Headphone" GUI popup. But my mic doesn't look like it's working. (Also, I need to not blacklist snd-hda-intel for this config to work, otherwise I only have "Dummy Output") Do you happen to know which of those situations seems "more right"? I fear that there's more than one problem going on at once, and I wonder which setting (3 vs 1) I should use as I experiment with the other possibilities (your script, etc.) Lastly, I notice if I look in alsa-info, its reporting "line_outs=1", but "speaker_outs=0" in almost all configurations, and its not binding either line_out or speaker to anything in "/devices" (though it is binding the HDMIs, headphone, and sometimes the Mic). I checked my older laptop, however, which has speaker sound, and it reports the same (though its running a 4.xx kernel and the ALC256). I don't know if any of this gives any clues, and I apologize for my posts length and poor formatting.. I'm just trying to make sense of all this. -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in Linux: New Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system
[Kernel-packages] [Bug 1992468] Re: segfault in ld-linux-x86-64.so
Am now convinced, albeit without much in the way of concrete evidence, this is the missing DT_HASH (in libc.so.6 and libdl.so.2) issue, not that I've yet tried to create a DT_GNU_HASH replacment yet. See (eg) https://src.fedoraproject.org/rpms/glibc/c/1cd731cf293a236f70ed6d54ff711d6a1342a3d3?branch=rawhide -- 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/1992468 Title: segfault in ld-linux-x86-64.so Status in linux package in Ubuntu: Incomplete Bug description: My manually built elf x64 file has started crashing on load, within the last month or so. It worked fine on Ubuntu 20.04.x, but fails on 22.04 - same problem on Mint 19.3 and Fedora 36. dmesg ... gives this: [ 107.121214] p[4370]: segfault at 0 ip 7f3d725b8350 sp 7ffea111fba0 error 4 in ld-linux-x86-64.so.2[7f3d72598000+2a000] [ 107.121230] Code: ff ff 00 45 31 db 48 8d 15 c9 ac 00 00 4c 8d 05 46 8f 01 00 4c 8d 2d 1f 8f 01 00 49 89 c2 48 8d 58 ff 48 89 f8 49 f7 da 66 90 <8b> 08 83 f9 07 77 19 85 c9 74 45 83 f9 07 77 40 48 63 0c 8a 48 01 You can download the offending file (a single plain 4MB ELF x64) from http://phix.x10.mx/p64 It almost certainly contains older/rarer forms of relocations and suchlike, but only about ten or so and meant to be as simple as possible. If I need to change the binary content of that file, I can, but might need a wee bit of help. Of course, if/once it gets through ld-linux-x86-64.so and complains about something else, ignore it, or should you be at all intrigued you can visit http://phix.x10.mx/download.php to get the full package. References, just in case you need them, or to ask a wider set than just me for more details direct: https://openeuphoria.org/forum/136972.wc?last_id=136973 https://github.com/petelomax/Phix/issues/13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992468/+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 1996208] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1996208 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996208 Title: kernel: nvme nvme0: failed to set APST feature (2) Status in linux package in Ubuntu: Incomplete Bug description: always my computer on show me this error: kernel: nvme nvme0: failed to set APST feature (2) this error start with update kernel 5.15.0-52 well i check the logs and saw this: kernel: nvme nvme0: failed to set APST feature (2) [7.163360] kernel: nvme nvme0: allocated 64 MiB host memory buffer. [7.184123] kernel: nvme nvme0: 4/0/0 default/read/poll queues [7.201139] kernel: nvme0n1: p1 p2 [7.268310] kernel: usb 1-3: new full-speed USB device number 2 using xhci_h> [7.311210] kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [7.311225] kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [7.311239] kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [7.311251] kernel: ata4: SATA link down (SStatus 4 SControl 300) [7.311264] kernel: ata6: SATA link down (SStatus 4 SControl 300) [7.311278] kernel: ata3: SATA link down (SStatus 4 SControl 300) [7.312183] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.312217] kernel: [7.312218] kernel: No Local Variables are initialized for Method [_GTF] [7.312219] kernel: [7.312220] kernel: No Arguments are initialized for method [_GTF] [7.312221] kernel: 7.31] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due> [7.312325] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.312357] kernel: [7.312359] kernel: No Local Variables are initialized for Method [_GTF] [7.312359] kernel: [7.312360] kernel: No Arguments are initialized for method [_GTF] [7.312361] kernel: [7.312362] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due> [7.312399] kernel: ata5.00: ATA-10: CT240BX500SSD1, M6CR054, max UDMA/133 [7.312420] kernel: ata1.00: ATA-8: Hitachi HTS542525K9SA00, BBFOC31P, max U> [7.312699] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.312731] kernel: [7.312732] kernel: No Local Variables are initialized for Method [_GTF] [7.312733] kernel: [7.312734] kernel: No Arguments are initialized for method [_GTF] 7.312736] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due> [7.312768] kernel: ata2.00: ATA-9: HGST HTS541010A9E680, JA0OA710, max UDMA> [7.313013] kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth > [7.313420] kernel: ata5.00: 468862128 sectors, multi 1: LBA48 NCQ (depth 32> [7.314598] kernel: ata1.00: ATA Identify Device Log not supported [7.314601] kernel: ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 3> [7.314706] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.314738] kernel: [7.314740] kernel: No Local Variables are initialized for Method [_GTF] [7.314740] kernel: [7.314741] kernel: No Arguments are initialized for method [_GTF] [7.314742] kernel: [7.314743] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due> [7.315039] kernel: ata2.00: configured for UDMA/133 [7.315707] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.315740] kernel: [7.315741] kernel: No Local Variables are initialized for Method [_GTF] [7.315742] kernel: [7.315742] kernel: No Arguments are initialized for method [_GTF] [7.315743] kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996208/+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 1996208] Re: kernel: nvme nvme0: failed to set APST feature (2)
** Package changed: ubuntu => linux (Ubuntu) ** Tags removed: 22.04 bug lts ** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996208 Title: kernel: nvme nvme0: failed to set APST feature (2) Status in linux package in Ubuntu: New Bug description: always my computer on show me this error: kernel: nvme nvme0: failed to set APST feature (2) this error start with update kernel 5.15.0-52 well i check the logs and saw this: kernel: nvme nvme0: failed to set APST feature (2) [7.163360] kernel: nvme nvme0: allocated 64 MiB host memory buffer. [7.184123] kernel: nvme nvme0: 4/0/0 default/read/poll queues [7.201139] kernel: nvme0n1: p1 p2 [7.268310] kernel: usb 1-3: new full-speed USB device number 2 using xhci_h> [7.311210] kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [7.311225] kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [7.311239] kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [7.311251] kernel: ata4: SATA link down (SStatus 4 SControl 300) [7.311264] kernel: ata6: SATA link down (SStatus 4 SControl 300) [7.311278] kernel: ata3: SATA link down (SStatus 4 SControl 300) [7.312183] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.312217] kernel: [7.312218] kernel: No Local Variables are initialized for Method [_GTF] [7.312219] kernel: [7.312220] kernel: No Arguments are initialized for method [_GTF] [7.312221] kernel: 7.31] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due> [7.312325] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.312357] kernel: [7.312359] kernel: No Local Variables are initialized for Method [_GTF] [7.312359] kernel: [7.312360] kernel: No Arguments are initialized for method [_GTF] [7.312361] kernel: [7.312362] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due> [7.312399] kernel: ata5.00: ATA-10: CT240BX500SSD1, M6CR054, max UDMA/133 [7.312420] kernel: ata1.00: ATA-8: Hitachi HTS542525K9SA00, BBFOC31P, max U> [7.312699] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.312731] kernel: [7.312732] kernel: No Local Variables are initialized for Method [_GTF] [7.312733] kernel: [7.312734] kernel: No Arguments are initialized for method [_GTF] 7.312736] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due> [7.312768] kernel: ata2.00: ATA-9: HGST HTS541010A9E680, JA0OA710, max UDMA> [7.313013] kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth > [7.313420] kernel: ata5.00: 468862128 sectors, multi 1: LBA48 NCQ (depth 32> [7.314598] kernel: ata1.00: ATA Identify Device Log not supported [7.314601] kernel: ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 3> [7.314706] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.314738] kernel: [7.314740] kernel: No Local Variables are initialized for Method [_GTF] [7.314740] kernel: [7.314741] kernel: No Arguments are initialized for method [_GTF] [7.314742] kernel: [7.314743] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due> [7.315039] kernel: ata2.00: configured for UDMA/133 [7.315707] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.315740] kernel: [7.315741] kernel: No Local Variables are initialized for Method [_GTF] [7.315742] kernel: [7.315742] kernel: No Arguments are initialized for method [_GTF] [7.315743] kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996208/+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 1996208] [NEW] kernel: nvme nvme0: failed to set APST feature (2)
You have been subscribed to a public bug: always my computer on show me this error: kernel: nvme nvme0: failed to set APST feature (2) this error start with update kernel 5.15.0-52 well i check the logs and saw this: kernel: nvme nvme0: failed to set APST feature (2) [7.163360] kernel: nvme nvme0: allocated 64 MiB host memory buffer. [7.184123] kernel: nvme nvme0: 4/0/0 default/read/poll queues [7.201139] kernel: nvme0n1: p1 p2 [7.268310] kernel: usb 1-3: new full-speed USB device number 2 using xhci_h> [7.311210] kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [7.311225] kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [7.311239] kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [7.311251] kernel: ata4: SATA link down (SStatus 4 SControl 300) [7.311264] kernel: ata6: SATA link down (SStatus 4 SControl 300) [7.311278] kernel: ata3: SATA link down (SStatus 4 SControl 300) [7.312183] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.312217] kernel: [7.312218] kernel: No Local Variables are initialized for Method [_GTF] [7.312219] kernel: [7.312220] kernel: No Arguments are initialized for method [_GTF] [7.312221] kernel: 7.31] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due> [7.312325] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.312357] kernel: [7.312359] kernel: No Local Variables are initialized for Method [_GTF] [7.312359] kernel: [7.312360] kernel: No Arguments are initialized for method [_GTF] [7.312361] kernel: [7.312362] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due> [7.312399] kernel: ata5.00: ATA-10: CT240BX500SSD1, M6CR054, max UDMA/133 [7.312420] kernel: ata1.00: ATA-8: Hitachi HTS542525K9SA00, BBFOC31P, max U> [7.312699] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.312731] kernel: [7.312732] kernel: No Local Variables are initialized for Method [_GTF] [7.312733] kernel: [7.312734] kernel: No Arguments are initialized for method [_GTF] 7.312736] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due> [7.312768] kernel: ata2.00: ATA-9: HGST HTS541010A9E680, JA0OA710, max UDMA> [7.313013] kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth > [7.313420] kernel: ata5.00: 468862128 sectors, multi 1: LBA48 NCQ (depth 32> [7.314598] kernel: ata1.00: ATA Identify Device Log not supported [7.314601] kernel: ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 3> [7.314706] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.314738] kernel: [7.314740] kernel: No Local Variables are initialized for Method [_GTF] [7.314740] kernel: [7.314741] kernel: No Arguments are initialized for method [_GTF] [7.314742] kernel: [7.314743] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due> [7.315039] kernel: ata2.00: configured for UDMA/133 [7.315707] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC> [7.315740] kernel: [7.315741] kernel: No Local Variables are initialized for Method [_GTF] [7.315742] kernel: [7.315742] kernel: No Arguments are initialized for method [_GTF] [7.315743] kernel: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 22.04 bot-comment bug lts nvme ubuntu -- kernel: nvme nvme0: failed to set APST feature (2) https://bugs.launchpad.net/bugs/1996208 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992468] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1992468 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992468 Title: segfault in ld-linux-x86-64.so Status in linux package in Ubuntu: Incomplete Bug description: My manually built elf x64 file has started crashing on load, within the last month or so. It worked fine on Ubuntu 20.04.x, but fails on 22.04 - same problem on Mint 19.3 and Fedora 36. dmesg ... gives this: [ 107.121214] p[4370]: segfault at 0 ip 7f3d725b8350 sp 7ffea111fba0 error 4 in ld-linux-x86-64.so.2[7f3d72598000+2a000] [ 107.121230] Code: ff ff 00 45 31 db 48 8d 15 c9 ac 00 00 4c 8d 05 46 8f 01 00 4c 8d 2d 1f 8f 01 00 49 89 c2 48 8d 58 ff 48 89 f8 49 f7 da 66 90 <8b> 08 83 f9 07 77 19 85 c9 74 45 83 f9 07 77 40 48 63 0c 8a 48 01 You can download the offending file (a single plain 4MB ELF x64) from http://phix.x10.mx/p64 It almost certainly contains older/rarer forms of relocations and suchlike, but only about ten or so and meant to be as simple as possible. If I need to change the binary content of that file, I can, but might need a wee bit of help. Of course, if/once it gets through ld-linux-x86-64.so and complains about something else, ignore it, or should you be at all intrigued you can visit http://phix.x10.mx/download.php to get the full package. References, just in case you need them, or to ask a wider set than just me for more details direct: https://openeuphoria.org/forum/136972.wc?last_id=136973 https://github.com/petelomax/Phix/issues/13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992468/+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 1992468] Re: segfault in ld-linux-x86-64.so
Irv said: I upgraded my Linux kernel to 5.4.0-131-generic, and that solved the segfault issue. But latest Ubuntu uses 5.15.x, so the problem is probably back again. ** Package changed: glibc (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992468 Title: segfault in ld-linux-x86-64.so Status in linux package in Ubuntu: New Bug description: My manually built elf x64 file has started crashing on load, within the last month or so. It worked fine on Ubuntu 20.04.x, but fails on 22.04 - same problem on Mint 19.3 and Fedora 36. dmesg ... gives this: [ 107.121214] p[4370]: segfault at 0 ip 7f3d725b8350 sp 7ffea111fba0 error 4 in ld-linux-x86-64.so.2[7f3d72598000+2a000] [ 107.121230] Code: ff ff 00 45 31 db 48 8d 15 c9 ac 00 00 4c 8d 05 46 8f 01 00 4c 8d 2d 1f 8f 01 00 49 89 c2 48 8d 58 ff 48 89 f8 49 f7 da 66 90 <8b> 08 83 f9 07 77 19 85 c9 74 45 83 f9 07 77 40 48 63 0c 8a 48 01 You can download the offending file (a single plain 4MB ELF x64) from http://phix.x10.mx/p64 It almost certainly contains older/rarer forms of relocations and suchlike, but only about ten or so and meant to be as simple as possible. If I need to change the binary content of that file, I can, but might need a wee bit of help. Of course, if/once it gets through ld-linux-x86-64.so and complains about something else, ignore it, or should you be at all intrigued you can visit http://phix.x10.mx/download.php to get the full package. References, just in case you need them, or to ask a wider set than just me for more details direct: https://openeuphoria.org/forum/136972.wc?last_id=136973 https://github.com/petelomax/Phix/issues/13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992468/+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 1992468] [NEW] segfault in ld-linux-x86-64.so
You have been subscribed to a public bug: My manually built elf x64 file has started crashing on load, within the last month or so. It worked fine on Ubuntu 20.04.x, but fails on 22.04 - same problem on Mint 19.3 and Fedora 36. dmesg ... gives this: [ 107.121214] p[4370]: segfault at 0 ip 7f3d725b8350 sp 7ffea111fba0 error 4 in ld-linux-x86-64.so.2[7f3d72598000+2a000] [ 107.121230] Code: ff ff 00 45 31 db 48 8d 15 c9 ac 00 00 4c 8d 05 46 8f 01 00 4c 8d 2d 1f 8f 01 00 49 89 c2 48 8d 58 ff 48 89 f8 49 f7 da 66 90 <8b> 08 83 f9 07 77 19 85 c9 74 45 83 f9 07 77 40 48 63 0c 8a 48 01 You can download the offending file (a single plain 4MB ELF x64) from http://phix.x10.mx/p64 It almost certainly contains older/rarer forms of relocations and suchlike, but only about ten or so and meant to be as simple as possible. If I need to change the binary content of that file, I can, but might need a wee bit of help. Of course, if/once it gets through ld-linux-x86-64.so and complains about something else, ignore it, or should you be at all intrigued you can visit http://phix.x10.mx/download.php to get the full package. References, just in case you need them, or to ask a wider set than just me for more details direct: https://openeuphoria.org/forum/136972.wc?last_id=136973 https://github.com/petelomax/Phix/issues/13 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- segfault in ld-linux-x86-64.so https://bugs.launchpad.net/bugs/1992468 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Update: Last night I tried as far back as 18.04 and it turns out this has been backported everywhere. I've had these controllers since 2016-ish, have never had a problem before. Now I can't even work around by installing older kernels (s/a 5.3 used for 18.04.5). Finding other HWRAID controllers is not a solution for me. Here's the good news: https://github.com/torvalds/linux/commit/1e41e693f458eef2d5728207dbd327cd3b16580a ...has been merged into 6.1-rc4. So, help is on the way. -- 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Confirmed Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene16798 F pulseaudio /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Co
[Kernel-packages] [Bug 1995941] Re: [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait
A test kernel is currently being build at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1995941
--
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/1995941
Title:
[UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW
wait
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* In a secure execution guest, the external interrupt for the SIGP
external call order is delivered twice to a VCPU even though it was
only sent once.
* Under PV (protected virtualization), external call interrupts are
delivered by the SIGP interpretation facility, without KVM's
involvement.
But, if the receiving CPU is in enabled wait, KVM needs to wake the
receiving CPU such that the interrupt can be delivered.
Hence, in this case, the SIGP external call order causes
an interception.
* In response, KVM only needs to wake the receiving VCPU.
Interrupt delivery is then handled by the SIGP interpretation facility.
* KVM wrongly assumed it also needs to request injection for the
external call interrupt after the respective intercept, causing the
interrupt to be delivered twice:
* once through the SIGP interpretation facility
* and once through the interrupt injection control by KVM.
* Solution is to add appropriate special handling for 108 external
call intercepts.
[Fix]
* c3f0e5fd2d33 c3f0e5fd2d33d80c5a5a8b5e5d2bab2841709cc8
"KVM: s390: pv: don't present the ecall interrupt twice"
[Test Case]
* Have an Secure Execution (PV) environment setup on an
IBM z15 or LinuxONE III LPAR using Ubuntu Server 20.04 (latest).
* Apply kvm-unit-test submitted upstream:
"[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP call \
orders in enabled wait"
* Run the smp_PV kvm-unit-test: ./run_tests.sh smp_PV
* Check logs/smp_PV.log.
If system is affected, the following line can be found:
"ABORT: smp: psw wait: ecall: Unexpected external call interrupt \
(code 0x1202): on cpu 1 at 0x11958"
* If the system is not affected, the line should look like this:
"PASS: smp: psw wait: ecall: received"
[Regression Potential / What can go wrong]
* The handle_pv_notification can be wrong and misleading
in case 'ret' is not handled correctly.
* trace_kvm_s390_handle_sigp_pei might not be called correctly,
now after the if condition.
* In worst case the external interrupt could not be delivered
at all or still too often.
[Other]
* The fix/patch c3f0e5fd2d33 got upstream accepted with kernel v6.0,
so it not only needs to be applied to 20.04/5.4, but also to 22.04/5.15
and 22.10/5.19.
* But the patch got properly tagged for upstream stable:
Cc: # 5.7
Fixes: da24a0cc58ed ("KVM: s390: protvirt: Instruction emulation")
* And with that it got already picked up and is included in:
22.04 with Ubuntu-5.15.0-53.59 (currently in jammy-proposed)
22.10 with Ubuntu-5.19.0-16.16 means incl. in the release kernel.
* So the only Ubuntu release that is affected is 20.04/focal.
__
Description: KVM: PV: ext call delivered twice when receiver in PSW wait
Symptom: In a secure execution guest, the external interrupt for the
SIGP external call order is delivered twice to a VCPU even
though it was only sent once.
Problem: Under PV, external call interrupts are delivered by the SIGP
interpretation facility, without KVM's involvement. But, if the
receiving CPU is in enabled wait, KVM needs to wake the
receiving CPU such that the interrupt can be delivered. Hence,
in this case, the SIGP external call order causes an
interception. In response, KVM only needs to wake the receiving
VCPU. Interrupt delivery is then handled by the SIGP
interpretation facility.
KVM wrongfuly assumed it also needs to request injection for
the
external call interrupt after the respective intercept, causing
the interrupt to be delivered twice: once through the SIGP
interpretation facility and once through the interrupt
injection
control by KVM.
Solution: Add appropriate special handling for 108 external call
intercepts.
Reproduction: 0. Apply kvm-unit-test submitted upstream
("[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP
call orders in enabled wait").
1. Run the smp_PV kvm-unit-test:
./run_tests.sh sm
[Kernel-packages] [Bug 1995941] Re: [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait
SRU request submitted to the Ubuntu kernel team mailing list for focal:
https://lists.ubuntu.com/archives/kernel-team/2022-November/thread.html#134671
Changing status to 'In Progress' for focal.
** Changed in: linux (Ubuntu Focal)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel
Team (canonical-kernel-team)
** Changed in: linux (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: ubuntu-z-systems
Status: Triaged => In Progress
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1995941
Title:
[UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW
wait
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* In a secure execution guest, the external interrupt for the SIGP
external call order is delivered twice to a VCPU even though it was
only sent once.
* Under PV (protected virtualization), external call interrupts are
delivered by the SIGP interpretation facility, without KVM's
involvement.
But, if the receiving CPU is in enabled wait, KVM needs to wake the
receiving CPU such that the interrupt can be delivered.
Hence, in this case, the SIGP external call order causes
an interception.
* In response, KVM only needs to wake the receiving VCPU.
Interrupt delivery is then handled by the SIGP interpretation facility.
* KVM wrongly assumed it also needs to request injection for the
external call interrupt after the respective intercept, causing the
interrupt to be delivered twice:
* once through the SIGP interpretation facility
* and once through the interrupt injection control by KVM.
* Solution is to add appropriate special handling for 108 external
call intercepts.
[Fix]
* c3f0e5fd2d33 c3f0e5fd2d33d80c5a5a8b5e5d2bab2841709cc8
"KVM: s390: pv: don't present the ecall interrupt twice"
[Test Case]
* Have an Secure Execution (PV) environment setup on an
IBM z15 or LinuxONE III LPAR using Ubuntu Server 20.04 (latest).
* Apply kvm-unit-test submitted upstream:
"[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP call \
orders in enabled wait"
* Run the smp_PV kvm-unit-test: ./run_tests.sh smp_PV
* Check logs/smp_PV.log.
If system is affected, the following line can be found:
"ABORT: smp: psw wait: ecall: Unexpected external call interrupt \
(code 0x1202): on cpu 1 at 0x11958"
* If the system is not affected, the line should look like this:
"PASS: smp: psw wait: ecall: received"
[Regression Potential / What can go wrong]
* The handle_pv_notification can be wrong and misleading
in case 'ret' is not handled correctly.
* trace_kvm_s390_handle_sigp_pei might not be called correctly,
now after the if condition.
* In worst case the external interrupt could not be delivered
at all or still too often.
[Other]
* The fix/patch c3f0e5fd2d33 got upstream accepted with kernel v6.0,
so it not only needs to be applied to 20.04/5.4, but also to 22.04/5.15
and 22.10/5.19.
* But the patch got properly tagged for upstream stable:
Cc: # 5.7
Fixes: da24a0cc58ed ("KVM: s390: protvirt: Instruction emulation")
* And with that it got already picked up and is included in:
22.04 with Ubuntu-5.15.0-53.59 (currently in jammy-proposed)
22.10 with Ubuntu-5.19.0-16.16 means incl. in the release kernel.
* So the only Ubuntu release that is affected is 20.04/focal.
__
Description: KVM: PV: ext call delivered twice when receiver in PSW wait
Symptom: In a secure execution guest, the external interrupt for the
SIGP external call order is delivered twice to a VCPU even
though it was only sent once.
Problem: Under PV, external call interrupts are delivered by the SIGP
interpretation facility, without KVM's involvement. But, if the
receiving CPU is in enabled wait, KVM needs to wake the
receiving CPU such that the interrupt can be delivered. Hence,
in this case, the SIGP external call order causes an
interception. In response, KVM only needs to wake the receiving
VCPU. Interrupt delivery is then handled by the SIGP
interpretation facility.
KVM wrongfuly assumed it also needs to request injection for
the
external call interrupt after the respective intercept, causing
the interrupt to be delivered twice
[Kernel-packages] [Bug 1995941] Re: [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait
** Description changed:
+ SRU Justification:
+ ==
+
+ [Impact]
+
+ * In a secure execution guest, the external interrupt for the SIGP external
+call order is delivered twice to a VCPU even though it was only sent once.
+
+ * Under PV (protected virtualization), external call interrupts are
+delivered by the SIGP interpretation facility, without KVM's
+involvement.
+But, if the receiving CPU is in enabled wait, KVM needs to wake the
+receiving CPU such that the interrupt can be delivered.
+Hence, in this case, the SIGP external call order causes
+an interception.
+
+ * In response, KVM only needs to wake the receiving VCPU.
+Interrupt delivery is then handled by the SIGP interpretation facility.
+
+ * KVM wrongly assumed it also needs to request injection for the
+external call interrupt after the respective intercept, causing the
+interrupt to be delivered twice:
+* once through the SIGP interpretation facility
+* and once through the interrupt injection control by KVM.
+
+ * Solution is to add appropriate special handling for 108 external
+call intercepts.
+
+ [Fix]
+
+ * c3f0e5fd2d33 c3f0e5fd2d33d80c5a5a8b5e5d2bab2841709cc8
+"KVM: s390: pv: don't present the ecall interrupt twice"
+
+ [Test Case]
+
+ * Have an Secure Execution (PV) environment setup on an
+IBM z15 or LinuxONE III LPAR using Ubuntu Server 20.04 (latest).
+
+ * Apply kvm-unit-test submitted upstream:
+"[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP call \
+ orders in enabled wait"
+
+ * Run the smp_PV kvm-unit-test: ./run_tests.sh smp_PV
+
+ * Check logs/smp_PV.log.
+If system is affected, the following line can be found:
+"ABORT: smp: psw wait: ecall: Unexpected external call interrupt \
+ (code 0x1202): on cpu 1 at 0x11958"
+
+ * If the system is not affected, the line should look like this:
+"PASS: smp: psw wait: ecall: received"
+
+ [Regression Potential / What can go wrong]
+
+ * The handle_pv_notification can be wrong and misleading
+in case 'ret' is not handled correctly.
+
+ * trace_kvm_s390_handle_sigp_pei might not be called correctly,
+now after the if condition.
+
+ * In worst case the external interrupt could not be delivered
+at all or still too often.
+
+ [Other]
+
+ * The fix/patch c3f0e5fd2d33 got upstream accepted with kernel v6.0,
+so it not only needs to be applied to 20.04/5.4, but also to 22.04/5.15
+and 22.10/5.19.
+
+ * But the patch got properly tagged for upstream stable:
+Cc: # 5.7
+Fixes: da24a0cc58ed ("KVM: s390: protvirt: Instruction emulation")
+
+ * And with that it got already picked up and is included in:
+22.04 with Ubuntu-5.15.0-53.59 (currently in jammy-proposed)
+22.10 with Ubuntu-5.19.0-16.16 means incl. in the release kernel.
+
+ * So the only Ubuntu release that is affected is 20.04/focal.
+ __
+
Description: KVM: PV: ext call delivered twice when receiver in PSW wait
- Symptom: In a secure execution guest, the external interrupt for the
-SIGP external call order is delivered twice to a VCPU even
-though it was only sent once.
+ Symptom: In a secure execution guest, the external interrupt for the
+ SIGP external call order is delivered twice to a VCPU even
+ though it was only sent once.
Problem: Under PV, external call interrupts are delivered by the SIGP
-interpretation facility, without KVM's involvement. But, if the
-receiving CPU is in enabled wait, KVM needs to wake the
-receiving CPU such that the interrupt can be delivered. Hence,
-in this case, the SIGP external call order causes an
-interception. In response, KVM only needs to wake the receiving
-VCPU. Interrupt delivery is then handled by the SIGP
-interpretation facility.
+ interpretation facility, without KVM's involvement. But, if the
+ receiving CPU is in enabled wait, KVM needs to wake the
+ receiving CPU such that the interrupt can be delivered. Hence,
+ in this case, the SIGP external call order causes an
+ interception. In response, KVM only needs to wake the receiving
+ VCPU. Interrupt delivery is then handled by the SIGP
+ interpretation facility.
-KVM wrongfuly assumed it also needs to request injection for
the
-external call interrupt after the respective intercept, causing
-the interrupt to be delivered twice: once through the SIGP
-interpretation facility and once through the interrupt
injection
-control by KVM.
+ KVM wrongfuly assumed it also needs to request injection for
the
+ external call interrupt after the re
[Kernel-packages] [Bug 1994974] Re: Azure: hv_netvsc: Fix race between VF offering and VF association message from host
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux-azure (Ubuntu) Assignee: Tim Gardner (timg-tpi) => (unassigned) -- 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/1994974 Title: Azure: hv_netvsc: Fix race between VF offering and VF association message from host Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] During vm boot, there might be possibility that vf registration call comes before the vf association from host to vm. And this might break netvsc vf path, this is in order to prevent the same block vf registration until vf bind message comes from host. [Test Plan] Microsoft tested [Where things could go wrong] The 5.4 backport patch could hang waiting for a VF addition to complete. [Other Info] SF: #00347129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1994974/+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 1973434] Re: massive performance issues since 22.04 upgrade
I don't know if it is related with what is happening to me, but all my drag actions becomes slow / frozen. It appears that the window is updated internally for each the way the mouse taked (when I am dragging). It happens only when I have a lot of things opened. Specially if that things uses 3D acceleration (it can be vulkan or OpenGL that does not matter I already tested it). I monitored the system usage and the CPU is very low usage and the GPU too (3% to 7% CPU and 20% to 33% GPU). But, the system load becomes high (more than 1.0) when I try to drag some window. When I stop of trying to drag the system load slowly lowers. I recorded a video with OBS and the recording freezes too in the same moments so It appears to be related with image drawing when using input on a window manager. It happens too on Budgie Desktop. The action drains CPU usage (one core almost). I mean, when I drag a window slowy (a terminal with htop running) I can view a very high CPU usage in that moment (And I can ear the CPU fan running faster too). So it is some function that stay on some loop of some kind related with the drag action only draining CPU instead of waiting and let other tasks to run. My system information: intel_iommu=off Linux 5.15.0-52-generic NVIDIA 520.56.06 Ubuntu 22.04.1 LTS -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.ve
[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer
Test packages were build for F, J and K and are available via this PPA: https://launchpad.net/~fheimes/+archive/ubuntu/lp1996071 -- 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/1996071 Title: [UBUNTU 20.04] boot: Add s390x secure boot trailer Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Bug description: SRU Justification: == [Impact] * Secure boot of Linux on s390x will no longer be possible with an upcoming IBM zSystems firmware update. [Fix] * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add secure boot trailer" for kinetic and jammy * https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch backport for focal [Test Plan] * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is required. * Ensure that 'Enable Secure Boot for Linux' is marked in case 'SCSI Load' is selected at the HMCs Load task and Activation Profile. * Perform an Ubuntu Server installation, either 20.04 or 22.04 (latest ISO). It will be a secure boot installation by default in case 'Enable Secure Boot for Linux' was marked. * Check sysfs: /sys/firmware/ipl/has_secure '1' indicates hw support for secure boot, otherwise '0' /sys/firmware/ipl/secure '1' indicates that secure IPL was successful, otherwise '0' * Navigate to the HMC task 'System information' and check the active firmware release. * Ensure that Ubuntu is still bootable in secure-boot mode with the updated firmware active, by for example doing a reboot after the firmware upgrade. [Where problems could occur] * The 'trailer' might be broken, invalid or in a wrong format and can't be identified or read properly, or may cause issues while compressing/decompressing the kernel. * In worst case secure boot might become broken, even on systems that are still on the unpatched firmware level. * Or secure boot will become broken in general. [Other Info] * The above commit was upstream accepted with v6.1-rc3. * And it got tagged for upstream stable with: "Cc: # 5.2+" * But since this bug is marked as critical, and the patch is relatively short, traceable and s390x-specific, I'll go ahead and submit this patch for Jammy and Focal ahead of upstream stable. * Since on focal file 'vmlinux.lds.S' is at a different location 'arch/s390/boot/compressed/' instead of 'arch/s390/boot/' and the context is slightly different, the backport is needed. * It's planned to have kernel 6.2 in lunar (23.04), hence it will have the patch incl. when at the planned target level. __ Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+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 1993665] Re: Update the 470-server NVIDIA driver
Tested bionic, focal and jammy on VMs and a DGX2. All cuda tests passed. There is no updated kinetic driver, so unable to test there. ** Tags added: verification-done-bionic verification-done-focal verification-done-jammy verification-failed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1993665 Title: Update the 470-server NVIDIA driver Status in fabric-manager-470 package in Ubuntu: In Progress Status in libnvidia-nscq-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in fabric-manager-470 source package in Bionic: In Progress Status in libnvidia-nscq-470 source package in Bionic: In Progress Status in nvidia-graphics-drivers-470-server source package in Bionic: In Progress Status in fabric-manager-470 source package in Focal: In Progress Status in libnvidia-nscq-470 source package in Focal: In Progress Status in nvidia-graphics-drivers-470-server source package in Focal: In Progress Status in fabric-manager-470 source package in Jammy: In Progress Status in libnvidia-nscq-470 source package in Jammy: In Progress Status in nvidia-graphics-drivers-470-server source package in Jammy: In Progress Status in fabric-manager-470 source package in Kinetic: In Progress Status in libnvidia-nscq-470 source package in Kinetic: In Progress Status in nvidia-graphics-drivers-470-server source package in Kinetic: In Progress Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/1993665/+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 1996217] Re: SIGTRAP on launch 109.0.5396.2-2184
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2022-08-26 (76 days ago)
Inst
[Kernel-packages] [Bug 1996217] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630407/+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/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubun
[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer
** Description changed: + SRU Justification: + == + + [Impact] + + * Secure boot of Linux on s390x will no longer be possible +with an upcoming IBM zSystems firmware update. + + [Fix] + + * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add secure boot trailer" +for kinetic and jammy + + * https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch +backport for focal + + [Test Plan] + + * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is + required. + + * Ensure that 'Enable Secure Boot for Linux' is marked in case +'SCSI Load' is selected at the HMCs Load task and Activation Profile. + + * Perform an Ubuntu Server installation, either 20.04 or 22.04 +(latest ISO). +It will be a secure boot installation by default in case +'Enable Secure Boot for Linux' was marked. + + * Check sysfs: +/sys/firmware/ipl/has_secure + '1' indicates hw support for secure boot, otherwise '0' +/sys/firmware/ipl/secure + '1' indicates that secure IPL was successful, otherwise '0' + + * Navigate to the HMC task 'System information' +and check the active firmware release. + + * Ensure that Ubuntu is still bootable in secure-boot mode +with the updated firmware active, +by for example doing a reboot after the firmware upgrade. + + [Where problems could occur] + + * The 'trailer' might be broken, invalid or in a wrong format +and can't be identified or read properly, +or may cause issues while compressing/decompressing the kernel. + + * In worst case secure boot might become broken, +even on systems that are still on the unpatched firmware level. + + * Or secure boot will become broken in general. + + [Other Info] + + * The above commit was upstream accepted with v6.1-rc3. + + * And it got tagged for upstream stable with: +"Cc: # 5.2+" + + * But since this bug is marked as critical, and the patch is relatively +short, traceable and s390x-specific, I'll go ahead and submit this +patch for Jammy and Focal ahead of upstream stable. + + * Since on focal file 'vmlinux.lds.S' is at a different location +'arch/s390/boot/compressed/' instead of 'arch/s390/boot/' +and the context is slightly different, the backport is needed. + + * It's planned to have kernel 6.2 in lunar (23.04), hence it will have +the patch incl. when at the planned target level. + + __ + Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming -IBM Z firmware update. + IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a -trailing data block with a specific format. + trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel -- 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/1996071 Title: [UBUNTU 20.04] boot: Add s390x secure boot trailer Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Bug description: SRU Justification: == [Impact] * Secure boot of Linux on s390x will no longer be possible with an upcoming IBM zSystems firmware update. [Fix] * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add secure boot trailer" for kinetic and jammy * https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch backport for focal [Test Plan] * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is required. * Ensure that 'Enable Secure Boot for Linux' is marked in case 'SCSI Load' is selected at the HMCs Load task and Activation Profile. * Perform an Ubuntu Server installation, either 20.04 or 22.04 (latest ISO). It will be a secure boot installation by default in case 'Enable Secure Boot for Linux' was marked. * Check sysfs: /sys/firmware/ipl/has_secure '1' indicates hw support for secure boot, otherwise '0' /sys/firmware/ipl/secure '1' indicates that secure IPL was successful, otherwise '0' * Navigate to the HMC task 'System information' and check the active firmware release. * Ensure that Ubuntu is still bootable in secure-boot mode with the up
[Kernel-packages] [Bug 1996217] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630400/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop
[Kernel-packages] [Bug 1996217] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630402/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop
[Kernel-packages] [Bug 1996217] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630399/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu
[Kernel-packages] [Bug 1996217] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630397/+files/Lsusb.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/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOM
[Kernel-packages] [Bug 1996217] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630398/+files/Lsusb-t.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/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu
[Kernel-packages] [Bug 1996217] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630406/+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/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop:
[Kernel-packages] [Bug 1996217] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630403/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentD
[Kernel-packages] [Bug 1996217] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630404/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop
[Kernel-packages] [Bug 1996217] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630405/+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/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GN
[Kernel-packages] [Bug 1996217] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630401/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
[Kernel-packages] [Bug 1996217] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630396/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubun
[Kernel-packages] [Bug 1996217] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630395/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOM
[Kernel-packages] [Bug 1996217] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630393/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDeskt
[Kernel-packages] [Bug 1996217] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630394/+files/IwConfig.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/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
SNAPPY DEBUG
$ snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
= Seccomp =
Time: Nov 10 09:48:03
Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
Syscall: pkey_mprotect
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stolk 2044 F wireplumber
/dev/snd/controlC1: stolk 2044 F wireplumber
/dev/snd/seq:stolk 2041 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubun
[Kernel-packages] [Bug 1996217] Re: SIGTRAP on launch 109.0.5396.2-2184
apport information
** Description changed:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
-
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
-
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
+
+ SNAPPY DEBUG
+
+
+ $ snappy-debug
+ INFO: Following '/var/log/syslog'. If have dropped messages, use:
+ INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
+ = Seccomp =
+ Time: Nov 10 09:48:03
+ Log: auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=60371
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e 329(pkey_mprotect) compat=0 ip=0x7f739326773d code=0x5
+ Syscall: pkey_mprotect
+
+
+
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
** Tags added: apport-collected kinetic wayland-session
** Description changed:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_R
[Kernel-packages] [Bug 1991676] Re: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.)
@juliank, ah, I found another detail. This appears to only break when the package is updated in the ADT testbed. My assumption is if the latest package version is already in the base image, there is no package update and therefore no breakage. For example: [1] older image, fails: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/d/dpdk/20221027_190645_aae03@/log.gz [2] newer image, passes: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/d/dpdk/20221028_185258_2a00f@/log.gz The second run occurred about a day later. I can't tell if this is using a new image, but when I inspected the artifacts from the run. I do see `grub-efi-arm64-bin 2.04-1ubuntu47.4`, which is the latest and the version that [1] tried to upgrade to. So I guess we generally avoid this by refreshing the ADT base images. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1991676 Title: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.) Status in ubuntu-kernel-tests: New Status in grub2-signed package in Ubuntu: Invalid Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in grub2-signed source package in Bionic: Triaged Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: The ADT tests for arm64 kernels in Bionic are failing during the setup phase with the following errors: Setting up grub-efi-arm64-signed (1.173.2~18.04.1+2.04-1ubuntu47.4) ... Installing for arm64-efi platform. grub-install: error: efibootmgr: not found. dpkg: error processing package grub-efi-arm64-signed (--configure): installed grub-efi-arm64-signed package post-installation script subprocess returned error exit status 1 Setting up libx11-6:arm64 (2:1.6.4-3ubuntu0.5) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for libc-bin (2.27-3ubuntu1.6) ... Errors were encountered while processing: grub-efi-arm64-signed E: Sub-process /usr/bin/dpkg returned an error code (1) blame: badpkg: testbed setup commands failed with status 100 autopkgtest [15:12:03]: ERROR: erroneous package: testbed setup commands failed with status 100 ADT test log: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux-hwe-5.4/20220930_151219_13ac3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991676/+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 1996217] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1996217
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1996217/+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 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer
** Summary changed: - [UBUNTU 20.04] boot: Add secure boot trailer + [UBUNTU 20.04] boot: Add s390x secure boot trailer -- 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/1996071 Title: [UBUNTU 20.04] boot: Add s390x secure boot trailer Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Bug description: Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+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 1989944] Re: [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version
** Description changed: - We applied a set of patches early as the upstreaming got delayed. The - patch now is in linux-next on its way into upstream linux. When that - happens we want to replace the SAUCE patch by its upstream version (for - example to get security checks right). + [SRU Justification] - “UBUNTU: SAUCE: thunderbolt: Add DP out resource when DP tunnel is - discovered.” + == Impact == + We applied a set of patches early as the upstreaming got delayed. The patch now is in upstream linux. Since it differs somewhat from the patch we carry and in order to get potential security and other updates right, we want to replace the SAUCE patch by its upstream counterpart. - to be replaced by: + == Fix == + “UBUNTU: SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered.” + to be replaced by: + commit b60e31bf18a7064032dbcb73dcb5b58f8a00a110 linux-next + “thunderbolt: Add DP OUT resource when DP tunnel is discovered” - commit b60e31bf18a7064032dbcb73dcb5b58f8a00a110 linux-next - “thunderbolt: Add DP OUT resource when DP tunnel is discovered” + == Testcase == + Attach external Monitor via Thunderbolt port (AMD GPU) (Reference: bug 1983143) - By now it is confirmed that the patch in linux-next is somehow different - from the one we carry. But to be on the safe side we should wait until - it is really upstream and maybe give a little time to settle before - actually changing things. + == Regression Potential == + Previously working external connections might no longer work. ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Stefan Bader (smb) -- 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/1989944 Title: [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version Status in linux package in Ubuntu: Triaged Status in linux source package in Jammy: In Progress Bug description: [SRU Justification] == Impact == We applied a set of patches early as the upstreaming got delayed. The patch now is in upstream linux. Since it differs somewhat from the patch we carry and in order to get potential security and other updates right, we want to replace the SAUCE patch by its upstream counterpart. == Fix == “UBUNTU: SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered.” to be replaced by: commit b60e31bf18a7064032dbcb73dcb5b58f8a00a110 linux-next “thunderbolt: Add DP OUT resource when DP tunnel is discovered” == Testcase == Attach external Monitor via Thunderbolt port (AMD GPU) (Reference: bug 1983143) == Regression Potential == Previously working external connections might no longer work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989944/+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 1991676] Re: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.)
Well surely not more than the past year, this is not a new bug after all, the regression was introduced with the initial boothole update when we did the one grub split. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1991676 Title: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.) Status in ubuntu-kernel-tests: New Status in grub2-signed package in Ubuntu: Invalid Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in grub2-signed source package in Bionic: Triaged Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: The ADT tests for arm64 kernels in Bionic are failing during the setup phase with the following errors: Setting up grub-efi-arm64-signed (1.173.2~18.04.1+2.04-1ubuntu47.4) ... Installing for arm64-efi platform. grub-install: error: efibootmgr: not found. dpkg: error processing package grub-efi-arm64-signed (--configure): installed grub-efi-arm64-signed package post-installation script subprocess returned error exit status 1 Setting up libx11-6:arm64 (2:1.6.4-3ubuntu0.5) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for libc-bin (2.27-3ubuntu1.6) ... Errors were encountered while processing: grub-efi-arm64-signed E: Sub-process /usr/bin/dpkg returned an error code (1) blame: badpkg: testbed setup commands failed with status 100 autopkgtest [15:12:03]: ERROR: erroneous package: testbed setup commands failed with status 100 ADT test log: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux-hwe-5.4/20220930_151219_13ac3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991676/+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 1996217] Re: SIGTRAP on launch 109.0.5396.2-2184
I'm targeting this to Linux too as I suspect it's kernel related. I may
be wrong.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996217
Title:
SIGTRAP on launch 109.0.5396.2-2184
Status in chromium-browser package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Bug description:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
...
mprotect(0x560c91e2d000, 8187904, PROT_READ) = 0
mprotect(0x7f9013377000, 4096, PROT_READ) = 0
munmap(0x7f9012e3e000, 91649) = 0
set_tid_address(0x7f9010ae0110) = 55209
set_robust_list(0x7f9010ae0120, 24) = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f9012e1bbf0, sa_mask=[],
sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f9012e1bc90, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f9012e29420}, NULL,
8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
futex(0x7f9012e3d0c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\x74\xd0\x85\x97\x19\x76\xcf\x4a", 8, 0) = 8
getrandom("\x0b\x28\x11\x02\x4b\x2b\x50\xce", 8, 0) = 8
mmap(0x27d4, 17179869184, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x27d4
mmap(0x2e43f000, 17179873280, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2e43f000
pkey_mprotect(0x27d400201000, 4096, PROT_READ|PROT_WRITE, 0) = -1 EPERM
(Operation not permitted)
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
error: signal: trace/breakpoint trap
===
JOURNAL
===
And the journal entries during launch:
Nov 10 08:24:02 workpc systemd[1949]: Started Application launched by
gnome-shell.
Nov 10 08:24:02 workpc systemd[1949]: Started VTE child process 54818
launched by gnome-terminal-server process 40213.
Nov 10 08:24:09 workpc systemd[1949]: Started
snap.chromium.chromium.414af9f4-295b-44f0-976c-4abb39846b28.scope.
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:548):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=12 capname="net_admin"
Nov 10 08:24:09 workpc kernel: audit: type=1400 audit(1668097449.379:549):
apparmor="DENIED" operation="capable" class="cap"
profile="/usr/lib/snapd/snap-confine" pid=54829 comm="snap-confine"
capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: AVC apparmor="DENIED"
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=54829
comm="snap-confine" capability=38 capname="perfmon"
Nov 10 08:24:09 workpc audit[54829]: SECCOMP auid=1000 uid=1000 gid=1000
ses=2 subj=snap.chromium.chromium pid=54829 comm="chrome"
exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
Nov 10 08:24:09 workpc kernel: traps: chrome[54829] trap int3 ip:558e4009f96e
sp:7fff421fe9f0 error:0 in chrome[558e3fecb000+a1b2000]
Nov 10 08:24:09 workpc kernel: audit: type=1326 audit(1668097449.439:550):
auid=1000 uid=1000 gid=1000 ses=2 subj=snap.chromium.chromium pid=54829
comm="chrome" exe="/snap/chromium/2184/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=329 compat=0 ip=0x7f3259ae573d code=0x5
=
SPECS
=
OS: Ubuntu 22.10
Kernel: 5.19.0-21-generic
CPU: 12600k
snap: 109.0.5396.2 2184 latest/edge canonical✓
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1996217/+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 1991676] Re: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.)
@juliank Hello, I see that you picked up https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1991676. I just want to mention so that you are aware, that this is blocking most, if not all, kernel ADT testing on bionic arm64. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1991676 Title: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.) Status in ubuntu-kernel-tests: New Status in grub2-signed package in Ubuntu: Invalid Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in grub2-signed source package in Bionic: Triaged Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: The ADT tests for arm64 kernels in Bionic are failing during the setup phase with the following errors: Setting up grub-efi-arm64-signed (1.173.2~18.04.1+2.04-1ubuntu47.4) ... Installing for arm64-efi platform. grub-install: error: efibootmgr: not found. dpkg: error processing package grub-efi-arm64-signed (--configure): installed grub-efi-arm64-signed package post-installation script subprocess returned error exit status 1 Setting up libx11-6:arm64 (2:1.6.4-3ubuntu0.5) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for libc-bin (2.27-3ubuntu1.6) ... Errors were encountered while processing: grub-efi-arm64-signed E: Sub-process /usr/bin/dpkg returned an error code (1) blame: badpkg: testbed setup commands failed with status 100 autopkgtest [15:12:03]: ERROR: erroneous package: testbed setup commands failed with status 100 ADT test log: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux-hwe-5.4/20220930_151219_13ac3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991676/+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 1996198] Re: Fix rfkill causing soft blocked wifi
** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: Confirmed => 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/1996198 Title: Fix rfkill causing soft blocked wifi Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-6.0 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Need this patch in so a BIOS upgrade won't cause issues on HP laptops. commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a Author: Jorge Lopez Date: Fri Oct 28 10:55:27 2022 -0500 platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded strange char "^@" which printed out every second and makes login nearly impossible. Also the below messages were shown both in console and journal/dmesg every second: usb 1-3: Device not responding to setup address. usb 1-3: device not accepting address 4, error -71 usb 1-3: device descriptor read/all, error -71 usb usb1-port3: unable to enumerate USB device Wifi is soft blocked by checking rfkill. When unblocked manually, after few seconds it would be soft blocked again. So I was suspecting something triggered rfkill to soft block wifi. At the end it was fixed by removing hp_wmi module. The root cause is the way hp-wmi driver handles command 1B on post-2009 BIOS. In pre-2009 BIOS, command 1Bh return 0x4 to indicate that BIOS no longer controls the power for the wireless devices. Signed-off-by: Jorge Lopez Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468 Reviewed-by: Mario Limonciello Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com Cc: sta...@vger.kernel.org Reviewed-by: Hans de Goede Signed-off-by: Hans de Goede [Test case] test on a HP laptop with the new BIOS [Where problems could occur] from the commit: * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that * BIOS no longer controls the power for the wireless * devices. All features supported by this command will no * longer be supported. anyone running a laptop with obsolete pre-2009 BIOS probably won't notice the missing feature at this point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996198/+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 1988018] Re: [mlx5] Intermittent VF-LAG activation failure
** Tags removed: foundations-triage-discuss -- 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/1988018 Title: [mlx5] Intermittent VF-LAG activation failure Status in linux package in Ubuntu: Fix Committed Status in netplan.io package in Ubuntu: Triaged Status in linux source package in Jammy: New Status in netplan.io source package in Jammy: New Status in linux source package in Kinetic: Fix Committed Status in netplan.io source package in Kinetic: Triaged Bug description: During system initialization there is a specific sequence that must be followed to enable the use of hardware offload and VF-LAG. Intermittently one may see that VF-LAG initialization fails: [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2 shared_fdb:1 [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_cmd_check:782:(pid 9): CREATE_LAG(0x840) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x7d49cb) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_create_lag:248:(pid 9): Failed to create LAG (-22) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_activate_lag:288:(pid 9): Failed to activate VF LAG Make sure all VFs are unbound prior to VF LAG activation or deactivation This is caused by rebinding the driver prior to the VF lag being ready. A sysfs knob has recently been added to the driver [0] and we should monitor it before attempting to rebind the driver: $ cat /sys/kernel/debug/mlx5/\:08\:00.0/lag/state The kernel feature is available in the upcoming Kinetic 5.19 kernel and we should probably backport it to the Jammy 5.15 kernel. 0: https://github.com/torvalds/linux/commit/7f46a0b7327ae261f9981888708dbca22c283900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988018/+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 1994601] Comment bridged from LTC Bugzilla
--- Comment From mihaj...@de.ibm.com 2022-11-10 11:26 EDT--- I re-ran the installation as described above and now I was able to boot the VM. Thanks! -- 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/1994601 Title: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: SRU Justification: == [ Impact ] * Ubuntu 18.04 / bionic installations with latest kernel 4.15.0-194 are no longer able to IPL (boot) on IBM z14 or newer hardware. * This issue got introduced by upstream commit e4f74400308c "s390/archrandom: simplify back to earlier design and initialize earlier" that was SRUed to 18.04/bionic based on LP#1989625, which made changes in the s390s IPL/boot area of kernel/arch/random. * The reason seems to be that the bad patch moves the decision about if arch randomness is available to setup.c function setup_randomness(). This code uses a static_key s390_arch_random_available. But in the Canonical kernel the initialization function for the jump labels (where the static keys are based on) jump_label_init() is called in generic start_kernel() wheres in the upstream kernel the init function is called early in setup_arch(). * Reverting this commit from bionic master-next makes bionic systems again bootable. (https://launchpad.net/~fheimes/+archive/ubuntu/test/) [ Test Plan ] * An IBM z14 or LinuxONE II or newer system is needed. * Now install latest bionic on that system - doesn't if it's on LPAR, z/VM or KVM. * After the installation (an the trigger of the post install reboot), the system will not come up. * To test a patched kernel with e4f74400308c can be tested in the following way: * Install 18.04 GA and prevent it from doing any kernel updates. * Means, install in 'island' mode or select in d-i 'Advanced Installation' and explicitly choose '4.15.0-50 generic' to install. * That allows the system to come up and to update the kernel to a modified one. * Then reboot and verify if the system comes up properly. [ Where problems could occur ] * Problems could occur due to the fact that the commit was not cleanly reversible because of minor context changes. * Adjustments that were needed might break other things if not done carefully. * Further commits (applied after e4f74400308c) may still rely on the bad e4f74400308c commit - or even further patches (from upstream stable). * In worst case IPL / boot might get broken, even on hardware older than z14. * If the revert works fine can be easily tested and was tested based on https://launchpad.net/~fheimes/+archive/ubuntu/test/ and the above test plan. [ Other Info ] * Ubuntu 20.04 (focal, using legacy image with virt-install) was tested as well, but is not affected by this issue. __ ---Problem Description--- Ubuntu 18.04 crashes during IPL with no output on the console. Contact Information = Viktor Mihajlovski ---uname output--- n/a Machine Type = 3096 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install Ubuntu 18.04 as a KVM guest using the following command: virt-install -n bionic --cdrom /var/lib/libvirt/images/ubuntu-18.04.5-server-s390x.iso --memory 2048 --disk size=8 then reboot. Stack trace output: no Oops output: no == Comment: #1 - Viktor Mihajlovski - 2022-10-25 10:48:30 == Installing under z/VM leads to the same failure. == Comment: #2 - Viktor Mihajlovski - 2022-10-25 10:55:10 == I have captured a dump using virsh dump --memory-only. The output of crash log is uploaded == Comment: #7 - Harald Freudenberger - 2022-10-26 07:33:52 == Looks like all ubuntu 18.04 installations on s390 are not working any more. It is not an issue with z14 but z17 also fails to run a fresh installed ubuntu 18.04. == Comment: #8 - Harald Freudenberger - 2022-10-26 08:25:52 == when I use the 'advanced installation' where I am able to choose the kernel package and then choose the 4.15.0-50 generic the installed Ubuntu 18.04 comes up fine. So this issue is somewhere between kernel 4.15.0-50 and 4.15.0-194. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1994601/+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 1995453] Re: Add some ACPI device IDs for Intel HID device
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995453 Title: Add some ACPI device IDs for Intel HID device Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: New Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake [Fix] ACPI devices IDs are add the the related Intel HID devices on these platforms can work. [Test] Verified the Intel HID events can work such as power button for suspend and wake. [Where problems could occur] Add the ACPI device IDs for support Intel HID devices, so chance of problems should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995453/+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 1996198] Re: Fix rfkill causing soft blocked wifi
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Confirmed => 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/1996198 Title: Fix rfkill causing soft blocked wifi Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-6.0 source package in Focal: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Confirmed Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Need this patch in so a BIOS upgrade won't cause issues on HP laptops. commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a Author: Jorge Lopez Date: Fri Oct 28 10:55:27 2022 -0500 platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded strange char "^@" which printed out every second and makes login nearly impossible. Also the below messages were shown both in console and journal/dmesg every second: usb 1-3: Device not responding to setup address. usb 1-3: device not accepting address 4, error -71 usb 1-3: device descriptor read/all, error -71 usb usb1-port3: unable to enumerate USB device Wifi is soft blocked by checking rfkill. When unblocked manually, after few seconds it would be soft blocked again. So I was suspecting something triggered rfkill to soft block wifi. At the end it was fixed by removing hp_wmi module. The root cause is the way hp-wmi driver handles command 1B on post-2009 BIOS. In pre-2009 BIOS, command 1Bh return 0x4 to indicate that BIOS no longer controls the power for the wireless devices. Signed-off-by: Jorge Lopez Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468 Reviewed-by: Mario Limonciello Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com Cc: sta...@vger.kernel.org Reviewed-by: Hans de Goede Signed-off-by: Hans de Goede [Test case] test on a HP laptop with the new BIOS [Where problems could occur] from the commit: * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that * BIOS no longer controls the power for the wireless * devices. All features supported by this command will no * longer be supported. anyone running a laptop with obsolete pre-2009 BIOS probably won't notice the missing feature at this point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996198/+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 1993240] Re: amd_sfh modprobe fails when no sensor reported from AMD MP2
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1993240 Title: amd_sfh modprobe fails when no sensor reported from AMD MP2 Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] Some AMD platforms might not have sensor reported from MP2 controller, and that fails device init. [Fix] Two commits targeting v6.1 release in mainline kernel. [Test Case] On such platforms, driver loading should be bailed out with: $ sudo dmesg | grep amd_sfh1_1_hid_client_init [ 1.204896] pcie_mp2_amd :62:00.7: amd_sfh1_1_hid_client_init failed [Where problems could occur] This skips driver loading against ineffective hardware only. [Other Info] While this targets oem-6.0 and above, and is already in mainline v6.1-rc1, only oem-6.0 is nominated for fix. == original bug report == Fix amd_sfh to make each sensor with proper initialization & resource allocation during MP2 loaded. To be in v6.1 https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/drivers/hid/amd-sfh- hid?h=next-20221010&id=68266bdcceec10ea364e62c63732cd6fe5a256a8 https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/drivers/hid/amd-sfh- hid?h=next-20221010&id=beb18bb22cd4fb88648bb2925d56f36131c1ac21 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993240/+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 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990700 Title: Fibocom WWAN FM350-GL suspend error (notebook not suspend) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Fibocom WWAN FM350-GL equipped platform fails to suspend. [Fix] Full t7xx driver is still under development and some of them have already accepted and merged in mainline kernel. The following commits are once in the mainline and are reverted in v6.0: d20ef656f994 net: wwan: t7xx: Add AP CLDMA 007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration 140424d90165 net: wwan: t7xx: PCIe reset rescan 87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and coredump collection The first patch implemented the other AP-CLDMA, and with that applied, platforms in question may suspend and resume normally as every bits are in position. However, while these patches had been reverted for another revision that is still being worked on by the hardware vendor, a minimum, sauced patch is created to work-around this first to meet project schedules, and will be reverted and superseded with a final, mainline landing revision. [Test Case] Trigger suspend and there should be no more suspend errors from t7xx: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 [Where problems could occur] The t7xx driver is still incomplete and we're staging aforementioned 4 patches in internal experimental kernels for development use. [Other Info] This affects Kinetic and above, so only Unstable, Kinetic and OEM-6.0 are nominated for fix. == original bug report == Hi, I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module mtk_t7xx . Power management for this modem is bad. When the notebook goes to sleep/suspend, kernel module mtk_t7xx return an error: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 So power management failed to suspend: PM: Some devices failed to suspend, or early wake event detected And the notebook not suspend and wake up again. It must be this module, because if I remove the module first (modprobe -r), the laptop goes to sleep and wakes up normally. However, after reinserting the module, the modem no longer appears in the system. Expected state: sleep occurs when the device is put to sleep - including the modem. When you wake up, you will wake up, including activating the modem and logging into the operator's network. Description:Ubuntu 20.04.5 LTS Release:20.04 lspci -v: 58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01) Subsystem: Device 1cf8:3500 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at 601e80 (64-bit, prefetchable) [size=32K] Memory at 5e80 (64-bit, non-prefetchable) [size=8M] Memory at 601e00 (64-bit, prefetchable) [size=8M] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [d0] MSI-X: Enable+ Count=34 Masked- Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [f8] Power Management version 3 Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 Capabilities: [108] Latency Tolerance Reporting Capabilities: [110] L1 PM Substates Capabilities: [200] Advanced Error Reporting Capabilities: [300] Secondary PCI Express Kernel driver in use: mtk_t7xx Kernel modules: mtk_t7xx lshw: *-generic description: Wireless controller product: MEDIATEK Corp. vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:58:00.0
[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Tags removed: foundations-triage-discuss -- 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/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in snapd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Invalid Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+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 1995041] Re: Fix ath11k deadlock on WCN6855
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995041 Title: Fix ath11k deadlock on WCN6855 Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] ath11k is in deadlock when stress reboot or suspend on WCN6855. sometimes kernel hang. Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211] [Fix] Fix this by switching from using regulatory_set_wiphy_regd_sync() to regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue which handles the locking on it's own. So the ath11k workqueue can simply exit without taking any locks, avoiding the deadlock. [Test] Verified on hardware, stress reboot and suspend 30 times OK. [Where problems could occur] It may break ath11k wifi driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1991366 Title: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] Some Dell laptops where booting with Thunderbolt/USB4 devices connected the BIOS leaves some of the PCIe devices unconfigured. The kernel message shows "No bus number available for hot-added bridge". The connected devices can't be found. [Fix] Current linux PCI distribute the "spare" resources between hotplug ports on hot-add but have not done that upon the initial scan. The patches make the initial root bus scan path to do the same. The additional patches are just a small cleanups that can be applied separately too. [Test] 1. Power on the machine with Thunderbolt/USB4 devices connected. 2. Check the kernel message to see if "No bus number available for hot-added bridge" shows up or not. 3. Check if the Thunderbolt/USB4 devices works or not. [Where problems could occur] The patches only apply the same procedures on initial root bus scan which was not done. If the BIOS configures the PCI correctly, everything is OK. It only takes effect for the BIOS w/ unconfigured PCIe devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993315] Re: md: Replace snprintf with scnprintf
** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1993315 Title: md: Replace snprintf with scnprintf Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] Current code produces a warning as shown below when total characters in the constituent block device names plus the slashes exceeds 200. snprintf() returns the number of characters generated from the given input, which could cause the expression “200 – len” to wrap around to a large positive number. Fix this by using scnprintf() instead, which returns the actual number of characters written into the buffer. [ 1513.267938] [ cut here ] [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 vsnprintf+0x2c8/0x510 [ 1513.267944] Modules linked in: [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure #90~18.04.1-Ubuntu [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022 [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510 <-snip-> [ 1513.267982] Call Trace: [ 1513.267986] snprintf+0x45/0x70 [ 1513.267990] ? disk_name+0x71/0xa0 [ 1513.267993] dump_zones+0x114/0x240 [raid0] [ 1513.267996] ? _cond_resched+0x19/0x40 [ 1513.267998] raid0_run+0x19e/0x270 [raid0] [ 1513.268000] md_run+0x5e0/0xc50 [ 1513.268003] ? security_capable+0x3f/0x60 [ 1513.268005] do_md_run+0x19/0x110 [ 1513.268006] md_ioctl+0x195e/0x1f90 [ 1513.268007] blkdev_ioctl+0x91f/0x9f0 [ 1513.268010] block_ioctl+0x3d/0x50 [ 1513.268012] do_vfs_ioctl+0xa9/0x640 [ 1513.268014] ? __fput+0x162/0x260 [ 1513.268016] ksys_ioctl+0x75/0x80 [ 1513.268017] __x64_sys_ioctl+0x1a/0x20 [ 1513.268019] do_syscall_64+0x5e/0x200 [ 1513.268021] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43 [Where things could go wrong] This seems unlikely to cause a regression [Other Info] SF: #00346036 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1991366 Title: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] Some Dell laptops where booting with Thunderbolt/USB4 devices connected the BIOS leaves some of the PCIe devices unconfigured. The kernel message shows "No bus number available for hot-added bridge". The connected devices can't be found. [Fix] Current linux PCI distribute the "spare" resources between hotplug ports on hot-add but have not done that upon the initial scan. The patches make the initial root bus scan path to do the same. The additional patches are just a small cleanups that can be applied separately too. [Test] 1. Power on the machine with Thunderbolt/USB4 devices connected. 2. Check the kernel message to see if "No bus number available for hot-added bridge" shows up or not. 3. Check if the Thunderbolt/USB4 devices works or not. [Where problems could occur] The patches only apply the same procedures on initial root bus scan which was not done. If the BIOS configures the PCI correctly, everything is OK. It only takes effect for the BIOS w/ unconfigured PCIe devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996071] 0001-s390-boot-add-secure-boot-trailer.patch
Default Comment by Bridge ** Attachment added: "0001-s390-boot-add-secure-boot-trailer.patch" https://bugs.launchpad.net/bugs/1996071/+attachment/5630390/+files/0001-s390-boot-add-secure-boot-trailer.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/1996071 Title: [UBUNTU 20.04] boot: Add secure boot trailer Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Bug description: Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+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 1996071] Re: [UBUNTU 20.04] boot: Add secure boot trailer
Ok, so it's actually like this ... (for focal) ** Attachment removed: "0001-s390-boot-add-secure-boot-trailer.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996071/+attachment/5630383/+files/0001-s390-boot-add-secure-boot-trailer.patch ** Patch added: "0001-s390-boot-add-secure-boot-trailer.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996071/+attachment/5630388/+files/0001-s390-boot-add-secure-boot-trailer.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/1996071 Title: [UBUNTU 20.04] boot: Add secure boot trailer Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Bug description: Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+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 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+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 1993148] Re: Support Icicle Kit reference design v2022.10
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993148 Title: Support Icicle Kit reference design v2022.10 Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Fix Committed Bug description: [ Impact ] * The Michochip PolarFire SoC on the Icicle Kit is an FPGA with 4 + 1 RISC-V cores. So the memory map and some peripherals depend on the FPGA design loaded. * Microchip releases reference designs and are upstreaming support for running Linux on it. Unfortunately the upcoming v2022.10 release changes the memory layout compared to earlier versions, but v6.1-rc1 contains patches for it. * We'd like to support the v2022.10 release and hopefully future versions by backporting these changes. [ Test Plan ] * Update the Icicle Kit to the v2022.10 reference design and check that the generic riscv64 kernel boots. [ Where problems could occur ] * Users who are running v2022.9 or older versions of the reference design may have trouble booting, but the Icicle Kit was never officially supported by Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993148/+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 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) 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/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+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 1996198] Re: Fix rfkill causing soft blocked wifi
** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu Kinetic) 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/1996198 Title: Fix rfkill causing soft blocked wifi Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-6.0 source package in Focal: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-6.0 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Need this patch in so a BIOS upgrade won't cause issues on HP laptops. commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a Author: Jorge Lopez Date: Fri Oct 28 10:55:27 2022 -0500 platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded strange char "^@" which printed out every second and makes login nearly impossible. Also the below messages were shown both in console and journal/dmesg every second: usb 1-3: Device not responding to setup address. usb 1-3: device not accepting address 4, error -71 usb 1-3: device descriptor read/all, error -71 usb usb1-port3: unable to enumerate USB device Wifi is soft blocked by checking rfkill. When unblocked manually, after few seconds it would be soft blocked again. So I was suspecting something triggered rfkill to soft block wifi. At the end it was fixed by removing hp_wmi module. The root cause is the way hp-wmi driver handles command 1B on post-2009 BIOS. In pre-2009 BIOS, command 1Bh return 0x4 to indicate that BIOS no longer controls the power for the wireless devices. Signed-off-by: Jorge Lopez Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468 Reviewed-by: Mario Limonciello Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com Cc: sta...@vger.kernel.org Reviewed-by: Hans de Goede Signed-off-by: Hans de Goede [Test case] test on a HP laptop with the new BIOS [Where problems could occur] from the commit: * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that * BIOS no longer controls the power for the wireless * devices. All features supported by this command will no * longer be supported. anyone running a laptop with obsolete pre-2009 BIOS probably won't notice the missing feature at this point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996198/+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 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
> Without linux-image-5.19.0-21-generic i915-fix the USB Live will never boot in an intel Tiger Lake/Alder Lake IGPU Indeed the live desktop installer fails to boot on a 12th intel cpu: I have lots of kernel backtraces in dmesg caused by nouveau driver. The kernel from the installer is 5.19.0-21. -- 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/1991704 Title: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Fix Released Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+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 1996071] Comment bridged from LTC Bugzilla
--- Comment From peter.oberparlei...@de.ibm.com 2022-11-10 10:24 EDT---
(In reply to comment #8)
> In the focal master-next tree file 'vmlinux.lds.S' is at a different
> location: 'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
> and the context is also slightly different.
>
> Would you please have a look at the attached backport for focal and confirm
> that it's correct?
> Since it has this add. block:
> "
> . = ALIGN(256);
> .bss : {
> _bss = . ;
> *(.bss)
> *(.bss.*)
> *(COMMON)
> . = ALIGN(8); /* For convenience during zeroing */
> _ebss = .;
> }
> "
The sb_trailer block needs to move to before the .bss definition, and
replaces the ALIGN(256) line. Otherwise kernel image sizes will be
unnecessarily increased by the size of the discarded bss section. It
should look something like this:
_compressed_start = .;
*(.vmlinux.bin.compressed)
_compressed_end = .;
- FILL(0xff);
- . = ALIGN(4096);
}
- . = ALIGN(256);
+
+#define SB_TRAILER_SIZE 32
+ /* Trailer needed for Secure Boot */
+ . += SB_TRAILER_SIZE; /* make sure .sb.trailer does not overwrite the
previous section */
+ . = ALIGN(4096) - SB_TRAILER_SIZE;
+ .sb.trailer : {
+ QUAD(0)
+ QUAD(0)
+ QUAD(0)
+ QUAD(0x00207a49504c)
+ }
+
.bss : {
_bss = . ;
*(.bss)
> Looks like we commented in parallel.
> Yes, backport will be helpful.
Ok, will try to work on that.
--
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/1996071
Title:
[UBUNTU 20.04] boot: Add secure boot trailer
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
New
Status in linux source package in Jammy:
New
Status in linux source package in Kinetic:
New
Bug description:
Description: boot: Add secure boot trailer
Symptom: Secure boot of Linux will no longer be possible with an
upcoming
IBM Z firmware update.
Problem: New IBM Z firmware requires signed bootable images to contain a
trailing data block with a specific format.
Solution: Add the trailing data block to the Linux kernel image.
Reproduction: Apply latest firmware, perform IPL with Secure Boot
enabled.
Fix: available upstream with
Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7
Preventive:yes
Date: 2022-10-27
Author:Peter Oberparleiter
Component: kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+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 1952823] Re: Screen blinks when entering suspend
I've not aware of this since 510 ** Changed in: oem-priority Assignee: jeremyszu (os369510) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1952823 Title: Screen blinks when entering suspend Status in OEM Priority Project: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: [Summary] The screen turns on for a moment when laptop is entering suspend. This issue happens on Dell Latitude 5421. [Steps to reproduce] 1. Enter suspend via power menu 2. Observe the display (Note that `rtcwake` may not able to reproduce this issue. `systemctl suspend` may reproduce this.) [Expected result] The screen should not turn back on if the system is going to suspend. [Actual result] When "Suspend" is clicked, screen turns off, then turns back on for a moment, then turns off before laptop entering suspend. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952823/+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 1995606] Re: Upgrade thermald to 2.5.1
** Description changed: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] - For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: + For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] - since the PL1 min/max is introduced, we may face the edge case in the future. + since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. + this may cause machines run like the old behavior that doesn't have PL1 min/max. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Incomplete Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscr
[Kernel-packages] [Bug 1996198] Re: Fix rfkill causing soft blocked wifi
unstable will get this after rebase to 6.1-rc5 ** Changed in: linux (Ubuntu) Status: New => 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/1996198 Title: Fix rfkill causing soft blocked wifi Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Bug description: [Impact] Need this patch in so a BIOS upgrade won't cause issues on HP laptops. commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a Author: Jorge Lopez Date: Fri Oct 28 10:55:27 2022 -0500 platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded strange char "^@" which printed out every second and makes login nearly impossible. Also the below messages were shown both in console and journal/dmesg every second: usb 1-3: Device not responding to setup address. usb 1-3: device not accepting address 4, error -71 usb 1-3: device descriptor read/all, error -71 usb usb1-port3: unable to enumerate USB device Wifi is soft blocked by checking rfkill. When unblocked manually, after few seconds it would be soft blocked again. So I was suspecting something triggered rfkill to soft block wifi. At the end it was fixed by removing hp_wmi module. The root cause is the way hp-wmi driver handles command 1B on post-2009 BIOS. In pre-2009 BIOS, command 1Bh return 0x4 to indicate that BIOS no longer controls the power for the wireless devices. Signed-off-by: Jorge Lopez Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468 Reviewed-by: Mario Limonciello Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com Cc: sta...@vger.kernel.org Reviewed-by: Hans de Goede Signed-off-by: Hans de Goede [Test case] test on a HP laptop with the new BIOS [Where problems could occur] from the commit: * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that * BIOS no longer controls the power for the wireless * devices. All features supported by this command will no * longer be supported. anyone running a laptop with obsolete pre-2009 BIOS probably won't notice the missing feature at this point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996198/+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 1996198] [NEW] Fix rfkill causing soft blocked wifi
Public bug reported: [Impact] Need this patch in so a BIOS upgrade won't cause issues on HP laptops. commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a Author: Jorge Lopez Date: Fri Oct 28 10:55:27 2022 -0500 platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded strange char "^@" which printed out every second and makes login nearly impossible. Also the below messages were shown both in console and journal/dmesg every second: usb 1-3: Device not responding to setup address. usb 1-3: device not accepting address 4, error -71 usb 1-3: device descriptor read/all, error -71 usb usb1-port3: unable to enumerate USB device Wifi is soft blocked by checking rfkill. When unblocked manually, after few seconds it would be soft blocked again. So I was suspecting something triggered rfkill to soft block wifi. At the end it was fixed by removing hp_wmi module. The root cause is the way hp-wmi driver handles command 1B on post-2009 BIOS. In pre-2009 BIOS, command 1Bh return 0x4 to indicate that BIOS no longer controls the power for the wireless devices. Signed-off-by: Jorge Lopez Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468 Reviewed-by: Mario Limonciello Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com Cc: sta...@vger.kernel.org Reviewed-by: Hans de Goede Signed-off-by: Hans de Goede [Test case] test on a HP laptop with the new BIOS [Where problems could occur] from the commit: * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that * BIOS no longer controls the power for the wireless * devices. All features supported by this command will no * longer be supported. anyone running a laptop with obsolete pre-2009 BIOS probably won't notice the missing feature at this point. ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Description changed: [Impact] Need this patch in so a BIOS upgrade won't cause issues on HP laptops. - platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi + commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a + Author: Jorge Lopez + Date: Fri Oct 28 10:55:27 2022 -0500 + + platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded strange char "^@" which printed out every second and makes login nearly impossible. Also the below messages were shown both in console and journal/dmesg every second: usb 1-3: Device not responding to setup address. usb 1-3: device not accepting address 4, error -71 usb 1-3: device descriptor read/all, error -71 usb usb1-port3: unable to enumerate USB device Wifi is soft blocked by checking rfkill. When unblocked manually, after few seconds it would be soft blocked again. So I was suspecting something triggered rfkill to soft block wifi. At the end it was fixed by removing hp_wmi module. The root cause is the way hp-wmi driver handles command 1B on post-2009 BIOS. In pre-2009 BIOS, command 1Bh return 0x4 to indicate that BIOS no longer controls the power for the wireless devices. Signed-off-by: Jorge Lopez Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468 Reviewed-by: Mario Limonciello Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com Cc: sta...@vger.kernel.org Reviewed-by: Hans de Goede Signed-off-by: Hans de Goede [Test case] test on a HP laptop with the new BIOS [Where problems could occur] from the commit: -* In pre-2009 BIOS, command 1Bh return 0x4 to indicate that -* BIOS no longer controls the power for the wireless -* devices. All features supported by this command will no -* longer be supported. + * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that + * BIOS no longer controls the power for the wireless + * devices. All features supported by this command will no + * longer be supported. anyone running a laptop with obsolete pre-2009 BIOS probably won't notice the missing feature at this point. -- 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/1996198 Title: Fix rfkill causing soft blocked wifi Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linu
[Kernel-packages] [Bug 1991365] Re: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU
** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1991365 Title: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] turbostat doesn't show the correct fields for RPL-S. This's a wrong column. usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,CPU%LPI,SYS%LPI [Fix] Add RPL-S support in turbostat [Test Case] 1. run "turbostat --list" 2. check the output, this is a correct column. usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,SMI,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CPU%c1,CPU%c6,CPU%c7,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,Totl%C0,Any%C0,GFX%C0,CPUGFX%,Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI,PkgWatt,CorWatt,GFXWatt,RAMWatt,PKG_%,RAM_% [Where problems could occur] Low, just add a devcie id to support RPL-S. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991365/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Hi Drew,
Since creating the TO912.sh script I have also upgraded to a GalaxyBook2
Pro (NP930XED) running 22.04 and the script was required (i.e. the
latest kernels don't automatically fix issue), but the script continues
to work fine for me on both headphones are speakers. Personally I would
recommend upgrading from the 5.15 kernel because it doesn't work fully
with the intel grpahics (im running 6.0.6-060006-generic now), but that
is unrelated. Here are the full steps I did again that work for me ...
I still have not figured out how to make the screen brightness control
functional on the book 2 pro, but also a different story...
- placed TO912.sh script and set as 777 +x
- Create daemon for boot
sudo gedit /etc/systemd/system/ionsound.service
Add text in file
[Unit]
Description=Custom Sound
[Service]
Type=idle
ExecStart={enter your path to script}/TO912.sh
[Install]
WantedBy=multi-user.target
sudo chmod 664 /etc/systemd/system/ionsound.service
- Create daemon for sleep exit
sudo gedit /etc/systemd/system/ionsoundsleep.service
Add text in file
[Unit]
Description=Custom Sound Sleep Fix
[Service]
Type=idle
ExecStart={enter your path to script}/TO912.sh
[Install]
WantedBy=suspend.target
sudo chmod 664 /etc/systemd/system/ionsoundsleep.service
- Activate daemons
sudo systemctl daemon-reload
sudo systemctl enable ionsound.service
sudo systemctl enable ionsoundsleep.service
Note, I left the names as Ion because I was too lazy to change, but
nothing in here is ion specific and this does work on your model. You
can change naming if you like as long as you change it everywhere...
For the kernel part, if you haven't already discovered the mainline tool for
kernel mgmt then I would highly recommend trying it
sudo add-apt-repository ppa:cappelikan/ppa -y
sudo apt install mainline -y
Launch mainline GUI and pick kernel to install
--
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/1851518
Title:
[950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
internal speakers, very very quiet on headphones
Status in Linux:
New
Status in linux package in Ubuntu:
Fix Released
Bug description:
I've been googling this issue for 10's of hours and tried many things.
Relase of Ubuntu: 19.10
Expected outcome: Music plays on the internal speakers and headphones.
Actual outcome: I can barely hear audio using headphones with volume
turned up to 150%. Absolutely nothing comes out of the speakers. (The
speakers sound great under Windows 10.)
Complete alsa-info output is attached, but here are some snippets:
!!DMI Information
!!---
Manufacturer: SAMSUNG ELECTRONICS CO., LTD.
Product Name: 950SBE/951SBE
Product Version: P06RES
Firmware Version: P06RES.075.190529.SP
Board Vendor: SAMSUNG ELECTRONICS CO., LTD.
Board Name:NP950SBE-K01US
!!Kernel Information
!!--
Kernel release:5.3.0-19-generic
Operating System: GNU/Linux
Architecture: x86_64
Processor: x86_64
SMP Enabled: Yes
!!ALSA Version
!!
Driver version: k5.3.0-19-generic
Library version:1.1.9
Utilities version: 1.1.9
!!Loaded ALSA modules
!!---
snd_hda_intel
!!Sound Servers on this system
!!
Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes
!!Soundcards recognised by ALSA
!!-
0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177
!!PCI Soundcards installed in the system
!!--
00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
High Definition Audio Controller (rev 11)
!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!---
00:1f.3 0401: 8086:9dc8 (rev 11)
DeviceName: Onboard - Sound
!!HDA-Intel Codec information
!!---
--startcollapse--
Codec: Realtek ALC298
Address: 0
AFG Function Id: 0x1 (unsol 1)
Vendor Id: 0x10ec0298
Subsystem Id: 0x144dc812
Revision Id: 0x100103
No Modem Function Group found
Default PCM:
rates [0x60]: 44100 480
[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add secure boot trailer
Looks like we commented in parallel. Yes, backport will be helpful. -- 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/1996071 Title: [UBUNTU 20.04] boot: Add secure boot trailer Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Bug description: Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+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 1996071] Re: [UBUNTU 20.04] boot: Add secure boot trailer
In the focal master-next tree file 'vmlinux.lds.S' is at a different location:
'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
and the context is also slightly different.
Would you please have a look at the attached backport for focal and confirm
that it's correct?
Since it has this add. block:
"
. = ALIGN(256);
.bss : {
_bss = . ;
*(.bss)
*(.bss.*)
*(COMMON)
. = ALIGN(8); /* For convenience during zeroing */
_ebss = .;
}
"
Cherry-pick was fine for kinetic and jammy.
** Patch added: "0001-s390-boot-add-secure-boot-trailer.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996071/+attachment/5630383/+files/0001-s390-boot-add-secure-boot-trailer.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/1996071
Title:
[UBUNTU 20.04] boot: Add secure boot trailer
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
New
Status in linux source package in Jammy:
New
Status in linux source package in Kinetic:
New
Bug description:
Description: boot: Add secure boot trailer
Symptom: Secure boot of Linux will no longer be possible with an
upcoming
IBM Z firmware update.
Problem: New IBM Z firmware requires signed bootable images to contain a
trailing data block with a specific format.
Solution: Add the trailing data block to the Linux kernel image.
Reproduction: Apply latest firmware, perform IPL with Secure Boot
enabled.
Fix: available upstream with
Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7
Preventive:yes
Date: 2022-10-27
Author:Peter Oberparleiter
Component: kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
sigh, this will land in -1022 -- 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/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
This was at least committed already to Kinetic. Potentially released by now... ** Changed in: linux (Ubuntu Kinetic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => 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/1988797 Title: pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- Fatal), type=Transaction Layer, (Requester ID) Status in HWE Next: Confirmed Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: My kernel log periodically bursts with: [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.598564] pcieport :00:1b.0:[20] UnsupReq (First) [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.620296] pcieport :00:1b.0:[20] UnsupReq (First) [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.641867] pcieport :00:1b.0:[20] UnsupReq (First) [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.663803] pcieport :00:1b.0:[20] UnsupReq (First) [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.686267] pcieport :00:1b.0:[20] UnsupReq (First) [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 0152 This has happened even since I got the machine. It also happened with 5.15. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2477 F wireplumber /dev/snd/seq:dan2474 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 6 13:52:35 2022 InstallationDate: Installed on 2022-07-20 (47 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.cha
[Kernel-packages] [Bug 1995453] Re: Add some ACPI device IDs for Intel HID device
this is already in upstream master, so unstable will get it on rebase to 6.1-rc5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995453 Title: Add some ACPI device IDs for Intel HID device Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: New Status in linux source package in Kinetic: New Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake [Fix] ACPI devices IDs are add the the related Intel HID devices on these platforms can work. [Test] Verified the Intel HID events can work such as power button for suspend and wake. [Where problems could occur] Add the ACPI device IDs for support Intel HID devices, so chance of problems should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995453/+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 1996071] Comment bridged from LTC Bugzilla
--- Comment From peter.oberparlei...@de.ibm.com 2022-11-10 08:55 EDT--- (In reply to comment #6) > So commit aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add secure > boot trailer" was just upstream accepted with v6.1-rc3. > And it got tagged for upstream stable with: > "Cc: # 5.2+" > That means that it will ideally automatically land over time in all Ubuntu > kernels, down to focal's 5.4. Unfortunately the automated stable backport to v5.4, v5.10, and v5.14 failed because the source file that is modified by this patch was moved around: https://lore.kernel.org/stable/166719900013...@kroah.com/ > But since this bug is marked as critical, the patch is relatively short, > traceable and s390x-specific, I'll go ahead and submit this patch for Jammy > and Focal ahead of upstream stable. In addition to the work you plan, I could provide an adjusted stable backport for the upstream targets for which automatic backport failed. Would this help get this patch into any more Ubuntu versions? -- 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/1996071 Title: [UBUNTU 20.04] boot: Add secure boot trailer Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Bug description: Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+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 1990161] Re: Fix RPL-S support on powercap/intel_rapl
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1990161 Title: Fix RPL-S support on powercap/intel_rapl Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] proc_thermal driver is not loaded [Fix] Add RPL-S id on device id table of powercap/intel_rapl. [Test Case] 1. sudo checkbox-cli run com.canonical.certification::miscellanea/proc_thermal [Where problems could occur] Low, only add RPL-S id on powercap/intel_rap but may lack of RPL-S features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990161/+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 1991974] Re: AMD Yellow Carp system hang on HDMI plug in/out over HP hook2 docking
** Changed in: linux (Ubuntu Jammy) 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/1991974 Title: AMD Yellow Carp system hang on HDMI plug in/out over HP hook2 docking Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] AMD Yellow Carp system hang on HDMI plug in/out over dock station. [Fix] 5 patches from mainline kernel v5.16 to be backported. [Test Case] Plug and unplug HDMI cable connected external monitor on a docking station connected to HP Lockheed platform to try trigger system hang. [Where problems could occur] This series tries to address null state of MST link encoder, and no know fix commits for them ever since till current mainline HEAD. [Other Info] While this is already available in v5.16 kernel and on, only 5.15 and oem-5.14 are nominated for fix. == original bug description == In order to resolve system hang during docking scenario with HDMI plug in/out, these patches are needed into hwe-5.15. v5.16 43dc2ad5 drm/amd/display: Fix MST link encoder availability check e3ab29aa drm/amd/display: Fix for link encoder access for MST 7fb52632 drm/amd/display: FEC configuration for dpia links ed0ffb5d drm/amd/display: FEC configuration for dpia links in MST mode c9beecc5 drm/amd/display: Add work around for tunneled MST To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991974/+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 1990272] Re: PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0], AER UnsupReq
I'm also experiencing this issue on a ThinkPad X1 Extreme Gen 5, and it actually causes some problems more than just logs being spammed. First of all, I noticed that this only happens after a reboot when I have an external display connected via USB Type-C. The other end can be HDMI 2.0 or DisplayPort 1.2/1.4 (also tested an LG that has a Type-C port and the laptop doesn't detect it at all). When this happens, my Lenovo Ethernet adapter [1] (Realtek 0bda:8156) has to be reconnected to be detected. The same thing happens even if I reboot into Windows. As a result, I have to do cold boots currently to make sure I have Internet. Another problem it causes is that after a shutdown in Linux, if I connect a USB Type-C drive and boot up the laptop, it won't be detected by BIOS. I have an Orico M2PAC3-G20 [2] and I have to connect it first then reboot to see it in boot menu. It can always be detected after a shutdown in Windows by the way. I'm running Arch and I have this issue with both mainline 6.0.7 and LTS 5.15.77 kernels. I also tested nvidia-dkms, nvidia-open-dkms, and nouveau but unfortunately it seemed unrelated. Things like pci=nommconf, pcie_aspm=off, disabling Thunderbolt 4 in BIOS didn't make any difference either. PS: Not sure if [3] is the same issue. [1] https://www.lenovo.com/us/en/p/4x91h17795 [2] https://www.orico.cc/us/product/detail/7207.html [3] https://bugzilla.kernel.org/show_bug.cgi?id=215453 ** Bug watch added: Linux Kernel Bug Tracker #215453 https://bugzilla.kernel.org/show_bug.cgi?id=215453 -- 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/1990272 Title: PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0],AER UnsupReq Status in linux package in Ubuntu: Confirmed Bug description: My dmesg is getting spammed by these AER errors. The laptop (Lenovo X1 Extreme Gen 5, Intel Core i7-12700H) is otherwise working fine. The errors come in random waves of 60..160 back-to-back errors with an interval of 130..140 microseconds. Device [8086:51b0] is the PCI/thunderbolt bridge. [ 20.086628] pcieport :00:1d.0: AER: Uncorrected (Non-Fatal) error received: :00:1d.0 [ 20.086671] pcieport :00:1d.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ 20.086680] pcieport :00:1d.0: device [8086:51b0] error status/mask=0010/4000 [ 20.086688] pcieport :00:1d.0:[20] UnsupReq (First) [ 20.086694] pcieport :00:1d.0: AER: TLP Header: 3400 2052 [ 20.086810] thunderbolt :22:00.0: AER: can't recover (no error_detected callback) [ 20.086846] xhci_hcd :56:00.0: AER: can't recover (no error_detected callback) [ 20.086878] pcieport :00:1d.0: AER: device recovery failed [ 20.106033] pcieport :00:1d.0: AER: Multiple Uncorrected (Non-Fatal) error received: :00:1d.0 [ 20.106082] pcieport :00:1d.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ 20.106093] pcieport :00:1d.0: device [8086:51b0] error status/mask=0010/4000 [ 20.106101] pcieport :00:1d.0:[20] UnsupReq (First) [ 20.106108] pcieport :00:1d.0: AER: TLP Header: 3400 2052 [ 20.106219] thunderbolt :22:00.0: AER: can't recover (no error_detected callback) [ 20.106257] xhci_hcd :56:00.0: AER: can't recover (no error_detected callback) [ 20.106301] pcieport :00:1d.0: AER: device recovery failed Another wave was at 418s, 440s, 1168s, etc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: me 1827 F pulseaudio /dev/snd/controlC0: me 1827 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Sep 20 13:34:43 2022 InstallationDate: Installed on 2022-08-31 (19 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 21DE001QMH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=d4a7fdda-30e3-439b-b327-e87d7b2bc81e ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade
[Kernel-packages] [Bug 1996069] Re: [UBUNTU 20.04] zipl: Add secure boot trailer (s390-tools part)
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) ** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) ** Also affects: s390-tools-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => High -- 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/1996069 Title: [UBUNTU 20.04] zipl: Add secure boot trailer (s390-tools part) Status in Ubuntu on IBM z Systems: New Status in s390-tools package in Ubuntu: New Status in s390-tools-signed package in Ubuntu: New Bug description: Description: zipl: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires all signed boot images to contain a trailing data block with a specific format. Solution: Add trailing data block to the zipl stage 3 boot loader image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: Available upstream with Upstream-ID: 5768d55a08e163f718bd87498b9e763687ae7137 Upstream-Description: zipl/boot: add secure boot trailer This patch enhances the zipl stage3 loader image adding a trailer as required for secure boot by future firmware versions. Note: with the change in this patch the padding via objcopy command line options is replaced by padding via linker script directives with the same effect. Signed-off-by: Peter Oberparleiter Signed-off-by: Jan Hoeppner Signed-off-by: Peter Oberparleiter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996069/+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 1996092] 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/1996092 Title: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) Status in linux package in Ubuntu: Confirmed Bug description: I have old MacBook with broken main Graphic Controller (a well-known hardware issue https://discussions.apple.com/thread/251049873 ). So I switch to use Integrated Graphics Controller. I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot (freeze during boot). I looked for latest updated packages and I found: linux-image-4.15.0-192-generic 4.15.0-192.203 amd64 => linux-image-4.15.0-193-generic 4.15.0-193.204 amd64 So, MacBook boots linux-image-4.15.0-192-generic correctly, but it doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) I could not find which change is included in newer kernels that did this issue. How could I support about this issue? PD: Added bellow some additional information and attached 'lspci-vnvn.log' file $ sudo lshw macbookpro description: Notebook product: MacBookPro8,2 (System SKU#) vendor: Apple Inc. ... lspci-vnvn.log 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00dc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+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 1996174] Re: CVE-2016-3672 in ubuntu_cve_kernel failed with J-oem-6.0
This CVE is relatively old, we already got this commit in our tree:
$ git tag --contain 8b8addf891d
...
Ubuntu-oem-6.0-6.0.0-1005.5
Ubuntu-oem-6.0-6.0.0-1006.6
Ubuntu-oem-6.0-6.0.0-1007.7
It's unclear why this is still failing.
** Also affects: linux-oem-6.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1996174
Title:
CVE-2016-3672 in ubuntu_cve_kernel failed with J-oem-6.0
Status in ubuntu-kernel-tests:
New
Status in linux-oem-6.0 package in Ubuntu:
New
Bug description:
Issue found with J-oem-6.0.0-1007
This is not a regression as this failure can be found with older
kernel (6.0.0-1004.4) as well
Test log:
STARTubuntu_cve_kernel.CVE-2016-3672
ubuntu_cve_kernel.CVE-2016-3672timestamp=1666797878timeout=900
localtime=Oct 26 15:24:38
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_cve_kernel.CVE-2016-3672', 'ubuntu_cve_kernel.CVE-2016-3672')
Waiting for pid 55210 for 900 seconds
System python is too old, crash handling disabled
*** CVE-2016-3672 ***
Running 'make -C
/home/ubuntu/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3672 check'
[stdout] make: Entering directory
'/home/ubuntu/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3672'
[stdout] gcc -o show_maps show_maps.c -m32
[stdout] sudo -u ubuntu ./check.sh
[stdout] make: Leaving directory
'/home/ubuntu/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3672'
[stderr] make: *** [Makefile:11: check] Error 1
A manual test shows this test case is a bit flaky for some reason:
ubuntu@curly:~/autotest-client-tests/ubuntu_cve_kernel/cves/CVE-2016-3672$
for i in {1..10}; do make check; echo $?; make clean; done
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
make: *** [Makefile:11: check] Error 1
2
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
make: *** [Makefile:11: check] Error 1
2
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
I don't recall we have this issue with other kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1996174/+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 1996071] Re: [UBUNTU 20.04] boot: Add secure boot trailer
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996071 Title: [UBUNTU 20.04] boot: Add secure boot trailer Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Bug description: Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+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 1996092] Re: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204, 4.15.0-194.205, 4.15.0-196.207)
I did 'apport-collect 1996092' in correct linux-image-4.15.0-192-generic but I can not boot newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) ** Changed in: linux (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996092 Title: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) Status in linux package in Ubuntu: New Bug description: I have old MacBook with broken main Graphic Controller (a well-known hardware issue https://discussions.apple.com/thread/251049873 ). So I switch to use Integrated Graphics Controller. I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot (freeze during boot). I looked for latest updated packages and I found: linux-image-4.15.0-192-generic 4.15.0-192.203 amd64 => linux-image-4.15.0-193-generic 4.15.0-193.204 amd64 So, MacBook boots linux-image-4.15.0-192-generic correctly, but it doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) I could not find which change is included in newer kernels that did this issue. How could I support about this issue? PD: Added bellow some additional information and attached 'lspci-vnvn.log' file $ sudo lshw macbookpro description: Notebook product: MacBookPro8,2 (System SKU#) vendor: Apple Inc. ... lspci-vnvn.log 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00dc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+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 1996092] 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/1996092 Title: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) Status in linux package in Ubuntu: New Bug description: I have old MacBook with broken main Graphic Controller (a well-known hardware issue https://discussions.apple.com/thread/251049873 ). So I switch to use Integrated Graphics Controller. I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot (freeze during boot). I looked for latest updated packages and I found: linux-image-4.15.0-192-generic 4.15.0-192.203 amd64 => linux-image-4.15.0-193-generic 4.15.0-193.204 amd64 So, MacBook boots linux-image-4.15.0-192-generic correctly, but it doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) I could not find which change is included in newer kernels that did this issue. How could I support about this issue? PD: Added bellow some additional information and attached 'lspci-vnvn.log' file $ sudo lshw macbookpro description: Notebook product: MacBookPro8,2 (System SKU#) vendor: Apple Inc. ... lspci-vnvn.log 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00dc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+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 1961076] Re: linux-hwe-5.4 ADT test failure (ubuntu_stress_smoke_test) with linux-hwe-5.4/5.4.0-100.113~18.04.1
Fix committed to stress-ng: https://github.com/ColinIanKing/stress- ng/commit/79b54d692ea8e422efa5dee72c7c397d18b237db -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1961076 Title: linux-hwe-5.4 ADT test failure (ubuntu_stress_smoke_test) with linux- hwe-5.4/5.4.0-100.113~18.04.1 Status in Stress-ng: New Status in ubuntu-kernel-tests: New Status in linux-hwe-5.4 package in Ubuntu: New Status in linux-hwe-5.4 source package in Bionic: New Bug description: The 'dev-shm' stress-ng test is failing with bionic/linux-hwe-5.4 5.4.0-100.113~18.04.1 on ADT, only on ppc64el. Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/l/linux-hwe-5.4/20220216_115416_c1d6c@/log.gz 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] stress-ng 0.13.11 g48be8ff4ffc4 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] system: Linux autopkgtest 5.4.0-100-generic #113~18.04.1-Ubuntu SMP Mon Feb 7 15:02:55 UTC 2022 ppc64le 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] RAM total: 7.9G, RAM free: 3.3G, swap free: 1023.9M 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] 4 processors online, 4 processors configured 11:35:08 DEBUG| [stdout] stress-ng: info: [26897] setting to a 5 second run per stressor 11:35:08 DEBUG| [stdout] stress-ng: info: [26897] dispatching hogs: 4 dev-shm 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] cache allocate: using cache maximum level L1 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] cache allocate: shared cache buffer size: 32K 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] starting stressors 11:35:08 DEBUG| [stdout] stress-ng: debug: [26899] stress-ng-dev-shm: started [26899] (instance 0) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26900] stress-ng-dev-shm: started [26900] (instance 1) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: started [26901] (instance 2) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26902] stress-ng-dev-shm: started [26902] (instance 3) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] 4 stressors started 11:35:08 DEBUG| [stdout] stress-ng: debug: [26899] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 0) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26902] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 3) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 2) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26900] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 1) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] (stress-ng-dev-shm) terminated on signal: 9 (Killed) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] (stress-ng-dev-shm) was killed by the OOM killer 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] terminated 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] (stress-ng-dev-shm) terminated on signal: 9 (Killed) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] (stress-ng-dev-shm) was possibly killed by the OOM killer 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] terminated 11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: exited [26901] (instance 2) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26901] terminated 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] (stress-ng-dev-shm) terminated on signal: 9 (Killed) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] (stress-ng-dev-shm) was killed by the OOM killer 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] terminated 11:35:08 DEBUG| [stdout] stress-ng: info: [26897] successful run completed in 5.06s 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 0 corrupted bogo-ops counter, 14 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 0 hash error in bogo-ops counter and run flag, 2146579844 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 1 corrupted bogo-ops counter, 13 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 1 hash error in bogo-ops counter and run flag, 1093487894 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 3 corrupted bogo-ops counter, 13 vs 0 11:35:08 DEBUG| [stdout] info: 5 failures reached, aborting stress process 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 3 hash error in bogo-ops counter and run flag, 1093487894 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] metrics-check: stressor metrics corrupted, data is compromised 11:35:08 DEBUG| [stdout] 11:35:08 DEBUG| [stdout]
[Kernel-packages] [Bug 1996092] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1996092/+attachment/5630246/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996092 Title: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) Status in linux package in Ubuntu: New Bug description: I have old MacBook with broken main Graphic Controller (a well-known hardware issue https://discussions.apple.com/thread/251049873 ). So I switch to use Integrated Graphics Controller. I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot (freeze during boot). I looked for latest updated packages and I found: linux-image-4.15.0-192-generic 4.15.0-192.203 amd64 => linux-image-4.15.0-193-generic 4.15.0-193.204 amd64 So, MacBook boots linux-image-4.15.0-192-generic correctly, but it doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) I could not find which change is included in newer kernels that did this issue. How could I support about this issue? PD: Added bellow some additional information and attached 'lspci-vnvn.log' file $ sudo lshw macbookpro description: Notebook product: MacBookPro8,2 (System SKU#) vendor: Apple Inc. ... lspci-vnvn.log 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00dc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+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 1996092] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1996092/+attachment/5630251/+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/1996092 Title: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) Status in linux package in Ubuntu: New Bug description: I have old MacBook with broken main Graphic Controller (a well-known hardware issue https://discussions.apple.com/thread/251049873 ). So I switch to use Integrated Graphics Controller. I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot (freeze during boot). I looked for latest updated packages and I found: linux-image-4.15.0-192-generic 4.15.0-192.203 amd64 => linux-image-4.15.0-193-generic 4.15.0-193.204 amd64 So, MacBook boots linux-image-4.15.0-192-generic correctly, but it doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) I could not find which change is included in newer kernels that did this issue. How could I support about this issue? PD: Added bellow some additional information and attached 'lspci-vnvn.log' file $ sudo lshw macbookpro description: Notebook product: MacBookPro8,2 (System SKU#) vendor: Apple Inc. ... lspci-vnvn.log 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00dc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+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 1996092] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1996092/+attachment/5630250/+files/RfKill.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/1996092 Title: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) Status in linux package in Ubuntu: New Bug description: I have old MacBook with broken main Graphic Controller (a well-known hardware issue https://discussions.apple.com/thread/251049873 ). So I switch to use Integrated Graphics Controller. I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot (freeze during boot). I looked for latest updated packages and I found: linux-image-4.15.0-192-generic 4.15.0-192.203 amd64 => linux-image-4.15.0-193-generic 4.15.0-193.204 amd64 So, MacBook boots linux-image-4.15.0-192-generic correctly, but it doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) I could not find which change is included in newer kernels that did this issue. How could I support about this issue? PD: Added bellow some additional information and attached 'lspci-vnvn.log' file $ sudo lshw macbookpro description: Notebook product: MacBookPro8,2 (System SKU#) vendor: Apple Inc. ... lspci-vnvn.log 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00dc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+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 1996092] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1996092/+attachment/5630249/+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/1996092 Title: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) Status in linux package in Ubuntu: New Bug description: I have old MacBook with broken main Graphic Controller (a well-known hardware issue https://discussions.apple.com/thread/251049873 ). So I switch to use Integrated Graphics Controller. I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot (freeze during boot). I looked for latest updated packages and I found: linux-image-4.15.0-192-generic 4.15.0-192.203 amd64 => linux-image-4.15.0-193-generic 4.15.0-193.204 amd64 So, MacBook boots linux-image-4.15.0-192-generic correctly, but it doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) I could not find which change is included in newer kernels that did this issue. How could I support about this issue? PD: Added bellow some additional information and attached 'lspci-vnvn.log' file $ sudo lshw macbookpro description: Notebook product: MacBookPro8,2 (System SKU#) vendor: Apple Inc. ... lspci-vnvn.log 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00dc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+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 1996092] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1996092/+attachment/5630252/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996092 Title: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) Status in linux package in Ubuntu: New Bug description: I have old MacBook with broken main Graphic Controller (a well-known hardware issue https://discussions.apple.com/thread/251049873 ). So I switch to use Integrated Graphics Controller. I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot (freeze during boot). I looked for latest updated packages and I found: linux-image-4.15.0-192-generic 4.15.0-192.203 amd64 => linux-image-4.15.0-193-generic 4.15.0-193.204 amd64 So, MacBook boots linux-image-4.15.0-192-generic correctly, but it doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) I could not find which change is included in newer kernels that did this issue. How could I support about this issue? PD: Added bellow some additional information and attached 'lspci-vnvn.log' file $ sudo lshw macbookpro description: Notebook product: MacBookPro8,2 (System SKU#) vendor: Apple Inc. ... lspci-vnvn.log 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00dc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+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 1996092] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1996092/+attachment/5630248/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996092 Title: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) Status in linux package in Ubuntu: New Bug description: I have old MacBook with broken main Graphic Controller (a well-known hardware issue https://discussions.apple.com/thread/251049873 ). So I switch to use Integrated Graphics Controller. I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot (freeze during boot). I looked for latest updated packages and I found: linux-image-4.15.0-192-generic 4.15.0-192.203 amd64 => linux-image-4.15.0-193-generic 4.15.0-193.204 amd64 So, MacBook boots linux-image-4.15.0-192-generic correctly, but it doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) I could not find which change is included in newer kernels that did this issue. How could I support about this issue? PD: Added bellow some additional information and attached 'lspci-vnvn.log' file $ sudo lshw macbookpro description: Notebook product: MacBookPro8,2 (System SKU#) vendor: Apple Inc. ... lspci-vnvn.log 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00dc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+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 1996092] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1996092/+attachment/5630244/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996092 Title: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) Status in linux package in Ubuntu: New Bug description: I have old MacBook with broken main Graphic Controller (a well-known hardware issue https://discussions.apple.com/thread/251049873 ). So I switch to use Integrated Graphics Controller. I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot (freeze during boot). I looked for latest updated packages and I found: linux-image-4.15.0-192-generic 4.15.0-192.203 amd64 => linux-image-4.15.0-193-generic 4.15.0-193.204 amd64 So, MacBook boots linux-image-4.15.0-192-generic correctly, but it doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) I could not find which change is included in newer kernels that did this issue. How could I support about this issue? PD: Added bellow some additional information and attached 'lspci-vnvn.log' file $ sudo lshw macbookpro description: Notebook product: MacBookPro8,2 (System SKU#) vendor: Apple Inc. ... lspci-vnvn.log 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00dc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+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 1996092] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1996092/+attachment/5630245/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996092 Title: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) Status in linux package in Ubuntu: New Bug description: I have old MacBook with broken main Graphic Controller (a well-known hardware issue https://discussions.apple.com/thread/251049873 ). So I switch to use Integrated Graphics Controller. I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot (freeze during boot). I looked for latest updated packages and I found: linux-image-4.15.0-192-generic 4.15.0-192.203 amd64 => linux-image-4.15.0-193-generic 4.15.0-193.204 amd64 So, MacBook boots linux-image-4.15.0-192-generic correctly, but it doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) I could not find which change is included in newer kernels that did this issue. How could I support about this issue? PD: Added bellow some additional information and attached 'lspci-vnvn.log' file $ sudo lshw macbookpro description: Notebook product: MacBookPro8,2 (System SKU#) vendor: Apple Inc. ... lspci-vnvn.log 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00dc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+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 1996092] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1996092/+attachment/5630247/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996092 Title: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) Status in linux package in Ubuntu: New Bug description: I have old MacBook with broken main Graphic Controller (a well-known hardware issue https://discussions.apple.com/thread/251049873 ). So I switch to use Integrated Graphics Controller. I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot (freeze during boot). I looked for latest updated packages and I found: linux-image-4.15.0-192-generic 4.15.0-192.203 amd64 => linux-image-4.15.0-193-generic 4.15.0-193.204 amd64 So, MacBook boots linux-image-4.15.0-192-generic correctly, but it doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) I could not find which change is included in newer kernels that did this issue. How could I support about this issue? PD: Added bellow some additional information and attached 'lspci-vnvn.log' file $ sudo lshw macbookpro description: Notebook product: MacBookPro8,2 (System SKU#) vendor: Apple Inc. ... lspci-vnvn.log 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00dc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+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 1996092] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1996092/+attachment/5630243/+files/Lsusb.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/1996092 Title: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) Status in linux package in Ubuntu: New Bug description: I have old MacBook with broken main Graphic Controller (a well-known hardware issue https://discussions.apple.com/thread/251049873 ). So I switch to use Integrated Graphics Controller. I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot (freeze during boot). I looked for latest updated packages and I found: linux-image-4.15.0-192-generic 4.15.0-192.203 amd64 => linux-image-4.15.0-193-generic 4.15.0-193.204 amd64 So, MacBook boots linux-image-4.15.0-192-generic correctly, but it doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) I could not find which change is included in newer kernels that did this issue. How could I support about this issue? PD: Added bellow some additional information and attached 'lspci-vnvn.log' file $ sudo lshw macbookpro description: Notebook product: MacBookPro8,2 (System SKU#) vendor: Apple Inc. ... lspci-vnvn.log 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00dc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+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
