November 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1205603] New: bpf lsm enabled but not included in LSM list
by bugzilla_noreply＠suse.com 17 Apr '23

17 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1205603 Bug ID: 1205603 Summary: bpf lsm enabled but not included in LSM list 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: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- During my system upgrades i noticed the following message: ```systemd[1]: bpf-lsm: BPF LSM hook not enabled in the kernel, BPF LSM not supported``` but we have: ```CONFIG_BPF_LSM=y``` i asked Frank Bui what it checks for. it checks for the string "bpf" in this list: ``` cat /sys/kernel/security/lsm lockdown,capability,apparmor ``` it seems ```CONFIG_LSM="integrity,apparmor"``` needs an update. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1188954] New: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1
by bugzilla_noreply＠suse.com 14 Apr '23

14 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1188954 Bug ID: 1188954 Summary: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1 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: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: sndirsch(a)suse.com Found By: --- Blocker: --- Created attachment 851460 --> http://bugzilla.opensuse.org/attachment.cgi?id=851460&action=edit Xorg.0.log and dmesg Initial summary: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1 To reproduce: 1-boot with included on kernel cmdline radeon.cik_support=0 amdgpu.cik_support=1 2-wait for X to fail to start 3-login on a tty 4-systemctl restart xdm Actual behavior: 1-X fails to start, finding no /dev/dri/card0, leaving login prompt on tty1 on display screen 2-X starts normally using amdgpu DDX driver Expected behavior: 1-X starts normally using amdgpu DDX driver Tested with kernels 5.12.13, 5.11.16, 5.7.11 # inxi -SGIay System: Host: asa88 Kernel: 5.12.13-1-default x86_64 bits: 64 compiler: gcc v: 11.1.1 parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=tvgp07stw noresume ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 radeon.cik_support=0 amdgpu.cik_support=1 video=1024x768@60 video=1440x900@60 drm.debug=0x1e log_buf_len=1M Console: tty pts/0 DM: TDM Distro: openSUSE Tumbleweed 20210730 Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASUSTeK driver: amdgpu v: kernel alternate: radeon bus-ID: 00:01.0 chip-ID: 1002:130f class-ID: 0300 Display: server: X.org 1.20.12 driver: loaded: vesa unloaded: fbdev,modesetting alternate: ati Message: Advanced graphics data unavailable for root. Info:...inxi: 3.3.06 Comments: 1-without radeon.cik_support=0 amdgpu.cik_support=1 on cmdline, X cannot be coaxed into using amdgpu DDX driver via /etc/X11/xorg.conf.d/*conf 2-without radeon.cik_support=0 amdgpu.cik_support=1, greeter startup completes (normally, on first try) using modesetting DIX driver -- You are receiving this mail because: You are the assignee for the bug.

1 27

[Bug 1191924] New: kernel-source.git/README outdated
by bugzilla_noreply＠suse.com 10 Apr '23

10 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1191924 Bug ID: 1191924 Summary: kernel-source.git/README outdated 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: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There is a section "Before You Commit -- Things To Check" in kernel-source.git/README, it will likely not work out of the box. According to rpm/kernel-binary.spec.in, at least three more packages beside the obvious gcc/make/patch need to be installed: BuildRequires: libopenssl-devel BuildRequires: libelf-devel BuildRequires: dwarves >= 1.21 Furthermore rapidquilt is not mentioned. It is not strictly required, but one can hardly live without it. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1202353] New: kernel: replace mkinitrd wrapper with native dracut
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1202353 Bug ID: 1202353 Summary: kernel: replace mkinitrd wrapper with native dracut 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: antonio.feijoo(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1202351 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1202351 +++ Upstream support removed in March 2021 (https://github.com/dracutdevs/dracut/commit/43df4ee2) and deprecation announcement on factory mailing list in May 2021 (https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/…) ALP will not ship the mkinitrd wrapper, so it's better to get rid of it in Tumbleweed first. Affected packages that need to be updated before (at least): # zypper se --requires mkinitrd Loading repository data... Reading installed packages... S | Name | Summary | Type ---+---------------------+----------------------------------------------------+-------- | kernel-debug | A Debug Version of the Kernel | package i+ | kernel-default | The Standard Kernel | package | kernel-default-base | The Standard Kernel - base modules | package | kernel-kvmsmall | The Small Developer Kernel for KVM | package | kernel-pae | Kernel with PAE Support | package | kernel-vanilla | The Standard Kernel - without any SUSE patches | package i | mdadm | Utility for configuring "MD" software RAID devices | package -- You are receiving this mail because: You are the assignee for the bug.

1 39

[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 1189826] New: Severe screen flickering with kernel 5.13.12-1-default and i915
by bugzilla_noreply＠suse.com 12 Mar '23

12 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1189826 Bug ID: 1189826 Summary: Severe screen flickering with kernel 5.13.12-1-default and i915 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: javier(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- My laptop's screen flickers so much with 5.13.12 that it renders my laptop unusable. One workaround is to close and open the lid. After resuming, it works fine - there is no flickering. Booting up from the KDE Live image works fine. I have used the same Tumbleweed version (20210820) as the one I have installed on my laptop. The only difference is that I have an encrypted /home partition on my laptop's SSD. Tested kernels: 5.10.16-1.3: OK 5.11.4-1.3: NON-OK 5.12.12-1: NON-OK 5.13.12-1: NON-OK KDE Plasma 5.22.4 KDE Frameworks 5.85.0 Qt 5.15.2 See the attachments for more details. -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 1189283] New: kernel-obs-build needs af_alg
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1189283 Bug ID: 1189283 Summary: kernel-obs-build needs af_alg 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: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- libkcapi got updated to 1.3.1 (https://build.opensuse.org/request/show/910806) and apparently gnutls picks that up now and enables support for it. It seems like that depends on AF_ALG sockets though, which are currently not enabled in kernel-obs-build (missing af_alg module), so various builds (libzip, libvirt) fail with libkcapi - Error: AF_ALG: socket syscall failed (errno: -97) I'm not sure whether just af_alg is enough, it might need some other modules as well. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1202570] New: steam deck - echo freeze | tee -a /sys/powerstate glitches the screen
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202570 Bug ID: 1202570 Summary: steam deck - echo freeze | tee -a /sys/powerstate glitches the screen Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Suspend seems to work in the latest kernel in kernel:HEAD repo. Software suspends seems to glitch the screen upon re-initialization. Wifi and changing to tty works. lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20220817 Codename: n/a zypper info kernel-default Loading repository data... Reading installed packages... Information for package kernel-default: --------------------------------------- Repository : kernel-repo Name : kernel-default Version : 6.0~rc1-3.1.g7bd57d5 Arch : x86_64 Vendor : obs://build.opensuse.org/Kernel Installed Size : 273.3 MiB Installed : Yes Status : up-to-date Source package : kernel-default-6.0~rc1-3.1.g7bd57d5.nosrc Upstream URL : https://www.kernel.org/ Summary : The Standard Kernel Description : The standard kernel for both uniprocessor and multiprocessor systems. Source Timestamp: 2022-08-16 07:58:42 +0000 GIT Revision: 7bd57d59ba8c141be35bb5189487a899d04e76ec GIT Branch: master -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1202566] New: Steam deck wakes up from hibernate with max brightness
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202566 Bug ID: 1202566 Summary: Steam deck wakes up from hibernate with max brightness Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- echo 0x1e | sudo tee -a /sys/module/drm/parameters/debug [sudo] password for root: 0x1e -> echo disk | sudo tee -a /sys/power/state disk ~> dmesg > dmesg-suspend-from-disk-with-0x1e-enabled lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20220817 Codename: n/a Linux steamdeck 6.0.0-rc1-1.gd997b88-default #1 SMP PREEMPT_DYNAMIC Thu Aug 18 14:44:01 UTC 2022 (d997b88) x86_64 x86_64 x86_64 GNU/Linux https://build.opensuse.org/project/show/home:tiwai:bsc1201418 -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1188352] New: Can't enter LUKS password since kernel 5.13 on Pinebook Pro
by bugzilla_noreply＠suse.com 28 Jan '23

28 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1188352 Bug ID: 1188352 Summary: Can't enter LUKS password since kernel 5.13 on Pinebook Pro Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jonasdcdm(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 851029 --> http://bugzilla.opensuse.org/attachment.cgi?id=851029&action=edit dmesg Since the upgrade to kernel 5.13 it's no longer possible to enter the LUKS password on boot. The physical keyboard works fine in GRUB, but the LUKS prompt won't see it, it doesn't register any key press. Entering the password via serial console works, and the Pinebook Pro boots to the desktop, where the physical keyboard works again. Kernel 5.12.13-1 is still working fine. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1201121] New: kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash
by bugzilla_noreply＠suse.com 28 Jan '23

28 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1201121 Bug ID: 1201121 Summary: kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with the Tumbleweed snapshot installed on June 7th I get kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash in my journal on every boot. Running fwupdmgr I get fwupd[6102]: 12:26:06:0015 FuPluginDfu truncated DFU interface data, no bcdDFUVersion The daemon nevertheless is starting. Because there is no newer firmware for any of my devices I am not able to test, if an update would work despite these error messages. This is a XPS 13 9310 2-in-1/0NVVG0, BIOS 2.8.1 02/25/2022. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1198722] New: initialize useful compiled in LSMs by default
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1198722 Bug ID: 1198722 Summary: initialize useful compiled in LSMs by default 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently CONFIG_LSM is very minimal, not even listing the LSMs that we compile into the kernel, which requires manual fixing on kernel boot cmdline using the "lsm=" parameter. we can enable these * landlock: optional ability for user land applications to sandbox themselves * yama: optional restrict of use of ptrace for nonprivileged users * bpf: create eBPF based LSMs dynamically bpf was enabled earlier already, but reverted due to bsc#1197746 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1196048] New: audit file watches do not really work?
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1196048 Bug ID: 1196048 Summary: audit file watches do not really work? 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: meissner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- auditctl -e 1 auditctl -w /etc/issue if i do echo hallo >> /etc/issue -> not audited if i do vim /etc/issue ... remove hallo line and save ... -> audited cat /etc/issue -> not audited Not sure if I am doing it right. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1194268] New: disable btrfs asserts in default kernels
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1194268 Bug ID: 1194268 Summary: disable btrfs asserts in default kernels 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- while chasing for I/O performance issues in virtualized environments (usecase Open Build Service package builds for example), I noticed that btrfs in our default kernel has asserts enabled. according to the Kconfig help setting, this setting is purely for development purposes. I suggested to move the setting CONFIG_BTRFS_ASSERT only into the debug flavors, however there was concerns that this affects finding memory corruptions and other hardware related issues. On the other side, in my brief testing it appeared disabling reduced code size noticeably (in dual-digit percentage range) and also improved IOPS on a FIO randrw test (on a cow file) by over 20%. I will replicate the tests to be sure. This bug is to track how to address the issue and making asserts purely developer only and disable them in production builds of the openSUSE distribution. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1195297] New: fbtft spi screens no longer functions properly.
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1195297 Bug ID: 1195297 Summary: fbtft spi screens no longer functions properly. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: simonf.lees(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Connected to the raspberry pi on my Robot I have a small 3.2" display [1] (or a clone / older version) it connects via SPI on the raspberry pi's GPIO header. In the past i've had it working with the overlay at [2] and the fbtft driver. This kinda setup is pretty common in the embedded / hobbyist world, I don't use a desktop or anything just simple status apps using the framebuffer directly on the other hand it wouldn't be the end of the world if I moved to Qt. Today I finally got a chance to update and as of now I no longer have an /dev/fb1 (/dev/fb0 is hdmi) is that expected with my current setup? I had other issues with the update and had to grab a fresh image and re add my overlay and raspbery pi config so there is also a chance I missed something setting it up again. I've put some dmesg output from the older system the new system shows nothing and below that is an fbi command I use for testing. Log from previously working system: [ 59.468595] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 59.714749] fb_ili9340: module is from the staging directory, the quality is unknown, you have been warned. [ 59.716023] fb_ili9340 spi0.0: fbtft_property_value: buswidth = 8 [ 59.716049] fb_ili9340 spi0.0: fbtft_property_value: debug = 0 [ 59.716063] fb_ili9340 spi0.0: fbtft_property_value: rotate = 270 [ 59.716079] fb_ili9340 spi0.0: fbtft_property_value: fps = 25 [ 59.716093] fb_ili9340 spi0.0: fbtft_property_value: txbuflen = 32768 [ 61.352903] graphics fb1: fb_ili9340 frame buffer, 320x240, 150 KiB video memory, 32 KiB buffer memory, fps=25, spi0.0 at 16 MHz Test command: sudo fbi -T 13 -d /dev/fb1 --noverbose 1-110313112A3.jpg 1. https://www.waveshare.com/wiki/3.2inch_RPi_LCD_(B) 2. https://github.com/swkim01/waveshare-dtoverlays -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1179894] New: warnings in OBS builds from kernel+initrd about "Warning: running kernel does not support fscaps"
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1179894 Bug ID: 1179894 Summary: warnings in OBS builds from kernel+initrd about "Warning: running kernel does not support fscaps" 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: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fvogt(a)suse.com, jslaby(a)suse.com, msuchanek(a)suse.com, okurz(a)suse.com, thomas.blume(a)suse.com, tiwai(a)suse.com Depends on: 1178401 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1178401 +++ ## Observation https://build.opensuse.org/build/openSUSE:Factory/images/local/000product:o… shows repeated warnings about: ``` [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps ``` ## Steps to reproduce Seemingly reproducible in any build of packages, e.g. https://build.opensuse.org/public/build/openSUSE:Factory/standard/x86_64/00… shows the same ## Expected result Only errors and warnings in the log that I as package/project maintainer can fix -- You are receiving this mail because: You are the assignee for the bug.

1 6

[kernel-bugs] [Bug 1178463] New: Flood of "usb usb{2,6}-port1: Cannot enable." messages
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1178463 Bug ID: 1178463 Summary: Flood of "usb usb{2,6}-port1: Cannot enable." messages 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: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 843325 --> https://bugzilla.suse.com/attachment.cgi?id=843325&action=edit lsusb -vv With the 5.10.0rc2 kernel from Kernel:HEAD, I'm experiencing a flood of: ... [ 372.567942] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 374.686509] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 377.026495] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 378.986503] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 381.446415] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 383.290504] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 385.918496] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 387.586478] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 390.386475] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 391.894454] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? ... The XPS 13 is connected to a Belkin Thunberbird dock. As far as I can tell, except for these messages, all USB connected peripherals (keyboard, mouse, webcam) are working. Attaching lsusb -vv and dmesg output. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1188487] New: BUG: workqueue lockup
by bugzilla_noreply＠suse.com 26 Jan '23

26 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188487 Bug ID: 1188487 Summary: BUG: workqueue lockup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: tdevries(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I started seeing this bug on my tumbleweed system: ... 2021-07-07T16:24:41.803560+02:00 lena kernel: [1053710.804959] CPU: 3 PID: 31988 Comm: gdb Tainted: G D 5.12.10-1-default #1 openSUSE Tumbleweed Message from syslogd@lena at Jul 19 16:18:29 ... kernel:[722585.589404] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for inted: G D 5.12.10-1-default #1 openSUSE Tumbleweed 2021-07-07T16:24:41.803561+02:00 lena kernel: [1053710.804964] Hardware name: LENOVO 20F5S0KF00/20F5S0KF00, BIOS R02ET73W (1.46 ) 01/08/2020 2021-07-07T16:24:41.803563+02:00 lena kernel: [1053710.804966] Call Trace: 2021-07-07T16:24:41.803564+02:00 lena kernel: [1053710.804971] dump_stack+0x76/0x94 2021-07-07T16:24:41.803566+02:00 lena kernel: [1053710.804978] bad_page.cold+0x9b/0xa0 2021-07-07T16:24:41.803567+02:00 lena kernel: [1053710.804983] get_page_from_freelist+0x739/0x13a0 2021-07-07T16:24:41.803568+02:00 lena kernel: [1053710.804990] __alloc_pages_nodemask+0x161/0x310 2021-07-07T16:24:41.803569+02:00 lena kernel: [1053710.804993] pagecache_get_page+0x14c/0x4f0 2021-07-07T16:24:41.803570+02:00 lena kernel: [1053710.805000] grab_cache_page_write_begin+0 7-07T16:24:41.803572+02:00 lena kernel: [1053710.805009] iomap_write_actor+0x9f/0x1a0 2021-07-07T16:24:41.803573+02:00 lena kernel: [1053710.805013] iomap_apply+0x111/0x2e0 2021-07-07T16:24:41.803575+02:00 lena kernel: [1053710.805015] ? iomap_write_end+0x260/0x260 2021-07-07T16:24:41.803576+02:00 lena kernel: [1053710.805020] iomap_file_buffered_write+0x5c/0x80 2021-07-07T16:24:41.803577+02:00 lena kernel: [1053710.805023] ? iomap_write_end+0x260/0x260 2021-07-07T16:24:41.803578+02:00 lena kernel: [1053710.805026] xfs_file_buffered_write+0xbd/0x2b0 [xfs] 2021-07-07T16:24:41.803579+02:00 lena kernel: [1053710.805122] ? _flat_send_IPI_mask+0x21/0x40 2021-07-07T16:24:41.803580+02:00 lena kernel: [1053710.805128] ? generic_exec_single+0x50/0xc0 2021-07-07T16:24:41.803582+02:00 lena kernel: [1053710.805133] ? smp_call_function_single_async+0x17/0x20 2021-07-07T16:24:41.803583+02:00 lena kernel: [1053710.805138] new_sync_write+0x11c/0x1b0 2021-07-07T16:24:41.803583+02:00 lena kernel: [1053710.805143] vfs_write+0x1b8/0x270 2021-07-07T16:24:41.803585+02:00 lena kernel: [1053710.805146] ksys_write+0x5f/0xe0 2021-07-07T16:24:41.803586+02:00 lena kernel: [1053710.805150] do_syscall_64+0x33/0x80 2021-07-07T16:24:41.803587+02:00 lena kernel: [1053710.805155] entry_SYSCALL_64_after_hwframe+0x44/0xae 2021-07-07T16:24:41.803588+02:00 lena kernel: [1053710.805159] RIP: 0033:0x7fc4b3b4539f 2021-07-07T16:24:41.803589+02:00 lena kernel: [1053710.805162] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 b9 49 f9 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 0c 4a f9 ff 48 2021-07-07T16:24:41.803590+02:00 lena kernel: [1053710.805167] RSP: 002b:00007fff61dfb5f0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 2021-07-07T16:24:41.803592+02:00 lena kernel: [1053710.805171] RAX: ffffffffffffffda RBX: 0000000000001000 RCX: 00007fc4b3b4539f 2021-07-07T16:24:41.803592+02:00 lena kernel: [1053710.805174] RDX: 0000000000001000 RSI: 0000000001f9fe90 RDI: 000000000000000e 2021-07-07T16:24:41.803593+02:00 lena kernel: [1053710.805177] RBP: 0000000001f9fe90 R08: 0000000000000000 R09: 00007fff61dfbb30 2021-07-07T16:24:41.803594+02:00 lena kernel: [1053710.805180] R10: 0000000001a44440 R11: 0000000000000293 R12: 0000000000001000 2021-07-07T16:24:41.803596+02:00 lena kernel: [1053710.805182] R13: 00000000018442a0 R14: 0000000000001000 R15: 00007fc4b3c18700 ... This is with kernel: ... $ uname -a Linux lena 5.12.13-1-default #1 SMP Mon Jun 28 06:37:23 UTC 2021 (74bd8c0) x86_64 x86_64 x86_64 GNU/Linux ... It happens during a build and test run of gdb. I've updated and rebooted to kernel version 5.13.0-1-default, but ran into the same bug. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1193931] New: unexpectedly, the system freezes very much
by bugzilla_noreply＠suse.com 26 Jan '23

26 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1193931 Bug ID: 1193931 Summary: unexpectedly, the system freezes very much 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: suse(a)rop.cx QA Contact: qa-bugs(a)suse.de Group: novellonly, SUSE Security Internal Found By: --- Blocker: --- Created attachment 854712 --> https://bugzilla.suse.com/attachment.cgi?id=854712&action=edit full dmesg usually nothing works and only sometimes works very slowly for a few seconds, but the cursor is working properly, usually without delay -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1192623] New: ltp_nfs FCNTL_LOCKTESTS test causes stack trace in dmesg
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1192623 Bug ID: 1192623 Summary: ltp_nfs FCNTL_LOCKTESTS test causes stack trace in dmesg 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tumbleweed Build 20211110 kernel 5.14.14-2-default (2b5383f) (but it might have been failing in 5.13 and older kernels) https://openqa.opensuse.org/tests/2029105/file/serial0.txt Prints really long stack trace, which begins: [ 5211.445898][ C0] sysrq: Show State [ 5211.446508][ C0] task:systemd state:S stack: 0 pid: 1 ppid: 0 flags:0x00000000 [ 5211.447686][ C0] Call Trace: [ 5211.448216][ C0] __schedule+0x325/0x1530 [ 5211.448874][ C0] ? kmem_cache_alloc+0x151/0x480 [ 5211.449593][ C0] schedule+0x44/0xa0 [ 5211.450202][ C0] schedule_hrtimeout_range_clock+0x10b/0x120 [ 5211.451077][ C0] ? kfree+0xba/0x3c0 [ 5211.451934][ C0] ? sock_poll+0x4f/0xe0 [ 5211.452914][ C0] ? ep_done_scan+0xa7/0xf0 [ 5211.453723][ C0] do_epoll_wait+0x542/0x700 [ 5211.454594][ C0] ? wait_woken+0x70/0x70 [ 5211.455511][ C0] __x64_sys_epoll_wait+0x60/0x100 [ 5211.456475][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.457467][ C0] do_syscall_64+0x5c/0x80 [ 5211.458342][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.459302][ C0] ? do_syscall_64+0x69/0x80 [ 5211.460048][ C0] ? ksys_read+0x5f/0xe0 [ 5211.460755][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.461615][ C0] ? do_syscall_64+0x69/0x80 [ 5211.462361][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.463276][ C0] ? do_syscall_64+0x69/0x80 [ 5211.464043][ C0] ? exc_page_fault+0x68/0x130 [ 5211.464821][ C0] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 5211.465736][ C0] RIP: 0033:0x7fe070700c1e [ 5211.466480][ C0] RSP: 002b:00007ffc484b5ed0 EFLAGS: 00000293 ORIG_RAX: 00000000000000e8 [ 5211.467713][ C0] RAX: ffffffffffffffda RBX: 0000562627698e40 RCX: 00007fe070700c1e [ 5211.468853][ C0] RDX: 00000000000000ae RSI: 000056262788a3e0 RDI: 0000000000000004 [ 5211.469999][ C0] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000006 [ 5211.471147][ C0] R10: 00000000ffffffff R11: 0000000000000293 R12: 0000000000000352 [ 5211.472315][ C0] R13: 00000000000000ae R14: 0000000000000055 R15: 0000562627698fd0 [ 5211.473472][ C0] task:kthreadd state:S stack: 0 pid: 2 ppid: 0 flags:0x00004000 [ 5211.474773][ C0] Call Trace: [ 5211.475449][ C0] __schedule+0x325/0x1530 [ 5211.476249][ C0] ? kernel_thread+0x55/0x70 [ 5211.477068][ C0] schedule+0x44/0xa0 [ 5211.477836][ C0] kthreadd+0x2c0/0x2e0 [ 5211.478647][ C0] ? kthread_is_per_cpu+0x30/0x30 [ 5211.479670][ C0] ret_from_fork+0x22/0x30 [ 5211.480495][ C0] task:rcu_gp state:I stack: 0 pid: 3 ppid: 2 flags:0x00004000 -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1192624] New: ltp_nfs nfs05 (NFS stress test with make) fails
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1192624 Bug ID: 1192624 Summary: ltp_nfs nfs05 (NFS stress test with make) fails 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tumbleweed Build 20211110 kernel 5.14.14-2-default (2b5383f) [1] (but it might have been failing in 5.13 and older kernels) fails to run all nfs*_05 tests which run shell script nfs05 [2] which runs nfs05_make_tree.c [3] (NFS stress test with make). Test output: # nfs05 -v 4 -t tcp; echo "### TEST nfs4_05 COMPLETE >>> $?" nfs05 1 TINFO: timeout per run is 0h 5m 0s nfs05 1 TINFO: setup NFSv4, socket type tcp nfs05 1 TINFO: Mounting NFS: mount -v -t nfs -o proto=tcp,vers=4 10.0.0.2:/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp /tmp/LTP_nfs05.G8q7DLN0j0/4/0 nfs05 1 TINFO: start nfs05_make_tree -d 20 -f 50 -t 8 tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s Test timed out, sending SIGTERM! If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 Terminated nfs05 1 TBROK: test terminated nfs05 1 TINFO: Cleaning up testcase umount.nfs4: /tmp/LTP_nfs05.G8q7DLN0j0/4/0: device is busy Test is still running... 10 Test is still running... 9 Test is still running... 8 make[6]: *** No rule to make target '26445.6.20.c', needed by '26445.6.20'. Stop. make[5]: *** [makefile:9: dir] Error 2 make[4]: *** [makefile:9: dir] Error 2 make[3]: *** [makefile:9: dir] Error 2 make[2]: *** [makefile:9: dir] Error 2 make[1]: *** [makefile:9: dir] Error 2 make: *** [makefile:9: dir] Error 2 tst_cmd.c:109: TBROK: 'make' exited with a non-zero code 2 at tst_cmd.c:109 Test is still running... 7 ... make: *** [makefile:9: dir] Error 2 Test is still running... 1 rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26445/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26446/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26447/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26448/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26449/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26450/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26452/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26451/dir/dir/dir/dir/dir/dir': Directory not empty make[6]: *** No rule to make target '26451.6.46.c', needed by '26451.6.46'. Stop. make[5]: *** [makefile:9: dir] Error 2 make[4]: *** [makefile:9: dir] Error 2 make[3]: *** [makefile:9: dir] Error 2 make[2]: *** [makefile:9: dir] Error 2 make[1]: *** [makefile:9: dir] Error 2 make: *** [makefile:9: dir] Error 2 rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/0': Device or resource busy rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/0': Is a directory There is probably no stack trace in dmesg related to this test (in attached dmesg there is really long Call Trace related to FCNTL_LOCKTESTS reported in #1192623). [1] https://openqa.opensuse.org/tests/2029105 [2] https://github.com/linux-test-project/ltp/blob/master/testcases/network/nfs… [3] https://github.com/linux-test-project/ltp/blob/master/testcases/network/nfs… -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kernel-bugs] [Bug 1176026] New: bond interface should not invent mac address by default
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1176026 Bug ID: 1176026 Summary: bond interface should not invent mac address by default 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: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- since 5.8.4 (unsure about last digit): when setting up a bond if kernel chooses a random mac removing and readding the slave gets back to the used behaviour: obs-arm-1:~ # modprobe bonding 3: enP2p1s0v1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 1c:1b:0d:60:ee:8b brd ff:ff:ff:ff:ff:ff 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 9e:29:55:da:aa:0e brd ff:ff:ff:ff:ff:ff obs-arm-1:~ # echo +enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 9e:29:55:da:aa:0e brd ff:ff:ff:ff:ff:ff obs-arm-1:~ # echo -enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves obs-arm-1:~ # echo +enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 1c:1b:0d:60:ee:8b brd ff:ff:ff:ff:ff:ff -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1193417] New: using a Bluetooth keyboard slows down going to sleep for a few seconds
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1193417 Bug ID: 1193417 Summary: using a Bluetooth keyboard slows down going to sleep for a few seconds 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: suse(a)rop.cx QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- when I have a Bluetooth keyboard connected and I press the switch to sleep mode, then at first the screen simply locks, stays in this state for about 4-6 seconds and only then goes to sleep mode Kernel logs: 06/12/2021 01:57 systemd-logind Power key pressed. 06/12/2021 01:57 dbus-daemon [session uid=1000 pid=1840] Activating service name='org.kde.LogoutPrompt' requested by ':1.13' (uid=1000 pid=1991 comm="/usr/bin/ksmserver ") 06/12/2021 01:57 dbus-daemon [session uid=1000 pid=1840] Successfully activated service 'org.kde.LogoutPrompt' 06/12/2021 01:57 NetworkManager <info> [1638745075.7552] manager: sleep: sleep requested (sleeping: no enabled: yes) 06/12/2021 01:57 ModemManager <info> [sleep-monitor] system is about to suspend 06/12/2021 01:57 kded5 bluedevil: About to suspend 06/12/2021 01:57 kded5 plasma-nm: Unhandled active connection state change: 3 06/12/2021 01:57 dbus-daemon [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=1166 comm="/usr/sbin/NetworkManager --no-daemon ") 06/12/2021 01:57 dbus-daemon [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.53' (uid=1000 pid=2018 comm="/usr/bin/plasmashell ") 06/12/2021 01:57 systemd Starting Network Manager Script Dispatcher Service... 06/12/2021 01:57 systemd Starting PackageKit Daemon... 06/12/2021 01:57 PackageKit daemon start 06/12/2021 01:57 dbus-daemon [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 06/12/2021 01:57 systemd Started Network Manager Script Dispatcher Service. 06/12/2021 01:57 kernel wlp0s20f3: deauthenticating from f8:f0:82:6d:a9:5a by local choice (Reason: 3=DEAUTH_LEAVING) 06/12/2021 01:57 dbus-daemon [system] Successfully activated service 'org.freedesktop.PackageKit' 06/12/2021 01:57 plasmashell plasma-pk-updates: Daemon changed 06/12/2021 01:57 kscreenlocker_greet Qt: Session management error: networkIdsList argument is NULL 06/12/2021 01:57 kded5 plasma-nm: Not emitting connection deactivated notification as we're about to suspend 06/12/2021 01:57 kded5 plasma-nm: Network connectivity limited, scheduling notification 06/12/2021 01:57 kscreenlocker_greet file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:47:9: Unable to assign [undefined] to bool 06/12/2021 01:57 systemd Reached target Sleep. 06/12/2021 01:57 systemd Starting System Suspend... 06/12/2021 01:57 kscreenlocker_greet file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:535: TypeError: Cannot read property 'longName' of undefined 06/12/2021 01:57 systemd-sleep INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend 06/12/2021 01:57 systemd-sleep Entering sleep state 'suspend'... 06/12/2021 01:57 kernel PM: suspend entry (s2idle) 06/12/2021 01:57 kernel Filesystems sync: 0.008 seconds 06/12/2021 01:57 kscreenlocker_greet qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for "en_GB" . Search paths ("/usr/share/qt5/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts") 06/12/2021 01:57 org_kde_powerdevil QObject::disconnect: Unexpected nullptr parameter 06/12/2021 01:57 org_kde_powerdevil QObject::disconnect: Unexpected nullptr parameter 06/12/2021 02:00 kernel Bluetooth: hci0: Timed out waiting for suspend events 06/12/2021 02:00 kernel Bluetooth: hci0: Suspend timeout bit: 6 06/12/2021 02:00 kernel Bluetooth: hci0: Suspend notifier action (3) failed: -110 06/12/2021 02:00 kernel Freezing user space processes ... (elapsed 0.003 seconds) done. 06/12/2021 02:00 kernel OOM killer disabled. 06/12/2021 02:00 kernel Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. 06/12/2021 02:00 kernel printk: Suspending console(s) (use no_console_suspend to debug) 06/12/2021 02:00 kernel ACPI: EC: interrupt blocked 06/12/2021 02:00 kernel ACPI: EC: interrupt unblocked 06/12/2021 02:00 kernel OOM killer enabled. 06/12/2021 02:00 kernel Restarting tasks ... 06/12/2021 02:00 kernel mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) 06/12/2021 02:00 bluetoothd Controller resume with wake event 0x0 06/12/2021 02:00 systemd-sleep System returned from sleep state. 06/12/2021 02:00 systemd Started Timeline of Snapper Snapshots. 06/12/2021 02:00 kernel done. 06/12/2021 02:00 kernel PM: suspend exit 06/12/2021 02:00 systemd-sleep INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend 06/12/2021 02:00 systemd systemd-suspend.service: Deactivated successfully. 06/12/2021 02:00 systemd Finished System Suspend. 06/12/2021 02:00 systemd Stopped target Sleep. 06/12/2021 02:00 systemd Reached target Suspend. 06/12/2021 02:00 systemd Stopped target Suspend. 06/12/2021 02:00 systemd-logind Operation 'sleep' finished. So, probably problem in: 06/12/2021 02:00 kernel Bluetooth: hci0: Timed out waiting for suspend events 06/12/2021 02:00 kernel Bluetooth: hci0: Suspend timeout bit: 6 06/12/2021 02:00 kernel Bluetooth: hci0: Suspend notifier action (3) failed: -110 (timed out) -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1190411] New: USB devices missing after kexec reboot with XHCI enabled
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1190411 Bug ID: 1190411 Summary: USB devices missing after kexec reboot with XHCI enabled 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: roger.whittaker(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852446 --> https://bugzilla.suse.com/attachment.cgi?id=852446&action=edit hwinfo, dmesg, usb-devices and lsusb with and without XHCI enabled in BIOS, normal boot and kexec boot Hardware is an Intel NUC (D54250WYK). With XHCI enabled in the UEFI BIOS, USB devices are not available after a kexec reboot. Hence the boot failed in the initrd when I had USB attached disks referenced in /etc/fstab. When I commented these out, the boot succeeded but the keyboard and mouse did not work after a kexec reboot. With XHCI disabled in the BIOS, kexec works as expected. On this hardware using Tumbleweed at some time in the past (but I'm afraid I don't know when) kexec worked with XHCI enabled. Linux jabberwock 5.14.0-1-default #1 SMP Mon Aug 30 07:01:36 UTC 2021 (dc06e24) x86_64 x86_64 x86_64 GNU/Linux NAME="openSUSE Tumbleweed" # VERSION="20210908" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20210908" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20210908" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo" -- You are receiving this mail because: You are the assignee for the bug.

1 23

[Bug 1190738] New: kernel-default-base does not contain kernel changelog
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1190738 Bug ID: 1190738 Summary: kernel-default-base does not contain kernel changelog 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: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jeos-internal(a)suse.de Found By: --- Blocker: --- kernel-default-base is built from a separate set of .spec and .changes files, making use of the kernel-subpackage facilities. This however means that the changelog of the original kernel packages (kernel-default, -vanilla, etc.) does not end up in the changelog of kernel-default-base. This is especially visible in updates, which only change the binary content and the version number in an unobvious way. There is no mention of any relevant fixed bugs (bsc#, CVE-). It would be very useful to include the kernel changelog in the kernel-default-base package. I don't think it can (or should) be interleaved with the subpackage .changes file, but it could be included as file. The target systems usually have excludedocs enabled though, so marking the file as %doc means it won't get installed. That makes it more complex and annoying... -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1188589] New: libbpf: failed to find valid kernel BTF
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188589 Bug ID: 1188589 Summary: libbpf: failed to find valid kernel BTF 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: mrostecki(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the update to the TW snapshot with the kernel 5.13.2-1, I see the following errors when trying to load BPF CO-RE skeletons with libbpf: libbpf: failed to find valid kernel BTF libbpf: Error loading vmlinux BTF: -3 The full example - I'm trying to load BPF programs which I have in this project: https://github.com/rancher-sandbox/lockc and the full output is: �� sudo ./out/lockcd libbpf: elf: skipping unrecognized data section(9) .rodata.str1.1 libbpf: failed to find valid kernel BTF libbpf: Error loading vmlinux BTF: -3 libbpf: failed to load object 'lockc_bpf' libbpf: failed to load BPF skeleton 'lockc_bpf': -3 Error: libbpf error Caused by: System error, errno: 3 Most likely, the solution for them would be setting the following kernel parameters to "y": CONFIG_DEBUG_INFO_REDUCED CONFIG_DEBUG_INFO_SPLIT But I'm not entirely sure yet. trying to test that... -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1190539] New: scsi host0: uas_eh_device_reset_handler
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1190539 Bug ID: 1190539 Summary: scsi host0: uas_eh_device_reset_handler Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mkrapp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I got a new ASUS Zenbook 14 UM524UA. It has two USB-c and one USB-A sockets. An external SATA M2 disk connected to the USB-A Port does not mount, but uas_device_reset happens frequently and the disk is not usable: 22:43:03 susi kernel: usb 4-2: new SuperSpeed USB device number 6 using xhci_hcd 22:43:03 susi kernel: usb 4-2: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00 22:43:03 susi kernel: usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 22:43:03 susi kernel: usb 4-2: Product: ASM105x 22:43:03 susi kernel: usb 4-2: Manufacturer: ASMT 22:43:03 susi kernel: usb 4-2: SerialNumber: ACDFD0000000000007B4 22:43:03 susi kernel: scsi host0: uas 22:43:03 susi kernel: scsi 0:0:0:0: Direct-Access ASMT 2115 0 PQ: 0 ANSI: 6 22:43:03 susi kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 22:43:03 susi kernel: sd 0:0:0:0: [sda] 937721856 512-byte logical blocks: (480 GB/447 GiB) 22:43:03 susi kernel: sd 0:0:0:0: [sda] Write Protect is off 22:43:03 susi kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 22:43:03 susi kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA 22:43:03 susi kernel: sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes 22:43:03 susi kernel: sda: sda1 22:43:03 susi kernel: sd 0:0:0:0: [sda] Attached SCSI disk 22:43:36 susi kernel: sd 0:0:0:0: [sda] tag#16 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 22:43:36 susi kernel: sd 0:0:0:0: [sda] tag#16 CDB: Read(10) 28 00 00 00 00 78 00 00 08 00 22:43:36 susi kernel: scsi host0: uas_eh_device_reset_handler start 22:43:36 susi kernel: usb 4-2: reset SuperSpeed USB device number 6 using xhci_hcd 22:43:36 susi kernel: scsi host0: uas_eh_device_reset_handler success 22:44:04 susi systemd-udevd[713]: sda: Worker [14902] processing SEQNUM=4825 is taking a long time 22:44:06 susi kernel: sd 0:0:0:0: [sda] tag#4 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN 22:44:06 susi kernel: sd 0:0:0:0: [sda] tag#4 CDB: Read(10) 28 00 00 00 01 08 00 00 f8 00 22:44:06 susi kernel: sd 0:0:0:0: [sda] tag#3 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD IN 22:44:06 susi kernel: sd 0:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 00 00 00 88 00 00 78 00 22:44:06 susi kernel: sd 0:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN 22:44:06 susi kernel: sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 00 00 00 48 00 00 30 00 22:44:07 susi kernel: scsi host0: uas_eh_device_reset_handler start 22:44:07 susi kernel: usb 4-2: reset SuperSpeed USB device number 6 using xhci_hcd 22:44:07 susi kernel: scsi host0: uas_eh_device_reset_handler success 22:44:37 susi kernel: scsi host0: uas_eh_device_reset_handler start 22:44:37 susi kernel: sd 0:0:0:0: [sda] tag#1 uas_zap_pending 0 uas-tag 2 inflight: CMD 22:44:37 susi kernel: sd 0:0:0:0: [sda] tag#1 CDB: Read(10) 28 00 00 00 00 88 00 00 78 00 22:44:37 susi kernel: sd 0:0:0:0: [sda] tag#2 uas_zap_pending 0 uas-tag 3 inflight: CMD 22:44:37 susi kernel: sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 00 00 01 08 00 00 f8 00 22:44:37 susi kernel: usb 4-2: reset SuperSpeed USB device number 6 using xhci_hcd 22:44:37 susi kernel: scsi host0: uas_eh_device_reset_handler success 22:45:08 susi kernel: scsi host0: uas_eh_device_reset_handler start 22:45:08 susi kernel: sd 0:0:0:0: [sda] tag#3 uas_zap_pending 0 uas-tag 1 inflight: CMD 22:45:08 susi kernel: sd 0:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 00 00 01 08 00 00 f8 00 22:45:08 susi kernel: sd 0:0:0:0: [sda] tag#5 uas_zap_pending 0 uas-tag 2 inflight: CMD 22:45:08 susi kernel: sd 0:0:0:0: [sda] tag#5 CDB: Read(10) 28 00 00 00 00 88 00 00 78 00 22:45:08 susi kernel: usb 4-2: reset SuperSpeed USB device number 6 using xhci_hcd 22:45:08 susi kernel: scsi host0: uas_eh_device_reset_handler success /dev/sda1 is not mountable (xfs) and fdisk hangs, disk is not usable -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1190058] New: Unable to handle kernel paging request at virtual address ffff8000156dc028
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1190058 Bug ID: 1190058 Summary: Unable to handle kernel paging request at virtual address ffff8000156dc028 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: schwab(a)suse.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Loading Linux 5.13.12-2-default ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x431f0a10] [ 0.000000] Linux version 5.13.12-2-default (geeko@buildhost) (gcc (SUSE Linux) 11.2.1 20210816 [revision 056e324ce46a7924b5cf10f61010cf9dd2ca10e9], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.36.1.20210326-4) #1 SMP Fri Aug 20 07:04:28 UTC 2021 (33df9c6) [ 0.000000] Machine model: cavium,thunder-88xx [ 0.000000] printk: debug: ignoring loglevel setting. [ 0.000000] efi: EFI v2.40 by American Megatrends [ 0.000000] efi: ESRT=0x1ffdb2fd18 SMBIOS 3.0=0x1ffbe7f998 ACPI 2.0=0x1ff24a0000 MEMRESERVE=0x1ff2510d98 [ 0.000000] esrt: Reserving ESRT space from 0x0000001ffdb2fd18 to 0x0000001ffdb2fd50. [ 0.000000] NUMA: NODE_DATA [mem 0x1fed056480-0x1fed05afff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000000500000-0x00000000ffffffff] [ 0.000000] DMA32 empty [ 0.000000] Normal [mem 0x0000000100000000-0x0000001fff0fffff] [ 0.000000] Device empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000500000-0x0000000000cfffff] [ 0.000000] node 0: [mem 0x0000000000d00000-0x000000000fffffff] [ 0.000000] node 0: [mem 0x0000000010000000-0x00000000101d3fff] [ 0.000000] node 0: [mem 0x00000000101d5000-0x00000000fffbffff] [ 0.000000] node 0: [mem 0x00000000fffc0000-0x00000000ffffffff] [ 0.000000] node 0: [mem 0x0000000100000000-0x0000001ff247ffff] [ 0.000000] node 0: [mem 0x0000001ff2480000-0x0000001ff249ffff] [ 0.000000] node 0: [mem 0x0000001ff24a0000-0x0000001ff252ffff] [ 0.000000] node 0: [mem 0x0000001ff2530000-0x0000001ff254ffff] [ 0.000000] node 0: [mem 0x0000001ff2550000-0x0000001ff972ffff] [ 0.000000] node 0: [mem 0x0000001ff9730000-0x0000001ff9c0ffff] [ 0.000000] node 0: [mem 0x0000001ff9c10000-0x0000001ffb5affff] [ 0.000000] node 0: [mem 0x0000001ffb5b0000-0x0000001ffd00ffff] [ 0.000000] node 0: [mem 0x0000001ffd010000-0x0000001ffeb9ffff] [ 0.000000] node 0: [mem 0x0000001ffeba0000-0x0000001ffebfffff] [ 0.000000] node 0: [mem 0x0000001ffec00000-0x0000001fff0fffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000500000-0x0000001fff0fffff] [ 0.000000] On node 0 totalpages: 33549311 [ 0.000000] DMA zone: 16364 pages used for memmap [ 0.000000] DMA zone: 0 pages reserved [ 0.000000] DMA zone: 1047295 pages, LIFO batch:63 [ 0.000000] Normal zone: 507844 pages used for memmap [ 0.000000] Normal zone: 32502016 pages, LIFO batch:63 [ 0.000000] On node 0, zone Normal: 256 pages in unavailable ranges [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv0.2 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: Trusted OS resident on physical CPU 0x0 [ 0.000000] percpu: Embedded 33 pages/cpu s97496 r8192 d29480 u135168 [ 0.000000] pcpu-alloc: s97496 r8192 d29480 u135168 alloc=33*4096 [ 0.000000] pcpu-alloc: [0] 00 [0] 01 [0] 02 [0] 03 [0] 04 [0] 05 [0] 06 [0] 07 [ 0.000000] pcpu-alloc: [0] 08 [0] 09 [0] 10 [0] 11 [0] 12 [0] 13 [0] 14 [0] 15 [ 0.000000] pcpu-alloc: [0] 16 [0] 17 [0] 18 [0] 19 [0] 20 [0] 21 [0] 22 [0] 23 [ 0.000000] pcpu-alloc: [0] 24 [0] 25 [0] 26 [0] 27 [0] 28 [0] 29 [0] 30 [0] 31 [ 0.000000] pcpu-alloc: [0] 32 [0] 33 [0] 34 [0] 35 [0] 36 [0] 37 [0] 38 [0] 39 [ 0.000000] pcpu-alloc: [0] 40 [0] 41 [0] 42 [0] 43 [0] 44 [0] 45 [0] 46 [0] 47 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: Software prefetching using PRFM [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: detected: Spectre-v2 [ 0.000000] CPU features: detected: Spectre-v4 [ 0.000000] CPU features: detected: Kernel page table isolation (KPTI) [ 0.000000] CPU features: detected: Cavium erratum 27456 [ 0.000000] CPU features: detected: Cavium erratum 30115 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 33025103 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/Image-5.13.12-2-default root=UUID=9b635036-2655-4d9a-918d-686308f3a2f5 console=ttyAMA0,115200 ignore_loglevel mitigations=auto [ 0.000000] printk: log_buf_len individual max cpu contribution: 32768 bytes [ 0.000000] printk: log_buf_len total cpu_extra contributions: 1540096 bytes [ 0.000000] printk: log_buf_len min size: 262144 bytes [ 0.000000] printk: log_buf_len: 2097152 bytes [ 0.000000] printk: early log buf free: 257936(98%) [ 0.000000] Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes, linear) [ 0.000000] Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] software IO TLB: mapped [mem 0x00000000fbfc0000-0x00000000fffc0000] (64MB) [ 0.000000] Memory: 4244396K/134197244K available (14080K kernel code, 3394K rwdata, 11648K rodata, 6912K init, 1607K bss, 2642620K reserved, 0K cma-reserved) [ 0.000000] random: get_random_u64 called from __kmem_cache_create+0x38/0x550 with crng_init=0 [ 0.000000] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=48, Nodes=1 [ 0.000000] ftrace: allocating 45114 entries in 177 pages [ 0.000000] ftrace: allocated 177 pages with 4 groups [ 0.000000] trace event string verifier disabled [ 0.000000] rcu: Hierarchical RCU implementation. [ 0.000000] rcu: RCU event tracing is enabled. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=480 to nr_cpu_ids=48. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Rude variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=48 [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode [ 0.000000] GIC: enabling workaround for GICv3: Cavium erratum 38539 [ 0.000000] GICv3: 128 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] GICv3: Distributor has no Range Selector support [ 0.000000] Root IRQ handler: gic_handle_irq [ 0.000000] GICv3: 16 PPIs implemented [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000801080000000 [ 0.000000] ITS [mem 0x801000020000-0x80100021ffff] [ 0.000000] ITS@0x0000801000020000: Devices Table too large, reduce ids 21->19 [ 0.000000] ITS@0x0000801000020000: allocated 524288 Devices @100800000 (flat, esz 8, psz 64K, shr 1) [ 0.000000] GICv3: using LPI property table @0x0000000100260000 [ 0.000000] GICv3: CPU0: using allocated LPI pending table @0x0000000100270000 [ 0.000000] arch_timer: cp15 timer(s) running at 100.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x171024e7e0, max_idle_ns: 440795205315 ns [ 0.000000] sched_clock: 56 bits at 100MHz, resolution 10ns, wraps every 4398046511100ns [ 0.000266] Console: colour dummy device 80x25 [ 0.000346] Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=1000000) [ 0.000357] pid_max: default: 49152 minimum: 384 [ 0.000486] LSM: Security Framework initializing [ 0.000550] AppArmor: AppArmor initialized [ 0.000686] Mount-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear) [ 0.000744] Mountpoint-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear) [ 0.019172] rcu: Hierarchical SRCU implementation. [ 0.019921] Platform MSI: gic-its@801000020000 domain created [ 0.019993] PCI/MSI: /interrupt-controller@801000000000/gic-its@801000020000 domain created [ 0.020052] fsl-mc MSI: gic-its@801000020000 domain created [ 0.020665] Remapping and enabling EFI services. [ 0.023404] smp: Bringing up secondary CPUs ... [ 0.023863] Detected VIPT I-cache on CPU1 [ 0.023879] GICv3: CPU1: found redistributor 1 region 0:0x0000801080020000 [ 0.023901] GICv3: CPU1: using allocated LPI pending table @0x0000000100280000 [ 0.023924] CPU1: Booted secondary processor 0x0000000001 [0x431f0a10] [ 0.024456] Detected VIPT I-cache on CPU2 [ 0.024468] GICv3: CPU2: found redistributor 2 region 0:0x0000801080040000 [ 0.024489] GICv3: CPU2: using allocated LPI pending table @0x0000000100290000 [ 0.024510] CPU2: Booted secondary processor 0x0000000002 [0x431f0a10] [ 0.025021] Detected VIPT I-cache on CPU3 [ 0.025033] GICv3: CPU3: found redistributor 3 region 0:0x0000801080060000 [ 0.025055] GICv3: CPU3: using allocated LPI pending table @0x00000001002a0000 [ 0.025076] CPU3: Booted secondary processor 0x0000000003 [0x431f0a10] [ 0.025591] Detected VIPT I-cache on CPU4 [ 0.025603] GICv3: CPU4: found redistributor 4 region 0:0x0000801080080000 [ 0.025624] GICv3: CPU4: using allocated LPI pending table @0x00000001002b0000 [ 0.025645] CPU4: Booted secondary processor 0x0000000004 [0x431f0a10] [ 0.026157] Detected VIPT I-cache on CPU5 [ 0.026169] GICv3: CPU5: found redistributor 5 region 0:0x00008010800a0000 [ 0.026191] GICv3: CPU5: using allocated LPI pending table @0x00000001002c0000 [ 0.026213] CPU5: Booted secondary processor 0x0000000005 [0x431f0a10] [ 0.026730] Detected VIPT I-cache on CPU6 [ 0.026742] GICv3: CPU6: found redistributor 6 region 0:0x00008010800c0000 [ 0.026764] GICv3: CPU6: using allocated LPI pending table @0x00000001002d0000 [ 0.026786] CPU6: Booted secondary processor 0x0000000006 [0x431f0a10] [ 0.027297] Detected VIPT I-cache on CPU7 [ 0.027310] GICv3: CPU7: found redistributor 7 region 0:0x00008010800e0000 [ 0.027333] GICv3: CPU7: using allocated LPI pending table @0x00000001002e0000 [ 0.027355] CPU7: Booted secondary processor 0x0000000007 [0x431f0a10] [ 0.027872] Detected VIPT I-cache on CPU8 [ 0.027885] GICv3: CPU8: found redistributor 8 region 0:0x0000801080100000 [ 0.027907] GICv3: CPU8: using allocated LPI pending table @0x00000001002f0000 [ 0.027930] CPU8: Booted secondary processor 0x0000000008 [0x431f0a10] [ 0.028446] Detected VIPT I-cache on CPU9 [ 0.028459] GICv3: CPU9: found redistributor 9 region 0:0x0000801080120000 [ 0.028481] GICv3: CPU9: using allocated LPI pending table @0x0000000100300000 [ 0.028504] CPU9: Booted secondary processor 0x0000000009 [0x431f0a10] [ 0.029035] Detected VIPT I-cache on CPU10 [ 0.029048] GICv3: CPU10: found redistributor a region 0:0x0000801080140000 [ 0.029070] GICv3: CPU10: using allocated LPI pending table @0x0000000100310000 [ 0.029093] CPU10: Booted secondary processor 0x000000000a [0x431f0a10] [ 0.029607] Detected VIPT I-cache on CPU11 [ 0.029621] GICv3: CPU11: found redistributor b region 0:0x0000801080160000 [ 0.029644] GICv3: CPU11: using allocated LPI pending table @0x0000000100320000 [ 0.029667] CPU11: Booted secondary processor 0x000000000b [0x431f0a10] [ 0.030216] Detected VIPT I-cache on CPU12 [ 0.030229] GICv3: CPU12: found redistributor c region 0:0x0000801080180000 [ 0.030253] GICv3: CPU12: using allocated LPI pending table @0x0000000100330000 [ 0.030276] CPU12: Booted secondary processor 0x000000000c [0x431f0a10] [ 0.030791] Detected VIPT I-cache on CPU13 [ 0.030805] GICv3: CPU13: found redistributor d region 0:0x00008010801a0000 [ 0.030828] GICv3: CPU13: using allocated LPI pending table @0x0000000100340000 [ 0.030852] CPU13: Booted secondary processor 0x000000000d [0x431f0a10] [ 0.031377] Detected VIPT I-cache on CPU14 [ 0.031391] GICv3: CPU14: found redistributor e region 0:0x00008010801c0000 [ 0.031414] GICv3: CPU14: using allocated LPI pending table @0x0000000100350000 [ 0.031438] CPU14: Booted secondary processor 0x000000000e [0x431f0a10] [ 0.031960] Detected VIPT I-cache on CPU15 [ 0.031974] GICv3: CPU15: found redistributor f region 0:0x00008010801e0000 [ 0.031998] GICv3: CPU15: using allocated LPI pending table @0x0000000100360000 [ 0.032023] CPU15: Booted secondary processor 0x000000000f [0x431f0a10] [ 0.032548] Detected VIPT I-cache on CPU16 [ 0.032563] GICv3: CPU16: found redistributor 100 region 0:0x0000801080200000 [ 0.032587] GICv3: CPU16: using allocated LPI pending table @0x0000000100370000 [ 0.032611] CPU16: Booted secondary processor 0x0000000100 [0x431f0a10] [ 0.033134] Detected VIPT I-cache on CPU17 [ 0.033149] GICv3: CPU17: found redistributor 101 region 0:0x0000801080220000 [ 0.033172] GICv3: CPU17: using allocated LPI pending table @0x0000000100380000 [ 0.033197] CPU17: Booted secondary processor 0x0000000101 [0x431f0a10] [ 0.033726] Detected VIPT I-cache on CPU18 [ 0.033741] GICv3: CPU18: found redistributor 102 region 0:0x0000801080240000 [ 0.033765] GICv3: CPU18: using allocated LPI pending table @0x0000000100390000 [ 0.033790] CPU18: Booted secondary processor 0x0000000102 [0x431f0a10] [ 0.034309] Detected VIPT I-cache on CPU19 [ 0.034325] GICv3: CPU19: found redistributor 103 region 0:0x0000801080260000 [ 0.034349] GICv3: CPU19: using allocated LPI pending table @0x00000001003a0000 [ 0.034375] CPU19: Booted secondary processor 0x0000000103 [0x431f0a10] [ 0.034897] Detected VIPT I-cache on CPU20 [ 0.034912] GICv3: CPU20: found redistributor 104 region 0:0x0000801080280000 [ 0.034936] GICv3: CPU20: using allocated LPI pending table @0x00000001003b0000 [ 0.034962] CPU20: Booted secondary processor 0x0000000104 [0x431f0a10] [ 0.035484] Detected VIPT I-cache on CPU21 [ 0.035500] GICv3: CPU21: found redistributor 105 region 0:0x00008010802a0000 [ 0.035524] GICv3: CPU21: using allocated LPI pending table @0x00000001003c0000 [ 0.035551] CPU21: Booted secondary processor 0x0000000105 [0x431f0a10] [ 0.036083] Detected VIPT I-cache on CPU22 [ 0.036099] GICv3: CPU22: found redistributor 106 region 0:0x00008010802c0000 [ 0.036124] GICv3: CPU22: using allocated LPI pending table @0x00000001003d0000 [ 0.036150] CPU22: Booted secondary processor 0x0000000106 [0x431f0a10] [ 0.036672] Detected VIPT I-cache on CPU23 [ 0.036688] GICv3: CPU23: found redistributor 107 region 0:0x00008010802e0000 [ 0.036713] GICv3: CPU23: using allocated LPI pending table @0x00000001003e0000 [ 0.036740] CPU23: Booted secondary processor 0x0000000107 [0x431f0a10] [ 0.037271] Detected VIPT I-cache on CPU24 [ 0.037287] GICv3: CPU24: found redistributor 108 region 0:0x0000801080300000 [ 0.037312] GICv3: CPU24: using allocated LPI pending table @0x00000001003f0000 [ 0.037339] CPU24: Booted secondary processor 0x0000000108 [0x431f0a10] [ 0.037859] Detected VIPT I-cache on CPU25 [ 0.037875] GICv3: CPU25: found redistributor 109 region 0:0x0000801080320000 [ 0.037900] GICv3: CPU25: using allocated LPI pending table @0x0000000100c00000 [ 0.037928] CPU25: Booted secondary processor 0x0000000109 [0x431f0a10] [ 0.038460] Detected VIPT I-cache on CPU26 [ 0.038476] GICv3: CPU26: found redistributor 10a region 0:0x0000801080340000 [ 0.038501] GICv3: CPU26: using allocated LPI pending table @0x0000000100c10000 [ 0.038529] CPU26: Booted secondary processor 0x000000010a [0x431f0a10] [ 0.039062] Detected VIPT I-cache on CPU27 [ 0.039079] GICv3: CPU27: found redistributor 10b region 0:0x0000801080360000 [ 0.039105] GICv3: CPU27: using allocated LPI pending table @0x0000000100c20000 [ 0.039132] CPU27: Booted secondary processor 0x000000010b [0x431f0a10] [ 0.039659] Detected VIPT I-cache on CPU28 [ 0.039676] GICv3: CPU28: found redistributor 10c region 0:0x0000801080380000 [ 0.039702] GICv3: CPU28: using allocated LPI pending table @0x0000000100c30000 [ 0.039730] CPU28: Booted secondary processor 0x000000010c [0x431f0a10] [ 0.040280] Detected VIPT I-cache on CPU29 [ 0.040297] GICv3: CPU29: found redistributor 10d region 0:0x00008010803a0000 [ 0.040324] GICv3: CPU29: using allocated LPI pending table @0x0000000100c40000 [ 0.040352] CPU29: Booted secondary processor 0x000000010d [0x431f0a10] [ 0.040889] Detected VIPT I-cache on CPU30 [ 0.040906] GICv3: CPU30: found redistributor 10e region 0:0x00008010803c0000 [ 0.040933] GICv3: CPU30: using allocated LPI pending table @0x0000000100c50000 [ 0.040961] CPU30: Booted secondary processor 0x000000010e [0x431f0a10] [ 0.041492] Detected VIPT I-cache on CPU31 [ 0.041510] GICv3: CPU31: found redistributor 10f region 0:0x00008010803e0000 [ 0.041536] GICv3: CPU31: using allocated LPI pending table @0x0000000100c60000 [ 0.041565] CPU31: Booted secondary processor 0x000000010f [0x431f0a10] [ 0.042095] Detected VIPT I-cache on CPU32 [ 0.042113] GICv3: CPU32: found redistributor 200 region 0:0x0000801080400000 [ 0.042139] GICv3: CPU32: using allocated LPI pending table @0x0000000100c70000 [ 0.042168] CPU32: Booted secondary processor 0x0000000200 [0x431f0a10] [ 0.042709] Detected VIPT I-cache on CPU33 [ 0.042727] GICv3: CPU33: found redistributor 201 region 0:0x0000801080420000 [ 0.042754] GICv3: CPU33: using allocated LPI pending table @0x0000000100c80000 [ 0.042784] CPU33: Booted secondary processor 0x0000000201 [0x431f0a10] [ 0.043320] Detected VIPT I-cache on CPU34 [ 0.043338] GICv3: CPU34: found redistributor 202 region 0:0x0000801080440000 [ 0.043365] GICv3: CPU34: using allocated LPI pending table @0x0000000100c90000 [ 0.043395] CPU34: Booted secondary processor 0x0000000202 [0x431f0a10] [ 0.043925] Detected VIPT I-cache on CPU35 [ 0.043944] GICv3: CPU35: found redistributor 203 region 0:0x0000801080460000 [ 0.043971] GICv3: CPU35: using allocated LPI pending table @0x0000000100ca0000 [ 0.044002] CPU35: Booted secondary processor 0x0000000203 [0x431f0a10] [ 0.044542] Detected VIPT I-cache on CPU36 [ 0.044561] GICv3: CPU36: found redistributor 204 region 0:0x0000801080480000 [ 0.044588] GICv3: CPU36: using allocated LPI pending table @0x0000000100cb0000 [ 0.044618] CPU36: Booted secondary processor 0x0000000204 [0x431f0a10] [ 0.045150] Detected VIPT I-cache on CPU37 [ 0.045169] GICv3: CPU37: found redistributor 205 region 0:0x00008010804a0000 [ 0.045197] GICv3: CPU37: using allocated LPI pending table @0x0000000100cc0000 [ 0.045228] CPU37: Booted secondary processor 0x0000000205 [0x431f0a10] [ 0.045769] Detected VIPT I-cache on CPU38 [ 0.045788] GICv3: CPU38: found redistributor 206 region 0:0x00008010804c0000 [ 0.045816] GICv3: CPU38: using allocated LPI pending table @0x0000000100cd0000 [ 0.045847] CPU38: Booted secondary processor 0x0000000206 [0x431f0a10] [ 0.046391] Detected VIPT I-cache on CPU39 [ 0.046411] GICv3: CPU39: found redistributor 207 region 0:0x00008010804e0000 [ 0.046438] GICv3: CPU39: using allocated LPI pending table @0x0000000100ce0000 [ 0.046470] CPU39: Booted secondary processor 0x0000000207 [0x431f0a10] [ 0.047006] Detected VIPT I-cache on CPU40 [ 0.047024] GICv3: CPU40: found redistributor 208 region 0:0x0000801080500000 [ 0.047052] GICv3: CPU40: using allocated LPI pending table @0x0000000100cf0000 [ 0.047084] CPU40: Booted secondary processor 0x0000000208 [0x431f0a10] [ 0.047621] Detected VIPT I-cache on CPU41 [ 0.047641] GICv3: CPU41: found redistributor 209 region 0:0x0000801080520000 [ 0.047668] GICv3: CPU41: using allocated LPI pending table @0x0000000100d00000 [ 0.047701] CPU41: Booted secondary processor 0x0000000209 [0x431f0a10] [ 0.048252] Detected VIPT I-cache on CPU42 [ 0.048271] GICv3: CPU42: found redistributor 20a region 0:0x0000801080540000 [ 0.048299] GICv3: CPU42: using allocated LPI pending table @0x0000000100d10000 [ 0.048332] CPU42: Booted secondary processor 0x000000020a [0x431f0a10] [ 0.048870] Detected VIPT I-cache on CPU43 [ 0.048890] GICv3: CPU43: found redistributor 20b region 0:0x0000801080560000 [ 0.048918] GICv3: CPU43: using allocated LPI pending table @0x0000000100d20000 [ 0.048950] CPU43: Booted secondary processor 0x000000020b [0x431f0a10] [ 0.049491] Detected VIPT I-cache on CPU44 [ 0.049510] GICv3: CPU44: found redistributor 20c region 0:0x0000801080580000 [ 0.049539] GICv3: CPU44: using allocated LPI pending table @0x0000000100d30000 [ 0.049571] CPU44: Booted secondary processor 0x000000020c [0x431f0a10] [ 0.050127] Detected VIPT I-cache on CPU45 [ 0.050148] GICv3: CPU45: found redistributor 20d region 0:0x00008010805a0000 [ 0.050176] GICv3: CPU45: using allocated LPI pending table @0x0000000100d40000 [ 0.050209] CPU45: Booted secondary processor 0x000000020d [0x431f0a10] [ 0.050760] Detected VIPT I-cache on CPU46 [ 0.050780] GICv3: CPU46: found redistributor 20e region 0:0x00008010805c0000 [ 0.050809] GICv3: CPU46: using allocated LPI pending table @0x0000000100d50000 [ 0.050842] CPU46: Booted secondary processor 0x000000020e [0x431f0a10] [ 0.051384] Detected VIPT I-cache on CPU47 [ 0.051405] GICv3: CPU47: found redistributor 20f region 0:0x00008010805e0000 [ 0.051433] GICv3: CPU47: using allocated LPI pending table @0x0000000100d60000 [ 0.051467] CPU47: Booted secondary processor 0x000000020f [0x431f0a10] [ 0.051574] smp: Brought up 1 node, 48 CPUs [ 0.051845] SMP: Total of 48 processors activated. [ 0.051852] CPU features: detected: Data cache clean to the PoU not required for I/D coherence [ 0.051857] CPU features: detected: CRC32 instructions [ 1.476590] CPU features: emulated: Privileged Access Never (PAN) using TTBR0_EL1 switching [ 1.484926] CPU: All CPU(s) started at EL2 [ 1.485092] alternatives: patching kernel code [ 6.630500] node 0 deferred pages initialised in 5140ms [ 6.656888] devtmpfs: initialized [ 6.702287] Registered cp15_barrier emulation handler [ 6.702314] Registered setend emulation handler [ 6.702323] KASLR disabled due to lack of seed [ 6.702563] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 6.702593] futex hash table entries: 16384 (order: 8, 1048576 bytes, linear) [ 6.702961] pinctrl core: initialized pinctrl subsystem [ 6.703631] SMBIOS 3.0.0 present. [ 6.703650] DMI: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 5.11 12/12/2012 [ 6.704180] NET: Registered protocol family 16 [ 6.705825] DMA: preallocated 4096 KiB GFP_KERNEL pool for atomic allocations [ 6.706079] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations [ 6.706328] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations [ 6.706359] audit: initializing netlink subsys (disabled) [ 6.706481] audit: type=2000 audit(5.280:1): state=initialized audit_enabled=0 res=1 [ 6.707124] thermal_sys: Registered thermal governor 'fair_share' [ 6.707130] thermal_sys: Registered thermal governor 'bang_bang' [ 6.707135] thermal_sys: Registered thermal governor 'step_wise' [ 6.707140] thermal_sys: Registered thermal governor 'user_space' [ 6.707351] cpuidle: using governor ladder [ 6.707523] cpuidle: using governor menu [ 6.707638] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 6.708154] ASID allocator initialised with 32768 entries [ 6.708916] Serial: AMBA PL011 UART driver [ 6.714312] 87e024000000.serial: ttyAMA0 at MMIO 0x87e024000000 (irq = 15, base_baud = 0) is a PL011 rev3 [ 8.794589] printk: console [ttyAMA0] enabled [ 8.799424] 87e025000000.serial: ttyAMA1 at MMIO 0x87e025000000 (irq = 16, base_baud = 0) is a PL011 rev3 [ 8.816002] OF: /soc@0/pci@848000000000: #msi-cells = 1 found -1 [ 8.822218] OF: /soc@0/pci@849000000000: #msi-cells = 1 found -1 [ 8.828384] OF: /soc@0/pci@84a000000000: #msi-cells = 1 found -1 [ 8.834556] OF: /soc@0/pci@84b000000000: #msi-cells = 1 found -1 [ 8.840734] OF: /soc@0/pci@87e0c0000000: #msi-cells = 1 found -1 [ 8.861572] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [ 8.868281] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages [ 8.874973] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [ 8.881669] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages [ 9.390424] wait_for_initramfs() called before rootfs_initcalls [ 9.410996] ACPI: Interpreter disabled. [ 9.415247] iommu: Default domain type: Passthrough [ 9.420333] vgaarb: loaded [ 9.423415] SCSI subsystem initialized [ 9.427316] libata version 3.00 loaded. [ 9.431286] pps_core: LinuxPPS API ver. 1 registered [ 9.436243] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti(a)linux.it> [ 9.445384] PTP clock support registered [ 9.449362] EDAC MC: Ver: 3.0.0 [ 9.452570] EDAC DEBUG: edac_mc_sysfs_init: device mc created [ 9.458662] Registered efivars operations [ 9.463678] NetLabel: Initializing [ 9.467074] NetLabel: domain hash size = 128 [ 9.471434] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [ 9.477130] NetLabel: unlabeled traffic allowed by default [ 9.483163] clocksource: Switched to clocksource arch_sys_counter [ 9.526951] VFS: Disk quotas dquot_6.6.0 [ 9.530923] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 9.538304] AppArmor: AppArmor Filesystem Enabled [ 9.543037] pnp: PnP ACPI: disabled [ 9.552318] NET: Registered protocol family 2 [ 9.556840] IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear) [ 9.569273] tcp_listen_portaddr_hash hash table entries: 65536 (order: 8, 1048576 bytes, linear) [ 9.578759] TCP established hash table entries: 524288 (order: 10, 4194304 bytes, linear) [ 9.588866] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear) [ 9.596681] TCP: Hash tables configured (established 524288 bind 65536) [ 9.603724] MPTCP token hash table entries: 65536 (order: 8, 1572864 bytes, linear) [ 9.611978] UDP hash table entries: 65536 (order: 9, 2097152 bytes, linear) [ 9.620173] UDP-Lite hash table entries: 65536 (order: 9, 2097152 bytes, linear) [ 9.629353] NET: Registered protocol family 1 [ 9.633729] NET: Registered protocol family 44 [ 9.638172] PCI: CLS 0 bytes, default 64 [ 9.642293] Trying to unpack rootfs image as initramfs... [ 9.648381] hw perfevents: enabled with armv8_cavium_thunder PMU driver, 7 counters available [ 9.657109] kvm [1]: IPA Size Limit: 48 bits [ 9.663379] kvm [1]: GICv3: no GICV resource entry [ 9.668165] kvm [1]: disabling GICv2 emulation [ 9.672599] kvm [1]: GICv3 sysreg trapping enabled ([G0G1], reduced performance) [ 9.680029] kvm [1]: GIC system register CPU interface enabled [ 9.687038] kvm [1]: vgic interrupt IRQ9 [ 9.692549] kvm [1]: Hyp mode initialized successfully [ 9.700853] Initialise system trusted keyrings [ 9.705315] Key type blacklist registered [ 9.709468] workingset: timestamp_bits=40 max_order=25 bucket_order=0 [ 9.720674] zbud: loaded [ 9.724694] integrity: Platform Keyring initialized [ 9.755027] Key type asymmetric registered [ 9.759119] Asymmetric key parser 'x509' registered [ 9.764022] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245) [ 9.771567] io scheduler mq-deadline registered [ 9.776102] io scheduler kyber registered [ 9.780257] io scheduler bfq registered [ 9.787105] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 9.794162] pci-host-generic 848000000000.pci: host bridge /soc@0/pci@848000000000 ranges: [ 9.802447] pci-host-generic 848000000000.pci: MEM 0x802000000000..0x807fffffffff -> 0x802000000000 [ 9.811941] pci-host-generic 848000000000.pci: MEM 0x838000000000..0x841fffffffff -> 0x838000000000 [ 9.821426] pci-host-generic 848000000000.pci: MEM 0x846000000000..0x847fffffffff -> 0x846000000000 [ 9.830913] pci-host-generic 848000000000.pci: MEM 0x868000000000..0x87e023ffffff -> 0x868000000000 [ 9.840405] pci-host-generic 848000000000.pci: MEM 0x87e026000000..0x87e0bfffffff -> 0x87e026000000 [ 9.849888] pci-host-generic 848000000000.pci: MEM 0x87e0c6000000..0x87ffffffffff -> 0x87e0c6000000 [ 9.859376] pci-host-generic 848000000000.pci: Memory resource size exceeds max for 32 bits [ 9.867721] pci-host-generic 848000000000.pci: Memory resource size exceeds max for 32 bits [ 9.876066] pci-host-generic 848000000000.pci: Memory resource size exceeds max for 32 bits [ 9.884410] pci-host-generic 848000000000.pci: Memory resource size exceeds max for 32 bits [ 9.892751] pci-host-generic 848000000000.pci: Memory resource size exceeds max for 32 bits [ 9.901119] pci-host-generic 848000000000.pci: ECAM at [mem 0x848000000000-0x848001ffffff] for [bus 00-1f] [ 9.910878] pci-host-generic 848000000000.pci: PCI host bridge to bus 0000:00 [ 9.918022] pci_bus 0000:00: root bus resource [bus 00-1f] [ 9.923503] pci_bus 0000:00: root bus resource [mem 0x802000000000-0x807fffffffff] [ 9.931065] pci_bus 0000:00: root bus resource [mem 0x838000000000-0x841fffffffff] [ 9.938630] pci_bus 0000:00: root bus resource [mem 0x846000000000-0x847fffffffff] [ 9.946210] pci_bus 0000:00: root bus resource [mem 0x868000000000-0x87e023ffffff] [ 9.953782] pci_bus 0000:00: root bus resource [mem 0x87e026000000-0x87e0bfffffff] [ 9.961343] pci_bus 0000:00: root bus resource [mem 0x87e0c6000000-0x87ffffffffff] [ 9.968997] pci 0000:00:01.0: [177d:a002] type 01 class 0x060400 [ 9.975467] pci 0000:00:09.0: [177d:a018] type 00 class 0x120000 [ 9.981493] pci 0000:00:09.0: BAR 0: [mem 0x87e040000000-0x87e0400fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 9.992455] pci 0000:00:09.0: VF BAR 0: [mem 0x840000800000-0x8400008fffff 64bit] (from Enhanced Allocation, properties 0x4) [ 11.033182] pci 0000:00:09.0: VF(n) BAR0 space: [mem 0x840000800000-0x8400008fffff 64bit] (contains BAR0 for 1 VFs) [ 11.044083] pci 0000:00:10.0: [177d:a01b] type 00 class 0x0c0330 [ 11.050115] pci 0000:00:10.0: BAR 0: [mem 0x868000000000-0x8680001fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.061075] pci 0000:00:10.0: BAR 4: [mem 0x868000200000-0x8680002fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.072198] pci 0000:00:11.0: [177d:a01b] type 00 class 0x0c0330 [ 11.078232] pci 0000:00:11.0: BAR 0: [mem 0x869000000000-0x8690001fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.089185] pci 0000:00:11.0: BAR 4: [mem 0x869000200000-0x8690002fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.100366] pci 0000:00:14.0: [177d:a002] type 01 class 0x060400 [ 11.106561] pci 0000:00:15.0: [177d:a002] type 01 class 0x060400 [ 11.112750] pci 0000:00:16.0: [177d:a002] type 01 class 0x060400 [ 11.119304] pci 0000:01:00.0: [177d:a001] type 00 class 0x088000 [ 11.125340] pci 0000:01:00.0: BAR 0: [mem 0x87e0fc000000-0x87e0fc0fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.136295] pci 0000:01:00.0: BAR 4: [mem 0x87e0fcf00000-0x87e0fcffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.147393] pci 0000:01:00.1: [177d:a00e] type 00 class 0x088000 [ 11.153431] pci 0000:01:00.1: BAR 0: [mem 0x87e006000000-0x87e0067fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.164384] pci 0000:01:00.1: BAR 4: [mem 0x87e006f00000-0x87e006ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.175469] pci 0000:01:01.3: [177d:a02b] type 00 class 0x0c8000 [ 11.181494] pci 0000:01:01.3: BAR 0: [mem 0x87e005000000-0x87e0057fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.192623] pci 0000:01:01.4: [177d:a010] type 00 class 0x058000 [ 11.198658] pci 0000:01:01.4: BAR 0: [mem 0x87e009000000-0x87e0097fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.209611] pci 0000:01:01.4: BAR 4: [mem 0x87e009f00000-0x87e009ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.220705] pci 0000:01:06.0: [177d:a02e] type 00 class 0x058000 [ 11.226741] pci 0000:01:06.0: BAR 0: [mem 0x87e050000000-0x87e0507fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.237694] pci 0000:01:06.0: BAR 4: [mem 0x87e050f00000-0x87e050ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.248796] pci 0000:01:06.1: [177d:a02e] type 00 class 0x058000 [ 11.254832] pci 0000:01:06.1: BAR 0: [mem 0x87e051000000-0x87e0517fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.265785] pci 0000:01:06.1: BAR 4: [mem 0x87e051f00000-0x87e051ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.276880] pci 0000:01:06.2: [177d:a02e] type 00 class 0x058000 [ 11.282906] pci 0000:01:06.2: BAR 0: [mem 0x87e052000000-0x87e0527fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.293865] pci 0000:01:06.2: BAR 4: [mem 0x87e052f00000-0x87e052ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.304957] pci 0000:01:06.3: [177d:a02e] type 00 class 0x058000 [ 11.310983] pci 0000:01:06.3: BAR 0: [mem 0x87e053000000-0x87e0537fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.321942] pci 0000:01:06.3: BAR 4: [mem 0x87e053f00000-0x87e053ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.333035] pci 0000:01:06.4: [177d:a02e] type 00 class 0x058000 [ 11.339070] pci 0000:01:06.4: BAR 0: [mem 0x87e054000000-0x87e0547fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.350023] pci 0000:01:06.4: BAR 4: [mem 0x87e054f00000-0x87e054ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.361117] pci 0000:01:06.5: [177d:a02e] type 00 class 0x058000 [ 11.367161] pci 0000:01:06.5: BAR 0: [mem 0x87e055000000-0x87e0557fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.378118] pci 0000:01:06.5: BAR 4: [mem 0x87e055f00000-0x87e055ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.389212] pci 0000:01:06.6: [177d:a02e] type 00 class 0x058000 [ 11.395248] pci 0000:01:06.6: BAR 0: [mem 0x87e056000000-0x87e0567fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.406200] pci 0000:01:06.6: BAR 4: [mem 0x87e056f00000-0x87e056ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.417296] pci 0000:01:06.7: [177d:a02e] type 00 class 0x058000 [ 11.423331] pci 0000:01:06.7: BAR 0: [mem 0x87e057000000-0x87e0577fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.434284] pci 0000:01:06.7: BAR 4: [mem 0x87e057f00000-0x87e057ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.445386] pci 0000:01:07.0: [177d:a02f] type 00 class 0x058000 [ 11.451412] pci 0000:01:07.0: BAR 0: [mem 0x87e058000000-0x87e0587fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.462371] pci 0000:01:07.0: BAR 4: [mem 0x87e058f00000-0x87e058ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.473471] pci 0000:01:07.1: [177d:a02f] type 00 class 0x058000 [ 11.479497] pci 0000:01:07.1: BAR 0: [mem 0x87e059000000-0x87e0597fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.490457] pci 0000:01:07.1: BAR 4: [mem 0x87e059f00000-0x87e059ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.501552] pci 0000:01:07.2: [177d:a02f] type 00 class 0x058000 [ 11.507595] pci 0000:01:07.2: BAR 0: [mem 0x87e05a000000-0x87e05a7fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.518554] pci 0000:01:07.2: BAR 4: [mem 0x87e05af00000-0x87e05affffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.529649] pci 0000:01:07.3: [177d:a02f] type 00 class 0x058000 [ 11.535692] pci 0000:01:07.3: BAR 0: [mem 0x87e05b000000-0x87e05b7fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.546650] pci 0000:01:07.3: BAR 4: [mem 0x87e05bf00000-0x87e05bffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.557746] pci 0000:01:07.4: [177d:a030] type 00 class 0x058000 [ 11.563781] pci 0000:01:07.4: BAR 0: [mem 0x87e05c000000-0x87e05c7fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.574734] pci 0000:01:07.4: BAR 4: [mem 0x87e05cf00000-0x87e05cffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.585826] pci 0000:01:07.5: [177d:a030] type 00 class 0x058000 [ 11.591851] pci 0000:01:07.5: BAR 0: [mem 0x87e05d000000-0x87e05d7fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.602811] pci 0000:01:07.5: BAR 4: [mem 0x87e05df00000-0x87e05dffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.613903] pci 0000:01:07.6: [177d:a030] type 00 class 0x058000 [ 11.619929] pci 0000:01:07.6: BAR 0: [mem 0x87e05e000000-0x87e05e7fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.630889] pci 0000:01:07.6: BAR 4: [mem 0x87e05ef00000-0x87e05effffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.641986] pci 0000:01:07.7: [177d:a030] type 00 class 0x058000 [ 11.648021] pci 0000:01:07.7: BAR 0: [mem 0x87e05f000000-0x87e05f7fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.658974] pci 0000:01:07.7: BAR 4: [mem 0x87e05ff00000-0x87e05fffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.670065] pci 0000:01:09.4: [177d:a012] type 00 class 0x0c8000 [ 11.676107] pci 0000:01:09.4: BAR 0: [mem 0x87e0d4000000-0x87e0d47fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.687065] pci 0000:01:09.4: BAR 4: [mem 0x87e0d4f00000-0x87e0d4ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.698184] pci 0000:01:0a.0: [177d:a022] type 00 class 0x058000 [ 11.704223] pci 0000:01:0a.0: BAR 0: [mem 0x87e088000000-0x87e0887fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.715176] pci 0000:01:0a.0: BAR 4: [mem 0x87e088f00000-0x87e088ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.726276] pci 0000:01:0a.1: [177d:a022] type 00 class 0x058000 [ 11.732302] pci 0000:01:0a.1: BAR 0: [mem 0x87e089000000-0x87e0897fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.743261] pci 0000:01:0a.1: BAR 4: [mem 0x87e089f00000-0x87e089ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.754354] pci 0000:01:0a.2: [177d:a022] type 00 class 0x058000 [ 11.760380] pci 0000:01:0a.2: BAR 0: [mem 0x87e08a000000-0x87e08a7fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.771339] pci 0000:01:0a.2: BAR 4: [mem 0x87e08af00000-0x87e08affffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.782443] pci 0000:01:0a.3: [177d:a022] type 00 class 0x058000 [ 11.788479] pci 0000:01:0a.3: BAR 0: [mem 0x87e08b000000-0x87e08b7fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.799432] pci 0000:01:0a.3: BAR 4: [mem 0x87e08bf00000-0x87e08bffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.810524] pci 0000:01:10.0: [177d:a026] type 00 class 0x028000 [ 11.816559] pci 0000:01:10.0: BAR 0: [mem 0x87e0e0000000-0x87e0e03fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.827511] pci 0000:01:10.0: BAR 4: [mem 0x87e0e0400000-0x87e0e07fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.838626] pci 0000:01:10.1: [177d:a026] type 00 class 0x028000 [ 11.844662] pci 0000:01:10.1: BAR 0: [mem 0x87e0e1000000-0x87e0e13fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.855614] pci 0000:01:10.1: BAR 4: [mem 0x87e0e1400000-0x87e0e17fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.866712] pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' [ 11.877779] pci_bus 0000:01: busn_res: [bus 01-1f] end is updated to 01 [ 11.884480] pci 0000:02:00.0: [177d:a01d] type 00 class 0x010400 [ 11.890505] pci 0000:02:00.0: BAR 0: [mem 0x870000000000-0x8700007fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.901464] pci 0000:02:00.0: BAR 4: [mem 0x870000f00000-0x870000ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.912544] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' [ 11.923472] pci_bus 0000:02: busn_res: [bus 02-1f] end is updated to 02 [ 11.930158] pci 0000:03:00.0: [177d:a01a] type 00 class 0x120000 [ 11.936192] pci 0000:03:00.0: BAR 0: [mem 0x838000000000-0x8380003fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.947145] pci 0000:03:00.0: BAR 4: [mem 0x838000f00000-0x838000ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.958230] pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' [ 11.969153] pci_bus 0000:03: busn_res: [bus 03-1f] end is updated to 03 [ 11.975842] pci 0000:04:00.0: [177d:a019] type 00 class 0x120000 [ 11.981866] pci 0000:04:00.0: BAR 0: [mem 0x846000000000-0x8467ffffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 11.992825] pci 0000:04:00.0: BAR 4: [mem 0x846a00000000-0x846a000fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 12.003949] pci 0000:04:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' [ 12.014884] pci_bus 0000:04: busn_res: [bus 04-1f] end is updated to 04 [ 12.021568] pci 0000:00:01.0: PCI bridge to [bus 01] [ 12.026544] pci 0000:00:14.0: PCI bridge to [bus 02] [ 12.031504] pci 0000:00:15.0: PCI bridge to [bus 03] [ 12.036467] pci 0000:00:16.0: PCI bridge to [bus 04] [ 12.042171] pci-host-generic 849000000000.pci: host bridge /soc@0/pci@849000000000 ranges: [ 12.050468] pci-host-generic 849000000000.pci: MEM 0x810000000000..0x817fffffffff -> 0x810000000000 [ 12.059956] pci-host-generic 849000000000.pci: Memory resource size exceeds max for 32 bits [ 12.068320] pci-host-generic 849000000000.pci: ECAM at [mem 0x849000000000-0x849001ffffff] for [bus 00-1f] [ 12.078072] pci-host-generic 849000000000.pci: PCI host bridge to bus 0001:00 [ 12.085212] pci_bus 0001:00: root bus resource [bus 00-1f] [ 12.090690] pci_bus 0001:00: root bus resource [mem 0x810000000000-0x817fffffffff] [ 12.098504] pci 0001:00:08.0: [177d:a01c] type 00 class 0x010601 [ 12.104532] pci 0001:00:08.0: BAR 0: [mem 0x814000000000-0x8140001fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 12.115487] pci 0001:00:08.0: BAR 4: [mem 0x814000200000-0x8140002fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 12.126606] pci 0001:00:09.0: [177d:a01c] type 00 class 0x010601 [ 12.131333] Freeing initrd memory: 13244K [ 12.132637] pci 0001:00:09.0: BAR 0: [mem 0x815000000000-0x8150001fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 12.147578] pci 0001:00:09.0: BAR 4: [mem 0x815000200000-0x8150002fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 12.158738] pci 0001:00:0a.0: [177d:a01c] type 00 class 0x010601 [ 12.164774] pci 0001:00:0a.0: BAR 0: [mem 0x816000000000-0x8160001fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 12.175726] pci 0001:00:0a.0: BAR 4: [mem 0x816000200000-0x8160002fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 12.186845] pci 0001:00:0b.0: [177d:a01c] type 00 class 0x010601 [ 12.192870] pci 0001:00:0b.0: BAR 0: [mem 0x817000000000-0x8170001fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 12.203840] pci 0001:00:0b.0: BAR 4: [mem 0x817000200000-0x8170002fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 12.215661] pci-host-generic 84a000000000.pci: host bridge /soc@0/pci@84a000000000 ranges: [ 12.223955] pci-host-generic 84a000000000.pci: MEM 0x842000000000..0x843fffffffff -> 0x842000000000 [ 12.233441] pci-host-generic 84a000000000.pci: Memory resource size exceeds max for 32 bits [ 12.241810] pci-host-generic 84a000000000.pci: ECAM at [mem 0x84a000000000-0x84a001ffffff] for [bus 00-1f] [ 12.251563] pci-host-generic 84a000000000.pci: PCI host bridge to bus 0002:00 [ 12.258703] pci_bus 0002:00: root bus resource [bus 00-1f] [ 12.264184] pci_bus 0002:00: root bus resource [mem 0x842000000000-0x843fffffffff] [ 12.271818] pci 0002:00:02.0: [177d:a002] type 01 class 0x060400 [ 12.278006] pci 0002:00:03.0: [177d:a01f] type 00 class 0x028000 [ 12.284041] pci 0002:00:03.0: BAR 0: [mem 0x842000000000-0x84200000ffff 64bit] (from Enhanced Allocation, properties 0x0) [ 12.294994] pci 0002:00:03.0: BAR 2: [mem 0x842040000000-0x84207fffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 12.305948] pci 0002:00:03.0: BAR 4: [mem 0x842000f00000-0x842000ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 12.317949] pci 0002:01:00.0: [177d:a01e] type 00 class 0x020000 [ 12.323985] pci 0002:01:00.0: BAR 0: [mem 0x843000000000-0x84303fffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 12.334938] pci 0002:01:00.0: BAR 4: [mem 0x843060000000-0x8430600fffff 64bit] (from Enhanced Allocation, properties 0x0) [ 12.345893] pci 0002:01:00.0: VF BAR 0: [mem 0x8430a0000000-0x8430a01fffff 64bit] (from Enhanced Allocation, properties 0x4) [ 12.357105] pci 0002:01:00.0: VF BAR 4: [mem 0x8430e0000000-0x8430e01fffff 64bit] (from Enhanced Allocation, properties 0x4) [ 13.433187] pci 0002:01:00.0: VF(n) BAR0 space: [mem 0x8430a0000000-0x8430afffffff 64bit] (contains BAR0 for 128 VFs) [ 13.443809] pci 0002:01:00.0: VF(n) BAR4 space: [mem 0x8430e0000000-0x8430efffffff 64bit] (contains BAR4 for 128 VFs) [ 13.454648] pci 0002:01:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' [ 13.465574] pci_bus 0002:01: busn_res: [bus 01-1f] end is updated to 01 [ 13.472190] pci 0002:00:02.0: PCI bridge to [bus 01] [ 13.477335] pci-host-generic 84b000000000.pci: host bridge /soc@0/pci@84b000000000 ranges: [ 13.485621] pci-host-generic 84b000000000.pci: MEM 0x818000000000..0x81ffffffffff -> 0x818000000000 [ 13.495104] pci-host-generic 84b000000000.pci: Memory resource size exceeds max for 32 bits [ 13.503470] pci-host-generic 84b000000000.pci: ECAM at [mem 0x84b000000000-0x84b001ffffff] for [bus 00-1f] [ 13.513229] pci-host-generic 84b000000000.pci: PCI host bridge to bus 0003:00 [ 13.520359] pci_bus 0003:00: root bus resource [bus 00-1f] [ 13.525849] pci_bus 0003:00: root bus resource [mem 0x818000000000-0x81ffffffffff] [ 13.534511] pci_thunder_pem 88001f000000.pci: host bridge /soc@0/pci@87e0c0000000 ranges: [ 13.542702] pci_thunder_pem 88001f000000.pci: IO 0x883000000000..0x88300000ffff -> 0x0000000000 [ 13.551938] pci_thunder_pem 88001f000000.pci: MEM 0x881010000000..0x881fffffffff -> 0x0010000000 [ 13.561168] pci_thunder_pem 88001f000000.pci: MEM 0x882000000000..0x882fffffffff -> 0x1000000000 [ 13.570391] pci_thunder_pem 88001f000000.pci: MEM 0x87e0c0000000..0x87e0c0ffffff -> 0x87e0c0000000 [ 13.579792] pci_thunder_pem 88001f000000.pci: Memory resource size exceeds max for 32 bits [ 13.588105] pci_thunder_pem 88001f000000.pci: ECAM at [mem 0x88001f000000-0x880057ffffff] for [bus 1f-57] [ 13.597771] pci_thunder_pem 88001f000000.pci: PCI host bridge to bus 0004:1f [ 13.604826] pci_bus 0004:1f: root bus resource [bus 1f-57] [ 13.610303] pci_bus 0004:1f: root bus resource [io 0x0000-0xffff] [ 13.616480] pci_bus 0004:1f: root bus resource [mem 0x881010000000-0x881fffffffff] (bus address [0x10000000-0xfffffffff]) [ 13.627432] pci_bus 0004:1f: root bus resource [mem 0x882000000000-0x882fffffffff pref] (bus address [0x1000000000-0x1fffffffff]) [ 13.639078] pci_bus 0004:1f: root bus resource [mem 0x87e0c0000000-0x87e0c0ffffff] [ 13.646658] pci 0004:1f:00.0: [177d:a100] type 01 class 0x060400 [ 13.652666] pci 0004:1f:00.0: reg 0x10: [mem 0x00000000-0x00007fff 64bit pref] [ 13.659889] pci 0004:1f:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref] [ 13.666595] pci 0004:1f:00.0: enabling Extended Tags [ 13.671566] pci 0004:1f:00.0: BAR 0: [mem 0x87e0c0f00000-0x87e0c0ffffff 64bit] (from Enhanced Allocation, properties 0x0) [ 13.683635] pci 0004:1f:00.0: Primary bus is hard wired to 0 [ 13.689389] pci 0004:20:00.0: [1a03:1150] type 01 class 0x060400 [ 13.695445] pci 0004:20:00.0: Upstream bridge's Max Payload Size set to 128 (was 256, max 256) [ 13.704054] pci 0004:20:00.0: Max Payload Size set to 128 (was 128, max 128) [ 13.711097] pci 0004:20:00.0: enabling Extended Tags [ 13.716128] pci 0004:20:00.0: supports D1 D2 [ 13.720389] pci 0004:20:00.0: PME# supported from D0 D1 D2 D3hot D3cold [ 13.727169] pci 0004:20:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' [ 13.738158] pci_bus 0004:21: extended config space not accessible [ 13.744325] pci 0004:21:00.0: [1a03:2000] type 00 class 0x030000 [ 13.750340] pci 0004:21:00.0: reg 0x10: [mem 0x881010000000-0x881010ffffff] [ 13.757312] pci 0004:21:00.0: reg 0x14: [mem 0x881011000000-0x88101101ffff] [ 13.764275] pci 0004:21:00.0: reg 0x18: [io 0x0000-0x007f] [ 13.769872] pci 0004:21:00.0: BAR 0: assigned to efifb [ 13.775050] pci 0004:21:00.0: supports D1 D2 [ 13.779311] pci 0004:21:00.0: PME# supported from D0 D1 D2 D3hot D3cold [ 13.786048] pci 0004:21:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none [ 13.795399] pci_bus 0004:21: busn_res: [bus 21-57] end is updated to 21 [ 13.802010] pci_bus 0004:20: busn_res: [bus 20-57] end is updated to 21 [ 13.808643] pci 0004:1f:00.0: BAR 14: assigned [mem 0x881010000000-0x8810117fffff] [ 13.816214] pci 0004:1f:00.0: BAR 15: assigned [mem 0x882000000000-0x8820001fffff 64bit pref] [ 13.824736] pci 0004:1f:00.0: BAR 6: assigned [mem 0x881011800000-0x88101180ffff pref] [ 13.832646] pci 0004:1f:00.0: BAR 13: assigned [io 0x1000-0x2fff] [ 13.838826] pci 0004:20:00.0: BAR 14: assigned [mem 0x881010000000-0x8810117fffff] [ 13.846392] pci 0004:20:00.0: BAR 13: assigned [io 0x1000-0x1fff] [ 13.852566] pci 0004:21:00.0: BAR 0: assigned [mem 0x881010000000-0x881010ffffff] [ 13.860048] pci 0004:21:00.0: BAR 1: assigned [mem 0x881011000000-0x88101101ffff] [ 13.867529] pci 0004:21:00.0: BAR 2: assigned [io 0x1000-0x107f] [ 13.873620] pci 0004:20:00.0: PCI bridge to [bus 21] [ 13.878578] pci 0004:20:00.0: bridge window [io 0x1000-0x1fff] [ 13.884667] pci 0004:20:00.0: bridge window [mem 0x881010000000-0x8810117fffff] [ 13.892143] pci 0004:1f:00.0: PCI bridge to [bus 20-21] [ 13.897363] pci 0004:1f:00.0: bridge window [io 0x1000-0x2fff] [ 13.903452] pci 0004:1f:00.0: bridge window [mem 0x881010000000-0x8810117fffff] [ 13.910927] pci 0004:1f:00.0: bridge window [mem 0x882000000000-0x8820001fffff 64bit pref] [ 13.920145] pcieport 0004:1f:00.0: PME: Signaling with IRQ 28 [ 13.926239] pcieport 0004:1f:00.0: AER: enabled with IRQ 26 [ 13.931883] pcieport 0004:1f:00.0: pciehp: Slot #3 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl- IbPresDis- LLActRep+ [ 13.946670] efifb: probing for efifb [ 13.950303] efifb: framebuffer at 0x881010000000, using 1876k, total 1875k [ 13.957190] efifb: mode is 800x600x32, linelength=3200, pages=1 [ 13.963107] efifb: scrolling: redraw [ 13.966672] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 14.088101] Console: switching to colour frame buffer device 100x37 [ 14.209220] fb0: EFI VGA frame buffer device [ 14.219084] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled [ 14.232224] Serial: AMBA driver [ 14.235623] msm_serial: driver initialized [ 14.240473] arm-smmu: deprecated "mmu-masters" DT property in use; SMMU support unavailable [ 14.249687] arm-smmu 830000000000.smmu0: probing hardware configuration... [ 14.256564] arm-smmu 830000000000.smmu0: SMMUv2 with: [ 14.261607] arm-smmu 830000000000.smmu0: stage 1 translation [ 14.267347] arm-smmu 830000000000.smmu0: stage 2 translation [ 14.273083] arm-smmu 830000000000.smmu0: nested translation [ 14.278735] arm-smmu 830000000000.smmu0: non-coherent table walk [ 14.284822] arm-smmu 830000000000.smmu0: (IDR0.CTTW overridden by FW configuration) [ 14.292556] arm-smmu 830000000000.smmu0: stream matching with 128 register groups [ 14.300122] arm-smmu 830000000000.smmu0: 128 context banks (0 stage-2 only) [ 14.307168] arm-smmu 830000000000.smmu0: enabling workaround for Cavium erratum 27704 [ 14.315078] arm-smmu 830000000000.smmu0: Supported page sizes: 0x62215000 [ 14.321944] arm-smmu 830000000000.smmu0: Stage-1: 48-bit VA -> 48-bit IPA [ 14.328812] arm-smmu 830000000000.smmu0: Stage-2: 48-bit IPA -> 48-bit PA [ 14.336665] arm-smmu 831000000000.smmu1: probing hardware configuration... [ 14.343544] arm-smmu 831000000000.smmu1: SMMUv2 with: [ 14.348587] arm-smmu 831000000000.smmu1: stage 1 translation [ 14.354326] arm-smmu 831000000000.smmu1: stage 2 translation [ 14.360062] arm-smmu 831000000000.smmu1: nested translation [ 14.365715] arm-smmu 831000000000.smmu1: non-coherent table walk [ 14.371799] arm-smmu 831000000000.smmu1: (IDR0.CTTW overridden by FW configuration) [ 14.379538] arm-smmu 831000000000.smmu1: stream matching with 128 register groups [ 14.387128] arm-smmu 831000000000.smmu1: 128 context banks (0 stage-2 only) [ 14.394191] arm-smmu 831000000000.smmu1: enabling workaround for Cavium erratum 27704 [ 14.402099] arm-smmu 831000000000.smmu1: Supported page sizes: 0x62215000 [ 14.408969] arm-smmu 831000000000.smmu1: Stage-1: 48-bit VA -> 48-bit IPA [ 14.415839] arm-smmu 831000000000.smmu1: Stage-2: 48-bit IPA -> 48-bit PA [ 14.423693] arm-smmu 832000000000.smmu2: probing hardware configuration... [ 14.430562] arm-smmu 832000000000.smmu2: SMMUv2 with: [ 14.435609] arm-smmu 832000000000.smmu2: stage 1 translation [ 14.441345] arm-smmu 832000000000.smmu2: stage 2 translation [ 14.447084] arm-smmu 832000000000.smmu2: nested translation [ 14.452733] arm-smmu 832000000000.smmu2: non-coherent table walk [ 14.458820] arm-smmu 832000000000.smmu2: (IDR0.CTTW overridden by FW configuration) [ 14.466557] arm-smmu 832000000000.smmu2: stream matching with 128 register groups [ 14.474122] arm-smmu 832000000000.smmu2: 128 context banks (0 stage-2 only) [ 14.481162] arm-smmu 832000000000.smmu2: enabling workaround for Cavium erratum 27704 [ 14.489072] arm-smmu 832000000000.smmu2: Supported page sizes: 0x62215000 [ 14.495940] arm-smmu 832000000000.smmu2: Stage-1: 48-bit VA -> 48-bit IPA [ 14.502806] arm-smmu 832000000000.smmu2: Stage-2: 48-bit IPA -> 48-bit PA [ 14.510648] arm-smmu 833000000000.smmu3: probing hardware configuration... [ 14.517527] arm-smmu 833000000000.smmu3: SMMUv2 with: [ 14.522570] arm-smmu 833000000000.smmu3: stage 1 translation [ 14.528309] arm-smmu 833000000000.smmu3: stage 2 translation [ 14.534049] arm-smmu 833000000000.smmu3: nested translation [ 14.539698] arm-smmu 833000000000.smmu3: non-coherent table walk [ 14.545785] arm-smmu 833000000000.smmu3: (IDR0.CTTW overridden by FW configuration) [ 14.553523] arm-smmu 833000000000.smmu3: stream matching with 128 register groups [ 14.561085] arm-smmu 833000000000.smmu3: 128 context banks (0 stage-2 only) [ 14.568136] arm-smmu 833000000000.smmu3: enabling workaround for Cavium erratum 27704 [ 14.576049] arm-smmu 833000000000.smmu3: Supported page sizes: 0x62215000 [ 14.582914] arm-smmu 833000000000.smmu3: Stage-1: 48-bit VA -> 48-bit IPA [ 14.589786] arm-smmu 833000000000.smmu3: Stage-2: 48-bit IPA -> 48-bit PA [ 14.603689] ahci 0001:00:08.0: version 3.0 [ 14.607912] ahci 0001:00:08.0: SSS flag set, parallel bus scan disabled [ 14.614547] ahci 0001:00:08.0: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode [ 14.622633] ahci 0001:00:08.0: flags: 64bit ncq sntf ilck stag pm led clo only pmp fbs pio slum part ccc apst [ 14.632639] ahci 0001:00:08.0: port 0 is not capable of FBS [ 14.638786] scsi host0: ahci [ 14.641897] ata1: SATA max UDMA/133 abar m2097152@0x814000000000 port 0x814000000100 irq 29 [ 14.650452] ahci 0001:00:09.0: SSS flag set, parallel bus scan disabled [ 14.657082] ahci 0001:00:09.0: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode [ 14.665171] ahci 0001:00:09.0: flags: 64bit ncq sntf ilck stag pm led clo only pmp fbs pio slum part ccc apst [ 14.675176] ahci 0001:00:09.0: port 0 is not capable of FBS [ 14.681297] scsi host1: ahci [ 14.684345] ata2: SATA max UDMA/133 abar m2097152@0x815000000000 port 0x815000000100 irq 30 [ 14.692923] ahci 0001:00:0a.0: SSS flag set, parallel bus scan disabled [ 14.699551] ahci 0001:00:0a.0: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode [ 14.707641] ahci 0001:00:0a.0: flags: 64bit ncq sntf ilck stag pm led clo only pmp fbs pio slum part ccc apst [ 14.717641] ahci 0001:00:0a.0: port 0 is not capable of FBS [ 14.723744] scsi host2: ahci [ 14.726771] ata3: SATA max UDMA/133 abar m2097152@0x816000000000 port 0x816000000100 irq 31 [ 14.735355] ahci 0001:00:0b.0: SSS flag set, parallel bus scan disabled [ 14.741970] ahci 0001:00:0b.0: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode [ 14.750070] ahci 0001:00:0b.0: flags: 64bit ncq sntf ilck stag pm led clo only pmp fbs pio slum part ccc apst [ 14.760071] ahci 0001:00:0b.0: port 0 is not capable of FBS [ 14.766183] scsi host3: ahci [ 14.769210] ata4: SATA max UDMA/133 abar m2097152@0x817000000000 port 0x817000000100 irq 32 [ 14.778188] libphy: Fixed MDIO Bus: probed [ 14.782666] mousedev: PS/2 mouse device common for all mice [ 14.790737] rtc-efi rtc-efi.0: registered as rtc0 [ 14.796515] rtc-efi rtc-efi.0: setting system clock to 2021-09-01T11:56:36 UTC (1630497396) [ 14.807192] ledtrig-cpu: registered to indicate activity on CPUs [ 14.813577] hid: raw HID events driver (C) Jiri Kosina [ 14.820151] Unable to handle kernel paging request at virtual address ffff8000156dc028 [ 14.828064] Mem abort info: [ 14.830847] ESR = 0x96000007 [ 14.833891] EC = 0x25: DABT (current EL), IL = 32 bits [ 14.839194] SET = 0, FnV = 0 [ 14.842238] EA = 0, S1PTW = 0 [ 14.845369] Data abort info: [ 14.848238] ISV = 0, ISS = 0x00000007 [ 14.852064] CM = 0, WnR = 0 [ 14.855022] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000001f891e5000 [ 14.861714] [ffff8000156dc028] pgd=1000001fff0ff803, p4d=1000001fff0ff803, pud=1000001fff0fe803, pmd=10000001034f3003, pte=0000000000000000 [ 14.874237] Internal error: Oops: 96000007 [#1] SMP [ 14.879107] Modules linked in: [ 14.882153] CPU: 14 PID: 395 Comm: modprobe Not tainted 5.13.12-2-default #1 openSUSE Tumbleweed [ 14.890931] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 5.11 12/12/2012 [ 14.899272] pstate: 204000c5 (nzCv daIF +PAN -UAO -TCO BTYPE=--) [ 14.905270] pc : load_elf_binary+0x664/0x1810 [ 14.909627] lr : load_elf_binary+0xaf4/0x1810 [ 14.913975] sp : ffff8000156dbcd0 [ 14.917280] x29: 0000000000000000 x28: ffff000102df5e00 x27: ffff00010148de00 [ 14.924413] x26: ffff8000156dbd9c x25: 0000aaaad0d80000 x24: ffff000102df7000 [ 14.931545] x23: 0000000000040130 x22: ffff000800881b00 x21: ffff800012515e28 [ 14.938676] x20: ffff80001044ce90 x19: ffff8000156dbdc0 x18: 0000000000000014 [ 14.945808] x17: 0000000077b8d053 x16: 000000001ceb51b0 x15: 0001400000000000 [ 14.952940] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 [ 14.960071] x11: ffff000800883dd0 x10: 0000000000000000 x9 : 0000aaabaaaaaa9c [ 14.967203] x8 : ffff000800883838 x7 : 0000000000000030 x6 : 0000000000000024 [ 14.974335] x5 : ffff8000157009c0 x4 : 0000000000000000 x3 : 0000001f891e5000 [ 14.981466] x2 : 0000000000000000 x1 : 0000000000000a80 x0 : ffff8000156dc028 [ 14.988598] Call trace: [ 14.991036] load_elf_binary+0x664/0x1810 [ 14.995041] Code: 14000004 9100e000 eb0000bf 540006a0 (b9400002) [ 15.001129] ---[ end trace f8304eb4d2aa20ef ]--- [ 15.143143] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 15.150200] ata1.00: ATA-8: WDC WD5003ABYZ-011FA0, 01.01S03, max UDMA/133 [ 15.156992] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 32), AA [ 15.164787] ata1.00: configured for UDMA/133 [ 15.169403] scsi 0:0:0:0: Direct-Access ATA WDC WD5003ABYZ-0 1S03 PQ: 0 ANSI: 5 [ 15.178047] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB) [ 15.185618] sd 0:0:0:0: [sda] Write Protect is off [ 15.190405] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 15.195502] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 15.254020] sda: sda1 sda2 sda3 [ 15.273141] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 15.333224] sd 0:0:0:0: [sda] Attached SCSI disk [ 15.361935] ata4.00: ATA-10: WDC WD2004FBYZ-01YCBB0, RR01, max UDMA/133 [ 15.368555] ata4.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA [ 15.389299] ata4.00: configured for UDMA/133 [ 15.793137] ata2: failed to resume link (SControl 301) [ 15.798276] ata2: SATA link down (SStatus 0 SControl 300) [ 15.833136] ata3: failed to resume link (SControl 301) [ 15.838275] ata3: SATA link down (SStatus 0 SControl 300) [ 15.843956] scsi 3:0:0:0: Direct-Access ATA WDC WD2004FBYZ-0 RR01 PQ: 0 ANSI: 5 [ 15.852521] sd 3:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) [ 15.860351] sd 3:0:0:0: [sdb] Write Protect is off [ 15.865149] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 15.870238] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 15.943548] sdb: sdb1 [ 16.043225] sd 3:0:0:0: [sdb] Attached SCSI disk -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1189993] New: Btrfs hogged one of the CPU cores for more than 30 minutes after a reboot (5.13.12-2-default, 33df9c6)
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1189993 Bug ID: 1189993 Summary: Btrfs hogged one of the CPU cores for more than 30 minutes after a reboot (5.13.12-2-default, 33df9c6) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852174 --> https://bugzilla.suse.com/attachment.cgi?id=852174&action=edit dmesg, SysRq-L, perf data, lsblk -f, snapper list My CPU fan had a long high-intensity exercise this morning. The root cause turned out to be a kworker thread doing "btrfs_preempt_reclaim_metadata_space". The offending thread identification is "kworker/u16:11". I've collected some data bits (dmesg, SysRq-L, perf data) during the event. It is unclear to me, however, what triggered this long-running FS maintenance and how I could stop it in case I needed to - i.e. if the laptop ran battery or if I sat in a quiet room where the CPU fan disturbance would be unacceptable. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1189881] New: warning: /var/tmp/weak-modules2.7WPIFB/symvers-5.13.12-2-default not available
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1189881 Bug ID: 1189881 Summary: warning: /var/tmp/weak-modules2.7WPIFB/symvers-5.13.12-2-defaul t not available 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: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running zypper dup on my Tumbleweed machine, I noticed the following in the logs: (121/203) Installing: kernel-default-5.13.12-2.1.x86_64 ....[done] Additional rpm output: warning: /var/tmp/weak-modules2.7WPIFB/symvers-5.13.12-2-default not available It is probably benign, but still a bit confusing/worrisome. What do we want to tell users here (that would be actionable)? And/or is this indicative of some problem with the upgrade as such? -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1188940] New: bluetooth adapter fails to power on
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188940 Bug ID: 1188940 Summary: bluetooth adapter fails to power on 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- hramrach@naga:~> bluetoothctl Agent registered [CHG] Controller 00:E0:3C:87:B8:03 Pairable: yes [bluetooth]# power on Failed to set power on: org.bluez.Error.Failed [bluetooth]# power on Failed to set power on: org.bluez.Error.Busy [bluetooth]# power on Failed to set power on: org.bluez.Error.Busy [bluetooth]# power on Failed to set power on: org.bluez.Error.Busy [bluetooth]# -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1188889] New: crash is failing with 5.13 kernels
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188889 Bug ID: 1188889 Summary: crash is failing with 5.13 kernels 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: hare(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When trying to run crash on a 5.13 or later kernel dump I get the error message: crash: invalid structure member offset: task_struct_state FILE: task.c LINE: 5916 FUNCTION: task_state() [/usr/bin/crash] error trace: 559027f7b785 => 559027f7b54d => 559027fffe94 => 559027fffe0d This has been fixed by upstream commit d6b4f36d6b22b70fb14e692f36d20910ef5563c1. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1184718] New: systemtap simple helloworld script execution fails in Tumbleweed
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1184718 Bug ID: 1184718 Summary: systemtap simple helloworld script execution fails in Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: vasilios.anastasiadis(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 848350 --> https://bugzilla.suse.com/attachment.cgi?id=848350&action=edit Related errors Unable to run a simple systemtap helloworld.stp example script (provided with systemtap-docs) in Tumbleweed. It works fine in SLE versions 12sp2-15sp3. Steps to reproduce: - Install systemtap, systemtap-docs, kernel-default-devel - Run: stap /usr/share/doc/packages/systemtap/examples/general/helloworld.stp See attached file for errors. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1188712] New: VDSO change on PPC causes random segfaults in Go applications
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188712 Bug ID: 1188712 Summary: VDSO change on PPC causes random segfaults in Go applications Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jkowalczyk(a)suse.com Found By: --- Blocker: --- https://lwn.net/ml/linux-kernel/cover.1601365869.git.christophe.leroy@csgro… changed the implementation of the VDSO from a PowerPC specific one to the generic C version. Apparently executables built with Go before 1.17 implicitly relied on the fact that the VDSO did not mangle r30, but with the generic C implementation it now does. This leads to random crashes in Go executables. This is fixed with https://go-review.googlesource.com/c/go/+/334410/1 and I submitted this to our go1.16 package with https://build.opensuse.org/request/show/907807. However, all executables built with a compiler which doesn't include that will not work on kernel >= 5.13. This probably affects containerized workloads as well. So it might be useful to raise awareness of this issue. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kernel-bugs] [Bug 1173891] New: BUG: kernel NULL pointer dereference, address: 0000000d during install on i686 notebook
by bugzilla_noreply＠suse.com 20 Jan '23

20 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1173891 Bug ID: 1173891 Summary: BUG: kernel NULL pointer dereference, address: 0000000d during install on i686 notebook Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i686 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: richard(a)nod.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- While installing Tumbleweed (openSUSE-Tumbleweed-NET-i586-Snapshot20200701-Media.iso) on my old notbook I got the following crash: ---cut--- [ 3448.675690] BUG: kernel NULL pointer dereference, address: 0000000d [ 3448.675713] #PF: supervisor read access in kernel mode [ 3448.675723] #PF: error_code(0x0000) - not-present page [ 3448.675733] *pde = 00000000 [ 3448.675746] Oops: 0000 [#1] SMP [ 3448.675759] CPU: 1 PID: 13684 Comm: rpm Not tainted 5.7.5-1-default #1 openSUSE Tumbleweed (unreleased) [ 3448.675771] Hardware name: Dell Inc. Latitude 2100 /0W785N, BIOS A01 06/02/2009 [ 3448.675792] EIP: __vfs_write+0x83/0x200 [ 3448.675805] Code: 00 00 8b 73 24 89 55 b0 89 4d b4 89 f0 89 75 ac c1 e8 09 83 e0 02 81 e6 00 40 00 00 0f 85 fd 00 00 00 8b b3 a4 00 00 00 8b 36 <f6> 46 0d 20 0f 85 eb 00 00 00 f7 45 ac 00 10 00 00 75 15 8b b3 a4 [ 3448.675825] EAX: 00000000 EBX: ddb3a180 ECX: 00005e44 EDX: bfd3af6c [ 3448.675836] ESI: 00000000 EDI: c28fdf7c EBP: c28fdf4c ESP: c28fdef4 [ 3448.675848] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010246 [ 3448.675859] CR0: 80050033 CR2: 0000000d CR3: 32744000 CR4: 000006d0 [ 3448.675868] Call Trace: [ 3448.675885] ? apparmor_file_permission+0x56/0x160 [ 3448.675902] ? security_file_permission+0x2c/0x150 [ 3448.675916] ? rw_verify_area+0x44/0x90 [ 3448.675928] vfs_write+0x9b/0x1c0 [ 3448.675942] ? ktime_get_real_ts64+0x4f/0x150 [ 3448.675955] ksys_write+0x58/0xd0 [ 3448.675968] __ia32_sys_write+0x15/0x20 [ 3448.675982] do_int80_syscall_32+0x41/0x120 [ 3448.675996] entry_INT80_32+0xfc/0xfc [ 3448.676007] EIP: 0xb7d71522 [ 3448.676018] Code: 90 66 90 66 90 66 90 90 56 53 83 ec 14 8b 5c 24 20 8b 4c 24 24 8b 54 24 28 65 a1 0c 00 00 00 85 c0 75 1d b8 04 00 00 00 cd 80 <89> c3 3d 00 f0 ff ff 77 4d 83 c4 14 89 d8 5b 5e c3 8d 74 26 00 90 [ 3448.676039] EAX: ffffffda EBX: 00000009 ECX: bfd3af6c EDX: 00005e44 [ 3448.676050] ESI: 02486bf0 EDI: b7e5ba90 EBP: 02481c50 ESP: bfd3aea0 [ 3448.676061] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000246 [ 3448.676077] ? nmi+0xc5/0x2b0 [ 3448.676085] Modules linked in: nls_utf8 isofs usbhid parport_pc parport btrfs xor raid6_pq libcrc32c dm_multipath dm_mod 8021q garp mrp stp llc arc4 fan nfs lockd grace fscache nls_iso8859_1 nls_cp437 af_packet sg st sr_mod cdrom iscsi_ibft iscsi_boot_sysfs sunrpc b43 cordic bcma mac80211 cfg80211 i915 ums_realtek uas usb_storage libarc4 dell_laptop gpio_ich ledtrig_audio dell_wmi rfkill sparse_keymap wmi_bmof dell_smbios dell_wmi_descriptor dcdbas i2c_algo_bit ahci drm_kms_helper libahci syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 cec joydev libata rc_core pcspkr serio_raw i2c_i801 libphy lpc_ich drm uhci_hcd ssb ehci_pci ehci_hcd mmc_core usbcore ptp pps_core hwmon pcmcia pcmcia_core thermal wmi tiny_power_button battery button ac video acpi_cpufreq scsi_dh_rdac scsi_dh_emc scsi_dh_alua edd squashfs loop [ 3448.676246] CR2: 000000000000000d [ 3448.676258] ---[ end trace 2e9b3e59a1582583 ]--- ---cut--- Filesystem is btrfs. Thanks, //richard -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1201384] New: less does not start on serial port
by bugzilla_noreply＠suse.com 17 Jan '23

17 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1201384 Bug ID: 1201384 Summary: less does not start on serial port 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- strace less mmc0.txt execve("/usr/bin/less", ["less", "mmc0.txt"], 0xffffcc58c1a8 /* 51 vars */) = 0 brk(NULL) = 0xaaaaf2288000 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffff8b72a000 faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=20583, ...}, AT_EMPTY_PATH) = 0 mmap(NULL, 20583, PROT_READ, MAP_PRIVATE, 3, 0) = 0xffff8b724000 close(3) = 0 openat(AT_FDCWD, "/lib64/libtinfo.so.6", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832 newfstatat(3, "", {st_mode=S_IFREG|0755, st_size=231504, ...}, AT_EMPTY_PATH) = 0 mmap(NULL, 360832, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffff8b698000 mmap(0xffff8b6a0000, 295296, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0xffff8b6a0000 munmap(0xffff8b698000, 32768) = 0 munmap(0xffff8b6e9000, 29056) = 0 mprotect(0xffff8b6c9000, 90112, PROT_NONE) = 0 mmap(0xffff8b6df000, 40960, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2f000) = 0xffff8b6df000 close(3) = 0 openat(AT_FDCWD, "/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0\220\264\2\0\0\0\0\0"..., 832) = 832 pread64(3, "\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\305\350$SK\4\324\342\230\240\317b\vA3\260"..., 68, 768) = 68 newfstatat(3, "", {st_mode=S_IFREG|0755, st_size=2118080, ...}, AT_EMPTY_PATH) = 0 mmap(NULL, 1895216, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffff8b4d1000 mmap(0xffff8b4e0000, 1829680, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0xffff8b4e0000 munmap(0xffff8b4d1000, 61440) = 0 munmap(0xffff8b69f000, 2864) = 0 mprotect(0xffff8b673000, 106496, PROT_NONE) = 0 mmap(0xffff8b68d000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x19d000) = 0xffff8b68d000 mmap(0xffff8b693000, 47920, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xffff8b693000 close(3) = 0 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffff8b722000 set_tid_address(0xffff8b7220f0) = 6076 set_robust_list(0xffff8b722100, 24) = 0 rseq(0xffff8b7227c0, 0x20, 0, 0xd428bc00) = 0 mprotect(0xffff8b68d000, 12288, PROT_READ) = 0 mprotect(0xffff8b6df000, 4096, PROT_READ) = 0 mprotect(0xaaaabe98f000, 4096, PROT_READ) = 0 mprotect(0xffff8b72f000, 8192, PROT_READ) = 0 prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0 munmap(0xffff8b724000, 20583) = 0 ioctl(1, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 getrandom("\x63\x32\x32\x25\xf1\x9e\x1e\x9a", 8, GRND_NONBLOCK) = 8 brk(NULL) = 0xaaaaf2288000 brk(0xaaaaf22a9000) = 0xaaaaf22a9000 openat(AT_FDCWD, "/usr/bin/.sysless", O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/etc/syslesskey", O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/etc/sysless", O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/root/.lesskey", O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/etc/lesskey.bin", O_RDONLY) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=589, ...}, AT_EMPTY_PATH) = 0 lseek(3, 0, SEEK_SET) = 0 read(3, "\0M+Gc\33\2\33[A\0\2\33[B\0\f\33O5A\0\2\33O5B\0\f\33O5"..., 589) = 589 close(3) = 0 ioctl(1, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 getuid() = 0 geteuid() = 0 getgid() = 0 getegid() = 0 getuid() = 0 newfstatat(AT_FDCWD, "/etc/terminfo", {st_mode=S_IFDIR|0755, st_size=4096, ...}, 0) = 0 newfstatat(AT_FDCWD, "/usr/share/terminfo", {st_mode=S_IFDIR|0755, st_size=4096, ...}, 0) = 0 faccessat(AT_FDCWD, "/etc/terminfo/s/screen", R_OK) = -1 ENOENT (No such file or directory) faccessat(AT_FDCWD, "/usr/share/terminfo/s/screen", R_OK) = 0 openat(AT_FDCWD, "/usr/share/terminfo/s/screen", O_RDONLY) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=1607, ...}, AT_EMPTY_PATH) = 0 read(3, "\32\0011\0+\0\20\0i\1\265\2screen|VT 100/ANSI X"..., 32768) = 1607 read(3, "", 28672) = 0 close(3) = 0 ioctl(1, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 ioctl(1, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 ioctl(1, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 ioctl(1, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 ioctl(1, TIOCGWINSZ, {ws_row=41, ws_col=157, ws_xpixel=0, ws_ypixel=0}) = 0 ioctl(2, TIOCGWINSZ, {ws_row=41, ws_col=157, ws_xpixel=0, ws_ypixel=0}) = 0 openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=2940, ...}, AT_EMPTY_PATH) = 0 read(3, "# Locale name alias data base.\n#"..., 4096) = 2940 read(3, "", 4096) = 0 close(3) = 0 openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=353616, ...}, AT_EMPTY_PATH) = 0 mmap(NULL, 353616, PROT_READ, MAP_PRIVATE, 3, 0) = 0xffff8b489000 close(3) = 0 openat(AT_FDCWD, "/usr/lib64/gconv/gconv-modules.cache", O_RDONLY) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=26988, ...}, AT_EMPTY_PATH) = 0 mmap(NULL, 26988, PROT_READ, MAP_SHARED, 3, 0) = 0xffff8b71b000 close(3) = 0 futex(0xffff8b69236c, FUTEX_WAKE_PRIVATE, 2147483647) = 0 openat(AT_FDCWD, "/root/.lesshst", O_RDONLY) = 3 close(3) = 0 openat(AT_FDCWD, "/root/.lesshst", O_RDONLY) = 3 newfstatat(3, "", {st_mode=S_IFREG|0600, st_size=20, ...}, AT_EMPTY_PATH) = 0 read(3, ".less-history-file:\n", 4096) = 20 read(3, "", 4096) = 0 close(3) = 0 getcwd("/root", 1024) = 6 readlinkat(AT_FDCWD, "/root/mmc0.txt", 0xfffff3f0b0f0, 1023) = -1 EINVAL (Invalid argument) getcwd("/root", 1024) = 6 readlinkat(AT_FDCWD, "/root/mmc0.txt", 0xfffff3f0b0f0, 1023) = -1 EINVAL (Invalid argument) ioctl(2, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 ioctl(2, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 newfstatat(2, "", {st_mode=S_IFCHR|0620, st_rdev=makedev(0x4, 0x42), ...}, AT_EMPTY_PATH) = 0 readlinkat(AT_FDCWD, "/proc/self/fd/2", "/dev/ttyS2", 4095) = 10 newfstatat(AT_FDCWD, "/dev/ttyS2", {st_mode=S_IFCHR|0620, st_rdev=makedev(0x4, 0x42), ...}, 0) = 0 openat(AT_FDCWD, "/dev/ttyS2", O_RDONLY cat /proc/6076/stack [<0>] tty_port_block_til_ready+0x124/0x344 [<0>] tty_port_open+0xc8/0x26c [<0>] uart_open+0x28/0x40 [<0>] tty_open+0x140/0x670 [<0>] chrdev_open+0xcc/0x21c [<0>] do_dentry_open+0x1c0/0x38c [<0>] vfs_open+0x38/0x44 [<0>] path_openat+0xa50/0x108c [<0>] do_filp_open+0x8c/0x140 [<0>] do_sys_openat2+0xbc/0x174 [<0>] __arm64_sys_openat+0x70/0xb0 [<0>] invoke_syscall+0x78/0x100 [<0>] el0_svc_common.constprop.0+0x18c/0x190 [<0>] do_el0_svc+0x30/0x90 [<0>] el0_svc+0x34/0x130 [<0>] el0t_64_sync_handler+0x10c/0x140 [<0>] el0t_64_sync+0x1a0/0x1a4 Linux PinebookPro 5.18.9-1-default #1 SMP PREEMPT_DYNAMIC Sun Jul 3 08:04:03 UTC 2022 (0e67dc1) aarch64 aarch64 aarch64 GNU/Linux -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1196778] New: amdgpu bug
by bugzilla_noreply＠suse.com 15 Jan '23

15 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1196778 Bug ID: 1196778 Summary: amdgpu bug Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: james(a)sevener.us QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When plugging my laptop (Lenovo E14 Gen3, Ryzen 5500U) amdgpu spams the journal, and I can no longer run two screens at 2560x1440. This started on 2/15/2022 after updating. I have been able to get both screens working now, but I have to run one at 1080p and one at 1440p. It used to work great with both at 1440p. In the one log file (it's rolled a few times) I got the following which seems to show once per error. grep -c drivers/gpu/drm/drm_dp_mst_topology.c messages 177772 Full error: 2022-02-18T09:08:02.625936-05:00 localhost kernel: [ 91.051548][ T5215] ------------[ cut here ]------------ 2022-02-18T09:08:02.625954-05:00 localhost kernel: [ 91.051554][ T5215] WARNING: CPU: 10 PID: 5215 at drivers/gpu/drm/drm_dp_mst_topology.c:4404 drm_dp_atomic_find_vcpi_slots.cold+0x0/0x24 2022-02-18T09:08:02.625958-05:00 localhost kernel: [ 91.051567][ T5215] Modules linked in: rfcomm xt_CHECKSUM xt_conntrack ipt_REJECT xt_tcpudp nf_nat_tftp nf_conntrack_tftp bridge stp llc xt_mark xt_MASQUERADE xt_comment tun nft_objref af_packet nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set nfnetlink snd_usb_audio snd_usbmidi_lib ebtable_filter snd_rawmidi snd_seq_device ebtables ip6table_filter ip6_tables iptable_filter bpfilter cmac algif_hash algif_skcipher af_alg bnep dmi_sysfs r8153_ecm cdc_ether usbnet r8152 mii btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ecdh_generic mc intel_rapl_msr intel_rapl_common edac_mce_amd 2022-02-18T09:08:02.625960-05:00 localhost kernel: [ 91.051650][ T5215] kvm_amd kvm irqbypass snd_ctl_led snd_hda_codec_realtek pcspkr snd_hda_codec_generic snd_hda_codec_hdmi joydev snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_pci_acp6x r8169 snd_hwdep thinkpad_acpi snd_pcm snd_pci_acp5x realtek mdio_devres think_lmi snd_rn_pci_acp3x ledtrig_audio efi_pstore firmware_attributes_class wmi_bmof k10temp snd_timer i2c_piix4 snd_pci_acp3x libphy platform_profile snd soundcore tiny_power_button ac ucsi_acpi i2c_scmi typec_ucsi typec roles acpi_cpufreq button nls_iso8859_1 nls_cp437 vfat fat fuse configfs ip_tables x_tables dm_crypt essiv authenc trusted asn1_encoder tee hid_logitech_hidpp hid_logitech_dj hid_generic usbhid rtw89pci(OE) rtw89core(OE) amdgpu crct10dif_pclmul crc32_pclmul ghash_clmulni_intel mac80211 libarc4 xhci_pci xhci_pci_renesas cfg80211 xhci_hcd aesni_intel crypto_simd cryptd usbcore drm_ttm_helper nvme ttm serio_raw ccp iommu_v2 nvme_core sp5100_tco gpu_sched rfkill wmi battery 2022-02-18T09:08:02.625962-05:00 localhost kernel: [ 91.051742][ T5215] video btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs 2022-02-18T09:08:02.625964-05:00 localhost kernel: [ 91.051759][ T5215] CPU: 10 PID: 5215 Comm: kwin_wayland Tainted: G OE 5.16.8-1-default #1 openSUSE Tumbleweed 257f8f36371552cd38032922fd021edb6811ecdc 2022-02-18T09:08:02.625967-05:00 localhost kernel: [ 91.051766][ T5215] Hardware name: LENOVO 20Y7003EUS/20Y7003EUS, BIOS R1OET31W (1.10 ) 11/29/2021 2022-02-18T09:08:02.625968-05:00 localhost kernel: [ 91.051770][ T5215] RIP: 0010:drm_dp_atomic_find_vcpi_slots.cold+0x0/0x24 2022-02-18T09:08:02.625970-05:00 localhost kernel: [ 91.051776][ T5215] Code: 28 ea 57 a4 e8 a4 7c fe ff 49 8b 45 58 48 89 ea 48 c7 c6 70 88 90 a4 48 8b 78 08 e8 78 14 00 00 b8 f4 ff ff ff e9 55 fc c5 ff <0f> 0b 49 8b 46 58 4c 89 e2 48 c7 c6 a0 88 90 a4 41 bf ea ff ff ff 2022-02-18T09:08:02.625972-05:00 localhost kernel: [ 91.051779][ T5215] RSP: 0018:ffffc35b81daf790 EFLAGS: 00010246 2022-02-18T09:08:02.625973-05:00 localhost kernel: [ 91.051783][ T5215] RAX: ffff9f65d94afd98 RBX: ffff9f65d94afd80 RCX: 0000000000000000 2022-02-18T09:08:02.625974-05:00 localhost kernel: [ 91.051786][ T5215] RDX: ffff9f65d94afcc0 RSI: ffff9f661018a500 RDI: ffff9f6660a7d580 2022-02-18T09:08:02.625976-05:00 localhost kernel: [ 91.051788][ T5215] RBP: ffff9f65d94af508 R08: 0000000000000013 R09: ffffc35b81daf8a8 2022-02-18T09:08:02.625977-05:00 localhost kernel: [ 91.051790][ T5215] R10: 00000000000001b5 R11: 0000000000000000 R12: ffff9f65d3d8b800 2022-02-18T09:08:02.625979-05:00 localhost kernel: [ 91.051792][ T5215] R13: ffff9f65d94af500 R14: ffff9f661018a500 R15: 0000000000000013 2022-02-18T09:08:02.625980-05:00 localhost kernel: [ 91.051794][ T5215] FS: 00007fa96d006e40(0000) GS:ffff9f6860080000(0000) knlGS:0000000000000000 2022-02-18T09:08:02.625981-05:00 localhost kernel: [ 91.051798][ T5215] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2022-02-18T09:08:02.625982-05:00 localhost kernel: [ 91.051800][ T5215] CR2: 00007fa95c50d0e0 CR3: 000000014a278000 CR4: 0000000000350ee0 2022-02-18T09:08:02.626005-05:00 localhost kernel: [ 91.051803][ T5215] Call Trace: 2022-02-18T09:08:02.626007-05:00 localhost kernel: [ 91.051806][ T5215] <TASK> 2022-02-18T09:08:02.626008-05:00 localhost kernel: [ 91.051812][ T5215] ? dc_link_should_enable_fec+0x3d/0x60 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630215-05:00 localhost kernel: [ 91.052250][ T5215] compute_mst_dsc_configs_for_link+0x7dd/0xa20 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630227-05:00 localhost kernel: [ 91.052432][ T5215] compute_mst_dsc_configs_for_state+0x1eb/0x340 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630230-05:00 localhost kernel: [ 91.052605][ T5215] amdgpu_dm_atomic_check+0xce4/0xf00 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630232-05:00 localhost kernel: [ 91.052777][ T5215] drm_atomic_check_only+0x595/0x8d0 2022-02-18T09:08:02.630234-05:00 localhost kernel: [ 91.052781][ T5215] drm_mode_atomic_ioctl+0x73c/0xaf0 2022-02-18T09:08:02.630236-05:00 localhost kernel: [ 91.052784][ T5215] ? drm_plane_get_damage_clips.cold+0x1c/0x1c 2022-02-18T09:08:02.630237-05:00 localhost kernel: [ 91.052788][ T5215] ? drm_atomic_set_property+0xb50/0xb50 2022-02-18T09:08:02.630238-05:00 localhost kernel: [ 91.052789][ T5215] drm_ioctl_kernel+0xb0/0x140 2022-02-18T09:08:02.630239-05:00 localhost kernel: [ 91.052794][ T5215] drm_ioctl+0x220/0x3e0 2022-02-18T09:08:02.630241-05:00 localhost kernel: [ 91.052796][ T5215] ? drm_atomic_set_property+0xb50/0xb50 2022-02-18T09:08:02.630243-05:00 localhost kernel: [ 91.052797][ T5215] ? amdgpu_drm_ioctl+0x6a/0x80 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630246-05:00 localhost kernel: [ 91.052938][ T5215] amdgpu_drm_ioctl+0x49/0x80 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630247-05:00 localhost kernel: [ 91.053078][ T5215] __x64_sys_ioctl+0x82/0xb0 2022-02-18T09:08:02.630249-05:00 localhost kernel: [ 91.053081][ T5215] do_syscall_64+0x5c/0x80 2022-02-18T09:08:02.630250-05:00 localhost kernel: [ 91.053084][ T5215] ? __x64_sys_ioctl+0x9a/0xb0 2022-02-18T09:08:02.630251-05:00 localhost kernel: [ 91.053085][ T5215] ? syscall_exit_to_user_mode+0x18/0x40 2022-02-18T09:08:02.630252-05:00 localhost kernel: [ 91.053088][ T5215] ? do_syscall_64+0x69/0x80 2022-02-18T09:08:02.630254-05:00 localhost kernel: [ 91.053089][ T5215] ? do_syscall_64+0x69/0x80 2022-02-18T09:08:02.630265-05:00 localhost kernel: [ 91.053091][ T5215] ? do_syscall_64+0x69/0x80 2022-02-18T09:08:02.630267-05:00 localhost kernel: [ 91.053092][ T5215] ? exc_page_fault+0x68/0x150 2022-02-18T09:08:02.630268-05:00 localhost kernel: [ 91.053094][ T5215] entry_SYSCALL_64_after_hwframe+0x44/0xae 2022-02-18T09:08:02.630270-05:00 localhost kernel: [ 91.053097][ T5215] RIP: 0033:0x7fa96f8a688b 2022-02-18T09:08:02.630272-05:00 localhost kernel: [ 91.053099][ T5215] Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5d 75 0f 00 f7 d8 64 89 01 48 2022-02-18T09:08:02.630274-05:00 localhost kernel: [ 91.053101][ T5215] RSP: 002b:00007ffc93f8fbb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 2022-02-18T09:08:02.630275-05:00 localhost kernel: [ 91.053103][ T5215] RAX: ffffffffffffffda RBX: 00007ffc93f8fc00 RCX: 00007fa96f8a688b 2022-02-18T09:08:02.630277-05:00 localhost kernel: [ 91.053104][ T5215] RDX: 00007ffc93f8fc00 RSI: 00000000c03864bc RDI: 0000000000000013 2022-02-18T09:08:02.630278-05:00 localhost kernel: [ 91.053105][ T5215] RBP: 00000000c03864bc R08: 0000000000000000 R09: 0000000000000000 2022-02-18T09:08:02.630279-05:00 localhost kernel: [ 91.053106][ T5215] R10: 000000000000000d R11: 0000000000000246 R12: 000055c2e2d4dbf0 2022-02-18T09:08:02.630281-05:00 localhost kernel: [ 91.053106][ T5215] R13: 0000000000000013 R14: 000055c2e2d87840 R15: 000055c2e2d201f0 2022-02-18T09:08:02.630282-05:00 localhost kernel: [ 91.053108][ T5215] </TASK> 2022-02-18T09:08:02.630283-05:00 localhost kernel: [ 91.053109][ T5215] ---[ end trace dd8544f5a3a3564e ]--- 2022-02-18T09:08:02.630285-05:00 localhost kernel: [ 91.053111][ T5215] amdgpu 0000:04:00.0: [drm] *ERROR* cannot allocate and release VCPI on [MST PORT:00000000224748f2] in the same state The error I'm seeing now from journalctl -f -g amdgpu is: amdgpu 0000:05:00.0: [drm] *ERROR* cannot allocate and release VCPI on [MST PORT:0000000050490ba5] in the same state Mar 04 12:18:28 localhost.localdomain kernel: snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi think_lmi wmi_bmof firmware_at> Mar 04 12:18:28 localhost.localdomain kernel: ? dc_link_should_enable_fec+0x3d/0x60 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] Mar 04 12:18:28 localhost.localdomain kernel: compute_mst_dsc_configs_for_link+0x949/0xa20 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] Mar 04 12:18:28 localhost.localdomain kernel: compute_mst_dsc_configs_for_state+0x1eb/0x340 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] Mar 04 12:18:28 localhost.localdomain kernel: amdgpu_dm_atomic_check+0xce4/0xf00 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] Mar 04 12:18:28 localhost.localdomain kernel: amdgpu_drm_ioctl+0x49/0x80 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1205111] New: USB audio interface Edirol M-100FX is not recognized as audio interface anymore with kernel version > 6.0.2
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205111 Bug ID: 1205111 Summary: USB audio interface Edirol M-100FX is not recognized as audio interface anymore with kernel version > 6.0.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: wolfgang.engel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862676 --> https://bugzilla.suse.com/attachment.cgi?id=862676&action=edit dmesg kernel 6.0.2 My USB audio interface is not recognized as audio interface anymore after upgrading to kernel version > 6.0.2 With kernel 6.0.2 the interface shows up correctly with aplay -l : **** List of PLAYBACK Hardware Devices **** card 0: M100FX [EDIROL M-100FX], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 0: ALC3235 Analog [ALC3235 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 With kernel 6.0.3 it doesn't show up anymore: **** List of PLAYBACK Hardware Devices **** card 1: PCH [HDA Intel PCH], device 0: ALC3235 Analog [ALC3235 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 I attached the output from dmesg, lsusb and lsusb -vv from kernel version 6.0.2 and 6.0.6 -- You are receiving this mail because: You are the assignee for the bug.

1 35

[Bug 1203767] New: Backport AMD ACPI processor idle dummy wait fix
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1203767 Bug ID: 1203767 Summary: Backport AMD ACPI processor idle dummy wait fix 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak <kprateek.nayak(a)amd.com> Suggested-by: Rafael J. Wysocki <rafael.j.wysocki(a)intel.com> Signed-off-by: Dave Hansen <dave.hansen(a)linux.intel.com> Reviewed-by: Mario Limonciello <mario.limonciello(a)amd.com> Tested-by: K Prateek Nayak <kprateek.nayak(a)amd.com> Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.nayak@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.hansen@intel.com git commit e400ad8b7e6a1b9102123c6240289a811501f7d9 -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1200461] New: Dracut locks computer, fails to generate initrd file
by bugzilla_noreply＠suse.com 21 Dec '22

21 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200461 Bug ID: 1200461 Summary: Dracut locks computer, fails to generate initrd file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mfdemicco(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859545 --> http://bugzilla.opensuse.org/attachment.cgi?id=859545&action=edit Photo of screen at moment of freeze When I update to kernel 5.18.1-1 or 5.18.2.1, Dracut locks up my system requiring a power button reboot when creating the initrd file. I also tried installing the latest version of Tumbleweed to another partition, and the installation locked up the computer about 50% into the installation with no creation of the initrd file. The computer freezes at: Dracut: *** Including module: kernel-modules *** When I look in my /boot folder, everything for the kernel is created except for the initrd file I've done a search and can't find anyone that has the same problem. The system runs file with the older kernel 5.17.4-1. I have a legacy BIOS system. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1191244] New: USB speaker working when plugged while system is up but not on reboot
by bugzilla_noreply＠suse.com 19 Dec '22

19 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191244 Bug ID: 1191244 Summary: USB speaker working when plugged while system is up but not on reboot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: aarch64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: peter.stark(a)storck.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have multiple raspberry PI 4Bs with openSUSE Leap 15.3 and some with raspbian 9. I got a USB speaker (e2b7:0811) which I connected to the 4Bs using Leap 15.3. This speaker works fine when I plug it in when the PI is already running: rpi15:~ # uname -a Linux rpi15 5.3.18-59.24-default #1 SMP Mon Sep 13 15:06:42 UTC 2021 (2f872ea) aarch64 aarch64 aarch64 GNU/Linux rpi15:~ # lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 03eb:2013 Atmel Corp. iAQ Stick Bus 001 Device 007: ID e2b7:0811 Jie Li CD002 Bus 001 Device 003: ID 044f:b351 ThrustMaster, Inc. F16 MFD 1 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rpi15:~ # dmesg -T|grep 1-1.2 [Sa Okt 2 10:56:09 2021] usb 1-1.2: USB disconnect, device number 4 [Sa Okt 2 10:56:17 2021] usb 1-1.2: new full-speed USB device number 6 using xhci_hcd [Sa Okt 2 10:56:17 2021] usb 1-1.2: device descriptor read/64, error -32 [Sa Okt 2 10:56:17 2021] usb 1-1.2: device descriptor read/64, error -32 [Sa Okt 2 10:56:17 2021] usb 1-1.2: new full-speed USB device number 7 using xhci_hcd [Sa Okt 2 10:56:17 2021] usb 1-1.2: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:56:17 2021] usb 1-1.2: config 1 has no interface number 0 [Sa Okt 2 10:56:17 2021] usb 1-1.2: New USB device found, idVendor=e2b7, idProduct=0811, bcdDevice= 1.00 [Sa Okt 2 10:56:17 2021] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:56:17 2021] usb 1-1.2: Product: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: Manufacturer: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: SerialNumber: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: 9:1: bogus dB values (-12800/-12700), disabling dB reporting [Sa Okt 2 10:56:17 2021] input: CD002 CD002 as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.3/0003:E2B7:0811.0003/input/input1 However, after a reboot with the device still connected (no change) the kernel boots and does not even see the device. rpi15:~ # lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:2013 Atmel Corp. iAQ Stick Bus 001 Device 003: ID 044f:b351 ThrustMaster, Inc. F16 MFD 1 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rpi15:~ # dmesg -T|grep 1-1.2 rpi15:~ # I have tried the same USB speaker on another PI4B with Leap 15.3 with the same result. So, it doesn't seem to be that PI. When I connect the speaker to a PI3 with raspbian 9, it works as expected. root@rpi13:~# dmesg -T |grep 1-1.3 [Sa Okt 2 10:33:08 2021] usb 1-1.3: new full-speed USB device number 4 using dwc_otg [Sa Okt 2 10:33:08 2021] usb 1-1.3: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:33:08 2021] usb 1-1.3: config 1 has no interface number 0 [Sa Okt 2 10:33:08 2021] usb 1-1.3: New USB device found, idVendor=e2b7, idProduct=0811 [Sa Okt 2 10:33:08 2021] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:33:08 2021] usb 1-1.3: Product: CD002 [Sa Okt 2 10:33:08 2021] usb 1-1.3: Manufacturer: CD002 [Sa Okt 2 10:33:08 2021] usb 1-1.3: SerialNumber: CD002 [Sa Okt 2 10:33:08 2021] input: CD002 CD002 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.3/0003:E2B7:0811.0001/input/input0 [Sa Okt 2 10:42:57 2021] usb 1-1.3: reset full-speed USB device number 4 using dwc_otg [Sa Okt 2 10:42:58 2021] usb 1-1.3: USB disconnect, device number 4 [Sa Okt 2 10:42:58 2021] usb 1-1.3: 9:1: cannot get min/max values for control 2 (id 9) [Sa Okt 2 10:43:04 2021] usb 1-1.3: new full-speed USB device number 6 using dwc_otg [Sa Okt 2 10:43:04 2021] usb 1-1.3: device descriptor read/64, error -32 [Sa Okt 2 10:43:04 2021] usb 1-1.3: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:43:04 2021] usb 1-1.3: config 1 has no interface number 0 [Sa Okt 2 10:43:04 2021] usb 1-1.3: New USB device found, idVendor=e2b7, idProduct=0811 [Sa Okt 2 10:43:04 2021] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:43:04 2021] usb 1-1.3: Product: CD002 [Sa Okt 2 10:43:04 2021] usb 1-1.3: Manufacturer: CD002 [Sa Okt 2 10:43:04 2021] usb 1-1.3: SerialNumber: CD002 [Sa Okt 2 10:43:04 2021] input: CD002 CD002 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.3/0003:E2B7:0811.0002/input/input1 I noticed that the raspbian uses dwc_otg vs. xhci_hcd on Leap. However, dwc_otg doesn't seem to be a separate module in raspbian nor it is available on leap. As the speaker is working when I un-plug and plug it in again, I wonder what may causes this strange behavior. Especially as I do not see the device via lsusb after reboot, though it is still connected. Any ideas on how to fix it? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1201963] New: 11th Gen Intel(R) Core(TM) i5-1145G7 throttling to 400MHz from 70°C until it reaches 54°C
by bugzilla_noreply＠suse.com 16 Dec '22

16 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1201963 Bug ID: 1201963 Summary: 11th Gen Intel(R) Core(TM) i5-1145G7 throttling to 400MHz from 70�C until it reaches 54�C 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: gryffus(a)hkfree.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 860458 --> https://bugzilla.suse.com/attachment.cgi?id=860458&action=edit Turbostat log output I have a Dell Latitude 5420 laptop and i am experiencing CPU slowdown when using any graphical / CPU demanding application. The laptop contains 11th Gen Intel(R) Core(TM) i5-1145G7 which can do 4,4GHz on turbo. When the system reaches about 70�C, all cores switch to 400MHz and stay there until temperature hits 53-54�C. I can see this behavior especially in Vulkan graphics applications, but not only in them, it just happens almost instantly there, since the 70�C is reached within about 30 seconds there. I would want to raise the temperature limits to at least 80-90�C or disable throttling completely (at my own responsibility of cooking it). But throttling from 70�C seems as a complete nonsense to me - the CPU package gets to this temperature in 10-20 seconds under load, so i basically never make use of the 4,4GHz. What i have tried: 1) Kernel 5.19 from Kernel:HEAD - no change 2) installed throttled ( https://github.com/erpalma/throttled ) - no change 3) blacklisted intel_powerclamp, intel_rapl_msr, processor_thermal_rapl, intel_rapl_common kernel modules - no change 4) cpupower frequency-set -g performance - no change # cat /sys/devices/platform/*/uuids/current_uuid INVALID # cat /sys/devices/platform/*/uuids/available_uuids UNKNOWN # cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.40 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 4.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 3.16 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes # cpupower idle-info CPUidle driver: intel_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 4 Available idle states: POLL C1_ACPI C2_ACPI C3_ACPI POLL: Flags/Description: CPUIDLE CORE POLL IDLE Latency: 0 Usage: 265266 Duration: 8068126 C1_ACPI: Flags/Description: ACPI FFH MWAIT 0x0 Latency: 1 Usage: 10617293 Duration: 1984558460 C2_ACPI: Flags/Description: ACPI FFH MWAIT 0x31 Latency: 253 Usage: 273458 Duration: 261649941 C3_ACPI: Flags/Description: ACPI FFH MWAIT 0x60 Latency: 1048 Usage: 206150 Duration: 509227956 # cpupower info analyzing CPU 0: perf-bias: 0 Turbostat debug log attached. Some further reading with probably related reports: https://www.dell.com/community/Latitude/Latitude-5420-7420-7520-CPU-Throttl… https://github.com/intel/thermal_daemon/issues/341 https://github.com/intel/thermal_daemon/issues/293 https://github.com/erpalma/throttled Any clues? -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1205149] New: %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets
by bugzilla_noreply＠suse.com 14 Dec '22

14 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205149 Bug ID: 1205149 Summary: %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets 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: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- kernel rpm scriptlets will be moved to a separate subpackage (see https://github.com/openSUSE/suse-module-tools/pull/64) kmps do already (pre)require suse-kernel-rpm-scriptlets just fine. However during build those prerequires are not seen by the OBS schedule as they are hidden inside the %suse_kernel_module_package macro. So the package install check after build fails due to missing scriptlets. Therefore %kernel_module_package_buildreqs needs to list suse-kernel-rpm-scriptlets -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1189946] New: [trackerbug] Ancient patch cleanup
by bugzilla_noreply＠suse.com 09 Dec '22

09 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1189946 Bug ID: 1189946 Summary: [trackerbug] Ancient patch cleanup 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: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jeffm(a)suse.com, mkubecek(a)suse.com Found By: --- Blocker: --- This is the tracker bug for cleaning up old patches in the master branch. -- You are receiving this mail because: You are the assignee for the bug.

1 27

[Bug 1203519] New: floating shutdown problem on pinebook pro
by bugzilla_noreply＠suse.com 08 Dec '22

08 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203519 Bug ID: 1203519 Summary: floating shutdown problem on pinebook pro Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: werwolf131313(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- intermittent shutdown problem on pinebook pro, the problem is expressed as follows: after the laptop is turned off (it doesn��t matter by the button in the menu or via sudo systemctl shutdown), a regular shutdown occurs, the service stop log is visible and everything is as it should be, BUT, after the screen goes blank, the board remains on. this can be checked if you try to turn it on, pressing the button does not work. only a long press of the power key (to completely turn off) for 7-10 seconds, and a second press (to turn it on) allows you to turn on the pinebook. the problem is not observed in other distributions (tried on manjaro, armbian, gentoo) and is specific to opensuse. in my case, the installation differs from the typical one in that the operating system is installed on a microsd card (due to the death of emmc), can this affect? but in other distributions, even installed on the same microsd card, the problem is not observed. I'm using opensuse tumbleweed installed from the openSUSE-Tumbleweed-ARM-KDE-pinebookpro.aarch64.raw.xz image. at the moment there are all the latest updates, but the problem has existed for quite a long time. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1193599] New: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193599 Bug ID: 1193599 Summary: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following errors appear at boot broken atomic modeset userspace detected, disabling atomic [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D Full log https://paste.opensuse.org/83436185 Hardware Dell Precision 7530 CPU: Intel Xeon E-2186M GPU: Intel P630 / Nvidia Quadro P3200 -- You are receiving this mail because: You are the assignee for the bug.

1 33

[Bug 1205774] New: Kernel 6.0.8 + nvidia 525.53 crash on BUG: kernel NULL pointer dereference, #PF: supervisor instruction fetch in kernel mode
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205774 Bug ID: 1205774 Summary: Kernel 6.0.8 + nvidia 525.53 crash on BUG: kernel NULL pointer dereference, #PF: supervisor instruction fetch in kernel mode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bruno(a)ioda-net.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863125 --> http://bugzilla.opensuse.org/attachment.cgi?id=863125&action=edit Last kernel 6.0.8 boot and crash Hello I need help to find the root cause of crashes (complete freeze of the workstation). Since the introduction of kernel 6.0.8 and latest nvidia 525.53 I constantly face complete machine freeze, when I'm using my external monitors. nov 25 16:05:34 qt-kt kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 nov 25 16:05:34 qt-kt kernel: #PF: supervisor instruction fetch in kernel mode nov 25 16:05:34 qt-kt kernel: #PF: error_code(0x0010) - not-present page nov 25 16:05:34 qt-kt kernel: PGD 0 P4D 0 nov 25 16:05:34 qt-kt kernel: Oops: 0010 [#1] PREEMPT SMP PTI nov 25 16:05:34 qt-kt kernel: CPU: 3 PID: 1004 Comm: nvidia-modeset/ Tainted: P OE 6.0.8-1-default #1 openSUSE Tumbleweed 9d20364b934f5aab0a9bdf84e8f45cfdfae39dab nov 25 16:05:34 qt-kt kernel: Hardware name: Dell Inc. Precision 7510/0YH43H, BIOS 1.29.3 09/18/2022 nov 25 16:05:34 qt-kt kernel: RIP: 0010:0x0 nov 25 16:05:34 qt-kt kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6. nov 25 16:05:34 qt-kt kernel: RSP: 0018:ffffadc300703c90 EFLAGS: 00010207 nov 25 16:05:34 qt-kt kernel: RAX: 0000000000000000 RBX: ffff9b2996c75378 RCX: 0000000000000004 nov 25 16:05:34 qt-kt kernel: RDX: 0000000000000010 RSI: ffff9b2996c75378 RDI: ffffadc300703a10 nov 25 16:05:34 qt-kt kernel: RBP: ffff9b292ef8b560 R08: 0000000000000000 R09: 0000000000000040 nov 25 16:05:34 qt-kt kernel: R10: ffff9b2886b28008 R11: ffffadc300703c00 R12: 0000000000000000 nov 25 16:05:34 qt-kt kernel: R13: 0000000000000000 R14: ffffffffc4fbee70 R15: ffffffffc4eb7580 nov 25 16:05:34 qt-kt kernel: FS: 0000000000000000(0000) GS:ffff9b37c44c0000(0000) knlGS:0000000000000000 nov 25 16:05:34 qt-kt kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 nov 25 16:05:34 qt-kt kernel: CR2: ffffffffffffffd6 CR3: 000000075be10001 CR4: 00000000003706e0 nov 25 16:05:34 qt-kt kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 nov 25 16:05:34 qt-kt kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 nov 25 16:05:34 qt-kt kernel: Call Trace: nov 25 16:05:34 qt-kt kernel: <TASK> nov 25 16:05:34 qt-kt kernel: _nv001281kms+0x194/0x1a0 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv001274kms+0x9a/0xd0 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv001466kms+0x172/0x180 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv001149kms+0xf3/0xa50 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? schedule+0x5a/0xd0 nov 25 16:05:34 qt-kt kernel: ? schedule_timeout+0x10e/0x150 nov 25 16:05:34 qt-kt kernel: ? nvkms_sema_up+0x10/0x10 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? __down_common+0x10b/0x1e0 nov 25 16:05:34 qt-kt kernel: ? nvkms_sema_up+0x10/0x10 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv002457kms+0x2d/0x70 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? nvkms_kthread_q_callback+0x88/0xf0 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _main_loop+0x77/0x130 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? kthread+0xd7/0x100 nov 25 16:05:34 qt-kt kernel: ? kthread_complete_and_exit+0x20/0x20 nov 25 16:05:34 qt-kt kernel: ? ret_from_fork+0x1f/0x30 nov 25 16:05:34 qt-kt kernel: </TASK> nov 25 16:05:34 qt-kt kernel: Modules linked in: rfcomm snd_seq_dummy snd_hrtimer snd_seq nf_nat_sip nft_objref af_packet nf_conntrack_sip nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct n> nov 25 16:05:34 qt-kt kernel: processor_thermal_device_pci_legacy irqbypass iwlwifi processor_thermal_device pcspkr ledtrig_audio processor_thermal_rfim snd_usbmidi_lib efi_pstore snd_intel_sdw_acpi sparse_keymap processor_thermal_mbox cdc_wdm videob> nov 25 16:05:34 qt-kt kernel: fuse configfs dmi_sysfs ip_tables x_tables cmac algif_hash algif_skcipher af_alg hid_logitech_hidpp hid_logitech_dj hid_generic dm_crypt usbhid essiv authenc trusted asn1_encoder tee bnep btusb btrtl btbcm btintel btmtk > nov 25 16:05:34 qt-kt kernel: CR2: 0000000000000000 nov 25 16:05:34 qt-kt kernel: ---[ end trace 0000000000000000 ]--- Most of the time this happen after resuming the screens, the primary one get on, but the second is always in suspend mode, I have to open neither display settings in plasma or nvidia-settings to set on the second monitor (displayport slave link) after switching off and on the monitor. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1191933] New: Kernel can not update on Secure boot envirnment
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191933 Bug ID: 1191933 Summary: Kernel can not update on Secure boot envirnment 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: kokeko(a)mac.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Current 20211012, update to 20211016 or 20211019. Kernel-default update failed by fallowing error. subprocess error, secure boot enabled. Is it something change? -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1200781] New: xhci stop working. Works briefly after reboot, or remove and load xhci_pci & xhci_hcd.
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200781 Bug ID: 1200781 Summary: xhci stop working. Works briefly after reboot, or remove and load xhci_pci & xhci_hcd. 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: publio.escipion.el.africano(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSuSE Leap 15.4 x86_64, kernel 4.14.21-150400.22-default, in a Lenovo IdeaPad 3 15ADA05: https://psref.lenovo.com/syspool/Sys/PDF/IdeaPad/IdeaPad_3_15ADA05/IdeaPad_… An external mouse stops working after a brief period of time, after login into KDE, or after removing and loading xhci_pci & xhci_hcd. System complaints of: �xhci_hcd 0000:02:00.3 WARNIGN: Host System Error� and: �usb 2-3: device not accepting address 2, error -108� I've tried two bluetooth mice, and a standard cord mouse. The same result. It seems that it's the USB controllers are the only components affected, so far. Mousepad works properly, but I'm not use to it. I have to constantly remove and load xhci_pci & xhci_hcd, as root. rmmod xhci_pci rmmod xhci_hcd modprobe xhci_pci modprobe xhci_hcd Mouse works after that for a short time. Nota bene: Devices work properly under openSuSE Leap 15.2 x86_64, kernel 5.3.18-lp152.106-default (old HP Pavillion). This bug resembles https://bugzilla.opensuse.org/show_bug.cgi?id=1193652 -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 1205597] ltp:pty03:slcan: null-ptr-deref in process_one_work
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205597 https://bugzilla.suse.com/show_bug.cgi?id=1205597#c6 --- Comment #6 from Petr Vorel <petr.vorel(a)suse.com> --- @Jiri: running for many times (~ 50) none of runs on kernel with fix from you [4] failed. But running ~ 20 times on original unfixed openSUSE kernel [5] it failed 6 times (some of the failed tests are visible on [5]). I guess you can send your patch :). Or do you want me to test patch, where flush_work(&sl->tx_work) call is removed from slcan_netdev_close() or it will stay here? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205597] ltp:pty03:slcan: null-ptr-deref in process_one_work
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205597 https://bugzilla.suse.com/show_bug.cgi?id=1205597#c5 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(richard.palethorp | |e(a)suse.com) | --- Comment #5 from Petr Vorel <petr.vorel(a)suse.com> --- I created modified openQA code [1], which installs my RPM [2]. where I just added your change [3] (branch users/pvorel/stable/bsc1205597). So far I haven't been able to trigger error on fixed kernel [4], but there were 2 failures on unfixed kernel [5]. I'll keep restarting it to see if it really fixed the problem. [1] https://github.com/pevik/os-autoinst-distri-opensuse/tree/update_kernel/ins… [2] https://download.opensuse.org/repositories/home:/pevik:/bsc1205597/standard… [3] https://kerncvs.suse.de/gitweb/?p=kernel-source.git;a=commit;h=74fd656eb8fb… [4] https://openqa.opensuse.org/tests/overview?build=pty03-fixed-kernel&version… [5] https://openqa.opensuse.org/tests/overview?build=pty03-unfixed&distri=opens… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205149] %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205149 https://bugzilla.suse.com/show_bug.cgi?id=1205149#c5 Dominique Leuenberger <dleuenberger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dleuenberger@suse | |.com) | --- Comment #5 from Dominique Leuenberger <dleuenberger(a)suse.com> --- (In reply to Martin Wilck from comment #3) > I pushed this to Factory again (sr#1038933). > > @Dominique, this means that the prjconf will need to be adapted to avoid > errors for kmp builds (see above). Thanks - s-m-t is currently Staged in :L and prjconf adjusted there; once accepted to Factory, the prjconf will be moved there. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204063] Kernel 5.19.8 appears to be missing lpuart earlycon and console
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204063 https://bugzilla.suse.com/show_bug.cgi?id=1204063#c8 --- Comment #8 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- I have found the right combination of parameters and device tree content which activates earlycon for VAR-SOM-MX8 without upstream Linux modifications. 'earlycon' have to be passed to kernel command line via GRUB and NOT via device tree like this: chosen { bootargs = "earlycon"; Then just make sure you have following into chosen device tree node: chosen { stdout-path = "serial0"; -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205891] System freeze
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205891 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |branislav.klocok(a)orava.sk Flags| |needinfo?(branislav.klocok@ | |orava.sk) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204063] Kernel 5.19.8 appears to be missing lpuart earlycon and console
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204063 https://bugzilla.suse.com/show_bug.cgi?id=1204063#c7 --- Comment #7 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Patch above is not real fix, I would say, but for now I can't find how to activate early console based on compatible string, because with current state early consoles defined without compatible string take precedence, see (f8c3686c65f0 "serial: earlycon: prefer EARLYCON_DECLARE() variant") I have removed "earlycon=lpuart32,0x5a060000,115200" from the kernel command because it take precedence and pick "wrong" console_setup() method. Then I just added stdout-path = "serial0:115200n8" which should activate early console using compatible string, but no luck so far. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204063] Kernel 5.19.8 appears to be missing lpuart earlycon and console
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204063 https://bugzilla.suse.com/show_bug.cgi?id=1204063#c6 --- Comment #6 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Above simple patch fixes earlycon on VAR-SOM-MX8 for me. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204063] Kernel 5.19.8 appears to be missing lpuart earlycon and console
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204063 https://bugzilla.suse.com/show_bug.cgi?id=1204063#c5 --- Comment #5 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Created attachment 863207 --> https://bugzilla.suse.com/attachment.cgi?id=863207&action=edit Proper lpuart32 setup -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205891] System freeze
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205891 https://bugzilla.suse.com/show_bug.cgi?id=1205891#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> --- Hmm, it's really difficult to read. At the next time, please use attachments for those full texts. Through a quick glance, I couldn't see any error relevant with the graphics, and IIUC, your problem is the frozen screen, right? Is the whole screen frozen while something displayed, or is it blank, or any other state? Did you have the access to the machine by other means, i.e. it was only about the graphics? Also, you mentioned that you removed the machine from the dock *before* closing the lid. So, the display should be already in laptop-only mode, and it was shown correctly before closing the lid, but this wasn't resumed after the lid open? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205597] ltp:pty03:slcan: null-ptr-deref in process_one_work
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205597 https://bugzilla.suse.com/show_bug.cgi?id=1205597#c4 --- Comment #4 from Petr Vorel <petr.vorel(a)suse.com> --- BTW bug was triggered not only on x86_64, but also on aarch64, but just once for very long time https://openqa.opensuse.org/tests/2890022#step/pty03/9 https://openqa.opensuse.org/tests/2914591#next_previous There is about 50% to trigger it on x86_64: https://openqa.opensuse.org/tests/2891345#next_previous -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205891] System freeze
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205891 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |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 1205597] ltp:pty03:slcan: null-ptr-deref in process_one_work
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205597 https://bugzilla.suse.com/show_bug.cgi?id=1205597#c3 --- Comment #3 from Petr Vorel <petr.vorel(a)suse.com> --- (In reply to Petr Vorel from comment #2) > I'll verify your patch. I'm also not able to on my VMs, nor on my laptop. s/able to/able to reproduce the bug / -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205597] ltp:pty03:slcan: null-ptr-deref in process_one_work
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205597 https://bugzilla.suse.com/show_bug.cgi?id=1205597#c2 --- Comment #2 from Petr Vorel <petr.vorel(a)suse.com> --- I'll verify your patch. I'm also not able to on my VMs, nor on my laptop. Therefore had to push your patch to OBS [1] to have package, which I'll install before running LTP test. [1] https://build.opensuse.org/package/show/home:pevik:bsc1205597/kernel-source -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205743] Installer hangs on "Probing USB devices" on Dell XPS 9520
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205743 https://bugzilla.suse.com/show_bug.cgi?id=1205743#c8 --- Comment #8 from Johnny Willemsen <jwillemsen(a)remedy.nl> --- ctrl-alt-F1, F2 or other and also ctrl-alt-shift-X don't work. I can move the mouse but none of the special keys work :-( -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204063] Kernel 5.19.8 appears to be missing lpuart earlycon and console
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204063 https://bugzilla.suse.com/show_bug.cgi?id=1204063#c4 --- Comment #4 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Preliminary findings. This UART device depends on power-domain controller compatible="nxp,imx8-pd", for which I can not find corresponding driver, for now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205597] ltp:pty03:slcan: null-ptr-deref in process_one_work
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205597 https://bugzilla.suse.com/show_bug.cgi?id=1205597#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |richard.palethorpe(a)suse.com Flags| |needinfo?(richard.palethorp | |e(a)suse.com) --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- Does this help? I don't understand why they think the CAN net device is UP at tty close and so ndo_stop will be always called to flush the tx work. IMO it is not called. --- a/drivers/net/can/slcan/slcan-core.c +++ b/drivers/net/can/slcan/slcan-core.c @@ -870,6 +870,8 @@ static void slcan_close(struct tty_struct *tty) */ unregister_candev(sl->dev); + flush_work(&sl->tx_work); + /* Mark channel as dead */ spin_lock_bh(&sl->lock); tty->disc_data = NULL; -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205597] ltp:pty03:slcan: null-ptr-deref in process_one_work
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c56 --- Comment #56 from Paul Soto <pst73de(a)yahoo.com> --- another issue popped up: worked on some WIFI project last days and sometimes the touchpad enters another "stupid mode" when I frequently switch the WLAN BSSID Im connected to. Using Network manager to connect (not wickedd). So after switching the BSSID about 30 times what happened: the mouse pointer suddenly becomes very slow (about 1/3 of the original speed) and feels like it has no acceleration at all. No error message or anything in the kernel log, just happens. So far I experienced this 3 times - now the project is done so Im not switching the BSSID anymore (at least not 30 times in a row). Could not diagnose it what actually happens - hey guys I also have to work on something and not debugging this god damn laptop and OS. What fixed the latest issue: lock the screen and put the laptop to sleep for a couple of seconds (5s) then wake it up again, enter the password for screenlock and it works again (mouse back to normal behavior). The mouse however feels different from the first bug (when it enters another crazy mode with the jumpy two finger scrolling) - absolutely not the same. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c55 --- Comment #55 from Paul Soto <pst73de(a)yahoo.com> --- Created attachment 863186 --> http://bugzilla.opensuse.org/attachment.cgi?id=863186&action=edit STR resume log cant provide more than this -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202353] kernel: replace mkinitrd wrapper with native dracut
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

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

1 0

[Bug 1205149] %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205149 https://bugzilla.suse.com/show_bug.cgi?id=1205149#c3 Martin Wilck <martin.wilck(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(dleuenberger@suse | |.com) --- Comment #3 from Martin Wilck <martin.wilck(a)suse.com> --- I pushed this to Factory again (sr#1038933). @Dominique, this means that the prjconf will need to be adapted to avoid errors for kmp builds (see above). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204063] New: Kernel 5.19.8 appears to be missing lpuart earlycon and console
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204063 Bug ID: 1204063 Summary: Kernel 5.19.8 appears to be missing lpuart earlycon and console Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: afaerber(a)suse.com Reporter: afaerber(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ddavis(a)suse.com, dmueller(a)suse.com, guillaume.gardet(a)arm.com, kernel-bugs(a)opensuse.org, mbrugger(a)suse.com, mkubecek(a)suse.com Found By: --- Blocker: --- Despite kernel command line "console=ttyLP0,115200 earlycon=lpuart32,0x5a060000,115200" on an NXP i.MX 8QM based Variscite VAR-SOM-MX8 module based device, I am not seeing any kernel serial output other than EFI stub: Loading Linux 5.19.8-1-default ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... or without EFI: Starting kernel ... Having ruled out a red herring of EFI stub: ERROR: Failed to install memreserve config table! as caused by old U-Boot 2018.03 having a hardcoded config table array size of 2, the lack of output most likely is because of: CONFIG_SERIAL_FSL_LPUART=m git-blame points to a SLE15-SP2 sync: https://github.com/openSUSE/kernel-source/commit/769684a2fa08#diff-a9e1c242… Serial Kconfig options need to be built-in (=y) in order to enable their sub-option *_CONSOLE=y, needed for both console= and earlycon= kernel options. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1205743] Installer hangs on "Probing USB devices" on Dell XPS 9520
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205743 https://bugzilla.suse.com/show_bug.cgi?id=1205743#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Can switch the VT via ctrl-alt-F1, F2 or other? Also, ctrl-alt-shift-X should start an xterm, IIRC. If you can have a terminal access, try to get the dmesg output. If we are lucky, we can see some errors. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205743] Installer hangs on "Probing USB devices" on Dell XPS 9520
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205743 https://bugzilla.suse.com/show_bug.cgi?id=1205743#c6 --- Comment #6 from Johnny Willemsen <jwillemsen(a)remedy.nl> --- The screen "System Probing" appears and on "Probe USB devides" nothing happens, progress bar stays at 0%, mouse does seem to work but nothing more happens. Any magic button or something I can do to give you more details/insight? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205743] Installer hangs on "Probing USB devices" on Dell XPS 9520
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205743 https://bugzilla.suse.com/show_bug.cgi?id=1205743#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo?(jwillemsen@remedy | |.nl) --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- How exactly is the situation? Does the complete screen freeze, or does the cursor still work? Also, can you change the VT? It's difficult to know what's going without the detailed logs and without the way to reproduce locally on the installed system, unfortunately. Judging from the hwinfo, it's a system with Alterlake and Nvidia, and as nomodeset works around it, it's likely a problem in i915 driver. But that's the only information we can have from the description. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205639] New: After 'zypper dup' the Ethernet device got name end0 instead of eth0
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205639 Bug ID: 1205639 Summary: After 'zypper dup' the Ethernet device got name end0 instead of eth0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After 'zypper dup' to tumbleweed:20221120 on an aarch64 system the name of the Ethernet device got the name end0 instead of remaining eth0. Because this device is not present in the firewall configuration, access to this system is not possible anymore. I do have access via a tty device. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1205813] BTRFS data corruption - need help
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205813 http://bugzilla.opensuse.org/show_bug.cgi?id=1205813#c7 --- Comment #7 from Felix Niederwanger <felix.niederwanger(a)suse.com> --- Hard to know. btrfs can only detect those issues via checksuming but is itself not able to tell you where they come from - they can originate from basically anywhere. Faulty hardware or bad connectors are by far more likely than a filesystem issue itself. IMHO - don't bother trying to repair such issues. If you could save the data elsewhere then nuke the filesystem and start over. I would be suspicious on the hardware itself and wouldn't rely on it for a couple of months after such a failure, i.e. always keep backups and assume it's going to shoot itself in the foot again. At this point I would say it's safe to assume the disk is somehow flanky until proven otherwise. But those are just my two cents - Your hardware, your rules :-) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

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

1 0

[Bug 1205813] BTRFS data corruption - need help
by bugzilla_noreply＠suse.com 28 Nov '22

28 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205813 http://bugzilla.opensuse.org/show_bug.cgi?id=1205813#c6 --- Comment #6 from Max Thein <opensuse(a)mailbox.org> --- I have followed the wiki instructions up to the scrub command. After that, the first warning box says: "...If the above doesn't fix things for you, you can continue with the below steps but the situation is serious enough to justify a bug report, please!" Wouldn't it be interesting to know why there are these checksum errors? Occurred during an average desktop use case? I can follow the further wiki instructions. Maybe it will help, maybe my system will become unusable. Then I am left with a reinstall without knowing the reason. Not very smart. My hope is to figure out the problem before I enter irreversible terminal commands. I'm not a BTRFS expert, so I am asking for help here. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205813] BTRFS data corruption - need help
by bugzilla_noreply＠suse.com 28 Nov '22

28 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205813 http://bugzilla.opensuse.org/show_bug.cgi?id=1205813#c5 Felix Niederwanger <felix.niederwanger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |felix.niederwanger(a)suse.com --- Comment #5 from Felix Niederwanger <felix.niederwanger(a)suse.com> --- It's more a support request than a bug report. Judging from the dmesg output it looks like that part of the partition got corrupted and btrfs detects checksum mismatches. It's good that you could save everything important already elsewhere. Checkout the wiki page on how to repair a (unmountable) btrfs filesystem, that might help you: https://en.opensuse.org/SDB:BTRFS#How_to_repair_a_broken.2Funmountable_btrf… Good luck! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205660] New: Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 28 Nov '22

28 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205660 Bug ID: 1205660 Summary: Fix non-working Realtek USB ethernet after system resume 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: noga.dany(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863051 --> http://bugzilla.opensuse.org/attachment.cgi?id=863051&action=edit Dmesg from trying to multiple sleep, resume cycles I am using Lenovo T15p gen.2 (Intel) connected to the Dell TB16 dock. Whenever I put notebook on the sleep and then resume, ethernet from dock does not work. I can fix it by unplug and plug again thunderbold cable or by command line: sudo rmmod r8153_ecm sudo rmmod r8152 sudo modprobe r8153_ecm Issue is with all Leap 15.4 kernels including 5.14.21-150400.24.33-default It looks similar to the https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847063 , but that bug mentions something about r8152 and nothing about r8153_ecm Dmesg from trying to multiple sleep, resume cycles and from trying to fix it via rmmod and modprobe attached. Issue is not 100% reproducible, when I wrote this bug report, it worked once right after boot. But only once. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 28 Nov '22

28 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c69 --- Comment #69 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Martin Greco from comment #68) > Hi, I'm struggling with same issue but in ASUS Q408UG model.. I'd like to > try if this kernel works.. The problem is that I don't have a clue how to > download and install it.. If someone could give me a hand, I'd appreciate a > lot You can try to pass i8042.probe_defer=1 boot option for the recent kernels. If this solves the problem, we may add the similar quirk entry. If it doesn't, it must be another problem. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205813] BTRFS data corruption - need help
by bugzilla_noreply＠suse.com 28 Nov '22

28 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205813 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |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 1204952] System crashes when booting first time after kernel update
by bugzilla_noreply＠suse.com 28 Nov '22

28 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204952 https://bugzilla.suse.com/show_bug.cgi?id=1204952#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Basesystem Assignee|kernel-bugs(a)opensuse.org |systemd-maintainers(a)suse.de --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Tossed to systemd people. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205624] qemu fails in test on openSUSE:Step:15-SP5 armv7
by bugzilla_noreply＠suse.com 28 Nov '22

28 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205624 https://bugzilla.suse.com/show_bug.cgi?id=1205624#c11 Dario Faggioli <dfaggioli(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|KVM |Kernel Assignee|kvm-bugs(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #11 from Dario Faggioli <dfaggioli(a)suse.com> --- (In reply to Dirk Mueller from comment #10) > It isn't the fix. the issue appears to be on kernel side. still bissecting > down. it works with kernel 5.18, fails with the 15-SP4 kernel > Ok, thanks Dirk for all the work you've done on this issue. Just from the "process" point of view, I think the component can be set to 'Kernel', for now. Ping us back if there emerges new QEMU aspects of it. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205359] Modprobing spidev on a Raspberry Pi does not create "/dev/spidev*.*".
by bugzilla_noreply＠suse.com 28 Nov '22

28 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205359 https://bugzilla.suse.com/show_bug.cgi?id=1205359#c5 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Thanks for the updated wiki pages! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205743] Installer hangs on "Probing USB devices" on Dell XPS 9520
by bugzilla_noreply＠suse.com 28 Nov '22

28 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205743 http://bugzilla.opensuse.org/show_bug.cgi?id=1205743#c4 --- Comment #4 from Johnny Willemsen <jwillemsen(a)remedy.nl> --- Created attachment 863138 --> http://bugzilla.opensuse.org/attachment.cgi?id=863138&action=edit Output of hwinfo Output of hwinfo -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205743] Installer hangs on "Probing USB devices" on Dell XPS 9520
by bugzilla_noreply＠suse.com 27 Nov '22

27 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205743 https://bugzilla.suse.com/show_bug.cgi?id=1205743#c3 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Kernel Assignee|yast2-maintainers(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de Flags|needinfo?(jwillemsen@remedy | |.nl) | --- Comment #3 from Stefan Hundhammer <shundhammer(a)suse.com> --- I just saw that there is a lot of HW information at that OpenSUSE forum thread. I guess that should be enough. But one way or the other, this is not an installer bug. My guess is that some hardware ID is not yet in one of the kernel tables for proper hardware detection. Reassigning to the kernel maintainers. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 26 Nov '22

26 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c68 Martin Greco <martin00greco(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin00greco(a)gmail.com --- Comment #68 from Martin Greco <martin00greco(a)gmail.com> --- Hi, I'm struggling with same issue but in ASUS Q408UG model.. I'd like to try if this kernel works.. The problem is that I don't have a clue how to download and install it.. If someone could give me a hand, I'd appreciate a lot -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205660] Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205660 https://bugzilla.suse.com/show_bug.cgi?id=1205660#c24 --- Comment #24 from Daniel Noga <noga.dany(a)gmail.com> --- Only resetting quirk usbcore.quirks=0bda:8153:b worked from all that tries -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205660] Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205660 https://bugzilla.suse.com/show_bug.cgi?id=1205660#c23 --- Comment #23 from Daniel Noga <noga.dany(a)gmail.com> --- Yes, still broken, parameter usbcore.autosuspend=-1 did not help. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205660] Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205660 https://bugzilla.suse.com/show_bug.cgi?id=1205660#c22 --- Comment #22 from Takashi Iwai <tiwai(a)suse.com> --- I see no -71 error in the comment 19. Was the network still broken after suspend/resume in this case? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205660] Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205660 https://bugzilla.suse.com/show_bug.cgi?id=1205660#c21 Daniel Noga <noga.dany(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(noga.dany(a)gmail.c | |om) | --- Comment #21 from Daniel Noga <noga.dany(a)gmail.com> --- Adding usbcore.quirks=0bda:8153:b works! From lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader Bus 003 Device 003: ID 5986:9106 Acer, Inc Integrated Camera Bus 003 Device 008: ID 06cb:00bd Synaptics, Inc. Prometheus MIS Touch Fingerprint Reader Bus 003 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 003: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 006 Device 002: ID 0424:5807 Microchip Technology, Inc. (formerly SMSC) Hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 005: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500] Bus 005 Device 006: ID 413c:2110 Dell Computer Corp. Dell Wired Multimedia Keyboard Bus 005 Device 004: ID 413c:1010 Dell Computer Corp. USB 2.0 Hub [MTT] Bus 005 Device 003: ID 0bda:4014 Realtek Semiconductor Corp. USB Audio Bus 005 Device 002: ID 0424:2807 Microchip Technology, Inc. (formerly SMSC) Hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205660] Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205660 https://bugzilla.suse.com/show_bug.cgi?id=1205660#c20 --- Comment #20 from Daniel Noga <noga.dany(a)gmail.com> --- Created attachment 863123 --> https://bugzilla.suse.com/attachment.cgi?id=863123&action=edit hwinfo -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205660] Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205660 https://bugzilla.suse.com/show_bug.cgi?id=1205660#c19 --- Comment #19 from Daniel Noga <noga.dany(a)gmail.com> --- Created attachment 863122 --> https://bugzilla.suse.com/attachment.cgi?id=863122&action=edit dmesg old kernel autosuspend disabled one restart -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205660] Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205660 https://bugzilla.suse.com/show_bug.cgi?id=1205660#c18 --- Comment #18 from Daniel Noga <noga.dany(a)gmail.com> --- Ok, I found, that Lenovo had issues with blocking thunderbolt. With long fight I managed to reset bios settings, disable it there, enable it again and it works now again. So, back to testing original issue -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205660] Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205660 https://bugzilla.suse.com/show_bug.cgi?id=1205660#c17 --- Comment #17 from Takashi Iwai <tiwai(a)suse.com> --- No, that shouldn't bring such things; the option is only to disable the runtime suspend/resume of USB devices. I suspect something else going wrong. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205660] Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205660 https://bugzilla.suse.com/show_bug.cgi?id=1205660#c16 --- Comment #16 from Daniel Noga <noga.dany(a)gmail.com> --- I mean it does not work now at all. Is it possible, that parameter can damage dock or I had just very bad luck? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205660] Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205660 https://bugzilla.suse.com/show_bug.cgi?id=1205660#c15 --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- OK, then forget about the option for now. It's just for checking whether the behavior is related with the autopm. Another test is to pass usbcore.quirks=XXXX:YYYY:b boot option, where XXXX:YYYY is the hex USB ID for your r8152 device. Let me know if this changes the behavior. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205660] Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205660 https://bugzilla.suse.com/show_bug.cgi?id=1205660#c14 --- Comment #14 from Daniel Noga <noga.dany(a)gmail.com> --- Need help. I passed that parameter usbcore.autosuspend=-1 into boot. After boot monitor blinked a few times and now thunderbolt dock does not work at all. Even with old kernel. What to do now? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205660] Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205660 https://bugzilla.suse.com/show_bug.cgi?id=1205660#c13 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |noga.dany(a)gmail.com Flags| |needinfo?(noga.dany(a)gmail.c | |om) --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- Also, could you give hwinfo output? -- You are receiving this mail because: You are the assignee for the bug.

1 0