April 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1182535] New: Start-up hangs with iommu message

by bugzilla_noreply＠suse.com

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.

4 months, 2 weeks

1
2
0 0

[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

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.

4 months, 2 weeks

1
5
0 0

[Bug 1182226] New: amdgpu driver not working in Leap 15.2

by bugzilla_noreply＠suse.com

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.

4 months, 2 weeks

1
2
0 0

[Bug 1180985] New: Kernel 5.10 breaks ethernet connection with lenovo x390

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1180985 Bug ID: 1180985 Summary: Kernel 5.10 breaks ethernet connection with lenovo x390 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: fcastelli(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have a lenovo x390 laptop with an intel CPU. I've been running Tumbleweed on it since a while because I needed a newer kernel compared to Leap to get my network card to work. Everything worked fine since I upgraded to 5.10.x. The upgrade caused the ethernet card to became unreliable (like it happened with old Leap 15.1 kernel). The network card works fine for some time, then it suddenly loses the connection. I can see Gnome NetworkManager trying to setup the card, but the process never ends. The x390 doesn't have a physical eth port, it has a proprietary adapter that provides that to the laptop. This adapter is plagued by the issue. The same issue happens when I connect the computer to its USB-C docking station (an official one provided by Lenovo). The docking station provides an eth port which is affected by this issue. The 5.9.14-1.2 and the 5.9.12-1.1 kernels are the last kernels I tested on my computer that proved to be fine. I'll try to collect more detailed logs from syslog, but right now it's a bit hard for me because I cannot reproduce the issue. I just have to wait for it to happen... -- You are receiving this mail because: You are the assignee for the bug.

4 months, 3 weeks

1
16
0 0

[Bug 1181327] New: kernel splat, screen remains in power save mode

by bugzilla_noreply＠suse.com

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.

4 months, 3 weeks

1
7
0 0

[Bug 1179894] New: warnings in OBS builds from kernel+initrd about "Warning: running kernel does not support fscaps"

by bugzilla_noreply＠suse.com

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

5 months, 1 week

1
5
0 0

[kernel-bugs] [Bug 1174622] New: System not reconnecting to WLAN after suspend/resume

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1174622 Bug ID: 1174622 Summary: System not reconnecting to WLAN after suspend/resume Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: holgi(a)suse.com QA Contact: qa-bugs(a)suse.de CC: tiwai(a)suse.com Found By: Development Blocker: --- Created attachment 840122 --> https://bugzilla.suse.com/attachment.cgi?id=840122&action=edit Output of hwinfo --netcard System with NetworkManger is connected to a wifi network. After suspend and resume later, it is not able to reconnect to the same wifi network. After a reboot, system is connecting to the same wifi network without any problems. -- You are receiving this mail because: You are the assignee for the bug.

5 months, 1 week

1
25
0 0

[kernel-bugs] [Bug 1178463] New: Flood of "usb usb{2,6}-port1: Cannot enable." messages

by bugzilla_noreply＠suse.com

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

5 months, 1 week

1
6
0 0

[Bug 1180260] New: [RPi4] Switch to vc4 for display/sound (was rooted through efifb)

by bugzilla_noreply＠suse.com

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.

5 months, 2 weeks

1
4
0 0

[kernel-bugs] [Bug 1179226] New: System hang related to power saving

by bugzilla_noreply＠suse.com

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.

5 months, 2 weeks

1
6
0 0