June 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[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 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 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 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