July 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1201384] New: less does not start on serial port
by bugzilla_noreply＠suse.com 17 Jan '23

17 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1201384 Bug ID: 1201384 Summary: less does not start on serial port Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- strace less mmc0.txt execve("/usr/bin/less", ["less", "mmc0.txt"], 0xffffcc58c1a8 /* 51 vars */) = 0 brk(NULL) = 0xaaaaf2288000 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffff8b72a000 faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=20583, ...}, AT_EMPTY_PATH) = 0 mmap(NULL, 20583, PROT_READ, MAP_PRIVATE, 3, 0) = 0xffff8b724000 close(3) = 0 openat(AT_FDCWD, "/lib64/libtinfo.so.6", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832 newfstatat(3, "", {st_mode=S_IFREG|0755, st_size=231504, ...}, AT_EMPTY_PATH) = 0 mmap(NULL, 360832, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffff8b698000 mmap(0xffff8b6a0000, 295296, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0xffff8b6a0000 munmap(0xffff8b698000, 32768) = 0 munmap(0xffff8b6e9000, 29056) = 0 mprotect(0xffff8b6c9000, 90112, PROT_NONE) = 0 mmap(0xffff8b6df000, 40960, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2f000) = 0xffff8b6df000 close(3) = 0 openat(AT_FDCWD, "/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0\220\264\2\0\0\0\0\0"..., 832) = 832 pread64(3, "\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\305\350$SK\4\324\342\230\240\317b\vA3\260"..., 68, 768) = 68 newfstatat(3, "", {st_mode=S_IFREG|0755, st_size=2118080, ...}, AT_EMPTY_PATH) = 0 mmap(NULL, 1895216, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffff8b4d1000 mmap(0xffff8b4e0000, 1829680, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0xffff8b4e0000 munmap(0xffff8b4d1000, 61440) = 0 munmap(0xffff8b69f000, 2864) = 0 mprotect(0xffff8b673000, 106496, PROT_NONE) = 0 mmap(0xffff8b68d000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x19d000) = 0xffff8b68d000 mmap(0xffff8b693000, 47920, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xffff8b693000 close(3) = 0 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffff8b722000 set_tid_address(0xffff8b7220f0) = 6076 set_robust_list(0xffff8b722100, 24) = 0 rseq(0xffff8b7227c0, 0x20, 0, 0xd428bc00) = 0 mprotect(0xffff8b68d000, 12288, PROT_READ) = 0 mprotect(0xffff8b6df000, 4096, PROT_READ) = 0 mprotect(0xaaaabe98f000, 4096, PROT_READ) = 0 mprotect(0xffff8b72f000, 8192, PROT_READ) = 0 prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0 munmap(0xffff8b724000, 20583) = 0 ioctl(1, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 getrandom("\x63\x32\x32\x25\xf1\x9e\x1e\x9a", 8, GRND_NONBLOCK) = 8 brk(NULL) = 0xaaaaf2288000 brk(0xaaaaf22a9000) = 0xaaaaf22a9000 openat(AT_FDCWD, "/usr/bin/.sysless", O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/etc/syslesskey", O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/etc/sysless", O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/root/.lesskey", O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/etc/lesskey.bin", O_RDONLY) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=589, ...}, AT_EMPTY_PATH) = 0 lseek(3, 0, SEEK_SET) = 0 read(3, "\0M+Gc\33\2\33[A\0\2\33[B\0\f\33O5A\0\2\33O5B\0\f\33O5"..., 589) = 589 close(3) = 0 ioctl(1, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 getuid() = 0 geteuid() = 0 getgid() = 0 getegid() = 0 getuid() = 0 newfstatat(AT_FDCWD, "/etc/terminfo", {st_mode=S_IFDIR|0755, st_size=4096, ...}, 0) = 0 newfstatat(AT_FDCWD, "/usr/share/terminfo", {st_mode=S_IFDIR|0755, st_size=4096, ...}, 0) = 0 faccessat(AT_FDCWD, "/etc/terminfo/s/screen", R_OK) = -1 ENOENT (No such file or directory) faccessat(AT_FDCWD, "/usr/share/terminfo/s/screen", R_OK) = 0 openat(AT_FDCWD, "/usr/share/terminfo/s/screen", O_RDONLY) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=1607, ...}, AT_EMPTY_PATH) = 0 read(3, "\32\0011\0+\0\20\0i\1\265\2screen|VT 100/ANSI X"..., 32768) = 1607 read(3, "", 28672) = 0 close(3) = 0 ioctl(1, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 ioctl(1, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 ioctl(1, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 ioctl(1, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 ioctl(1, TIOCGWINSZ, {ws_row=41, ws_col=157, ws_xpixel=0, ws_ypixel=0}) = 0 ioctl(2, TIOCGWINSZ, {ws_row=41, ws_col=157, ws_xpixel=0, ws_ypixel=0}) = 0 openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=2940, ...}, AT_EMPTY_PATH) = 0 read(3, "# Locale name alias data base.\n#"..., 4096) = 2940 read(3, "", 4096) = 0 close(3) = 0 openat(AT_FDCWD, "/usr/lib/locale/en_US.UTF-8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/locale/en_US.utf8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=353616, ...}, AT_EMPTY_PATH) = 0 mmap(NULL, 353616, PROT_READ, MAP_PRIVATE, 3, 0) = 0xffff8b489000 close(3) = 0 openat(AT_FDCWD, "/usr/lib64/gconv/gconv-modules.cache", O_RDONLY) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=26988, ...}, AT_EMPTY_PATH) = 0 mmap(NULL, 26988, PROT_READ, MAP_SHARED, 3, 0) = 0xffff8b71b000 close(3) = 0 futex(0xffff8b69236c, FUTEX_WAKE_PRIVATE, 2147483647) = 0 openat(AT_FDCWD, "/root/.lesshst", O_RDONLY) = 3 close(3) = 0 openat(AT_FDCWD, "/root/.lesshst", O_RDONLY) = 3 newfstatat(3, "", {st_mode=S_IFREG|0600, st_size=20, ...}, AT_EMPTY_PATH) = 0 read(3, ".less-history-file:\n", 4096) = 20 read(3, "", 4096) = 0 close(3) = 0 getcwd("/root", 1024) = 6 readlinkat(AT_FDCWD, "/root/mmc0.txt", 0xfffff3f0b0f0, 1023) = -1 EINVAL (Invalid argument) getcwd("/root", 1024) = 6 readlinkat(AT_FDCWD, "/root/mmc0.txt", 0xfffff3f0b0f0, 1023) = -1 EINVAL (Invalid argument) ioctl(2, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 ioctl(2, TCGETS, {B1500000 opost isig icanon echo ...}) = 0 newfstatat(2, "", {st_mode=S_IFCHR|0620, st_rdev=makedev(0x4, 0x42), ...}, AT_EMPTY_PATH) = 0 readlinkat(AT_FDCWD, "/proc/self/fd/2", "/dev/ttyS2", 4095) = 10 newfstatat(AT_FDCWD, "/dev/ttyS2", {st_mode=S_IFCHR|0620, st_rdev=makedev(0x4, 0x42), ...}, 0) = 0 openat(AT_FDCWD, "/dev/ttyS2", O_RDONLY cat /proc/6076/stack [<0>] tty_port_block_til_ready+0x124/0x344 [<0>] tty_port_open+0xc8/0x26c [<0>] uart_open+0x28/0x40 [<0>] tty_open+0x140/0x670 [<0>] chrdev_open+0xcc/0x21c [<0>] do_dentry_open+0x1c0/0x38c [<0>] vfs_open+0x38/0x44 [<0>] path_openat+0xa50/0x108c [<0>] do_filp_open+0x8c/0x140 [<0>] do_sys_openat2+0xbc/0x174 [<0>] __arm64_sys_openat+0x70/0xb0 [<0>] invoke_syscall+0x78/0x100 [<0>] el0_svc_common.constprop.0+0x18c/0x190 [<0>] do_el0_svc+0x30/0x90 [<0>] el0_svc+0x34/0x130 [<0>] el0t_64_sync_handler+0x10c/0x140 [<0>] el0t_64_sync+0x1a0/0x1a4 Linux PinebookPro 5.18.9-1-default #1 SMP PREEMPT_DYNAMIC Sun Jul 3 08:04:03 UTC 2022 (0e67dc1) aarch64 aarch64 aarch64 GNU/Linux -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1196778] New: amdgpu bug
by bugzilla_noreply＠suse.com 15 Jan '23

15 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1196778 Bug ID: 1196778 Summary: amdgpu bug Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: james(a)sevener.us QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When plugging my laptop (Lenovo E14 Gen3, Ryzen 5500U) amdgpu spams the journal, and I can no longer run two screens at 2560x1440. This started on 2/15/2022 after updating. I have been able to get both screens working now, but I have to run one at 1080p and one at 1440p. It used to work great with both at 1440p. In the one log file (it's rolled a few times) I got the following which seems to show once per error. grep -c drivers/gpu/drm/drm_dp_mst_topology.c messages 177772 Full error: 2022-02-18T09:08:02.625936-05:00 localhost kernel: [ 91.051548][ T5215] ------------[ cut here ]------------ 2022-02-18T09:08:02.625954-05:00 localhost kernel: [ 91.051554][ T5215] WARNING: CPU: 10 PID: 5215 at drivers/gpu/drm/drm_dp_mst_topology.c:4404 drm_dp_atomic_find_vcpi_slots.cold+0x0/0x24 2022-02-18T09:08:02.625958-05:00 localhost kernel: [ 91.051567][ T5215] Modules linked in: rfcomm xt_CHECKSUM xt_conntrack ipt_REJECT xt_tcpudp nf_nat_tftp nf_conntrack_tftp bridge stp llc xt_mark xt_MASQUERADE xt_comment tun nft_objref af_packet nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_tables 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 ip_set nfnetlink snd_usb_audio snd_usbmidi_lib ebtable_filter snd_rawmidi snd_seq_device ebtables ip6table_filter ip6_tables iptable_filter bpfilter cmac algif_hash algif_skcipher af_alg bnep dmi_sysfs r8153_ecm cdc_ether usbnet r8152 mii btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ecdh_generic mc intel_rapl_msr intel_rapl_common edac_mce_amd 2022-02-18T09:08:02.625960-05:00 localhost kernel: [ 91.051650][ T5215] kvm_amd kvm irqbypass snd_ctl_led snd_hda_codec_realtek pcspkr snd_hda_codec_generic snd_hda_codec_hdmi joydev snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_pci_acp6x r8169 snd_hwdep thinkpad_acpi snd_pcm snd_pci_acp5x realtek mdio_devres think_lmi snd_rn_pci_acp3x ledtrig_audio efi_pstore firmware_attributes_class wmi_bmof k10temp snd_timer i2c_piix4 snd_pci_acp3x libphy platform_profile snd soundcore tiny_power_button ac ucsi_acpi i2c_scmi typec_ucsi typec roles acpi_cpufreq button nls_iso8859_1 nls_cp437 vfat fat fuse configfs ip_tables x_tables dm_crypt essiv authenc trusted asn1_encoder tee hid_logitech_hidpp hid_logitech_dj hid_generic usbhid rtw89pci(OE) rtw89core(OE) amdgpu crct10dif_pclmul crc32_pclmul ghash_clmulni_intel mac80211 libarc4 xhci_pci xhci_pci_renesas cfg80211 xhci_hcd aesni_intel crypto_simd cryptd usbcore drm_ttm_helper nvme ttm serio_raw ccp iommu_v2 nvme_core sp5100_tco gpu_sched rfkill wmi battery 2022-02-18T09:08:02.625962-05:00 localhost kernel: [ 91.051742][ T5215] video btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs 2022-02-18T09:08:02.625964-05:00 localhost kernel: [ 91.051759][ T5215] CPU: 10 PID: 5215 Comm: kwin_wayland Tainted: G OE 5.16.8-1-default #1 openSUSE Tumbleweed 257f8f36371552cd38032922fd021edb6811ecdc 2022-02-18T09:08:02.625967-05:00 localhost kernel: [ 91.051766][ T5215] Hardware name: LENOVO 20Y7003EUS/20Y7003EUS, BIOS R1OET31W (1.10 ) 11/29/2021 2022-02-18T09:08:02.625968-05:00 localhost kernel: [ 91.051770][ T5215] RIP: 0010:drm_dp_atomic_find_vcpi_slots.cold+0x0/0x24 2022-02-18T09:08:02.625970-05:00 localhost kernel: [ 91.051776][ T5215] Code: 28 ea 57 a4 e8 a4 7c fe ff 49 8b 45 58 48 89 ea 48 c7 c6 70 88 90 a4 48 8b 78 08 e8 78 14 00 00 b8 f4 ff ff ff e9 55 fc c5 ff <0f> 0b 49 8b 46 58 4c 89 e2 48 c7 c6 a0 88 90 a4 41 bf ea ff ff ff 2022-02-18T09:08:02.625972-05:00 localhost kernel: [ 91.051779][ T5215] RSP: 0018:ffffc35b81daf790 EFLAGS: 00010246 2022-02-18T09:08:02.625973-05:00 localhost kernel: [ 91.051783][ T5215] RAX: ffff9f65d94afd98 RBX: ffff9f65d94afd80 RCX: 0000000000000000 2022-02-18T09:08:02.625974-05:00 localhost kernel: [ 91.051786][ T5215] RDX: ffff9f65d94afcc0 RSI: ffff9f661018a500 RDI: ffff9f6660a7d580 2022-02-18T09:08:02.625976-05:00 localhost kernel: [ 91.051788][ T5215] RBP: ffff9f65d94af508 R08: 0000000000000013 R09: ffffc35b81daf8a8 2022-02-18T09:08:02.625977-05:00 localhost kernel: [ 91.051790][ T5215] R10: 00000000000001b5 R11: 0000000000000000 R12: ffff9f65d3d8b800 2022-02-18T09:08:02.625979-05:00 localhost kernel: [ 91.051792][ T5215] R13: ffff9f65d94af500 R14: ffff9f661018a500 R15: 0000000000000013 2022-02-18T09:08:02.625980-05:00 localhost kernel: [ 91.051794][ T5215] FS: 00007fa96d006e40(0000) GS:ffff9f6860080000(0000) knlGS:0000000000000000 2022-02-18T09:08:02.625981-05:00 localhost kernel: [ 91.051798][ T5215] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2022-02-18T09:08:02.625982-05:00 localhost kernel: [ 91.051800][ T5215] CR2: 00007fa95c50d0e0 CR3: 000000014a278000 CR4: 0000000000350ee0 2022-02-18T09:08:02.626005-05:00 localhost kernel: [ 91.051803][ T5215] Call Trace: 2022-02-18T09:08:02.626007-05:00 localhost kernel: [ 91.051806][ T5215] <TASK> 2022-02-18T09:08:02.626008-05:00 localhost kernel: [ 91.051812][ T5215] ? dc_link_should_enable_fec+0x3d/0x60 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630215-05:00 localhost kernel: [ 91.052250][ T5215] compute_mst_dsc_configs_for_link+0x7dd/0xa20 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630227-05:00 localhost kernel: [ 91.052432][ T5215] compute_mst_dsc_configs_for_state+0x1eb/0x340 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630230-05:00 localhost kernel: [ 91.052605][ T5215] amdgpu_dm_atomic_check+0xce4/0xf00 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630232-05:00 localhost kernel: [ 91.052777][ T5215] drm_atomic_check_only+0x595/0x8d0 2022-02-18T09:08:02.630234-05:00 localhost kernel: [ 91.052781][ T5215] drm_mode_atomic_ioctl+0x73c/0xaf0 2022-02-18T09:08:02.630236-05:00 localhost kernel: [ 91.052784][ T5215] ? drm_plane_get_damage_clips.cold+0x1c/0x1c 2022-02-18T09:08:02.630237-05:00 localhost kernel: [ 91.052788][ T5215] ? drm_atomic_set_property+0xb50/0xb50 2022-02-18T09:08:02.630238-05:00 localhost kernel: [ 91.052789][ T5215] drm_ioctl_kernel+0xb0/0x140 2022-02-18T09:08:02.630239-05:00 localhost kernel: [ 91.052794][ T5215] drm_ioctl+0x220/0x3e0 2022-02-18T09:08:02.630241-05:00 localhost kernel: [ 91.052796][ T5215] ? drm_atomic_set_property+0xb50/0xb50 2022-02-18T09:08:02.630243-05:00 localhost kernel: [ 91.052797][ T5215] ? amdgpu_drm_ioctl+0x6a/0x80 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630246-05:00 localhost kernel: [ 91.052938][ T5215] amdgpu_drm_ioctl+0x49/0x80 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630247-05:00 localhost kernel: [ 91.053078][ T5215] __x64_sys_ioctl+0x82/0xb0 2022-02-18T09:08:02.630249-05:00 localhost kernel: [ 91.053081][ T5215] do_syscall_64+0x5c/0x80 2022-02-18T09:08:02.630250-05:00 localhost kernel: [ 91.053084][ T5215] ? __x64_sys_ioctl+0x9a/0xb0 2022-02-18T09:08:02.630251-05:00 localhost kernel: [ 91.053085][ T5215] ? syscall_exit_to_user_mode+0x18/0x40 2022-02-18T09:08:02.630252-05:00 localhost kernel: [ 91.053088][ T5215] ? do_syscall_64+0x69/0x80 2022-02-18T09:08:02.630254-05:00 localhost kernel: [ 91.053089][ T5215] ? do_syscall_64+0x69/0x80 2022-02-18T09:08:02.630265-05:00 localhost kernel: [ 91.053091][ T5215] ? do_syscall_64+0x69/0x80 2022-02-18T09:08:02.630267-05:00 localhost kernel: [ 91.053092][ T5215] ? exc_page_fault+0x68/0x150 2022-02-18T09:08:02.630268-05:00 localhost kernel: [ 91.053094][ T5215] entry_SYSCALL_64_after_hwframe+0x44/0xae 2022-02-18T09:08:02.630270-05:00 localhost kernel: [ 91.053097][ T5215] RIP: 0033:0x7fa96f8a688b 2022-02-18T09:08:02.630272-05:00 localhost kernel: [ 91.053099][ T5215] Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5d 75 0f 00 f7 d8 64 89 01 48 2022-02-18T09:08:02.630274-05:00 localhost kernel: [ 91.053101][ T5215] RSP: 002b:00007ffc93f8fbb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 2022-02-18T09:08:02.630275-05:00 localhost kernel: [ 91.053103][ T5215] RAX: ffffffffffffffda RBX: 00007ffc93f8fc00 RCX: 00007fa96f8a688b 2022-02-18T09:08:02.630277-05:00 localhost kernel: [ 91.053104][ T5215] RDX: 00007ffc93f8fc00 RSI: 00000000c03864bc RDI: 0000000000000013 2022-02-18T09:08:02.630278-05:00 localhost kernel: [ 91.053105][ T5215] RBP: 00000000c03864bc R08: 0000000000000000 R09: 0000000000000000 2022-02-18T09:08:02.630279-05:00 localhost kernel: [ 91.053106][ T5215] R10: 000000000000000d R11: 0000000000000246 R12: 000055c2e2d4dbf0 2022-02-18T09:08:02.630281-05:00 localhost kernel: [ 91.053106][ T5215] R13: 0000000000000013 R14: 000055c2e2d87840 R15: 000055c2e2d201f0 2022-02-18T09:08:02.630282-05:00 localhost kernel: [ 91.053108][ T5215] </TASK> 2022-02-18T09:08:02.630283-05:00 localhost kernel: [ 91.053109][ T5215] ---[ end trace dd8544f5a3a3564e ]--- 2022-02-18T09:08:02.630285-05:00 localhost kernel: [ 91.053111][ T5215] amdgpu 0000:04:00.0: [drm] *ERROR* cannot allocate and release VCPI on [MST PORT:00000000224748f2] in the same state The error I'm seeing now from journalctl -f -g amdgpu is: amdgpu 0000:05:00.0: [drm] *ERROR* cannot allocate and release VCPI on [MST PORT:0000000050490ba5] in the same state Mar 04 12:18:28 localhost.localdomain kernel: snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi think_lmi wmi_bmof firmware_at> Mar 04 12:18:28 localhost.localdomain kernel: ? dc_link_should_enable_fec+0x3d/0x60 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] Mar 04 12:18:28 localhost.localdomain kernel: compute_mst_dsc_configs_for_link+0x949/0xa20 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] Mar 04 12:18:28 localhost.localdomain kernel: compute_mst_dsc_configs_for_state+0x1eb/0x340 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] Mar 04 12:18:28 localhost.localdomain kernel: amdgpu_dm_atomic_check+0xce4/0xf00 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] Mar 04 12:18:28 localhost.localdomain kernel: amdgpu_drm_ioctl+0x49/0x80 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1200461] New: Dracut locks computer, fails to generate initrd file
by bugzilla_noreply＠suse.com 21 Dec '22

21 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200461 Bug ID: 1200461 Summary: Dracut locks computer, fails to generate initrd file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mfdemicco(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859545 --> http://bugzilla.opensuse.org/attachment.cgi?id=859545&action=edit Photo of screen at moment of freeze When I update to kernel 5.18.1-1 or 5.18.2.1, Dracut locks up my system requiring a power button reboot when creating the initrd file. I also tried installing the latest version of Tumbleweed to another partition, and the installation locked up the computer about 50% into the installation with no creation of the initrd file. The computer freezes at: Dracut: *** Including module: kernel-modules *** When I look in my /boot folder, everything for the kernel is created except for the initrd file I've done a search and can't find anyone that has the same problem. The system runs file with the older kernel 5.17.4-1. I have a legacy BIOS system. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1188954] New: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1
by bugzilla_noreply＠suse.com 21 Dec '22

21 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188954 Bug ID: 1188954 Summary: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1 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: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: sndirsch(a)suse.com Found By: --- Blocker: --- Created attachment 851460 --> http://bugzilla.opensuse.org/attachment.cgi?id=851460&action=edit Xorg.0.log and dmesg Initial summary: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1 To reproduce: 1-boot with included on kernel cmdline radeon.cik_support=0 amdgpu.cik_support=1 2-wait for X to fail to start 3-login on a tty 4-systemctl restart xdm Actual behavior: 1-X fails to start, finding no /dev/dri/card0, leaving login prompt on tty1 on display screen 2-X starts normally using amdgpu DDX driver Expected behavior: 1-X starts normally using amdgpu DDX driver Tested with kernels 5.12.13, 5.11.16, 5.7.11 # inxi -SGIay System: Host: asa88 Kernel: 5.12.13-1-default x86_64 bits: 64 compiler: gcc v: 11.1.1 parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=tvgp07stw noresume ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 radeon.cik_support=0 amdgpu.cik_support=1 video=1024x768@60 video=1440x900@60 drm.debug=0x1e log_buf_len=1M Console: tty pts/0 DM: TDM Distro: openSUSE Tumbleweed 20210730 Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASUSTeK driver: amdgpu v: kernel alternate: radeon bus-ID: 00:01.0 chip-ID: 1002:130f class-ID: 0300 Display: server: X.org 1.20.12 driver: loaded: vesa unloaded: fbdev,modesetting alternate: ati Message: Advanced graphics data unavailable for root. Info:...inxi: 3.3.06 Comments: 1-without radeon.cik_support=0 amdgpu.cik_support=1 on cmdline, X cannot be coaxed into using amdgpu DDX driver via /etc/X11/xorg.conf.d/*conf 2-without radeon.cik_support=0 amdgpu.cik_support=1, greeter startup completes (normally, on first try) using modesetting DIX driver -- You are receiving this mail because: You are the assignee for the bug.

1 26

[Bug 1191244] New: USB speaker working when plugged while system is up but not on reboot
by bugzilla_noreply＠suse.com 19 Dec '22

19 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191244 Bug ID: 1191244 Summary: USB speaker working when plugged while system is up but not on reboot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: aarch64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: peter.stark(a)storck.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have multiple raspberry PI 4Bs with openSUSE Leap 15.3 and some with raspbian 9. I got a USB speaker (e2b7:0811) which I connected to the 4Bs using Leap 15.3. This speaker works fine when I plug it in when the PI is already running: rpi15:~ # uname -a Linux rpi15 5.3.18-59.24-default #1 SMP Mon Sep 13 15:06:42 UTC 2021 (2f872ea) aarch64 aarch64 aarch64 GNU/Linux rpi15:~ # lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 03eb:2013 Atmel Corp. iAQ Stick Bus 001 Device 007: ID e2b7:0811 Jie Li CD002 Bus 001 Device 003: ID 044f:b351 ThrustMaster, Inc. F16 MFD 1 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rpi15:~ # dmesg -T|grep 1-1.2 [Sa Okt 2 10:56:09 2021] usb 1-1.2: USB disconnect, device number 4 [Sa Okt 2 10:56:17 2021] usb 1-1.2: new full-speed USB device number 6 using xhci_hcd [Sa Okt 2 10:56:17 2021] usb 1-1.2: device descriptor read/64, error -32 [Sa Okt 2 10:56:17 2021] usb 1-1.2: device descriptor read/64, error -32 [Sa Okt 2 10:56:17 2021] usb 1-1.2: new full-speed USB device number 7 using xhci_hcd [Sa Okt 2 10:56:17 2021] usb 1-1.2: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:56:17 2021] usb 1-1.2: config 1 has no interface number 0 [Sa Okt 2 10:56:17 2021] usb 1-1.2: New USB device found, idVendor=e2b7, idProduct=0811, bcdDevice= 1.00 [Sa Okt 2 10:56:17 2021] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:56:17 2021] usb 1-1.2: Product: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: Manufacturer: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: SerialNumber: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: 9:1: bogus dB values (-12800/-12700), disabling dB reporting [Sa Okt 2 10:56:17 2021] input: CD002 CD002 as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.3/0003:E2B7:0811.0003/input/input1 However, after a reboot with the device still connected (no change) the kernel boots and does not even see the device. rpi15:~ # lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:2013 Atmel Corp. iAQ Stick Bus 001 Device 003: ID 044f:b351 ThrustMaster, Inc. F16 MFD 1 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rpi15:~ # dmesg -T|grep 1-1.2 rpi15:~ # I have tried the same USB speaker on another PI4B with Leap 15.3 with the same result. So, it doesn't seem to be that PI. When I connect the speaker to a PI3 with raspbian 9, it works as expected. root@rpi13:~# dmesg -T |grep 1-1.3 [Sa Okt 2 10:33:08 2021] usb 1-1.3: new full-speed USB device number 4 using dwc_otg [Sa Okt 2 10:33:08 2021] usb 1-1.3: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:33:08 2021] usb 1-1.3: config 1 has no interface number 0 [Sa Okt 2 10:33:08 2021] usb 1-1.3: New USB device found, idVendor=e2b7, idProduct=0811 [Sa Okt 2 10:33:08 2021] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:33:08 2021] usb 1-1.3: Product: CD002 [Sa Okt 2 10:33:08 2021] usb 1-1.3: Manufacturer: CD002 [Sa Okt 2 10:33:08 2021] usb 1-1.3: SerialNumber: CD002 [Sa Okt 2 10:33:08 2021] input: CD002 CD002 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.3/0003:E2B7:0811.0001/input/input0 [Sa Okt 2 10:42:57 2021] usb 1-1.3: reset full-speed USB device number 4 using dwc_otg [Sa Okt 2 10:42:58 2021] usb 1-1.3: USB disconnect, device number 4 [Sa Okt 2 10:42:58 2021] usb 1-1.3: 9:1: cannot get min/max values for control 2 (id 9) [Sa Okt 2 10:43:04 2021] usb 1-1.3: new full-speed USB device number 6 using dwc_otg [Sa Okt 2 10:43:04 2021] usb 1-1.3: device descriptor read/64, error -32 [Sa Okt 2 10:43:04 2021] usb 1-1.3: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:43:04 2021] usb 1-1.3: config 1 has no interface number 0 [Sa Okt 2 10:43:04 2021] usb 1-1.3: New USB device found, idVendor=e2b7, idProduct=0811 [Sa Okt 2 10:43:04 2021] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:43:04 2021] usb 1-1.3: Product: CD002 [Sa Okt 2 10:43:04 2021] usb 1-1.3: Manufacturer: CD002 [Sa Okt 2 10:43:04 2021] usb 1-1.3: SerialNumber: CD002 [Sa Okt 2 10:43:04 2021] input: CD002 CD002 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.3/0003:E2B7:0811.0002/input/input1 I noticed that the raspbian uses dwc_otg vs. xhci_hcd on Leap. However, dwc_otg doesn't seem to be a separate module in raspbian nor it is available on leap. As the speaker is working when I un-plug and plug it in again, I wonder what may causes this strange behavior. Especially as I do not see the device via lsusb after reboot, though it is still connected. Any ideas on how to fix it? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1201963] New: 11th Gen Intel(R) Core(TM) i5-1145G7 throttling to 400MHz from 70°C until it reaches 54°C
by bugzilla_noreply＠suse.com 16 Dec '22

16 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1201963 Bug ID: 1201963 Summary: 11th Gen Intel(R) Core(TM) i5-1145G7 throttling to 400MHz from 70�C until it reaches 54�C 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: gryffus(a)hkfree.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 860458 --> https://bugzilla.suse.com/attachment.cgi?id=860458&action=edit Turbostat log output I have a Dell Latitude 5420 laptop and i am experiencing CPU slowdown when using any graphical / CPU demanding application. The laptop contains 11th Gen Intel(R) Core(TM) i5-1145G7 which can do 4,4GHz on turbo. When the system reaches about 70�C, all cores switch to 400MHz and stay there until temperature hits 53-54�C. I can see this behavior especially in Vulkan graphics applications, but not only in them, it just happens almost instantly there, since the 70�C is reached within about 30 seconds there. I would want to raise the temperature limits to at least 80-90�C or disable throttling completely (at my own responsibility of cooking it). But throttling from 70�C seems as a complete nonsense to me - the CPU package gets to this temperature in 10-20 seconds under load, so i basically never make use of the 4,4GHz. What i have tried: 1) Kernel 5.19 from Kernel:HEAD - no change 2) installed throttled ( https://github.com/erpalma/throttled ) - no change 3) blacklisted intel_powerclamp, intel_rapl_msr, processor_thermal_rapl, intel_rapl_common kernel modules - no change 4) cpupower frequency-set -g performance - no change # cat /sys/devices/platform/*/uuids/current_uuid INVALID # cat /sys/devices/platform/*/uuids/available_uuids UNKNOWN # cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.40 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 4.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 3.16 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes # cpupower idle-info CPUidle driver: intel_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 4 Available idle states: POLL C1_ACPI C2_ACPI C3_ACPI POLL: Flags/Description: CPUIDLE CORE POLL IDLE Latency: 0 Usage: 265266 Duration: 8068126 C1_ACPI: Flags/Description: ACPI FFH MWAIT 0x0 Latency: 1 Usage: 10617293 Duration: 1984558460 C2_ACPI: Flags/Description: ACPI FFH MWAIT 0x31 Latency: 253 Usage: 273458 Duration: 261649941 C3_ACPI: Flags/Description: ACPI FFH MWAIT 0x60 Latency: 1048 Usage: 206150 Duration: 509227956 # cpupower info analyzing CPU 0: perf-bias: 0 Turbostat debug log attached. Some further reading with probably related reports: https://www.dell.com/community/Latitude/Latitude-5420-7420-7520-CPU-Throttl… https://github.com/intel/thermal_daemon/issues/341 https://github.com/intel/thermal_daemon/issues/293 https://github.com/erpalma/throttled Any clues? -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1189946] New: [trackerbug] Ancient patch cleanup
by bugzilla_noreply＠suse.com 09 Dec '22

09 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1189946 Bug ID: 1189946 Summary: [trackerbug] Ancient patch cleanup 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: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jeffm(a)suse.com, mkubecek(a)suse.com Found By: --- Blocker: --- This is the tracker bug for cleaning up old patches in the master branch. -- You are receiving this mail because: You are the assignee for the bug.

1 27

[Bug 1193599] New: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193599 Bug ID: 1193599 Summary: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following errors appear at boot broken atomic modeset userspace detected, disabling atomic [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D Full log https://paste.opensuse.org/83436185 Hardware Dell Precision 7530 CPU: Intel Xeon E-2186M GPU: Intel P630 / Nvidia Quadro P3200 -- You are receiving this mail because: You are the assignee for the bug.

1 33

[Bug 1191933] New: Kernel can not update on Secure boot envirnment
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191933 Bug ID: 1191933 Summary: Kernel can not update on Secure boot envirnment 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: kokeko(a)mac.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Current 20211012, update to 20211016 or 20211019. Kernel-default update failed by fallowing error. subprocess error, secure boot enabled. Is it something change? -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1200781] New: xhci stop working. Works briefly after reboot, or remove and load xhci_pci & xhci_hcd.
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200781 Bug ID: 1200781 Summary: xhci stop working. Works briefly after reboot, or remove and load xhci_pci & xhci_hcd. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: publio.escipion.el.africano(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSuSE Leap 15.4 x86_64, kernel 4.14.21-150400.22-default, in a Lenovo IdeaPad 3 15ADA05: https://psref.lenovo.com/syspool/Sys/PDF/IdeaPad/IdeaPad_3_15ADA05/IdeaPad_… An external mouse stops working after a brief period of time, after login into KDE, or after removing and loading xhci_pci & xhci_hcd. System complaints of: �xhci_hcd 0000:02:00.3 WARNIGN: Host System Error� and: �usb 2-3: device not accepting address 2, error -108� I've tried two bluetooth mice, and a standard cord mouse. The same result. It seems that it's the USB controllers are the only components affected, so far. Mousepad works properly, but I'm not use to it. I have to constantly remove and load xhci_pci & xhci_hcd, as root. rmmod xhci_pci rmmod xhci_hcd modprobe xhci_pci modprobe xhci_hcd Mouse works after that for a short time. Nota bene: Devices work properly under openSuSE Leap 15.2 x86_64, kernel 5.3.18-lp152.106-default (old HP Pavillion). This bug resembles https://bugzilla.opensuse.org/show_bug.cgi?id=1193652 -- You are receiving this mail because: You are the assignee for the bug.

1 17

2023

2022

2021

2020

openSUSE Kernel Bugs July 2022