March 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] Account verification
by noreply＠suse.de 18 Nov '24

18 Nov '24

Dear user opensuse-kernelbugs, we have received your email verification request. To verify your email address, please follow this link: https://idp-portal.suse.com/univention/self-service/#page=verifyaccount&tok… If the link does not work, you can go to https://idp-portal.suse.com/univention/self-service/#page=verifyaccount and enter the following token manually: vNjCDHqnMwqYa48z3RokLQTpZdp3sYBxddU7iGJR9UhboG8guN3hssVvHHxVARWo -- To unsubscribe, e-mail: kernel-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kernel-bugs+owner(a)opensuse.org

2 1

[kernel-bugs] [Bug 1172181] test bug for assignee change
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

http://bugzilla.suse.com/show_bug.cgi?id=1172181 Jeff Mahoney <jeffm(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jeffm(a)suse.com |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 1

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

27 Jan '23

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

1 6

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

27 Jan '23

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

1 7

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

25 Jan '23

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

1 2

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

20 Jan '23

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

1 6

[Bug 1180985] New: Kernel 5.10 breaks ethernet connection with lenovo x390
by bugzilla_noreply＠suse.com 30 Sep '22

30 Sep '22

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.

1 17

[Bug 1180591] New: Display backlight stuck at 100%
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1180591 Bug ID: 1180591 Summary: Display backlight stuck at 100% 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: maurizio.galli(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 844855 --> http://bugzilla.opensuse.org/attachment.cgi?id=844855&action=edit system information I have just upgraded my device to Tumbleweed and now backlight brightness is stuck at 100% with no way to change it. I have tried several methods, including xbacklight and Xfce settings. Backlight control used to work fine with Kernel 5.3 shipped by Leap. I found a recent report using similar hardware that could suggest a regression in the kernel: https://discuss.getsol.us/d/6039-brightness-control-not-working-on-apple-di… I attached information about my system but please let me know what else I can provide. -- You are receiving this mail because: You are the assignee for the bug.

1 24

[kernel-bugs] [Bug 1174622] New: System not reconnecting to WLAN after suspend/resume
by bugzilla_noreply＠suse.com 22 Jul '22

22 Jul '22

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.

1 27

[kernel-bugs] [Bug 1174868] New: Upgrade to LEAP 15.2 makes Thinkpad 480s sometimes completely freezes, 20°C warmer and journal is trimmed
by bugzilla_noreply＠suse.com 20 Jul '22

20 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1174868 Bug ID: 1174868 Summary: Upgrade to LEAP 15.2 makes Thinkpad 480s sometimes completely freezes, 20°C warmer and journal is trimmed 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: markus.zimmermann(a)symflower.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- One of our machines here a Thinkpad T480s on openSUSE 15.2 kernel 5.3.18-lp152.33-default. In general this machine was upgraded from LEAP 15.1 to 15.2 and then the problems started to show. The CPU is constantly hotter while working. by 20°C. This machine now freezes sometimes completely. The machine is then - not pingable - no keyboard interaction works - lid close/open does nothng - no mouse interaction works - the notebook is really warm - When a freeze happens also a trim of the journal happens... e.g. we loose the whole journal for the day. - We SSH'ed into the machine and watched via "htop", "journal -f" and "sensors". WHen the machine freezes, there is no significant load via htop seeable, there are no interesting logs in journal and sensors shows that it is simply hotter. Interestingly, we upgraded another machine before (also a Thinkpad T480s) and this does not have any problems. We are btw on the latest firmwares using fwupdmgr. What should we try? How can we debug it? -- You are receiving this mail because: You are the assignee for the bug.

1 20

[kernel-bugs] [Bug 1177800] New: [Ten64] getsysinfo caused kernel error (synchronous external abort)
by bugzilla_noreply＠suse.com 08 Jul '22

08 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177800 Bug ID: 1177800 Summary: [Ten64] getsysinfo caused kernel error (synchronous external abort) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: afaerber(a)suse.com QA Contact: qa-bugs(a)suse.de CC: matt(a)traverse.com.au, snwint(a)suse.com, yousaf.kaukab(a)suse.com Found By: --- Blocker: --- Running `getsysinfo` (via ssh) on Tumbleweed 20201011 with kernel-default 5.9.0 from Kernel:HEAD repository caused a kernel error, with ssh getting stuck and reconnections failing. Serial login still worked. zehn:~ # getsysinfo /proc/bus/input /proc/cpuinfo /proc/device-tree /proc/devices /proc/fb /proc/filesystems /proc/interrupts /proc/iomem /proc/ioports /proc/meminfo /proc/modules /proc/net/dev /proc/partitions /proc/scsi /proc/tty /proc/version /sys /usr/sbin/getsysinfo: line 23: 2761 Segmentation fault cp -x -a --parents "$i" "$dir/$host" 2> /dev/null /var/lib/hardware/udi /proc/mounts System data written to: /tmp/zehn.tar.gz zehn:~ # [ 544.956478] Internal error: synchronous external abort: 96000210 [#1] SMP [ 544.963295] Modules linked in: af_packet ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter xt_tcpudp ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security iscsi_ibft iscsi_boot_sysfs ip_set nfnetlink ebtable_filter ebtables rfkill ip6table_filter ip6_tables iptable_filter ip_tables x_tables fsl_dpaa2_ptp ptp_qoriq fsl_dpaa2_eth phylink xgmac_mdio hid_generic fsl_mc_dpio usbhid cdc_acm i2c_mux_pca954x i2c_mux tpm_i2c_atmel spi_fsl_qspi qoriq_thermal leds_gpio optee tee uio_pdrv_genirq uio qoriq_cpufreq nls_iso8859_1 nls_cp437 vfat fat drm xhci_plat_hcd xhci_hcd usbcore caam_jr mmc_block libdes authenc caamhash_desc caamalg_desc crypto_engine rtc_ds1307 mp886x aes_ce_blk crypto_simd cryptd aes_ce_cipher crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce dpaa2_console nvme nvme_core dwc3 sdhci_of_esdhc caam sdhci_pltfm ulpi [ 544.963547] error sdhci udc_core roles mmc_core i2c_imx btrfs blake2b_generic libcrc32c xor xor_neon raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 545.066303] CPU: 0 PID: 2761 Comm: cp Not tainted 5.9.0-1.g11733e1-default #1 openSUSE Tumbleweed (unreleased) [ 545.076303] Hardware name: traverse ten64/ten64, BIOS 2020.07-rc1-g1d4a3d9d5c 07/28/2020 [ 545.084393] pstate: 60000085 (nZCv daIf -PAN -UAO BTYPE=--) [ 545.089967] pc : dw_pcie_read+0x48/0xc0 [ 545.093799] lr : dw_pcie_access_other_conf.isra.0+0xc4/0x120 [ 545.099452] sp : ffff800012203bf0 [ 545.102759] x29: ffff800012203bf0 x28: 0000000000000400 [ 545.108067] x27: ffff00833e683400 x26: ffff008348240000 [ 545.113375] x25: ffff800010085000 x24: 0000000000000000 [ 545.118683] x23: ffff00834b239880 x22: ffff800012203cc4 [ 545.123991] x21: 0000000000000004 x20: 0000000000000400 [ 545.129299] x19: ffff00834b2398a8 x18: 0000000000000000 [ 545.134607] x17: 0000000000000000 x16: ffffafadaf1be170 [ 545.139915] x15: 0000000000000000 x14: 0000000000000000 [ 545.145222] x13: 0000000000000000 x12: 0000000000000040 [ 545.150530] x11: ffff00834bd8c920 x10: 0000000000000000 [ 545.155837] x9 : ffffafadaf12e8f4 x8 : 0000000002080000 [ 545.161145] x7 : 0000000000000000 x6 : ffff800010f00000 [ 545.166452] x5 : 0000000000000000 x4 : 0000000000000908 [ 545.171759] x3 : 0000000000000003 x2 : ffff800012203cc4 [ 545.177066] x1 : 0000000000000004 x0 : ffff800010085400 [ 545.182374] Call trace: [ 545.184816] dw_pcie_read+0x48/0xc0 [ 545.188298] dw_pcie_rd_conf+0x11c/0x150 [ 545.192217] pci_user_read_config_dword+0xa8/0x190 [ 545.197004] pci_read_config+0x1f8/0x264 [ 545.200923] sysfs_kf_bin_read+0x78/0xa0 [ 545.204840] kernfs_file_direct_read+0x90/0x220 [ 545.209365] kernfs_fop_read+0x44/0x50 [ 545.213111] vfs_read+0xb8/0x1e4 [ 545.216334] ksys_read+0x78/0x110 [ 545.219643] __arm64_sys_read+0x28/0x34 [ 545.223476] el0_svc_common.constprop.0+0x84/0x230 [ 545.228261] do_el0_svc+0x30/0xa0 [ 545.231572] el0_svc+0x18/0x50 [ 545.234621] el0_sync_handler+0x90/0x254 [ 545.238538] el0_sync+0x158/0x180 [ 545.241849] Code: 528010e0 d50323bf b900005f d65f03c0 (b9400001) [ 545.247941] ---[ end trace 68383e7eecaae870 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kernel-bugs] [Bug 1177288] New: Raspberry pi3 (model b) crashes with network gadget
by bugzilla_noreply＠suse.com 03 Jul '22

03 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177288 Bug ID: 1177288 Summary: Raspberry pi3 (model b) crashes with network gadget 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: coolo(a)suse.com QA Contact: qa-bugs(a)suse.de CC: guillaume.gardet(a)arm.com, nsaenzjulienne(a)suse.com Found By: --- Blocker: --- I use the official Leap 15.2 Jeos image on a pi3b and have a USB network device attached to it (a very special one, https://www.fibrecode.com/fc602-usb-oabr-broadr-reach-100base-t1-stick.html) and it crashes the kernel pretty reliably with the following crash dump. [ 86.184109] usb 1-1.3: USB disconnect, device number 5 [ 86.184427] cdc_ether 1-1.3:1.0 eth2: unregister 'cdc_ether' usb-3f980000.usb-1.3, CDC Ethernet Device [ 99.795717] usb 1-1.3: new high-speed USB device number 7 using dwc2 [ 99.926758] usb 1-1.3: New USB device found, idVendor=152a, idProduct=857b, bcdDevice= 2.24 [ 99.926780] usb 1-1.3: New USB device strings: Mfr=2, Product=1, SerialNumber=3 [ 99.926788] usb 1-1.3: Product: FibreCode FC602 Stick [ 99.926796] usb 1-1.3: Manufacturer: FibreCode [ 99.926804] usb 1-1.3: SerialNumber: FC01330000018a69 [ 99.930380] cdc_ether 1-1.3:1.0 eth1: register 'cdc_ether' at usb-3f980000.usb-1.3, CDC Ethernet Device, fc:c2:3d:1f:7f:ad [ 99.949857] cdc_ether 1-1.3:1.0 eth2: renamed from eth1 [ 740.880346] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 7 - ChHltd set, but reason is unknown [ 740.880360] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04400001 [ 741.461843] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown [ 741.461858] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x06400001 [ 741.880374] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 5 - ChHltd set, but reason is unknown [ 741.880386] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04400001 [ 741.880395] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 741.880573] WARNING: CPU: 0 PID: 0 at ../drivers/usb/dwc2/hcd.c:2683 dwc2_assign_and_init_hc+0x664/0xa10 [dwc2] [ 741.880578] Modules linked in: af_packet iscsi_ibft iscsi_boot_sysfs vc4 drm_kms_helper drm btsdio snd_soc_core bluetooth snd_compress snd_bcm2835(C) nls_iso8859_1 ac97_bus nls_cp437 snd_pcm_dmaengine ecdh_generic snd_pcm bcm2835_v4l2(C) ecc vfat v4l2_common snd_timer fat videobuf2_vmalloc brcmfmac videobuf2_memops videobuf2_v4l2 snd videobuf2_common videodev mc brcmutil cpufreq_dt soundcore fb_sys_fops cfg80211 syscopyarea sysfillrect microchip sysimgblt rfkill ftdi_sio cdc_ether usbnet lan78xx usbserial mii raspberrypi_hwmon bcm2835_thermal raspberrypi_cpufreq vchiq(C) bcm2835_rng bcm2835_wdt crct10dif_ce uio_pdrv_genirq uio leds_gpio ext4 mbcache jbd2 mmc_block dwc2 udc_core usbcore sdhci_iproc sdhci_pltfm sdhci bcm2835 gpio_raspberrypi_exp mmc_core clk_raspberrypi i2c_bcm2835 bcm2835_dma fixed phy_generic dm_mirror dm_region_hash dm_log sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod efivarfs [ 741.880754] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C 5.3.18-lp152.36-default #1 openSUSE Leap 15.2 (unreleased) [ 741.880759] Hardware name: raspberrypi rpi/rpi, BIOS 2020.01 06/02/2020 [ 741.880765] pstate: 60000085 (nZCv daIf -PAN -UAO) [ 741.880799] pc : dwc2_assign_and_init_hc+0x664/0xa10 [dwc2] [ 741.880834] lr : dwc2_hcd_select_transactions+0x104/0x1a0 [dwc2] [ 741.880838] sp : ffff000010003c60 [ 741.880842] x29: ffff000010003c60 x28: ffff3bd997683dc0 [ 741.880849] x27: ffffa6ec7c4c4000 x26: ffff3bd997679000 [ 741.880857] x25: 0000000000000008 x24: ffffa6ec7c6a55e0 [ 741.880864] x23: ffffa6ec6bbc5080 x22: ffffa6ec77d12830 [ 741.880871] x21: ffffa6ec79871600 x20: ffffa6ec7c6a5080 [ 741.880878] x19: ffffa6ec6bbc50c8 x18: ffffffffffffffff [ 741.880885] x17: 0000000000000001 x16: 0000000000000007 [ 741.880891] x15: ffff3bd997679708 x14: ffff3bd9978cfa28 [ 741.880898] x13: ffff3bd9978cf67e x12: ffff3bd9976a2000 [ 741.880905] x11: 0000000000000000 x10: ffff3bd9978ce000 [ 741.880912] x9 : 0000000000000000 x8 : 0000000000000003 [ 741.880919] x7 : 0000000000000176 x6 : ffff3bd9978cec90 [ 741.880925] x5 : 0000000000000001 x4 : ffffa6ec79871698 [ 741.880932] x3 : 0000000000000000 x2 : 00000000000005ee [ 741.880939] x1 : 0000000000000000 x0 : 0000000000000002 [ 741.880946] Call trace: [ 741.880984] dwc2_assign_and_init_hc+0x664/0xa10 [dwc2] [ 741.881018] dwc2_hcd_select_transactions+0x104/0x1a0 [dwc2] [ 741.881052] dwc2_release_channel+0xfc/0x280 [dwc2] [ 741.881087] dwc2_halt_channel+0xac/0x158 [dwc2] [ 741.881121] dwc2_hc_n_intr+0x860/0x8c0 [dwc2] [ 741.881155] dwc2_handle_hcd_intr+0x38c/0x450 [dwc2] [ 741.881188] _dwc2_hcd_irq+0x20/0x30 [dwc2] [ 741.881278] usb_hcd_irq+0x3c/0x60 [usbcore] [ 741.881291] __handle_irq_event_percpu+0x74/0x268 [ 741.881299] handle_irq_event_percpu+0x40/0x98 [ 741.881307] handle_irq_event+0x50/0xa8 [ 741.881314] handle_level_irq+0xd4/0x178 [ 741.881321] generic_handle_irq+0x34/0x50 [ 741.881332] bcm2836_chained_handle_irq+0x4c/0x70 [ 741.881339] generic_handle_irq+0x34/0x50 [ 741.881346] __handle_domain_irq+0x68/0xc0 [ 741.881354] bcm2836_arm_irqchip_handle_irq+0x78/0xe0 [ 741.881360] el1_irq+0xcc/0x180 [ 741.881369] arch_cpu_idle+0x40/0x1c0 [ 741.881377] default_idle_call+0x24/0x44 [ 741.881385] do_idle+0x1dc/0x2c0 [ 741.881392] cpu_startup_entry+0x28/0x30 [ 741.881400] rest_init+0xc4/0xd0 [ 741.881409] arch_call_rest_init+0x14/0x1c [ 741.881414] start_kernel+0x4e8/0x51c [ 741.881419] ---[ end trace 29007ab7897c5716 ]--- [ 742.880425] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 7 - ChHltd set, but reason is unknown [ 742.880437] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 742.880445] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 743.880453] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 3 - ChHltd set, but reason is unknown [ 743.880465] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 743.880474] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 744.880491] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 4 - ChHltd set, but reason is unknown [ 744.880505] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 744.880514] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 745.880537] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 6 - ChHltd set, but reason is unknown [ 745.880549] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 745.880557] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 746.880564] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 5 - ChHltd set, but reason is unknown [ 746.880576] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 746.880585] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 747.880601] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown [ 747.880612] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 747.880621] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 748.880641] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 6 - ChHltd set, but reason is unknown [ 748.880654] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600009 [ 748.880664] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 749.880675] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown [ 749.880686] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 749.880695] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 750.880718] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 4 - ChHltd set, but reason is unknown -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1180316] New: [Build 20201222] openQA test fails in kdump_and_crash
by bugzilla_noreply＠suse.com 15 Mar '22

15 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1180316 Bug ID: 1180316 Summary: [Build 20201222] openQA test fails in kdump_and_crash Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1523048/modules/kdum p_and_crash/steps/58 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G fails in [kdump_and_crash](https://openqa.opensuse.org/tests/1523048/modules/kdump_an… After the update to kernel 5.10, kdump_and_crash fails crash: cannot determine length of symbol: log_end ## Test suite description Same as jeos, plus some more tests. ## Reproducible Fails since (at least) Build [20190311](https://openqa.opensuse.org/tests/877894) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1183990] New: I think I found the cause of a kernel lock when attempting hibernation
by bugzilla_noreply＠suse.com 10 Mar '22

10 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1183990 Bug ID: 1183990 Summary: I think I found the cause of a kernel lock when attempting hibernation 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: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, For months I have been experiencing a kernel "trouble" in _some_ of my attempts to hibernate. Sometimes the hibernation would stall and not proceed. Issuing "systemctl hibernate" replied that there was one in progress, but there was no progress. I would attempt to halt the machine, but this would also stall at some point. If I pressed ctrl-alt-del several times, fast, I would see the message that it had detected the keys seven times and would halt immediately, but it did not. I had no way out but hit the power switch, and suffer the long fsck the next morning. Nothing in the logs whatsoever. Well, one day I noticed in "atop" that one of my disks went to 100% busy when this happened. So I left running another instance of gkrellm, displaying the i/o state of all my partitions in /dev/sdc, and experimenting with "sync" I noticed it was sdc9 which was active, at something like 400 Kbps. I noticed that "sync" would take sometimes a minute to complete. /dev/sdc9 is a reiserfs, and has several bind mounts: /dev/sdc9 on /data/Lareiserfs type reiserfs (rw,relatime,lazytime,user_xattr,acl) bind mounts: /dev/sdc9 on /data/homedvl type reiserfs (rw,relatime,lazytime,user_xattr,acl) /dev/sdc9 on /usr/share/flightgear type reiserfs (rw,relatime,lazytime,user_xattr,acl) /dev/sdc9 on /var/spool/news type reiserfs (rw,relatime,lazytime,user_xattr,acl) /dev/sdc9 on /home/cer/terrasync type reiserfs (rw,relatime,lazytime,user_xattr,acl) /dev/sdc9 on /usr/src type reiserfs (rw,relatime,lazytime,user_xattr,acl) Now, the directory that is active is "/var/spool/news". I use leafnode nntp proxy server. It contains 1.2 million files in about 3 GB of space. I found that if I run this sequence: time sync time sync && systemctl hibernate the machine hibernates successfully - 13 days so far, a record. Most days it takes a minute to sync, but one day, I noticed it took several minutes. Why? Well, it happened that at the same time "/usr/sbin/texpire" was working (a cronjob triggers it). This task runs for about half an hour daily expunging old posts, meaning it examines a million files. Maybe with this (tentative) report you can improve the kernel response so that it doesn't stall when trying to hibernate, assumedly when taking too long to sync. Me would think that the kernel should stop tasks before doing the sync :-? At least, running sync manually I can detect the situation and kill the busy task before suffering the crash. On the other hand, maybe there is an issue on reiserfs with "lazytime" (which is default), delaying the writes of "something" till forced to. My wild guess, it delays the timestamp that registers a file was touched. Each time I read a post, or Thunderbird scans a post, the timestamp (sorry, I don't remember which exact timestamp it is) is written, but it is not actually written but delayed "for ever". I use reiserfs for this mount because in theory it should work better than others with millions of small files. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[kernel-bugs] [Bug 1177624] New: watchdog: BUG: soft lockup - CPU#16 stuck for 23s! [qemu-system-aar:4554]
by bugzilla_noreply＠suse.com 08 Mar '22

08 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177624 Bug ID: 1177624 Summary: watchdog: BUG: soft lockup - CPU#16 stuck for 23s! [qemu-system-aar:4554] Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, dmueller(a)suse.com Found By: --- Blocker: --- Created attachment 842562 --> http://bugzilla.opensuse.org/attachment.cgi?id=842562&action=edit dmesg.log The D05 machine used as a worker for openqa.opensuse.org have been upgraded from Leap 15.1 to Leap 15.2 and shows lots of performance problems. Lots of mistyping in qemu, few screen corruptions. Checking the kernel log (in attachment), we can see some traces related to the watchdog. -- You are receiving this mail because: You are the assignee for the bug.

1 5

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