May 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1198552] systemd-udevd: USB devices fails to probe. Cant suspend/reboot/shutdown
by bugzilla_noreply＠suse.com 17 May '22

17 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1198552 https://bugzilla.suse.com/show_bug.cgi?id=1198552#c12 Oliver Neukum <oneukum(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Flags| |needinfo?(matias.nicolas.zc | |(a)gmail.com) --- Comment #12 from Oliver Neukum <oneukum(a)suse.com> --- (In reply to Mat�as Z��iga from comment #11) > - if booted with 'usbcore.autosuspend=-1' (and no ac-adapter), udev tasks > cannot be terminated either, but now the HC dies and I can run lsusb (though > it doesn't show the devices) Does the HC die if you boot _with_ an ac-adapter and 'usbcore.autosuspend=-1'? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199593] New: kexec performs full reboot since kexec-tools 2.0.22-2.2
by bugzilla_noreply＠suse.com 16 May '22

16 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199593 Bug ID: 1199593 Summary: kexec performs full reboot since kexec-tools 2.0.22-2.2 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: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since version 2.0.22-2.2 (which appeared in snapshot 20220510) "kexec -e" does full firmware reboot. This is 100% reproducible 1. Install snapshot 20220509 via TW history 2. Install single RPM kexec-tools-2.0.22-2.2 3. kexec stops working 4. Revert back to kexec-tools-2.0.22-2.1 5. kexec works again Because installing the latest kexec-tools from Kernel:kdump in Leap 15.3 still works and snapshot 20220510 was full rebuild with gcc12, my best guess is that gcc12 miscompiles something. kexec remains broken so far also with different kernels (including kernels built with previous compilers). See also https://forums.opensuse.org/showthread.php/569924-Kexec-has-stoppped-working -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1198552] systemd-udevd: USB devices fails to probe. Cant suspend/reboot/shutdown
by bugzilla_noreply＠suse.com 16 May '22

16 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1198552 http://bugzilla.opensuse.org/show_bug.cgi?id=1198552#c11 Mat�as Z��iga <matias.nicolas.zc(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #858871|0 |1 is obsolete| | Flags|needinfo?(matias.nicolas.zc | |(a)gmail.com) | --- Comment #11 from Mat�as Z��iga <matias.nicolas.zc(a)gmail.com> --- Created attachment 858947 --> http://bugzilla.opensuse.org/attachment.cgi?id=858947&action=edit dmesg 5.17 The testcases of attachment 858871 (dmesg 5.17) and attachment 858872 (dmesg usbcore.autosuspend=-1) are the same already: boot the machine with no ac-adapter connected. The only difference between them is the 'usbcore.autosuspend=-1' param. I did not blacklist 'uvc', since I don't know if 'blacklist=uvc brokenmodules=uvc' does anything (i did a test with it, and saw no differences). Attached is an updated dmesg, with no command line modifications. The behaviour is consistent between multiple boots: - if booted with no command line (and no ac-adapter), udev tasks cannot be terminated, and lsusb freezes - if booted with 'usbcore.autosuspend=-1' (and no ac-adapter), udev tasks cannot be terminated either, but now the HC dies and I can run lsusb (though it doesn't show the devices) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199355] aarch64 oopses on raspberry pi4 KVM host (OBS worker)
by bugzilla_noreply＠suse.com 16 May '22

16 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1199355 https://bugzilla.suse.com/show_bug.cgi?id=1199355#c17 --- Comment #17 from Anthony Iliopoulos <ailiopoulos(a)suse.com> --- (In reply to Stefan Seyfried from comment #16) > unfortunately, the whole build.opensuse.org does not supply anything newer > than 7.3.0 and the amount of patches in the package does not encourage me to > try and update it ;-) I actually built it from source (from git master). Looking at the osc package it seems that some of those patches are backports, so I think we can just the package maintainer to update it to the latest stable release. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1198552] systemd-udevd: USB devices fails to probe. Cant suspend/reboot/shutdown
by bugzilla_noreply＠suse.com 16 May '22

16 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1198552 https://bugzilla.suse.com/show_bug.cgi?id=1198552#c10 Oliver Neukum <oneukum(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(matias.nicolas.zc | |(a)gmail.com) --- Comment #10 from Oliver Neukum <oneukum(a)suse.com> --- (In reply to Mat�as Z��iga from comment #9) ssages. > > Attached is the 'usbcore.autosuspend=-1' dmesg with the same 5.17.5 kernel. > The xhci_hcd/usb messages are at the end. Wait. In this case your HC dies. In the other dmesg logs that is not the case. Please redo that test without the modification to the kernel command line and attach dmesg. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199355] aarch64 oopses on raspberry pi4 KVM host (OBS worker)
by bugzilla_noreply＠suse.com 16 May '22

16 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1199355 https://bugzilla.suse.com/show_bug.cgi?id=1199355#c15 --- Comment #15 from Anthony Iliopoulos <ailiopoulos(a)suse.com> --- I'm getting the same issues with crash v7.3.0 but I've managed to get it fully working with crash v8.0.1. There have been several commits for arm64 that fix those issues. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189283] kernel-obs-build needs af_alg
by bugzilla_noreply＠suse.com 16 May '22

16 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1189283 http://bugzilla.opensuse.org/show_bug.cgi?id=1189283#c5 --- Comment #5 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1189283) was mentioned in https://build.opensuse.org/request/show/977461 Factory / gnutls -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199355] aarch64 oopses on raspberry pi4 KVM host (OBS worker)
by bugzilla_noreply＠suse.com 16 May '22

16 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1199355 https://bugzilla.suse.com/show_bug.cgi?id=1199355#c12 --- Comment #12 from Anthony Iliopoulos <ailiopoulos(a)suse.com> --- (In reply to Stefan Seyfried from comment #11) > I now have a crash but no way to load it: > > raspi4c:/var/crash/2022-05-16-10:14 # crash Image-5.17.5-1-default vmcore > > crash 7.3.0 > Copyright (C) 2002-2021 Red Hat, Inc. > Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation > Copyright (C) 1999-2006 Hewlett-Packard Co > Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited > Copyright (C) 2006, 2007 VA Linux Systems Japan K.K. > Copyright (C) 2005, 2011, 2020-2021 NEC Corporation > Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc. > Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc. > This program is free software, covered by the GNU General Public License, > and you are welcome to change it and/or distribute copies of it under > certain conditions. Enter "help copying" to see the conditions. > This program has absolutely no warranty. Enter "help warranty" for details. > > crash: Image-5.17.5-1-default: not a supported file format > > Usage: > > crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form) > crash [OPTION]... [NAMELIST] (live system form) > > Enter "crash -h" for details. > > > Please advise :-( I only used crash on x86_64 before. You should have a /boot/vmlinux-5.17.5-1-default.gz that can be used as the image, please try with that. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199122] amdgpu intermittent brightness issue pops up again
by bugzilla_noreply＠suse.com 16 May '22

16 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199122 http://bugzilla.opensuse.org/show_bug.cgi?id=1199122#c13 --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- Then try to remove those and reboot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199425] Undefined status of process hangs in system, causing other processes to hang too
by bugzilla_noreply＠suse.com 16 May '22

16 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1199425 https://bugzilla.suse.com/show_bug.cgi?id=1199425#c2 --- Comment #2 from Freek de Kruijf <freek(a)opensuse.org> --- (In reply to Matthias Brugger from comment #1) > Hi Freek, > > I think the first thing we have to find out is, where the process is stuck, > I can see that it is in uninterruptible sleep state. > Do I understand correctly that you don't use any rpm for the SBFspot but the > source code from [1]? Indeed. I use the file V3.9.4.tar.gz, and compile it from source. A few days ago a new version of boost, 78->79, became available and I needed to build SBFspot with the new version. I manage two of these systems, which I try to keep the same. > Could you connect to the process via GDB and provide the traceback where the > process got stuck? I have currently access to only one of the systems, which runs OK since yesterday. I am waiting for remote access to the other one; this one still needs the update to boost79. I installed gdb, but I did not use it before. Will look in the manual to find out how to make a traceback of a stuck process. I assume this is not the one that has been killed and is left in that strange status, but the one that gets stuck after that. > > Apart from that, just in case, can you provide the kernel version you are > running on? smahp:~ # uname -a Linux smahp 5.17.5-1-lpae #1 SMP Thu May 5 10:06:09 UTC 2022 (e57ab05) armv7l armv7l armv7l GNU/Linux > > [1] https://github.com/SBFspot/SBFspot/ So it may take some time to report any result. -- You are receiving this mail because: You are the assignee for the bug.

1 0