[Kernel-packages] [Bug 1995957] Re: Add cs35l41 firmware loading support
** Tags added: kern-4858 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1995957 Title: Add cs35l41 firmware loading support Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: New 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: Won't Fix Status in linux-firmware source package in Jammy: Confirmed Status in linux-oem-5.17 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-firmware source package in Kinetic: Confirmed 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] Speakers on some laptops are rather quiet even with max volume. [Fix] Loading firmware to make cs35l41 speaker amplifier really work. [Test] With the fix applied, the speaker has become really loud as intended. [Where problems could occur] Most commits are refactoring codes on both ASoC and HDA parts, so things can be missed. Other than that, the change is strictly limited to cs35l41, so the regression scope is rather narrow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996134] Re: test_resolved_domain_restricted_dns in networkd-test.py from systemd ADT failed with J-oem-6.0.0-1007
The offending line is: 678 out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) With -1006: $ sudo pdb3 ./networkd-test.py > /home/ubuntu/systemd-249.11/test/networkd-test.py(21)() -> import errno (Pdb) b 678 Breakpoint 1 at /home/ubuntu/systemd-249.11/test/networkd-test.py:678 (Pdb) c systemd-network:x:100:102:systemd Network Management,,,:/run/systemd:/usr/sbin/nologin test_bridge_init (__main__.BridgeTest) ... ok test_bridge_port_priority (__main__.BridgeTest) ... ok test_bridge_port_priority_set_zero (__main__.BridgeTest) It should be possible to set the bridge port priority to 0 ... ok test_bridge_port_property (__main__.BridgeTest) Test the "[Bridge]" section keys ... ok test_coldplug_dhcp_ip4_only (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers ... > /home/ubuntu/systemd-249.11/test/networkd-test.py(678)test_resolved_domain_restricted_dns() -> out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) (Pdb) (in another terminal) ubuntu@curly:~$ resolvectl query math.lab math.lab: 10.241.3.3 -- link: testvpnrouter -- Information acquired via protocol DNS in 10.4732s. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network With -1007 $ sudo pdb3 ./networkd-test.py > /home/ubuntu/systemd-249.11/test/networkd-test.py(21)() -> import errno (Pdb) b 678 Breakpoint 1 at /home/ubuntu/systemd-249.11/test/networkd-test.py:678 (Pdb) c systemd-network:x:100:102:systemd Network Management,,,:/run/systemd:/usr/sbin/nologin test_bridge_init (__main__.BridgeTest) ... ok test_bridge_port_priority (__main__.BridgeTest) ... ok test_bridge_port_priority_set_zero (__main__.BridgeTest) It should be possible to set the bridge port priority to 0 ... ok test_bridge_port_property (__main__.BridgeTest) Test the "[Bridge]" section keys ... ok test_coldplug_dhcp_ip4_only (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers ... > /home/ubuntu/systemd-249.11/test/networkd-test.py(678)test_resolved_domain_restricted_dns() -> out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) (Pdb) (in another terminal) ubuntu@curly:~$ resolvectl query math.lab math.lab: resolve call failed: Lookup failed due to system error: No route to host ** Tags added: 6.0 jammy oem sru-20221010 -- 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/1996134 Title: test_resolved_domain_restricted_dns in networkd-test.py from systemd ADT failed with J-oem-6.0.0-1007 Status in ubuntu-kernel-tests: New Status in linux-oem-6.0 package in Ubuntu: New Status in linux-oem-6.0 source package in Jammy: New Bug description: This issue does not exist with J-oem-6.0.0-1006 With systemd 249.11-0ubuntu3.6 ubuntu@curly:~/systemd-249.11/test$ sudo ./networkd-test.py ; uname -a systemd-network:x:100:102:systemd Network Management,,,:/run/systemd:/usr/sbin/nologin test_bridge_init (__main__.BridgeTest) ... ok test_bridge_port_priority (__main__.BridgeTest) ... ok test_bridge_port_priority_set_zero (__main__.BridgeTest) It should be possible to set the bridge port priority to 0 ... ok test_bridge_port_property (__main__.BridgeTest) Test the "[Bridge]" section keys ... ok test_coldplug_dhcp_ip4_only (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers ... ERROR test_resolved_etc_hosts (__main__.DnsmasqClientTest) resolved queries to /etc/hosts ... ok test_route_only_dns (__main__.DnsmasqClientTest) ... ok
[Kernel-packages] [Bug 1946433] Re: Can only reach PC3 when ethernet is plugged r8169
This bug is awaiting verification that the linux-oem-5.17/5.17.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1946433 Title: Can only reach PC3 when ethernet is plugged r8169 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid 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: Confirmed Status in linux-oem-5.13 source package in Kinetic: Invalid 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] System only can reach PC3, and it affects power consumption alot. [Fix] Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state issue, but also fixes network speed issue. V7: https://patchwork.kernel.org/project/netdevbpf/patch/20211016075442.650311-5-kai.heng.f...@canonical.com/ V6: https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/ [Test] Verified on 2 different systems which has PC state issue and has network speed issue, these patches fix both issues. [Where problems could occur] It toggles ASPM on and off depends on the network traffic during runtime, I don't think it'll lead to any regressions. Some potential issues have been addressed during the patch submitting. It's v6 now and accepted by upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991365] Re: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU
This bug is awaiting verification that the linux-oem-5.17/5.17.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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: 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 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] 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 1995453] Re: Add some ACPI device IDs for Intel HID device
This bug is awaiting verification that the linux-oem-5.17/5.17.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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: New 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 1992714] Re: [SRU] SoF for RPL platform support
The log in #12 shows ``` Nov 09 10:42:51 ubuntu kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: Parent card not yet available, widget card binding deferred Nov 09 10:42:51 ubuntu kernel: snd_hda_codec_hdmi ehdaudio0D2: failed to create hda codec -12 Nov 09 10:42:51 ubuntu kernel: snd_hda_codec_hdmi ehdaudio0D2: ASoC: error at snd_soc_component_probe on ehdaudio0D2: -12 Nov 09 10:42:51 ubuntu kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to instantiate card -12 Nov 09 10:42:51 ubuntu kernel: skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -12 ``` The -12 indicates -ENOMEM, but I can't see it anymore after I add some debug messages for the reason of -ENOMEM. Not it shows ``` [4.973481] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: Parent card not yet available, widget card binding deferred [5.002339] typec port0: bound usb3-port2 (ops connector_ops) [5.002345] typec port0: bound usb2-port1 (ops connector_ops) [5.032874] skl_hda_dsp_generic skl_hda_dsp_generic: snd_hda_codec_device_new: entry [5.044347] skl_hda_dsp_generic skl_hda_dsp_generic: snd_hda_codec_device_new: entry [5.051784] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC3254: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [5.051789] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [5.051791] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [5.051793] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [5.051794] snd_hda_codec_realtek ehdaudio0D0:inputs: [5.051796] snd_hda_codec_realtek ehdaudio0D0: Headset Mic=0x19 [5.051797] snd_hda_codec_realtek ehdaudio0D0: Headphone Mic=0x1b [5.753612] snd_hda_codec_realtek ehdaudio0D0: ASoC: sink widget AIF1TX overwritten [5.753633] snd_hda_codec_realtek ehdaudio0D0: ASoC: source widget AIF1RX overwritten [5.753758] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi3 overwritten [5.753761] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi2 overwritten [5.753764] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi1 overwritten [5.753766] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Codec Output Pin1 overwritten [5.753768] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Codec Input Pin1 overwritten [5.753772] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Analog Codec Playback overwritten [5.753775] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Digital Codec Playback overwritten [5.753778] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Alt Analog Codec Playback overwritten [5.753782] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Analog Codec Capture overwritten [5.753785] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Digital Codec Capture overwritten [5.753789] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Alt Analog Codec Capture overwritten [5.753798] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3 ``` Don't really know the reason. Will keep investigating. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: New Status in firmware-sof package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in firmware-sof source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996134] Re: test_resolved_domain_restricted_dns in networkd-test.py from systemd ADT failed with J-oem-6.0.0-1007
** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Jammy) 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/1996134 Title: test_resolved_domain_restricted_dns in networkd-test.py from systemd ADT failed with J-oem-6.0.0-1007 Status in ubuntu-kernel-tests: New Status in linux-oem-6.0 package in Ubuntu: New Status in linux-oem-6.0 source package in Jammy: New Bug description: This issue does not exist with J-oem-6.0.0-1006 With systemd 249.11-0ubuntu3.6 ubuntu@curly:~/systemd-249.11/test$ sudo ./networkd-test.py ; uname -a systemd-network:x:100:102:systemd Network Management,,,:/run/systemd:/usr/sbin/nologin test_bridge_init (__main__.BridgeTest) ... ok test_bridge_port_priority (__main__.BridgeTest) ... ok test_bridge_port_priority_set_zero (__main__.BridgeTest) It should be possible to set the bridge port priority to 0 ... ok test_bridge_port_property (__main__.BridgeTest) Test the "[Bridge]" section keys ... ok test_coldplug_dhcp_ip4_only (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers ... ERROR test_resolved_etc_hosts (__main__.DnsmasqClientTest) resolved queries to /etc/hosts ... ok test_route_only_dns (__main__.DnsmasqClientTest) ... ok test_route_only_dns_all_domains (__main__.DnsmasqClientTest) ... ok test_transient_hostname (__main__.DnsmasqClientTest) networkd sets transient hostname from DHCP ... ok test_transient_hostname_with_static (__main__.DnsmasqClientTest) transient hostname is not applied if static hostname exists ... ok test_basic_matching (__main__.MatchClientTest) Verify the Name= line works throughout this class. ... ok test_inverted_matching (__main__.MatchClientTest) Verify that a '!'-prefixed value inverts the match. ... ok test_coldplug_dhcp_ip4_only (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.NetworkdClientTest) ... skipped 'networkd does not have DHCPv6 server support' test_coldplug_dhcp_yes_ip4 (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.NetworkdClientTest) ... ok test_dhcp_timezone (__main__.NetworkdClientTest) networkd sets time zone from DHCP ... ok test_dropin (__main__.NetworkdClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.NetworkdClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.NetworkdClientTest) ... skipped 'networkd does not have DHCPv6 server support' test_route_only_dns (__main__.NetworkdClientTest) ... ok test_route_only_dns_all_domains (__main__.NetworkdClientTest) ... ok test_search_domains (__main__.NetworkdClientTest) ... ok test_catchall_config (__main__.UnmanagedClientTest) Verify link states with a catch-all config, hot-plug. ... ok test_catchall_config_coldplug (__main__.UnmanagedClientTest) Verify link states with a catch-all config, cold-plug. ... ok test_unmanaged_setting (__main__.UnmanagedClientTest) Verify link states with Unmanaged= settings, hot-plug. ... ok test_unmanaged_setting_coldplug (__main__.UnmanagedClientTest) Verify link states with Unmanaged= settings, cold-plug. ... ok == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/home/ubuntu/systemd-249.11/test/./networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 420, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 524, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 156.268s FAILED (errors=1, skipped=2) Linux curly 6.0.0-1007-oem #7-Ubuntu SMP PREEMPT_DYNAMIC Tue Oct 25 18:05:20 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Here is the test log with
[Kernel-packages] [Bug 1995904] Re: Computer freezes or is stuck
After a bit of testing I was able to install ubuntu server 19.10, however when running "do-release-upgrade" it immediately started the issue. -- 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/1995904 Title: Computer freezes or is stuck Status in linux package in Ubuntu: Confirmed Bug description: 13-15 year old Toshiba laptop (Toshiba Satellite C665D) consistently runs into problems trying to run Ubuntu server 22.04.1. If left alone it will output "Uhhuh. NMI received for for unknown reason 2d on cpu 0. Do you have a strange power saving mode enabled? Dazed and confused, but trying to continue" repeatedly over and over disabling any input. Other times when running it would just freeze altogether needing a forced restart. The computer uses a AMD E-450 APU with Radeon HD Graphics (dual core @ 1650MHz) with 4GB of ram and the bios is InsydeH2O version 1.8 rev 3.5. I tried "intel_idle.max_cstate=0" and "processor.max_cstate=0" to no avail as a user on askUbuntu suggested I should disable c-states, however there is no option in the bios. I am terribly sorry but I do not know what source package is causing this. I am very new to Ubuntu and Linux in general. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
** Description changed: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) - Subsystem: Hewlett-Packard Company Device [103c:8914] + Subsystem: Hewlett-Packard Company Device [103c:8914] - https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ - --- + https://lore.kernel.org/linux- + wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ + + Modemmanager requires >= 1.19.1, the detail info is in + lp:1962525 + + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: - + DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 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.14.0-9007-oem N/A - linux-backports-modules-5.14.0-9007-oem N/A - linux-firmware 1.187.20+staging.31 + linux-restricted-modules-5.14.0-9007-oem N/A + linux-backports-modules-5.14.0-9007-oem N/A + linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: New Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
Hi to all, I also had perfomance issue, I have a Toshiba C845 with 4 cores i7-3632qm with CPU power manager with top speed 2.9 - 3,2 ghz I disabled IOMM, thermald, power-profile-daemon and had improvements, but changing to xorg recovered most of the speed. In my case seems that the rest of slowness is because gnome 42 takes graphical resources than gnome 32. The system responds, but gnome smoothness is gone :/ -- 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.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1995238] Re: snaps randomly crash after some time
I'm on kernel 6.0.7, all appears well so far. -- 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/1995238 Title: snaps randomly crash after some time Status in snapd: Invalid Status in linux package in Ubuntu: Confirmed Bug description: This is https://forum.snapcraft.io/t/unsupported-version-0-of-verneed- record-linux-6-0/32160. When I load the web interfaces to these two services, firefox will immediately crash. Attempting to run from the command-line produces an error message as follows: Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: /snap/firefox/2015/usr/lib/firefox/firefox: error while loading shared libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed record Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: message repeated 2 times: [ /snap/firefox/2015/usr/lib/firefox/firefox: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verdef record] The only way to restart firefox is to restart the computer! Logging out and in again, then running firefox, produces the same errors. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 Uname: Linux 6.0.6-060006-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 31 19:41:21 2022 InstallationDate: Installed on 2019-05-26 (1253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-04-29 (184 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1995238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Deleted #31 as it may not be relevant. Has this been merged into the 6.1 kernel RC? thx, sorry for multiples, catching up here -- 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 Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
** Also affects: modemmanager (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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: New Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 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.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Also, @khfeng —if asking people to beta test a random kernel from an S3 bucket, would you mind providing some original checksums? :) -- 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 Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Kernel-packages] [Bug 1996121] Re: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec
** Description changed: - this bug is for tracking purpose. + The cs35l41 codec driver was backported to Jammy kernel a couple of + months ago, recently the Jammy kernel was adopted as the hwe kernel + for OEM machines and with this kernel the UBSAN calltrace was seen, + need to backport these 2 patches. Kinetic kernel already has the + patches, so this SRU is only for Jammy kernel. + + [Impact] + Install the 5.15 hwe kernel on the machines with cs35l41 + codec, after booting and check the dmesg, there is a UBSAN calltrace. + + [Fix] + Backport 2 patches from mainlie kernel to fix this problem. + + [Test] + boot the patched kernel on the machine, check the dmesg, there + is no UBSAN calltrace, and test the audio functions, all input + and output devices coudl work as well as before. + + + [Where problems could occur] + The patch only affects the cirruslogic asoc codec driver, if it + could introduce the regression, it will be on the machines with + cs codec, and it will make the audio driver initialization fail + and make the system lose the audio function. But this possibility + is very low, we tested the patches on many oem machines, all + worked well. -- 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/1996121 Title: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: The cs35l41 codec driver was backported to Jammy kernel a couple of months ago, recently the Jammy kernel was adopted as the hwe kernel for OEM machines and with this kernel the UBSAN calltrace was seen, need to backport these 2 patches. Kinetic kernel already has the patches, so this SRU is only for Jammy kernel. [Impact] Install the 5.15 hwe kernel on the machines with cs35l41 codec, after booting and check the dmesg, there is a UBSAN calltrace. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, check the dmesg, there is no UBSAN calltrace, and test the audio functions, all input and output devices coudl work as well as before. [Where problems could occur] The patch only affects the cirruslogic asoc codec driver, if it could introduce the regression, it will be on the machines with cs codec, and it will make the audio driver initialization fail and make the system lose the audio function. But this possibility is very low, we tested the patches on many oem machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996121] [NEW] alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec
Public bug reported: this bug is for tracking purpose. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Medium Status: In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) 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/1996121 Title: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: this bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995904] Re: Computer freezes or is stuck
When the problem starts all input is disabled so the command cannot be run. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995904 Title: Computer freezes or is stuck Status in linux package in Ubuntu: Confirmed Bug description: 13-15 year old Toshiba laptop (Toshiba Satellite C665D) consistently runs into problems trying to run Ubuntu server 22.04.1. If left alone it will output "Uhhuh. NMI received for for unknown reason 2d on cpu 0. Do you have a strange power saving mode enabled? Dazed and confused, but trying to continue" repeatedly over and over disabling any input. Other times when running it would just freeze altogether needing a forced restart. The computer uses a AMD E-450 APU with Radeon HD Graphics (dual core @ 1650MHz) with 4GB of ram and the bios is InsydeH2O version 1.8 rev 3.5. I tried "intel_idle.max_cstate=0" and "processor.max_cstate=0" to no avail as a user on askUbuntu suggested I should disable c-states, however there is no option in the bios. I am terribly sorry but I do not know what source package is causing this. I am very new to Ubuntu and Linux in general. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] Re: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10
Changing status to 'Confirmed' as was requested in comment #2. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806488] Re: Support non-strict iommu mode on arm64
** Changed in: linux-aws (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1806488 Title: Support non-strict iommu mode on arm64 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Invalid Status in linux source package in Cosmic: Fix Released Status in linux-aws source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-aws source package in Disco: Invalid Status in linux source package in Jammy: Invalid Status in linux-aws source package in Jammy: Fix Committed Status in linux source package in Kinetic: Invalid Status in linux-aws source package in Kinetic: Fix Committed Bug description: [Impact] The Intel IOMMU driver provides an option for strict mode. When disabled, batching of IOTLB flush operations is permitted, allowing the user to trade-off isolation for improved performance. Ubuntu's kernel currently lacks a parity for this feature for ARM. There's a significant performance gain to be had by removing the need to flush the IOMMU TLB on every unmap on arm64. I'm seeing a 25% performance gain w/ fio reads on a single NVMe device. This mode of operation is available for x86 via the "intel_iommu=strict" parameter. Upstream now exposes an equivalent feature for ARM platforms via the "iommu.strict=[0|1]" parameter, while retaining the default strict-enabled mode. [Test Case] Run fio with the following config before and after applying the patches and collection IOPS count. Run again after applying the patches. Finally, run a 3rd time after adding iommu.strict=0 to the kernel commandline. Performance should not regress after the update. Performance should further improve after adding iommu.strict=0 - but if it doesn't for some reason, that is not a regression. $ cat fio.rc [global] rw=read direct=1 ioengine=libaio iodepth=2048 numjobs=10 bs=4k group_reporting=1 group_reporting=1 cpumask=0xff runtime=100 loops = 1 [job1] filename=/dev/nvme0n1 [Fix] 44f6876a00e83 iommu/arm-smmu: Support non-strict mode b2dfeba654cb0 iommu/io-pgtable-arm-v7s: Add support for non-strict mode 9662b99a19abc iommu/arm-smmu-v3: Add support for non-strict mode b6b65ca20bc93 iommu/io-pgtable-arm: Add support for non-strict mode 68a6efe86f6a1 iommu: Add "iommu.strict" command line option 2da274cdf998a iommu/dma: Add support for non-strict mode 07fdef34d2be6 iommu/arm-smmu-v3: Implement flush_iotlb_all hook 85c7a0f1ef624 iommu/io-pgtable-arm: Fix race handling in split_blk_unmap() [Regression Risk] Most of these patches are specific to ARM, and have been regression tested on both arm64 (HiSilicon D06) and armhf (QEMU virt) using "stress-ng --vm $(nproc)" 2 patches do touch arch-indep code however: > 68a6efe86f6a1 iommu: Add "iommu.strict" command line option Adds a new command line option and sets an attribute that iommu drivers can optionally react to. Doesn't change default behavior. > 2da274cdf998a iommu/dma: Add support for non-strict mode This driver is only built for arm64 and ppc64el (determined by looking at the build logs). Most of this patch only changes behavior in the non-default (and new) iommu.strict=0 case. The exception, which is called out in the commit message, is this hunk: - WARN_ON(iommu_unmap(domain, dma_addr, size) != size); + WARN_ON(iommu_unmap_fast(domain, dma_addr, size) != size); + if (!cookie->fq_domain) + iommu_tlb_sync(domain); In the default case, where fq_domain will be NULl, we are now factoring iommu_unmap() into: iommu_unmap_fast() iommu_tlb_sync() Looking at the source to iommu_unmap() confirms that this is functionally equivalent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
** Also affects: linux-azure (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Kinetic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu) Status: New => 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/1996117 Title: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Kinetic: In Progress Bug description: SRU Justification [Impact] SRIOV tests fail where sometimes 0 and other times only 6 VF devices are detected instead of 8. This is using the 5.19 Edge kernel. Example failure from LISA test run - Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected <6> to be equal to <8>, but was not. Microsoft has requested the inclusion of [1], now in linux-next. 1 - https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] Microsoft tested [Where things could go wrong] VNICs could go undetected. [Other Info] SF: #00346751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996117] [NEW] [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
Public bug reported: SRU Justification [Impact] SRIOV tests fail where sometimes 0 and other times only 6 VF devices are detected instead of 8. This is using the 5.19 Edge kernel. Example failure from LISA test run - Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected <6> to be equal to <8>, but was not. Microsoft has requested the inclusion of [1], now in linux-next. 1 - https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] Microsoft tested [Where things could go wrong] VNICs could go undetected. [Other Info] SF: #00346751 ** Affects: linux-azure (Ubuntu) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: New ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Changed in: linux-azure (Ubuntu) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1996117 Title: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning Status in linux-azure package in Ubuntu: New Bug description: SRU Justification [Impact] SRIOV tests fail where sometimes 0 and other times only 6 VF devices are detected instead of 8. This is using the 5.19 Edge kernel. Example failure from LISA test run - Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected <6> to be equal to <8>, but was not. Microsoft has requested the inclusion of [1], now in linux-next. 1 - https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] Microsoft tested [Where things could go wrong] VNICs could go undetected. [Other Info] SF: #00346751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996116] [NEW] 5.15.0-52 does not see USB block device
Public bug reported: I've got a server that boots off a microSD card connected to a USB reader (HPE ProLiant DL380p Gen8, if relevant). The bootloader (GRUB) and rootfs are both on that microSD card. The BIOS boots it just fine, GRUB runs and has no issues loading the kernel and initrd. However, once the kernel loads, it doesn't see the microSD card anymore. As far as I can tell, the reader shows up in `dmesg`, it's just that no block device enumerates. I had to revert to 5.15.0-46 (which is the only other kernel I had installed) in order to boot up my server properly. I've tried different microSD cards and different USB-connected readers for them, and nothing changed. ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1996116 Title: 5.15.0-52 does not see USB block device Status in linux-hwe-5.15 package in Ubuntu: New Bug description: I've got a server that boots off a microSD card connected to a USB reader (HPE ProLiant DL380p Gen8, if relevant). The bootloader (GRUB) and rootfs are both on that microSD card. The BIOS boots it just fine, GRUB runs and has no issues loading the kernel and initrd. However, once the kernel loads, it doesn't see the microSD card anymore. As far as I can tell, the reader shows up in `dmesg`, it's just that no block device enumerates. I had to revert to 5.15.0-46 (which is the only other kernel I had installed) in order to boot up my server properly. I've tried different microSD cards and different USB-connected readers for them, and nothing changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1996116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1169727] Re: [SONY VAIO VPCEB13FX] Battery charging at zero rate - will never fully charge
Have same/similar problem
Differenct is shows BAT1
os: Ubuntu 22.04.1 LTS
Manufacturer: Acer
Product Name: Aspire E5-523G
Version: V1.08
Wake-up Type: Power Switch
SKU Number: Aspire E5-523G_1099_1.08
Family: SR
ViewResult: dmidecode -s bios-version && sudo dmidecode -s bios-release-date
V1.08
07/11/2016
ViewResult: dmesg | grep -i bat
[0.335998] libata version 3.00 loaded.
[0.419103] ACPI: battery: Slot [BAT1] (battery present)
ViewResult: acpi -abi
Battery 0: Charging, 0%, charging at zero rate - will never fully charge.
Battery 0: design capacity 6000 mAh, last full capacity 6157 mAh = 100%
Adapter 0: on-line
--
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/1169727
Title:
[SONY VAIO VPCEB13FX] Battery charging at zero rate - will never fully
charge
Status in linux package in Ubuntu:
Incomplete
Bug description:
:~$ acpi -abi
Battery 0: Charging, 9%, charging at zero rate - will never fully charge.
Battery 0: design capacity 42180 mWh, last full capacity 29050 mWh = 68%
Adapter 0: on-line
Similar to Question #210041, I could charge my battery with Windows 7,
and cannot charge my battery with Linux. I wiped the Windows
partition for more HD space, and hope posting this bug will lead to a
simple strategy to charge my battery. What am I missing to charge it
again? Information to help the process is listed below.
:~$ dmesg | grep Sony
DMI: Sony Corporation VPCEB13FX/VAIO, BIOS R0230Y8 01/26/2010
Also, would someone post the steps to update the BIOS from an .exe? (this
may improve fan performance, while not solving the battery charging issue in
linux)
http://esupport.sony.com/US/p/swu-download.pl?mdl=VPCEB13FX_id=5961_group_id=6
:~$ lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise
:~$ uname -a
Linux toddh 3.9.0-030900rc6-generic #201304080035 SMP Mon Apr 8 04:36:25 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
Trouble-shooting included using an upstream kernel from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc6-raring/
Afterwards, /proc/acpi/ was different, and is reflected in an attached
tarball (/proc/acpi/event/ directory busy during copy and not included).
:~$ upower --monitor-detail:
battery
present: yes
rechargeable:yes
state: charging
energy: 2.9 Wh
energy-empty:0 Wh
energy-full: 29.05 Wh
energy-full-design: 42.18 Wh
energy-rate: 0 W
percentage: 9.98279%
capacity:68.8715%
technology: lithium-ion
History (charge):
13661391989.983 charging
13661391980.000 unknown
History (rate):
13661391980.000 unknown
After dpkg (via synaptic) to remove the mainline kernels, and sudo
update-grub:
:~$ uname -a
Linux toddh 3.2.0-40-generic #64-Ubuntu SMP Mon Mar 25 21:22:10 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
I'd expect the battery to start recharging again when the issue is
resolved.
Finally, could any of these bugs be related?
Battery charging status is not recognized
https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/1027798
acpi reports battery state incorrectly
https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061
Wrong values for battery charge rate and design capacity
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/820295
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-40-generic 3.2.0-40.64
ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40
Uname: Linux 3.2.0-40-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: todd 2379 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf600 irq 44'
Mixer name : 'Intel IbexPeak HDMI'
Components : 'HDA:10ec0269,104d4600,0014
HDA:80862804,104d4600,0010'
Controls : 24
Simple ctrls : 11
CurrentDmesg: [ 40.443109] wlan0: no IPv6 routers present
Date: Tue Apr 16 14:51:23 2013
HibernationDevice: RESUME=UUID=d901bc0d-a953-4557-8bc0-80915c834c5e
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate
[Kernel-packages] [Bug 1996112] 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 1996112 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/1996112 Title: Virtual GPU driver packaging regression Status in linux package in Ubuntu: Incomplete Bug description: Several virtual machine GPU drivers were moved from linux-modules- extra to linux-modules in bug #1960633 so that users running virtualized Linux would not need to install the drivers for real hardware in linux-modules-extra. linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these drivers, but linux-modules-extra-5.19.0-23-generic does. This is a regression. Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was limited to sub-HD resolutions until I installed linux-modules- extra-5.19.0-23-generic. A previous kernel (5.15) had the modules in linux-modules: $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ The current kernel (5.19) has the modules in linux-modules-extra: $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996112] [NEW] Virtual GPU driver packaging regression
Public bug reported: Several virtual machine GPU drivers were moved from linux-modules-extra to linux-modules in bug #1960633 so that users running virtualized Linux would not need to install the drivers for real hardware in linux- modules-extra. linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these drivers, but linux-modules-extra-5.19.0-23-generic does. This is a regression. Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was limited to sub-HD resolutions until I installed linux-modules- extra-5.19.0-23-generic. A previous kernel (5.15) had the modules in linux-modules: $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ The current kernel (5.19) has the modules in linux-modules-extra: $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Several virtual machine GPU drivers were moved from linux-modules-extra - to linux-modules in bug #1960633 ( - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633 ) so that - users running virtualized Linux would not need to install the drivers - for real hardware in linux-modules-extra. + to linux-modules in bug #1960633 so that users running virtualized Linux + would not need to install the drivers for real hardware in linux- + modules-extra. linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these drivers, but linux-modules-extra-5.19.0-23-generic does. This is a regression. Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was limited to sub-HD resolutions until I installed linux-modules- extra-5.19.0-23-generic. A previous kernel (5.15) had the modules in linux-modules: $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ The current kernel (5.19) has the modules in linux-modules-extra: $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko -- 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/1996112 Title: Virtual GPU driver packaging regression Status in linux package in Ubuntu: New Bug description: Several virtual machine GPU drivers were moved from linux-modules- extra to linux-modules in bug #1960633 so that users running virtualized Linux would not need to install the drivers for real hardware in linux-modules-extra. linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these drivers, but linux-modules-extra-5.19.0-23-generic does. This is a regression. Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was limited to sub-HD resolutions until I installed linux-modules- extra-5.19.0-23-generic. A previous kernel (5.15) had the modules in linux-modules: $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ The current kernel (5.19) has the modules in linux-modules-extra: $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E
[Kernel-packages] [Bug 1995966] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630114/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630113/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630112/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630115/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995957 should be helpful. Will try to build a test kernel for it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all Status in linux package in Ubuntu: Confirmed Bug description: Sound/speakers don't work at all on Asus Zenbook 14 OLED and other similar models with Realtek ALC294. No solution works. Audio is not muted, tried adding snd-hda arguments - no dice. This has been reported numerous times, when will a fix finally be rolled out?! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1730 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 12 13:57:05 2022 InstallationDate: Installed on 2022-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630111/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630110/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630105/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630109/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630108/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630106/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630103/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630102/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630104/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630107/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630099/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630101/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630100/+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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630098/+files/AudioDevicesInUse.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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0S05000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0S05000 dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995966] Re: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10
apport information ** Tags added: apport-collected kinetic wayland-session ** Description changed: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? + --- + ProblemType: Bug + ApportVersion: 2.23.1-0ubuntu3 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.10 + InstallationDate: Installed on 2022-10-24 (16 days ago) + InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) + MachineType: LENOVO 21A0S05000 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 + RelatedPackageVersions: + linux-restricted-modules-5.19.0-23-generic N/A + linux-backports-modules-5.19.0-23-generic N/A + linux-firmware 20220923.gitf09bebf3-0ubuntu1 + Tags: kinetic wayland-session + Uname: Linux 5.19.0-23-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 06/27/2022 + dmi.bios.release: 1.19 + dmi.bios.vendor: LENOVO + dmi.bios.version: R1MET49W (1.19 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 21A0S05000 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.ec.firmware.release: 1.19 + dmi.modalias: dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: + dmi.product.family: ThinkPad P14s Gen 2a + dmi.product.name: 21A0S05000 + dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a + dmi.product.version: ThinkPad P14s Gen 2a + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1995966/+attachment/5630097/+files/AlsaInfo.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/1995966 Title: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) on Lenovo P14s laptop. There is built-in SD card reader, which does not work. i e., when I insert SD card, it is not mounted or recognized at all. Please note this is not a problem of the SD card, because this SD card works on older Lenovo laptop (with different SD card reader) with Ubuntu (so it is not some "special", incompatible SD card). lspci says: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci lsmod | grep rtsx_pci says: rtsx_pci_sdmmc 36864 0 rtsx_pci 106496 1 rtsx_pci_sdmmc I guess it is a kernel problem? Or there is another solution? --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21A0S05000 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A
[Kernel-packages] [Bug 1995238] Re: snaps randomly crash after some time
This is a bug in the linux v6.0 kernel and it's fixed with https://lore.kernel.org/lkml/20221020223616.7571-1-phil...@squashfs.org.uk/ ** Changed in: snapd Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995238 Title: snaps randomly crash after some time Status in snapd: Invalid Status in linux package in Ubuntu: Confirmed Bug description: This is https://forum.snapcraft.io/t/unsupported-version-0-of-verneed- record-linux-6-0/32160. When I load the web interfaces to these two services, firefox will immediately crash. Attempting to run from the command-line produces an error message as follows: Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: /snap/firefox/2015/usr/lib/firefox/firefox: error while loading shared libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed record Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: message repeated 2 times: [ /snap/firefox/2015/usr/lib/firefox/firefox: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verdef record] The only way to restart firefox is to restart the computer! Logging out and in again, then running firefox, produces the same errors. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 Uname: Linux 6.0.6-060006-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 31 19:41:21 2022 InstallationDate: Installed on 2019-05-26 (1253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-04-29 (184 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1995238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] 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 1996092 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/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: Incomplete 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] [NEW] 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)
Public bug reported: 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- lspci-vnvn.log" https://bugs.launchpad.net/bugs/1996092/+attachment/5630095/+files/lspci-vnvn.log -- 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 1996093] [NEW] [RELEASE BLOCKER] Call trace during nvme storage performance test in bionic/linux-azure 4.15.0-1154
Public bug reported: SRU Justification [Impact] Hypervisor only allocates interrupts to happen on a single physical GPU, which can lead to CPU soft locks when using PCI NVME under heavy load. [Test Case] Microsoft tested [Where things could go wrong] Hypervisor PCI driver may not load correctly. Patch did not apply cleanly and could lead to merge conflicts once the upstream patch is pulled in. [Other Info] SF: #00347669 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Attachment added: "KernelLogStatus[1].txt" https://bugs.launchpad.net/bugs/1996093/+attachment/5630096/+files/KernelLogStatus%5B1%5D.txt -- 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/1996093 Title: [RELEASE BLOCKER] Call trace during nvme storage performance test in bionic/linux-azure 4.15.0-1154 Status in linux-azure package in Ubuntu: New Bug description: SRU Justification [Impact] Hypervisor only allocates interrupts to happen on a single physical GPU, which can lead to CPU soft locks when using PCI NVME under heavy load. [Test Case] Microsoft tested [Where things could go wrong] Hypervisor PCI driver may not load correctly. Patch did not apply cleanly and could lead to merge conflicts once the upstream patch is pulled in. [Other Info] SF: #00347669 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996068] Re: i915 crash at boot time (probably to activate vga console)
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Confirmed Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [2.211045] ? 0xc098b000 Nov 5 09:46:42 shusaku kernel: [
[Kernel-packages] [Bug 1175465] Re: Alcor AU9520 not recognized by libccid > 1.4.2
Is the problem still present with libccid 1.5.0-2 from Ubuntu 22.04 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/1175465 Title: Alcor AU9520 not recognized by libccid > 1.4.2 Status in ccid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: CID: 201205-11052 (Pavilion Slimline S5 Pavilion P6) With this card reader: 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer Steps: 1. Insert a MMC/SD/SDHC card. 2. (The file browser will pop out.) 3. Remove the pre-inserted card. Expected Results: 1. The card will be removed from the /media, the icon will disappear from the launcher. 2. Open a file browser, and it's not in the devices section of the left column. Actual Results: 1. The card will be removed from the /media, the icon will disappear. 2. It still listed in the devices section, if you click on it in the file browser, an error pops, telling you the device was not found, and the disappears from the left column of the file browser. The reason seems to be the eject event is not being sent through dbus. Will try update later to see if it can be solved. The eject event is not being sent through dbus ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1547 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d0 irq 50' Mixer name : 'IDT 92HD73E1X5' Components : 'HDA:111d7676,103c2ada,00100103' Controls : 39 Simple ctrls : 21 Date: Thu May 2 02:11:18 2013 HibernationDevice: RESUME=UUID=0059822b-2011-4dbc-aea6-3e1aff45462e InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=c6420b34-c860-4df2-99fd-9fa1a0b893b7 ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.79.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2013 dmi.bios.vendor: AMI dmi.bios.version: 00.05 dmi.board.name: 2ADA dmi.board.vendor: Hewlett-Packard dmi.board.version: PVT dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr00.05:bd03/29/2013:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn2ADA:rvrPVT:cvnHewlett-Packard:ct3:cvr: dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995638] Re: Jammy update: v5.15.74 upstream stable release
** 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/1995638
Title:
Jammy update: v5.15.74 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.74 upstream stable release
from git://git.kernel.org/
nilfs2: fix NULL pointer dereference at nilfs_bmap_lookup_at_level()
nilfs2: fix use-after-free bug of struct nilfs_root
nilfs2: fix leak of nilfs_root in case of writer thread creation failure
nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
ceph: don't truncate file in atomic_open
random: restore O_NONBLOCK support
random: clamp credited irq bits to maximum mixed
ALSA: hda: Fix position reporting on Poulsbo
efi: Correct Macmini DMI match in uefi cert quirk
USB: serial: qcserial: add new usb-id for Dell branded EM7455
Revert "powerpc/rtas: Implement reentrant rtas call"
Revert "crypto: qat - reduce size of mapped region"
random: avoid reading two cache lines on irq randomness
random: use expired timer rather than wq for mixing fast pool
Input: xpad - add supported devices as contributed on github
Input: xpad - fix wireless 360 controller breaking after suspend
misc: pci_endpoint_test: Aggregate params checking for xfer
misc: pci_endpoint_test: Fix pci_endpoint_test_{copy,write,read}() panic
Linux 5.15.74
UBUNTU: Upstream stable to v5.15.74
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995638/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995637] Re: Jammy update: v5.15.73 upstream stable release
** 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/1995637 Title: Jammy update: v5.15.73 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.73 upstream stable release from git://git.kernel.org/ Makefile.extrawarn: Move -Wcast-function-type-strict to W=1 docs: update mediator information in CoC docs xsk: Inherit need_wakeup flag for shared sockets mm: gup: fix the fast GUP race against THP collapse powerpc/64s/radix: don't need to broadcast IPI for radix pmd collapse flush firmware: arm_scmi: Improve checks in the info_get operations firmware: arm_scmi: Harden accesses to the sensor domains firmware: arm_scmi: Add SCMI PM driver remove routine dmaengine: xilinx_dma: Fix devm_platform_ioremap_resource error handling dmaengine: xilinx_dma: cleanup for fetching xlnx,num-fstores property dmaengine: xilinx_dma: Report error in case of dma_set_mask_and_coherent API failure ARM: dts: fix Moxa SDIO 'compatible', remove 'sdhci' misnomer scsi: qedf: Fix a UAF bug in __qedf_probe() net/ieee802154: fix uninit value bug in dgram_sendmsg net: marvell: prestera: add support for for Aldrin2 ALSA: hda/hdmi: Fix the converter reuse for the silent stream um: Cleanup syscall_handler_t cast in syscalls_32.h um: Cleanup compiler warning in arch/x86/um/tls_32.c arch: um: Mark the stack non-executable to fix a binutils warning net: atlantic: fix potential memory leak in aq_ndev_close() drm/amd/display: Fix double cursor on non-video RGB MPO drm/amd/display: Assume an LTTPR is always present on fixed_vs links drm/amd/display: update gamut remap if plane has changed drm/amd/display: skip audio setup when audio stream is enabled mmc: core: Replace with already defined values for readability mmc: core: Terminate infinite loop in SD-UHS voltage switch perf parse-events: Identify broken modifiers mm/huge_memory: minor cleanup for split_huge_pages_all mm/huge_memory: use pfn_to_online_page() in split_huge_pages_all() wifi: cfg80211: fix MCS divisor value net/mlx5: Disable irq when locking lag_lock usb: mon: make mmapped memory read only USB: serial: ftdi_sio: fix 300 bps rate for SIO rpmsg: qcom: glink: replace strncpy() with strscpy_pad() Revert "clk: ti: Stop using legacy clkctrl names for omap4 and 5" Linux 5.15.73 UBUNTU: Upstream stable to v5.15.73 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995517] Re: Jammy update: v5.15.72 upstream stable release
** 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/1995517 Title: Jammy update: v5.15.72 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.72 upstream stable release from git://git.kernel.org/ ALSA: hda: Do disconnect jacks at codec unbind ALSA: hda: Fix hang at HD-audio codec unbinding due to refcount saturation ALSA: hda: Fix Nvidia dp infoframe cgroup: reduce dependency on cgroup_mutex cgroup: cgroup_get_from_id() must check the looked-up kn is a directory uas: add no-uas quirk for Hiksemi usb_disk usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS uas: ignore UAS for Thinkplus chips usb: typec: ucsi: Remove incorrect warning thunderbolt: Explicitly reset plug events delay back to USB4 spec value net: usb: qmi_wwan: Add new usb-id for Dell branded EM7455 Input: snvs_pwrkey - fix SNVS_HPVIDR1 register address can: c_can: don't cache TX messages for C_CAN cores clk: ingenic-tcu: Properly enable registers before accessing timers x86/sgx: Do not fail on incomplete sanitization on premature stop of ksgxd ARM: dts: integrator: Tag PCI host with device_type ntfs: fix BUG_ON in ntfs_lookup_inode_by_name() mm/damon/dbgfs: fix memory leak when using debugfs_lookup() net: mt7531: only do PLL once after the reset Revert "firmware: arm_scmi: Add clock management to the SCMI power domain" drm/i915/gt: Restrict forced preemption to the active context drm/amdgpu: Add amdgpu suspend-resume code path under SRIOV vduse: prevent uninitialized memory accesses libata: add ATA_HORKAGE_NOLPM for Pioneer BDR-207M and BDR-205 mmc: moxart: fix 4-bit bus width and remove 8-bit bus width mmc: hsq: Fix data stomping during mmc recovery mm/page_alloc: fix race condition between build_all_zonelists and page allocation mm: prevent page_frag_alloc() from corrupting the memory mm: fix dereferencing possible ERR_PTR mm/migrate_device.c: flush TLB while holding PTL mm: fix madivse_pageout mishandling on non-LRU page mm,hwpoison: check mm when killing accessing process media: dvb_vb2: fix possible out of bound access media: rkvdec: Disable H.264 error detection media: v4l2-compat-ioctl32.c: zero buffer passed to v4l2_compat_get_array_args() swiotlb: max mapping size takes min align mask into account ARM: dts: am33xx: Fix MMCHS0 dma properties reset: imx7: Fix the iMX8MP PCIe PHY PERST support ARM: dts: am5748: keep usb4_tm disabled soc: sunxi: sram: Actually claim SRAM regions soc: sunxi: sram: Prevent the driver from being unbound soc: sunxi_sram: Make use of the helper function devm_platform_ioremap_resource() soc: sunxi: sram: Fix probe function ordering issues soc: sunxi: sram: Fix debugfs info for A64 SRAM C ASoC: imx-card: Fix refcount issue with of_node_put arm64: dts: qcom: sm8350: fix UFS PHY serdes size ASoC: tas2770: Reinit regcache on reset drm/bridge: lt8912b: add vsync hsync drm/bridge: lt8912b: set hdmi or dvi mode drm/bridge: lt8912b: fix corrupted image output Revert "drm: bridge: analogix/dp: add panel prepare/unprepare in suspend/resume time" Input: melfas_mip4 - fix return value check in mip4_probe() gpio: mvebu: Fix check for pwm support on non-A8K platforms usbnet: Fix memory leak in usbnet_disconnect() net: sched: act_ct: fix possible refcount leak in tcf_ct_init() cxgb4: fix missing unlock on ETHOFLD desc collect fail path net/mlxbf_gige: Fix an IS_ERR() vs NULL bug in mlxbf_gige_mdio_probe nvme: Fix IOC_PR_CLEAR and IOC_PR_RELEASE ioctls for nvme devices wifi: mac80211: fix regression with non-QoS drivers net: stmmac: power up/down serdes in stmmac_open/release net: phy: Don't WARN for PHY_UP state in mdio_bus_phy_resume() selftests: Fix the if conditions of in test_extra_filter() vdpa/ifcvf: fix the calculation of queuepair fs: split off setxattr_copy and do_setxattr function from setxattr clk: imx: imx6sx: remove the SET_RATE_PARENT flag for QSPI clocks clk: iproc: Do not rely on node name for correct PLL setup KVM: x86: Hide IA32_PLATFORM_DCA_CAP[31:0] from the guest x86/alternative: Fix race in try_get_desc() drm/i915/gem: Really move i915_gem_context.link under ref protection Linux 5.15.72 UBUNTU: Upstream stable
[Kernel-packages] [Bug 1996084] [NEW] Jammy update: v6.0.7 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.7 upstream stable release from git://git.kernel.org/ ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-6.0 (Ubuntu Jammy) 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/1996084 Title: Jammy update: v6.0.7 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Confirmed Status in linux-oem-6.0 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.7 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1996084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995270] Re: Kernel crash dump not getting generated
** Also affects: kdump-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kdump-tools in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1995270 Title: Kernel crash dump not getting generated Status in ubuntu-realtime: Triaged Status in kdump-tools package in Ubuntu: New Bug description: I have to enable the kernel crash dump feature to investigate certain system hang issues. My intention is to enable the kernel crash dump feature (https://ubuntu.com/server/docs/kernel-crash-dump) along with kernel.hung_task_panic and kernel.hung_task_timeout_secs parameters (in /etc/sysctl.conf), so that a kernel vmcore is generated when kernel detects a hung task for more than 5 minutes. I will be then able to send the vmcore files to Kernel engineers in Canonical for investigation. However, While trying to enable kernel crash dump, I'm unable to get a vmcore generate using the test procedure described in "Testing the Crash Dump Mechanism" section in: https://ubuntu.com/server/docs/kernel-crash-dump When I run the command: "echo c > /proc/sysrq-trigger", all I see is a backtrace (image attached). I do not see the print .. "Begin: Saving vmcore from kernel crash ..." Upon system reboot there is no vmcore file under the /var/crash directory. could you please help pointing out what steps i'm missing? Here are some system information: === Last login: Mon Oct 31 11:35:21 2022 root@vran-server-1:~# cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.15.0-1025-realtime root=/dev/mapper/ubuntu--vg-ubuntu--lv ro rhgb quiet skew_tick=1 nohz=on nohz_full=2-23,26-47,50-71,74-95 rcu_nocbs=2-23,26-47,50-71,74-95 intel_pstate=disable nosoftlockup intel_iommu=on iommu=pt usbcore.autosuspend=-1 selinux=0 enforcing=0 nmi_watchdog=0 softlockup_panic=0 audit=0 cgroup_memory=1 cgroup_enable=memory mce=off idle=poll default_hugepagesz=1G skew_tick=1 idle=poll processor.max_cstate=1 intel_idle.max_cstate=0 rcu_nocb_poll kthread_cpus=0,1,72,73,48,49,24,25 irqaffinity=0,1,72,73,48,49,24,25 nosoftlockup tsc=nowatchdog isolcpus=managed_irq,domain,2-23,26-47,50-71,74-95 systemd.cpu_affinity=0,1,72,73,48,49,24,25 cgroup.memory=nokmem crashkernel=512M-:256M root@vran-server-1:~# uname -a Linux vran-server-1 5.15.0-1025-realtime #26 SMP PREEMPT_RT Thu Oct 20 18:14:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@vran-server-1:~# kdump-config show DUMP_MODE: kdump USE_KDUMP: 1 KDUMP_COREDIR: /var/crash crashkernel addr: 0x4900 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-1025-realtime kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-1025-realtime current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/vmlinuz-5.15.0-1025-realtime root=/dev/mapper/ubuntu--vg-ubuntu--lv ro rhgb quiet skew_tick=1 nohz=on nohz_full=2-23,26-47,50-71,74-95 rcu_nocbs=2-23,26-47,50-71,74-95 intel_pstate=disable nosoftlockup intel_iommu=on iommu=pt usbcore.autosuspend=-1 selinux=0 enforcing=0 nmi_watchdog=0 softlockup_panic=0 audit=0 cgroup_memory=1 cgroup_enable=memory mce=off idle=poll default_hugepagesz=1G skew_tick=1 idle=poll processor.max_cstate=1 intel_idle.max_cstate=0 rcu_nocb_poll kthread_cpus=0,1,72,73,48,49,24,25 irqaffinity=0,1,72,73,48,49,24,25 nosoftlockup tsc=nowatchdog isolcpus=managed_irq,domain,2-23,26-47,50-71,74-95 systemd.cpu_affinity=0,1,72,73,48,49,24,25 cgroup.memory=nokmem reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@vran-server-1:~# cat /etc/default/kexec # Defaults for kexec initscript # sourced by /etc/init.d/kexec and /etc/init.d/kexec-load # Load a kexec kernel (true/false) LOAD_KEXEC=true # Kernel and initrd image KERNEL_IMAGE="/vmlinuz" INITRD="/initrd.img" # If empty, use current /proc/cmdline APPEND="" # Load the default kernel from grub config (true/false) USE_GRUB_CONFIG=false root@vran-server-1:~# cat /etc/default/kdump-tools # kdump-tools configuration # --- # USE_KDUMP - controls kdump will be configured # 0 - kdump kernel will not be loaded # 1 - kdump kernel will be loaded and kdump is configured # USE_KDUMP=1 # --- # Kdump Kernel: # KDUMP_KERNEL - A full pathname to a kdump kernel. # KDUMP_INITRD - A full pathname to the kdump initrd (if used). # If these are not set, kdump-config will try to use the current kernel # and initrd if it is relocatable. Otherwise, you will need to specify # these
[Kernel-packages] [Bug 1996083] [NEW] Jammy update: v6.0.6 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.6 upstream stable release from git://git.kernel.org/ ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-6.0 (Ubuntu Jammy) 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/1996083 Title: Jammy update: v6.0.6 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Confirmed Status in linux-oem-6.0 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.6 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1996083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996081] [NEW] Jammy update: v6.0.5 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.5 upstream stable release from git://git.kernel.org/ ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-6.0 (Ubuntu Jammy) 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/1996081 Title: Jammy update: v6.0.5 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Confirmed Status in linux-oem-6.0 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.5 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1996081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996080] [NEW] Jammy update: v6.0.4 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.4 upstream stable release from git://git.kernel.org/ ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-6.0 (Ubuntu Jammy) 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/1996080 Title: Jammy update: v6.0.4 upstream stable release Status in linux-oem-6.0 package in Ubuntu: Confirmed Status in linux-oem-6.0 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.0.4 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1996080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995420] Re: Jammy update: v5.15.71 upstream stable release
** 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/1995420
Title:
Jammy update: v5.15.71 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.71 upstream stable release
from git://git.kernel.org/
drm/amdgpu: Separate vf2pf work item init from virt data exchange
drm/amdgpu: make sure to init common IP before gmc
staging: r8188eu: Remove support for devices with 8188FU chipset (0bda:f179)
staging: r8188eu: Add Rosewill USB-N150 Nano to device tables
usb: dwc3: gadget: Avoid starting DWC3 gadget during UDC unbind
usb: dwc3: Issue core soft reset before enabling run/stop
usb: dwc3: gadget: Prevent repeat pullup()
usb: dwc3: gadget: Refactor pullup()
usb: dwc3: gadget: Don't modify GEVNTCOUNT in pullup()
usb: dwc3: gadget: Avoid duplicate requests to enable Run/Stop
usb: add quirks for Lenovo OneLink+ Dock
usb: gadget: udc-xilinx: replace memcpy with memcpy_toio
Revert "usb: add quirks for Lenovo OneLink+ Dock"
Revert "usb: gadget: udc-xilinx: replace memcpy with memcpy_toio"
drivers/base: Fix unsigned comparison to -1 in CPUMAP_FILE_MAX_BYTES
USB: core: Fix RST error in hub.c
USB: serial: option: add Quectel BG95 0x0203 composition
USB: serial: option: add Quectel RM520N
ALSA: core: Fix double-free at snd_card_new()
ALSA: hda/tegra: set depop delay for tegra
ALSA: hda: add Intel 5 Series / 3400 PCI DID
ALSA: hda/realtek: Add quirk for Huawei WRT-WX9
ALSA: hda/realtek: Enable 4-speaker output Dell Precision 5570 laptop
ALSA: hda/realtek: Re-arrange quirk table entries
ALSA: hda/realtek: Add pincfg for ASUS G513 HP jack
ALSA: hda/realtek: Add pincfg for ASUS G533Z HP jack
ALSA: hda/realtek: Add quirk for ASUS GA503R laptop
ALSA: hda/realtek: Enable 4-speaker output Dell Precision 5530 laptop
iommu/vt-d: Check correct capability for sagaw determination
btrfs: fix hang during unmount when stopping block group reclaim worker
btrfs: fix hang during unmount when stopping a space reclaim worker
media: flexcop-usb: fix endpoint type check
usb: dwc3: core: leave default DMA if the controller does not support 64-bit
DMA
efi: x86: Wipe setup_data on pure EFI boot
efi: libstub: check Shim mode using MokSBStateRT
wifi: mt76: fix reading current per-tid starting sequence number for
aggregation
gpio: mockup: fix NULL pointer dereference when removing debugfs
gpio: mockup: Fix potential resource leakage when register a chip
gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully
riscv: fix a nasty sigreturn bug...
kasan: call kasan_malloc() from __kmalloc_*track_caller()
can: flexcan: flexcan_mailbox_read() fix return value for drop = true
net: mana: Add rmb after checking owner bits
mm/slub: fix to return errno if kmalloc() fails
mm: slub: fix flush_cpu_slab()/__free_slab() invocations in task context.
KVM: x86: Inject #UD on emulated XSETBV if XSAVES isn't enabled
arm64: topology: fix possible overflow in amu_fie_setup()
vmlinux.lds.h: CFI: Reduce alignment of jump-table to function alignment
xfs: reorder iunlink remove operation in xfs_ifree
xfs: fix xfs_ifree() error handling to not leak perag ref
xfs: validate inode fork size against fork format
firmware: arm_scmi: Harden accesses to the reset domains
firmware: arm_scmi: Fix the asynchronous reset requests
arm64: dts: rockchip: Pull up wlan wake# on Gru-Bob
arm64: dts: rockchip: Fix typo in lisense text for PX30.Core
drm/mediatek: dsi: Add atomic {destroy,duplicate}_state, reset callbacks
arm64: dts: rockchip: Set RK3399-Gru PCLK_EDP to 24 MHz
dmaengine: ti: k3-udma-private: Fix refcount leak bug in of_xudma_dev_get()
arm64: dts: rockchip: Remove 'enable-active-low' from rk3399-puma
netfilter: nf_conntrack_sip: fix ct_sip_walk_headers
netfilter: nf_conntrack_irc: Tighten matching on DCC message
netfilter: nfnetlink_osf: fix possible bogus match in nf_osf_find()
ice: Don't double unplug aux on peer initiated reset
iavf: Fix cached head and tail value for iavf_get_tx_pending
ipvlan: Fix out-of-bound bugs caused by unset skb->mac_header
net: core: fix flow symmetric hash
net: phy: aquantia: wait for the suspend/resume operations to finish
scsi: qla2xxx: Fix memory leak
[Kernel-packages] [Bug 1995415] Re: Jammy update: v5.15.70 upstream stable release
Skipped "video: fbdev: i740fb: Error out if 'pixclock' equals zero" as it is already applied as CVE-2022-3061. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3061 ** 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/1995415 Title: Jammy update: v5.15.70 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.70 upstream stable release from git://git.kernel.org/ drm/tegra: vic: Fix build warning when CONFIG_PM=n serial: atmel: remove redundant assignment in rs485_config tty: serial: atmel: Preserve previous USART mode if RS485 disabled of: fdt: fix off-by-one error in unflatten_dt_nodes() pinctrl: qcom: sc8180x: Fix gpio_wakeirq_map pinctrl: qcom: sc8180x: Fix wrong pin numbers pinctrl: rockchip: Enhance support for IRQ_TYPE_EDGE_BOTH pinctrl: sunxi: Fix name for A100 R_PIO NFSv4: Turn off open-by-filehandle and NFS re-export for NFSv4.0 gpio: mpc8xxx: Fix support for IRQ_TYPE_LEVEL_LOW flow_type in mpc85xx drm/meson: Correct OSD1 global alpha value drm/meson: Fix OSD1 RGB to YCbCr coefficient block: blk_queue_enter() / __bio_queue_enter() must return -EAGAIN for nowait parisc: ccio-dma: Add missing iounmap in error path in ccio_probe() of/device: Fix up of_dma_configure_id() stub cifs: revalidate mapping when doing direct writes cifs: don't send down the destination address to sendmsg for a SOCK_STREAM cifs: always initialize struct msghdr smb_msg completely parisc: Allow CONFIG_64BIT with ARCH=parisc tools/include/uapi: Fix for parisc and xtensa drm/amdgpu: Don't enable LTR if not supported drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega binder: remove inaccurate mmap_assert_locked() video: fbdev: i740fb: Error out if 'pixclock' equals zero arm64: dts: juno: Add missing MHU secure-irq ASoC: nau8824: Fix semaphore unbalance at error paths regulator: pfuze100: Fix the global-out-of-bounds access in pfuze100_regulator_probe() scsi: lpfc: Return DID_TRANSPORT_DISRUPTED instead of DID_REQUEUE rxrpc: Fix local destruction being repeated rxrpc: Fix calc of resend age wifi: mac80211_hwsim: check length for virtio packets ALSA: hda/sigmatel: Keep power up while beep is enabled ALSA: hda/tegra: Align BDL entry to 4KB boundary net: usb: qmi_wwan: add Quectel RM520N afs: Return -EAGAIN, not -EREMOTEIO, when a file already locked MIPS: OCTEON: irq: Fix octeon_irq_force_ciu_mapping() drm/panfrost: devfreq: set opp to the recommended one to configure regulator mksysmap: Fix the mismatch of 'L0' symbols in System.map video: fbdev: pxa3xx-gcu: Fix integer overflow in pxa3xx_gcu_write net: Find dst with sk's xfrm policy not ctl_sk KVM: SEV: add cache flush to solve SEV cache incoherency issues cgroup: Add missing cpus_read_lock() to cgroup_attach_task_all() ALSA: hda/sigmatel: Fix unused variable warning for beep power change Linux 5.15.70 UBUNTU: Upstream stable to v5.15.70 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993010] Re: Jammy update: v5.15.69 upstream stable release
** 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/1993010
Title:
Jammy update: v5.15.69 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.69 upstream stable release
from git://git.kernel.org/
NFS: Fix WARN_ON due to unionization of nfs_inode.nrequests
ACPI: resource: skip IRQ override on AMD Zen platforms
ARM: dts: imx: align SPI NOR node name with dtschema
ARM: dts: imx6qdl-kontron-samx6i: fix spi-flash compatible
ARM: dts: at91: fix low limit for CPU regulator
ARM: dts: at91: sama7g5ek: specify proper regulator output ranges
lockdep: Fix -Wunused-parameter for _THIS_IP_
x86/mm: Force-inline __phys_addr_nodebug()
task_stack, x86/cea: Force-inline stack helpers
tracing: hold caller_addr to hardirq_{enable,disable}_ip
tracefs: Only clobber mode/uid/gid on remount if asked
iommu/vt-d: Fix kdump kernels boot failure with scalable mode
Input: goodix - add support for GT1158
platform/surface: aggregator_registry: Add support for Surface Laptop Go 2
drm/msm/rd: Fix FIFO-full deadlock
dt-bindings: iio: gyroscope: bosch,bmg160: correct number of pins
HID: ishtp-hid-clientHID: ishtp-hid-client: Fix comment typo
hid: intel-ish-hid: ishtp: Fix ishtp client sending disordered message
tg3: Disable tg3 device on system reboot to avoid triggering AER
gpio: mockup: remove gpio debugfs when remove device
ieee802154: cc2520: add rc code in cc2520_tx()
Input: iforce - add support for Boeder Force Feedback Wheel
nvmet-tcp: fix unhandled tcp states in nvmet_tcp_state_change()
drm/amd/amdgpu: skip ucode loading if ucode_size == 0
net: dsa: hellcreek: Print warning only once
perf/arm_pmu_platform: fix tests for platform_get_irq() failure
platform/x86: acer-wmi: Acer Aspire One AOD270/Packard Bell Dot keymap fixes
usb: storage: Add ASUS <0x0b05:0x1932> to IGNORE_UAS
mm: Fix TLB flush for not-first PFNMAP mappings in unmap_region()
soc: fsl: select FSL_GUTS driver for DPIO
usb: gadget: f_uac2: clean up some inconsistent indenting
usb: gadget: f_uac2: fix superspeed transfer
RDMA/irdma: Use s/g array in post send only when its valid
Input: goodix - add compatible string for GT1158
Linux 5.15.69
UBUNTU: Upstream stable to v5.15.69
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993010/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995870] Re: BUG: scheduling while atomic: ip/1210/0x00000200 on xenial/hwe rumford
** Changed in: linux-hwe (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1995870 Title: BUG: scheduling while atomic: ip/1210/0x0200 on xenial/hwe rumford Status in linux-hwe package in Ubuntu: Fix Committed Status in linux-hwe source package in Xenial: New Bug description: [Impact] There were BUG: scheduling while atomic: ip/1210/0x0200 appearing on xenial/hwe with the tg3 ethernet driver when running on rumford instance. Probably some performace degradation as the driver was trying to sleep while holding a spinlock. There also was cluttering of the kernel log with stack traces. [Fix] Change usleep_range -> udelay which is safe to call from atomic contexts. [Test] Compile tested only. Should see this resolved in the next cycle on xenial/hwe rumford instance. [Where problems could occur] Not much regression potential as the correct delay call is now being called. -- There is a bug being triggered on a usleep within the tg3 driver with xenial/linux-hwe 4.15.0-197.208~16.04.1 on rumford. This has been observed in multiple cycles during boot-testing. [ 27.437584] BUG: scheduling while atomic: ip/1210/0x0200 [ 27.468440] Modules linked in: nls_iso8859_1 intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp ipmi_ssif kvm_intel hpilo kvm irqbypass intel_cstate shpchp ioatdma dca intel_rapl_perf ipmi_si ipmi_devintf lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ses crct10dif_pclmul enclosure crc32_pclmul ttm ghash_clmulni_intel drm_kms_helper mlx5_core pcbc syscopyarea aesni_intel mlxfw sysfillrect sysimgblt aes_x86_64 fb_sys_fops tg3 devlink crypto_simd hpsa nvme glue_helper ptp drm cryptd pps_core nvme_core scsi_transport_sas wmi [ 27.468491] CPU: 1 PID: 1210 Comm: ip Not tainted 4.15.0-197-generic #208~16.04.1-Ubuntu [ 27.468493] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 05/21/2018 [ 27.468494] Call Trace: [ 27.468508] dump_stack+0x6d/0x8b [ 27.468515] __schedule_bug+0x54/0x70 [ 27.468519] __schedule+0x635/0x8b0 [ 27.468522] schedule+0x36/0x80 [ 27.468527] schedule_hrtimeout_range_clock+0xbc/0x1b0 [ 27.468532] ? __hrtimer_init+0x90/0x90 [ 27.468536] schedule_hrtimeout_range+0x13/0x20 [ 27.468539] usleep_range+0x62/0x90 [ 27.468547] tg3_ape_event_lock+0x36/0xa0 [tg3] [ 27.468552] tg3_ape_driver_state_change.part.69+0xc6/0x160 [tg3] [ 27.468557] tg3_start+0xebc/0x10b0 [tg3] [ 27.468563] tg3_open+0x130/0x280 [tg3] [ 27.468568] __dev_open+0xd7/0x150 [ 27.468572] __dev_change_flags+0x186/0x1c0 [ 27.468575] dev_change_flags+0x29/0x70 [ 27.468580] do_setlink+0x355/0xd90 [ 27.468589] ? nla_parse+0xa7/0x120 [ 27.468592] rtnl_newlink+0x773/0x8f0 [ 27.468597] ? do_anonymous_page+0x24b/0x430 [ 27.468605] ? ns_capable_common+0x2b/0x50 [ 27.468608] ? ns_capable+0x10/0x20 [ 27.468612] rtnetlink_rcv_msg+0x205/0x290 [ 27.468615] ? _cond_resched+0x1a/0x50 [ 27.468620] ? __kmalloc_node_track_caller+0x201/0x2c0 [ 27.468623] ? rtnl_calcit.isra.25+0x100/0x100 [ 27.468627] netlink_rcv_skb+0xd9/0x110 [ 27.468630] rtnetlink_rcv+0x15/0x20 [ 27.468633] netlink_unicast+0x198/0x260 [ 27.468637] netlink_sendmsg+0x2ea/0x410 [ 27.468640] sock_sendmsg+0x3e/0x50 [ 27.468642] ___sys_sendmsg+0x2e9/0x300 [ 27.468646] ? lru_cache_add_active_or_unevictable+0x36/0xb0 [ 27.468649] ? do_anonymous_page+0x24b/0x430 [ 27.468653] ? __handle_mm_fault+0xae7/0xc80 [ 27.468657] __sys_sendmsg+0x54/0x90 [ 27.468659] ? __sys_sendmsg+0x54/0x90 [ 27.468662] SyS_sendmsg+0x12/0x20 [ 27.468667] do_syscall_64+0x73/0x130 [ 27.468670] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 27.468673] RIP: 0033:0x7f285dd57590 [ 27.468675] RSP: 002b:7ffd4370bf38 EFLAGS: 0246 ORIG_RAX: 002e [ 27.468678] RAX: ffda RBX: 7ffd43714040 RCX: 7f285dd57590 [ 27.468679] RDX: RSI: 7ffd4370bf80 RDI: 0003 [ 27.468681] RBP: 6364ddd8 R08: 0040 R09: 0008 [ 27.468682] R10: 05e7 R11: 0246 R12: 7ffd4370bf80 [ 27.468683] R13: R14: 006573a0 R15: 7ffd43714018 [ 27.468703] NOHZ: local_softirq_pending 282 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1995984] Re: T14 Gen3 AMD low Mic volume
*** This bug is a duplicate of bug 1995982 *** https://bugs.launchpad.net/bugs/1995982 ** This bug has been marked a duplicate of bug 1995982 T14 Gen3 AMD low Mic volume -- 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/1995984 Title: T14 Gen3 AMD low Mic volume Status in linux package in Ubuntu: Incomplete Bug description: User Reported: I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37 beta. In every distribution I tried I have the same problem: The volume of the mic is rather low. Mic is set to 100% but it is still low. I can boost with pulseaudio but it's not a big difference. I own another Lenovo laptop. If I set the mic to 100% on this old laptop it's a difference like day and night to the T14 Gen3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993003] Re: Jammy update: v5.15.68 upstream stable release
** 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/1993003
Title:
Jammy update: v5.15.68 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.68 upstream stable release
from git://git.kernel.org/
mm: Force TLB flush for PFNMAP mappings before unlink_file_vma()
drm/bridge: Add stubs for devm_drm_of_get_bridge when OF is disabled
ACPI: thermal: drop an always true check
drm/vc4: hdmi: Rework power up
drm/vc4: hdmi: Depends on CONFIG_PM
firmware: tegra: bpmp: Do only aligned access to IPC memory area
crypto: lib - remove unneeded selection of XOR_BLOCKS
Drivers: hv: balloon: Support status report for larger page sizes
mm/hugetlb: avoid corrupting page->mapping in hugetlb_mcopy_atomic_pte
UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_2441009
arm64: errata: Add Cortex-A510 to the repeat tlbi list
io_uring: Remove unused function req_ref_put
kbuild: Fix include path in scripts/Makefile.modpost
Bluetooth: L2CAP: Fix build errors in some archs
HID: steam: Prevent NULL pointer dereference in steam_{recv,send}_report
udmabuf: Set the DMA mask for the udmabuf device (v2)
media: pvrusb2: fix memory leak in pvr_probe
HID: hidraw: fix memory leak in hidraw_release()
net: fix refcount bug in sk_psock_get (2)
fbdev: fb_pm2fb: Avoid potential divide by zero error
ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is
dead
bpf: Don't redirect packets with invalid pkt_len
mm/rmap: Fix anon_vma->degree ambiguity leading to double-reuse
ALSA: usb-audio: Add quirk for LH Labs Geek Out HD Audio 1V5
HID: add Lenovo Yoga C630 battery quirk
HID: AMD_SFH: Add a DMI quirk entry for Chromebooks
HID: asus: ROG NKey: Ignore portion of 0x5a report
HID: thrustmaster: Add sparco wheel and fix array length
drm/i915/gt: Skip TLB invalidations once wedged
mmc: mtk-sd: Clear interrupts when cqe off/disable
mmc: sdhci-of-dwcmshc: add reset call back for rockchip Socs
mmc: sdhci-of-dwcmshc: rename rk3568 to rk35xx
mmc: sdhci-of-dwcmshc: Re-enable support for the BlueField-3 SoC
btrfs: remove root argument from btrfs_unlink_inode()
btrfs: remove no longer needed logic for replaying directory deletes
btrfs: add and use helper for unlinking inode during log replay
btrfs: fix warning during log replay when bumping inode link count
fs/ntfs3: Fix work with fragmented xattr
ASoC: sh: rz-ssi: Improve error handling in rz_ssi_probe() error path
drm/amd/display: Avoid MPC infinite loop
drm/amd/display: Fix HDMI VSIF V3 incorrect issue
drm/amd/display: For stereo keep "FLIP_ANY_FRAME"
drm/amd/display: clear optc underflow before turn off odm clock
ksmbd: return STATUS_BAD_NETWORK_NAME error status if share is not configured
neigh: fix possible DoS due to net iface start/stop loop
s390/hypfs: avoid error message under KVM
ksmbd: don't remove dos attribute xattr on O_TRUNC open
drm/amd/pm: add missing ->fini_microcode interface for Sienna Cichlid
drm/amd/display: Fix pixel clock programming
drm/amdgpu: Increase tlb flush timeout for sriov
drm/amd/display: avoid doing vm_init multiple time
netfilter: conntrack: NF_CONNTRACK_PROCFS should no longer default to y
testing: selftests: nft_flowtable.sh: use random netns names
btrfs: move lockdep class helpers to locking.c
btrfs: fix lockdep splat with reloc root extent buffers
btrfs: tree-checker: check for overlapping extent items
kprobes: don't call disarm_kprobe() for disabled kprobes
btrfs: fix space cache corruption and potential double allocations
android: binder: fix lockdep check on clearing vma
net/af_packet: check len when min_header_len equals to 0
net: neigh: don't call kfree_skb() under spin_lock_irqsave()
Linux 5.15.65
UBUNTU: Upstream stable to v5.15.65
drm/msm/dsi: fix the inconsistent indenting
drm/msm/dp: delete DP_RECOVERED_CLOCK_OUT_EN to fix tps4
drm/msm/dsi: Fix number of regulators for msm8996_dsi_cfg
drm/msm/dsi: Fix number of regulators for SDM660
platform/x86: pmc_atom: Fix SLP_TYPx bitfield mask
iio: adc: mcp3911: make use of the sign bit
skmsg: Fix wrong last sg check in sk_msg_recvmsg()
bpf: Restrict bpf_sys_bpf to CAP_PERFMON
bpf, cgroup: Fix kernel BUG in
[Kernel-packages] [Bug 1993003] Re: Jammy update: v5.15.68 upstream stable release
Skipped:
"drm/i915: Implement WaEdpLinkRateDataReload" which is already applied for bug
1980621,
"netfilter: nf_conntrack_irc: Fix forged IP logic" which is already applied for
CVE-2022-2663.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-2663
--
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/1993003
Title:
Jammy update: v5.15.68 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.68 upstream stable release
from git://git.kernel.org/
mm: Force TLB flush for PFNMAP mappings before unlink_file_vma()
drm/bridge: Add stubs for devm_drm_of_get_bridge when OF is disabled
ACPI: thermal: drop an always true check
drm/vc4: hdmi: Rework power up
drm/vc4: hdmi: Depends on CONFIG_PM
firmware: tegra: bpmp: Do only aligned access to IPC memory area
crypto: lib - remove unneeded selection of XOR_BLOCKS
Drivers: hv: balloon: Support status report for larger page sizes
mm/hugetlb: avoid corrupting page->mapping in hugetlb_mcopy_atomic_pte
UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_2441009
arm64: errata: Add Cortex-A510 to the repeat tlbi list
io_uring: Remove unused function req_ref_put
kbuild: Fix include path in scripts/Makefile.modpost
Bluetooth: L2CAP: Fix build errors in some archs
HID: steam: Prevent NULL pointer dereference in steam_{recv,send}_report
udmabuf: Set the DMA mask for the udmabuf device (v2)
media: pvrusb2: fix memory leak in pvr_probe
HID: hidraw: fix memory leak in hidraw_release()
net: fix refcount bug in sk_psock_get (2)
fbdev: fb_pm2fb: Avoid potential divide by zero error
ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is
dead
bpf: Don't redirect packets with invalid pkt_len
mm/rmap: Fix anon_vma->degree ambiguity leading to double-reuse
ALSA: usb-audio: Add quirk for LH Labs Geek Out HD Audio 1V5
HID: add Lenovo Yoga C630 battery quirk
HID: AMD_SFH: Add a DMI quirk entry for Chromebooks
HID: asus: ROG NKey: Ignore portion of 0x5a report
HID: thrustmaster: Add sparco wheel and fix array length
drm/i915/gt: Skip TLB invalidations once wedged
mmc: mtk-sd: Clear interrupts when cqe off/disable
mmc: sdhci-of-dwcmshc: add reset call back for rockchip Socs
mmc: sdhci-of-dwcmshc: rename rk3568 to rk35xx
mmc: sdhci-of-dwcmshc: Re-enable support for the BlueField-3 SoC
btrfs: remove root argument from btrfs_unlink_inode()
btrfs: remove no longer needed logic for replaying directory deletes
btrfs: add and use helper for unlinking inode during log replay
btrfs: fix warning during log replay when bumping inode link count
fs/ntfs3: Fix work with fragmented xattr
ASoC: sh: rz-ssi: Improve error handling in rz_ssi_probe() error path
drm/amd/display: Avoid MPC infinite loop
drm/amd/display: Fix HDMI VSIF V3 incorrect issue
drm/amd/display: For stereo keep "FLIP_ANY_FRAME"
drm/amd/display: clear optc underflow before turn off odm clock
ksmbd: return STATUS_BAD_NETWORK_NAME error status if share is not configured
neigh: fix possible DoS due to net iface start/stop loop
s390/hypfs: avoid error message under KVM
ksmbd: don't remove dos attribute xattr on O_TRUNC open
drm/amd/pm: add missing ->fini_microcode interface for Sienna Cichlid
drm/amd/display: Fix pixel clock programming
drm/amdgpu: Increase tlb flush timeout for sriov
drm/amd/display: avoid doing vm_init multiple time
netfilter: conntrack: NF_CONNTRACK_PROCFS should no longer default to y
testing: selftests: nft_flowtable.sh: use random netns names
btrfs: move lockdep class helpers to locking.c
btrfs: fix lockdep splat with reloc root extent buffers
btrfs: tree-checker: check for overlapping extent items
kprobes: don't call disarm_kprobe() for disabled kprobes
btrfs: fix space cache corruption and potential double allocations
android: binder: fix lockdep check on clearing vma
net/af_packet: check len when min_header_len equals to 0
net: neigh: don't call kfree_skb() under spin_lock_irqsave()
Linux 5.15.65
UBUNTU: Upstream stable to v5.15.65
drm/msm/dsi: fix the inconsistent indenting
drm/msm/dp: delete DP_RECOVERED_CLOCK_OUT_EN to fix tps4
drm/msm/dsi: Fix number of regulators for msm8996_dsi_cfg
drm/msm/dsi: Fix number of regulators for SDM660
platform/x86: pmc_atom: Fix SLP_TYPx bitfield mask
[Kernel-packages] [Bug 1996068] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630086/+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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [2.211045]
[Kernel-packages] [Bug 1996068] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630087/+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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [2.211045]
[Kernel-packages] [Bug 1996068] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630083/+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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [
[Kernel-packages] [Bug 1996068] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630085/+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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [
[Kernel-packages] [Bug 1996068] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630080/+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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [
[Kernel-packages] [Bug 1996068] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630084/+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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku
[Kernel-packages] [Bug 1996068] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630078/+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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [2.211045]
[Kernel-packages] [Bug 1996068] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630082/+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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42
[Kernel-packages] [Bug 1996068] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630081/+files/PaInfo.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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [2.211045]
[Kernel-packages] [Bug 1996068] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630079/+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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [
[Kernel-packages] [Bug 1996068] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630077/+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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [
[Kernel-packages] [Bug 1996068] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630076/+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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [2.211045]
[Kernel-packages] [Bug 1996068] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630075/+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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [
[Kernel-packages] [Bug 1996068] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630074/+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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [
[Kernel-packages] [Bug 1996068] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1996068/+attachment/5630073/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [2.211045] ?
[Kernel-packages] [Bug 1996068] Re: i915 crash at boot time (probably to activate vga console)
apport information ** Tags added: apport-collected kinetic wayland-session ** Description changed: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [2.211045] ? 0xc098b000 Nov 5 09:46:42 shusaku kernel: [2.211046] do_one_initcall+0x5b/0x240 Nov 5 09:46:42 shusaku kernel: [2.211049] do_init_module+0x50/0x210 Nov 5 09:46:42 shusaku kernel: [2.211051] load_module+0xb7d/0xcd0 Nov 5 09:46:42 shusaku kernel: [2.211053]
[Kernel-packages] [Bug 1991841] Re: Jammy update: v5.15.67 upstream stable release
** 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/1991841 Title: Jammy update: v5.15.67 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.67 upstream stable release from git://git.kernel.org/ kbuild: fix up permissions on scripts/pahole-flags.sh Linux 5.15.67 UBUNTU: Upstream stable to v5.15.67 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996068] 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 1996068 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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: Incomplete Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952]
[Kernel-packages] [Bug 1991840] Re: Jammy update: v5.15.66 upstream stable release
** 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/1991840 Title: Jammy update: v5.15.66 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.66 upstream stable release from git://git.kernel.org/ drm/msm/dsi: fix the inconsistent indenting drm/msm/dp: delete DP_RECOVERED_CLOCK_OUT_EN to fix tps4 drm/msm/dsi: Fix number of regulators for msm8996_dsi_cfg drm/msm/dsi: Fix number of regulators for SDM660 platform/x86: pmc_atom: Fix SLP_TYPx bitfield mask iio: adc: mcp3911: make use of the sign bit skmsg: Fix wrong last sg check in sk_msg_recvmsg() bpf: Restrict bpf_sys_bpf to CAP_PERFMON bpf, cgroup: Fix kernel BUG in purge_effective_progs ieee802154/adf7242: defer destroy_workqueue call drm/i915/backlight: extract backlight code to a separate file drm/i915/display: avoid warnings when registering dual panel backlight ALSA: hda: intel-nhlt: remove use of __func__ in dev_dbg ALSA: hda: intel-nhlt: Correct the handling of fmt_config flexible array wifi: cfg80211: debugfs: fix return type in ht40allow_map_read() Revert "xhci: turn off port power in shutdown" net: sparx5: fix handling uneven length packets in manual extraction net: smsc911x: Stop and start PHY during suspend and resume openvswitch: fix memory leak at failed datapath creation net: dsa: xrs700x: Use irqsave variant for u64 stats update net: sched: tbf: don't call qdisc_put() while holding tree lock net/sched: fix netdevice reference leaks in attach_default_qdiscs() ethernet: rocker: fix sleep in atomic context bug in neigh_timer_handler mlxbf_gige: compute MDIO period based on i1clk kcm: fix strp_init() order and cleanup sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb tcp: annotate data-race around challenge_timestamp Revert "sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb" net/smc: Remove redundant refcount increase soundwire: qcom: fix device status array range serial: fsl_lpuart: RS485 RTS polariy is inverse staging: rtl8712: fix use after free bugs staging: r8188eu: add firmware dependency powerpc: align syscall table for ppc32 vt: Clear selection before changing the font musb: fix USB_MUSB_TUSB6010 dependency tty: serial: lpuart: disable flow control while waiting for the transmit engine to complete Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag iio: ad7292: Prevent regulator double disable iio: adc: mcp3911: use correct formula for AD conversion misc: fastrpc: fix memory corruption on probe misc: fastrpc: fix memory corruption on open USB: serial: ftdi_sio: add Omron CS1W-CIF31 device id mmc: core: Fix UHS-I SD 1.8V workaround branch mmc: core: Fix inconsistent sd3_bus_mode at UHS-I SD voltage switch failure binder: fix UAF of ref->proc caused by race condition binder: fix alloc->vma_vm_mm null-ptr dereference cifs: fix small mempool leak in SMB2_negotiate() KVM: VMX: Heed the 'msr' argument in msr_write_intercepted() drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported" clk: core: Honor CLK_OPS_PARENT_ENABLE for clk gate ops Revert "clk: core: Honor CLK_OPS_PARENT_ENABLE for clk gate ops" clk: core: Fix runtime PM sequence in clk_core_unprepare() Input: rk805-pwrkey - fix module autoloading clk: bcm: rpi: Fix error handling of raspberrypi_fw_get_rate clk: bcm: rpi: Use correct order for the parameters of devm_kcalloc() clk: bcm: rpi: Prevent out-of-bounds access clk: bcm: rpi: Add missing newline hwmon: (gpio-fan) Fix array out of bounds access gpio: pca953x: Add mutex_lock for regcache sync in PM KVM: x86: Mask off unsupported and unknown bits of IA32_ARCH_CAPABILITIES xen/grants: prevent integer overflow in gnttab_dma_alloc_pages() mm: pagewalk: Fix race between unmap and page walker xen-blkback: Advertise feature-persistent as user requested xen-blkfront: Advertise feature-persistent as user requested xen-blkfront: Cache feature_persistent value before advertisement thunderbolt: Use the actual buffer in tb_async_error() usb: dwc3: pci: Add support for Intel Raptor Lake media: mceusb: Use new usb_control_msg_*() routines xhci: Add grace period after xHC start to prevent premature runtime
[Kernel-packages] [Bug 1991831] Re: Jammy update: v5.15.65 upstream stable release
Submission was messed up. Instead of 1227 changes from the pull request
I applied 63 which matches upstream stable 74 - 13 (io_uring we already
have via security) + 2 UBUNTU.
** 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/1991831
Title:
Jammy update: v5.15.65 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.65 upstream stable release
from git://git.kernel.org/
mm: Force TLB flush for PFNMAP mappings before unlink_file_vma()
drm/bridge: Add stubs for devm_drm_of_get_bridge when OF is disabled
ACPI: thermal: drop an always true check
drm/vc4: hdmi: Rework power up
drm/vc4: hdmi: Depends on CONFIG_PM
firmware: tegra: bpmp: Do only aligned access to IPC memory area
crypto: lib - remove unneeded selection of XOR_BLOCKS
Drivers: hv: balloon: Support status report for larger page sizes
mm/hugetlb: avoid corrupting page->mapping in hugetlb_mcopy_atomic_pte
UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_2441009
arm64: errata: Add Cortex-A510 to the repeat tlbi list
io_uring: Remove unused function req_ref_put
kbuild: Fix include path in scripts/Makefile.modpost
Bluetooth: L2CAP: Fix build errors in some archs
HID: steam: Prevent NULL pointer dereference in steam_{recv,send}_report
udmabuf: Set the DMA mask for the udmabuf device (v2)
media: pvrusb2: fix memory leak in pvr_probe
HID: hidraw: fix memory leak in hidraw_release()
net: fix refcount bug in sk_psock_get (2)
fbdev: fb_pm2fb: Avoid potential divide by zero error
ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is
dead
bpf: Don't redirect packets with invalid pkt_len
mm/rmap: Fix anon_vma->degree ambiguity leading to double-reuse
ALSA: usb-audio: Add quirk for LH Labs Geek Out HD Audio 1V5
HID: add Lenovo Yoga C630 battery quirk
HID: AMD_SFH: Add a DMI quirk entry for Chromebooks
HID: asus: ROG NKey: Ignore portion of 0x5a report
HID: thrustmaster: Add sparco wheel and fix array length
drm/i915/gt: Skip TLB invalidations once wedged
mmc: mtk-sd: Clear interrupts when cqe off/disable
mmc: sdhci-of-dwcmshc: add reset call back for rockchip Socs
mmc: sdhci-of-dwcmshc: rename rk3568 to rk35xx
mmc: sdhci-of-dwcmshc: Re-enable support for the BlueField-3 SoC
btrfs: remove root argument from btrfs_unlink_inode()
btrfs: remove no longer needed logic for replaying directory deletes
btrfs: add and use helper for unlinking inode during log replay
btrfs: fix warning during log replay when bumping inode link count
fs/ntfs3: Fix work with fragmented xattr
ASoC: sh: rz-ssi: Improve error handling in rz_ssi_probe() error path
drm/amd/display: Avoid MPC infinite loop
drm/amd/display: Fix HDMI VSIF V3 incorrect issue
drm/amd/display: For stereo keep "FLIP_ANY_FRAME"
drm/amd/display: clear optc underflow before turn off odm clock
ksmbd: return STATUS_BAD_NETWORK_NAME error status if share is not configured
neigh: fix possible DoS due to net iface start/stop loop
s390/hypfs: avoid error message under KVM
ksmbd: don't remove dos attribute xattr on O_TRUNC open
drm/amd/pm: add missing ->fini_microcode interface for Sienna Cichlid
drm/amd/display: Fix pixel clock programming
drm/amdgpu: Increase tlb flush timeout for sriov
drm/amd/display: avoid doing vm_init multiple time
netfilter: conntrack: NF_CONNTRACK_PROCFS should no longer default to y
testing: selftests: nft_flowtable.sh: use random netns names
btrfs: move lockdep class helpers to locking.c
btrfs: fix lockdep splat with reloc root extent buffers
btrfs: tree-checker: check for overlapping extent items
kprobes: don't call disarm_kprobe() for disabled kprobes
btrfs: fix space cache corruption and potential double allocations
android: binder: fix lockdep check on clearing vma
net/af_packet: check len when min_header_len equals to 0
net: neigh: don't call kfree_skb() under spin_lock_irqsave()
Linux 5.15.65
UBUNTU: Upstream stable to v5.15.65
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991831/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 1995979] Re: T14 Gen3 AMD low Mic volume
*** This bug is a duplicate of bug 1995982 *** https://bugs.launchpad.net/bugs/1995982 ** This bug has been marked a duplicate of bug 1995982 T14 Gen3 AMD low Mic volume -- 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/1995979 Title: T14 Gen3 AMD low Mic volume Status in linux package in Ubuntu: Incomplete Bug description: User Reported: I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37 beta. In every distribution I tried I have the same problem: The volume of the mic is rather low. Mic is set to 100% but it is still low. I can boost with pulseaudio but it's not a big difference. I own another Lenovo laptop. If I set the mic to 100% on this old laptop it's a difference like day and night to the T14 Gen3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995978] Re: T14 Gen3 AMD low Mic volume
*** This bug is a duplicate of bug 1995982 *** https://bugs.launchpad.net/bugs/1995982 ** This bug has been marked a duplicate of bug 1995982 T14 Gen3 AMD low Mic volume -- 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/1995978 Title: T14 Gen3 AMD low Mic volume Status in linux package in Ubuntu: Incomplete Bug description: User Reported: I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37 beta. In every distribution I tried I have the same problem: The volume of the mic is rather low. Mic is set to 100% but it is still low. I can boost with pulseaudio but it's not a big difference. I own another Lenovo laptop. If I set the mic to 100% on this old laptop it's a difference like day and night to the T14 Gen3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995981] Re: T14 Gen3 AMD low Mic volume
*** This bug is a duplicate of bug 1995982 *** https://bugs.launchpad.net/bugs/1995982 ** This bug has been marked a duplicate of bug 1995982 T14 Gen3 AMD low Mic volume -- 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/1995981 Title: T14 Gen3 AMD low Mic volume Status in linux package in Ubuntu: Incomplete Bug description: User Reported: I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37 beta. In every distribution I tried I have the same problem: The volume of the mic is rather low. Mic is set to 100% but it is still low. I can boost with pulseaudio but it's not a big difference. I own another Lenovo laptop. If I set the mic to 100% on this old laptop it's a difference like day and night to the T14 Gen3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996068] Re: i915 crash at boot time (probably to activate vga console)
** Package changed: mutter (Ubuntu) => linux (Ubuntu) ** Attachment added: "Output of dmidecoe" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996068/+attachment/5630050/+files/dmi.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/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: New Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2
[Kernel-packages] [Bug 1996069] [NEW] [UBUNTU 20.04] zipl: Add secure boot trailer (s390-tools part)
Public bug reported: 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 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-200453 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-200453 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996069 Title: [UBUNTU 20.04] zipl: Add secure boot trailer (s390-tools part) Status in linux 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/+source/linux/+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 1996071] [NEW] [UBUNTU 20.04] boot: Add secure boot trailer
Public bug reported: 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 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-200452 severity-critical targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-200452 severity-critical targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996071 Title: [UBUNTU 20.04] boot: Add secure boot trailer Status in linux package in Ubuntu: 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/+source/linux/+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 1995980] Re: T14 Gen3 AMD low Mic volume
*** This bug is a duplicate of bug 1995982 *** https://bugs.launchpad.net/bugs/1995982 ** This bug has been marked a duplicate of bug 1995982 T14 Gen3 AMD low Mic volume -- 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/1995980 Title: T14 Gen3 AMD low Mic volume Status in linux package in Ubuntu: Incomplete Bug description: User Reported: I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37 beta. In every distribution I tried I have the same problem: The volume of the mic is rather low. Mic is set to 100% but it is still low. I can boost with pulseaudio but it's not a big difference. I own another Lenovo laptop. If I set the mic to 100% on this old laptop it's a difference like day and night to the T14 Gen3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] [NEW] [UBUNTU 20.04] boot: Add secure boot trailer
You have been subscribed to a public bug: 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 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-200452 severity-critical targetmilestone-inin--- -- [UBUNTU 20.04] boot: Add secure boot trailer https://bugs.launchpad.net/bugs/1996071 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 1996069] [NEW] [UBUNTU 20.04] zipl: Add secure boot trailer (s390-tools part)
You have been subscribed to a public bug: 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 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-200453 severity-high targetmilestone-inin--- -- [UBUNTU 20.04] zipl: Add secure boot trailer (s390-tools part) https://bugs.launchpad.net/bugs/1996069 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 1996068] [NEW] i915 crash at boot time (probably to activate vga console)
You have been subscribed to a public bug: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [2.211045] ? 0xc098b000 Nov 5 09:46:42 shusaku kernel: [2.211046] do_one_initcall+0x5b/0x240 Nov 5 09:46:42 shusaku kernel: [2.211049] do_init_module+0x50/0x210 Nov 5 09:46:42 shusaku kernel: [2.211051] load_module+0xb7d/0xcd0 Nov 5 09:46:42 shusaku kernel: [2.211053] __do_sys_finit_module+0xc4/0x140 Nov 5 09:46:42 shusaku kernel: [2.211054] ? __do_sys_finit_module+0xc4/0x140 Nov 5 09:46:42 shusaku kernel: [2.211056] __x64_sys_finit_module+0x18/0x30
[Kernel-packages] [Bug 1995408] Re: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks
** Changed in: linux-azure (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1995408 Title: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] Hypervisor only allocates interrupts to happen on a single physical GPU, which can lead to CPU soft locks when using PCI NVME under heavy load. Kinetic will get this patch via stable updates. [Test Case] Microsoft tested [Where things could go wrong] Hypervisor PCI driver may not load correctly. Patch did not apply cleanly and could lead to merge conflicts once the upstream patch is pulled in. [Other Info] SF: #00346549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1995408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988429] Re: support linux-oem-6.0
This bug was fixed in the package nvidia-graphics-drivers-510 - 510.85.02-0ubuntu0.22.04.2 --- nvidia-graphics-drivers-510 (510.85.02-0ubuntu0.22.04.2) jammy; urgency=medium * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_6.0.patch: - Add support for Linux 6.0 (LP: #1988429). -- Alberto Milone Thu, 01 Sep 2022 16:14:06 + ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1988429 Title: support linux-oem-6.0 Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Triaged Bug description: [Impact] Building nvidia dkms against linux 6.0 fails. The compat code needs updates to support 6.0. [Test case] Check that it builds after fixes applied. [What could go wrong] The compat code changes affect only builds on 6.0, so there's no chance of it breaking build for other kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1988429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
@Chris, 1) as per Intel, increased cpu power may throttle iGPU, the current thermald can't balance this issue. Ref. https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1944389/comments/23 2.1) i can't answer what testing does upstream do. i asked this but didn't get answer. @Srinivas, could you help on this? 2.2) cant find the machine older than KBL in canonical cert lab. I am still looking for those and request to Dell. in case, if can't find the older machine, how could we do? 3.1) just check which kernel support this. if there're some patches missed in generic/oem kernels, I would sru. 4.1) for sandybridge, Im looking for the machines older than kbl. in case , can't find them, how could I do? i only could get the way that user could report it on launchpad. -- 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 each supported 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. 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 Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995870] Re: BUG: scheduling while atomic: ip/1210/0x00000200 on xenial/hwe rumford
** Changed in: linux-hwe (Ubuntu) Status: Confirmed => In Progress ** Description changed: + [Impact] + + There were BUG: scheduling while atomic: ip/1210/0x0200 appearing + on xenial/hwe with the tg3 ethernet driver when running on rumford instance. + Probably some performace degradation as the driver was trying to sleep while + holding a spinlock. + There also was cluttering of the kernel log with stack traces. + + [Fix] + + Change usleep_range -> udelay which is safe to call from atomic + contexts. + + [Test] + + Compile tested only. Should see this resolved in the next cycle on + xenial/hwe rumford instance. + + [Where problems could occur] + + Not much regression potential as the correct delay call is now being + called. + + + -- + There is a bug being triggered on a usleep within the tg3 driver with xenial/linux-hwe 4.15.0-197.208~16.04.1 on rumford. This has been observed in multiple cycles during boot-testing. [ 27.437584] BUG: scheduling while atomic: ip/1210/0x0200 [ 27.468440] Modules linked in: nls_iso8859_1 intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp ipmi_ssif kvm_intel hpilo kvm irqbypass intel_cstate shpchp ioatdma dca intel_rapl_perf ipmi_si ipmi_devintf lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ses crct10dif_pclmul enclosure crc32_pclmul ttm ghash_clmulni_intel drm_kms_helper mlx5_core pcbc syscopyarea aesni_intel mlxfw sysfillrect sysimgblt aes_x86_64 fb_sys_fops tg3 devlink crypto_simd hpsa nvme glue_helper ptp drm cryptd pps_core nvme_core scsi_transport_sas wmi [ 27.468491] CPU: 1 PID: 1210 Comm: ip Not tainted 4.15.0-197-generic #208~16.04.1-Ubuntu [ 27.468493] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 05/21/2018 [ 27.468494] Call Trace: [ 27.468508] dump_stack+0x6d/0x8b [ 27.468515] __schedule_bug+0x54/0x70 [ 27.468519] __schedule+0x635/0x8b0 [ 27.468522] schedule+0x36/0x80 [ 27.468527] schedule_hrtimeout_range_clock+0xbc/0x1b0 [ 27.468532] ? __hrtimer_init+0x90/0x90 [ 27.468536] schedule_hrtimeout_range+0x13/0x20 [ 27.468539] usleep_range+0x62/0x90 [ 27.468547] tg3_ape_event_lock+0x36/0xa0 [tg3] [ 27.468552] tg3_ape_driver_state_change.part.69+0xc6/0x160 [tg3] [ 27.468557] tg3_start+0xebc/0x10b0 [tg3] [ 27.468563] tg3_open+0x130/0x280 [tg3] [ 27.468568] __dev_open+0xd7/0x150 [ 27.468572] __dev_change_flags+0x186/0x1c0 [ 27.468575] dev_change_flags+0x29/0x70 [ 27.468580] do_setlink+0x355/0xd90 [ 27.468589] ? nla_parse+0xa7/0x120 [ 27.468592] rtnl_newlink+0x773/0x8f0 [ 27.468597] ? do_anonymous_page+0x24b/0x430 [ 27.468605] ? ns_capable_common+0x2b/0x50 [ 27.468608] ? ns_capable+0x10/0x20 [ 27.468612] rtnetlink_rcv_msg+0x205/0x290 [ 27.468615] ? _cond_resched+0x1a/0x50 [ 27.468620] ? __kmalloc_node_track_caller+0x201/0x2c0 [ 27.468623] ? rtnl_calcit.isra.25+0x100/0x100 [ 27.468627] netlink_rcv_skb+0xd9/0x110 [ 27.468630] rtnetlink_rcv+0x15/0x20 [ 27.468633] netlink_unicast+0x198/0x260 [ 27.468637] netlink_sendmsg+0x2ea/0x410 [ 27.468640] sock_sendmsg+0x3e/0x50 [ 27.468642] ___sys_sendmsg+0x2e9/0x300 [ 27.468646] ? lru_cache_add_active_or_unevictable+0x36/0xb0 [ 27.468649] ? do_anonymous_page+0x24b/0x430 [ 27.468653] ? __handle_mm_fault+0xae7/0xc80 [ 27.468657] __sys_sendmsg+0x54/0x90 [ 27.468659] ? __sys_sendmsg+0x54/0x90 [ 27.468662] SyS_sendmsg+0x12/0x20 [ 27.468667] do_syscall_64+0x73/0x130 [ 27.468670] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 27.468673] RIP: 0033:0x7f285dd57590 [ 27.468675] RSP: 002b:7ffd4370bf38 EFLAGS: 0246 ORIG_RAX: 002e [ 27.468678] RAX: ffda RBX: 7ffd43714040 RCX: 7f285dd57590 [ 27.468679] RDX: RSI: 7ffd4370bf80 RDI: 0003 [ 27.468681] RBP: 6364ddd8 R08: 0040 R09: 0008 [ 27.468682] R10: 05e7 R11: 0246 R12: 7ffd4370bf80 [ 27.468683] R13: R14: 006573a0 R15: 7ffd43714018 [ 27.468703] NOHZ: local_softirq_pending 282 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1995870 Title: BUG: scheduling while atomic: ip/1210/0x0200 on xenial/hwe rumford Status in linux-hwe package in Ubuntu: In Progress Status in linux-hwe source package in Xenial: New Bug description: [Impact] There were BUG:
