February 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 11 Feb '23

11 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tiwai(a)suse.com) | --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Go to the download URL for the OBS repo, and download kernel-default.rpm, kernel-default-extra.rpm and kernel-default-optional.rpm for the architecture (x86_64): http://download.opensuse.org/repositories/Kernel:/SLE15-SP5/pool/ Then install them via zypper install (as root): % zypper in kernel-default-*.rpm But, it'd be safer to increase the number of installable kernels beforehand. Edit /etc/zypp/zypp.conf (as root), and modify the line defining "multiversion.kernels" to add more entries, e.g. multiversion.kernels = latest,latest-1,latest-2,latest-3,running This will keep up to 4 kernels without purge. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207837] amdgpu: externals displays don't work when booting with plugged in docking station
by bugzilla_noreply＠suse.com 11 Feb '23

11 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207837 https://bugzilla.suse.com/show_bug.cgi?id=1207837#c10 --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- Could you verify whether the problem is already addressed with the kernel in OBS Kernel:HEAD repo? If yes, we'll try to backport the fix. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207837] amdgpu: externals displays don't work when booting with plugged in docking station
by bugzilla_noreply＠suse.com 10 Feb '23

10 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207837 https://bugzilla.suse.com/show_bug.cgi?id=1207837#c9 --- Comment #9 from David Anes <david.anes(a)suse.com> --- Ok, I reported upstream: https://gitlab.freedesktop.org/drm/amd/-/issues/2171#note_1765097 It seems upstream already patched and closed the issue: https://gitlab.freedesktop.org/drm/amd/-/issues/2171 Can we have the latest patches that landed in 6.2 backported to 6.1? I would like to test these and see if the bug is already fixed and report here. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 10 Feb '23

10 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c3 Fritz Hudnut <non.space.1(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(tiwai(a)suse.com) --- Comment #3 from Fritz Hudnut <non.space.1(a)gmail.com> --- (In reply to Takashi Iwai from comment #2) > Could you retest with the kernel in OBS Kernel:SLE15-SP5 repo? If the bug > persists, please give the hwinfo output. @Takashi: Happy to do that, but jammed today. The other problem is not knowing how to do what you are suggesting . . . ??? Add "SLE15-SP5" to the repos?? Search "OBS kernel:SLE15-SP5" in YaST? and then install it? For the most part I have a bunch of linux installs that I maintain, but don't "get under the hood" with them, except the fix them . . . which lately TW and Leap 15.5 have been requesting more of my attention that I have to spare . . . . The "third" confirmation is that I had the same problem with another openSUSE based system yesterday, a Gecko rolling MATE iteration had the same problem as the other two, failure to revive from suspending, display stays black, etc. Historically, when these "failure to suspend or revive" issues showed up it was an "nvidia" issue . . . so years ago I stopped using proprietary drivers. But recently in TW there was a "G06" package that somehow insinuated itself into the system, wiping out video in older cards like my GTX780. After that issue I scanned the upgrade packages looking for "G06" but didn't see any in the Leap or Gecko zypper listings . . . but possibly some aspects of "nvidia-ness" have been adapted by the system?? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208123] Random audio pops, crackling sound on HQ USB DAC Fulla Shiit
by bugzilla_noreply＠suse.com 10 Feb '23

10 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208123 https://bugzilla.suse.com/show_bug.cgi?id=1208123#c2 --- Comment #2 from Bystron <cartesius68(a)gmail.com> --- Created attachment 864818 --> https://bugzilla.suse.com/attachment.cgi?id=864818&action=edit alsa-info.sh --no-upload -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207900] Thinkpad P16 Gen 1 freezes when put into Dockingstation
by bugzilla_noreply＠suse.com 10 Feb '23

10 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c7 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mvetter(a)suse.com) --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- So, did you try the boot options I mentioned in comment 2? Also, tests with the older kernels? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207900] Thinkpad P16 Gen 1 freezes when put into Dockingstation
by bugzilla_noreply＠suse.com 10 Feb '23

10 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207900 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mvetter(a)suse.com) | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207900] Thinkpad P16 Gen 1 freezes when put into Dockingstation
by bugzilla_noreply＠suse.com 10 Feb '23

10 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvetter(a)suse.com Flags| |needinfo?(mvetter(a)suse.com) --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Then could you check a few old kernels to see whether it's a recent regression or not? Some kernel packages are found in my OBS repo like OBS home:tiwai:kernel:6.0, home:tiwai:kernel:5.19, ... Note that those are unofficial builds, hence you'd need to turn off Secure Boot (if enabled on BIOS). Also, please give the hwinfo output. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207837] amdgpu: externals displays don't work when booting with plugged in docking station
by bugzilla_noreply＠suse.com 10 Feb '23

10 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207837 https://bugzilla.suse.com/show_bug.cgi?id=1207837#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Actually, that's no real "crash" but merely a kernel warning with the stack trace (see the line "WARNING: CPU: X PID: Y at ...."). So the problem seems to be that the driver doesn't recognize / handle the unplug of DP before the resume properly. This should be reported to the upstream. Care to add the follow-up comment to the upstream gitlab issues? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 10 Feb '23

10 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |non.space.1(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(non.space.1@gmail | |.com) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Could you retest with the kernel in OBS Kernel:SLE15-SP5 repo? If the bug persists, please give the hwinfo output. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208123] Random audio pops, crackling sound on HQ USB DAC Fulla Shiit
by bugzilla_noreply＠suse.com 10 Feb '23

10 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208123 https://bugzilla.suse.com/show_bug.cgi?id=1208123#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cartesius68(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(cartesius68@gmail | |.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you give alsa-info.sh output? Run the script with --no-upload option, and attach the output to Bugzilla. This kind of crackling noise is often due to the clock issues with the implicit feedback sink. But it's hard to say without seeing the device information. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208013] New: [Build 395.1] lockup in GNOME on three migrated systems from older releases
by bugzilla_noreply＠suse.com 10 Feb '23

10 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208013 Bug ID: 1208013 Summary: [Build 395.1] lockup in GNOME on three migrated systems from older releases Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://openqa.opensuse.org/tests/3098160/modules/desk top_mainmenu/steps/2 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation Hello team, at first time it look like as sporadic hang, however separate four migration test got stuck at the same point in GNOME after migration from previous release. Kernel version: 5.14.21-150500.37-default (hvc1) Migration from 42.1 https://openqa.opensuse.org/tests/3097642#step/desktop_mainmenu/2 Migration from 42.2 https://openqa.opensuse.org/tests/3098117#step/desktop_mainmenu/2 Migration from 42.3 (cryptlvm) https://openqa.opensuse.org/tests/3097662#step/desktop_mainmenu/2 Migration from 42.3 https://openqa.opensuse.org/tests/3097645#step/desktop_mainmenu/2 From e.g. https://openqa.opensuse.org/tests/3097642/logfile?filename=serial0.txt [ 3794.441888][ C0] sysrq: Show State [ 3794.844399][ C0] sysrq: Show Blocked State openQA test in scenario opensuse-15.5-DVD-x86_64-upgrade_Leap_42.2_gnome@64bit fails in [desktop_mainmenu](https://openqa.opensuse.org/tests/3098160/modules/desktop… ## Test suite description 20180309 -- lnussel -- switched to last available 42.2 image 20180206. Using opensuse-42.2-x86_64-Updates-20180313-2-gnome(a)64bit.qcow2 to resolved out-of-space, see https://progress.opensuse.org/issues/33061 ## Reproducible Fails since (at least) Build [365.2](https://openqa.opensuse.org/tests/2981267) ## Expected result Last good: [363.1](https://openqa.opensuse.org/tests/2969396) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1208123] New: Random audio pops, crackling sound on HQ USB DAC Fulla Shiit
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208123 Bug ID: 1208123 Summary: Random audio pops, crackling sound on HQ USB DAC Fulla Shiit 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: cartesius68(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Regardless whether pipewire or "old" pulseaudio is used I'm experiencing random audio pops and crackling sounds. Have spent a day playing with priorities, turning off resampling, trying different buffering related options without any luck. Random post on Reddit confirmed that current TW is affected by this and many owners of (not only) HQ USB DACs confirmed that. It's very hard to debug this but it's definitely not related to resampling or process priority. Willing to help debug that. IMPORTANT Have verified that the hardware is OK. Audio is almost perfect on FreeBSD 13.1/portaudio. System: Kernel: 6.1.10-1-default arch: x86_64 bits: 64 Desktop: GNOME v: 43.2 Distro: openSUSE Tumbleweed 20230208 Device-4: Schiit Audio Im Fulla type: USB driver: hid-generic,snd-usb-audio,usbhid Bus 001 Device 003: ID 30be:0100 Schiit Audio I'm Fulla Schiit -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207837] amdgpu: externals displays don't work when booting with plugged in docking station
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207837 https://bugzilla.suse.com/show_bug.cgi?id=1207837#c7 --- Comment #7 from David Anes <david.anes(a)suse.com> --- Created attachment 864810 --> https://bugzilla.suse.com/attachment.cgi?id=864810&action=edit journal with dock connections and disconnections between suspensions (In reply to Takashi Iwai from comment #6) > Try to check whether Secure Boot is set on BIOS. You'll need to turn it off > for booting with the unofficial kernels. Doh! I forgot that. Thanks, now I'm able to use the 6.0.x branch. I was able to reproduce the behaviour as I described, so there is something between 6.0 and 6.1 that changed that breaks waking up the displays, as Jiri mentioned. Also, I was able to crash the latest 6.1.x kernel playing with resuming/suspending and connecting/disconnecting the dock while the laptop is suspended. I'm adding the log. Let me know if a new bug should be created. Here are the steps to crash the latest 6.1.x kernel (there are 9 steps below): 1) Boot the laptop, dock disconnected. 2) Connect the dock. 3) Suspend the system. 4) Disconnect the dock while suspended. 5) Wake up the laptop, with the dock disconnected. Here the kernel complains with the following messages (but does not crash). > Feb 09 20:21:14.590862 laptop kernel: [drm:dm_late_init [amdgpu]] *ERROR* DM_MST: Failed to start MST > Feb 09 20:21:14.590913 laptop kernel: [drm:amdgpu_device_ip_late_init [amdgpu]] *ERROR* late_init of IP block <dm> failed -5 > Feb 09 20:21:14.590941 laptop kernel: amdgpu 0000:06:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -5 > Feb 09 20:21:14.591133 laptop kernel: amdgpu 0000:06:00.0: PM: failed to resume async: error -5 > Feb 09 20:21:14.591328 laptop kernel: OOM killer enabled. 6) Suspend the laptop. 7) Connect the dock while suspended. 8) Wake up the laptop (dock connected at this point). 9) Kernel crash: > Feb 09 20:21:14.854008 laptop kernel: Hardware name: LENOVO 20UJS2B905/20UJS2B905, BIOS R1CET63W(1.32 ) 04/09/2021 > Feb 09 20:21:14.854041 laptop kernel: RIP: 0010:drm_dp_atomic_release_time_slots+0x1bb/0x1f0 [drm_display_helper] > Feb 09 20:21:14.854078 laptop kernel: Code: 08 44 8b 4b 0c 49 89 e8 48 c7 c1 ef a7 23 c1 ba 04 00 00 00 48 c7 c7 00 e3 23 c1 e8 1f 9c 95 c2 eb 8a 44 89 e8 e9 31 ff ff ff <0f> 0b 49 8b 44 24 58 4c 89 e9 48 89 ea 48 c7 c6 f0 8f 23 c1 48 8b > Feb 09 20:21:14.854118 laptop kernel: RSP: 0018:ffffba938207b958 EFLAGS: 00010246 > Feb 09 20:21:14.854155 laptop kernel: RAX: ffff92fd84a624b8 RBX: ffff92fd84a624a0 RCX: 0000000000000001 > Feb 09 20:21:14.854185 laptop kernel: RDX: ffff92fd84a624b8 RSI: ffff92fd84a62480 RDI: ffff92fda1b02540 > Feb 09 20:21:14.854214 laptop kernel: RBP: ffff92fd85f55000 R08: ffffba938207b850 R09: ffff92fd8443e1e0 > Feb 09 20:21:14.854244 laptop kernel: R10: ffff92fe211c8a00 R11: 0000000000000000 R12: ffff92fda1b02540 > Feb 09 20:21:14.854269 laptop kernel: R13: ffff92fd84a62480 R14: ffff92fe326646c0 R15: ffff92fd8443e100 > Feb 09 20:21:14.854293 laptop kernel: FS: 00007f10b0217940(0000) GS:ffff93007f980000(0000) knlGS:0000000000000000 > Feb 09 20:21:14.854334 laptop kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > Feb 09 20:21:14.854370 laptop kernel: CR2: 00007f4d0b01943e CR3: 000000011e384000 CR4: 0000000000350ee0 > Feb 09 20:21:14.854405 laptop kernel: Call Trace: > Feb 09 20:21:14.854441 laptop kernel: <TASK> > Feb 09 20:21:14.854467 laptop kernel: drm_atomic_helper_check_modeset+0x335/0xdc0 > Feb 09 20:21:14.854512 laptop kernel: amdgpu_dm_atomic_check+0x54/0x12c0 [amdgpu b2b447105068cd3b6d7d93eaa9a3d2a7ff3ec4c6] > Feb 09 20:21:14.854538 laptop kernel: ? __kmem_cache_alloc_node+0x1b1/0x320 > Feb 09 20:21:14.854567 laptop kernel: ? amdgpu_dm_connector_atomic_duplicate_state+0x25/0xb0 [amdgpu b2b447105068cd3b6d7d93eaa9a3d2a7ff3ec4c6] > Feb 09 20:21:14.854601 laptop kernel: ? __kmalloc_node_track_caller+0x4a/0x150 > Feb 09 20:21:14.854635 laptop kernel: ? __drm_atomic_helper_connector_duplicate_state+0x54/0x80 > Feb 09 20:21:14.854668 laptop kernel: ? amdgpu_dm_connector_atomic_duplicate_state+0x38/0xb0 [amdgpu b2b447105068cd3b6d7d93eaa9a3d2a7ff3ec4c6] > Feb 09 20:21:14.854696 laptop kernel: drm_atomic_check_only+0x533/0xb90 > Feb 09 20:21:14.854729 laptop kernel: drm_atomic_commit+0x58/0xf0 > Feb 09 20:21:14.854762 laptop kernel: ? drm_plane_get_damage_clips.cold+0x1c/0x1c > Feb 09 20:21:14.854800 laptop kernel: drm_atomic_helper_set_config+0x70/0xb0 > Feb 09 20:21:14.854839 laptop kernel: drm_mode_setcrtc+0x340/0x820 > Feb 09 20:21:14.854870 laptop kernel: ? drm_mode_getcrtc+0x180/0x180 > Feb 09 20:21:14.854905 laptop kernel: drm_ioctl_kernel+0xc1/0x160 > Feb 09 20:21:14.854939 laptop kernel: drm_ioctl+0x1de/0x460 > Feb 09 20:21:14.854968 laptop kernel: ? drm_mode_getcrtc+0x180/0x180 > Feb 09 20:21:14.854993 laptop kernel: amdgpu_drm_ioctl+0x4a/0x80 [amdgpu b2b447105068cd3b6d7d93eaa9a3d2a7ff3ec4c6] > Feb 09 20:21:14.855022 laptop kernel: __x64_sys_ioctl+0x90/0xd0 > Feb 09 20:21:14.855046 laptop kernel: do_syscall_64+0x5b/0x80 > Feb 09 20:21:14.855073 laptop kernel: ? syscall_exit_to_user_mode+0x17/0x40 > Feb 09 20:21:14.855102 laptop kernel: ? do_syscall_64+0x67/0x80 > Feb 09 20:21:14.855130 laptop kernel: ? syscall_exit_to_user_mode+0x17/0x40 > Feb 09 20:21:14.855149 laptop kernel: ? do_syscall_64+0x67/0x80 > Feb 09 20:21:14.855178 laptop kernel: ? exit_to_user_mode_prepare+0x166/0x1f0 > Feb 09 20:21:14.855206 laptop kernel: ? syscall_exit_to_user_mode+0x17/0x40 > Feb 09 20:21:14.855223 laptop kernel: ? do_syscall_64+0x67/0x80 > Feb 09 20:21:14.855252 laptop kernel: ? do_syscall_64+0x67/0x80 > Feb 09 20:21:14.855274 laptop kernel: ? exc_page_fault+0x66/0x150 > Feb 09 20:21:14.855302 laptop kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd > Feb 09 20:21:14.855337 laptop kernel: RIP: 0033:0x7f10b07209bf (... and continues with more and more stacktraces, one for each CPU ...) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189808] udp datagrams received out-of-order with kernel 5.3.18-lp152.72.1 onwards
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1189808 https://bugzilla.suse.com/show_bug.cgi?id=1189808#c10 --- Comment #10 from Simon Logan <simonalogan(a)gmail.com> --- Confirmed that kernel 5.14.21-150400.24.38-default is still fine. Let's close this one. Simon -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208113] New: FreeRTOS 10.0.0 matched in kernel-firmware-mediatek-20220509-150400.4.13.1.noarch.rpm
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208113 Bug ID: 1208113 Summary: FreeRTOS 10.0.0 matched in kernel-firmware-mediatek-20220509-150400.4.13.1.noarch .rpm Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: simonalogan(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Our security scanning tool has matched FreeRTOS 10.0.0 in kernel-firmware-mediatek-20220509-150400.4.13.1.noarch.rpm as follows. Full File Path /6.2.0.266/nvr/noarch/kernel-firmware-mediatek-20220509-150400.4.13.1.noarch.rpm/lib/firmware/mediatek/mt7986_wa.bin.xz/mt7986_wa.bin Signature 0:"/FreeRTOSv10.0.0" There are a number of high severity CVEs associated with FreeRTOS 10.0.0. Is it possible to have this updated? Thanks, Simon -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1208101] mount=ordered not shown on ext4 root filesystem in /proc/self/mounts
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208101 http://bugzilla.opensuse.org/show_bug.cgi?id=1208101#c1 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |Andreas.Stieger(a)gmx.de Resolution|--- |WONTFIX --- Comment #1 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- openSUSE Leap 15.3 is EOL. If this remains reproducible in a maintained release please re-open and move to the correct version. Closing for now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208101] New: mount=ordered not shown on ext4 root filesystem in /proc/self/mounts
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208101 Bug ID: 1208101 Summary: mount=ordered not shown on ext4 root filesystem in /proc/self/mounts Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: david(a)dgreaves.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running a 15.3 kvm client (hostname bsfe) on an openSuse 15.3 host kvm and host kernels are 5.3.18-150300.59.106-default The root filesystem is supposed to have data=ordered bsfe:~ # grep vda /etc/fstab /dev/vda / ext4 rw,noatime,user_xattr,acl,barrier=1,data=ordered 0 1 Both /proc/self/mountinfo and /proc/self/mounts do not show data=ordered bsfe:~ # grep vda /proc/self/mountinfo 96 1 254:0 / / rw,noatime shared:1 - ext4 /dev/vda rw,stripe=32 bsfe:~ # grep vda /proc/mounts /dev/vda / ext4 rw,noatime,stripe=32 0 0 The kernel messages show the options during mount like so: bsfe:~ # dmesg | grep vda | grep ordered [ 3.209441] EXT4-fs (vda): mounted filesystem with ordered data mode. Opts: (null) [ 3.648673] EXT4-fs (vda): re-mounted. Opts: user_xattr,acl,barrier=1,data=ordered The options in /proc/fs/ext4 DOES show data=ordered which I *think* means that the device is currently mounted with data=ordered. bsfe:~ # grep ordered /proc/fs/ext4/vda/options data=ordered Another filesystem does show this correctly/consistently: bbsfe:~ # grep vdc /etc/fstab /dev/vdc /var ext4 rw,noatime,user_xattr,acl,barrier=1,data=ordered 0 2 sfe:~ # grep vdc /proc/mounts /dev/vdc /var ext4 rw,noatime,stripe=32,data=ordered 0 0 bsfe:~ # grep vdc /proc/self/mountinfo 120 96 254:32 / /var rw,noatime shared:65 - ext4 /dev/vdc rw,stripe=32,data=ordered bsfe:~ # dmesg | grep vdc | grep ordered [ 3.804751] EXT4-fs (vdc): mounted filesystem with ordered data mode. Opts: user_xattr,acl,barrier=1,data=ordered bsfe:~ # grep ordered /proc/fs/ext4/vdc/options data=ordered In case it's useful : The vdX devices are mapped from an lvm over raid6 on the host libvirt boots directly into the kernel without a bootloader: <os> <type arch='x86_64' machine='pc-q35-2.9'>hvm</type> <kernel>/kvmboot/bsfe/vmlinuz-5.3.18-150300.59.106-default</kernel> <initrd>/kvmboot/bsfe/initrd-5.3.18-150300.59.106-default</initrd> <cmdline>root=/dev/vda read-only console=ttyS0 net.ifnames=0 biosdevname=0</cmdline> <boot dev='fd'/> </os> -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206224] Dell notebook drains battery during sleep
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1206224 https://bugzilla.suse.com/show_bug.cgi?id=1206224#c17 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(msvec(a)suse.com) --- Comment #17 from Takashi Iwai <tiwai(a)suse.com> --- Good to hear. Meanwhile, I tried to backport the patches for s2idle ACPI code on Leap 15.4 kernel. The test kernel is being built in OBS home:tiwai:bsc1206224 repo. Could you give it a try later, too? I'm not really sure whether this is relevant, as most of changes are basically for AMD, but it's still worth to try. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207837] amdgpu: externals displays don't work when booting with plugged in docking station
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207837 https://bugzilla.suse.com/show_bug.cgi?id=1207837#c4 --- Comment #4 from Jiri Belka <jiri.belka(a)suse.com> --- After a wake from suspend, the external monitors still do not work (although they were working before the suspend itself). I will upload logs later. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207948] Lenovo T14s Gen3 AMD resume from hibernation ends in kernel panic
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207948 https://bugzilla.suse.com/show_bug.cgi?id=1207948#c14 --- Comment #14 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Martin Jambor from comment #9) > > Does pstore store anything to efi afterall? > > I tried following > https://blogs.oracle.com/linux/post/pstore-linux-kernel-persistent-storage- > file-system > > I got as far as "cat /sys/module/pstore/parameters/backend" resulting > in "efi" but no file ever appeared in /sys/fs/pstore Weird. It would be also some /sys/firmware/efi/efivars/[Dd]ump*. But apparently, nothing is logged. Is the service running: systemctl status systemd-pstore.service ? > > Do you have kdump set up? > > I don't think so. So no, unless it is somehow on default. It should be a matter of zypper in kdump systemctl enable kdump Add something like crashkernel=192M to the kernel commandline. Reboot systemctl status kdump /sys/kernel/kexec_loaded should return 1. /boot/initrd-kdump should exist crash it by s2disk /var/crash should contain a folder after a crash. The blinking LED should not happen, the kdump kernel should be loaded instead. Thinking about it, it probably won't work. The resume kernel+initrd probably didn't manage to load kdump yet at this phase. Or maybe it jumped to the suspended kernel already and the suspended kernel crashes. In which case it could work. (In reply to Martin Jambor from comment #12) > (In reply to Jiri Slaby from comment #6) > > Yeah and I also asked you about: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/ > > Documentation/power/basic-pm-debugging.rst > > > > What last step (from [freezer, devices, ...]) does not expose the crash? > > None of them exposes it - even "core" returns fine without any > problems - except for "none" which of course results in the panic. Which means the BIOS does something weird during suspend. Or kernel does something weird during resume. > Funny thing, when triggering the suspend with > > echo platform > /sys/power/disk > echo disk > /sys/power/state > > (as opposed to "systemctl hibernate") the virtual console echo works > at the end of the unsuccessful resuming from disk. I.e. I can see the > letters I type - but there is no reaction from bash or anything, the > next bash prompt is not displayed either - until the panic when > everything stops... is it perhaps some watchdog that is triggering it? Another note: klog.service makes tty10 the console. Can you comment out the whole line containing /usr/bin/setlogcons in /usr/lib/systemd/system/klog.service? And also ignore_loglevel or loglevel=7 kernel parameters could help to show something (added on top of no_console_suspend). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207837] amdgpu: externals displays don't work when booting with plugged in docking station
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207837 https://bugzilla.suse.com/show_bug.cgi?id=1207837#c3 Jiri Belka <jiri.belka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jiri.belka(a)suse.com Flags|needinfo?(jirib79(a)gmail.com | |) | --- Comment #3 from Jiri Belka <jiri.belka(a)suse.com> --- (In reply to Takashi Iwai from comment #2) > Could you verify whether the issue is fixed with the latest TW kernel (6.1.9 > and later)? I just booted 6.1.10-3.g82ff25b-default from 'Kernel_stable' report and external monitors are working. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208069] New: Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208069 Bug ID: 1208069 Summary: Leap 15.5 & Gecko rolling plasma does not revive video from suspend? Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: non.space.1(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Having a recurring issue with Leap 15.5 not reviving from suspend on '12 Mac Pro, and the issue was also happening in another installed system, Gecko rolling Plasma. Leap 15.5 will suspend the machine and clicking on shift key will again start the "engine" and the display light turns blue, but the screen stays black. In the case of the Gecko install clicking suspend the machine makes some funny noise like it is "trying" to suspend, but the machine keeps running, the screen goes black. In one of the installs I got the display to come back up, but mousing around and clicking on the GUI does nothing . . . I think that was the Leap 15.5. I was switching systems to see if it was a "hardware" issue, but when I got to my Manjaro install it's fine; I can suspend and wake from suspend. I'm typing this in Manjaro. A forum request has been started on opensuse, so far the only suggestion in it has been to "file a bug report on bugzilla." The bugzilla server showed me another similar bug report from 2017 on a Plasma system; didn't have time today to read through it . . . just making the report here. https://bugzilla.opensuse.org/show_bug.cgi?id=1047729 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1207948] Lenovo T14s Gen3 AMD resume from hibernation ends in kernel panic
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207948 https://bugzilla.suse.com/show_bug.cgi?id=1207948#c7 --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- And yet (sorry), brand new BIOSes might be buggy, so no BIOS update available (e.g. via fwupd)? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207655] amdgpu [RX 7900] causing system freeze
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207655 https://bugzilla.suse.com/show_bug.cgi?id=1207655#c7 --- Comment #7 from Stefan Dirsch <sndirsch(a)suse.com> --- (In reply to Stefan Dirsch from comment #6) > I've branched Mesa to build Mesa 23.0.0-rc4. Unfortunately this doesn't > include these fixes yet. I think it was branched before the patches got > merged. :-( > > https://build.opensuse.org/package/show/home:sndirsch:branches:X11:XOrg/Mesa Took me some time to get build working again, but looks good now. ------------------------------------------------------------------- Wed Feb 8 13:24:22 UTC 2023 - Stefan Dirsch <sndirsch(a)suse.com> - Update to version 23.0.0-rc4 - adjusted n_stop-iris-flicker.patch, u_dep_xcb.patch, u_fix-build-on-ppc64le.patch - re-enabled xmlconfig (/usr/share/drirc.d config snippets) - adjusted n_no-sse2-on-ix86-except-for-intel-drivers.patch to fix build on %ix86 -- You are receiving this mail because: You are the assignee for the bug.

1 0