November 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1189808] New: udp datagrams received out-of-order with kernel 5.3.18-lp152.72.1 onwards
by bugzilla_noreply＠suse.com 08 Mar '22

08 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1189808 Bug ID: 1189808 Summary: udp datagrams received out-of-order with kernel 5.3.18-lp152.72.1 onwards Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: simonalogan(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36 Build Identifier: Hi folks, We have observed that Leap 15.2 kernels 5.3.18-lp152.72.1 onwards frequently deliver UDP packets out of order. The issue is 100% reproducable on Haswell hardware, for example an Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz machine. I know UDP makes no guarantee of packet delivery order, but previous kernels always seemed to deliver packets in order. Did something change in 72.1 that would affect this? We noticed this affecting video streaming, but it is easily reproducable using iperf. Please see steps below. Thanks, Simon Reproducible: Always Steps to Reproduce: - Run an iperf server on the Haswell box. iperf3 -s - Now run a set of 10 tests, asking a remote client to receive 300Mbit blocks of UDP data. for iter in 0 1 2 3 4 5 6 7 8 9; do echo "iter: $iter"; iperf3 -c 192.168.1.10 -u -b 300M -R | grep "datagrams received out-of-order"; done Using kernel 5.3.18-lp152.60 I see no out-of-order datagrams. Using kernel 5.3.18-lp152.87 I see > 10k out-of-order datagrams on each run. Actual Results: Using the 5.3.18-lp152.87 kernel: iter: 0 [SUM] 0.0-10.0 sec 22283 datagrams received out-of-order iter: 1 [SUM] 0.0-10.0 sec 23910 datagrams received out-of-order iter: 2 [SUM] 0.0-10.0 sec 20661 datagrams received out-of-order iter: 3 [SUM] 0.0-10.0 sec 20182 datagrams received out-of-order iter: 4 [SUM] 0.0-10.0 sec 18224 datagrams received out-of-order iter: 5 [SUM] 0.0-10.0 sec 19448 datagrams received out-of-order iter: 6 [SUM] 0.0-10.0 sec 27404 datagrams received out-of-order iter: 7 [SUM] 0.0-10.0 sec 17781 datagrams received out-of-order iter: 8 [SUM] 0.0-10.0 sec 11182 datagrams received out-of-order iter: 9 [SUM] 0.0-10.0 sec 25676 datagrams received out-of-order Here's the full output from one run: [ 5] local 192.168.1.8 port 53594 connected to 192.168.1.10 port 5201 [ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-1.00 sec 35.8 MBytes 300 Mbits/sec 0.010 ms 0/25904 (0%) [ 5] 1.00-2.00 sec 35.7 MBytes 300 Mbits/sec 0.024 ms 0/25888 (0%) [ 5] 2.00-3.00 sec 35.8 MBytes 300 Mbits/sec 0.027 ms 0/25897 (0%) [ 5] 3.00-4.00 sec 35.8 MBytes 300 Mbits/sec 0.012 ms 1/25908 (0.0039%) [ 5] 4.00-5.00 sec 35.8 MBytes 300 Mbits/sec 0.021 ms -1/25897 (-0.0039%) [ 5] 5.00-6.00 sec 35.8 MBytes 300 Mbits/sec 0.017 ms 0/25897 (0%) [ 5] 6.00-7.00 sec 35.7 MBytes 300 Mbits/sec 0.032 ms 0/25887 (0%) [ 5] 7.00-8.00 sec 35.8 MBytes 300 Mbits/sec 0.012 ms 0/25909 (0%) [ 5] 8.00-9.00 sec 35.8 MBytes 300 Mbits/sec 0.009 ms 0/25899 (0%) [ 5] 9.00-10.00 sec 35.8 MBytes 300 Mbits/sec 0.015 ms 0/25897 (0%) - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-10.00 sec 358 MBytes 300 Mbits/sec 0.000 ms 0/259008 (0%) sender [SUM] 0.0-10.0 sec 22745 datagrams received out-of-order [ 5] 0.00-10.00 sec 358 MBytes 300 Mbits/sec 0.015 ms 0/258983 (0%) receiver Going the other way simon@localhost:~> iperf3 -c 192.168.1.10 -u -b 300M Connecting to host 192.168.1.10, port 5201 [ 5] local 192.168.1.8 port 56004 connected to 192.168.1.10 port 5201 [ ID] Interval Transfer Bitrate Total Datagrams [ 5] 0.00-1.00 sec 35.7 MBytes 300 Mbits/sec 25878 [ 5] 1.00-2.00 sec 35.8 MBytes 300 Mbits/sec 25898 [ 5] 2.00-3.00 sec 35.8 MBytes 300 Mbits/sec 25900 [ 5] 3.00-4.00 sec 35.8 MBytes 300 Mbits/sec 25910 [ 5] 4.00-5.00 sec 35.7 MBytes 300 Mbits/sec 25878 [ 5] 5.00-6.00 sec 35.8 MBytes 300 Mbits/sec 25919 [ 5] 6.00-7.00 sec 35.7 MBytes 300 Mbits/sec 25882 [ 5] 7.00-8.00 sec 35.8 MBytes 300 Mbits/sec 25897 [ 5] 8.00-9.00 sec 35.8 MBytes 300 Mbits/sec 25898 [ 5] 9.00-10.00 sec 35.8 MBytes 300 Mbits/sec 25898 - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-10.00 sec 358 MBytes 300 Mbits/sec 0.000 ms 0/258958 (0%) sender [ 5] 0.00-10.00 sec 358 MBytes 300 Mbits/sec 0.013 ms 6/258958 (0.0023%) receiver Expected Results: Based on kernel 5.3.18-lp152.60, I expect no out-of-order datagrams. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1193213] New: Two-fingers scrolling on touch-pad no longer working
by bugzilla_noreply＠suse.com 04 Mar '22

04 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193213 Bug ID: 1193213 Summary: Two-fingers scrolling on touch-pad no longer working 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: marco.varlese(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With the latest update to 5.15 the touch-pad two-fingers scrolling does not work anymore. At the same time, it is possible to note an overall slowness of the pointer movement when using the touch-pad itself. Rebooting the machine to the previous kernel (5.14) shows that the previous kernel does not present the issue. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1182304] New: Integrated USB3 port / hub only works with AC adapter connected
by bugzilla_noreply＠suse.com 01 Mar '22

01 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1182304 Bug ID: 1182304 Summary: Integrated USB3 port / hub only works with AC adapter connected 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: rs.opensuse(a)spitzenpfeil.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kernel: 5.10.12-1-default Yet again I'm having issues with my laptops integrated USB3 port / hub. One of the USB-3 + USB-C ports only works with the AC adapter plugged in. Pulling the plug with devices connected leads to stuckage. Same hardware as in: https://bugzilla.opensuse.org/show_bug.cgi?id=1167146 -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1180742] New: [amdgpu]An AMD Vega series GPU randomly crashes
by bugzilla_noreply＠suse.com 28 Feb '22

28 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1180742 Bug ID: 1180742 Summary: [amdgpu]An AMD Vega series GPU randomly crashes Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: srid(a)rkmail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 844970 --> http://bugzilla.opensuse.org/attachment.cgi?id=844970&action=edit partial kernel log The AMDGPU kernel driver randomly crashes GPU, usually under load, with Radeon VII hardware. The GPU hang is relatively hard to hit, as it usually takes 5 to 7 days before it crashes. After a hang it attempts to reset the GPU, but sometimes the reset fails and system stays sort of unresponsive. You can still access it over network, and there's some sort of reaction on keyboard events, but display stays dead. Also, it seems to bring PCIe bus down to 1.0 mode, and it stays that until reboot. There's an upstream bug open that may have something to do about it: https://gitlab.freedesktop.org/drm/amd/-/issues/716 That particular GPU works fine on Windows machine openSUSE Leap 15.2, kernel 5.3.18-lp152.57-default #1 SMP Fri Dec 4 07:27:58 UTC 2020 (7be5551) -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1180380] New: Blank external monitor after resume from suspend
by bugzilla_noreply＠suse.com 21 Feb '22

21 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1180380 Bug ID: 1180380 Summary: Blank external monitor after resume from suspend Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jack(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 844706 --> https://bugzilla.suse.com/attachment.cgi?id=844706&action=edit dmesg from the system After resuming from suspend to RAM the external display connected through DVI port on the docking station remains blank. Internal display is fine. I can use xrandr to make the monitor work like: xrandr --output DP1-1 --mode some-other-mode xrandr --output DP1-1 --mode original-mode -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1190621] New: AX200 2.4G frequently disconnected (iwlwifi 0000:02:00.0: Unhandled alg: 0x3f0707)
by bugzilla_noreply＠suse.com 20 Feb '22

20 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190621 Bug ID: 1190621 Summary: AX200 2.4G frequently disconnected (iwlwifi 0000:02:00.0: Unhandled alg: 0x3f0707) 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: qydwhotmail(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Not sure if it's the suitable place to report. WiFi connection to 2.4G AP is very unstable, while the android phone does not have this issue. dmesg output: [20600.981734] iwlwifi 0000:02:00.0: reached 10 old SN frames from 20:76:93:xx:xx:xx on queue 5, stopping BA session on TID 0 [20601.387564] iwlwifi 0000:02:00.0: reached 10 old SN frames from 20:76:93:xx:xx:xx on queue 5, stopping BA session on TID 0 [20615.037674] iwlwifi 0000:02:00.0: reached 10 old SN frames from 20:76:93:xx:xx:xx on queue 5, stopping BA session on TID 0 [20615.220110] iwlwifi 0000:02:00.0: reached 10 old SN frames from 20:76:93:xx:xx:xx on queue 5, stopping BA session on TID 0 [20620.922268] iwlwifi 0000:02:00.0: reached 10 old SN frames from 20:76:93:xx:xx:xx on queue 5, stopping BA session on TID 0 [20622.751843] wlp2s0: Connection to AP 20:76:93:xx:xx:xx lost [20628.176527] wlp2s0: authenticate with 20:76:93:xx:xx:xx [20628.184436] wlp2s0: send auth to 20:76:93:xx:xx:xx (try 1/3) [20628.216269] iwlwifi 0000:02:00.0: Unhandled alg: 0x3f0707 [20628.216509] iwlwifi 0000:02:00.0: Unhandled alg: 0x3f0707 [20628.216911] iwlwifi 0000:02:00.0: Unhandled alg: 0x3f0707 [20628.217196] iwlwifi 0000:02:00.0: Unhandled alg: 0x3f0707 [20628.217441] iwlwifi 0000:02:00.0: Unhandled alg: 0x3f0707 [20628.233867] wlp2s0: authenticated [20628.241276] wlp2s0: associate with 20:76:93:xx:xx:xx (try 1/3) [20628.246673] iwlwifi 0000:02:00.0: Unhandled alg: 0x3f0707 [20628.376489] iwlwifi 0000:02:00.0: Unhandled alg: 0x3f0707 [20628.380013] iwlwifi 0000:02:00.0: Unhandled alg: 0x3f0707 [20628.380269] wlp2s0: RX AssocResp from 20:76:93:xx:xx:xx (capab=0x431 status=0 aid=3) [20628.383872] iwlwifi 0000:02:00.0: Unhandled alg: 0x3f0707 [20628.385709] iwlwifi 0000:02:00.0: Unhandled alg: 0x3f0707 [20628.392519] wlp2s0: associated -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1193125] New: System crashes heavily after updating to Linux 5.16.0-rc2-next-20211125 (kernel BUG at mm/page_table_check.c:101!)
by bugzilla_noreply＠suse.com 20 Feb '22

20 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193125 Bug ID: 1193125 Summary: System crashes heavily after updating to Linux 5.16.0-rc2-next-20211125 (kernel BUG at mm/page_table_check.c:101!) 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: qydwhotmail(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 854094 --> http://bugzilla.opensuse.org/attachment.cgi?id=854094&action=edit journactl output before reboot Linux 5.16.0-rc2-next-20211124 is still normal. journactl output updated -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1182535] New: Start-up hangs with iommu message
by bugzilla_noreply＠suse.com 18 Feb '22

18 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1182535 Bug ID: 1182535 Summary: Start-up hangs with iommu message Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: pchadwick(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Leap startup stops with: "Error getting iommu info. ist the iommu enabled?" "Error initializing iommuv2" Hardware is AMD Ryzen 5 3400G on an ASRock B450M based motherboard -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1182349] New: WARNING: CPU: 7 PID: 90 at ../drivers/gpu/drm/i915/display/intel_dp.c:1895 intel_dp_max_link_rate+0x7e/0xa0
by bugzilla_noreply＠suse.com 18 Feb '22

18 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1182349 Bug ID: 1182349 Summary: WARNING: CPU: 7 PID: 90 at ../drivers/gpu/drm/i915/display/intel_dp.c:1895 intel_dp_max_link_rate+0x7e/0xa0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 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: --- Trying to feed an external EDID for i915 to facilitate headless operation on an Intel NUC resulted in repeated warnings Feb 17 08:47:38 localhost kernel: ------------[ cut here ]------------ Feb 17 08:47:38 localhost kernel: i915 0000:00:02.0: drm_WARN_ON(len <= 0) Feb 17 08:47:38 localhost kernel: WARNING: CPU: 7 PID: 90 at ../drivers/gpu/drm/i915/display/in> and a non-working display. (Arguably the display doesn't work as it's headless, but the vncviewer for Intel AMT stays blank, too. It doesn't when a monitor is connected.) -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1182226] New: amdgpu driver not working in Leap 15.2
by bugzilla_noreply＠suse.com 18 Feb '22

18 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1182226 Bug ID: 1182226 Summary: amdgpu driver not working in Leap 15.2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: donaldmleslie(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am running Leap 15.2 on an HP 855 G7 The kernel supplied with Leap 15.2 is kernel-default-5.3.18-lp152.63.1.x86_64 It does not see the HDMI port I get the following results: From hwinfo: 25: PCI 300.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: svHJ.HB+rwQfOiT4 Parent ID: JZZT.e+TNXSUNut3 SysFS ID: /devices/pci0000:00/0000:00:08.1/0000:03:00.0 SysFS BusID: 0000:03:00.0 Hardware Class: graphics card Device Name: "Onboard IGD" Model: "ATI Renoir" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x1636 "Renoir" SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x8760 Revision: 0xd1 Memory Range: 0x460000000-0x46fffffff (ro,non-prefetchable) Memory Range: 0x470000000-0x4701fffff (ro,non-prefetchable) I/O Ports: 0x1000-0x1fff (rw) Memory Range: 0xfc300000-0xfc37ffff (rw,non-prefetchable) IRQ: 255 (no events) Module Alias: "pci:v00001002d00001636sv0000103Csd00008760bc03sc00i00" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #39 (PCI bridge) xrandr --listproviders xrandr: Failed to get size of gamma for output default Providers: number : 0 From glxinfo: OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 9.0.1, 128 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.3.4 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.3.4 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.1 Mesa 19.3.4 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 OpenGL ES profile extensions: inxi -G Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: N/A Device-2: N/A type: USB driver: uvcvideo Display: x11 server: X.Org 1.20.3 driver: ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~77Hz OpenGL: renderer: llvmpipe (LLVM 9.0.1 128 bits) v: 3.3 Mesa 19.3.4 After much fumbling trying to find what was wrong I added the .../kernel/stable and got a 5.10 kernel. Now everything works fine. I now get: 25: PCI 300.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: svHJ.HB+rwQfOiT4 Parent ID: JZZT.e+TNXSUNut3 SysFS ID: /devices/pci0000:00/0000:00:08.1/0000:03:00.0 SysFS BusID: 0000:03:00.0 Hardware Class: graphics card Device Name: "Onboard IGD" Model: "ATI Renoir" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x1636 "Renoir" SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x8760 Revision: 0xd1 Driver: "amdgpu" Driver Modules: "amdgpu" Memory Range: 0x460000000-0x46fffffff (ro,non-prefetchable) Memory Range: 0x470000000-0x4701fffff (ro,non-prefetchable) I/O Ports: 0x1000-0x1fff (rw) Memory Range: 0xfc300000-0xfc37ffff (rw,non-prefetchable) IRQ: 49 (no events) Module Alias: "pci:v00001002d00001636sv0000103Csd00008760bc03sc00i00" Driver Info #0: Driver Status: amdgpu is active Driver Activation Cmd: "modprobe amdgpu" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #39 (PCI bridge) xrandr --listproviders Providers: number : 1 Provider 0: id: 0x57; cap: 0xf (Source Output, Sink Output, Source Offload, Sink Offload); crtcs: 4; outputs: 4; associateproviders: 0; name: Unknown AMD Radeon GPU @ pci:0000:03:00.0 output eDP output HDMI-A-0 output DisplayPort-0 output DisplayPort-1 From glxinfo: OpenGL vendor string: AMD OpenGL renderer string: AMD RENOIR (DRM 3.40.0, 5.10.12-1-default, LLVM 11.0.1) OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.3.4 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.3.4 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.3.4 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: inxi -G Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel Device-2: Luxvisions Innotech Limited HP HD Camera type: USB driver: uvcvideo Display: x11 server: X.org 1.20.10 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: <xdpyinfo missing> OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.10.12-1-default LLVM 11.0.1) v: 4.6 Mesa 20.3.4 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1188896] New: "BUG: Bad rss-counter state mm:00000000e555b579 type:MM_FILEPAGES val:-256" during build of cross-epiphany-gcc11-bootstrap
by bugzilla_noreply＠suse.com 17 Feb '22

17 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188896 Bug ID: 1188896 Summary: "BUG: Bad rss-counter state mm:00000000e555b579 type:MM_FILEPAGES val:-256" during build of cross-epiphany-gcc11-bootstrap Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ada.lovelace(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This bug report is a mixture of gcc11 and Linux kernel. The build process of cross-epiphany-gcc11-bootstrap is hanging since 1 day with following information: [ 865s] g++ -fno-PIE -c -DIN_GCC_FRONTEND -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -funwind-tables -fasynchronous-unwind-tables -U_FORTIFY_SOURCE -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -Ic -I../../gcc -I../../gcc/c -I../../gcc/../include -I../../gcc/../libcpp/include -I../../gcc/../libcody -I../../gcc/../libdecnumber -I../../gcc/../libdecnumber/dpd -I../libdecnumber -I../../gcc/../libbacktrace -o c/c-aux-info.o -MT c/c-aux-info.o -MMD -MP -MF c/.deps/c-aux-info.TPo ../../gcc/c/c-aux-info.c [ 866s] In file included from ./tm.h:23, [ 866s] from ../../gcc/c/c-aux-info.c:26: [ 866s] ../../gcc/config/elfos.h:201: warning: "READONLY_DATA_SECTION_ASM_OP" redefined [ 866s] 201 | #define READONLY_DATA_SECTION_ASM_OP "\t.section\t.rodata" [ 866s] | [ 866s] In file included from ./tm.h:21, [ 866s] from ../../gcc/c/c-aux-info.c:26: [ 866s] ../../gcc/config/epiphany/epiphany.h:671: note: this is the location of the previous definition [ 866s] 671 | #define READONLY_DATA_SECTION_ASM_OP "\t.section .rodata" [ 866s] | [ 871s] g++ -fno-PIE -c -DIN_GCC_FRONTEND -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -funwind-tables -fasynchronous-unwind-tables -U_FORTIFY_SOURCE -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -Ic -I../../gcc -I../../gcc/c -I../../gcc/../include -I../../gcc/../libcpp/include -I../../gcc/../libcody -I../../gcc/../libdecnumber -I../../gcc/../libdecnumber/dpd -I../libdecnumber -I../../gcc/../libbacktrace -o c/c-objc-common.o -MT c/c-objc-common.o -MMD -MP -MF c/.deps/c-objc-common.TPo ../../gcc/c/c-objc-common.c [ 876s] [ 846.778933] BUG: Bad rss-counter state mm:00000000e555b579 type:MM_FILEPAGES val:-256 ... [ 2241s] g++ -fno-PIE -c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -funwind-tables -fasynchronous-unwind-tables -U_FORTIFY_SOURCE -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/../include -I../../gcc/../libcpp/include -I../../gcc/../libcody -I../../gcc/../libdecnumber -I../../gcc/../libdecnumber/dpd -I../libdecnumber -I../../gcc/../libbacktrace -o reload1.o -MT reload1.o -MMD -MP -MF ./.deps/reload1.TPo ../../gcc/reload1.c [ 2241s] [ 2211.961786] BUG: Bad page state in process cc1plus pfn:11d401 [ 2241s] [ 2211.967831] BUG: Bad page state in process cc1plus pfn:11d402 [ 2241s] [ 2211.968097] BUG: Bad page state in process cc1plus pfn:11d403 [ 2241s] [ 2211.968458] BUG: Bad page state in process cc1plus pfn:11d404 [ 2241s] [ 2211.968668] BUG: Bad page state in process cc1plus pfn:11d405 [ 2241s] [ 2211.968878] BUG: Bad page state in process cc1plus pfn:11d406 [ 2241s] [ 2211.969081] BUG: Bad page state in process cc1plus pfn:11d407 [ 2241s] [ 2211.969287] BUG: Bad page state in process cc1plus pfn:11d408 . [ 865s] g++ -fno-PIE -c -DIN_GCC_FRONTEND -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -funwind-tables -fasynchronous-unwind-tables -U_FORTIFY_SOURCE -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -Ic -I../../gcc -I../../gcc/c -I../../gcc/../include -I../../gcc/../libcpp/include -I../../gcc/../libcody -I../../gcc/../libdecnumber -I../../gcc/../libdecnumber/dpd -I../libdecnumber -I../../gcc/../libbacktrace -o c/c-aux-info.o -MT c/c-aux-info.o -MMD -MP -MF c/.deps/c-aux-info.TPo ../../gcc/c/c-aux-info.c [ 866s] In file included from ./tm.h:23, [ 866s] from ../../gcc/c/c-aux-info.c:26: [ 866s] ../../gcc/config/elfos.h:201: warning: "READONLY_DATA_SECTION_ASM_OP" redefined [ 866s] 201 | #define READONLY_DATA_SECTION_ASM_OP "\t.section\t.rodata" [ 866s] | [ 866s] In file included from ./tm.h:21, [ 866s] from ../../gcc/c/c-aux-info.c:26: [ 866s] ../../gcc/config/epiphany/epiphany.h:671: note: this is the location of the previous definition [ 866s] 671 | #define READONLY_DATA_SECTION_ASM_OP "\t.section .rodata" [ 866s] | [ 871s] g++ -fno-PIE -c -DIN_GCC_FRONTEND -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -funwind-tables -fasynchronous-unwind-tables -U_FORTIFY_SOURCE -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -Ic -I../../gcc -I../../gcc/c -I../../gcc/../include -I../../gcc/../libcpp/include -I../../gcc/../libcody -I../../gcc/../libdecnumber -I../../gcc/../libdecnumber/dpd -I../libdecnumber -I../../gcc/../libbacktrace -o c/c-objc-common.o -MT c/c-objc-common.o -MMD -MP -MF c/.deps/c-objc-common.TPo ../../gcc/c/c-objc-common.c [ 876s] [ 846.778933] BUG: Bad rss-counter state mm:00000000e555b579 type:MM_FILEPAGES val:-256 [ 2241s] In file included from ./tm.h:23, [ 2241s] from ../../gcc/backend.h:28, [ 2241s] from ../../gcc/reload1.c:23: [ 2241s] ../../gcc/config/elfos.h:201: warning: "READONLY_DATA_SECTION_ASM_OP" redefined [ 2241s] 201 | #define READONLY_DATA_SECTION_ASM_OP "\t.section\t.rodata" [ 2241s] | [ 2241s] In file included from ./tm.h:21, [ 2241s] from ../../gcc/backend.h:28, [ 2241s] from ../../gcc/reload1.c:23: [ 2241s] ../../gcc/config/epiphany/epiphany.h:671: note: this is the location of the previous definition [ 2241s] 671 | #define READONLY_DATA_SECTION_ASM_OP "\t.section .rodata" ... [ 2243s] g++ -fno-PIE -c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -funwind-tables -fasynchronous-unwind-tables -U_FORTIFY_SOURCE -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/../include -I../../gcc/../libcpp/include -I../../gcc/../libcody -I../../gcc/../libdecnumber -I../../gcc/../libdecnumber/dpd -I../libdecnumber -I../../gcc/../libbacktrace -o resource.o -MT resource.o -MMD -MP -MF ./.deps/resource.TPo ../../gcc/resource.c [ 2243s] In file included from ./tm.h:23, [ 2243s] from ../../gcc/backend.h:28, [ 2243s] from ../../gcc/resource.c:23: [ 2243s] ../../gcc/config/elfos.h:201: warning: "READONLY_DATA_SECTION_ASM_OP" redefined [ 2243s] 201 | #define READONLY_DATA_SECTION_ASM_OP "\t.section\t.rodata" [ 2243s] | [ 2243s] In file included from ./tm.h:21, [ 2243s] from ../../gcc/backend.h:28, [ 2243s] from ../../gcc/resource.c:23: [ 2243s] ../../gcc/config/epiphany/epiphany.h:671: note: this is the location of the previous definition [ 2243s] 671 | #define READONLY_DATA_SECTION_ASM_OP "\t.section .rodata" [ 2243s] | [ 2301s] [ 2272.129159] rcu: INFO: rcu_sched self-detected stall on CPU [ 2301s] [ 2272.129930] rcu: 1-...!: (2004 ticks this GP) idle=cda/1/0x4000000000000002 softirq=72272/72272 fqs=21 [ 2301s] [ 2272.130195] rcu: rcu_sched kthread starved for 5803 jiffies! g57669 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1 [ 2301s] [ 2272.130474] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior. [ 2301s] [ 2272.130715] rcu: RCU grace-period kthread stack dump: [ 2301s] [ 2272.130909] rcu: Stack dump where RCU GP kthread last ran: [ 2481s] [ 2452.178521] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 2481s] [ 2452.179275] rcu: 1-...!: (8411 ticks this GP) idle=cda/1/0x4000000000000000 softirq=72272/72272 fqs=21 [ 2481s] [ 2452.179617] rcu: rcu_sched kthread starved for 23808 jiffies! g57669 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1 [ 2481s] [ 2452.179949] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior. [ 2481s] [ 2452.180241] rcu: RCU grace-period kthread stack dump: [ 2481s] [ 2452.180457] rcu: Stack dump where RCU GP kthread last ran: [ 2661s] [ 2632.370659] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 2661s] [ 2632.422457] rcu: 1-...!: (15430 ticks this GP) idle=cda/1/0x4000000000000000 softirq=72272/72272 fqs=21 [ 2661s] [ 2632.422835] rcu: rcu_sched kthread starved for 41827 jiffies! g57669 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1 [ 2661s] [ 2632.423099] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior. [ 2661s] [ 2632.423322] rcu: RCU grace-period kthread stack dump: [ 2661s] [ 2632.423498] rcu: Stack dump where RCU GP kthread last ran: [ 2841s] [ 2812.408987] rcu: INFO: rcu_sched self-detected stall on CPU [ 2841s] [ 2812.409246] rcu: 1-...!: (21988 ticks this GP) idle=cda/1/0x4000000000000002 softirq=72272/72272 fqs=21 [ 2841s] [ 2812.409342] rcu: rcu_sched kthread starved for 59831 jiffies! g57669 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1 [ 2841s] [ 2812.464705] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior. [ 2841s] [ 2812.464890] rcu: RCU grace-period kthread stack dump: [ 2841s] [ 2812.465021] rcu: Stack dump where RCU GP kthread last ran: [ 3022s] [ 2992.448529] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 3022s] [ 2992.568724] rcu: 1-...!: (29161 ticks this GP) idle=cda/1/0x4000000000000000 softirq=72272/72272 fqs=21 [ 3022s] [ 2992.568847] rcu: rcu_sched kthread starved for 77835 jiffies! g57669 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1 [ 3022s] [ 2992.568940] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior. [ 3022s] [ 2992.569021] rcu: RCU grace-period kthread stack dump: [ 3022s] [ 2992.569104] rcu: Stack dump where RCU GP kthread last ran: [ 3202s] [ 3172.579399] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 3202s] [ 3172.638172] rcu: 1-...!: (36644 ticks this GP) idle=cda/1/0x4000000000000000 softirq=72272/72272 fqs=21 [ 3202s] [ 3172.638356] rcu: rcu_sched kthread starved for 95848 jiffies! g57669 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1 [ 3202s] [ 3172.638486] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior. [ 3202s] [ 3172.638608] rcu: RCU grace-period kthread stack dump: [ 3202s] [ 3172.638733] rcu: Stack dump where RCU GP kthread last ran: [ 3382s] [ 3352.635605] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 3382s] [ 3352.785267] rcu: 1-...!: (44755 ticks this GP) idle=cda/1/0x4000000000000000 softirq=72272/72272 fqs=21 [ 3382s] [ 3352.796719] rcu: rcu_sched kthread starved for 113853 jiffies! g57669 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1 [ 3382s] [ 3352.807909] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior. [ 3382s] [ 3352.808153] rcu: RCU grace-period kthread stack dump: [ 3382s] [ 3352.809425] rcu: Stack dump where RCU GP kthread last ran: [ 3562s] [ 3532.659925] rcu: INFO: rcu_sched self-detected stall on CPU [ 3562s] [ 3532.671463] rcu: 1-...!: (53554 ticks this GP) idle=cda/1/0x4000000000000002 softirq=72272/72272 fqs=21 [ 3562s] [ 3532.697304] rcu: rcu_sched kthread starved for 131859 jiffies! g57669 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1 [ 3562s] [ 3532.697588] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior. [ 3562s] [ 3532.697733] rcu: RCU grace-period kthread stack dump: [ 3562s] [ 3532.697877] rcu: Stack dump where RCU GP kthread last ran: [ 3742s] [ 3712.708722] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 3742s] [ 3712.709943] rcu: 1-...!: (61764 ticks this GP) idle=cda/1/0x4000000000000000 softirq=72272/72272 fqs=21 [ 3742s] [ 3712.710087] rcu: rcu_sched kthread starved for 149861 jiffies! g57669 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1 [ 3742s] [ 3712.710195] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior. [ 3742s] [ 3712.710286] rcu: RCU grace-period kthread stack dump: [ 3742s] [ 3712.710380] rcu: Stack dump where RCU GP kthread last ran: [ 3922s] [ 3892.766529] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 3922s] [ 3892.770375] rcu: 1-...!: (70277 ticks this GP) idle=cda/1/0x4000000000000000 softirq=72272/72272 fqs=21 [ 3922s] [ 3892.805972] rcu: rcu_sched kthread starved for 167870 jiffies! g57669 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1 [ 3922s] [ 3892.806225] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior. [ 3922s] [ 3892.806499] rcu: RCU grace-period kthread stack dump: Kernel version: 5.13.4-1.1: https://github.com/openSUSE/kernel/releases/tag/v5.13.4 Logs: https://build.opensuse.org/build/openSUSE:Factory:zSystems/standard/s390x/c… Latest updates for s390x July 21: https://build.opensuse.org/package/view_file/openSUSE:Factory:zSystems/cros… -- You are receiving this mail because: You are the assignee for the bug.

1 25

[Bug 1181327] New: kernel splat, screen remains in power save mode
by bugzilla_noreply＠suse.com 11 Feb '22

11 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1181327 Bug ID: 1181327 Summary: kernel splat, screen remains in power save mode Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jgross(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- System was inactive for some time, so screens were going to power save mode. After moving the mouse only two of my 3 screens became alive again, the third one remained black. In messages I see: 2021-01-23T20:16:09.512513+01:00 lap kernel: [14492.019503] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) 2021-01-23T20:16:09.512538+01:00 lap kernel: [14492.019598] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in shared_dpll (expected 00000000b8b74152, found 00000000971b3ba1) 2021-01-23T20:16:09.512544+01:00 lap kernel: [14492.019687] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x00000003, found 0x00000001) 2021-01-23T20:16:09.512546+01:00 lap kernel: [14492.019786] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) 2021-01-23T20:16:09.512548+01:00 lap kernel: [14492.019863] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in port_clock (expected 270000, found 540000) 2021-01-23T20:16:09.512550+01:00 lap kernel: [14492.019866] ------------[ cut here ]------------ 2021-01-23T20:16:09.512552+01:00 lap kernel: [14492.019867] pipe state doesn't match! 2021-01-23T20:16:09.512554+01:00 lap kernel: [14492.020019] WARNING: CPU: 8 PID: 1625 at ../drivers/gpu/drm/i915/display/intel_display.c:13159 intel_atomic_commit_tail+0x1414/0x14e0 [i915] 2021-01-23T20:16:09.512556+01:00 lap kernel: [14492.020021] Modules linked in: fuse tun ccm rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace sunrpc fscache af_packet dmi_sysfs bnep typec_displayport snd_hda_codec_hdmi uvcvideo v4l2_common videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common btusb btrtl videodev btbcm btintel mc bluetooth ecdh_generic ecc hid_multitouch sof_pci_dev snd_sof_intel_hda_common iTCO_wdt snd_sof_intel_hda mei_hdcp mei_wdt iTCO_vendor_support intel_rapl_msr dell_rbtn msr x86_pkg_temp_thermal snd_sof_intel_byt dell_laptop intel_powerclamp snd_sof_intel_ipc dell_smm_hwmon snd_sof coretemp snd_sof_xtensa_dsp kvm_intel snd_soc_skl kvm snd_soc_hdac_hda snd_hda_ext_core nls_iso8859_1 snd_soc_skl_ipc snd_soc_sst_ipc iwlmvm snd_hda_codec_realtek snd_soc_sst_dsp nls_cp437 irqbypass crct10dif_pclmul crc32_pclmul snd_soc_acpi_intel_match ghash_clmulni_intel snd_soc_acpi vfat snd_hda_codec_generic xfs ledtrig_audio mac80211 snd_soc_core fat aesni_intel libarc4 snd_compress aes_x86_64 2021-01-23T20:16:09.512563+01:00 lap kernel: [14492.020067] snd_pcm_dmaengine crypto_simd cryptd snd_hda_intel glue_helper iwlwifi snd_hda_codec snd_hda_core dell_wmi snd_hwdep dell_smbios dcdbas cfg80211 snd_pcm joydev pcspkr snd_timer efi_pstore snd idma64 mei_me rtsx_pci_ms processor_thermal_device intel_wmi_thunderbolt dell_wmi_descriptor wmi_bmof i2c_i801 mei memstick intel_rapl_common rfkill soundcore intel_lpss_pci intel_lpss intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone dell_smo8800 ucsi_acpi typec_ucsi typec thermal intel_hid battery int3400_thermal acpi_thermal_rel sparse_keymap acpi_pad ac hid_generic usbhid nouveau mxm_wmi btrfs libcrc32c xor i915 raid6_pq rtsx_pci_sdmmc mmc_core ttm i2c_algo_bit drm_kms_helper xhci_pci xhci_hcd syscopyarea sysfillrect sysimgblt fb_sys_fops crc32c_intel serio_raw drm nvme usbcore nvme_core rtsx_pci i2c_hid wmi video pinctrl_cannonlake pinctrl_intel button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs 2021-01-23T20:16:09.512565+01:00 lap kernel: [14492.020121] CPU: 8 PID: 1625 Comm: X Not tainted 5.3.18-lp152.60-default #1 openSUSE Leap 15.2 2021-01-23T20:16:09.512567+01:00 lap kernel: [14492.020123] Hardware name: Dell Inc. Precision 5530/0NFGCT, BIOS 1.8.1 02/01/2019 2021-01-23T20:16:09.512569+01:00 lap kernel: [14492.020202] RIP: 0010:intel_atomic_commit_tail+0x1414/0x14e0 [i915] 2021-01-23T20:16:09.512571+01:00 lap kernel: [14492.020206] Code: e9 1d f6 ff ff e8 cc 48 42 e5 0f 0b e9 2c f2 ff ff 0f b6 f0 48 c7 c7 b0 fd 73 c0 e8 96 62 d9 ff e9 8a fb ff ff e8 ac 48 42 e5 <0f> 0b e9 89 f2 ff ff e8 a0 48 42 e5 0f 0b 0f b6 0c 24 e9 a5 f8 ff 2021-01-23T20:16:09.512573+01:00 lap kernel: [14492.020208] RSP: 0018:ffffa861c05d3b30 EFLAGS: 00010282 2021-01-23T20:16:09.512575+01:00 lap kernel: [14492.020211] RAX: 0000000000000000 RBX: ffff9210529bf000 RCX: 0000000000000006 2021-01-23T20:16:09.512576+01:00 lap kernel: [14492.020213] RDX: 0000000000000007 RSI: 0000000000000092 RDI: ffff92125c419a10 2021-01-23T20:16:09.512579+01:00 lap kernel: [14492.020215] RBP: ffff920b07178000 R08: 0000000000000526 R09: 0000000000000001 2021-01-23T20:16:09.512581+01:00 lap kernel: [14492.020217] R10: 0000000000000007 R11: 0000000000000001 R12: ffff921142d20000 2021-01-23T20:16:09.512583+01:00 lap kernel: [14492.020219] R13: ffff921251f802b8 R14: ffff921251f80000 R15: ffff921251f802b0 2021-01-23T20:16:09.512585+01:00 lap kernel: [14492.020222] FS: 00007f474120eec0(0000) GS:ffff92125c400000(0000) knlGS:0000000000000000 2021-01-23T20:16:09.512586+01:00 lap kernel: [14492.020224] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2021-01-23T20:16:09.512588+01:00 lap kernel: [14492.020226] CR2: 00007f474122e000 CR3: 0000000854f32006 CR4: 00000000003606e0 2021-01-23T20:16:09.512607+01:00 lap kernel: [14492.020228] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 2021-01-23T20:16:09.512609+01:00 lap kernel: [14492.020229] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 2021-01-23T20:16:09.512610+01:00 lap kernel: [14492.020231] Call Trace: 2021-01-23T20:16:09.512612+01:00 lap kernel: [14492.020316] intel_atomic_commit+0x273/0x350 [i915] 2021-01-23T20:16:09.512615+01:00 lap kernel: [14492.020358] drm_atomic_connector_commit_dpms+0xe5/0xf0 [drm] 2021-01-23T20:16:09.512616+01:00 lap kernel: [14492.020398] drm_mode_obj_set_property_ioctl+0x19f/0x2e0 [drm] 2021-01-23T20:16:09.512619+01:00 lap kernel: [14492.020437] ? drm_connector_set_obj_prop+0x70/0x70 [drm] 2021-01-23T20:16:09.512620+01:00 lap kernel: [14492.020472] drm_connector_property_set_ioctl+0x3e/0x60 [drm] 2021-01-23T20:16:09.512622+01:00 lap kernel: [14492.020501] drm_ioctl_kernel+0xac/0xf0 [drm] 2021-01-23T20:16:09.512624+01:00 lap kernel: [14492.020531] drm_ioctl+0x2eb/0x3b0 [drm] 2021-01-23T20:16:09.512625+01:00 lap kernel: [14492.020566] ? drm_connector_set_obj_prop+0x70/0x70 [drm] 2021-01-23T20:16:09.512627+01:00 lap kernel: [14492.020574] ? __switch_to_xtra+0x2c8/0x580 2021-01-23T20:16:09.512629+01:00 lap kernel: [14492.020579] ? update_load_avg+0x1ac/0x620 2021-01-23T20:16:09.512631+01:00 lap kernel: [14492.020583] ? update_load_avg+0x1ac/0x620 2021-01-23T20:16:09.512633+01:00 lap kernel: [14492.020590] do_vfs_ioctl+0xa0/0x680 2021-01-23T20:16:09.512635+01:00 lap kernel: [14492.020597] ? __schedule+0x305/0x750 2021-01-23T20:16:09.512636+01:00 lap kernel: [14492.020602] ksys_ioctl+0x70/0x80 2021-01-23T20:16:09.512637+01:00 lap kernel: [14492.020608] __x64_sys_ioctl+0x16/0x20 2021-01-23T20:16:09.512640+01:00 lap kernel: [14492.020614] do_syscall_64+0x65/0x1f0 2021-01-23T20:16:09.512641+01:00 lap kernel: [14492.020618] entry_SYSCALL_64_after_hwframe+0x44/0xa9 2021-01-23T20:16:09.512643+01:00 lap kernel: [14492.020622] RIP: 0033:0x7f473eb02ac7 2021-01-23T20:16:09.512645+01:00 lap kernel: [14492.020626] Code: b3 66 90 48 8b 05 d1 13 2c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a1 13 2c 00 f7 d8 64 89 01 48 2021-01-23T20:16:09.512647+01:00 lap kernel: [14492.020628] RSP: 002b:00007ffdce072df8 EFLAGS: 00003246 ORIG_RAX: 0000000000000010 2021-01-23T20:16:09.512649+01:00 lap kernel: [14492.020631] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f473eb02ac7 2021-01-23T20:16:09.512651+01:00 lap kernel: [14492.020632] RDX: 00007ffdce072e30 RSI: 00000000c01064ab RDI: 000000000000000e 2021-01-23T20:16:09.512653+01:00 lap kernel: [14492.020634] RBP: 00007ffdce072e30 R08: 0000564866855dc0 R09: 000056486669fe70 2021-01-23T20:16:09.512655+01:00 lap kernel: [14492.020636] R10: 0000000000000000 R11: 0000000000003246 R12: 00000000c01064ab 2021-01-23T20:16:09.512657+01:00 lap kernel: [14492.020637] R13: 000000000000000e R14: 000056486669e3a0 R15: 0000564864c7a480 2021-01-23T20:16:09.512659+01:00 lap kernel: [14492.020641] ---[ end trace ca64441636ed8972 ]--- This happened twice today. Hardware config: Dell Precision Laptop with Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz cpu # lspci 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0 (rev 10) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #1 (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:17.0 SATA controller: Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller (rev 10) 00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #17 (rev f0) 00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0) 00:1c.4 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #5 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10) 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 01:00.0 3D controller: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] (rev a1) 02:00.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02) 03:00.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02) 03:01.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02) 03:02.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02) 3a:00.0 USB controller: Intel Corporation JHL6340 Thunderbolt 3 USB 3.1 Controller (C step) [Alpine Ridge 2C 2016] (rev 02) 3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) 3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 3d:00.0 Non-Volatile memory controller: Toshiba Corporation Device 0116 The affected monitor is connected to the docking station (via thunderbolt) I couldn't shut down the system normally when it happened the first time, it would hang. At the second incident I let the system just sit there and in the next morning it was unusable, even network access wasn't possible. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1187701] New: Ten64 fails to boot (kernel panic in initramfs) from nvme after upgrade to kernel 5.3.18-59.5-default
by bugzilla_noreply＠suse.com 03 Feb '22

03 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1187701 Bug ID: 1187701 Summary: Ten64 fails to boot (kernel panic in initramfs) from nvme after upgrade to kernel 5.3.18-59.5-default Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: aarch64 OS: openSUSE Leap 15.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: matt(a)traverse.com.au QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 850544 --> http://bugzilla.opensuse.org/attachment.cgi?id=850544&action=edit Failed boot on kernel 5.3.18-59.5-default Hello, After Leap 15.3 appliance images were updated recently, I have found the newer versions no longer boot on Ten64. Working image build: openSUSE-Leap-15.3-ARM-JeOS-efi.aarch64-2021.05.21-Build9.94.raw.xz / kernel 5.3.18-57-default Not working: openSUSE-Leap-15.3-ARM-JeOS-efi.aarch64-2021.05.21-Build9.106.raw.xz / kernel 5.3.18-59.5-default If I upgrade the kernel inside Build9.94 with 'zypper up', the same issue occurs. If I then choose the previous snapshot from GRUB the system can once again be booted with 5.3.18-57. Boot fails due to this, during initramfs/dracut: [ 6.227357] Internal error: synchronous external abort: 96000210 [#1] SMP [ 6.232443] mmc0: SDHCI controller on 2140000.esdhc [2140000.esdhc] using ADMA 64-bit [ 6.234152] Modules linked in: nvme nvme_core dwc3 sdhci_of_esdhc(+) sdhci_pltfm sdhci t10_pi mmc_core ulpi udc_core rtc_fsl_ftm_alarm i2c_imx gpio_keys sg scsi_mod [ 6.256675] Supported: Yes [ 6.259380] CPU: 6 PID: 7 Comm: kworker/u16:0 Not tainted 5.3.18-59.5-default #1 SLE15-SP3 [ 6.267643] Hardware name: traverse ten64/ten64, BIOS 2020.07-rc1-gb47b96d4 06/25/2021 [ 6.275581] Workqueue: nvme-reset-wq nvme_reset_work [nvme] [ 6.275587] pstate: a0000005 (NzCv daif -PAN -UAO) [ 6.275594] pc : nvme_reset_work+0x16c/0x12f8 [nvme] [ 6.275600] lr : nvme_reset_work+0x164/0x12f8 [nvme] [ OK 6.275601] sp : ffff8000100a3c80 m] Reached targe[ 6.275603] x29: ffff8000100a3c80 x28: ffff0732958af0c0 t Basic[ 6.275606] x27: ffff0732958af0c0 x26: ffff0732954412c0 System. [ 6.275609] x25: ffff073295441300 x24: ffff073295441710 [ 6.275611] x23: ffff0732958af000 x22: ffff073295441000 [ 6.275614] x21: ffffb9bd5bd89000 x20: ffff073295440f10 [ 6.275617] x19: ffff073295441000 x18: ffffffffffffffff [ 6.275620] x17: 0000000000000000 x16: ffffb9bd5a7a35a0 [ 6.275622] x15: ffffb9bd5bd89908 x14: 0000000000000040 [ 6.275625] x13: 0000000000000228 x12: 0000000000000000 [ 6.275628] x11: 0000000000000000 x10: 0000000000001a50 [ 6.275630] x9 : ffff8000100a3d10 x8 : 000000000000007d [ 6.275633] x7 : 0000000000000006 x6 : 0000000000010000 [ 6.275635] x5 : 0000000000000000 x4 : 0000000000000000 [ 6.275638] x3 : 0000000080000000 x2 : 0000000000000000 [ 6.275641] x1 : ffffffffffffffff x0 : ffff8000105b201c [ 6.275644] Call trace: [ 6.275651] nvme_reset_work+0x16c/0x12f8 [nvme] [ 6.275659] process_one_work+0x200/0x458 [ 6.275662] worker_thread+0x144/0x4f0 [ 6.275666] kthread+0x130/0x138 [ 6.275670] ret_from_fork+0x10/0x18 [ 6.275675] Code: aa1c03e0 940005af f9414ac0 91007000 (b9400000) [ 6.275678] ---[ end trace c33296e2e9bf08c4 ]--- I have confirmed this issue with multiple Ten64 units and different SSD models, so it does not appear to be hardware related -- You are receiving this mail because: You are the assignee for the bug.

1 22

[Bug 1192091] New: 5.14.14 assumes USB controller as dead
by bugzilla_noreply＠suse.com 28 Jan '22

28 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1192091 Bug ID: 1192091 Summary: 5.14.14 assumes USB controller as dead 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: stigpro(a)outlook.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Description : No USB(-C) at all when running `5.14.14` on a Lenovo Thinkpad X1 Yoga Gen 6 Steps to reproduce : 1. Boot `5.14.14` Excpected : Working USB like in `5.14.11` Result : Kernel assumes the USB contoller as dead System info : https://paste.opensuse.org/5d9b92f7 Log : https://paste.opensuse.org/f5553d43 Other info : The assumption of the USB controller being dead is at line 1005 (xhci error), it works with no issue on both `5.14.11` and `5.15.0-rc3-next-20210930-1.gd782f60-vanilla` -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1192181] New: brightness keys mute mic instead (HP Elitebook 840 G6)
by bugzilla_noreply＠suse.com 27 Jan '22

27 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1192181 Bug ID: 1192181 Summary: brightness keys mute mic instead (HP Elitebook 840 G6) 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: andreas_nordal_4(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a HP Elitebook 840 G6 laptop, both the backlight brightness keys (F3 and F4) toggle microphone mute state instead of doing their intended thing. The good thing is that other keys, such as mute, volume and the actual microphone mute key (F5, F6, F7, F8) work as intended. No messages appear in dmesg --follow or journalctl --follow when pressing these keys. In evtest, the brightness up and down keys appear as the same identical sequence, which is also a common prefix of the actual mic mute key: Common prefix: type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 type 1 (EV_KEY), code 190 (KEY_F20), value 1 -------------- SYN_REPORT ------------ type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 type 1 (EV_KEY), code 190 (KEY_F20), value 0 -------------- SYN_REPORT ------------ Actual mic mute key (unique suffix part): type 4 (EV_MSC), code 4 (MSC_SCAN), value 42 -------------- SYN_REPORT ------------ Kernel: Linux 5.14.6-1-default I found similar reports about these keys not working: 1. https://bugzilla.opensuse.org/show_bug.cgi?id=1105997 2. https://bugzilla.opensuse.org/show_bug.cgi?id=1160911 The first one was about not showing it correctly, but the last one says: Update: The issue is gone in the latest BIOS update issued by HP. Version: R70 Ver. 01.04.05 Release Date: 02/18/2020 That seems to be the same version as I have (according to lshw): *-firmware description: BIOS vendor: HP physical id: 1 version: R70 Ver. 01.04.05 date: 02/18/2020 size: 64KiB capacity: 32MiB capabilities: pci pcmcia upgrade shadowing cdboot bootselect edd int5printscreen int9keyboard int14serial int17printer acpi usb smartbattery biosbootspecification netboot uefi I haven't tried updating BIOS, but it doesn't look easy. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1180260] New: [RPi4] Switch to vc4 for display/sound (was rooted through efifb)
by bugzilla_noreply＠suse.com 21 Jan '22

21 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1180260 Bug ID: 1180260 Summary: [RPi4] Switch to vc4 for display/sound (was rooted through efifb) 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: nsaenzjulienne(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With v5.10 vc4, the driver enabling RPi's display controller, now supports RPi4. Let's switch the board's kernel configuration and firmware config to use this instead of efifb, which is extremely limited (no sound, no resolution changes). Among other things, some clocks have to be set-up as builtin, a fix is needed in u-boot so as to cater to DT changes involved in enabling vc4 and some overlays have to be selected in config.txt -- You are receiving this mail because: You are the assignee for the bug.

1 4

[kernel-bugs] [Bug 1179226] New: System hang related to power saving
by bugzilla_noreply＠suse.com 21 Jan '22

21 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1179226 Bug ID: 1179226 Summary: System hang related to power saving 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: jc(a)phocean.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # Issue : Screen and input devices would stop responding (black screen, no TTY), as soon as the computer goes into some low power mode. It can be triggered by locking the screen in Gnome (through gdm), and can also be reproduced in XFCE / LightDM by just leaving the computer for a while. # Impact : - black screen, no TTY access - unresponsive system (impossible to launch new processes, reboot, no way to switch init3 & init 5, etc.) - SSH/network access still available, existing process seem to run Moreover, no related log entry, no error (journalctl, dmesg...). # Notes : Hardware is very likely to be fine : - no issue with a Fedora LiveUSB ; - memtest tests passed. # Hardware : Asus PN40 Intel(R) Celeron(R) J4005 CPU @ 2.00GHz Intel Corporation UHD Graphics 605 (rev 03) # System Tumbleweed 20201123 I have no idea on how to debug it further. My huntch is that it is power saving related with Intel chipset. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[kernel-bugs] [Bug 1176646] New: Latest Kernel has i915 GPU Hang
by bugzilla_noreply＠suse.com 19 Jan '22

19 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1176646 Bug ID: 1176646 Summary: Latest Kernel has i915 GPU Hang Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: erecio(a)polywog.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 841741 --> http://bugzilla.opensuse.org/attachment.cgi?id=841741&action=edit dmesg output The following kernel works fine with my i915 GPU (5.6.14-1). However, the latest kernel 5.7+ (kernel-default-5.8.7-1.2.x86_64) causes my GPU to hang and it flickers and can never login. Switch back to 5.6 and it works fine. There have been other reports on Fedora with the same thing. https://bugzilla.redhat.com/show_bug.cgi?id=1843274 I have attached my dmesg output. I use the zap option to kill the xorg server and kdm comes up just fine most of the time. Trying to login is no good though. Also I can ctrl-alt-f2 to go on command line just fine. So it seems to be xorg with the new kernel. [ 163.236358] ------------[ cut here ]------------ [ 163.236365] WARNING: CPU: 0 PID: 0 at kernel/sched/core.c:4576 default_wake_function+0x16/0x30 [ 163.236366] Modules linked in: xt_MASQUERADE xt_addrtype iptable_nat nf_nat nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_state xt_LOG xt_multiport xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c af_packet iscsi_ibft iscsi_boot_sysfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables bpfilter rfkill tun binfmt_misc dmi_sysfs msr crypto_simd glue_helper dm_crypt intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio kvm_intel snd_hda_codec_hdmi snd_hda_intel kvm snd_intel_dspcfg irqbypass snd_hda_codec at24 mei_hdcp iTCO_wdt snd_hda_core intel_pmc_bxt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel iTCO_vendor_support cryptd snd_hwdep pcspkr snd_pcm snd_timer fan thermal snd e1000e soundcore i2c_i801 tiny_power_button i2c_smbus button mei_me lpc_ich mei hid_generic usbhid i915 i2c_algo_bit drm_kms_helper xhci_pci xhci_pci_renesas syscopyarea sysfillrect [ 163.236389] sysimgblt fb_sys_fops cec xhci_hcd rc_core ehci_pci ehci_hcd drm crc32c_intel usbcore video sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 163.236396] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.8.7-1-default #1 openSUSE Tumbleweed [ 163.236397] Hardware name: Gigabyte Technology Co., Ltd. B85M-Gaming 3/B85M-Gaming 3, BIOS F1 09/05/2014 [ 163.236399] RIP: 0010:default_wake_function+0x16/0x30 [ 163.236401] Code: e8 df 53 45 00 eb 99 0f 0b 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 f7 c2 fe ff ff ff 75 09 48 8b 7f 08 e9 da f9 ff ff <0f> 0b 48 8b 7f 08 e9 cf f9 ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 [ 163.236401] RSP: 0018:ffffa51080003eb8 EFLAGS: 00010086 [ 163.236402] RAX: ffffffffb0cf0e30 RBX: ffffa51080203db0 RCX: ffffa51080003ed0 [ 163.236403] RDX: 00000000fffffffb RSI: 0000000000000003 RDI: ffffa51080203db0 [ 163.236404] RBP: ffff980009218568 R08: 0000000000000000 R09: ffffffffc0321600 [ 163.236404] R10: ffff97ffdbd86280 R11: 0000000000000001 R12: 0000000000000046 [ 163.236405] R13: ffff980009218560 R14: ffffa51080003ed0 R15: ffffa51080003f60 [ 163.236406] FS: 0000000000000000(0000) GS:ffff980017200000(0000) knlGS:0000000000000000 [ 163.236406] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 163.236407] CR2: 00007f8ff0b07000 CR3: 000000003f80a001 CR4: 00000000000606f0 [ 163.236408] Call Trace: [ 163.236409] <IRQ> [ 163.236414] autoremove_wake_function+0xe/0x30 [ 163.236460] __i915_sw_fence_complete+0x160/0x1c0 [i915] [ 163.236483] dma_i915_sw_fence_wake_timer+0x2c/0x50 [i915] [ 163.236506] signal_irq_work+0x21c/0x310 [i915] [ 163.236510] irq_work_single+0x2c/0x40 [ 163.236511] irq_work_run_list+0x2d/0x40 [ 163.236512] irq_work_run+0x14/0x30 [ 163.236514] __sysvec_irq_work+0x2d/0xb0 [ 163.236517] asm_call_on_stack+0x12/0x20 [ 163.236518] </IRQ> [ 163.236520] sysvec_irq_work+0x6f/0x90 [ 163.236522] asm_sysvec_irq_work+0x12/0x20 [ 163.236524] RIP: 0010:cpuidle_enter_state+0xb6/0x3f0 [ 163.236525] Code: 10 ee c0 4e e8 eb 52 8d ff 49 89 c7 0f 1f 44 00 00 31 ff e8 cc 69 8d ff 80 7c 24 0f 00 0f 85 d4 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 e4 0f 88 e0 01 00 00 49 63 d4 4c 2b 7c 24 10 48 8d 04 52 48 [ 163.236526] RSP: 0018:ffffffffb2403e58 EFLAGS: 00000246 [ 163.236527] RAX: ffff98001722e680 RBX: ffff980017239600 RCX: 000000000000001f [ 163.236527] RDX: 0000000000000000 RSI: 000000002817b731 RDI: 0000000000000000 [ 163.236528] RBP: ffffffffb24f6260 R08: 0000002601a4c721 R09: 00000000000002ee [ 163.236528] R10: ffff98001722d444 R11: 00000000000005f4 R12: 0000000000000004 [ 163.236529] R13: 0000000000000004 R14: 0000000000000004 R15: 0000002601a4c721 [ 163.236531] ? cpuidle_enter_state+0xa4/0x3f0 [ 163.236533] cpuidle_enter+0x29/0x40 [ 163.236535] cpuidle_idle_call+0x13f/0x210 [ 163.236536] do_idle+0x73/0xd0 [ 163.236538] cpu_startup_entry+0x19/0x20 [ 163.236541] start_kernel+0x485/0x4a4 [ 163.236544] secondary_startup_64+0xb6/0xc0 [ 163.236546] ---[ end trace 5ea2057b70f281c8 ]--- [ 163.236548] ------------[ cut here ]------------ [ 574.899156] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in ksplashqml [3389] [ 574.899728] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 575.003261] i915 0000:00:02.0: [drm] ksplashqml[3389] context reset due to GPU hang [ 580.786335] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in ksplashqml [3389] [ 580.786882] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 580.890229] i915 0000:00:02.0: [drm] ksplashqml[3389] context reset due to GPU hang [ 583.858065] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc7b, in plasmashell [3461] [ 583.858294] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 583.961652] i915 0000:00:02.0: [drm] plasmashell[3461] context reset due to GPU hang [ 586.929534] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc7b, in kwin_x11 [3427] [ 586.929859] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 587.033116] i915 0000:00:02.0: [drm] kwin_x11[3427] context reset due to GPU hang -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1190286] New: Kernel 5.14 freezes in conjunction with Dell Docking Station
by bugzilla_noreply＠suse.com 19 Jan '22

19 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190286 Bug ID: 1190286 Summary: Kernel 5.14 freezes in conjunction with Dell Docking Station 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: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852364 --> http://bugzilla.opensuse.org/attachment.cgi?id=852364&action=edit Screenshot of frozen tty1 After the recent update to the 5.14 kernel, my Dell Latitude 7290 Laptop freezes on system startup after like 30 seconds. I could login via the display manager and even open a terminal and then the system froze. I could still move the mouse, but the terminal and everything else was stuck. I could switch to tty1 and tried to login as root there, but was stuck after the password prompt (See attached Screenshot). After about 5 minutes I had to forcefully terminate the system. I did a full system rollback to the previous snapshot (including Kernel 5.13), then installed all updates except the new kernel and rebooted. The system behaves nicely. Then I updated the Kernel as well, rebooted the Laptop and it was frozen again. The issue only happens when the Laptop is connected to the Dell Docking station. When disconnected from the Dock, it behaves nicely. When the system is stuck, disconnecting it from the docking station and waiting a bit also help to unfreeze the system. After reconnecting, the system remains responsive and does not freeze again (I'm writing on it right now). I also restarted the Docking Station but this had no effect at all. The Laptop was still freezing. -- You are receiving this mail because: You are the assignee for the bug.

1 29

[Bug 1191929] New: NVMe SSD slow since openSUSE-LEAP-15.3 (especially with cryptsetup / dm-crypt device)
by bugzilla_noreply＠suse.com 17 Jan '22

17 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191929 Bug ID: 1191929 Summary: NVMe SSD slow since openSUSE-LEAP-15.3 (especially with cryptsetup / dm-crypt device) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: duge(a)pre-sense.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I got a system with a NVMe SSD, whose performance with dm-crypt dropped from > 200 MB/s to below 2 MB/s from openSUSE-15.2 to openSUSE-15.3. Test procedure: dd oflag=direct bs="$((64 * 1024 * 1024))" count="$((16 * 1024 / 64))" if=dev/zero of=/dev/nvme0n1 dd oflag=sync bs="$((64 * 1024 * 1024))" count="$((16 * 1024 / 64))" if=dev/zero of=/dev/nvme0n1 cryptsetup --cipher "aes-cbc-essiv:sha256" create crypt_test /dev/nvme0n1 dd oflag=direct bs="$((64 * 1024 * 1024))" count="$((16 * 1024 / 64))" if=dev/zero of=/dev/mapper/crypt_test dd oflag=sync bs="$((64 * 1024 * 1024))" count="$((16 * 1024 / 64))" if=dev/zero of=/dev/mapper/crypt_test For oflag=direct openSUSE 15.2 and 15.3 both write with over 800 MB/s to /dev/nvme0n1 and over 300 MB/s to /dev/mapper/crypt_test. openSUSE-15.2 will write with over 600 MB/s to /dev/nvme0n1 and over 200 MB/s to /dev/mapper/crypt_test openSUSE-15.3 will write with 100 MB/s to /dev/nvme0n1 and less than 2 MB/s to /dev/mapper/crypt_test. Finally an "mkfs.ext4 /dev/mapper/crypt_test" takes more than 20 minutes and "iotop" shows even less I/O than 1 MB/s! Tumbleweed-x86_64-Snapshot20211019 (Linux-5.14.11) performs like openSUSE-15.2 or even better. localhost:~ # grep PRETTY /etc/os-release PRETTY_NAME="openSUSE Leap 15.3" localhost:~ # lsblk /dev/nvme0n1 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:0 0 238,5G 0 disk localhost:~ # lspci -v -d 1344:5410 04:00.0 Non-Volatile memory controller: Micron Technology Inc Device 5410 (rev 01) (prog-if 02 [NVM Express]) Subsystem: Micron Technology Inc Device 0100 Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0 Memory at a2100000 (64-bit, non-prefetchable) [size=16K] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [d0] MSI-X: Enable+ Count=32 Masked- Capabilities: [e0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [f8] Power Management version 3 Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?> Capabilities: [108] Latency Tolerance Reporting Capabilities: [110] L1 PM Substates Capabilities: [200] Advanced Error Reporting Capabilities: [300] #19 Kernel driver in use: nvme Kernel modules: nvme localhost:~ # smartctl -a /dev/nvme0n1 [...] === START OF INFORMATION SECTION === Model Number: Micron_2200_MTFDHBA256TCK [...] Firmware Version: P1MU003 PCI Vendor/Subsystem ID: 0x1344 IEEE OUI Identifier: 0x00a075 Controller ID: 0 Number of Namespaces: 1 Namespace 1 Size/Capacity: 256.060.514.304 [256 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 00a075 012cd592d5 [...] -- You are receiving this mail because: You are the assignee for the bug.

1 16

[kernel-bugs] [Bug 1173294] New: iwlwifi: TX on unused queue 5 WARNING: tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150
by bugzilla_noreply＠suse.com 17 Jan '22

17 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1173294 Bug ID: 1173294 Summary: iwlwifi: TX on unused queue 5 WARNING: tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ddiss(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This looks similar to: https://bugzilla.kernel.org/show_bug.cgi?id=204643 I hit the following WARNING while playing with network manager's new activate hotspot UI functionality and then disabling all radio (nmcli radio wifi off): [ 1157.323257] wlan1: deauthenticating from 34:31:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING) [ 1157.323301] ------------[ cut here ]------------ [ 1157.323302] TX on unused queue 5 [ 1157.323343] WARNING: CPU: 3 PID: 6784 at ../drivers/net/wireless/intel/iwlwifi/pcie/tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150 [iwlwifi] [ 1157.323344] Modules linked in: tun ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptablet [ 1157.323376] snd_hda_core dell_smm_hwmon fat kvm snd_hwdep dell_wmi dell_smbios irqbypass iwlwifi dcdbas joydev snd_pcm snd_timer sparse_keymap mei_me cfg80211 dell_wmi_d] [ 1157.323412] CPU: 3 PID: 6784 Comm: kworker/3:1 Not tainted 5.3.18-lp152.19-default #1 openSUSE Leap 15.2 (unreleased) [ 1157.323413] Hardware name: Dell Inc. Latitude E7450/0YGN55, BIOS A21 05/16/2019 [ 1157.323434] Workqueue: events cfg80211_rfkill_sync_work [cfg80211] [ 1157.323444] RIP: 0010:iwl_trans_pcie_tx+0xa1e/0x1150 [iwlwifi] [ 1157.323447] Code: 80 3d 2b 65 03 00 00 b8 ea ff ff ff 0f 85 25 f8 ff ff 89 ce 48 c7 c7 49 6e d8 c0 89 04 24 c6 05 0d 65 03 00 01 e8 42 94 33 e1 <0f> 0b 8b 04 24 e9 03 f8 c [ 1157.323448] RSP: 0018:ffff9f66404bf7f0 EFLAGS: 00010282 [ 1157.323449] RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000000006 [ 1157.323450] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff93915e399a10 [ 1157.323451] RBP: ffff939155e59e28 R08: 000000000000065e R09: 0000000000000001 [ 1157.323452] R10: 0000000000000005 R11: 0000000000000001 R12: ffff9390f1cc4b00 [ 1157.323453] R13: 0000000000000005 R14: 0000000000000037 R15: ffff9391566683e8 [ 1157.323454] FS: 0000000000000000(0000) GS:ffff93915e380000(0000) knlGS:0000000000000000 [ 1157.323455] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1157.323456] CR2: 00007f8e2af0a000 CR3: 00000002ba00a005 CR4: 00000000003606e0 [ 1157.323457] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 1157.323458] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 1157.323459] Call Trace: [ 1157.323473] ? iwl_mvm_set_tx_cmd+0x1a2/0x480 [iwlmvm] [ 1157.323483] ? iwl_mvm_get_tx_rate.isra.21+0x44/0xe0 [iwlmvm] [ 1157.323491] ? iwl_mvm_get_tx_ant+0x43/0x80 [iwlmvm] [ 1157.323499] ? iwl_mvm_set_tx_params+0x11f/0x4e0 [iwlmvm] [ 1157.323507] iwl_mvm_tx_mpdu+0x207/0x600 [iwlmvm] [ 1157.323516] iwl_mvm_tx_skb_sta+0x1ed/0x480 [iwlmvm] [ 1157.323524] iwl_mvm_tx_skb+0x17/0x40 [iwlmvm] [ 1157.323532] iwl_mvm_mac_itxq_xmit+0x7a/0xf0 [iwlmvm] [ 1157.323559] ieee80211_queue_skb+0x2da/0x420 [mac80211] [ 1157.323582] ieee80211_tx+0xd9/0x130 [mac80211] [ 1157.323604] __ieee80211_tx_skb_tid_band+0x58/0x70 [mac80211] [ 1157.323627] ieee80211_send_deauth_disassoc+0xfd/0x130 [mac80211] [ 1157.323649] ieee80211_set_disassoc+0x3a0/0x5e0 [mac80211] [ 1157.323679] ieee80211_mgd_deauth+0x113/0x230 [mac80211] [ 1157.323701] cfg80211_mlme_deauth+0xaf/0x1c0 [cfg80211] [ 1157.323720] cfg80211_mlme_down+0x7b/0x90 [cfg80211] [ 1157.323739] cfg80211_disconnect+0x11f/0x1d0 [cfg80211] [ 1157.323754] cfg80211_leave+0x26/0x40 [cfg80211] [ 1157.323767] cfg80211_netdev_notifier_call+0x258/0x5b0 [cfg80211] [ 1157.323774] ? iwl_mvm_set_tim+0x50/0x50 [iwlmvm] [ 1157.323794] ? __iterate_interfaces+0x78/0x110 [mac80211] [ 1157.323800] ? iwl_mvm_set_tim+0x50/0x50 [iwlmvm] [ 1157.323817] ? __iterate_interfaces+0x78/0x110 [mac80211] [ 1157.323831] ? ieee80211_iterate_active_interfaces_atomic+0xd/0x10 [mac80211] [ 1157.323838] ? iwl_mvm_recalc_multicast+0x45/0x70 [iwlmvm] [ 1157.323841] ? rtnl_is_locked+0x11/0x20 [ 1157.323843] ? inetdev_event+0x46/0x5c0 [ 1157.323850] ? iwl_mvm_configure_filter+0x61/0x80 [iwlmvm] [ 1157.323853] notifier_call_chain+0x47/0x70 [ 1157.323855] __dev_close_many+0x5f/0x110 [ 1157.323857] dev_close_many+0x7c/0x120 [ 1157.323859] dev_close.part.104+0x3e/0x70 [ 1157.323874] cfg80211_shutdown_all_interfaces+0x6d/0xc0 [cfg80211] [ 1157.323886] cfg80211_rfkill_sync_work+0x29/0x30 [cfg80211] [ 1157.323889] process_one_work+0x1f4/0x3e0 [ 1157.323892] worker_thread+0x2d/0x3e0 [ 1157.323894] ? process_one_work+0x3e0/0x3e0 [ 1157.323895] kthread+0x10d/0x130 [ 1157.323897] ? kthread_park+0xa0/0xa0 [ 1157.323899] ret_from_fork+0x35/0x40 [ 1157.323902] ---[ end trace 3217541a75ee82c3 ]--- I've not been able to reproduce it so far, but will update when/if I get a clear procedure. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1193142] New: usb mouse and usb keyboard not recognized by sddm
by bugzilla_noreply＠suse.com 13 Jan '22

13 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193142 Bug ID: 1193142 Summary: usb mouse and usb keyboard not recognized by sddm Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: PC OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jdd(a)dodin.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- since a week or so, I have no more working usb mouse and keyboard (separate, wired usb ones) on my Leap 15.3. ASUS laptop N550JK. The curious thing is that if I first boot an old 15.1 install, mouse and keyboard works, and if I just reboot on 15.3 (not power off), mouse and keyboard start working in 15.3. So on the morning I have to first start 15.1 (no need to login), and reboot on 15.3. odd. of course the two devices used to work since ages and still works after the double boot. Looks like some thing on the device is not correctly initialized (firmware?) * bug on last kernel, 5.3.18-59.34-default * no bug on kernel 5.3.18-58.10-default I didn't test all the kernels between these two -- You are receiving this mail because: You are the assignee for the bug.

1 10

[kernel-bugs] [Bug 1177499] New: prctl test fails on Tumbleweed
by bugzilla_noreply＠suse.com 07 Jan '22

07 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1177499 Bug ID: 1177499 Summary: prctl test fails on Tumbleweed 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: --- https://build.opensuse.org/package/live_build_log/home:michals/python-pytho… @require('get_no_new_privs') def test_no_new_privs(self): """Test the no_new_privs function""" self.assertEqual(prctl.get_no_new_privs(), 0) pid = os.fork() if pid: self.assertEqual(os.waitpid(pid, 0)[1], 0) else: prctl.set_no_new_privs(1) self.assertEqual(prctl.get_no_new_privs(), 1) if os.geteuid() != 0: sp = subprocess.Popen(['ping', '-c1', 'localhost'], stderr=subprocess.PIPE) sp.communicate() self.assertNotEqual(sp.returncode, 0) os._exit(0) It assumes that by default you cannot ping, and PR_SET_NO_NEW_PRIVS is inherited across fork. Has there been some change in the capabilities recently? -- You are receiving this mail because: You are the assignee for the bug.

1 9

[kernel-bugs] [Bug 1177459] New: general protection fault in native_queued_spin_lock_slowpath
by bugzilla_noreply＠suse.com 07 Jan '22

07 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1177459 Bug ID: 1177459 Summary: general protection fault in native_queued_spin_lock_slowpath Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jgross(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- System restarted over night, in /var/log/messages I could find: 2020-10-08T03:30:27.326958+02:00 localhost kernel: [36064.304226] general protection fault: 0000 [#1] SMP NOPTI 2020-10-08T03:30:27.326981+02:00 localhost kernel: [36064.304237] CPU: 1 PID: 2024 Comm: plasmashell Not tainted 5.3.18-lp152.44-default #1 openSUSE Leap 15.2 2020-10-08T03:30:27.327451+02:00 localhost kernel: [36064.304242] Hardware name: CSL-Computer GmbH & Co. KG A0000001/A320M-A PRO MAX (MS-7C52), BIOS 2.40 11/07/2019 2020-10-08T03:30:27.327454+02:00 localhost kernel: [36064.304253] RIP: 0010:native_queued_spin_lock_slowpath+0x188/0x1e0 2020-10-08T03:30:27.327456+02:00 localhost kernel: [36064.304259] Code: f3 90 48 8b 32 48 85 f6 74 f6 eb e8 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 80 d9 02 00 48 03 04 f5 80 79 3a b7 <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 74 f7 48 8b 32 2020-10-08T03:30:27.327456+02:00 localhost kernel: [36064.304266] RSP: 0018:ffffb881c0e07ac8 EFLAGS: 00010202 2020-10-08T03:30:27.327457+02:00 localhost kernel: [36064.304271] RAX: 0004374bff4d5340 RBX: ffff9e4a0524745c RCX: 0000000000080000 2020-10-08T03:30:27.327458+02:00 localhost kernel: [36064.304274] RDX: ffff9e4a1066d980 RSI: 0000000000003ffe RDI: ffff9e4a0524745c 2020-10-08T03:30:27.327458+02:00 localhost kernel: [36064.304278] RBP: ffff9e4a05247450 R08: 0000000000080000 R09: ffff9e482ba0f640 2020-10-08T03:30:27.327459+02:00 localhost kernel: [36064.304281] R10: 0000000000000013 R11: ffff9e49e5833138 R12: 0000000000000000 2020-10-08T03:30:27.327459+02:00 localhost kernel: [36064.304285] R13: ffffb881c0e07b94 R14: ffff9e49e5833100 R15: ffffb881c0e07b64 2020-10-08T03:30:27.327461+02:00 localhost kernel: [36064.304289] FS: 00007f1ceae4a900(0000) GS:ffff9e4a10640000(0000) knlGS:0000000000000000 2020-10-08T03:30:27.327463+02:00 localhost kernel: [36064.304293] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2020-10-08T03:30:27.327636+02:00 localhost kernel: [36064.304296] CR2: 00007fdea8d7d000 CR3: 00000003e0b40000 CR4: 00000000003406e0 2020-10-08T03:30:27.327652+02:00 localhost kernel: [36064.304300] Call Trace: 2020-10-08T03:30:27.327653+02:00 localhost kernel: [36064.304309] _raw_spin_lock+0x1b/0x20 2020-10-08T03:30:27.327653+02:00 localhost kernel: [36064.304315] inotify_poll+0x39/0x60 2020-10-08T03:30:27.327654+02:00 localhost kernel: [36064.304320] do_sys_poll+0x277/0x590 2020-10-08T03:30:27.327655+02:00 localhost kernel: [36064.304327] ? __wake_up_common+0x74/0x120 2020-10-08T03:30:27.327844+02:00 localhost kernel: [36064.304332] ? __wake_up_common_lock+0x87/0xc0 2020-10-08T03:30:27.327846+02:00 localhost kernel: [36064.304337] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327847+02:00 localhost kernel: [36064.304341] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327849+02:00 localhost kernel: [36064.304345] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327849+02:00 localhost kernel: [36064.304349] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327850+02:00 localhost kernel: [36064.304353] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327852+02:00 localhost kernel: [36064.304356] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327852+02:00 localhost kernel: [36064.304360] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327853+02:00 localhost kernel: [36064.304364] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327853+02:00 localhost kernel: [36064.304368] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327854+02:00 localhost kernel: [36064.304373] ? ktime_get_ts64+0x4c/0xf0 2020-10-08T03:30:27.328164+02:00 localhost kernel: [36064.304377] ? __x64_sys_poll+0x9e/0x130 2020-10-08T03:30:27.328165+02:00 localhost kernel: [36064.304380] __x64_sys_poll+0x9e/0x130 2020-10-08T03:30:27.328166+02:00 localhost kernel: [36064.304386] do_syscall_64+0x65/0x1f0 2020-10-08T03:30:27.328166+02:00 localhost kernel: [36064.304391] entry_SYSCALL_64_after_hwframe+0x44/0xa9 2020-10-08T03:30:27.328167+02:00 localhost kernel: [36064.304396] RIP: 0033:0x7f1ce427b6db 2020-10-08T03:30:27.328167+02:00 localhost kernel: [36064.304401] Code: 53 48 89 f5 48 89 fb 48 83 ec 18 48 89 54 24 08 e8 aa 7a 01 00 48 8b 54 24 08 41 89 c0 48 89 ee 48 89 df b8 07 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 08 e8 e1 7a 01 00 8b 44 2020-10-08T03:30:27.328168+02:00 localhost kernel: [36064.304407] RSP: 002b:00007ffc0b1ec680 EFLAGS: 00000293 ORIG_RAX: 0000000000000007 2020-10-08T03:30:27.328168+02:00 localhost kernel: [36064.304412] RAX: ffffffffffffffda RBX: 0000563bc7146440 RCX: 00007f1ce427b6db 2020-10-08T03:30:27.328170+02:00 localhost kernel: [36064.304415] RDX: 000000000000000f RSI: 0000000000000009 RDI: 0000563bc7146440 2020-10-08T03:30:27.328171+02:00 localhost kernel: [36064.304418] RBP: 0000000000000009 R08: 0000000000000000 R09: 0000563bc651f13c 2020-10-08T03:30:27.328172+02:00 localhost kernel: [36064.304422] R10: 0000563bc4efbc60 R11: 0000000000000293 R12: 0000563bc7146440 2020-10-08T03:30:27.328172+02:00 localhost kernel: [36064.304425] R13: 000000000000000f R14: 00007f1cde4ed6d0 R15: 000000000000000e 2020-10-08T03:30:27.328173+02:00 localhost kernel: [36064.304430] Modules linked in: fuse af_packet rfkill dmi_sysfs msr edac_mce_amd nls_iso8859_1 nls_cp437 snd_hda_codec_realtek ccp vfat fat snd_hda_codec_generic kvm ledtrig_audio snd_hda_codec_hdmi snd_hda_intel irqbypass crct10dif_pclmul snd_hda_codec crc32_pclmul ghash_clmulni_intel aesni_intel snd_hda_core aes_x86_64 snd_hwdep crypto_simd snd_pcm cryptd glue_helper snd_timer wmi_bmof joydev sp5100_tco snd pcspkr efi_pstore i2c_piix4 k10temp soundcore r8169 gpio_amdpt gpio_generic realtek button libphy btrfs libcrc32c xor hid_generic usbhid amdgpu raid6_pq amd_iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci crc32c_intel drm xhci_hcd usbcore sr_mod cdrom wmi video sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs 2020-10-08T03:30:27.328173+02:00 localhost kernel: [36064.304507] ---[ end trace bc466f6d04dd82ec ]--- 2020-10-08T03:30:27.328174+02:00 localhost kernel: [36064.304516] RIP: 0010:native_queued_spin_lock_slowpath+0x188/0x1e0 2020-10-08T03:30:27.328174+02:00 localhost kernel: [36064.304524] Code: f3 90 48 8b 32 48 85 f6 74 f6 eb e8 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 80 d9 02 00 48 03 04 f5 80 79 3a b7 <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 74 f7 48 8b 32 2020-10-08T03:30:27.328175+02:00 localhost kernel: [36064.304534] RSP: 0018:ffffb881c0e07ac8 EFLAGS: 00010202 2020-10-08T03:30:27.328175+02:00 localhost kernel: [36064.304540] RAX: 0004374bff4d5340 RBX: ffff9e4a0524745c RCX: 0000000000080000 2020-10-08T03:30:27.328177+02:00 localhost kernel: [36064.304546] RDX: ffff9e4a1066d980 RSI: 0000000000003ffe RDI: ffff9e4a0524745c 2020-10-08T03:30:27.3281782020-10-08T03:30:27.326958+02:00 localhost kernel: [36064.304226] general protection fault: 0000 [#1] SMP NOPTI 2020-10-08T03:30:27.326981+02:00 localhost kernel: [36064.304237] CPU: 1 PID: 2024 Comm: plasmashell Not tainted 5.3.18-lp152.44-default #1 openSUSE Leap 15.2 2020-10-08T03:30:27.327451+02:00 localhost kernel: [36064.304242] Hardware name: CSL-Computer GmbH & Co. KG A0000001/A320M-A PRO MAX (MS-7C52), BIOS 2.40 11/07/2019 2020-10-08T03:30:27.327454+02:00 localhost kernel: [36064.304253] RIP: 0010:native_queued_spin_lock_slowpath+0x188/0x1e0 2020-10-08T03:30:27.327456+02:00 localhost kernel: [36064.304259] Code: f3 90 48 8b 32 48 85 f6 74 f6 eb e8 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 80 d9 02 00 48 03 04 f5 80 79 3a b7 <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 74 f7 48 8b 32 2020-10-08T03:30:27.327456+02:00 localhost kernel: [36064.304266] RSP: 0018:ffffb881c0e07ac8 EFLAGS: 00010202 2020-10-08T03:30:27.327457+02:00 localhost kernel: [36064.304271] RAX: 0004374bff4d5340 RBX: ffff9e4a0524745c RCX: 0000000000080000 2020-10-08T03:30:27.327458+02:00 localhost kernel: [36064.304274] RDX: ffff9e4a1066d980 RSI: 0000000000003ffe RDI: ffff9e4a0524745c 2020-10-08T03:30:27.327458+02:00 localhost kernel: [36064.304278] RBP: ffff9e4a05247450 R08: 0000000000080000 R09: ffff9e482ba0f640 2020-10-08T03:30:27.327459+02:00 localhost kernel: [36064.304281] R10: 0000000000000013 R11: ffff9e49e5833138 R12: 0000000000000000 2020-10-08T03:30:27.327459+02:00 localhost kernel: [36064.304285] R13: ffffb881c0e07b94 R14: ffff9e49e5833100 R15: ffffb881c0e07b64 2020-10-08T03:30:27.327461+02:00 localhost kernel: [36064.304289] FS: 00007f1ceae4a900(0000) GS:ffff9e4a10640000(0000) knlGS:0000000000000000 2020-10-08T03:30:27.327463+02:00 localhost kernel: [36064.304293] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2020-10-08T03:30:27.327636+02:00 localhost kernel: [36064.304296] CR2: 00007fdea8d7d000 CR3: 00000003e0b40000 CR4: 00000000003406e0 2020-10-08T03:30:27.327652+02:00 localhost kernel: [36064.304300] Call Trace: 2020-10-08T03:30:27.327653+02:00 localhost kernel: [36064.304309] _raw_spin_lock+0x1b/0x20 2020-10-08T03:30:27.327653+02:00 localhost kernel: [36064.304315] inotify_poll+0x39/0x60 2020-10-08T03:30:27.327654+02:00 localhost kernel: [36064.304320] do_sys_poll+0x277/0x590 2020-10-08T03:30:27.327655+02:00 localhost kernel: [36064.304327] ? __wake_up_common+0x74/0x120 2020-10-08T03:30:27.327844+02:00 localhost kernel: [36064.304332] ? __wake_up_common_lock+0x87/0xc0 2020-10-08T03:30:27.327846+02:00 localhost kernel: [36064.304337] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327847+02:00 localhost kernel: [36064.304341] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327849+02:00 localhost kernel: [36064.304345] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327849+02:00 localhost kernel: [36064.304349] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327850+02:00 localhost kernel: [36064.304353] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327852+02:00 localhost kernel: [36064.304356] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327852+02:00 localhost kernel: [36064.304360] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327853+02:00 localhost kernel: [36064.304364] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327853+02:00 localhost kernel: [36064.304368] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.327854+02:00 localhost kernel: [36064.304373] ? ktime_get_ts64+0x4c/0xf0 2020-10-08T03:30:27.328164+02:00 localhost kernel: [36064.304377] ? __x64_sys_poll+0x9e/0x130 2020-10-08T03:30:27.328165+02:00 localhost kernel: [36064.304380] __x64_sys_poll+0x9e/0x130 2020-10-08T03:30:27.328166+02:00 localhost kernel: [36064.304386] do_syscall_64+0x65/0x1f0 2020-10-08T03:30:27.328166+02:00 localhost kernel: [36064.304391] entry_SYSCALL_64_after_hwframe+0x44/0xa9 2020-10-08T03:30:27.328167+02:00 localhost kernel: [36064.304396] RIP: 0033:0x7f1ce427b6db 2020-10-08T03:30:27.328167+02:00 localhost kernel: [36064.304401] Code: 53 48 89 f5 48 89 fb 48 83 ec 18 48 89 54 24 08 e8 aa 7a 01 00 48 8b 54 24 08 41 89 c0 48 89 ee 48 89 df b8 07 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 08 e8 e1 7a 01 00 8b 44 2020-10-08T03:30:27.328168+02:00 localhost kernel: [36064.304407] RSP: 002b:00007ffc0b1ec680 EFLAGS: 00000293 ORIG_RAX: 0000000000000007 2020-10-08T03:30:27.328168+02:00 localhost kernel: [36064.304412] RAX: ffffffffffffffda RBX: 0000563bc7146440 RCX: 00007f1ce427b6db 2020-10-08T03:30:27.328170+02:00 localhost kernel: [36064.304415] RDX: 000000000000000f RSI: 0000000000000009 RDI: 0000563bc7146440 2020-10-08T03:30:27.328171+02:00 localhost kernel: [36064.304418] RBP: 0000000000000009 R08: 0000000000000000 R09: 0000563bc651f13c 2020-10-08T03:30:27.328172+02:00 localhost kernel: [36064.304422] R10: 0000563bc4efbc60 R11: 0000000000000293 R12: 0000563bc7146440 2020-10-08T03:30:27.328172+02:00 localhost kernel: [36064.304425] R13: 000000000000000f R14: 00007f1cde4ed6d0 R15: 000000000000000e 2020-10-08T03:30:27.328173+02:00 localhost kernel: [36064.304430] Modules linked in: fuse af_packet rfkill dmi_sysfs msr edac_mce_amd nls_iso8859_1 nls_cp437 snd_hda_codec_realtek ccp vfat fat snd_hda_codec_generic kvm ledtrig_audio snd_hda_codec_hdmi snd_hda_intel irqbypass crct10dif_pclmul snd_hda_codec crc32_pclmul ghash_clmulni_intel aesni_intel snd_hda_core aes_x86_64 snd_hwdep crypto_simd snd_pcm cryptd glue_helper snd_timer wmi_bmof joydev sp5100_tco snd pcspkr efi_pstore i2c_piix4 k10temp soundcore r8169 gpio_amdpt gpio_generic realtek button libphy btrfs libcrc32c xor hid_generic usbhid amdgpu raid6_pq amd_iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci crc32c_intel drm xhci_hcd usbcore sr_mod cdrom wmi video sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs 2020-10-08T03:30:27.328173+02:00 localhost kernel: [36064.304507] ---[ end trace bc466f6d04dd82ec ]--- 2020-10-08T03:30:27.328174+02:00 localhost kernel: [36064.304516] RIP: 0010:native_queued_spin_lock_slowpath+0x188/0x1e0 2020-10-08T03:30:27.328174+02:00 localhost kernel: [36064.304524] Code: f3 90 48 8b 32 48 85 f6 74 f6 eb e8 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 80 d9 02 00 48 03 04 f5 80 79 3a b7 <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 74 f7 48 8b 32 2020-10-08T03:30:27.328175+02:00 localhost kernel: [36064.304534] RSP: 0018:ffffb881c0e07ac8 EFLAGS: 00010202 2020-10-08T03:30:27.328175+02:00 localhost kernel: [36064.304540] RAX: 0004374bff4d5340 RBX: ffff9e4a0524745c RCX: 0000000000080000 2020-10-08T03:30:27.328177+02:00 localhost kernel: [36064.304546] RDX: ffff9e4a1066d980 RSI: 0000000000003ffe RDI: ffff9e4a0524745c 2020-10-08T03:30:27.328178+02:00 localhost kernel: [36064.304553] RBP: ffff9e4a05247450 R08: 0000000000080000 R09: ffff9e482ba0f640 2020-10-08T03:30:27.328178+02:00 localhost kernel: [36064.304559] R10: 0000000000000013 R11: ffff9e49e5833138 R12: 0000000000000000 2020-10-08T03:30:27.328179+02:00 localhost kernel: [36064.304565] R13: ffffb881c0e07b94 R14: ffff9e49e5833100 R15: ffffb881c0e07b64 2020-10-08T03:30:27.328179+02:00 localhost kernel: [36064.304572] FS: 00007f1ceae4a900(0000) GS:ffff9e4a10640000(0000) knlGS:0000000000000000 2020-10-08T03:30:27.328180+02:00 localhost kernel: [36064.304578] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2020-10-08T03:30:27.328180+02:00 localhost kernel: [36064.304584] CR2: 00007fdea8d7d000 CR3: 00000003e0b40000 CR4: 00000000003406e0 2020-10-08T03:30:27.328318+02:00 localhost kernel: [36064.306057] BUG: unable to handle page fault for address: ffffb881c0e07da0 2020-10-08T03:30:27.328319+02:00 localhost kernel: [36064.306062] #PF: supervisor write access in kernel mode +02:00 localhost kernel: [36064.304553] RBP: ffff9e4a05247450 R08: 0000000000080000 R09: ffff9e482ba0f640 2020-10-08T03:30:27.328178+02:00 localhost kernel: [36064.304559] R10: 0000000000000013 R11: ffff9e49e5833138 R12: 0000000000000000 2020-10-08T03:30:27.328179+02:00 localhost kernel: [36064.304565] R13: ffffb881c0e07b94 R14: ffff9e49e5833100 R15: ffffb881c0e07b64 2020-10-08T03:30:27.328179+02:00 localhost kernel: [36064.304572] FS: 00007f1ceae4a900(0000) GS:ffff9e4a10640000(0000) knlGS:0000000000000000 2020-10-08T03:30:27.328180+02:00 localhost kernel: [36064.304578] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2020-10-08T03:30:27.328180+02:00 localhost kernel: [36064.304584] CR2: 00007fdea8d7d000 CR3: 00000003e0b40000 CR4: 00000000003406e0 2020-10-08T03:30:27.328318+02:00 localhost kernel: [36064.306057] BUG: unable to handle page fault for address: ffffb881c0e07da0 2020-10-08T03:30:27.328319+02:00 localhost kernel: [36064.306062] #PF: supervisor write access in kernel mode 2020-10-08T03:30:27.328319+02:00 localhost kernel: [36064.306065] #PF: error_code(0x0002) - not-present page 2020-10-08T03:30:27.328320+02:00 localhost kernel: [36064.306069] PGD 107d42067 P4D 107d42067 PUD 107d43067 PMD 22a67f067 PTE 0 2020-10-08T03:30:27.328320+02:00 localhost kernel: [36064.306075] Oops: 0002 [#2] SMP NOPTI 2020-10-08T03:30:27.328320+02:00 localhost kernel: [36064.306079] CPU: 1 PID: 9510 Comm: kscreenlocker_g Tainted: G D 5.3.18-lp152.44-default #1 openSUSE Leap 15.2 2020-10-08T03:30:27.328321+02:00 localhost kernel: [36064.306083] Hardware name: CSL-Computer GmbH & Co. KG A0000001/A320M-A PRO MAX (MS-7C52), BIOS 2.40 11/07/2019 2020-10-08T03:30:27.328322+02:00 localhost kernel: [36064.306089] RIP: 0010:remove_wait_queue+0x27/0x50 2020-10-08T03:30:27.328322+02:00 localhost kernel: [36064.306093] Code: 0f 1f 00 0f 1f 44 00 00 55 53 48 89 f3 48 89 fd e8 fe 2d 88 00 48 8b 53 20 48 8b 4b 18 48 be 00 01 00 00 00 00 ad de 48 89 ef <48> 89 51 08 48 89 0a 48 ba 22 01 00 00 00 00 ad de 48 89 73 18 48 2020-10-08T03:30:27.328323+02:00 localhost kernel: [36064.306098] RSP: 0018:ffffb881c824faa8 EFLAGS: 00010046 2020-10-08T03:30:27.328323+02:00 localhost kernel: [36064.306102] RAX: 0000000000000282 RBX: ffffb881c824fd80 RCX: ffffb881c0e07d98 2020-10-08T03:30:27.328324+02:00 localhost kernel: [36064.306106] RDX: ffff9e4707ec4658 RSI: dead000000000100 RDI: ffff9e4707ec4650 2020-10-08T03:30:27.328324+02:00 localhost kernel: [36064.306109] RBP: ffff9e4707ec4650 R08: 0000000000000001 R09: ffff9e4a0922a680 2020-10-08T03:30:27.328325+02:00 localhost kernel: [36064.306113] R10: 0000000000000018 R11: ffff9e4807ba8d38 R12: ffffb881c824fc40 2020-10-08T03:30:27.328325+02:00 localhost kernel: [36064.306116] R13: ffffb881c824fc70 R14: 0000000000000005 R15: 0000000000000000 2020-10-08T03:30:27.328326+02:00 localhost kernel: [36064.306120] FS: 00007fdef35ba180(0000) GS:ffff9e4a10640000(0000) knlGS:0000000000000000 2020-10-08T03:30:27.328326+02:00 localhost kernel: [36064.306124] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2020-10-08T03:30:27.328419+02:00 localhost kernel: [36064.306128] CR2: ffffb881c0e07da0 CR3: 0000000214a44000 CR4: 00000000003406e0 2020-10-08T03:30:27.328420+02:00 localhost kernel: [36064.306131] Call Trace: 2020-10-08T03:30:27.328420+02:00 localhost kernel: [36064.306136] poll_freewait+0x3d/0xa0 2020-10-08T03:30:27.328421+02:00 localhost kernel: [36064.306141] do_sys_poll+0x3f9/0x590 2020-10-08T03:30:27.328421+02:00 localhost kernel: [36064.306147] ? lookup_fast+0xc8/0x2d0 2020-10-08T03:30:27.328422+02:00 localhost kernel: [36064.306151] ? lookup_fast+0xc8/0x2d0 2020-10-08T03:30:27.328423+02:00 localhost kernel: [36064.306156] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.328424+02:00 localhost kernel: [36064.306160] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.328424+02:00 localhost kernel: [36064.306164] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.328425+02:00 localhost kernel: [36064.306168] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.328425+02:00 localhost kernel: [36064.306172] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.328425+02:00 localhost kernel: [36064.306175] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.328426+02:00 localhost kernel: [36064.306178] ? poll_select_finish+0x220/0x220 2020-10-08T03:30:27.328426+02:00 localhost kernel: [36064.306181] ? ktime_get_ts64+0x4c/0xf0 2020-10-08T03:30:27.328427+02:00 localhost kernel: [36064.306185] ? __x64_sys_poll+0x9e/0x130 2020-10-08T03:30:27.328427+02:00 localhost kernel: [36064.306188] __x64_sys_poll+0x9e/0x130 2020-10-08T03:30:27.328428+02:00 localhost kernel: [36064.306191] do_syscall_64+0x65/0x1f0 2020-10-08T03:30:27.328428+02:00 localhost kernel: [36064.306194] entry_SYSCALL_64_after_hwframe+0x44/0xa9 2020-10-08T03:30:27.328429+02:00 localhost kernel: [36064.306198] RIP: 0033:0x7fdeee9976db 2020-10-08T03:30:27.328600+02:00 localhost kernel: [36064.306202] Code: 53 48 89 f5 48 89 fb 48 83 ec 18 48 89 54 24 08 e8 aa 7a 01 00 48 8b 54 24 08 41 89 c0 48 89 ee 48 89 df b8 07 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 08 e8 e1 7a 01 00 8b 44 2020-10-08T03:30:27.328612+02:00 localhost kernel: [36064.306206] RSP: 002b:00007fffd505c8b0 EFLAGS: 00000293 ORIG_RAX: 0000000000000007 2020-10-08T03:30:27.328612+02:00 localhost kernel: [36064.306209] RAX: ffffffffffffffda RBX: 00005592ab440230 RCX: 00007fdeee9976db 2020-10-08T03:30:27.328613+02:00 localhost kernel: [36064.306212] RDX: 0000000000000005 RSI: 0000000000000007 RDI: 00005592ab440230 2020-10-08T03:30:27.328614+02:00 localhost kernel: [36064.306215] RBP: 0000000000000007 R08: 0000000000000000 R09: 00005592abe2eb90 2020-10-08T03:30:27.328614+02:00 localhost kernel: [36064.306217] R10: 00005592ab094720 R11: 0000000000000293 R12: 00005592ab440230 2020-10-08T03:30:27.328615+02:00 localhost kernel: [36064.306220] R13: 0000000000000005 R14: 00007fdeea02e6d0 R15: 0000000000000007 2020-10-08T03:30:27.328624+02:00 localhost kernel: [36064.306223] Modules linked in: fuse af_packet rfkill dmi_sysfs msr edac_mce_amd nls_iso8859_1 nls_cp437 snd_hda_codec_realtek ccp vfat fat snd_hda_codec_generic kvm ledtrig_audio snd_hda_codec_hdmi snd_hda_intel irqbypass crct10dif_pclmul snd_hda_codec crc32_pclmul ghash_clmulni_intel aesni_intel snd_hda_core aes_x86_64 snd_hwdep crypto_simd snd_pcm cryptd glue_helper snd_timer wmi_bmof joydev sp5100_tco snd pcspkr efi_pstore i2c_piix4 k10temp soundcore r8169 gpio_amdpt gpio_generic realtek button libphy btrfs libcrc32c xor hid_generic usbhid amdgpu raid6_pq amd_iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci crc32c_intel drm xhci_hcd usbcore sr_mod cdrom wmi video sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs 2020-10-08T03:30:27.328625+02:00 localhost kernel: [36064.306250] CR2: ffffb881c0e07da0 2020-10-08T03:30:27.328626+02:00 localhost kernel: [36064.306253] ---[ end trace bc466f6d04dd82ed ]--- 2020-10-08T03:30:27.328626+02:00 localhost kernel: [36064.306257] RIP: 0010:native_queued_spin_lock_slowpath+0x188/0x1e0 2020-10-08T03:30:27.328627+02:00 localhost kernel: [36064.306260] Code: f3 90 48 8b 32 48 85 f6 74 f6 eb e8 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 80 d9 02 00 48 03 04 f5 80 79 3a b7 <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 74 f7 48 8b 32 2020-10-08T03:30:27.328627+02:00 localhost kernel: [36064.306264] RSP: 0018:ffffb881c0e07ac8 EFLAGS: 00010202 2020-10-08T03:30:27.328629+02:00 localhost kernel: [36064.306267] RAX: 0004374bff4d5340 RBX: ffff9e4a0524745c RCX: 0000000000080000 2020-10-08T03:30:27.328630+02:00 localhost kernel: [36064.306270] RDX: ffff9e4a1066d980 RSI: 0000000000003ffe RDI: ffff9e4a0524745c 2020-10-08T03:30:27.328630+02:00 localhost kernel: [36064.306273] RBP: ffff9e4a05247450 R08: 0000000000080000 R09: ffff9e482ba0f640 2020-10-08T03:30:27.328631+02:00 localhost kernel: [36064.306276] R10: 0000000000000013 R11: ffff9e49e5833138 R12: 0000000000000000 2020-10-08T03:30:27.328631+02:00 localhost kernel: [36064.306279] R13: ffffb881c0e07b94 R14: ffff9e49e5833100 R15: ffffb881c0e07b64 2020-10-08T03:30:27.328632+02:00 localhost kernel: [36064.306282] FS: 00007fdef35ba180(0000) GS:ffff9e4a10640000(0000) knlGS:0000000000000000 2020-10-08T03:30:27.328632+02:00 localhost kernel: [36064.306285] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2020-10-08T03:30:27.328634+02:00 localhost kernel: [36064.306288] CR2: ffffb881c0e07da0 CR3: 0000000214a44000 CR4: 00000000003406e0 The system is an AMD machine (Ryzen). I should note that I'm seeing random user program segfaults now and then, not sure this is related in some way: # grep segfault /var/log/messages 2020-10-06T21:29:05.733073+02:00 localhost kernel: [210750.479119] Web Content[32336]: segfault at 74b83f90 ip 00007fb880daae40 sp 00007ffef2b45810 error 4 in libpthread-2.26.so[7fb880da0000+19000] 2020-10-07T08:11:39.210216+02:00 localhost kernel: [ 3509.555322] Web Content[2611]: segfault at c9e02ee8 ip 00007f7d728d118d sp 00007fffbd935c08 error 6 in libc-2.26.so[7f7d727c8000+1b1000] 2020-10-07T17:27:45.558216+02:00 localhost kernel: [36875.901410] zypper[9002]: segfault at 18 ip 00007f2519a3a912 sp 00007fffa641a308 error 4 in libzypp.so.1722.2.1[7f25196db000+598000] 2020-10-07T20:00:08.030810+02:00 localhost kernel: [ 9068.730779] Web Content[6224]: segfault at 11f2cd70db86 ip 000011f2cd70db86 sp 00007fffb65b0aa8 error 14 2020-10-08T01:54:38.826835+02:00 localhost kernel: [30320.853834] kscreenlocker_g[6899]: segfault at 4 ip 00007f5a07823625 sp 00007ffe7ebde8e0 error 6 in libQt5Quick.so.5.12.7[7f5a0762b000+48e000] -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1193124] New: tumbleweed release 20211124 with kernel 5.15.3 bluetooth fail
by bugzilla_noreply＠suse.com 20 Dec '21

20 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 Bug ID: 1193124 Summary: tumbleweed release 20211124 with kernel 5.15.3 bluetooth fail 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: tech(a)reachthetribes.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- My pc is an ASUS ZenBook Flip S UX371EA. This does not seem to be a duplicate After tumbleweed release 20211124 with kernel update to 5.15.3, bluetooth fails to operate. It no longer shows up in the system tray, the bluetooth service under systemctl doesn't start, and the btusb module is not loaded to the new kernel. When it is manually added to the kernel and the bluetooth service is started, the bluetooth icon comes back to the system tray, but bluetooth will not pick up any devices. Here are the command results: on the 5.15 kernel > sudo rfkill ID TYPE DEVICE SOFT HARD 0 wlan asus-wlan unblocked unblocked 1 bluetooth asus-bluetooth unblocked unblocked 2 wlan phy0 unblocked unblocked When this command is run in the 5.14 kernel, there is another line that comes out that is missing here: 3 bluetooth hci0 unblocked unblocked on the 5.15 kernel, lsusb doesn't read anything with bluetooth > lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 13d3:56eb IMC Networks USB2.0 HD UVC WebCam Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver 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 When this is run on the 5.14 kernel, the bluetooth adaptor shows up: Bus 003 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth For journalctl on the 5.15 kernel: > journalctl -b | egrep -i bluetooth Nov 26 20:27:44 asustribetrek NetworkManager[780]: <info> [1637980064.3080] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.32.12/libnm-device-plugin-bluetooth.so) Nov 26 20:27:48 asustribetrek systemd[1]: Condition check resulted in Bluetooth service being skipped. Nov 26 20:27:50 asustribetrek kded5[1660]: bluedevil: Bluetooth operational changed false Nov 26 20:28:14 asustribetrek systemd[1]: Condition check resulted in Bluetooth service being skipped. Nov 26 20:31:29 asustribetrek systemd[1]: Condition check resulted in Bluetooth service being skipped. Nov 26 20:31:30 asustribetrek kded5[5664]: bluedevil: Bluetooth operational changed false journalctl on the 5.14 kernel had significantly more results, as expected: > journalctl -b | egrep -i bluetooth Nov 26 20:35:16 asustribetrek NetworkManager[790]: <info> [1637980516.4366] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.32.12/libnm-device-plugin-bluetooth.so) Nov 26 20:35:17 asustribetrek kernel: Bluetooth: Core ver 2.22 Nov 26 20:35:17 asustribetrek kernel: NET: Registered PF_BLUETOOTH protocol family Nov 26 20:35:17 asustribetrek kernel: Bluetooth: HCI device and connection manager initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: HCI socket layer initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: L2CAP socket layer initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: SCO socket layer initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018 Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Device revision is 2 Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Secure boot is enabled Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: OTP lock is enabled Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: API lock is enabled Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Debug lock is disabled Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi Nov 26 20:35:17 asustribetrek systemd[1]: Starting Bluetooth service... Nov 26 20:35:17 asustribetrek bluetoothd[1432]: Bluetooth daemon 5.62 Nov 26 20:35:17 asustribetrek systemd[1]: Started Bluetooth service. Nov 26 20:35:17 asustribetrek systemd[1]: Reached target Bluetooth Support. Nov 26 20:35:17 asustribetrek bluetoothd[1432]: Starting SDP server Nov 26 20:35:17 asustribetrek bluetoothd[1432]: Bluetooth management interface 1.21 initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Nov 26 20:35:17 asustribetrek kernel: Bluetooth: BNEP filters: protocol multicast Nov 26 20:35:17 asustribetrek kernel: Bluetooth: BNEP socket layer initialized Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Waiting for firmware download to complete Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Firmware loaded in 1694554 usecs Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Waiting for device to boot Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Device booted in 14663 usecs Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Firmware revision 0.4 build 5 week 39 2021 Nov 26 20:35:19 asustribetrek bluetoothd[1432]: Admin Policy Set interface registered Nov 26 20:35:19 asustribetrek bluetoothd[1432]: Admin Policy Status interface registered Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Player registered: sender=:1.33 path=/media_player0 Nov 26 20:35:22 asustribetrek kernel: Bluetooth: RFCOMM TTY layer initialized Nov 26 20:35:22 asustribetrek kernel: Bluetooth: RFCOMM socket layer initialized Nov 26 20:35:22 asustribetrek kernel: Bluetooth: RFCOMM ver 1.11 Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/ldac Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/aptx_hd Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_hd Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/aptx Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aac Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/sbc Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/sbc Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/sbc_xq Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/sbc_xq Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream_duplex Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_1 Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_0 Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 Nov 26 20:35:24 asustribetrek kded5[1784]: bluedevil: Bluetooth operational changed true For dmesg on the 5.15 kernel, the results were empty: > dmesg | grep -i bluetooth For dmesg on the 5.14 kernel, there were lots of results as expected: > dmesg | grep -i bluetooth [ 5.769571] Bluetooth: Core ver 2.22 [ 5.769616] NET: Registered PF_BLUETOOTH protocol family [ 5.769618] Bluetooth: HCI device and connection manager initialized [ 5.769622] Bluetooth: HCI socket layer initialized [ 5.769628] Bluetooth: L2CAP socket layer initialized [ 5.769633] Bluetooth: SCO socket layer initialized [ 5.915512] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018 [ 5.916500] Bluetooth: hci0: Device revision is 2 [ 5.916511] Bluetooth: hci0: Secure boot is enabled [ 5.916513] Bluetooth: hci0: OTP lock is enabled [ 5.916514] Bluetooth: hci0: API lock is enabled [ 5.916515] Bluetooth: hci0: Debug lock is disabled [ 5.916516] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 5.963172] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi [ 6.003424] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 6.003428] Bluetooth: BNEP filters: protocol multicast [ 6.003431] Bluetooth: BNEP socket layer initialized [ 7.696847] Bluetooth: hci0: Waiting for firmware download to complete [ 7.698400] Bluetooth: hci0: Firmware loaded in 1694554 usecs [ 7.698487] Bluetooth: hci0: Waiting for device to boot [ 7.713473] Bluetooth: hci0: Device booted in 14663 usecs [ 7.714204] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc [ 7.716402] Bluetooth: hci0: Applying Intel DDC parameters completed [ 7.719474] Bluetooth: hci0: Firmware revision 0.4 build 5 week 39 2021 [ 11.170866] Bluetooth: RFCOMM TTY layer initialized [ 11.170873] Bluetooth: RFCOMM socket layer initialized [ 11.170877] Bluetooth: RFCOMM ver 1.11 -- You are receiving this mail because: You are the assignee for the bug.

1 60

[Bug 1193039] New: Alder Lake system fails to shutdown
by bugzilla_noreply＠suse.com 17 Dec '21

17 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193039 Bug ID: 1193039 Summary: Alder Lake system fails to shutdown 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: darrenleatherbarrow(a)hotmail.co.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 853999 --> http://bugzilla.opensuse.org/attachment.cgi?id=853999&action=edit Kernel To note I am using an Nvidia GPU. When shutting down the system hangs consistently and I have to force power off via holding power button. Systemd gets to this point and attached kernel log below: Nov 24 09:42:04 alderlake systemd[1712]: Closed D-Bus User Message Bus Socket. Nov 24 09:42:04 alderlake systemd[1712]: Closed Sound System. Nov 24 09:42:04 alderlake systemd[1712]: Stopped Create User's Volatile Files and Directories. Nov 24 09:42:04 alderlake systemd[1712]: Removed slice User Application Slice. Nov 24 09:42:04 alderlake systemd[1712]: app.slice: Consumed 2.318s CPU time. Nov 24 09:42:04 alderlake systemd[1712]: Reached target Shutdown. Nov 24 09:42:04 alderlake systemd[1712]: Finished Exit the Session. Nov 24 09:42:04 alderlake systemd[1712]: Reached target Exit the Session. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1193255] New: Regression: Logitech Brio webcam partially broken with 5.15.3+
by bugzilla_noreply＠suse.com 16 Dec '21

16 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193255 Bug ID: 1193255 Summary: Regression: Logitech Brio webcam partially broken with 5.15.3+ 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: rombert(a)apache.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With 5.15.3 and 5.15.5 the output of v4l2-ctl --list-devices does not list devices by name, only 'Video Capture X'. Also, programs like OBS studio and guvcview fail to set resolutions over 640x480 ( camera can record 4k@30fps). I have gathered the output of journalctl -b and v4l2-clt --list-devices with kernel versions 5.15.2 and 5.15.5 from boot and up til displaying the device with guvcview. I may have tried devices in different order with guvcview between the two invocations since it only shows the device name and multiple ones are not really disambiguated. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1193263] New: New journalctl errors after installing kernel-default 5.15.5-1.1
by bugzilla_noreply＠suse.com 08 Dec '21

08 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193263 Bug ID: 1193263 Summary: New journalctl errors after installing kernel-default 5.15.5-1.1 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: genes1122(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Rebooting after installing kernel-default 5.15.5-1.1 produces the following new messages from journalctl: > jctl-n -b -2 -p err -- Journal begins at Mon 2021-09-20 13:51:59 PDT, ends at Tue 2021-11-30 14:57:53 PST. -- Nov 30 14:43:14 Mobile-PC kernel: sd 0:0:0:0: [sda] Asking for cache data failed Nov 30 14:43:14 Mobile-PC kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Nov 30 14:43:20 Mobile-PC systemd-backlight[1570]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device Nov 30 14:43:21 Mobile-PC systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0. Nov 30 14:43:28 Mobile-PC lightdm[3574]: gkr-pam: unable to locate daemon control file Nov 30 14:43:29 Mobile-PC pipewire[5169]: jack-device 0x55feedbce848: can't open client: Input/output error Rebooting in the previous kernel, 5.15.3-1, removes the new errors: > jctl-n -b -p err -- Journal begins at Mon 2021-09-20 13:51:59 PDT, ends at Tue 2021-11-30 15:03:09 PST. -- Nov 30 14:47:43 Mobile-PC lightdm[1932]: gkr-pam: unable to locate daemon control file Nov 30 14:47:45 Mobile-PC pipewire[2112]: jack-device 0x558f82c95a68: can't open client: Input/output error Those last two errors have been around for quite a while. Gene -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 1192969] New: NVMe: kernel NULL pointer address 0000000000000040
by bugzilla_noreply＠suse.com 08 Dec '21

08 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192969 Bug ID: 1192969 Summary: NVMe: kernel NULL pointer address 0000000000000040 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: SLES 15 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: richard_golasky(a)dell.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 853939 --> http://bugzilla.opensuse.org/attachment.cgi?id=853939&action=edit message log Current code base: - 5.3.18-59.34-default - nvme version 1.13 - Latest updates installed on the SLES15-SP3 server. - in-kernel Native NVMe multipathing. - Qlogic QL41262 dualport HBA. Problem: NVMe connection to a target NVMe subsystem works fine. However, you will see a kernel panic noted in the attached message file and the attached screenshot. Both refer to nvme multipathing. [32m[ 1401.217246] [0m[33mRIP[0m[1m: 0010:nvme_mpath_revalidate_paths+0x27/0xb0 [nvme_core][0m [32m[ 1401.217250] [0m[33mCode[0m[1m: 44 00 00 0f 1f 44 00 00 55 53 48 8b 6f 50 48 8b 55 00 48 8b 85 10 c5 00 00 48 39 d5 48 8b 48 40 74 20 48 8d 42 d0 48 8b 50 20 <48> 3b 4a 40 74 05 f0 80 60 78 ef 48 8b 50 30 48 39 d5 48 8d 42 d0[0m [32m[ 1401.217254] [0m[33mRSP[0m[1m: 0018:ffffbd9d46533cc0 EFLAGS: 00010283[0m [32m[ 1401.217256] [0m[33mRAX[0m[1m: ffff94b637b96600 RBX: ffff94b66cf40a00 RCX: 000000000aa00000[0m [32m[ 1401.217258] [0m[33mRDX[0m[1m: 0000000000000000 RSI: 0000000000000001 RDI: ffff94b66cf40a00[0m [32m[ 1401.217259] [0m[33mRBP[0m[1m: ffff94b616710000 R08: 0000000800000000 R09: 00000008ffffffff[0m [32m[ 1401.217261] [0m[33mR10[0m[1m: 0000000000009b9a R11: 0000000000000230 R12: 0000000000000000[0m [32m[ 1401.217263] [0m[33mR13[0m[1m: ffff94b616710000 R14: ffffbd9d46533da7 R15: ffff94b66cf40a00[0m [32m[ 1401.217265] [0m[33mFS[0m[1m: 0000000000000000(0000) GS:ffff94b66f880000(0000) knlGS:0000000000000000[0m [32m[ 1401.217267] [0m[33mCS[0m[1m: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033[0m [32m[ 1401.217269] [0m[33mCR2[0m[1m: 0000000000000040 CR3: 00000003e0c0a005 CR4: 00000000001706e0[0m -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1191973] New: Battery fast discharging on fresh kernel in tumbleweed
by bugzilla_noreply＠suse.com 08 Dec '21

08 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1191973 Bug ID: 1191973 Summary: Battery fast discharging on fresh kernel in tumbleweed 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: virex(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I noticed for a long time that the battery on a laptop is consumed faster under openSUSE Tumbleweed with fresh kernel. Compared on another laptop with both installed Windows 10 and openSUSE Tumbleweed. Photos are atached. Under Windows 10 battery for about 17h, under openSUSE Tumbleweed battery work about 6h. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1191804] New: kernel cannot be updated if Secure Boot is disabled
by bugzilla_noreply＠suse.com 07 Dec '21

07 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1191804 Bug ID: 1191804 Summary: kernel cannot be updated if Secure Boot is disabled 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: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- (3/3) Installing: kernel-default-5.14.11-1.2.x86_64 [...........error] Installation of kernel-default-5.14.11-1.2.x86_64 failed: Error: Subprocess failed. Error: RPM failed: SecureBoot disabled Platform is in Setup Mode Abort, retry, ignore? [a/r/i] (a): a Warning: %posttrans scripts skipped while aborting: kernel-default-5.14.11-1.2.x86_64.rpm -- You are receiving this mail because: You are the assignee for the bug.

1 30

[Bug 1191480] New: Kernel:stable kernel 5.14.10-2.1.g2878fd1 cannot boot due to "bad shim signature"
by bugzilla_noreply＠suse.com 07 Dec '21

07 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1191480 Bug ID: 1191480 Summary: Kernel:stable kernel 5.14.10-2.1.g2878fd1 cannot boot due to "bad shim signature" 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: yan.huang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On openSUSE Tumbleweed 20211005 (with shim 15.4-4.2 and Secure Boot enabled), booting the newest Kernel:stable kernel 5.14.10-2.1.g2878fd1 leads to: > Loading Linux kernel-default-5.14.10-2.g2878fd1-default ... > error: ../../grub-core/kern/efi/sb.c:150:bad shim signature. > Loading initial ramdisk ... > error: ../../grub-core/loader/i386/efi/linux.c.98:you need to load the kernel first. > > Press any key to continue..._ The previous Kernel:stable kernel 5.14.9-2.1.gd0ace7f did not have this issue. The issue seems to be similar to the previous boo#1188142 (Kernel 5.13.1 does not boot due to bad shim signature). -- You are receiving this mail because: You are the assignee for the bug.

1 25

[Bug 1189879] New: Missing kernel config in /boot
by bugzilla_noreply＠suse.com 07 Dec '21

07 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1189879 Bug ID: 1189879 Summary: Missing kernel config in /boot 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: --- bsc#1184804 moved kernel config out of /boot into /usr/lib/modules/. But unlike vmlinuz and initrd there is missing symlink in /boot. Is it really a wanted change? $ ls -l /boot/ -rw-r--r-- 1 root root 0 Mar 13 2017 backup_mbr -rw-r--r-- 1 root root 1725 Jul 28 19:25 boot.readme drwxr-xr-x 6 root root 4096 Aug 25 11:18 grub2 lrwxrwxrwx 1 root root 34 Aug 25 10:57 initrd -> initrd-5.14.0-rc7-3.gdbb9dbc-debug -rw------- 1 root root 11202252 May 24 2019 initrd-5.0.7 -rw------- 1 root root 22664676 Aug 25 11:02 initrd-5.14.0-rc7-3.gdbb9dbc-debug -rw------- 1 root root 22652804 Aug 25 11:03 initrd-5.14.0-rc7-3.gdbb9dbc-default -rw------- 1 root root 13074280 Jul 4 2019 initrd-5.2.0-rc1-2.gb225e5a-default+ -rw------- 1 root root 19355748 Jul 4 2019 initrd-5.2.0-rc1-2.gb225e5a-default+-kdump lrwxrwxrwx 1 root root 58 Aug 25 10:57 sysctl.conf-5.14.0-rc7-3.gdbb9dbc-debug -> ../usr/lib/modules/5.14.0-rc7-3.gdbb9dbc-debug/sysctl.conf lrwxrwxrwx 1 root root 60 Aug 25 10:56 sysctl.conf-5.14.0-rc7-3.gdbb9dbc-default -> ../usr/lib/modules/5.14.0-rc7-3.gdbb9dbc-default/sysctl.conf lrwxrwxrwx 1 root root 57 Aug 25 10:57 System.map-5.14.0-rc7-3.gdbb9dbc-debug -> ../usr/lib/modules/5.14.0-rc7-3.gdbb9dbc-debug/System.map lrwxrwxrwx 1 root root 59 Aug 25 10:56 System.map-5.14.0-rc7-3.gdbb9dbc-default -> ../usr/lib/modules/5.14.0-rc7-3.gdbb9dbc-default/System.map lrwxrwxrwx 1 root root 35 Aug 25 10:57 vmlinuz -> vmlinuz-5.14.0-rc7-3.gdbb9dbc-debug lrwxrwxrwx 1 root root 54 Aug 25 10:57 vmlinuz-5.14.0-rc7-3.gdbb9dbc-debug -> ../usr/lib/modules/5.14.0-rc7-3.gdbb9dbc-debug/vmlinuz lrwxrwxrwx 1 root root 56 Aug 25 10:56 vmlinuz-5.14.0-rc7-3.gdbb9dbc-default -> ../usr/lib/modules/5.14.0-rc7-3.gdbb9dbc-default/vmlinuz If yes, some users can be surprised. Also rpm package claims to have config in /boot but it's not there: $ rpm -ql kernel-default-5.14~rc7-3.1.gdbb9dbc.x86_64 |grep /boot/config /boot/config-5.14.0-rc7-3.gdbb9dbc-default ls -la /boot/config-5.14.0-rc7-3.gdbb9dbc-default ls: cannot access '/boot/config-5.14.0-rc7-3.gdbb9dbc-default': No such file or directory According to openQA it was broken somewhere between 5.13.12-1.2 999e6048a4cc6accd2653c9dccaaaff2f4ae8f86 (good) and 5.13.12-2.1 33df9c651d0aa37cce1275bd9528ea5cb9196022 (bad). It looks to me that 33df9c651d0aa37cce1275bd9528ea5cb9196022 Revert "Revert "UsrMerge the kernel (boo#1184804)"" broke it. -- You are receiving this mail because: You are the assignee for the bug.

1 34

[Bug 1193189] New: Bogus rpmlint.log differences for kernel-syms rebuilds
by bugzilla_noreply＠suse.com 07 Dec '21

07 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193189 Bug ID: 1193189 Summary: Bogus rpmlint.log differences for kernel-syms rebuilds Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: mliska(a)suse.cz Reporter: schwab(a)linux-m68k.org QA Contact: qa-bugs(a)suse.de CC: kernel-bugs(a)opensuse.org Found By: --- Blocker: --- When kernel-syms is rebuilt it always results in differing contents of rpmlint.log. It looks like cycling between two states: comparing /.build.oldpackages/rpmlint.log and /home/abuild/rpmbuild/OTHER/rpmlint.log rpmlint.log files differ: --- /tmp/tmp.NnlgYU74Sb 2021-11-29 17:25:44.640000000 +0000 +++ /tmp/tmp.JLKflRhMvy 2021-11-29 17:25:44.640000000 +0000 @@ -31,17 +31,17 @@ itself. kernel-syms.aarch64: E: devel-dependency kernel-64kb-devel kernel-syms.aarch64: E: no-binary -kernel-syms.aarch64: E: unused-rpmlintrc-filter "dangling-symlink .*/lib/modules/[1-9].*/source" -kernel-syms.aarch64: E: unused-rpmlintrc-filter "hidden-file-or-dir /boot/\..*\.hmac" -kernel-syms.aarch64: E: unused-rpmlintrc-filter "hidden-file-or-dir /usr/src/linux-.*-obj/.*/.config" -kernel-syms.aarch64: E: unused-rpmlintrc-filter "hidden-file-or-dir /usr/src/linux-.*-obj/.*/.kernel-binary.spec.buildenv" -kernel-syms.aarch64: E: unused-rpmlintrc-filter "missing-PT_GNU_STACK-section .*/lib/modules/[1-9].*/vdso/.*" -kernel-syms.aarch64: E: unused-rpmlintrc-filter "shared-lib-without-dependency-information .*/lib/modules/[1-9].*/vdso/.*" -kernel-syms.aarch64: E: unused-rpmlintrc-filter "suse-policy-kmp-missing-supplements" -kernel-syms.aarch64: E: unused-rpmlintrc-filter "zero-length /usr/src/linux-.*-obj/.*/include/config.*h" -kernel-syms.aarch64: E: unused-rpmlintrc-filter "zero-length /usr/src/linux-.*-obj/.*/include/config/.*" kernel-syms.aarch64: E: useless-provides kernel-syms kernel-syms.spec: W: no-%build-section +kernel-syms.src: E: unused-rpmlintrc-filter "dangling-symlink .*/lib/modules/[1-9].*/source" +kernel-syms.src: E: unused-rpmlintrc-filter "hidden-file-or-dir /boot/\..*\.hmac" +kernel-syms.src: E: unused-rpmlintrc-filter "hidden-file-or-dir /usr/src/linux-.*-obj/.*/.config" This difference forces the rebuild of all other kernel packages due to rebuild counter sync. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1192740] New: Upgrade of broadcom-wl fails with "line 1: /usr/lib/module-init-tools/kernel-scriptlets/kmp-pre: No such file or directory"
by bugzilla_noreply＠suse.com 07 Dec '21

07 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192740 Bug ID: 1192740 Summary: Upgrade of broadcom-wl fails with "line 1: /usr/lib/module-init-tools/kernel-scriptlets/kmp-pre: No such file or directory" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation A `zypper dup` fails on openSUSE Leap 15.3 upgraded from openSUSE Leap 15.2 with ``` "line 1: /usr/lib/module-init-tools/kernel-scriptlets/kmp-pre: No such file or directory" ``` -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1192457] New: ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192457 Bug ID: 1192457 Summary: ZSTD compressed kernel module files are 35% bigger Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: schwab(a)linux-m68k.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # du -sh /lib/modules/*/kernel/ 91M /lib/modules/5.13.13-1-default/kernel/ 92M /lib/modules/5.14.14-1-default/kernel/ 125M /lib/modules/5.15.1-1.g0a42f4c-default/kernel/ # rpm -q --qf="%{NAME}-%{VERSION}: %{SIZE}\n" kernel-default kernel-default-5.13.13: 170499562 kernel-default-5.14.14: 171909997 kernel-default-5.15.1: 207900779 -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1192569] New: Regression: plugging in USB scanner breaks all USB functionality
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192569 Bug ID: 1192569 Summary: Regression: plugging in USB scanner breaks all USB functionality 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: rombert(a)apache.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 853679 --> http://bugzilla.opensuse.org/attachment.cgi?id=853679&action=edit journalctl output after plugging in USB scanner. When plugging in an USB scanner ( Brother DSMobile DS-740D ) I lose all USB devices. This used to work, but not 100% when as I don't use the scanner daily. For sure it was working ~4 weeks ago. I am Running 5.14.14-1-default, on a Lenovo Thinkpad P52. Only a reboot fixes the problem. I am connecting other USB devices ( Yubikey, USB hub with 4 other devices - Mouse, Keyboard, Mic, Android phone ) with no issues, only the scanner triggers the problem. The scanner is always plugged in directly to the laptop. I am not proactively gathering more information since I'm worried about potential hardware implications, but feel free to ask for anything that would be useful with debugging. -- You are receiving this mail because: You are the assignee for the bug.

1 19

[Bug 1190854] New: amdgpu fails to probe Radeon Pro WX3200
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190854 Bug ID: 1190854 Summary: amdgpu fails to probe Radeon Pro WX3200 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: grasland(a)lal.in2p3.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852729 --> http://bugzilla.opensuse.org/attachment.cgi?id=852729&action=edit dmesg log, with ANSI color codes On a Dell Precision 3650 equipped with a Radeon Pro WX3200, something very wrong happens during the amdgpu initialization process (or perhaps before, see below), which makes the card unusable on Linux. Thus, I have to fall back to the CPU's built-in graphics for the time being on this machine. The GPU is brand new and works on both the UEFI setup screen and Windows, which suggests to me that the hardware is not completely broken. But of course, this does not fully exclude the possibility of a hardware issue that would only be triggered by the Linux initialization process. You will find attached the dmesg log, with and without ANSI color codes as I personally find dmesg' color output much easier to visually parse. --- Let's have a closer look at the amdgpu logs, since that's what I'm directly interested in here. First we get the standard stuff, nothing special here as far as I can see. The CRAT table bit does looks suspicious, but it also happens during the init of my home Radeon RX 560 that otherwise works fine under Linux, so this does not seem to be a fatal issue... 771 �� [ 3.484654] [drm] amdgpu kernel modesetting enabled. 772 �� [ 3.484700] amdgpu: CRAT table not found 773 �� [ 3.484701] amdgpu: Virtual CRAT table created for CPU 774 �� [ 3.484707] amdgpu: Topology: Add CPU node ...then we get a power management failure, which may or may not be related to the problem at hand... 775 �� [ 3.484764] amdgpu 0000:01:00.0: can't change power state from D3hot to D0 (config space inaccessible) ...then more "normal" stuff, in the sense of stuff that looks close to what I see in the init logs of amdgpu on my RX 560... 776 �� [ 3.484888] [drm] initializing kernel modesetting (POLARIS12 0x1002:0x6981 0x1028:0x2B0D 0x10). 777 �� [ 3.484890] amdgpu 0000:01:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported 778 �� [ 3.484895] [drm] register mmio base: 0x6E900000 779 �� [ 3.484896] [drm] register mmio size: 262144 780 �� [ 3.484898] [drm] add ip block number 0 <vi_common> 781 �� [ 3.484899] [drm] add ip block number 1 <gmc_v8_0> 782 �� [ 3.484899] [drm] add ip block number 2 <tonga_ih> 783 �� [ 3.484900] [drm] add ip block number 3 <gfx_v8_0> 784 �� [ 3.484900] [drm] add ip block number 4 <sdma_v3_0> 785 �� [ 3.484901] [drm] add ip block number 5 <powerplay> 786 �� [ 3.484901] [drm] add ip block number 6 <dm> 787 �� [ 3.484902] [drm] add ip block number 7 <uvd_v6_0> 788 �� [ 3.484902] [drm] add ip block number 8 <vce_v3_0> 789 �� [ 3.484913] amdgpu 0000:01:00.0: amdgpu: Fetched VBIOS from VFCT 790 �� [ 3.484914] amdgpu: ATOM BIOS: 113-D0155200-100 791 �� [ 3.484932] [drm] vm size is 256 GB, 2 levels, block size is 10-bit, fragment size is 9-bit ...however, after this the driver tries to set up MMIO to communicate with the device, and here is where I think things go very wrong. 792 �� [ 3.485705] amdgpu 0000:01:00.0: BAR 2: releasing [mem 0x6100000000-0x61001fffff 64bit pref] 793 �� [ 3.485708] amdgpu 0000:01:00.0: BAR 0: releasing [mem 0x6000000000-0x60ffffffff 64bit pref] 794 �� [ 3.485709] [drm:amdgpu_device_resize_fb_bar [amdgpu]] *ERROR* Problem resizing BAR0 (-16). 795 �� [ 3.485811] amdgpu 0000:01:00.0: BAR 0: assigned [mem 0x6000000000-0x60ffffffff 64bit pref] 796 �� [ 3.485831] amdgpu 0000:01:00.0: BAR 0: error updating (0x00000c != 0xffffffff) 797 �� [ 3.485847] amdgpu 0000:01:00.0: BAR 0: error updating (high 0x000060 != 0xffffffff) 798 �� [ 3.485863] amdgpu 0000:01:00.0: BAR 2: assigned [mem 0x6100000000-0x61001fffff 64bit pref] 799 �� [ 3.485864] amdgpu 0000:01:00.0: BAR 2: error updating (0x00000c != 0xffffffff) 800 �� [ 3.485880] amdgpu 0000:01:00.0: BAR 2: error updating (high 0x000061 != 0xffffffff) 801 �� [ 3.485901] amdgpu 0000:01:00.0: amdgpu: VRAM: 4294967295M 0x000000FFFF000000 - 0x001000FFFEEFFFFF (4294967295M used) 802 �� [ 3.485903] amdgpu 0000:01:00.0: amdgpu: GART: 256M 0x0000000000000000 - 0x000000000FFFFFFF 803 �� [ 3.485905] [drm] Detected VRAM RAM=4294967295M, BAR=4096M 804 �� [ 3.485906] [drm] RAM width 64bits UNKNOWN 805 �� [ 3.485913] [drm] amdgpu: 4294967295M of VRAM memory ready 806 �� [ 3.485914] [drm] amdgpu: 48026M of GTT memory ready. 807 �� [ 3.485916] [drm] GART: num cpu pages 65536, num gpu pages 65536 Failing to set up PCI BARs sounds bad, and concluding from this failed setup process that the GPU has 4 PiB of VRAM sounds even worse. I wouldn't be surprised if this were the point where things really went hopeless. But amdgpu is not the kind of program that will stop cleanly when the first error occurs, so it will first wait for an event that doesn't want to happen... 808 �� [ 3.600399] amdgpu 0000:01:00.0: amdgpu: Wait for MC idle timedout ! [...] 813 �� [ 3.714578] amdgpu 0000:01:00.0: amdgpu: Wait for MC idle timedout ! ...then emits a few more messages that also appear during the successful initialization process of my home RX 560, so which I consider "normal"... 814 �� [ 3.715166] [drm] PCIE GART of 256M enabled (table at 0x000000FFFF900000). 815 �� [ 3.716221] [drm] Chained IB support enabled! 816 �� [ 3.721721] amdgpu: hwmgr_sw_init smu backed is polaris10_smu ...and only then it dies brutally. 817 �� [ 3.726521] amdgpu: 818 �� last message was failed ret is 65535 819 �� [ 3.726522] amdgpu: 820 �� failed to send message 100 ret is 65535 821 �� [ 3.726525] amdgpu: SMC address must be 4 byte aligned. 822 �� [ 3.726525] amdgpu: [AVFS][Polaris10_SetupGfxLvlStruct] Problems copying VRConfig value over to SMC 823 �� [ 3.726526] amdgpu: [AVFS][Polaris10_AVFSEventMgr] Could not Copy Graphics Level table over to SMU 824 �� [ 3.726565] amdgpu: 825 �� last message was failed ret is 65535 826 �� [ 3.726566] amdgpu: 827 �� failed to send message 252 ret is 65535 828 �� [ 3.726566] amdgpu: 829 �� last message was failed ret is 65535 830 �� [ 3.726567] amdgpu: 831 �� failed to send message 253 ret is 65535 832 �� [ 3.726569] amdgpu: 833 �� last message was failed ret is 65535 834 �� [ 3.726570] amdgpu: 835 �� failed to send message 250 ret is 65535 836 �� [ 3.726571] amdgpu: 837 �� last message was failed ret is 65535 838 �� [ 3.726571] amdgpu: 839 �� failed to send message 251 ret is 65535 840 �� [ 3.726572] amdgpu: 841 �� last message was failed ret is 65535 842 �� [ 3.726573] amdgpu: 843 �� failed to send message 254 ret is 65535 844 �� [ 3.861852] [drm] Timeout wait for RLC serdes 0,0 [...] 846 �� [ 3.975981] amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) 847 �� [ 3.976112] [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* hw_init of IP block <gfx_v8_0> failed -110 848 �� [ 3.976241] amdgpu 0000:01:00.0: amdgpu: amdgpu_device_ip_init failed 849 �� [ 3.976242] amdgpu 0000:01:00.0: amdgpu: Fatal error during GPU init 850 �� [ 3.976244] amdgpu 0000:01:00.0: amdgpu: amdgpu: finishing device. 851 �� [ 3.977567] amdgpu: probe of 0000:01:00.0 failed with error -110 852 �� [ 3.977650] [drm] amdgpu: ttm finalized --- So, to summarize, it seems something goes wrong at the MMIO setup stage, which may or may not be related to an earlier power management failure. My question is, how can I investigate this further? Here's some random trial and error stuff I already tried to no avail: - Upgrade the UEFI firmware. It's now at the latest release, and it did not change a thing. - Attempt to disable ASPM in case PCIe power management could be the issue (I found reports of an ASPM-related nvidia driver crash that started with the same ACPI error message at the beginning). Does not change anything here, rolled back. - Attempt to downgrade to an earlier amdgpu firmware, as this fixed a similar-looking crash on Arch. Did not help here, went back to the current AMD firmware. - Attempt to set the AMD GPU as the primary GPU in UEFI. This does not fix amdgpu initialization, and it breaks i915 initialization, which is definitely worse. Rolled back. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 30 Nov '21

30 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c27 --- Comment #27 from Jan Kara <jack(a)suse.com> --- Created attachment 854199 --> https://bugzilla.suse.com/attachment.cgi?id=854199&action=edit [PATCH] bfq: Fix use-after-free with cgroups Fabian, can you please try this patch, whether it fixes the KASAN splats you are getting? Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192874] During OS booting, the loading installation system progress is very slow with Intel Alder Lake nonVpro system.
by bugzilla_noreply＠suse.com 30 Nov '21

30 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192874 http://bugzilla.opensuse.org/show_bug.cgi?id=1192874#c18 Lin Ellen <ellen_lin(a)dell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ellen_lin(a)dell.com --- Comment #18 from Lin Ellen <ellen_lin(a)dell.com> --- May we have a trial version to check at our side? Thank you! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193213] Two-fingers scrolling on touch-pad no longer working
by bugzilla_noreply＠suse.com 30 Nov '21

30 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1193213 https://bugzilla.suse.com/show_bug.cgi?id=1193213#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marco.varlese(a)suse.com, | |tiwai(a)suse.com Flags| |needinfo?(marco.varlese@sus | |e.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you give dmesg outputs from both working and non-working cases? Also the hwinfo outputs from both, too, please. Last but not least, if you're running an X11 session, please check the input devices via xinput command. xinput --list will show the devices and xinput --list-props $ID will show the properties of the given device. We may see some differences in both working and non-working cases, there, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1177428] AMDGPU resume fail
by bugzilla_noreply＠suse.com 29 Nov '21

29 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1177428 https://bugzilla.suse.com/show_bug.cgi?id=1177428#c103 --- Comment #103 from Felipe Martinez <felipefm(a)gmail.com> --- That's exactly right Takashi. I originally tested out a fix through the PBS woth you guys' help and a particular 6 patches I had found on some posts online. Eventually it all worked great, then start I believe it was 5.14 (maybe 5.13?) It stopped sleeping again. This is a Lenovo Ideapad3 with a 4500U (perhaps a 5500u, i forget now I'm out of town). It sometimes goes to sleep fine but doesn't wake up, and sometimes it refuses to go to sleep and just goes dark with a flat white light (not blinking) What I can try doing is recompiling a kernel with the 6 patches I had gone with originally and see if that brings us back to working fashion. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183128] ETPS2/Elantech not working after suspend
by bugzilla_noreply＠suse.com 29 Nov '21

29 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1183128 https://bugzilla.suse.com/show_bug.cgi?id=1183128#c3 Artyom <suse(a)rop.cx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse(a)rop.cx --- Comment #3 from Artyom <suse(a)rop.cx> --- Try to disable touchpad service in background services (on kde) in my case, it helped -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180870] ETPS/2 Elantech TrackPoint and ETPS/2 Elantech Touchpad not working
by bugzilla_noreply＠suse.com 29 Nov '21

29 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1180870 https://bugzilla.suse.com/show_bug.cgi?id=1180870#c24 --- Comment #24 from Artyom <suse(a)rop.cx> --- oh, sorry, just now I noticed that this is not my bug report -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180870] ETPS/2 Elantech TrackPoint and ETPS/2 Elantech Touchpad not working
by bugzilla_noreply＠suse.com 29 Nov '21

29 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1180870 https://bugzilla.suse.com/show_bug.cgi?id=1180870#c23 --- Comment #23 from Artyom <suse(a)rop.cx> --- (In reply to Takashi Iwai from comment #22) > (In reply to Artyom from comment #21) > > (In reply to Takashi Iwai from comment #20) > > > I close this bug as the potential fix was already merged in SLE15-SP3 kernel > > > branch. > > > > Can I check it on my tumbleweed or any other free way? > > TW already contains the fix. Your problem is likely different from this. Okay, what kind of error has been fixed? Invalid elan driver (currently fixed via blacklist) or suspend/restore (currently fixed via disabling touchpad service)? I'll check then -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180870] ETPS/2 Elantech TrackPoint and ETPS/2 Elantech Touchpad not working
by bugzilla_noreply＠suse.com 29 Nov '21

29 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1180870 https://bugzilla.suse.com/show_bug.cgi?id=1180870#c22 --- Comment #22 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Artyom from comment #21) > (In reply to Takashi Iwai from comment #20) > > I close this bug as the potential fix was already merged in SLE15-SP3 kernel > > branch. > > Can I check it on my tumbleweed or any other free way? TW already contains the fix. Your problem is likely different from this. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180870] ETPS/2 Elantech TrackPoint and ETPS/2 Elantech Touchpad not working
by bugzilla_noreply＠suse.com 29 Nov '21

29 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1180870 https://bugzilla.suse.com/show_bug.cgi?id=1180870#c21 --- Comment #21 from Artyom <suse(a)rop.cx> --- (In reply to Takashi Iwai from comment #20) > I close this bug as the potential fix was already merged in SLE15-SP3 kernel > branch. Can I check it on my tumbleweed or any other free way? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1177428] AMDGPU resume fail
by bugzilla_noreply＠suse.com 29 Nov '21

29 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1177428 https://bugzilla.suse.com/show_bug.cgi?id=1177428#c102 --- Comment #102 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Felipe Martinez from comment #101) > This was fixed months ago and just started happening again I believe in 5.14? Do you mean experiencing it again on your machine? Details please. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180870] ETPS/2 Elantech TrackPoint and ETPS/2 Elantech Touchpad not working
by bugzilla_noreply＠suse.com 29 Nov '21

29 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1180870 https://bugzilla.suse.com/show_bug.cgi?id=1180870#c20 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #20 from Takashi Iwai <tiwai(a)suse.com> --- I close this bug as the potential fix was already merged in SLE15-SP3 kernel branch. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193169] New: Intel I225-IT Ethernet controller is not working during driver probe function
by bugzilla_noreply＠suse.com 29 Nov '21

29 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193169 Bug ID: 1193169 Summary: Intel I225-IT Ethernet controller is not working during driver probe function Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ee.lim.ong(a)ni.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After installing OpenSUSE 15.3 (Kernel 5.3.18-59.10-default) on PXIe controller with I225-IT Ethernet Controller, running dmesg message output the following error thrown by igc driver module: [ 22.237086] igc: probe of 0000:6d:00.0 failed with error -2 [ 22.266648] igc: probe of 0000:6e:00.0 failed with error -2 After sending inquiry to Intel, they stated that while kernel 5.15 is the official kernel containing igc driver module to support I225-IT Ethernet Controller, for any official Linux kernel between 5.8 to 5.14, manually adding these 2 patches will address the bug. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id… https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id… I would like to request for backporting these 2 patches into the official OpenSUSE Leap 15.3 (and later) kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 2