November 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1173819] New: 'BUG: workqueue lockup' on ThunderX2 machines with kernel 4.12.14 in OBS

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1173819 Bug ID: 1173819 Summary: 'BUG: workqueue lockup' on ThunderX2 machines with kernel 4.12.14 in OBS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: adrian.schroeter(a)suse.com, afaerber(a)suse.com, dmueller(a)suse.com Found By: --- Blocker: --- obs-arm-7, -8 and -9 are often down in OBS these days due to kernel issues. One issue is a workqueue lockup: BUG: workqueue lockup - pool cpus=59 node=0 flags=0x0 nice=0 stuck for 92265s! -- You are receiving this mail because: You are the assignee for the bug.

5 hours, 18 minutes

1
7
0 0

[kernel-bugs] [Bug 1175105] New: mdadm doesn't except partition for --add because of "dirt" in that partition of a fresh gpt table

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1175105 Bug ID: 1175105 Summary: mdadm doesn't except partition for --add because of "dirt" in that partition of a fresh gpt table Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ralf(a)czekalla.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm about to migrate an important central private nextcloud server to 15.2. I'm use RAID1 for all my partitions and benefit from that with easy made clones with the help of mdadm by growing the number of raid-devices and adding a refreshed SSD with a new gpt partition table and cloned partitions descriptions. This worked for most of the six partitions but one. (It's not the first installation I transform with this idea. Did these processes already several times) This faulty one showed weird error messages I couldn't find a real good reason for, like ... ...on console: # mdadm --verbose /dev/md2 --add /dev/sdc5 mdadm: add new device failed for /dev/sdc5 as 4: Invalid argument # mdadm -E /dev/sdc5 /dev/sdc5: Magic : a92b4efc Version : 1.0 Feature Map : 0x9 Array UUID : 94bbbcd3:ad4d1b0b:dcd4d548:1af16050 Name : any:2 Creation Time : Fri Feb 2 20:09:03 2018 Raid Level : raid1 Raid Devices : 3 Avail Dev Size : 83892192 sectors (40.00 GiB 42.95 GB) Array Size : 41945984 KiB (40.00 GiB 42.95 GB) Used Dev Size : 83891968 sectors (40.00 GiB 42.95 GB) Super Offset : 83892208 sectors Unused Space : before=0 sectors, after=224 sectors State : active Device UUID : c9e17312:0069d580:42782958:8817e0f7 Internal Bitmap : -16 sectors from superblock Update Time : Mon Aug 10 18:09:21 2020 Bad Block Log : 512 entries available at offset -8 sectors - bad blocks present. Checksum : 7b5d72a - correct Events : 0 Device Role : spare Array State : AA. ('A' == active, '.' == missing, 'R' == replacing) First I was blinded by the "bad blocks present", but all devices checked out perfectly healthy in smart and also extended device scans didn't show any problems. Took me several hours to get through all this. dmesg: md: sdc5 does not have a valid v1.0 superblock, not importing! md: md_import_device returned -22 Also tried to --zero-superblock the partition of course. No change of behavior and still the above error message in dmesg remained. At the end I found a surprising hint on serverfault.com (https://serverfault.com/questions/696392/how-to-add-disk-back-to-raid-and-r…) from Oct. 2015 with a similar behavior that suggested to clean-up of the partition first with dd writing zeros (dd if=/dev/zero of=/dev/sdc5 status=progress) and try again later to add the last seemingly faulty partition. And long story short, this really worked. Somehow mdadm - and md behind - is choking on some dirt inside of partition blocks from old content before the disk/ssd was wiped with a new gpt partition table. (Of course with SSDs you try to prevent unnecessary writes and wiping every block of a disk first) I'm using md device type 1.0 here (in contrast to the serverfault.com case), where the RAID/md setup data is stored at the end of the partition. I had to wipe exactly this area at the end of the partition to add it afterwards successfully. Of course, no effect when doing this at the beginning of the partition (mentioned in the serverfault.com case) where md type 1.2 stores the md setup data. I think after 5 years this might need a clean up in mdadm or md device management. At least the error message should suggest to clean the partition first instead of this error message in dmesg. Also the --zero-superblock should wipe out the dirt beneath the superblock and not seemingly let some stuff leak here. Thanks Ralf -- You are receiving this mail because: You are the assignee for the bug.

2 months, 2 weeks

1
5
0 0

[kernel-bugs] [Bug 1176351] New: Audio device: Intel Corporation Device 02c8: not detected

by bugzilla_noreply＠suse.com

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.

4 months

1
15
0 0

[kernel-bugs] [Bug 1177009] New: Leap 15.2 stopped working in KVM with ovmf-ia32 firmware

by bugzilla_noreply＠suse.com

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.

4 months, 1 week

1
21
0 0

[kernel-bugs] [Bug 1176775] New: Problems after upgrade to openSUSE Leap 15.2

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1176775 Bug ID: 1176775 Summary: Problems after upgrade to openSUSE Leap 15.2 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: tbazant(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrade from 15.1 to 15.2 on my Dell Latitude 5300 2-in-1, the following happened: * network link dies after ~ 20 minutes of operations (both ethernet & wi-fi) * audio problems (microphone did not work) * `journalctl -f` was fludded with the following message: "hid-sensor-hub 001F:8087:0AC2.0002: hid_field_extract() called with n (192)" -- You are receiving this mail because: You are the assignee for the bug.

7 months, 3 weeks

1
13
0 0

[kernel-bugs] [Bug 1175646] New: After bios update, some keyboard function keys not recognized.

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1175646 Bug ID: 1175646 Summary: After bios update, some keyboard function keys not recognized. 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: zhonb(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I performed a bios update on a Dell precision 7530, which resolved my issue with the bug reported here: https://bugzilla.opensuse.org/show_bug.cgi?id=1175626 However, the new bios version (1.13.1) does not map the keyboard function keys correctly. Some work (e.g., volume control, keyboard backlight) and some don't (wifi toggle, screen brightness). Is there a way to map the new keyboard configuration in the bios so it works correctly in openSUSE? The keyboard functions correctly in windows. It does not work correctly in LEAP, tumbleweed or the latest fedora release. -- You are receiving this mail because: You are the assignee for the bug.

8 months

1
6
0 0

[kernel-bugs] [Bug 1178971] New: intel-ucode update crashes system on boot

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1178971 Bug ID: 1178971 Summary: intel-ucode update crashes system on boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When upgrading from ucode-intel-20200616-1.2.x86_64 to 20201110-1.1, my laptop crashes with a amusingly garbled screen right after selecting the kernel entry from grub. This is a Dell XPS 13 laptop with: 01: None 00.0: 10103 CPU [Created at cpu.462] Unique ID: rdCR.j8NaKXDZtZ6 Hardware Class: cpu Arch: X86-64 Vendor: "GenuineIntel" Model: 6.140.1 "11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz" Features: fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,syscall,nx,pdpe1gb,rdtscp,lm,constant_tsc,art,arch_perfmon,pebs,bts,rep_good,nopl,xtopology,nonstop_tsc,cpuid,aperfmperf,tsc_known_freq,pni,pclmulqdq,dtes64,monitor,ds_cpl,vmx,est,tm2,ssse3,sdbg,fma,cx16,xtpr,pdcm,pcid,sse4_1,sse4_2,x2apic,movbe,popcnt,tsc_deadline_timer,aes,xsave,avx,f16c,rdrand,lahf_lm,abm,3dnowprefetch,cpuid_fault,epb,cat_l2,invpcid_single,cdp_l2,ssbd,ibrs,ibpb,stibp,ibrs_enhanced,tpr_shadow,vnmi,flexpriority,ept,vpid,ept_ad,fsgsbase,tsc_adjust,bmi1,avx2,smep,bmi2,erms,invpcid,rdt_a,avx512f,avx512dq,rdseed,adx,smap,avx512ifma,clflushopt,clwb,intel_pt,avx512cd,sha_ni,avx512bw,avx512vl,xsaveopt,xsavec,xgetbv1,xsaves,split_lock_detect,dtherm,ida,arat,pln,pts,hwp,hwp_notify,hwp_act_window,hwp_epp,hwp_pkg_req,avx512vbmi,umip,pku,ospke,avx512_vbmi2,gfni,vaes,vpclmulqdq,avx512_vnni,avx512_bitalg,avx512_vpopcntdq,rdpid,movdiri,movdir64b,fsrm,avx512_vp2in tersect,md_clear,flush_l1 Clock: 2272 MHz BogoMips: 5606.40 Cache: 12288 kb Units/Processor: 16 Config Status: cfg=no, avail=yes, need=no, active=unknown And an otherwise uptodate BIOS firmware (according to fwupd). Rolling back the package update makes the system bootable again. -- You are receiving this mail because: You are the assignee for the bug.

8 months

1
21
0 0

[kernel-bugs] [Bug 1178274] New: ath11k: Driver and firmware not included

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1178274 Bug ID: 1178274 Summary: ath11k: Driver and firmware not included Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- While kernel-default 5.10rc1 (from Kernel:HEAD) includes the ath11k driver (fixed via 322b60ceb0f321b4b9c41717f7306c0dbaf0279b), the firmware is still missing even in kernel-firmware-20201023-338.1.noarch: [ 26.249141] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is experimental! [ 26.249178] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem 0x8e300000-0x8e3fffff 64bit] [ 26.249196] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002) [ 26.325561] mhi 0000:55:00.0: Requested to power ON [ 26.325648] mhi 0000:55:00.0: Power on setup success [ 26.325693] mhi 0000:55:00.0: Direct firmware load for ath11k/QCA6390/hw2.0/amss.bin failed with error -2 [ 26.325695] mhi 0000:55:00.0: Error loading firmware: -2 https://github.com/kvalo/ath11k-firmware might still be missing? -- You are receiving this mail because: You are the assignee for the bug.

8 months, 1 week

1
9
0 0

[kernel-bugs] [Bug 1179387] New: Fubar X with Radeon AGP on Pentium III Coppermine

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1179387 Bug ID: 1179387 Summary: Fubar X with Radeon AGP on Pentium III Coppermine Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 32bit OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 843962 --> http://bugzilla.opensuse.org/attachment.cgi?id=843962&action=edit dmesg & journal tails beginning at each first radeon string; lscpu Initial Summary: Fubar X with Radeon AGP on Pentium III Coppermine forum thread: https://forums.opensuse.org/showthread.php/547620-Tumbleweed-DVD-i586-Snaps… Just guessing that this is a kernel driver bug rather than an X bug, hence the kernel component selected. When the login manager tries to load, all that ultimately paints is the background graphic. WINDOWMANAGER=/usr/bin/icewm startx produces a black screen with mouse pointer. Xorg.0.log shows no apparent problem. No apparent difference whether using kernel 5.9.10 or 5.8.15. Vttys work as expected. Replacing the Radeon AGP rv250 ID: 1002:4c66 gfxcard with a Matrox G400 makes X work entirely as expected. # inxi -Ca CPU: Info: Single Core model: Pentium III (Coppermine) socket: Slot-1 bits: 32 type: MCP arch: P6 III Coppermine family: 6 model-id: 8 stepping: 1 microcode: D L1 cache: 16 KiB L2 cache: 256 KiB flags: pae sse bogomips: 1403 Speed: 702 MHz min/max: N/A base/boost: 700/850 volts: 3.3 V ext-clock: 100 MHz Core speed (MHz): 1: 702 Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported Type: l1tf status: Vulnerable Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled Type: meltdown status: Vulnerable Type: spec_store_bypass status: Vulnerable Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected # inxi -GISMy System: Host: s2846 Kernel: 5.8.15-1-default i686 bits: 32 Console: tty 3 Distro: openSUSE Tumbleweed 20201127 Machine: Type: Desktop Mobo: Tyan model: Intel 440BX/GX v: Rev. 4 serial: 00000000 BIOS: American Megatrends v: 063101 date: 07/15/99 Graphics: Device-1: AMD RV250/M9 GL [Mobility FireGL 9000/Radeon 9000] driver: radeon v: kernel Display: server: X.org 1.20.9 driver: ati,radeon unloaded: fbdev,modesetting,vesa tty: 180x56 Message: Advanced graphics data unavailable in console for root. Info:...Shell: Bash inxi: 3.1.09 -- You are receiving this mail because: You are the assignee for the bug.

8 months, 1 week

1
19
0 0

[kernel-bugs] [Bug 1173776] New: media: add support for eyeTV Geniatech T2 lite

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1173776 Bug ID: 1173776 Summary: media: add support for eyeTV Geniatech T2 lite Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: thomas(a)abiwatch.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Would you consider to pick following patch into your kernel for Leap 15.2? commit 14494583336880640654300c76d0f5df3360d85f media: dvbsky: add support for eyeTV Geniatech T2 lite It went in to v5.5 and later it got automatically added to stable v5.4.y. It should apply cleanly and just work. -- You are receiving this mail because: You are the assignee for the bug.

8 months, 2 weeks

1
9
0 0

2021

2020

openSUSE Kernel Bugs November 2020

2021

2020

openSUSE Kernel Bugs November 2020 ----- 2021 ----- October 2021 September 2021 August 2021 July 2021 June 2021 May 2021 April 2021 March 2021 February 2021 January 2021 ----- 2020 ----- December 2020 November 2020 October 2020 September 2020 August 2020 July 2020 June 2020 May 2020

openSUSE Kernel Bugs November 2020