February 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1195885] New: kernel 5.16.8 with nvidia glG05-470.103.01 won't work
by bugzilla_noreply＠suse.com 14 Feb '22

14 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195885 Bug ID: 1195885 Summary: kernel 5.16.8 with nvidia glG05-470.103.01 won't work 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: werwolf131313(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- kernel 5.16.8 with nvidia glG05-470.103.01 won't work after grub only black screen. the kernel does not start. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195464] intel: screenlocker does not wake up after sleep
by bugzilla_noreply＠suse.com 13 Feb '22

13 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195464 http://bugzilla.opensuse.org/show_bug.cgi?id=1195464#c10 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |X.Org Assignee|kernel-bugs(a)opensuse.org |gfx-bugs(a)suse.de QA Contact|qa-bugs(a)suse.de |gfx-bugs(a)suse.de --- Comment #10 from Stefan Dirsch <sndirsch(a)suse.com> --- Ok. So apparently a X problem. Reassigning back. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195464] intel: screenlocker does not wake up after sleep
by bugzilla_noreply＠suse.com 13 Feb '22

13 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195464 http://bugzilla.opensuse.org/show_bug.cgi?id=1195464#c9 Michel Munnix <michel.munnix(a)skynet.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(michel.munnix@sky | |net.be) | --- Comment #9 from Michel Munnix <michel.munnix(a)skynet.be> --- Created attachment 856117 --> http://bugzilla.opensuse.org/attachment.cgi?id=856117&action=edit Xorg.0.log xf86-video-intel package is not installed. last line in log appears when moving the cursor to restore screen brightness: [ 745.406] [dix] EventToCore: Not implemented yet. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1194416] New: radeon drm crash
by bugzilla_noreply＠suse.com 13 Feb '22

13 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194416 Bug ID: 1194416 Summary: radeon drm crash 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: jtamate(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using KDE plasma with two sessions (in Ctrl+F7 and Ctrl+F8). Linux version 5.15.12-1-default (geeko@buildhost) (gcc (SUSE Linux) 11.2.1 20211124 [revision 7510c23c1ec53aa4a62705f0384079661342ff7b], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.37.20211112-3) #1 SMP Wed Dec 29 14:50:16 UTC 2021 (375fcb8) Jan 7 19:06:29 torresj kernel: ------------[ cut here ]------------ Jan 7 19:06:29 torresj kernel: WARNING: CPU: 2 PID: 28917 at drivers/gpu/drm/ttm/ttm_bo.c:409 ttm_bo_release+0x2e3/0x310 [ttm] Jan 7 19:06:29 torresj kernel: Modules linked in: xt_nat veth xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype overlay snd_seq_dummy snd_hrtimer ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter ipt_REJECT nf_reject_ipv4 xt_conntrack nft_chain_nat nf_nat nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp nft_counter ip6_tables rfkill nft_compat ip_set nf_tables libcrc32c nfnetlink vboxnetadp(O) vboxnetflt(O) vboxdrv(O) snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss dmi_sysfs it87 hwmon_vid usblp edac_mce_amd kvm_amd ccp kvm snd_hda_codec_realtek snd_hda_codec_generic irqbypass ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi pcspkr snd_hda_codec snd_hda_core snd_hwdep snd_pcm wmi_bmof k10temp r8169 snd_timer realtek snd mdio_devres i2c_piix4 libphy soundcore tiny_power_button button acpi_cpufreq binfmt_misc fuse configfs ip_tables x_tables ext4 mbcache jbd2 sg br_netfilter bridge stp llc Jan 7 19:06:29 torresj kernel: dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr hid_generic aoe usbhid uas usb_storage ohci_pci serio_raw sp5100_tco xhci_pci xhci_pci_renesas ehci_pci xhci_hcd oh ci_hcd ehci_hcd usbcore wmi radeon i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core drm Jan 7 19:06:29 torresj kernel: CPU: 2 PID: 28917 Comm: Xorg.bin Tainted: G O 5.15.12-1-default #1 openSUSE Tumbleweed dacaf19d133e8023737b25567dc90a32d973f26e Jan 7 19:06:29 torresj kernel: Hardware name: Gigabyte Technology Co., Ltd. GA-890FXA-UD5/GA-890FXA-UD5, BIOS F6 11/24/2010 Jan 7 19:06:29 torresj kernel: RIP: 0010:ttm_bo_release+0x2e3/0x310 [ttm] Jan 7 19:06:29 torresj kernel: Code: e8 92 ae d5 db e9 ac fd ff ff 48 8b 7d 98 b9 4c 1d 00 00 31 d2 be 01 00 00 00 e8 88 cf d5 db 48 8b 45 e8 eb 9d 4c 89 e0 eb 98 <0f> 0b e9 3c fd ff ff e8 a1 ac d5 db e9 f0 fe ff ff be 03 00 00 00 Jan 7 19:06:29 torresj kernel: RSP: 0018:ffffacf481a5fdb0 EFLAGS: 00010202 Jan 7 19:06:29 torresj kernel: RAX: 0000000000000001 RBX: ffffacf481a5fdf0 RCX: 0000000000000000 Jan 7 19:06:29 torresj kernel: RDX: 0000000000000001 RSI: ffff8d4e96b603c0 RDI: ffff8d518b2c51d8 Jan 7 19:06:29 torresj kernel: RBP: ffff8d518b2c51d8 R08: ffff8d518b2c51d8 R09: 0000000000000064 Jan 7 19:06:29 torresj kernel: R10: 0000000000000010 R11: ffff8d4f95753b50 R12: ffff8d4e88ce46f0 Jan 7 19:06:29 torresj kernel: R13: ffff8d518b2c5078 R14: ffff8d5138c8ccc0 R15: 0000000000000000 Jan 7 19:06:29 torresj kernel: FS: 00007fcc13d6cd80(0000) GS:ffff8d519fc80000(0000) knlGS:0000000000000000 Jan 7 19:06:29 torresj kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 7 19:06:29 torresj kernel: CR2: 000055c5d5046bb0 CR3: 000000021b0d6000 CR4: 00000000000006e0 Jan 7 19:06:29 torresj kernel: Call Trace: Jan 7 19:06:29 torresj kernel: <TASK> Jan 7 19:06:29 torresj kernel: radeon_bo_unref+0x1a/0x30 [radeon 5f048eaabec9bd1cd52ebd969c19efee79c13c16] Jan 7 19:06:29 torresj kernel: radeon_gem_object_free+0x30/0x50 [radeon 5f048eaabec9bd1cd52ebd969c19efee79c13c16] Jan 7 19:06:29 torresj kernel: drm_gem_dmabuf_release+0x36/0x50 [drm adb026bbd7eb07105bd885f795aa476263c57532] Jan 7 19:06:29 torresj kernel: dma_buf_release+0x3a/0x90 Jan 7 19:06:29 torresj kernel: __dentry_kill+0xfa/0x170 Jan 7 19:06:29 torresj kernel: __fput+0xe3/0x250 Jan 7 19:06:29 torresj kernel: task_work_run+0x65/0xa0 Jan 7 19:06:29 torresj kernel: exit_to_user_mode_prepare+0x224/0x230 Jan 7 19:06:29 torresj kernel: syscall_exit_to_user_mode+0x18/0x40 Jan 7 19:06:29 torresj kernel: do_syscall_64+0x69/0x80 Jan 7 19:06:29 torresj kernel: ? do_user_addr_fault+0x1de/0x680 Jan 7 19:06:29 torresj kernel: ? exit_to_user_mode_prepare+0x15f/0x230 Jan 7 19:06:29 torresj kernel: ? exc_page_fault+0x68/0x130 Jan 7 19:06:29 torresj kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Jan 7 19:06:29 torresj kernel: RIP: 0033:0x7fcc142d488b Jan 7 19:06:29 torresj kernel: Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5d 75 0f 00 f7 d8 64 89 01 48 Jan 7 19:06:29 torresj kernel: RSP: 002b:00007ffc3cbd5328 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Jan 7 19:06:29 torresj kernel: RAX: 0000000000000000 RBX: 00007ffc3cbd5378 RCX: 00007fcc142d488b Jan 7 19:06:29 torresj kernel: RDX: 00007ffc3cbd5378 RSI: 0000000040086409 RDI: 0000000000000013 Jan 7 19:06:29 torresj kernel: RBP: 0000000040086409 R08: 000055c5d480f500 R09: 0000000000000000 Jan 7 19:06:29 torresj kernel: R10: 00000000000050d2 R11: 0000000000000246 R12: 000055c5d2cc0928 Jan 7 19:06:29 torresj kernel: R13: 0000000000000013 R14: 000055c5d51e71e0 R15: 00007fcc0a51d010 Jan 7 19:06:29 torresj kernel: </TASK> Jan 7 19:06:29 torresj kernel: ---[ end trace 8fa1280a5aa218ff ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1195860] "Dummy output" for sound card on Huawei Matebook D16
by bugzilla_noreply＠suse.com 12 Feb '22

12 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195860 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |tiwai(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195464] intel: screenlocker does not wake up after sleep
by bugzilla_noreply＠suse.com 12 Feb '22

12 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195464 https://bugzilla.suse.com/show_bug.cgi?id=1195464#c8 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(michel.munnix@sky | |net.be) --- Comment #8 from Stefan Dirsch <sndirsch(a)suse.com> --- Oh. I don't know. If xf86-video-intel package is installed, please uninstall and try again. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195464] intel: screenlocker does not wake up after sleep
by bugzilla_noreply＠suse.com 12 Feb '22

12 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195464 https://bugzilla.suse.com/show_bug.cgi?id=1195464#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Sounds like some rendering problem on X (as the problem doesn't appear on Wayland)... Just to confirm: all problems (including suspend/resume) appear only with the X session and not on Wayland, or only part of them? And, is it modesetting driver, or xf86-video-intel? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195860] New: "Dummy output" for sound card on Huawei Matebook D16
by bugzilla_noreply＠suse.com 12 Feb '22

12 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195860 Bug ID: 1195860 Summary: "Dummy output" for sound card on Huawei Matebook D16 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: hector.selley(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 856103 --> http://bugzilla.opensuse.org/attachment.cgi?id=856103&action=edit lspci output Problem: Sound card of Huawei Matebook D16 isn't working properly, is detected as "Dummy Output" Hardware: Laptop: Huawei Matebook D16 APU: Amd Ryzen 5 4600H Sound card (as shown by lspci): 03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller Description: Sound card it's detected by the kernel and lspci is showing it. However it doesn't cast any sound at all. Gnome show it as a "Dummy output" and Plasma just shows a ticked red speaker. I was able to get sound out of the laptop trought Bluetooth, HDMI and an USB external sound card so I'm pretty sure is a missing driver issue. Kernel devs are working in this driver for another Huawei laptop with the same card but on Intel CPU platform. According with what I read on their's github thread, it's not the same driver despite is the same sound card (I don't have the proper knowledge to confirm this). https://github.com/thesofproject/linux/issues/3248 I'd be thankful if you can help me out on solving this annoying issue. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1195464] intel: screenlocker does not wake up after sleep
by bugzilla_noreply＠suse.com 12 Feb '22

12 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195464 https://bugzilla.suse.com/show_bug.cgi?id=1195464#c6 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson(a)suse.com, | |tiwai(a)suse.com, | |tzimmermann(a)suse.com Component|X.Org |Kernel Assignee|gfx-bugs(a)suse.de |kernel-bugs(a)opensuse.org Summary|screenlocker does not wake |intel: screenlocker does |up after sleep |not wake up after sleep QA Contact|gfx-bugs(a)suse.de |qa-bugs(a)suse.de --- Comment #6 from Stefan Dirsch <sndirsch(a)suse.com> --- This sounds like a kernel related issue to me on Intel graphics. Reassigning. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1175033] Black screen with cursor upon login to plasma
by bugzilla_noreply＠suse.com 12 Feb '22

12 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1175033 http://bugzilla.opensuse.org/show_bug.cgi?id=1175033#c10 --- Comment #10 from Felix Miata <mrmazda(a)earthlink.net> --- I just tried on comment #8 nvidia host p5bse, and SDDM won't show a cursor in username or password fields, or let me type in them. Startx is blocked for ordinary users. Startx brings up a nice working as expected Plasma session as root. On radeon host fi965, SDDM half works (initializes with touchscreen keyboard instead of normal greeter), and Plasma is working as expected. Whatever the problem was seems probably to have disappeared. -- You are receiving this mail because: You are the assignee for the bug.

1 0