November 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1178474] [i915] Display freezes for up to tens of seconds with kernel 5.9
by bugzilla_noreply＠suse.com 25 Nov '20

25 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178474 Thomas Zimmermann <tzimmermann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1179092 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1179092] [i915] Screen occasionally goes blank, sometimes staying that way until I press a key
by bugzilla_noreply＠suse.com 25 Nov '20

25 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1179092 Thomas Zimmermann <tzimmermann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1178474 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1178275] usb3 device generates lots of command errors
by bugzilla_noreply＠suse.com 25 Nov '20

25 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1178275 http://bugzilla.opensuse.org/show_bug.cgi?id=1178275#c7 Gus Fos <tvarsis(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tvarsis(a)hotmail.com --- Comment #7 from Gus Fos <tvarsis(a)hotmail.com> --- I think this is the issue that is affecting me as well. I have a USB EV Cert token from Sectigo, that I have mounted to a Windows 10 VM running in KVM. It has worked flawlessly for a long time, but after I went from October 14 update to November 19 snapshot, it has stopped working. This is how it is mounted to KVM and is the same config that I have run for a year: <hostdev mode="subsystem" type="usb" managed="yes"> <source startupPolicy="optional"> <vendor id="0x0529"/> <product id="0x0620"/> </source> </hostdev> This is what I get from dmesg when I plug in the USB and then start the VM: [55212.993512] usb 1-2: new full-speed USB device number 15 using xhci_hcd [55213.147159] usb 1-2: New USB device found, idVendor=0529, idProduct=0620, bcdDevice= 0.01 [55213.147164] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [55213.147166] usb 1-2: Product: Token JC [55213.147169] usb 1-2: Manufacturer: SafeNet [55289.253516] virbr0: port 1(vnet5) entered blocking state [55289.253520] virbr0: port 1(vnet5) entered disabled state [55289.253666] device vnet5 entered promiscuous mode [55289.254320] virbr0: port 1(vnet5) entered blocking state [55289.254324] virbr0: port 1(vnet5) entered listening state [55291.269169] virbr0: port 1(vnet5) entered learning state [55293.285164] virbr0: port 1(vnet5) entered forwarding state [55293.285166] virbr0: topology change detected, propagating [55294.497605] usb 1-2: reset full-speed USB device number 15 using xhci_hcd [55295.509558] usb 1-2: reset full-speed USB device number 15 using xhci_hcd [55296.681547] usb 1-2: reset full-speed USB device number 15 using xhci_hcd [55297.961482] usb 1-2: reset full-speed USB device number 15 using xhci_hcd And then Windows reports Device Manager reports it as "Unknown USB Deice (Invalid Configuration Descriptor)" Code 43. I have tested it directly on a Windows 10 laptop and then it works fine. Also tested different ports and same issue on all ports, and other USB devices still work fine on all ports, so it is not hardware related. I have also tested to change USB controllers and different configs for the VM, but nothing helps. So I'm pretty sure this must be from an update during that time period that have broken this. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1179158] New: fstrim.timer crashes system
by bugzilla_noreply＠suse.com 25 Nov '20

25 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179158 Bug ID: 1179158 Summary: fstrim.timer crashes system 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: frede(a)b1-systems.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- every time the fstrim.timer executes /usr/sbin/fstrim -Av all Filesystems are inaccessible. in dmesg i can see a trace. [Tue Nov 24 10:37:25 2020] WARNING: CPU: 23 PID: 1027 at ../drivers/nvme/host/core.c:640 nvme_setup_discard+0x167/0x1e0 [nvme_core] [Tue Nov 24 10:37:25 2020] Modules linked in: binfmt_misc vhost_net vhost tap ip6table_mangle ip6table_nat ebtable_filter ebtables ip6table_filter ip6_tables tun bridge stp llc af_packet iscsi_ibft rfkill dmi_sysfs ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_conntrack iptable_filter xt_MASQUERADE iptable_nat nf_nat nf_conntrack msr nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_mangle ip_tables x_tables bpfilter nct6775 hwmon_vid snd_hda_intel snd_hda_codec snd_hda_core amd64_edac_mod snd_hwdep edac_mce_amd snd_pcm kvm_amd wmi_bmof kvm snd_timer snd sp5100_tco irqbypass pcspkr i2c_piix4 k10temp soundcore gpio_amdpt gpio_generic acpi_cpufreq raid1 md_mod dm_service_time drm_vram_helper drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ttm crc32c_intel ghash_clmulni_intel aesni_intel drm xhci_pci aes_x86_64 crypto_simd xhci_hcd cryptd glue_helper nvme igb ccp nvme_core usbcore dca i2c_algo_bit wmi button sunrpc dm_mirror dm_region_hash dm_log be2iscsi bnx2i [Tue Nov 24 10:37:25 2020] cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_transport_iscsi [Tue Nov 24 10:37:25 2020] CPU: 23 PID: 1027 Comm: md3_raid1 Not tainted 5.3.18-lp152.50-default #1 openSUSE Leap 15.2 [Tue Nov 24 10:37:25 2020] Hardware name: Hetzner /B450D4U-V1L, BIOS L1.02W 07/09/2020 [Tue Nov 24 10:37:25 2020] RIP: 0010:nvme_setup_discard+0x167/0x1e0 [nvme_core] [Tue Nov 24 10:37:25 2020] Code: 48 8b 73 38 48 8b 80 b0 0a 00 00 48 2b 05 41 1d 73 c4 48 c1 f8 06 48 c1 e0 0c 48 03 05 42 1d 73 c4 48 85 f6 0f 85 e1 fe ff ff <0f> 0b ba 00 00 00 80 48 01 c2 72 5d 48 c7 c1 00 00 00 80 48 2b 0d [Tue Nov 24 10:37:25 2020] RSP: 0018:ffffa5f580d5f8e0 EFLAGS: 00010202 [Tue Nov 24 10:37:25 2020] RAX: ffff9127c60ab000 RBX: ffff9127abf8e280 RCX: ffff9128460ab000 [Tue Nov 24 10:37:25 2020] RDX: 0000000000000002 RSI: 0000000000000000 RDI: 0000000000000001 [Tue Nov 24 10:37:25 2020] RBP: ffffa5f580d5f988 R08: 0000000000000000 R09: 00000000194a17f8 [Tue Nov 24 10:37:25 2020] R10: 0000000000000008 R11: 0000000000000000 R12: ffff9127af5f4a00 [Tue Nov 24 10:37:25 2020] R13: 0000000000000000 R14: ffff9127b43da000 R15: ffff9127abf8e280 [Tue Nov 24 10:37:25 2020] FS: 0000000000000000(0000) GS:ffff9127cebc0000(0000) knlGS:0000000000000000 [Tue Nov 24 10:37:25 2020] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [Tue Nov 24 10:37:25 2020] CR2: 00007ffc239bb000 CR3: 0000001f78f52000 CR4: 0000000000340ee0 [Tue Nov 24 10:37:25 2020] Call Trace: [Tue Nov 24 10:37:25 2020] nvme_setup_cmd+0x155/0x320 [nvme_core] [Tue Nov 24 10:37:25 2020] nvme_queue_rq+0x7c/0xaff [nvme] [Tue Nov 24 10:37:25 2020] ? blk_mq_get_tag+0xd3/0x250 [Tue Nov 24 10:37:25 2020] ? wait_woken+0x80/0x80 [Tue Nov 24 10:37:25 2020] __blk_mq_try_issue_directly+0x133/0x200 [Tue Nov 24 10:37:25 2020] blk_mq_request_issue_directly+0x48/0xe0 [Tue Nov 24 10:37:25 2020] ? blk_account_io_start+0xb1/0x160 [Tue Nov 24 10:37:25 2020] dm_mq_queue_rq+0x2d5/0x3f0 [dm_mod] [Tue Nov 24 10:37:25 2020] ? blk_mq_get_driver_tag+0xa0/0x110 [Tue Nov 24 10:37:25 2020] blk_mq_dispatch_rq_list+0x90/0x540 [Tue Nov 24 10:37:25 2020] ? elv_rb_del+0x1f/0x30 [Tue Nov 24 10:37:25 2020] ? deadline_remove_request+0x49/0xb0 [Tue Nov 24 10:37:25 2020] blk_mq_do_dispatch_sched+0x5f/0xf0 [Tue Nov 24 10:37:25 2020] blk_mq_sched_dispatch_requests+0xf9/0x170 [Tue Nov 24 10:37:25 2020] __blk_mq_run_hw_queue+0x52/0x110 [Tue Nov 24 10:37:25 2020] __blk_mq_delay_run_hw_queue+0x100/0x150 [Tue Nov 24 10:37:25 2020] blk_mq_run_hw_queue+0x50/0x100 [Tue Nov 24 10:37:25 2020] blk_mq_sched_insert_requests+0x71/0xf0 [Tue Nov 24 10:37:25 2020] blk_mq_flush_plug_list+0xf6/0x2b0 [Tue Nov 24 10:37:25 2020] blk_flush_plug_list+0xc4/0xf0 [Tue Nov 24 10:37:25 2020] blk_finish_plug+0x27/0x40 [Tue Nov 24 10:37:25 2020] raid1d+0x5d8/0xd40 [raid1] [Tue Nov 24 10:37:25 2020] ? __switch_to+0x7a/0x440 [Tue Nov 24 10:37:25 2020] ? __switch_to_asm+0x34/0x70 [Tue Nov 24 10:37:25 2020] ? lock_timer_base+0x67/0x80 [Tue Nov 24 10:37:25 2020] ? try_to_del_timer_sync+0x4d/0x80 [Tue Nov 24 10:37:25 2020] ? selinux_task_setrlimit+0x30/0x80 [Tue Nov 24 10:37:25 2020] ? md_start_sync+0xe0/0xe0 [md_mod] [Tue Nov 24 10:37:25 2020] ? md_thread+0x122/0x160 [md_mod] [Tue Nov 24 10:37:25 2020] md_thread+0x122/0x160 [md_mod] [Tue Nov 24 10:37:25 2020] ? wait_woken+0x80/0x80 [Tue Nov 24 10:37:25 2020] kthread+0x10d/0x130 [Tue Nov 24 10:37:25 2020] ? kthread_park+0xa0/0xa0 [Tue Nov 24 10:37:25 2020] ret_from_fork+0x22/0x40 [Tue Nov 24 10:37:25 2020] ---[ end trace 5a7ba98f36d017da ]--- Hardware Motherboard ASRockRack B450D4U-V1L CPU AMD Ryzen 9 3900 RAM 128GB Disk 2x Samsung PM983 MZQLB1T9HAJR 1.92TB # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:0 0 1.8T 0 disk ��eui.343339304e4016760025384100000001 254:0 0 1.8T 0 mpath �� eui.343339304e4016760025384100000001-part1 254:2 0 4G 0 part �� md0 9:0 0 4G 0 raid1 [SWAP] �� eui.343339304e4016760025384100000001-part2 254:3 0 512M 0 part �� md1 9:1 0 511M 0 raid1 /boot �� eui.343339304e4016760025384100000001-part3 254:4 0 32G 0 part �� md2 9:2 0 32G 0 raid1 / �� eui.343339304e4016760025384100000001-part4 254:5 0 1K 0 part �� eui.343339304e4016760025384100000001-part5 254:6 0 1.7T 0 part �� md3 9:3 0 1.7T 0 raid1 /vmspace ��nvme0n1p1 259:2 0 4G 0 part ��nvme0n1p2 259:3 0 512M 0 part ��nvme0n1p3 259:4 0 32G 0 part ��nvme0n1p4 259:5 0 1K 0 part ��nvme0n1p5 259:6 0 1.7T 0 part nvme1n1 259:1 0 1.8T 0 disk ��eui.343339304e4016630025384100000001 254:1 0 1.8T 0 mpath �� eui.343339304e4016630025384100000001-part1 254:7 0 4G 0 part �� md0 9:0 0 4G 0 raid1 [SWAP] �� eui.343339304e4016630025384100000001-part2 254:8 0 512M 0 part �� md1 9:1 0 511M 0 raid1 /boot �� eui.343339304e4016630025384100000001-part3 254:9 0 32G 0 part �� md2 9:2 0 32G 0 raid1 / �� eui.343339304e4016630025384100000001-part4 254:10 0 1K 0 part �� eui.343339304e4016630025384100000001-part5 254:11 0 1.7T 0 part �� md3 9:3 0 1.7T 0 raid1 /vmspace ��nvme1n1p1 259:7 0 4G 0 part ��nvme1n1p2 259:8 0 512M 0 part ��nvme1n1p3 259:9 0 32G 0 part ��nvme1n1p4 259:10 0 1K 0 part ��nvme1n1p5 259:11 0 1.7T 0 part # smartctl -a /dev/nvme0 smartctl 7.0 2019-05-21 r4917 [x86_64-linux-5.9.10-4.g9a304fa-default] (SUSE RPM) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: SAMSUNG MZQLB1T9HAJR-00007 Serial Number: S439NA0N401676 Firmware Version: EDA5402Q PCI Vendor/Subsystem ID: 0x144d IEEE OUI Identifier: 0x002538 Total NVM Capacity: 1,920,383,410,176 [1.92 TB] Unallocated NVM Capacity: 0 Controller ID: 4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 1,920,383,410,176 [1.92 TB] Namespace 1 Utilization: 331,079,852,032 [331 GB] Namespace 1 Formatted LBA Size: 512 Local Time is: Tue Nov 24 15:16:44 2020 CET Firmware Updates (0x17): 3 Slots, Slot 1 R/O, no Reset required Optional Admin Commands (0x000f): Security Format Frmw_DL NS_Mngmt Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Maximum Data Transfer Size: 512 Pages Warning Comp. Temp. Threshold: 87 Celsius Critical Comp. Temp. Threshold: 88 Celsius Namespace 1 Features (0x02): NA_Fields Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 10.60W - - 0 0 0 0 0 0 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 1 - 4096 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 44 Celsius Available Spare: 100% Available Spare Threshold: 10% Percentage Used: 0% Data Units Read: 44,400,602 [22.7 TB] Data Units Written: 6,856,956 [3.51 TB] Host Read Commands: 3,141,932,778 Host Write Commands: 1,154,625,326 Controller Busy Time: 816 Power Cycles: 7 Power On Hours: 716 Unsafe Shutdowns: 1 Media and Data Integrity Errors: 0 Error Information Log Entries: 0 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Temperature Sensor 1: 44 Celsius Temperature Sensor 2: 48 Celsius Temperature Sensor 3: 54 Celsius Error Information (NVMe Log 0x01, max 64 entries) No Errors Logged # smartctl -a /dev/nvme1 smartctl 7.0 2019-05-21 r4917 [x86_64-linux-5.9.10-4.g9a304fa-default] (SUSE RPM) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: SAMSUNG MZQLB1T9HAJR-00007 Serial Number: S439NA0N401663 Firmware Version: EDA5402Q PCI Vendor/Subsystem ID: 0x144d IEEE OUI Identifier: 0x002538 Total NVM Capacity: 1,920,383,410,176 [1.92 TB] Unallocated NVM Capacity: 0 Controller ID: 4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 1,920,383,410,176 [1.92 TB] Namespace 1 Utilization: 403,220,099,072 [403 GB] Namespace 1 Formatted LBA Size: 512 Local Time is: Tue Nov 24 15:16:46 2020 CET Firmware Updates (0x17): 3 Slots, Slot 1 R/O, no Reset required Optional Admin Commands (0x000f): Security Format Frmw_DL NS_Mngmt Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Maximum Data Transfer Size: 512 Pages Warning Comp. Temp. Threshold: 87 Celsius Critical Comp. Temp. Threshold: 88 Celsius Namespace 1 Features (0x02): NA_Fields Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 10.60W - - 0 0 0 0 0 0 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 1 - 4096 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 45 Celsius Available Spare: 100% Available Spare Threshold: 10% Percentage Used: 0% Data Units Read: 28,870,758 [14.7 TB] Data Units Written: 22,271,845 [11.4 TB] Host Read Commands: 3,072,172,886 Host Write Commands: 1,195,861,023 Controller Busy Time: 809 Power Cycles: 7 Power On Hours: 716 Unsafe Shutdowns: 1 Media and Data Integrity Errors: 0 Error Information Log Entries: 0 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Temperature Sensor 1: 45 Celsius Temperature Sensor 2: 49 Celsius Temperature Sensor 3: 55 Celsius Error Information (NVMe Log 0x01, max 64 entries) No Errors Logged what i've tried to solve the Problem. kernel Parameters iommu=soft amd_iommu=off Did not change anything. update Kernel to Latest Kernel on buildservice. # uname -r 5.9.10-4.g9a304fa-default Did also not change anything. For now I've disabled fstrim.timer to avoid furter crashes but that seems not the right way to solve the Problem. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[kernel-bugs] [Bug 1178474] [i915] Display freezes for up to tens of seconds with kernel 5.9
by bugzilla_noreply＠suse.com 25 Nov '20

25 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178474 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Display freezes for up to |[i915] Display freezes for |tens of seconds with kernel |up to tens of seconds with |5.9 |kernel 5.9 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1179092] [i915] Screen occasionally goes blank, sometimes staying that way until I press a key
by bugzilla_noreply＠suse.com 25 Nov '20

25 Nov '20

1 0

[kernel-bugs] [Bug 1178639] [nouveau] The plasma login screen freezes on kernel 5.9.1 and later
by bugzilla_noreply＠suse.com 25 Nov '20

25 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178639 https://bugzilla.suse.com/show_bug.cgi?id=1178639#c20 --- Comment #20 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #19) > Can you ssh into the machine and obtain dmesg output? Or set up kdump and provoke crash using sysrq-c? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1178639] [nouveau] The plasma login screen freezes on kernel 5.9.1 and later
by bugzilla_noreply＠suse.com 25 Nov '20

25 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178639 https://bugzilla.suse.com/show_bug.cgi?id=1178639#c19 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #19 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Pawel from comment #8) > kernel-default-5.10.rc3-1.1.ge72caa5.x86_64 = things are even worse here. > After installing and restarting the computer, the system loading screen does > not show (the one with a circle and the word "tumbleweed"), just a black > screen. I am also unable to access the virtual console. The computer itself > does not freeze Can you ssh into the machine and obtain dmesg output? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1178639] [nouveau] The plasma login screen freezes on kernel 5.9.1 and later
by bugzilla_noreply＠suse.com 25 Nov '20

25 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178639 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|The plasma login screen |[nouveau] The plasma login |freezes on kernel 5.9.1-1 |screen freezes on kernel | |5.9.1 and later -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1178639] The plasma login screen freezes on kernel 5.9.1-1
by bugzilla_noreply＠suse.com 25 Nov '20

25 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178639 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #843475|text/x-log |text/plain mime type| | -- You are receiving this mail because: You are the assignee for the bug.

1 0