December 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1180402] New: Wifi doesn't work in kernel 5.10.1
by bugzilla_noreply＠suse.com 28 Dec '20

28 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1180402 Bug ID: 1180402 Summary: Wifi doesn't work in kernel 5.10.1 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: quiquoqua48(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I've update to kernel 5.10.1 and wifi doesn't work. When the desktop is loaded, automatically go in fly mode and there is no way to turn on wifi. In wicked, I can see the configured device, but it doesn't work, and if I try to scan for networks the popup message "searching for networks" appears just for half a second, then disappear and no networks are found. My network controller is this (from lshw): *-network description: Network controller product: Comet Lake PCH CNVi WiFi vendor: Intel Corporation physical id: 14.3 bus info: pci@0000:00:14.3 version: 00 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list configuration: driver=iwlwifi latency=0 resources: irq:16 memory:c5498000-c549bfff -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1180344] iwlwifi: Kernel 5.10 fails to boot with workqueue lockup
by bugzilla_noreply＠suse.com 28 Dec '20

28 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1180344 http://bugzilla.opensuse.org/show_bug.cgi?id=1180344#c44 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |quiquoqua48(a)gmail.com --- Comment #44 from Takashi Iwai <tiwai(a)suse.com> --- *** Bug 1180402 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180301] Update kernel-firmware to latest to support latest AMD graphics cards/Intel Bluetooth
by bugzilla_noreply＠suse.com 28 Dec '20

28 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1180301 https://bugzilla.suse.com/show_bug.cgi?id=1180301#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tiwai(a)suse.com Resolution|--- |FIXED --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Done. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180394] "ACPI Error: AE_NOT_FOUND" during boot
by bugzilla_noreply＠suse.com 28 Dec '20

28 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1180394 https://bugzilla.suse.com/show_bug.cgi?id=1180394#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo?(antoine@copernic. | |xyz) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- It's likely a bug of your BIOS/ACPI firmware, and kernel can't help much for that. Do you see any relevant kernel problem? Otherwise this kind of BIOS bug is harmless and can be ignored. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180381] [Build 20201225] [s390x] Kernel Panic - No TPM chip found, activating TPM-bypass
by bugzilla_noreply＠suse.com 28 Dec '20

28 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1180381 https://bugzilla.suse.com/show_bug.cgi?id=1180381#c6 Berthold Gunreben <azouhr(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |slindomansilla(a)suse.com Flags|needinfo?(ihno(a)suse.com) |needinfo?(slindomansilla@su | |se.com) --- Comment #6 from Berthold Gunreben <azouhr(a)opensuse.org> --- (In reply to Berthold Gunreben from comment #4) > (In reply to Berthold Gunreben from comment #3) > > (In reply to Petr Tesa��k from comment #2) > > > I'd like to understand why we're getting the DMS044E error message from CMS. > > > > Good catch. And it I also don't understand it so far. So, what qaboot does > > is retrieve the file (ftpboot.initrd.t) from the ftpserver, and then uses > > pipe with fblock to created fixed length records. > > > > 'pipe < ftpboot initrd t | fblock 80 00 | > ftpboot initrd t' > > > > For some reason, that does not seem to work as desired. > > I should have read the next line: > > 'DMSERD107S Disk T(FFFF) is full > > This is a disk in memory, and as you can see from the log, it has 20000 > Blocks (with 512 Bytes each) > > 10MB is definitly not enough for kernel and initrd, this looks like a setup > issue in z/VM. > > Ihno, could you please have a look? sorry, it is not 20000, but 200000 blocks. However, it looks like this is not enough. This should be increased in qaboot exec, please search for the line 'define vfb-512 as ffff blk 200000' and update accordingly. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180389] New: Unable to boot with Wireless card on
by bugzilla_noreply＠suse.com 28 Dec '20

28 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1180389 Bug ID: 1180389 Summary: Unable to boot with Wireless card on 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: songchuan.kang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 844716 --> http://bugzilla.opensuse.org/attachment.cgi?id=844716&action=edit output of `journalctl -b` Fresh install with Tumbleweed 20201225 using virt-manager, everything works well until I pass through the wireless card to virtual machine. With the wireless card passed through, the system was stuck on the boot screen. Logs are attached. Wireless card info: > 0000:00:14:3 Intel Corporation Comet Lake PCH-LP CNVi WiFi -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1180344] iwlwifi: Kernel 5.10 fails to boot with workqueue lockup
by bugzilla_noreply＠suse.com 28 Dec '20

28 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1180344 http://bugzilla.opensuse.org/show_bug.cgi?id=1180344#c41 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |songchuan.kang(a)suse.com --- Comment #41 from Takashi Iwai <tiwai(a)suse.com> --- *** Bug 1180389 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180394] New: "ACPI Error: AE_NOT_FOUND" during boot
by bugzilla_noreply＠suse.com 28 Dec '20

28 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1180394 Bug ID: 1180394 Summary: "ACPI Error: AE_NOT_FOUND" during boot 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: antoine(a)copernic.xyz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0 Build Identifier: The message "ACPI Error: AE_NOT_FOUND" appears during boot. The computer seems to be working anyway. Reproducible: Always Steps to Reproduce: 1. Start the computer 2. The error message appear Actual Results: The message "ACPI Error: AE_NOT_FOUND" appears during boot. Expected Results: no message antoine@Frankenstein:~> sudo dmidecode | grep -e Date -e Vendor -e Version -e Product | head -n 4 [sudo] Mot de passe de root�: Vendor: Award Software International, Inc. Version: F7 Release Date: 10/22/2012 Product Name: GA-970A-UD3 antoine@Frankenstein:~> dmesg | grep Error [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200925/dspkginit-438) [ 0.170125] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200925/dspkginit-438) [ 1.671066] RAS: Correctable Errors collector initialized. antoine@Frankenstein:~> uname -a Linux Frankenstein 5.10.1-1-default #1 SMP Sun Dec 20 07:24:34 UTC 2020 (d14c73f) x86_64 x86_64 x86_64 GNU/Linux antoine@Frankenstein:~> lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20201225 Codename: n/a antoine@Frankenstein:~> -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180381] [Build 20201225] [s390x] Kernel Panic - No TPM chip found, activating TPM-bypass
by bugzilla_noreply＠suse.com 28 Dec '20

28 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1180381 https://bugzilla.suse.com/show_bug.cgi?id=1180381#c4 Berthold Gunreben <azouhr(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(ihno(a)suse.com) --- Comment #4 from Berthold Gunreben <azouhr(a)opensuse.org> --- (In reply to Berthold Gunreben from comment #3) > (In reply to Petr Tesa��k from comment #2) > > I'd like to understand why we're getting the DMS044E error message from CMS. > > Good catch. And it I also don't understand it so far. So, what qaboot does > is retrieve the file (ftpboot.initrd.t) from the ftpserver, and then uses > pipe with fblock to created fixed length records. > > 'pipe < ftpboot initrd t | fblock 80 00 | > ftpboot initrd t' > > For some reason, that does not seem to work as desired. I should have read the next line: 'DMSERD107S Disk T(FFFF) is full This is a disk in memory, and as you can see from the log, it has 20000 Blocks (with 512 Bytes each) 10MB is definitly not enough for kernel and initrd, this looks like a setup issue in z/VM. Ihno, could you please have a look? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180381] [Build 20201225] [s390x] Kernel Panic - No TPM chip found, activating TPM-bypass
by bugzilla_noreply＠suse.com 27 Dec '20

27 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1180381 https://bugzilla.suse.com/show_bug.cgi?id=1180381#c3 --- Comment #3 from Berthold Gunreben <azouhr(a)opensuse.org> --- (In reply to Petr Tesa��k from comment #2) > (In reply to Sarah Kriesch from comment #1) > > ' 91 *-* \'punch ftpboot initrd t (noh\' > > ', > > ' >>> "punch ftpboot initrd t (noh" > > ', > > 'DMSPUN044E Record exceeds allowable maximum > > ', > > ' +++ RC(32) +++ > > ', > > AFAICS this is the root cause. The initrd could not be added to the virtual > punch. Since no block device driver is built in, and the dasd kernel module > was in the initrd (which is missing), the kernel cannot mount any root > device and panics. > > I'd like to understand why we're getting the DMS044E error message from CMS. Good catch. And it I also don't understand it so far. So, what qaboot does is retrieve the file (ftpboot.initrd.t) from the ftpserver, and then uses pipe with fblock to created fixed length records. 'pipe < ftpboot initrd t | fblock 80 00 | > ftpboot initrd t' For some reason, that does not seem to work as desired. For a slightly more verbose version of the error, see https://www.vm.ibm.com/library/640pdfs/64616105.pdf Page 43 (PDF Page 57): Explanation: The record length given exceeds the maximum record length allowed. For more information on the maximum record lengths allowed by the EDIT,PRINT and PUNCH commands, refer to z/VM: CMS Commands and Utilities Reference. System action:RC=32. Execution of the command is terminated. The system status remains the same. User response: ... For DMSPUN, you can change the record length with the COPYFILE command, and then reissue thecommand. Maybe we could have a LISTFILE on the contents of the T mode before the files get punched (would have to be added to qaboot rexx). -- You are receiving this mail because: You are the assignee for the bug.

1 0