May 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1186194] New: Many processes and up in D state after system resume (5.12.3-1-default, git 25d4ec7)
by bugzilla_noreply＠suse.com 01 Jul '21

01 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1186194 Bug ID: 1186194 Summary: Many processes and up in D state after system resume (5.12.3-1-default, git 25d4ec7) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de CC: oneukum(a)suse.com Found By: --- Blocker: --- Created attachment 849440 --> https://bugzilla.suse.com/attachment.cgi?id=849440&action=edit Output of SysRq-T I'm using a Dell laptop (Inspiron 7373) with a USB ethernet adapter (17ef:7205 Lenovo Thinkpad LAN, driver r8152). Sometimes, after resume, network-related utilities (e.g. ip, ping) freeze in D state. No communication over IP networks is possible. Attached is SysRq-T from the malfunctioning state. From my POV, the following stand out: May 18 11:00:34 fmn kernel: task:teams state:D stack: 0 pid: 316 ppid: 3234 flags:0x00000000 May 18 11:00:34 fmn kernel: Call Trace: May 18 11:00:34 fmn kernel: __schedule+0x2ee/0x950 May 18 11:00:34 fmn kernel: schedule+0x46/0xb0 May 18 11:00:34 fmn kernel: rpm_resume+0x19c/0x7b0 May 18 11:00:34 fmn kernel: ? wait_woken+0x80/0x80 May 18 11:00:34 fmn kernel: rpm_resume+0x2e7/0x7b0 May 18 11:00:34 fmn kernel: ? kernfs_fop_open+0x2a8/0x3a0 May 18 11:00:34 fmn kernel: __pm_runtime_resume+0x4a/0x80 May 18 11:00:34 fmn kernel: usb_autopm_get_interface+0x18/0x50 [usbcore] May 18 11:00:34 fmn kernel: rtl8152_get_link_ksettings+0x27/0x80 [r8152] May 18 11:00:34 fmn kernel: speed_show+0x6e/0xb0 May 18 11:00:34 fmn kernel: dev_attr_show+0x19/0x40 May 18 11:00:34 fmn kernel: sysfs_kf_seq_show+0xa6/0xe0 May 18 11:00:34 fmn kernel: seq_read_iter+0x1e1/0x510 May 18 11:00:34 fmn kernel: new_sync_read+0x115/0x1a0 May 18 11:00:34 fmn kernel: vfs_read+0x14b/0x1a0 May 18 11:00:34 fmn kernel: ksys_read+0x5f/0xe0 May 18 11:00:34 fmn kernel: do_syscall_64+0x33/0x80 May 18 11:00:34 fmn kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae AND May 18 11:00:34 fmn kernel: task:kworker/3:2 state:D stack: 0 pid:23489 ppid: 2 flags:0x00004000 May 18 11:00:34 fmn kernel: Workqueue: pm pm_runtime_work May 18 11:00:34 fmn kernel: Call Trace: May 18 11:00:34 fmn kernel: __schedule+0x2ee/0x950 May 18 11:00:34 fmn kernel: schedule+0x46/0xb0 May 18 11:00:34 fmn kernel: schedule_timeout+0x8b/0x140 May 18 11:00:34 fmn kernel: ? __next_timer_interrupt+0x100/0x100 May 18 11:00:34 fmn kernel: msleep+0x2a/0x40 May 18 11:00:34 fmn kernel: napi_disable+0x2b/0x70 May 18 11:00:34 fmn kernel: rtl8152_suspend+0x2ad/0x340 [r8152] May 18 11:00:34 fmn kernel: usb_suspend_both+0x9d/0x230 [usbcore] May 18 11:00:34 fmn kernel: usb_runtime_suspend+0x2b/0x70 [usbcore] May 18 11:00:34 fmn kernel: ? usb_autoresume_device+0x50/0x50 [usbcore] May 18 11:00:34 fmn kernel: __rpm_callback+0x81/0x140 May 18 11:00:34 fmn kernel: rpm_callback+0x4f/0x70 May 18 11:00:34 fmn kernel: ? usb_autoresume_device+0x50/0x50 [usbcore] May 18 11:00:34 fmn kernel: rpm_suspend+0x147/0x6f0 May 18 11:00:34 fmn kernel: ? __switch_to+0x26f/0x450 May 18 11:00:34 fmn kernel: pm_runtime_work+0x8e/0x90 May 18 11:00:34 fmn kernel: process_one_work+0x1df/0x370 May 18 11:00:34 fmn kernel: worker_thread+0x50/0x400 May 18 11:00:34 fmn kernel: ? process_one_work+0x370/0x370 May 18 11:00:34 fmn kernel: kthread+0x11b/0x140 May 18 11:00:34 fmn kernel: ? __kthread_bind_mask+0x60/0x60 May 18 11:00:34 fmn kernel: ret_from_fork+0x22/0x30 -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 1185824] New: Kernel 5.12.0-2 crash (video)
by bugzilla_noreply＠suse.com 29 Jun '21

29 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185824 Bug ID: 1185824 Summary: Kernel 5.12.0-2 crash (video) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: 7eggert(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With kernel 5.12.0-2, my system crashes reliably. I can't run any program after this happens. Bug Video: https://youtu.be/u677fL_iB_8 System: Dell Inc. Precision T1500/0XC7MM, BIOS 2.0.1 11/30/2009 Working kernel:# uname -a Linux be10 5.11.6-1-default #1 SMP Thu Mar 11 16:11:36 UTC 2021 (7358b30) x86_64 x86_64 x86_64 GNU/Linux # lspci 00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11) 00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11) 00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11) 00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11) 00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11) 00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11) 00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11) 00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11) 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) 00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06) 00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6) 00:1f.0 ISA bridge: Intel Corporation H57 Chipset LPC Interface Controller (rev 06) 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 06) 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti HDMI Audio [Radeon HD 7870 XT / 7950/7970] 02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM57780 Gigabit Ethernet PCIe (rev 01) 03:01.0 SCSI storage controller: Adaptec AHA-2930CU (rev 03) ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04) ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04) ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04) ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04) ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04) ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04) ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04) ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04) ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04) ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04) ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04) ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04) ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04) ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04) ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04) Bug Video: https://youtu.be/u677fL_iB_8 -- You are receiving this mail because: You are the assignee for the bug.

1 10

[kernel-bugs] [Bug 1176351] New: Audio device: Intel Corporation Device 02c8: not detected
by bugzilla_noreply＠suse.com 22 Jun '21

22 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1176351 Bug ID: 1176351 Summary: Audio device: Intel Corporation Device 02c8: not detected Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've got a new notebook, Intel chipsets only, where everythings works - except for audio. It appears the audio chip/sound card are not detected by the kernel or initialized. lspci -v has: 00:1f.3 Audio device: Intel Corporation Device 02c8 (prog-if 80) Subsystem: Lenovo Device 22be Flags: fast devsel, IRQ 16, IOMMU group 13 Memory at ea33c000 (64-bit, non-prefetchable) [size=16K] Memory at ea000000 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 <?> Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ Kernel modules: snd_hda_intel, snd_soc_skl, snd_sof_pci # lsmod | grep snd snd 114688 1 thinkpad_acpi soundcore 16384 1 snd # cat /proc/asound/cards --- no soundcards --- # dmesg | grep audio [ 18.072024] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [ 18.072026] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 18.072036] sof-audio-pci 0000:00:1f.3: enabling device (0004 -> 0006) [ 18.072179] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [ 18.072267] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 18.078993] sof-audio-pci 0000:00:1f.3: use msi interrupt mode [ 18.109492] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5 [ 18.109493] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 18.109497] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 4 [ 18.109521] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-cml.ri failed with error -2 [ 18.109522] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-cml.ri failed err: -2 [ 18.109524] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 [ 18.110449] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 [ 220.595600] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [ 220.595605] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 220.595786] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [ 220.595899] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 220.601386] sof-audio-pci 0000:00:1f.3: use msi interrupt mode [ 220.630638] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5 [ 220.630640] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 220.630644] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 4 [ 220.630664] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-cml.ri failed with error -2 [ 220.630666] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-cml.ri failed err: -2 [ 220.630669] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 [ 220.631004] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 1180058] New: Please don't create /boot/do_purge_kernels on initial install
by bugzilla_noreply＠suse.com 22 Jun '21

22 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1180058 Bug ID: 1180058 Summary: Please don't create /boot/do_purge_kernels on initial install Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dcermak(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently the %post scriptlet of the kernel creates /boot/do_purge_kernels to trigger zypper's kernel purging. Could this be modified so that it only creates this file on upgrades and *not* on fresh installations? Currently this will cause zypper to try to purge old kernels on fresh installations. While that is short, it can cause noticeable delays until zypper can be used again, especially in resource constrained systems. Could the creation of this file be adjusted so that it is only created on upgrades and not on new installations? -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 1180917] New: kernel BUG at mm/huge_memory.c:2144!
by bugzilla_noreply＠suse.com 18 Jun '21

18 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180917 Bug ID: 1180917 Summary: kernel BUG at mm/huge_memory.c:2144! Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: azouhr(a)opensuse.org QA Contact: qa-bugs(a)suse.de CC: ihno(a)suse.com, ro(a)suse.de, sarah.kriesch(a)ibm.com Found By: --- Blocker: --- Recently, a number of packages fails to build and instead hangs with the command cc1plus. In a recent build, I found a kernel trace in a hanging worker: [ 608s] [ 596.875979] kernel BUG at mm/huge_memory.c:2144! [ 608s] [ 596.876290] monitor event: 0040 ilc:2 [#1] SMP [ 608s] [ 596.876374] Modules linked in: sha256_s390 sha_common overlay sd_mod t10_pi nls_iso8859_1 nls_cp437 vfat fat virtio_rng rng_core virtio_blk xfs btrfs blake2b_generic xor raid6_pq libcrc32c crc32_vx_s390 reiserfs squashfs fuse dm_snapshot dm_bufio dm_crypt dm_mod binfmt_misc loop sg scsi_mod [ 608s] [ 596.876666] CPU: 1 PID: 2660 Comm: cc1plus Not tainted 5.10.5-1-default #1 openSUSE Tumbleweed [ 608s] [ 596.876750] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 608s] [ 596.876797] Krnl PSW : 0704e00180000000 00000000e33fb9ea (__split_huge_pmd+0x62a/0xc30) [ 608s] [ 596.877158] R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 608s] [ 596.877328] Krnl GPRS: 0000000000000000 00000000b2b40215 0000000003c91000 fffffffffffff800 [ 608s] [ 596.877408] 0000000081691a00 00000000f2440237 00000000000000c0 0000000000000000 [ 608s] [ 596.877493] 0000000081691800 000003d083c91030 0000000086d81d48 000003ff71a40000 [ 608s] [ 596.877567] 0000000086c1c000 00000000e47c4268 00000000e33fb748 000003e003ef3a80 [ 608s] [ 596.877652] Krnl Code: 00000000e33fb9de: a71f0400 cghi %r1,1024 [ 608s] [ 596.877652] 00000000e33fb9e2: a784ff18 brc 8,00000000e33fb812 [ 608s] [ 596.877652] #00000000e33fb9e6: af000000 mc 0,0 [ 608s] [ 596.877652] >00000000e33fb9ea: a55b0602 oill %r5,1538 [ 608s] [ 596.877652] 00000000e33fb9ee: a7f4ff06 brc 15,00000000e33fb7fa [ 608s] [ 596.877652] 00000000e33fb9f2: e32010080004 lg %r2,8(%r1) [ 608s] [ 596.877652] 00000000e33fb9f8: a7210001 tmll %r2,1 [ 608s] [ 596.877652] 00000000e33fb9fc: a77401f1 brc 7,00000000e33fbdde [ 608s] [ 596.878162] Call Trace: [ 608s] [ 596.878190] [<00000000e33fb9ea>] __split_huge_pmd+0x62a/0xc30 [ 608s] [ 596.878257] ([<00000000e33fb6ca>] __split_huge_pmd+0x30a/0xc30) [ 608s] [ 596.878327] [<00000000e3379116>] zap_p4d_range+0x246/0xbb0 [ 608s] [ 596.878396] [<00000000e33808f6>] zap_page_range+0x1a6/0x2e0 [ 608s] [ 596.878458] [<00000000e33b2e14>] do_madvise.part.0+0x844/0xc70 [ 608s] [ 596.879153] [<00000000e33b32a8>] __s390x_sys_madvise+0x68/0x80 [ 608s] [ 596.879247] [<00000000e3c676bc>] system_call+0xe0/0x2ac [ 608s] [ 596.879347] Last Breaking-Event-Address: [ 608s] [ 596.879390] [<00000000e33fb9b2>] __split_huge_pmd+0x5f2/0xc30 [ 608s] [ 596.879465] ---[ end trace 50ad5147a244f7d2 ]--- I don't know if this is related boo#1163684 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1185513] New: ACPI BIOS Error after upgrade to 5.12.0-1-default
by bugzilla_noreply＠suse.com 17 Jun '21

17 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185513 Bug ID: 1185513 Summary: ACPI BIOS Error after upgrade to 5.12.0-1-default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: iqgrande(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I recently updated to the 5.12.0-1-default kernel with openSUSE Tumbleweed and now I see the following messages during boot. These were not there before. The system seems to be fully functioning. There are updates to the BIOS I could try (however I'm afraid to as I've been burned updating the BIOS before) however I thought I'd start here first since it was the Linux kernel change (or whatever else came in the update this morning) that prompted it. Are there any thoughts on this? Thank you for your help with this. {{{ > dmesg | grep AE_NOT_FOUND [ 1.149107] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149136] ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149187] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149212] ACPI Error: Aborting method \_PR.PR02._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149262] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149287] ACPI Error: Aborting method \_PR.PR03._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149335] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149360] ACPI Error: Aborting method \_PR.PR04._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149408] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149433] ACPI Error: Aborting method \_PR.PR05._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149481] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149506] ACPI Error: Aborting method \_PR.PR06._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149553] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149578] ACPI Error: Aborting method \_PR.PR07._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149626] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149650] ACPI Error: Aborting method \_PR.PR08._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149698] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149723] ACPI Error: Aborting method \_PR.PR09._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149770] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149794] ACPI Error: Aborting method \_PR.PR10._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149842] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149867] ACPI Error: Aborting method \_PR.PR11._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) }}} -- You are receiving this mail because: You are the assignee for the bug.

1 33

[kernel-bugs] [Bug 1177009] New: Leap 15.2 stopped working in KVM with ovmf-ia32 firmware
by bugzilla_noreply＠suse.com 16 Jun '21

16 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1177009 Bug ID: 1177009 Summary: Leap 15.2 stopped working in KVM with ovmf-ia32 firmware Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Build Identifier: I'm reporting as a kernel bug, but it might be a bug elsewhere. And yes, I know that this is not a supported configuration. Situation: I have both Leap 15.2 and Tumbleweed installed side by side in a KVM virtual machine, using 32-bit efi for booting. Both Leap and Tumbleweed are 64-bit. I originally setup this VM under Leap 15.0 (as KVM host machine). Everything had been working well. However, I recently tried to boot the Leap 15.2 system in that VM, and it failed to boot. I see the kernel and initrd being loaded. And then there is a reset and I get back to the boot screen. However, Tumbleweed continues to boot without a problem on that virtual machine. I am booting with "grub2-i386-efi", which is installed for both Tumbleweed and for Leap 15.2. This does not appear to be a grub2 problem, because the kernel and initrd are being loaded. Before today, I most recently booted Leap 15.2 on Sept 22, and I updated it at that time. I then rebooted (successfully) to check after the update. I have not been able to boot since, until my workaround today. The KVM host is also running Leap 15.2, and I did apply some updates since Sept 22. My guess is that one of those updates affected how the virtualization is working. I have a similar install of Leap 15.2 on an external USB drive, and I have that setup so that it can boot with legacy BIOS, with 64-bit efi and with 32-bit efi. Testing with that, it also fails to boot the same virtual machine with 32-bit efi, bit it successfully boots with either legacy BIOS or with 64-bit efi. So it looks as if whatever is going wrong has to do with communication between the kernel and the 32-bit efi firmware. Booting the virtual machine to Tumbleweed, then setting up for rescue/chroot, I have installed kernel 5.8.11-1.gf4bb27a-default from the stable kernels repo. And now Leap 15.2 does boot successfully with that kernel. It does not boot with any of the 5.3.x kernels for Leap 15.2 that I have tested. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 1183056] New: Leap 15.3 kernel cannot load on a system with 32-bit UEFI
by bugzilla_noreply＠suse.com 16 Jun '21

16 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183056 Bug ID: 1183056 Summary: Leap 15.3 kernel cannot load on a system with 32-bit UEFI Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Build Identifier: I see this as related to bug 1172292 It seems impossible to load a Leap 15.3 kernel with 32-bit UEFI firmware. I tried several ways, but could not boot the installer. I eventually installed to a KVM virtual machine using legacy booting. I then took the installed memory image, and converted that to using 32-bit UEFI with ovmf-ia32-{code,vars}.bin firmware. And that still would not boot. I now have it successfully booting with kernel-default-5.3.18-lp152.63.1 which is a kernel from Leap 15.2. But it will not boot with the Leap 15.3 kernel. I'll grant that this is not an officially supported setup. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1184403] New: iwlwifi driver failing to load in current MicroOS Desktop image
by bugzilla_noreply＠suse.com 14 Jun '21

14 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1184403 Bug ID: 1184403 Summary: iwlwifi driver failing to load in current MicroOS Desktop image Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: martin.rohde(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Right upon installation I get the following errors during boot and connection via WiFi and LAN cable fail: iwlwifi: not suitable firmware found iwlwifi: minimum version required: iwlwifi-6000g2a-5 iwlwifi: maximum version supported: iwlwifi-6000g2a-6 -- You are receiving this mail because: You are the assignee for the bug.

1 23

[Bug 1186320] New: Current driver (module pl2303.ko) for Prolific chip 23a3 does not work on Leap 15.2 kernel
by bugzilla_noreply＠suse.com 07 Jun '21

07 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1186320 Bug ID: 1186320 Summary: Current driver (module pl2303.ko) for Prolific chip 23a3 does not work on Leap 15.2 kernel Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jfharrison(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Prolific USB to Full UART Bridge Controller with GPIO Chip PL2303GC Part No. PL2303G4ZJG8P2 Chip Product ID 23a3 From dmesg using kernel Linux 5.3.18-lp152.75-default [ 1434.839253] usb 5-2: new full-speed USB device number 3 using uhci_hcd [ 1435.038231] usb 5-2: New USB device found, idVendor=067b, idProduct=23a3, bcdDevice= 1.05 [ 1435.038238] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1435.038243] usb 5-2: Product: USB-Serial Controller [ 1435.038247] usb 5-2: Manufacturer: Prolific Technology Inc. [ 1435.038251] usb 5-2: SerialNumber: BUAMj19B616 output from lusb: T: Bus=05 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=067b ProdID=23a3 Rev=01.05 S: Manufacturer=Prolific Technology Inc. S: Product=USB-Serial Controller S: SerialNumber=BUAMj19B616 C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) I updated kernel to stable 15.12.4-5.gcf6ea2f and the pl2303 module in that kernel works perfectly. It is using module pl2303.ko.xz Hopefully that module can be included in the Leap15.3 release. -- You are receiving this mail because: You are the assignee for the bug.

1 10