April 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1211226] Eliminate the need for 'OBS source links': convert to _multibuild
by bugzilla_noreply＠suse.com 10 Apr '24

10 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1211226 Bug 1211226 depends on bug 1218998, which changed state. Bug 1218998 Summary: cannot abort build/restart build/wipe binaries for multibuild packages https://bugzilla.suse.com/show_bug.cgi?id=1218998 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1221504] bluetooth errors on every kernel starting
by bugzilla_noreply＠suse.com 10 Apr '24

10 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221504 https://bugzilla.suse.com/show_bug.cgi?id=1221504#c19 --- Comment #19 from Andreas <opendreas(a)gmail.com> --- (In reply to Takashi Iwai from comment #15) > OK, then it should be reported to the upstream devs. > Care to do that from your side? At best, write to linux-bluetooth ML. Feel > free to put me (tiwai(a)suse.de) to Cc. > Alternatively, you can report to bugzilla.kernel.org, but it gets little > attention in general. (In reply to Takashi Iwai from comment #15) > OK, then it should be reported to the upstream devs. > Care to do that from your side? At best, write to linux-bluetooth ML. Feel > free to put me (tiwai(a)suse.de) to Cc. > Alternatively, you can report to bugzilla.kernel.org, but it gets little > attention in general. I created a new issue, but I don't see an option to add you to the CC list on github. https://github.com/bluez/bluez/issues/809 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193599] intel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 09 Apr '24

09 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193599 https://bugzilla.suse.com/show_bug.cgi?id=1193599#c46 --- Comment #46 from Andreas <opendreas(a)gmail.com> --- (In reply to Paolo De Pasquale from comment #45) > (In reply to Andreas from comment #44) > > > No. One user attributes these errors to freezes in Wine and WeChat. > > I can confirm wine freezes on my Thinkpad ThinkPad P15 Gen 1 running TW > 20240402 It would probably be nice to write about this on GitLab and attach the log. https://gitlab.freedesktop.org/drm/intel/-/issues/4458#note_2336439 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193599] intel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 09 Apr '24

09 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193599 https://bugzilla.suse.com/show_bug.cgi?id=1193599#c45 --- Comment #45 from Paolo De Pasquale <paolo.depasquale(a)suse.com> --- (In reply to Andreas from comment #44) > No. One user attributes these errors to freezes in Wine and WeChat. I can confirm wine freezes on my Thinkpad ThinkPad P15 Gen 1 running TW 20240402 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193599] intel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 09 Apr '24

09 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193599 https://bugzilla.suse.com/show_bug.cgi?id=1193599#c44 --- Comment #44 from Andreas <opendreas(a)gmail.com> --- Created attachment 874166 --> https://bugzilla.suse.com/attachment.cgi?id=874166&action=edit journald-6.4.0-150600.1-patched (In reply to Takashi Iwai from comment #43) > (In reply to Andreas from comment #40) > > The following message contains patches from the Intel developer. > > https://patchwork.freedesktop.org/series/125157/ > > The patches aren't included in the upstream (yet?). No. One user attributes these errors to freezes in Wine and WeChat. I don't use these programs so I can't confirm this. The Intel developer says they can't do anything because... no access to proprietary nvidia module. In theory, these errors occur when nothing is connected to the HDMI port. > I'm building a test kernel for SLE15-SP6 in OBS home:tiwai:bsc1193599-sp6 > repo. > The package will appear later at > http://download.opensuse.org/repositories/home:/tiwai:/bsc1193599-sp6/pool/ > > Please give it a try later. The patch works, the errors have disappeared. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222345] Laptop wakes from suspend once the user closes the lid
by bugzilla_noreply＠suse.com 06 Apr '24

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Then some spurious interrupt must be waking up the machine. Please check the following: - Enable/disable LID ACPI: To check the status: % cat /proc/acpi/wakeup To toggle the status: % echo LID > /proc/acpi/wakeup If this doesn't influence, it's something else than ACPI wakeup. Then, you can try the direct suspend by echo mem > /sys/power/state Does it behave differently? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222345] Laptop wakes from suspend once the user closes the lid
by bugzilla_noreply＠suse.com 06 Apr '24

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c7 Tristan Miller <psychonaut(a)nothingisreal.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #7 from Tristan Miller <psychonaut(a)nothingisreal.com> --- Yes, I've rebooted (still using 6.8.4-rc1) and the problem occurs again. I suspect that the kernel version may have nothing to do with this bug. Rather, each time the computer is rebooted, it somehow decides whether or not closing the lid will wake from suspend, and it maintains this behaviour at least until the next reboot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219522] New: Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 06 Apr '24

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 Bug ID: 1219522 Summary: Kernel panic with 6.7.x version Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: e.kleinmentink(a)zonnet.nl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872422 --> https://bugzilla.suse.com/attachment.cgi?id=872422&action=edit dmesg 6.6.11-1 kernel I get a kernel panic since the 6.7.x kernels. The capslock key is flickering and if i use the "recovery mode" i usually see: [T8] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.16, id: 0x1e2b1, caps: 0xf01fa3/0x940300/0x12e800/0x400000, board id: 3276, fw id: 2700068 [T8] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [T8] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input2 I have no idea how to debug this. No error message. In the past i applied a kernel bisect (for debian i think) but i could not find a guide for Tumbleweed. Hardware: Lenovo T580 Grub menu contains: * 6.7.2-1 * 6.7.1-2 * 6.6.11-1 Included a "dmesg" output of a normal boot with the "6.6.11-1" kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 22

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 06 Apr '24

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c48 --- Comment #48 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- Created attachment 874102 --> https://bugzilla.suse.com/attachment.cgi?id=874102&action=edit ok_6.8.2-2.gb88b81e-default -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 06 Apr '24

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c47 --- Comment #47 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- Thanks for all the help! Can this bug also explain the random freezes while in desktop mode or is this code called only once (at boot)? How to continue? The current change at least prevent a panic but i assume a driver still contains a bug/race-condition. Can i see in which (suse) mainline kernel this workaround is upstreamed? Latest commit seems a while ago: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/dri… Should i file a bug somewhere? I will include "ok_6.8.2-2.gb88b81e-default.txt". The same kernel version log, but that startup did not trigger the error. -- You are receiving this mail because: You are the assignee for the bug.

1 0