Bug#983034: plasma-workspace-wayland: hanging in ksplashqml
I agree with Norbert. Bugs like this which involve proprietary hardware are quite common and unlikely to get attention from those developers who could fix them. They often get fixed more by accident. If you want to increase the chances, this is what you could do: * Compile the most recent kernel and try to reproduce the bug with that. If you don't know how to do that you have to teach yourself how with one of the countless tutorials from the web. * Provide a simple reproducer: The bug is triggered by a program interacting with the kernel, presumably the wayland compositor. If you can come up with a sequence of steps that reliably trigger this bug from the console, this would help a lot. * Become better at providing good, succinct bug reports. Tutorials for this exist on the web, too. If you do all that in the end you might collect enough useful information that an upstream dev will actually consider looking at this. All of this will involve quite a bit of time, skill and work from your side, and we cannot really help you with that. If you need help you'll have to ask nicely on the debian-users mailing list or in one of the many Linux forums if someone could help you with that. Until then you'll have to stick with X11. Good luck.
Bug#983034: plasma-workspace-wayland: hanging in ksplashqml
> dmesg shows a crash in the nouveau driver: Well ... that is not something we can care for, so I suggest closing this bug. Best Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research Labs + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#983034: plasma-workspace-wayland: hanging in ksplashqml
Control: severity -1 normal Change severity - nothing we can really deal with > dmesg shows a crash in the nouveau driver: Best Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research Labs + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#983034: plasma-workspace-wayland: hanging in ksplashqml
On 19.02.21 19:40, Dennis Filder wrote: > Control: tag -1 + moreinfo bullseye sid > > If you cannot switch to console with Ctrl-Alt-F2 then this is a strong > indicator that the bug is in the kernel, probably nouveau. > > If you can reproduce this reliably it would help a lot if you could > provide the output of these commands after the bug has happened: > > dmesg > strace -f -p $(pidof ksplashqml) 2>&1 | dd bs=1k count=20 > journalctl -ab > > You may have to run some of them as root. > dmesg shows a crash in the nouveau driver: [ 441.529012] [ cut here ] [ 441.529076] WARNING: CPU: 1 PID: 1964 at drivers/gpu/drm/nouveau/nvif/vmm.c:68 nvif_vmm_put+0x84/0x9c [nouveau] [ 441.529078] Modules linked in: xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc rfkill overlay nls_ascii nls_cp437 vfat fat snd_hda_codec_hdmi aes_ce_blk crypto_simd snd_hda_intel cryptd snd_intel_dspcfg aes_ce_cipher snd_hda_codec ghash_ce gf128mul libaes sha2_ce snd_hda_core snd_hwdep snd_pcm sha256_arm64 sha1_ce snd_timer evdev snd soundcore sg efi_pstore omap_rng rng_core sbsa_gwdt armada_thermal fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod hid_generic usbhid hid sd_mod t10_pi crc_t10dif crct10dif_generic nouveau i2c_mux_pca954x i2c_mux ahci_platform libahci_platform libahci marvell10g libata crct10dif_ce [ 441.529194] crct10dif_common scsi_mod i2c_algo_bit ttm xhci_plat_hcd drm_kms_helper marvell xhci_hcd drm mvpp2 usbcore i2c_mv64xxx mvmdio mdio_devres sfp mdio_i2c phylink of_mdio phy_generic fixed_phy libphy sdhci_xenon_driver sdhci_pltfm usb_common phy_mvebu_cp110_comphy fixed sdhci [ 441.529236] CPU: 1 PID: 1964 Comm: kworker/1:0 Not tainted 5.10.0-3-arm64 #1 Debian 5.10.13-1 [ 441.529238] Hardware name: SolidRun Armada 8040 MacchiatoBin/Armada 8040 MacchiatoBin, BIOS EDK II Mar 26 2020 [ 441.529284] Workqueue: events nouveau_cli_work [nouveau] [ 441.529289] pstate: 6005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 441.529332] pc : nvif_vmm_put+0x84/0x9c [nouveau] [ 441.529375] lr : nvif_vmm_put+0x78/0x9c [nouveau] [ 441.529376] sp : 8000119cbc80 [ 441.529378] x29: 8000119cbc80 x28: · [ 441.529383] x27: 386ac5329f28 x26: 0001· [ 441.529387] x25: dead0100 x24: dead0122· [ 441.529391] x23: 386ac5329f18 x22: 386ac5077300· [ 441.529395] x21: 386ac5329f08 x20: 386ac2b00080· [ 441.529398] x19: 8000119cbce8 x18: · [ 441.529402] x17: x16: bbff1d518580· [ 441.529406] x15: x14: · [ 441.529410] x13: x12: 0040· [ 441.529414] x11: bbff1dcf5ec0 x10: 0ad0· [ 441.529417] x9 : bbfea5a3d3f0 x8 : fefefefefefefeff· [ 441.529421] x7 : 8888 x6 : 8000119cbcb8· [ 441.529425] x5 : x4 : 0008· [ 441.529429] x3 : 048a x2 : · [ 441.529433] x1 : x0 : fffe· [ 441.529437] Call trace: [ 441.529480] nvif_vmm_put+0x84/0x9c [nouveau] [ 441.529523] nouveau_vma_del+0x9c/0xe0 [nouveau] [ 441.529565] nouveau_gem_object_delete_work+0x48/0x80 [nouveau] [ 441.529607] nouveau_cli_work+0xe8/0x180 [nouveau] [ 441.529616] process_one_work+0x1d4/0x490 [ 441.529619] worker_thread+0x188/0x504 [ 441.529622] kthread+0x130/0x134 [ 441.529625] ret_from_fork+0x10/0x38 [ 441.529628] ---[ end trace 28675099a596659e ]--- :set nonumber Best regards Heinrich
Bug#983034: plasma-workspace-wayland: hanging in ksplashqml
Control: tag -1 + moreinfo bullseye sid If you cannot switch to console with Ctrl-Alt-F2 then this is a strong indicator that the bug is in the kernel, probably nouveau. If you can reproduce this reliably it would help a lot if you could provide the output of these commands after the bug has happened: dmesg strace -f -p $(pidof ksplashqml) 2>&1 | dd bs=1k count=20 journalctl -ab You may have to run some of them as root.
Bug#983034: plasma-workspace-wayland: hanging in ksplashqml
Package: plasma-workspace-wayland Version: 4:5.20.5-3 Severity: grave Dear Maintainer, from SDDM I try to start a Wayland KDE session. The whole GUI freezes. CTRL-ALT-FN2 cannot be used to open a terminal session. SSH login is still possible. Top reports 100 % CPU load for ksplashqml. Mainboard is MacchiatoBIN with 16 GiB RAM. Video card is GeForce GT 710 with nouveau driver. Kernel command line: BOOT_IMAGE=/vmlinuz-5.10.0-3-arm64 root=UUID= ro quiet The problem only occurs in Wayland sessions. X11 KDE is working fine. Best regards Heinrich Schuchardt -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.10.0-3-arm64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-workspace-wayland depends on: ii kwayland-integration 5.20.5-1 ii kwin-wayland 4:5.20.5-1 ii libc6 2.31-9 ii libkf5configcore5 5.78.0-4 ii libkf5coreaddons5 5.78.0-2 ii libkworkspace5-5 4:5.20.5-3 ii libqt5core5a 5.15.2+dfsg-4 ii libqt5dbus5 5.15.2+dfsg-4 ii libstdc++610.2.1-6 ii plasma-workspace 4:5.20.5-3 ii qtwayland55.15.2-2 plasma-workspace-wayland recommends no packages. plasma-workspace-wayland suggests no packages. -- no debconf information
