November 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1179404] New: dbench4 regression on machines dobby
by bugzilla_noreply＠suse.com 03 Dec '20

03 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179404 Bug ID: 1179404 Summary: dbench4 regression on machines dobby 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: jack(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Our grid machine dobby is seeing heavy performance regression on dbench4 runs for all filesystems. Results for XFS: 15-SP2-5.3.18-24.34-187 LEAP-15.2-PT-5.10.0-rc2-pt-master-20201117 Amean 1 45.23 ( 0.00%) 39.53 ( 12.61%) Amean 2 53.92 ( 0.00%) 121.29 (-124.96%) Amean 4 70.61 ( 0.00%) 612.66 (-767.72%) Amean 8 83.34 ( 0.00%) 621.63 (-645.89%) Amean 16 105.08 ( 0.00%) 399.54 (-280.23%) Amean 32 137.76 ( 0.00%) 331.95 (-140.96%) Amean 64 254.23 ( 0.00%) 393.61 ( -54.83%) Amean 512 10252.94 ( 0.00%) 10961.67 ( -6.91%) Results for ext4: Amean 1 40.71 ( 0.00%) 52.90 ( -29.95%) Amean 2 103.78 ( 0.00%) 123.01 ( -18.52%) Amean 4 99.57 ( 0.00%) 505.56 (-407.74%) Amean 8 106.81 ( 0.00%) 341.80 (-220.01%) Amean 16 126.87 ( 0.00%) 359.92 (-183.68%) Amean 32 212.60 ( 0.00%) 624.00 (-193.51%) Amean 64 358.64 ( 0.00%) 1411.40 (-293.54%) Amean 512 4158.79 ( 0.00%) 11070.77 (-166.20%) -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kernel-bugs] [Bug 1175589] New: latest kernel update gives backtrace on boot on Huawei TaiShan 2280
by bugzilla_noreply＠suse.com 02 Dec '20

02 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1175589 Bug ID: 1175589 Summary: latest kernel update gives backtrace on boot on Huawei TaiShan 2280 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- System Information Manufacturer: Huawei Product Name: TaiShan 2280 Version: V100R001C00 Base Board Information Manufacturer: Huawei Product Name: BC11SPCD Version: VER.A last working kernel: obs-arm-6:~ # uname -a Linux obs-arm-6 5.3.18-lp152.33-default #1 SMP Wed Jul 22 06:32:33 UTC 2020 (e5a8383) aarch64 aarch64 aarch64 GNU/Linux crashing kernel: 5.3.18-lp152.36-default [ 198.659862] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010 [ 198.678721] Mem abort info: [ 198.681504] ESR = 0x96000004 [ 198.681506] Exception class = DABT (current EL), IL = 32 bits [ 198.681507] SET = 0, FnV = 0 [ 198.681508] EA = 0, S1PTW = 0 [ 198.681508] Data abort info: [ 198.681511] ISV = 0, ISS = 0x00000004 [ 198.684652] audit: type=1400 audit(1598003387.680:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/nagios/plugins/check_ntp_time" pid=6829 comm="apparmor_parser" [ 198.690461] CM = 0, WnR = 0 [ 198.690463] user pgtable: 4k pages, 48-bit VAs, pgdp=0000002fb4588000 [ 198.690464] [0000000000000010] pgd=0000000000000000 [ 198.690468] Internal error: Oops: 96000004 [#1] SMP [ 198.690470] Modules linked in: joydev sbsa_gwdt hns_roce_hw_v1(+) ib_uverbs ipmi_si(+) ib_core ipmi_devintf ipmi_msghandler efivarfs ext4 mbcache jbd2 fuse squashfs lz4_decompress loop brd af_packet ses enclosure sd_mod hid_generic usbhid marvell aes_ce_blk hibmc_drm crypto_simd drm_vram_helper ttm cryptd drm_kms_helper aes_ce_cipher syscopyarea crct10dif_ce ehci_platform ghash_ce sysfillrect ehci_hcd hisi_sas_v2_hw aes_arm64 sysimgblt hisi_sas_main fb_sys_fops sha2_ce libsas sha256_arm64 drm scsi_transport_sas sha1_ce usbcore libata hns_dsaf hns_enet_drv hns_mdio hnae sg nbd dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod [ 198.796596] CPU: 20 PID: 6588 Comm: systemd-udevd Not tainted 5.3.18-lp152.36-default #1 openSUSE Leap 15.2 (unreleased) [ 198.796597] Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.27 06/13/2017 [ 198.796600] pstate: 60000005 (nZCv daif -PAN -UAO) [ 198.819443] pc : hns_roce_create_cq+0x2c/0x810 [hns_roce_hw_v1] [ 198.821744] audit: type=1400 audit(1598003387.820:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/nagios/plugins/check_procs" pid=6848 comm="apparmor_parser" [ 198.825353] lr : hns_roce_v1_rsv_lp_qp+0xa8/0x4f8 [hns_roce_hw_v1] [ 198.848701] sp : ffff0000239035c0 [ 198.852001] x29: ffff0000239035c0 x28: ffff802fbad92000 [ 198.857299] x27: 0000000000000010 x26: ffff802f98eee200 [ 198.862597] x25: ffff80203cbd2010 x24: ffff802fb3b71900 [ 198.867895] x23: ffff80203cbd2010 x22: ffff80203cbd2010 [ 198.872967] audit: type=1400 audit(1598003387.870:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/nagios/plugins/check_swap" pid=6858 comm="apparmor_parser" [ 198.873193] x21: ffff000011679000 x20: 0000000000000000 [ 198.895591] x19: ffff000023903708 x18: ffffffffffffffff [ 198.900888] x17: 0000000000000000 x16: ffff802fb4b93d00 [ 198.906186] x15: 00000000000019b8 x14: 000000000000058a [ 198.911483] x13: 0000000000000003 x12: ffffffffffffffff [ 198.916781] x11: 0000000000000040 x10: ffffff7fff7fff7f [ 198.922078] x9 : a6c8de5e8022adff x8 : 0000000000000000 [ 198.927376] x7 : ffffffffffffffff x6 : ffff802fb2b59eb8 [ 198.932673] x5 : ffff802fb2b59eb8 x4 : 0000000000000400 [ 198.937971] x3 : 0000000000000000 x2 : 0000000000000000 [ 198.943268] x1 : ffff000023903708 x0 : ffff0000092ec808 [ 198.948566] Call trace: [ 198.951005] hns_roce_create_cq+0x2c/0x810 [hns_roce_hw_v1] [ 198.956566] hns_roce_v1_rsv_lp_qp+0xa8/0x4f8 [hns_roce_hw_v1] [ 198.962388] hns_roce_v1_init+0x584/0x8b8 [hns_roce_hw_v1] [ 198.967863] hns_roce_init+0x2b4/0xb08 [hns_roce_hw_v1] [ 198.973077] hns_roce_probe+0x328/0x478 [hns_roce_hw_v1] [ 198.978382] platform_drv_probe+0x58/0xa8 [ 198.982378] really_probe+0xdc/0x448 [ 198.985940] driver_probe_device+0x12c/0x148 [ 198.990196] device_driver_attach+0x74/0x98 [ 198.994366] __driver_attach+0x6c/0x168 [ 198.998188] bus_for_each_dev+0x84/0xd8 [ 199.002010] driver_attach+0x30/0x40 [ 199.005572] bus_add_driver+0x170/0x258 [ 199.009394] driver_register+0x64/0x118 [ 199.013217] __platform_driver_register+0x54/0x60 [ 199.017911] hns_roce_driver_init+0x24/0x1000 [hns_roce_hw_v1] [ 199.023731] do_one_initcall+0x54/0x240 [ 199.027554] do_init_module+0x60/0x1f0 [ 199.031289] load_module+0x1614/0x1718 [ 199.035024] __se_sys_finit_module+0xf8/0x110 [ 199.039367] __arm64_sys_finit_module+0x24/0x30 [ 199.043885] el0_svc_common.constprop.0+0xa0/0x1f8 [ 199.048662] el0_svc_handler+0x34/0x90 [ 199.052397] el0_svc+0x10/0x14 [ 199.055442] Code: aa0203f4 aa1e03e0 d503201f b0041c15 (f940037c) [ 199.061522] ---[ end trace 6041bb51aa4731d0 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 3

[kernel-bugs] [Bug 1179251] New: kmod(foo.ko) provides missing for builtin modules
by bugzilla_noreply＠suse.com 01 Dec '20

01 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179251 Bug ID: 1179251 Summary: kmod(foo.ko) provides missing for builtin modules 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: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I was about to submit an update of kernel-default-base, but when comparing the kmod provides I noticed that the Tumbleweed version was missing quite a lot of them, like sha256_generic or zstd_{,de}compress.ko on aarch64. I guess this is caused by [ 173s] Builtin modules for /home/abuild/rpmbuild/BUILDROOT/kernel-default-base-5.9.11-1.1.g91426ef.55.1.x86_64/boot/vmlinux-5.9.11-1.g91426ef-default.xz not available in /home/abuild/rpmbuild/BUILDROOT/kernel-default-base-5.9.11-1.1.g91426ef.55.1.x86_64/lib/modules/5.9.11-1.g91426ef-default.xz/modules.builtin The .xz seems wrong there, maybe that needs to be handled in https://github.com/openSUSE/rpm-config-SUSE/blob/dc40e5779d59d088658ee3dfe1… as well? -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1179437] New: Error messages on Raspberry Pi 4 with no SD card
by bugzilla_noreply＠suse.com 30 Nov '20

30 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179437 Bug ID: 1179437 Summary: Error messages on Raspberry Pi 4 with no SD card Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dillon.ang.h(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am currently running Tumbleweed aarch64 20201119 on a Raspberry Pi 4 off a USB flash drive with no SD card installed. Tumbleweed was installed using the ISO written to a USB 3.0 flash drive. The system is running the latest stable EEPROM firmware (updated using Raspberry Pi OS 64-bit). The system was booted directly off the Tumbleweed installation ISO on the USB 3.0 flash drive with no SD card installed. It was then installed on another USB 3.0 flash drive installed in the lower USB 3.0 port with the following software selection: XFCE Desktop. After the system was installed, it booted straight off the USB 3.0 flash drive (no need to use gdisk as with the Raspberry Pi 3). When using the system, I constantly get the following messages from dmesg when no SD card is installed (3 different commands, 0x00000502, 0x0000371a, and 0x0000341a) [ 207.194572] mmc1: Timeout waiting for hardware cmd interrupt. [ 207.194592] mmc1: sdhci: ============ SDHCI REGISTER DUMP =========== [ 207.194603] mmc1: sdhci: Sys addr: 0x00000000 | Version: 0x00001002 [ 207.194611] mmc1: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000 [ 207.194619] mmc1: sdhci: Argument: 0x00000000 | Trn mode: 0x00000000 [ 207.194627] mmc1: sdhci: Present: 0x1fff0001 | Host ctl: 0x00000001 [ 207.194634] mmc1: sdhci: Power: 0x0000000f | Blk gap: 0x00000080 [ 207.194642] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x0000f447 [ 207.194649] mmc1: sdhci: Timeout: 0x00000000 | Int stat: 0x00000000 [ 207.194656] mmc1: sdhci: Int enab: 0x00ff1003 | Sig enab: 0x00ff1003 [ 207.194663] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000 [ 207.194670] mmc1: sdhci: Caps: 0x45ee6432 | Caps_1: 0x0000a525 [ 207.194677] mmc1: sdhci: Cmd: 0x00000502 | Max curr: 0x00080008 [ 207.194683] mmc1: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000 [ 207.194690] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000 [ 207.194696] mmc1: sdhci: Host ctl2: 0x00000000 [ 207.194703] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000 [ 207.194708] mmc1: sdhci: ============================================ [ 235.364927] mmc1: Timeout waiting for hardware cmd interrupt. [ 235.364947] mmc1: sdhci: ============ SDHCI REGISTER DUMP =========== [ 235.364958] mmc1: sdhci: Sys addr: 0x00000000 | Version: 0x00001002 [ 235.364966] mmc1: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000 [ 235.364974] mmc1: sdhci: Argument: 0x00000000 | Trn mode: 0x00000000 [ 235.364982] mmc1: sdhci: Present: 0x1fff0001 | Host ctl: 0x00000001 [ 235.364989] mmc1: sdhci: Power: 0x0000000f | Blk gap: 0x00000080 [ 235.364997] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x0000f447 [ 235.365004] mmc1: sdhci: Timeout: 0x00000000 | Int stat: 0x00000000 [ 235.365011] mmc1: sdhci: Int enab: 0x00ff1003 | Sig enab: 0x00ff1003 [ 235.365018] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000 [ 235.365025] mmc1: sdhci: Caps: 0x45ee6432 | Caps_1: 0x0000a525 [ 235.365032] mmc1: sdhci: Cmd: 0x0000371a | Max curr: 0x00080008 [ 235.365039] mmc1: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000 [ 235.365045] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000 [ 235.365051] mmc1: sdhci: Host ctl2: 0x00000000 [ 235.365058] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000 [ 235.365064] mmc1: sdhci: ============================================ [ 383.839362] mmc1: Timeout waiting for hardware cmd interrupt. [ 383.839388] mmc1: sdhci: ============ SDHCI REGISTER DUMP =========== [ 383.839402] mmc1: sdhci: Sys addr: 0x00000000 | Version: 0x00001002 [ 383.839412] mmc1: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000 [ 383.839421] mmc1: sdhci: Argument: 0x80000c08 | Trn mode: 0x00000000 [ 383.839430] mmc1: sdhci: Present: 0x1fff0001 | Host ctl: 0x00000001 [ 383.839438] mmc1: sdhci: Power: 0x0000000f | Blk gap: 0x00000080 [ 383.839446] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x0000f447 [ 383.839453] mmc1: sdhci: Timeout: 0x00000000 | Int stat: 0x00000000 [ 383.839461] mmc1: sdhci: Int enab: 0x00ff1003 | Sig enab: 0x00ff1003 [ 383.839469] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000 [ 383.839478] mmc1: sdhci: Caps: 0x45ee6432 | Caps_1: 0x0000a525 [ 383.839485] mmc1: sdhci: Cmd: 0x0000341a | Max curr: 0x00080008 [ 383.839492] mmc1: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000 [ 383.839499] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000 [ 383.839505] mmc1: sdhci: Host ctl2: 0x00000000 [ 383.839512] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000 [ 383.839519] mmc1: sdhci: ============================================ Even with these messages, the system works as would be expected. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1179092] [i915] Screen occasionally goes blank, sometimes staying that way until I press a key
by bugzilla_noreply＠suse.com 30 Nov '20

30 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179092 http://bugzilla.opensuse.org/show_bug.cgi?id=1179092#c11 --- Comment #11 from Bengt G�rd�n <bengan(a)bag.org> --- (In reply to Bengt G�rd�n from comment #10) Sorry. This was meant to go in the bug that I filed (#1178474). Will update to. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1179387] Fubar X with Radeon AGP on Pentium III Coppermine
by bugzilla_noreply＠suse.com 30 Nov '20

30 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1179387 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(xmontell(a)gmail.co | |m) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1179387] Fubar X with Radeon AGP on Pentium III Coppermine
by bugzilla_noreply＠suse.com 30 Nov '20

30 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1179387 https://bugzilla.suse.com/show_bug.cgi?id=1179387#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson(a)suse.com, | |sndirsch(a)suse.com, | |tiwai(a)suse.com, | |tzimmermann(a)suse.com --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- What if you avoid radeon X11 driver? Does it render better? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1163120] No mitigations for CPU vulnerabilities
by bugzilla_noreply＠suse.com 30 Nov '20

30 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1163120 https://bugzilla.suse.com/show_bug.cgi?id=1163120#c18 --- Comment #18 from Miroslav Bene�� <mbenes(a)suse.com> --- You are welcome to report upstream, but I am confident you will fail there, because of the reasons provided here. The microcode mitigation is a standard way to deal with these issues and it is in most cases the only reliable way. Introducing a sub-optimal solution next to the standard one is not how the upstream development works. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1142370] Untested laptop multimedia keys, please report success or failure to eric.piel@tremplin-utc.net
by bugzilla_noreply＠suse.com 30 Nov '20

30 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1142370 https://bugzilla.suse.com/show_bug.cgi?id=1142370#c21 --- Comment #21 from Miroslav Bene�� <mbenes(a)suse.com> --- Well, the upstream bugzilla might work, but usually it does not. As is the case here. Mailing the upstream maintainer (with CCing linux-kernel(a)vger.kernel.org) is a perfect way to report issues, so do not worry. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1178639] [nouveau] The plasma login screen freezes on kernel 5.9.1 and later
by bugzilla_noreply＠suse.com 30 Nov '20

30 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178639 https://bugzilla.suse.com/show_bug.cgi?id=1178639#c23 --- Comment #23 from Takashi Iwai <tiwai(a)suse.com> --- It's a good finding. Then could you try to plug the external monitor after booting without it? Does it show the same lock up? If yes, you might have a better chance to catch the problem. e.g. you can set the drm debug option (e.g. echo 0x0e > /sys/module/drm/parameters/debug) before plugging the monitor, then check the kernel messages. In anyway, please update the upstream report. -- You are receiving this mail because: You are the assignee for the bug.

1 0