November 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] Account verification
by noreply＠suse.de 18 Nov '24

18 Nov '24

Dear user opensuse-kernelbugs, we have received your email verification request. To verify your email address, please follow this link: https://idp-portal.suse.com/univention/self-service/#page=verifyaccount&tok… If the link does not work, you can go to https://idp-portal.suse.com/univention/self-service/#page=verifyaccount and enter the following token manually: vNjCDHqnMwqYa48z3RokLQTpZdp3sYBxddU7iGJR9UhboG8guN3hssVvHHxVARWo -- To unsubscribe, e-mail: kernel-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kernel-bugs+owner(a)opensuse.org

2 1

[kernel-bugs] [Bug 1172181] test bug for assignee change
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

http://bugzilla.suse.com/show_bug.cgi?id=1172181 Jeff Mahoney <jeffm(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jeffm(a)suse.com |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 1

[Bug 1207854] kernel: warning about "pipe state doesn't match" when initializing DP displays at boot time
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1207854 https://bugzilla.suse.com/show_bug.cgi?id=1207854#c9 Adam Majer <amajer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Flags|needinfo?(amajer(a)suse.com) | Resolution|--- |FIXED --- Comment #9 from Adam Majer <amajer(a)suse.com> --- I'll close this as resolved for now. It's not reproducible anymore. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1220088] Hibernate completes shuts machine off *then* machine automatically turns back on.
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1220088 https://bugzilla.suse.com/show_bug.cgi?id=1220088#c32 --- Comment #32 from Paul Graff <pj.opensuse(a)gmx.com> --- Created attachment 878620 --> https://bugzilla.suse.com/attachment.cgi?id=878620&action=edit xorg log file, udev, keyboard as pwrb -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1220088] Hibernate completes shuts machine off *then* machine automatically turns back on.
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1220088 https://bugzilla.suse.com/show_bug.cgi?id=1220088#c31 --- Comment #31 from Paul Graff <pj.opensuse(a)gmx.com> --- I was looking at the xorg log file and this is an excerpt from it. [ 32.998] (II) config/udev: Adding input device Power Button (/dev/input/event3) [ 32.998] (**) Power Button: Applying InputClass "evdev keyboard catchall" [ 32.998] (**) Power Button: Applying InputClass "libinput keyboard catchall" [ 32.998] (**) Power Button: Applying InputClass "system-keyboard" [ 32.998] (II) LoadModule: "libinput" [ 32.999] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so [ 33.011] (II) Module libinput: vendor="X.Org Foundation" [ 33.011] compiled for 1.21.1.12, module version = 1.5.0 [ 33.011] Module class: X.Org XInput Driver [ 33.011] ABI class: X.Org XInput driver, version 24.4 [ 33.011] (II) Using input driver 'libinput' for 'Power Button' [ 33.011] (**) Power Button: always reports core events [ 33.011] (**) Option "Device" "/dev/input/event3" [ 33.022] (II) event3 - Power Button: is tagged by udev as: Keyboard [ 33.023] (II) event3 - Power Button: device is a keyboard [ 33.023] (II) event3 - Power Button: device removed [ 33.056] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3" [ 33.056] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6) [ 33.056] (**) Option "xkb_model" "pc105+inet" [ 33.056] (**) Option "xkb_layout" "us" [ 33.056] (**) Option "xkb_options" "terminate:ctrl_alt_bksp" [ 33.090] (II) event3 - Power Button: is tagged by udev as: Keyboard [ 33.090] (II) event3 - Power Button: device is a keyboard [ 33.091] (II) config/udev: Adding input device Power Button (/dev/input/event2) [ 33.091] (**) Power Button: Applying InputClass "evdev keyboard catchall" [ 33.091] (**) Power Button: Applying InputClass "libinput keyboard catchall" [ 33.091] (**) Power Button: Applying InputClass "system-keyboard" [ 33.091] (II) Using input driver 'libinput' for 'Power Button' [ 33.091] (**) Power Button: always reports core events [ 33.091] (**) Option "Device" "/dev/input/event2" [ 33.093] (II) event2 - Power Button: is tagged by udev as: Keyboard [ 33.093] (II) event2 - Power Button: device is a keyboard [ 33.093] (II) event2 - Power Button: device removed [ 33.116] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0C0C:00/input/input2/event2" [ 33.116] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7) [ 33.116] (**) Option "xkb_model" "pc105+inet" [ 33.116] (**) Option "xkb_layout" "us" [ 33.116] (**) Option "xkb_options" "terminate:ctrl_alt_bksp" [ 33.118] (II) event2 - Power Button: is tagged by udev as: Keyboard [ 33.118] (II) event2 - Power Button: device is a keyboard Would any of this udev event3 - Power Button: is tagged by udev as: Keyboard [ 33.023] (II) event3 - Power Button: device is a keyboard Have anything to do with this perhaps? Regardless I have attached an xorg log file. -Thanks -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1233416] CUPS printer discovery (lpinfo -v) causes kernel panic
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233416 https://bugzilla.suse.com/show_bug.cgi?id=1233416#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Please give the stack trace of the kernel crash. If we are lucky, this might have been recorded in the kernel logs. If not, and if the problem can be reliably reproduced, try to install kdump and get the kernel crash log. It's the essential info to start with. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1233416] CUPS printer discovery (lpinfo -v) causes kernel panic
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233416 https://bugzilla.suse.com/show_bug.cgi?id=1233416#c3 --- Comment #3 from Alex Ustinov <austinov(a)yandex.ru> --- (In reply to Johannes Meixner from comment #1) > My blind guess of the root cause of this kernel panic > is some specific hardware, in particular pluggable > hardware, like USB devices and things like that. Johannes, thank you for taking care of this. > I would try out if the kernel panic goes away > when you unplug as many hardware as possible > (e.g. all external hardware from your laptop) > and retry "lpinfo -v". No it does not go away unfortunately on my notebook without any external periphery. Already done that at the time of reporting the bug. lsusb only lists root hubs. I have no usb periphery in my computer, even the camera in this notebook is not USB camera. > Verify that the dependencies of all installed packages > are satisfied as 'root' via > # zypper verify --dry-run sudo zypper verify --dry-run [sudo] password for root: Loading repository data... Reading installed packages... Dependencies of all installed packages are satisfied. > Also verify that your installed RPM files are OK, > in particular your installed "cups" related things > as 'root' via > # rpm -V $( rpm -qa | grep cups ) sudo rpm -V $( rpm -qa | grep cups ) S.5....T. /usr/sbin/cupsd I am already tinkering with CUPS from git trunk on my system, but I tried removing and installing cups using zypper or yast and this did not help. The package system looks consistent. Please remember CUPS compiled from git tree works fine, that is why I am reporting bug to the distribution. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1233416] CUPS printer discovery (lpinfo -v) causes kernel panic
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233416 https://bugzilla.suse.com/show_bug.cgi?id=1233416#c2 --- Comment #2 from Johannes Meixner <jsmeix(a)suse.com> --- Alex Ustinov, instead of running all CUPS backend in /usr/lib/cups/backend/ via "lpinfo -v", you could run each of them one after the other manually. When you run a CUPS backend manually without command line options, it autodetects and reports the devices on stdout (plus debug messages on stderr) which belong to the particular CUPS backend, e.g. (preferably run CUPS backends as 'root') # /usr/lib/cups/backend/usb autodetects and reports USB printers. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1233416] CUPS printer discovery (lpinfo -v) causes kernel panic
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233416 https://bugzilla.suse.com/show_bug.cgi?id=1233416#c1 Johannes Meixner <jsmeix(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Printing |Kernel Flags| |needinfo?(austinov(a)yandex.r | |u) QA Contact|jsmeix(a)suse.com |qa-bugs(a)suse.de CC| |austinov(a)yandex.ru, | |jsmeix(a)suse.com Assignee|jsmeix(a)suse.com |kernel-bugs(a)opensuse.org --- Comment #1 from Johannes Meixner <jsmeix(a)suse.com> --- I reassign this issue from "Printing" to "Kernel" so kernel people could have a look here because I cannot debug kernel related issues (I know nothing about kernel internals). I assume that the root cause of this kernel panic is not in the CUPS software. I think if there was a bug in the CUPS software that causes a kernel panic, we would have got many such issue reports but (at least for now) this is the only one. The last code change in the openSUSE CUPS RPMs is from Mon Sep 30 2024 (RPM changelog entry date), the CUPS "Version upgrade to 2.4.11" which was submitted to openSUSE:Factory on 2024-10-01, see https://build.opensuse.org/request/show/1204788 My blind guess of the root cause of this kernel panic is some specific hardware, in particular pluggable hardware, like USB devices and things like that. Alex Ustinov, I would try out if the kernel panic goes away when you unplug as many hardware as possible (e.g. all external hardware from your laptop) and retry "lpinfo -v". When "lpinfo -v" runs it calls each CUPS backend in /usr/lib/cups/backend/ to let each CUPS backend report the printing devices which are autodetected by each CUPS backend. So you may try out if it helps to move away CUPS backends from /usr/lib/cups/backend/ to find out if a particular CUPS backend triggers this kernel panic which may indicate where the actual root cause is. But first and foremost you should do some basic system integrity checks: Verify that the dependencies of all installed packages are satisfied as 'root' via # zypper verify --dry-run which results for example on my system -------------------------------------------------------- # zypper verify --dry-run Loading repository data... Reading installed packages... Dependencies of all installed packages are satisfied. -------------------------------------------------------- or as needed with more detailed output via # zypper verify --dry-run --details Also verify that your installed RPM files are OK, in particular your installed "cups" related things as 'root' via # rpm -V $( rpm -qa | grep cups ) or even verify all your installed RPM files via # rpm -Va (may result a long list - perhaps too long to be useful). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1213761] No space left on device, during btrfs snapshot due ssd_spread option
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213761 https://bugzilla.suse.com/show_bug.cgi?id=1213761#c8 --- Comment #8 from Wenruo Qu <wqu(a)suse.com> --- The reproducer has nothing special, and it relies on a specific btrfs out of the script, so it's not really a helpful reproducer. And since the reproducer is not that useful, we can only rely on the extra info you can gather to debug, including the following output when the ENOSPC error is hit: # btrfs fi df /loopfs # btrfs fi usage /loopfs -- You are receiving this mail because: You are the assignee for the bug.

1 0