March 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1209620] dup from 6.1.8-1 to 6.2.6-1-default breaks mount cifs user access to NAS
by bugzilla_noreply＠suse.com 24 Mar '23

24 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209620 https://bugzilla.suse.com/show_bug.cgi?id=1209620#c1 Paulo Alcantara <palcantara(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |samba-maintainers(a)SuSE.de --- Comment #1 from Paulo Alcantara <palcantara(a)suse.com> --- Hi Rick, Thanks for the report. Could provide verbose logs and network traces from both working (6.1.8-1) and non-working (6.2.6-1) kernels as follows # umount any existing shares modprobe dns_resolver modprobe cifs dmesg --clear echo 'module cifs +p' > /sys/kernel/debug/dynamic_debug/control echo 'file fs/cifs/* +p' > /sys/kernel/debug/dynamic_debug/control echo 1 > /proc/fs/cifs/cifsFYI echo 1 > /sys/module/dns_resolver/parameters/debug tcpdump -s 0 -w trace.pcap port 445 & pid=$! sleep 3 mount -t cifs //169.254.8.252/NAS ~/Mount/NAS -o ... sleep 3 kill $pid dmesg > trace.log echo '----------' >> trace.log cat /proc/fs/cifs/dfscache >> trace.log and then send trace.log and trace.pcap files for both kernels. Please, also share - full mount options - server type, version and configuration -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208239] Driver for Intel Alder Lake-UP3 GT2 [UHD Graphics] -- HDMI not properly recognized
by bugzilla_noreply＠suse.com 24 Mar '23

24 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208239 http://bugzilla.opensuse.org/show_bug.cgi?id=1208239#c18 Patrik Jakobsson <patrik.jakobsson(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #18 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- Hi Luca, Again, sorry for they late reply. From your logs I can see that the Intel driver is properly loaded. I'm not sure if the benchmarking numbers are sane or not since I don't have a similar system to compare with. intel-gpu-top shows an idle GPU but perhaps that is because you didn't have a GPU load running when capturing the output. Since this bug is about HDMI not being properly recognized I think you should file a separate bug for the performance issues. The reason HDMI was not properly recognized at first was that 15.4 didn't support ADL-P. And the problem with 15.5 was a bad cable. I think we can close this bug. Please reopen if you feel differently. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 24 Mar '23

24 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c7 Christian Goll <cgoll(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(cgoll(a)suse.com) | --- Comment #7 from Christian Goll <cgoll(a)suse.com> --- Suspending and resuming works now fine, with and without attached docking station. Problems just show up, if the docking station is removed, when the laptop is suspended. Wakeup works, but I can't then suspend it. I used the 5.14.21-150500.95.g8e77d94-default -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 24 Mar '23

24 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Any chance to test the latest SLE15-SP5 kernel? If the problem persists with it, we'll have to take a deeper look. In general, it's known that AMD platforms had some unresolvable issues on SLE15-SP4/Leap-15.4, while SP5/15.5 can work better. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209680] ata1.00: exception Emask 0x40 SAct 0x3f0 SErr 0xd0800 action 0x6 frozen
by bugzilla_noreply＠suse.com 24 Mar '23

24 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209680 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 24 Mar '23

24 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c5 --- Comment #5 from Christian Goll <cgoll(a)suse.com> --- Still not perfect, especially if suspended when connected to a do a docking station, disconnect and then wake up. But this may be a fringe case. So in overall, much better. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 24 Mar '23

24 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Any update on this? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209499] System is freezing with current openSUSE Tumbleweed
by bugzilla_noreply＠suse.com 23 Mar '23

23 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209499 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P5 - None Status|IN_PROGRESS |NEW -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209499] System is freezing with current openSUSE Tumbleweed
by bugzilla_noreply＠suse.com 23 Mar '23

23 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209499 http://bugzilla.opensuse.org/show_bug.cgi?id=1209499#c11 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS --- Comment #11 from Stefan Dirsch <sndirsch(a)suse.com> --- Thanks for updating the ticket, Adrian. @Felix Not sure where is the context for your comment#9 here. Did you post to the wrong ticket? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207728] New: qgroup rescan paused every startup or reboot
by bugzilla_noreply＠suse.com 23 Mar '23

23 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207728 Bug ID: 1207728 Summary: qgroup rescan paused every startup or reboot 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: --- after the release of kernel 6.1.8, upon each startup and reboot i get a message: btrfs info : qgroup rescan paused. to get passed this point i have to run sudo btrfs quota rescan / each time to complete the rescan process so it gets to be BTRFS info (device sda2): qgroup scan completed (inconsistency flag cleared) -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 1169099] [Build 20200405][aarch64] crash: cannot determine VA_BITS_ACTUAL: please use /proc/kcore
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1169099 https://bugzilla.suse.com/show_bug.cgi?id=1169099#c42 --- Comment #42 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2023:0874-1: An update that has five recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1169099, 1183965, 1185209, 1187634, 1206328 Sources used: openSUSE Leap 15.4 (src): crash-7.2.9-150200.18.17.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1209499] System is freezing with current openSUSE Tumbleweed
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

1 0

[Bug 1209526] WOL not working with RTL8111/8168/8411 with 6.2.x kernel
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209526 https://bugzilla.suse.com/show_bug.cgi?id=1209526#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jiivee(a)iki.fi, | |tiwai(a)suse.com Flags| |needinfo?(jiivee(a)iki.fi) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Please check whether the problem persists with 6.3-rc kernel, e.g. in OBS Kernel:HEAD repo. If yes, we should report it to the upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209522] New: i915 pipe state doesn't match! WARNING: CPU: 1 PID: 4367 at drivers/gpu/drm/i915/display/intel_modeset_verify.c:219 intel_modeset_verify_crtc+0x3c5/0x3f0 [i915]
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209522 Bug ID: 1209522 Summary: i915 pipe state doesn't match! WARNING: CPU: 1 PID: 4367 at drivers/gpu/drm/i915/display/intel_modeset_verify.c:21 9 intel_modeset_verify_crtc+0x3c5/0x3f0 [i915] 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: mpdesouza(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi! it happens from time to time, but now I finally was able to configure journald to catch it. It usually happens on high load. I don't have a reproducer and either a step by step about how to trigger this problem. I'm currently using a Dell Docking station, using two additional monitors. Please let me know if you need more info! Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:98:pipe A] mismatch in infoframes.enable (expected 0x0000000> Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: [drm] *ERROR* mismatch in vsc dp sdp Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: [drm] *ERROR* expected: Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: DP SDP: VSC, revision 0, length 0 Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: pixelformat: RGB Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: colorimetry: sRGB Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: bpc: 0 Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: dynamic range: VESA range Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: content type: Not defined Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: [drm] *ERROR* found: Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: DP SDP: VSC, revision 2, length 8 Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: pixelformat: RGB Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: colorimetry: sRGB Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: bpc: 0 Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: dynamic range: VESA range Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: content type: Not defined Mar 20 11:53:20 daedalus kernel: ------------[ cut here ]------------ Mar 20 11:53:20 daedalus kernel: pipe state doesn't match! Mar 20 11:53:20 daedalus kernel: WARNING: CPU: 1 PID: 4367 at drivers/gpu/drm/i915/display/intel_modeset_verify.c:219 intel_modeset_> Mar 20 11:53:20 daedalus kernel: Modules linked in: usbhid ccm uinput rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device af_pac> Mar 20 11:53:20 daedalus kernel: iTCO_vendor_support processor_thermal_device snd_pcm processor_thermal_rfim processor_thermal_mbox> Mar 20 11:53:20 daedalus kernel: ghash_clmulni_intel rc_core video sha512_ssse3 rtsx_pci_sdmmc xhci_pci xhci_pci_renesas mmc_core x> Mar 20 11:53:20 daedalus kernel: CPU: 1 PID: 4367 Comm: gnome-shell Not tainted 6.2.6-1-default #1 openSUSE Tumbleweed 7d732c069aa49> Mar 20 11:53:20 daedalus kernel: Hardware name: Dell Inc. Latitude 5320/074GF2, BIOS 1.24.3 10/27/2022 Mar 20 11:53:20 daedalus kernel: RIP: 0010:intel_modeset_verify_crtc+0x3c5/0x3f0 [i915] Mar 20 11:53:20 daedalus kernel: Code: 4c 8b 04 24 e9 f9 fd ff ff 48 c7 c7 d0 fb 12 c1 e8 30 32 08 f2 0f 0b 4c 8b 04 24 0f b6 44 24 > Mar 20 11:53:20 daedalus kernel: RSP: 0018:ffff9c92c0b27b10 EFLAGS: 00010286 Mar 20 11:53:20 daedalus kernel: RAX: 0000000000000000 RBX: ffff88d1194602a8 RCX: 0000000000000027 Mar 20 11:53:20 daedalus kernel: RDX: ffff88d3bf6624c8 RSI: 0000000000000001 RDI: ffff88d3bf6624c0 Mar 20 11:53:20 daedalus kernel: RBP: ffff88d0d2efc000 R08: 0000000000000000 R09: ffff9c92c0b279b8 Mar 20 11:53:20 daedalus kernel: R10: 0000000000000003 R11: ffff88d3cf742b28 R12: ffff88d044966000 Mar 20 11:53:20 daedalus kernel: R13: ffff88d119410000 R14: ffff88d119460000 R15: ffff88d1194602b0 Mar 20 11:53:20 daedalus kernel: FS: 00007ff58c8145c0(0000) GS:ffff88d3bf640000(0000) knlGS:0000000000000000 Mar 20 11:53:20 daedalus kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 20 11:53:20 daedalus kernel: CR2: 000055c4e0ae7eb0 CR3: 000000010670c003 CR4: 0000000000770ee0 Mar 20 11:53:20 daedalus kernel: PKRU: 55555554 Mar 20 11:53:20 daedalus kernel: Call Trace: Mar 20 11:53:20 daedalus kernel: <TASK> Mar 20 11:53:20 daedalus kernel: intel_atomic_commit_tail+0x958/0xea0 [i915 3266444b8651c009ef6c700725f41e4a26b9ad4d] Mar 20 11:53:20 daedalus kernel: intel_atomic_commit+0x34f/0x390 [i915 3266444b8651c009ef6c700725f41e4a26b9ad4d] Mar 20 11:53:20 daedalus kernel: drm_atomic_commit+0x93/0xc0 Mar 20 11:53:20 daedalus kernel: ? __pfx___drm_printfn_info+0x10/0x10 Mar 20 11:53:20 daedalus kernel: drm_mode_atomic_ioctl+0x93d/0xb30 Mar 20 11:53:20 daedalus kernel: ? __pfx_drm_mode_atomic_ioctl+0x10/0x10 Mar 20 11:53:20 daedalus kernel: drm_ioctl_kernel+0xbe/0x160 Mar 20 11:53:20 daedalus kernel: drm_ioctl+0x221/0x420 Mar 20 11:53:20 daedalus kernel: ? __pfx_drm_mode_atomic_ioctl+0x10/0x10 Mar 20 11:53:20 daedalus kernel: ? __x64_sys_ioctl+0xa8/0xd0 Mar 20 11:53:20 daedalus kernel: __x64_sys_ioctl+0x8d/0xd0 Mar 20 11:53:20 daedalus kernel: do_syscall_64+0x58/0x80 Mar 20 11:53:20 daedalus kernel: ? do_syscall_64+0x67/0x80 Mar 20 11:53:20 daedalus kernel: ? __irq_exit_rcu+0x3b/0xe0 Mar 20 11:53:20 daedalus kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc Mar 20 11:53:20 daedalus kernel: RIP: 0033:0x7ff58f90dabf Mar 20 11:53:20 daedalus kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 > Mar 20 11:53:20 daedalus kernel: RSP: 002b:00007ffe71826070 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Mar 20 11:53:20 daedalus kernel: RAX: ffffffffffffffda RBX: 0000563ddd5149b0 RCX: 00007ff58f90dabf Mar 20 11:53:20 daedalus kernel: RDX: 00007ffe71826110 RSI: 00000000c03864bc RDI: 000000000000000a Mar 20 11:53:20 daedalus kernel: RBP: 00007ffe71826110 R08: 0000000000000007 R09: 000000000000002f Mar 20 11:53:20 daedalus kernel: R10: 000000000000002a R11: 0000000000000246 R12: 00000000c03864bc Mar 20 11:53:20 daedalus kernel: R13: 000000000000000a R14: 0000563ddb928440 R15: 0000563ddabad830 Mar 20 11:53:20 daedalus kernel: </TASK> Mar 20 11:53:20 daedalus kernel: ---[ end trace 0000000000000000 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1209436] I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c54 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #54 from Marcus Meissner <meissner(a)suse.com> --- The old kernel was retracted, you can still use that. (deinstall the released buggy one). The new kernel currently enters QA, will be released in the next days. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190261] New: Kernel scriptlets: XXX: Only call mokutil if UEFI and shim are used
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1190261 Bug ID: 1190261 Summary: Kernel scriptlets: XXX: Only call mokutil if UEFI and shim are used 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: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Spin-off from bug 1189841. From https://github.com/openSUSE/suse-module-tools/pull/33: @mwilck: so why not test this? e.g. like this: if [ "$(mokutil --sb-state 2>/dev/null)" = "SecureBoot enabled" ]; then ... fi @hramrach: ??? The part that github displays as context for this comment does not look relevant @hramrach hramrach 21 hours ago Member Right, if you refer to XXX: Only call mokutil if UEFI and shim are used then I have no opinion on that. Should be probably handled in a separate bug and the implications of any possible check discussed to death. @hramrach hramrach 21 hours ago Member Actually, there is the problem that on arm64 you suddenly get from no shim to shim on SP update without any warning so this is really hairy to get right. Really deserves a separate bug. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1209540] New: Kernel update hangs on boot
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209540 Bug ID: 1209540 Summary: Kernel update hangs on boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bugz57(a)top.geek.nz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865704 --> http://bugzilla.opensuse.org/attachment.cgi?id=865704&action=edit console output when hanging The kernel update a few days ago to kernel-default-5.14.21-150400.24.49.3.x86_64 hangs on boot, after the grub menu has been and gone. I have photos of the console output when booting the recovery version of the kernel. At that point console output just stops. Keyboard numlock/capslock do nothing, but sysrq sequences work (r e i s u b) and allow to reboot however cleanly. I had recently fiddled with the bios but can't find any settings that make this kernel boot. There is no change to USB devices connected. There was no change to any hardware. There is an nvidia graphics card but no nvidia driver nor nv are loaded; the card is unused. In any case, the previous kernel kernel-default-5.14.21-150400.24.46.1.x86_64 boots OK with any bios setting and with all USB devices connected. In 4 years no kernel has ever hung on boot on this box. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1209436] I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 Jeffrey Cheung <jcheung(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |jcheung(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208728] New: Thinkpad X1 Carbon Gen 10 won't enter S3 sleep on kernel 6
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208728 Bug ID: 1208728 Summary: Thinkpad X1 Carbon Gen 10 won't enter S3 sleep on kernel 6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: victorfuga(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with kernel 6, my thinkpad x1 carbon will not enter s3 sleep even when set as the default sleep option. Checked a few distros and noted it was working using kernel 5.19 "LTS" in manjaro. Currently running Tumbleweed snapshot 20230226, sleep mode is set to "Linux" in the bios. Checked on lid close, sleep button in KDE, and Fn + 4 key combo. $ cat /sys/power/mem_sleep s2idle [deep] $ sudo journalctl | grep "PM: suspend" | tail -2 2�� 27 18:29:09 reisen kernel: PM: suspend entry (s2idle) 2�� 27 18:29:11 reisen kernel: PM: suspend exit -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1200983] mouse & keyboard not available after a reboot (needs replug the devices)
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c14 --- Comment #14 from Michael Hirmke <opensuse(a)mike.franken.de> --- (In reply to Takashi Iwai from comment #13) > (In reply to Michael Hirmke from comment #12) > > (In reply to Stefan Dirsch from comment #10) > > > Thanks for testing. Indeed this makes it a kernel issue. You could also test > > > the mouse on the Linux console via 'evtest /dev/input/eventXX', but this is > > > a bit complicated to figure out the right device. So I only wanted to > > > mention keyboard here. > > > > Keyboard and mouse both have problems one the console, too. > > The keyboard vanishes after a few seconds and returns, as soon as a key is > > pressed, but the first keypress is not shown. The mouse never works on the > > console - no events are shown. > > What do you mean "vanishes" here? It means that the /dev/input/event* device > is gone? no, there is no mouse pointer and the keyboard light is off. > > The point to check here is whether the device file persists and can > read/write from a user-space (no matter whether it's processed or not). Or > is the (USB?) audio device itself disappears and reappears automatically. Because the keyboard also has problems, this isn't easy to debug. What exactly would you like me to test? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207915] amdgpu 0000:00:01.0: amdgpu: GPU fault detected: 147 0x00422002 for process sddm-greeter pid 2186 thread sddm-greet:cs0 pid 2193
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207915 http://bugzilla.opensuse.org/show_bug.cgi?id=1207915#c4 John Shand <jshand2013(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from John Shand <jshand2013(a)gmail.com> --- i think this was a once off. i will close it -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208756] Goodix GDIX1003/GT9110P i2c device is Unsupported
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208756 https://bugzilla.suse.com/show_bug.cgi?id=1208756#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you give hwinfo output? Also the output of acpidump. GDX10003 seems to be a new chip, so you'll likely need to do trial-and-error approach with the customized kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207915] amdgpu 0000:00:01.0: amdgpu: GPU fault detected: 147 0x00422002 for process sddm-greeter pid 2186 thread sddm-greet:cs0 pid 2193
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207915 https://bugzilla.suse.com/show_bug.cgi?id=1207915#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jshand2013(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(jshand2013@gmail. | |com) --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Sounds like a one-off issue. Is the problem reproduced? If not, let's close. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200983] mouse & keyboard not available after a reboot (needs replug the devices)
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c13 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Michael Hirmke from comment #12) > (In reply to Stefan Dirsch from comment #10) > > Thanks for testing. Indeed this makes it a kernel issue. You could also test > > the mouse on the Linux console via 'evtest /dev/input/eventXX', but this is > > a bit complicated to figure out the right device. So I only wanted to > > mention keyboard here. > > Keyboard and mouse both have problems one the console, too. > The keyboard vanishes after a few seconds and returns, as soon as a key is > pressed, but the first keypress is not shown. The mouse never works on the > console - no events are shown. What do you mean "vanishes" here? It means that the /dev/input/event* device is gone? The point to check here is whether the device file persists and can read/write from a user-space (no matter whether it's processed or not). Or is the (USB?) audio device itself disappears and reappears automatically. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209197] Kernel 6.2.2 with older NVIDIA graphics won't boot (freeze after 4.5 sec into boot process)
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209197 https://bugzilla.suse.com/show_bug.cgi?id=1209197#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sddrossy(a)aol.com, | |tiwai(a)suse.com Flags| |needinfo?(sddrossy(a)aol.com) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Seems to be a problem of nouveau. Could you report rather to the upstream, gitlab.freedesktop.org Issues? -- You are receiving this mail because: You are the assignee for the bug.

1 0