October 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1175300] New: AMDGPU Driver Brightness Issue
by bugzilla_noreply＠suse.com 06 Dec '20

06 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175300 Bug ID: 1175300 Summary: AMDGPU Driver Brightness Issue 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: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- hi, just checked the amdgpu brightness level and it seems to be on 20% -- You are receiving this mail because: You are the assignee for the bug.

1 1

[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 1178318] New: RX 5600M shader clocks stuck at 300MHz with kernel 5.9.1
by bugzilla_noreply＠suse.com 27 Nov '20

27 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1178318 Bug ID: 1178318 Summary: RX 5600M shader clocks stuck at 300MHz with kernel 5.9.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: aaron.zakhrov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 843188 --> http://bugzilla.opensuse.org/attachment.cgi?id=843188&action=edit Unigine Heaven with GALLIUM HUD=shader-clock and DRI_PRIME=1 set With Kernel 5.9.1-default on my Dell G5 15 SE running OpenSUSE tumbleweed, my discrete Radeon RX 5600M has its shader clock stuck at 300MHz. The relevant upstream bug reports are: https://gitlab.freedesktop.org/drm/amd/-/issues/1272 and https://gitlab.freedesktop.org/drm/amd/-/issues/1252 This happens regardless of GPU load. Glxgears, vkcube and Unigine heaven all show the same behavior both plugged in and on battery. The clock is not being misreported either. I get very slow graphics performance on the discrete GPU when using kernel 5.9.1 -- You are receiving this mail because: You are the assignee for the bug.

1 23

[kernel-bugs] [Bug 1175893] New: question: load insanely high
by bugzilla_noreply＠suse.com 26 Nov '20

26 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1175893 Bug ID: 1175893 Summary: question: load insanely high Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal 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: --- obs-arm-1:~ # uname -a Linux obs-arm-1 5.8.2-1-default #1 SMP Wed Aug 19 09:43:15 UTC 2020 (71b519a) aarch64 aarch64 aarch64 GNU/Linux obs-arm-1:~ # cat /proc/loadavg 848.03 848.11 847.01 8/660 35750 obs-arm-1:~ # ps awux | wc -l 526 obs-arm-1:~ # pstree -apl | wc -l 252 so I have 526 processes and a load of about 850 ... what am I missing here ? top - 13:00:18 up 1 day, 17:02, 1 user, load average: 845.34, 847.11, 846.76 Tasks: 524 total, 1 running, 523 sleeping, 0 stopped, 0 zombie %Cpu(s): 12.8 us, 0.3 sy, 0.0 ni, 86.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 257195.5+total, 13658.55+free, 30579.12+used, 212957.8+buff/cache MiB Swap: 1000.066 total, 956.066 free, 44.000 used. 223341.5+avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 18257 qemu 20 0 9553800 4.102g 22944 S 113.2 1.633 1317:44 qemu-system-aar 21778 qemu 20 0 9689056 4.106g 22956 S 107.2 1.635 1328:27 qemu-system-aar 9249 qemu 20 0 9566116 4.106g 23208 S 102.0 1.635 1318:27 qemu-system-aar 23827 qemu 20 0 9424236 4.059g 23048 S 102.0 1.616 23:30.35 qemu-system-aar 18143 qemu 20 0 9560948 4.104g 22880 S 100.7 1.634 1316:43 qemu-system-aar 22072 qemu 20 0 9465680 4.098g 23052 S 100.7 1.631 1329:10 qemu-system-aar 36915 root 20 0 9428 3852 2900 R 1.316 0.001 0:00.16 top 41766 qemu 20 0 9475952 4.099g 22728 S 0.658 1.632 41:10.28 qemu-system-aar 6601 root 20 0 31536 23576 7452 S 0.329 0.009 0:20.33 bs_worker 1 root 20 0 172424 13108 9568 S 0.000 0.005 3:31.34 systemd 2 root 20 0 0 0 0 S 0.000 0.000 0:00.99 kthreadd 3 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 rcu_gp 4 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 rcu_par_gp [... skipping the rest of zeroes ...] 8 VMs with about 24 qemu threads each, so I would not be surprised about a load of ~200 but why are we seeing > 800 now ? -- You are receiving this mail because: You are the assignee for the bug.

1 24

[kernel-bugs] [Bug 1177018] New: Rare kernel soft lockup causes PC to freeze
by bugzilla_noreply＠suse.com 19 Nov '20

19 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1177018 Bug ID: 1177018 Summary: Rare kernel soft lockup causes PC to freeze Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: pujos.michael(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 841985 --> http://bugzilla.opensuse.org/attachment.cgi?id=841985&action=edit output of journalctl Using Kernel 5.4.10 and current TW as of the date of this report. Today I was working normally in Xorg and suddenly my laptop freezed: no keyboard input, mouse cursor moving but clicks inoperant, ssh'ing from another PC impossible. Interestingly, I had audio playing and it still continue to play normally. Fans of the laptop triggered full speed, indicating high CPU usage. I rebooted the laptop with ALT+SysRq+b and looked at the journal which contains a lot of "watchdog: BUG: soft lockup - CPU#1 stuck for 22s!" entries with stack trace that seems to refer to usb. I have attached the full journal log, look at the end for the "BUG: soft lockup" entries. At that point, the laptop had an uptime of about 3 days with a few suspend in-between. As far as USB is concerned, I have a Thunderbolt 3 dock connected and audio was playing through it (via USB audio) when it happened. Also had an Android device connected to the laptop directly. There's the Logitech unifying receiver connected to the laptop and a keyboard connected to the dock. I can include the output of hwinfo if necessary This freeze is rare in the grand scheme of things but it also happened once 2 weeks ago with a previous 5.4.x kernel. First I blamed it to the NVIDIA driver and did not investigate more, but now I'm not so sure given that the stack trace refer to USB. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[kernel-bugs] [Bug 1176923] New: CONFIG_SECURITY_SELINUX_DISABLE deprecated
by bugzilla_noreply＠suse.com 04 Nov '20

04 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1176923 Bug ID: 1176923 Summary: CONFIG_SECURITY_SELINUX_DISABLE deprecated 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: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://www.phoronix.com/scan.php?page=news_item&px=Fedora-34-Drop-SELinux-… https://fedoraproject.org/wiki/Changes/Remove_Support_For_SELinux_Runtime_D… https://lwn.net/Articles/831748/ As CONFIG_SECURITY_SELINUX_DISABLE got deprecated with version 5.6, we should disable it, so that, if we restart our SELinux effords now because of CarWos and MicroOS, we do it "right" from the beginning. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[kernel-bugs] [Bug 1178305] New: WARNING in kmod.c request_module during drm load
by bugzilla_noreply＠suse.com 03 Nov '20

03 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178305 Bug ID: 1178305 Summary: WARNING in kmod.c request_module during drm load 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: --- [ 4.148929] nvme0n1: p1 p2 [ 4.223440] i915 0000:00:02.0: [drm] VT-d active for gfx access [ 4.223442] checking generic (4000000000 1d5000) vs hw (603e000000 1000000) [ 4.223443] checking generic (4000000000 1d5000) vs hw (4000000000 10000000) [ 4.223443] fb0: switching to inteldrmfb from EFI VGA [ 4.223507] Console: switching to colour dummy device 80x25 [ 4.223527] i915 0000:00:02.0: vgaarb: deactivate vga console [ 4.224592] i915 0000:00:02.0: [drm] Couldn't get system memory bandwidth [ 4.225238] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 4.225724] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_06.bin (v2.6) [ 4.242635] i915 0000:00:02.0: [drm] PHY D is disabled/in DSI mode with an ungated DDI clock, gate it [ 4.361120] [drm] Initialized i915 1.6.0 20200715 for 0000:00:02.0 on minor 0 [ 4.363066] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 4.363687] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3 [ 4.408002] ------------[ cut here ]------------ [ 4.408007] WARNING: CPU: 7 PID: 58 at kernel/kmod.c:136 __request_module+0x18e/0x2da [ 4.408007] Modules linked in: i915 nvme xhci_pci xhci_pci_renesas xhci_hcd rtsx_pci_sdmmc mmc_core i2c_algo_bit nvme_core drm_kms_helper usbcore syscopyarea sysfillrect sysimgblt fb_sys_fops cec crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel rc_core glue_helper crypto_simd drm cryptd serio_raw intel_ish_ipc(+) rtsx_pci intel_ishtp vmd wmi battery i2c_hid video pinctrl_tigerlake pinctrl_intel btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs [ 4.408021] CPU: 7 PID: 58 Comm: kworker/u16:1 Not tainted 5.9.1-1-default #1 openSUSE Tumbleweed [ 4.408022] Hardware name: Dell Inc. XPS 13 9310/0F7M4C, BIOS 1.0.3 10/05/2020 [ 4.408023] Workqueue: events_unbound async_run_entry_fn [ 4.408025] RIP: 0010:__request_module+0x18e/0x2da [ 4.408026] Code: 89 f1 44 89 ea 48 8d 74 24 40 e8 dd 3e d3 00 49 8b 04 24 48 85 c0 75 de e9 54 ff ff ff e8 ea e5 ff ff 84 c0 0f 84 c7 fe ff ff <0f> 0b e9 c0 fe ff ff 48 c7 c6 90 57 81 9a 48 c7 c7 e0 2e 06 9b e8 [ 4.408026] RSP: 0018:ffffb0a4002e7a48 EFLAGS: 00010202 [ 4.408027] RAX: ffff9c0586d04301 RBX: 0000000000000001 RCX: 0000000000000000 [ 4.408027] RDX: ffffffffc0890b4b RSI: ffffffffc0609f2c RDI: ffff9c0586d14b00 [ 4.408028] RBP: ffffb0a4002e7b18 R08: ffff9c0586f46d23 R09: 0000000000000000 [ 4.408028] R10: 0000000000000000 R11: ffff9c0586f46d23 R12: ffffffffc0609f2c [ 4.408029] R13: 0000000000000000 R14: ffff9c0c5e63f800 R15: ffff9c0c3fd4d658 [ 4.408029] FS: 0000000000000000(0000) GS:ffff9c0cef7c0000(0000) knlGS:0000000000000000 [ 4.408030] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 4.408030] CR2: 000055a796efe520 CR3: 0000000106fe4002 CR4: 0000000000770ee0 [ 4.408031] PKRU: 55555554 [ 4.408031] Call Trace: [ 4.408035] ? vsnprintf+0x368/0x4f0 [ 4.408039] ? kvasprintf+0x7b/0xc0 [ 4.408042] rc_map_get+0x30/0x60 [rc_core] [ 4.408045] rc_prepare_rx_device+0x35/0x280 [rc_core] [ 4.408047] rc_register_device+0xf1/0x1e0 [rc_core] [ 4.408049] cec_register_adapter.part.0+0x3b/0x170 [cec] [ 4.408058] drm_dp_cec_set_edid+0x131/0x1a7 [drm_kms_helper] [ 4.408106] intel_dp_set_edid+0x8d/0xc0 [i915] [ 4.408139] intel_dp_detect+0x204/0x480 [i915] [ 4.408144] drm_helper_probe_detect+0x49/0xa0 [drm_kms_helper] [ 4.408148] drm_helper_probe_single_connector_modes+0x435/0x5b0 [drm_kms_helper] [ 4.408162] drm_client_modeset_probe+0x1df/0x500 [drm] [ 4.408167] __drm_fb_helper_initial_config_and_unlock+0x30/0xc0 [drm_kms_helper] [ 4.408199] intel_fbdev_initial_config+0x14/0x30 [i915] [ 4.408201] async_run_entry_fn+0x37/0x140 [ 4.408203] process_one_work+0x1e3/0x3b0 [ 4.408204] worker_thread+0x46/0x340 [ 4.408205] ? process_one_work+0x3b0/0x3b0 [ 4.408207] kthread+0x11b/0x140 [ 4.408208] ? __kthread_bind_mask+0x60/0x60 [ 4.408210] ret_from_fork+0x1f/0x30 [ 4.408211] ---[ end trace 62d24077968bd90f ]--- [ 4.434360] rc_core: IR keymap rc-cec not found [ 4.434367] Registered IR keymap rc-empty [ 4.434416] rc rc0: DP-1 as /devices/pci0000:00/0000:00:02.0/rc/rc0 [ 4.434478] input: DP-1 as /devices/pci0000:00/0000:00:02.0/rc/rc0/input4 [ 4.440357] fbcon: i915drmfb (fb0) is primary device I think this is why my XPS (with the 5.9.1 kernel) does not properly enumerate the external displays. kernel-default-5.9.1-1.2.x86_64 from openSUSE TW -- You are receiving this mail because: You are the assignee for the bug.

1 6

[kernel-bugs] [Bug 1178306] New: error: request firmware intel/sof/sof-tgl.ri failed err: -2
by bugzilla_noreply＠suse.com 03 Nov '20

03 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178306 Bug ID: 1178306 Summary: error: request firmware intel/sof/sof-tgl.ri failed err: -2 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: --- On the Dell XPS 13, looks like the kernel is trying to load a non-existent audio driver firmware: [ 15.907191] idma64 idma64.1: Found Intel integrated DMA 64-bit [ 15.912927] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 15.912930] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 15.988359] i2c_hid i2c-DLL0945:00: supply vdd not found, using dummy regulator [ 15.988376] i2c_hid i2c-DLL0945:00: supply vddl not found, using dummy regulator [ 16.011076] input: Dell WMI hotkeys as /devices/platform/PNP0C14:02/wmi_bus/wmi_bus-PNP0C14:02/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input17 [ 16.020321] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 16.020325] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 16.020338] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002) [ 16.020661] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 16.020775] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 16.027386] sof-audio-pci 0000:00:1f.3: use msi interrupt mode [ 16.035823] i2c i2c-15: 8/8 memory slots populated (from DMI) [ 16.035824] i2c i2c-15: Systems with more than 4 memory slots not supported yet, not instantiating SPD [ 16.074627] input: PC Speaker as /devices/platform/pcspkr/input/input18 [ 16.074874] pstore: Efi pstore disabled, enforce via pstore.backend=efi [ 16.074874] pstore: On a broken BIOS, this can severely harm your system [ 16.074874] pstore: Only enable efi based pstore when you know what you are doing [ 16.087833] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5 [ 16.087834] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 16.087837] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 [ 16.088661] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-tgl.ri failed with error -2 [ 16.088663] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-tgl.ri failed err: -2 [ 16.088666] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 [ 16.088978] 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 7

[kernel-bugs] [Bug 1175536] New: Bluetooth connection is no longer working
by bugzilla_noreply＠suse.com 01 Nov '20

01 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175536 Bug ID: 1175536 Summary: Bluetooth connection is no longer working 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: duelistgamer(a)yahoo.co.in QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After updating to the first Tumbleweed snapshot containing kernel 5.8, my bluetooth connection is no longer functioning correctly. 1. On connecting to a bluetooth audio device after booting, the connection is fine. 2. On disconnecting and reconnecting to the same device, the connection doesn't seem to work and the audio device does not indicate that it has received a connection. 3. On wiping all saved bluetooth devices and adding new ones, the search function appears to behave strangely and add ALL bluetooth devices that it is able to detect, not just the one device I want to connect to. 4. It fails to pair any new bluetooth device that I want to connect after this. My tumbleweed machine is a Thinkpad T460p, configured with an i7 6820HQ CPU. lspci result: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:01.2 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x4) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:17.0 SATA controller: Intel Corporation HM170/QM170 Chipset SATA Controller [AHCI Mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1) 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) 00:1f.0 ISA bridge: Intel Corporation QM170 Chipset LPC/eSPI Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31) 02:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940MX] (rev a2) 03:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) -- You are receiving this mail because: You are the assignee for the bug.

1 8

[kernel-bugs] [Bug 1178304] No access to NFS4/KRB5 mounts after update to Kernel 5.3.18-lp152.47.2
by bugzilla_noreply＠suse.com 31 Oct '20

31 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1178304 https://bugzilla.suse.com/show_bug.cgi?id=1178304#c5 --- Comment #5 from Ralf Kölmel <ralf.koelmel(a)kit.edu> --- the problem with a running desktop over NFS is not occuring with sec=krb5. It seems that only NFS with sec=krb5p is affected. -- You are receiving this mail because: You are the assignee for the bug.

1 0