January 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1206916] Resume from hibernation fails hcd_pci_suspend returns -16
by bugzilla_noreply＠suse.com 06 Jan '23

06 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206916 https://bugzilla.suse.com/show_bug.cgi?id=1206916#c1 --- Comment #1 from Leys <wguy4biz(a)comcast.net> --- This problem is experienced elsewhere as well, see. https://forums.gentoo.org/viewtopic-t-1160218.html https://bugzilla.kernel.org/show_bug.cgi?id=216171 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206937] New: Enable CONFIG_LRU_GEN_ENABLED by default on x86_64
by bugzilla_noreply＠suse.com 06 Jan '23

06 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206937 Bug ID: 1206937 Summary: Enable CONFIG_LRU_GEN_ENABLED by default on x86_64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: johndoe1991239(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Enabling MGLRU could give some performance benefits. Right now it is compiled into the kernel but not enabled by default -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206925] WiFi does not work after update
by bugzilla_noreply＠suse.com 06 Jan '23

06 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206925 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Network |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206848] khugepaged at 100% CPU
by bugzilla_noreply＠suse.com 06 Jan '23

06 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206848 https://bugzilla.suse.com/show_bug.cgi?id=1206848#c5 --- Comment #5 from Michal Hocko <mhocko(a)suse.com> --- One notable metric I have overlooked before is a high number of isolated pages. We are talking about increase in range of 900k pages per second. That would likely explain the high CPU utilization. If the khugepaged was busy mostly isolating pages and not making anything with them this would surely burn a lot of CPU time. Anyway something for Vlastimil to rummage through. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206848] khugepaged at 100% CPU
by bugzilla_noreply＠suse.com 06 Jan '23

06 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206848 https://bugzilla.suse.com/show_bug.cgi?id=1206848#c4 Michal Hocko <mhocko(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(vbabka(a)suse.com) --- Comment #4 from Michal Hocko <mhocko(a)suse.com> --- In both of those logs there is barely anything scanned and actually nothing daemon* counters. So I am afraid vmstat alone will not tell us much. Vlastimil, do you have any suggestion for further data collection tips? I was thinking about collecting /proc/$(pidof khugepaged)/stack as well. But maybe compaction related tracepoints would tell us more. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206224] Dell notebook drains battery during sleep
by bugzilla_noreply＠suse.com 06 Jan '23

06 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206224 https://bugzilla.suse.com/show_bug.cgi?id=1206224#c4 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek(a)suse.com --- Comment #4 from Michal Suchanek <msuchanek(a)suse.com> --- Which means that every single driver needs runtime PM support, and if some does not have it the device and the bus will not be powered down in suspend. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206846] New: sysfs: cannot create duplicate filename '/bus/nvmem/devices/rmem0'
by bugzilla_noreply＠suse.com 06 Jan '23

06 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206846 Bug ID: 1206846 Summary: sysfs: cannot create duplicate filename '/bus/nvmem/devices/rmem0' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: seppe.hoogzaad(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863844 --> http://bugzilla.opensuse.org/attachment.cgi?id=863844&action=edit de output of dmesg I tried to do a dist-upgrade in Tumbleweed on my raspberry py 4 which boots from a USB-attached SSD. This was in December. The dist-upgrade went wrong. I had a lot of problems to get a roll back because a lot of stuff was just not working. There was only the emergency mode. Is did get a dmesg output before the roll back. This has an error which is new (i could not google it). I am reporting this because this might be of interest and hopefully someone can fix this. Because it caused a lot of inconvenience, i decided not to do a dist-upgrade for a while. My current version which works an to where i rolled-back: # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20220320" # uname -r 5.16.15-1-default The version after the dist-upgrade, which went wrong: NAME="openSUSE Tumbleweed" # VERSION="20221211" kernel: version 6.0.12-1-default In both cases the firmware is: # rpi-eeprom-update BOOTLOADER: up to date CURRENT: Tue Jan 25 14:30:41 UTC 2022 (1643121041) LATEST: Tue Jan 25 14:30:41 UTC 2022 (1643121041) RELEASE: critical (/lib/firmware/raspberrypi/bootloader/critical) Use raspi-config to change the release. VL805_FW: Dedicated VL805 EEPROM VL805: up to date CURRENT: 000138a1 LATEST: 000138a1 The full dmesg output is in the attachment. The bug in the dmesg is copied here: [ 60.746746] sysfs: cannot create duplicate filename '/bus/nvmem/devices/rmem0' [ 60.847703] CPU: 0 PID: 480 Comm: systemd-udevd Not tainted 6.0.12-1-default #1 openSUSE Tumbleweed 6ce97399187a5dcfe0ab74b073a14af92eb81d40 [ 61.017157] Hardware name: raspberrypi rpi/rpi, BIOS 2022.10 10/01/2022 [ 61.109255] Call trace: [ 61.150591] dump_backtrace+0xe8/0x130 [ 61.207826] show_stack+0x20/0x60 [ 61.259757] dump_stack_lvl+0x64/0x80 [ 61.315890] dump_stack+0x18/0x34 [ 61.367841] sysfs_warn_dup+0x6c/0x90 [ 61.423915] sysfs_do_create_link_sd+0xf8/0x100 [ 61.490463] sysfs_create_link+0x28/0x50 [ 61.549574] bus_add_device+0x70/0x160 [ 61.606540] device_add+0x398/0x920 [ 61.660307] device_register+0x28/0x40 [ 61.717254] nvmem_register+0x1b8/0xa10 [ 61.775239] devm_nvmem_register+0x24/0x70 [ 61.836359] rmem_probe+0x9c/0xf0 [nvmem_rmem acf08610ddc402f2c99db29f46fed6598b0fc3da] [ 61.944970] platform_probe+0x70/0xcc [ 62.000814] really_probe+0xc8/0x3e0 [ 62.055590] __driver_probe_device+0x84/0x190 [ 62.076130] ------------[ cut here ]------------ [ 62.116778] driver_probe_device+0x44/0x100 [ 62.116792] __driver_attach+0xfc/0x1f0 [ 62.116801] bus_for_each_dev+0x78/0xd0 [ 62.181166] Firmware transaction timeout [ 62.240213] driver_attach+0x2c/0x40 [ 62.240227] bus_add_driver+0x184/0x240 [ 62.240241] driver_register+0x80/0x13c [ 62.295141] WARNING: CPU: 1 PID: 38 at drivers/firmware/raspberrypi.c:63 rpi_firmware_property_list+0x1fc/0x264 [ 62.349937] __platform_driver_register+0x30/0x3c [ 62.405841] Modules linked in: [ 62.457524] rmem_driver_init+0x28/0x1000 [nvmem_rmem acf08610ddc402f2c99db29f46fed6598b0fc3da] [ 62.512375] nvmem_rmem(+) [ 62.567223] do_one_initcall+0x4c/0x2bc [ 62.698015] efi_pstore [ 62.763411] do_init_module+0x50/0x1f4 [ 62.808767] joydev [ 62.922683] load_module+0x1d2c/0x2190 [ 62.963819] uio_pdrv_genirq [ 63.018669] __do_sys_init_module+0x2d4/0x314 [ 63.056640] uio [ 63.110435] __arm64_sys_init_module+0x24/0x30 [ 63.144188] fuse [ 63.197981] invoke_syscall+0x78/0x100 [ 63.241228] nfsd [ 63.302405] el0_svc_common.constprop.0+0x178/0x1a0 [ 63.332994] auth_rpcgss [ 63.395226] do_el0_svc+0x34/0xc0 [ 63.426870] nfs_acl [ 63.480663] el0_svc+0x34/0x140 [ 63.512307] lockd [ 63.579812] el0t_64_sync_handler+0xf4/0x120 [ 63.618839] grace [ 63.667359] el0t_64_sync+0x1a0/0x1a4 [ 63.702167] sunrpc [ 63.749680] rmem: probe of 3ee62b40.nvram failed with error -17 [ 63.781276] dmi_sysfs ip_tables x_tables hid_generic usbhid uas usb_storage xhci_pci xhci_pci_renesas xhci_hcd usbcore usb_common vc4 snd_soc_hdmi_codec snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_pcm snd_timer clk_raspberrypi bcm2835_wdt i2c_brcmstb snd sdhci_iproc crct10dif_ce soundcore gpio_raspberrypi_exp drm_cma_helper bcm2835_dma drm_display_helper sdhci_pltfm pcie_brcmstb raspberrypi_hwmon clk_bcm2711_dvp sdhci virt_dma mmc_core cec gpio_regulator rc_core phy_generic fixed btrfs blake2b_generic libcrc32c xor xor_neon raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs [ 63.781505] CPU: 1 PID: 38 Comm: kworker/1:1 Not tainted 6.0.12-1-default #1 openSUSE Tumbleweed 6ce97399187a5dcfe0ab74b073a14af92eb81d40 [ 63.781522] Hardware name: raspberrypi rpi/rpi, BIOS 2022.10 10/01/2022 [ 63.781529] Workqueue: events_freezable mmc_rescan [mmc_core] [ 63.781637] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 63.781649] pc : rpi_firmware_property_list+0x1fc/0x264 [ 63.781666] lr : rpi_firmware_property_list+0x1fc/0x264 [ 65.465914] sp : ffff8000082e3a40 [ 65.465923] x29: ffff8000082e3a40 x28: 0000000000000000 x27: ffff43bc85a116c0 [ 65.465945] x26: 0000000000000001 x25: ffff8000081d6008 x24: 0000000000001000 [ 65.465962] x23: ffff43bc8240b500 x22: ffffba6af3d7e420 x21: ffff43bc85a11680 [ 65.465979] x20: 0000000000000014 x19: ffff8000081d6000 x18: ffffffffffffffff [ 65.465996] x17: 0000000000000000 x16: ffff43bd3b751e40 x15: ffffffffffffffff [ 65.466012] x14: 0000000000000000 x13: 205d303834542020 x12: 5b5d323937363131 [ 65.466028] x11: 00000000ffffe21e x10: 000000000000005d x9 : ffffba6af1744b8c [ 65.466045] x8 : 7f7f7f7f7f7f7f7f x7 : 205b5d3239373631 x6 : 312e32362020205b [ 65.466061] x5 : 0000000000000000 x4 : ffff43bd3b75fb88 x3 : ffff43bd3b76c568 [ 65.466077] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff43bc80358000 [ 65.466094] Call trace: [ 65.466099] rpi_firmware_property_list+0x1fc/0x264 [ 65.466125] rpi_firmware_property+0x78/0xbc [ 65.466137] rpi_exp_gpio_set+0x5c/0xb4 [gpio_raspberrypi_exp 50504e8edbb5f160ca557c27fdc9cbadf6ad7bc0] [ 65.466160] gpiod_set_raw_value_commit+0x50/0x190 [ 65.466176] gpiod_set_value_nocheck+0x44/0x84 [ 65.466185] gpiod_set_value_cansleep+0x48/0xc0 [ 65.466193] _regulator_do_enable+0x3f8/0x470 [ 65.466207] _regulator_enable+0x154/0x1c0 [ 65.466219] regulator_enable+0x44/0x84 [ 65.466230] mmc_regulator_set_ocr+0xc0/0xf0 [mmc_core 9f63a100780a06565bfee99bd40bcacc0aefad08] [ 65.466331] sdhci_set_power_and_bus_voltage+0x40/0x6c [sdhci 8a9d8db3ca8cbd1e33cd0a9b2644ffc690db0cf9] [ 65.466368] sdhci_set_ios+0xb8/0x8bc [sdhci 8a9d8db3ca8cbd1e33cd0a9b2644ffc690db0cf9] [ 65.466401] mmc_set_initial_state+0x98/0x110 [mmc_core 9f63a100780a06565bfee99bd40bcacc0aefad08] [ 65.466494] mmc_power_up.part.0+0x58/0x164 [mmc_core 9f63a100780a06565bfee99bd40bcacc0aefad08] [ 65.466585] mmc_rescan+0x19c/0x32c [mmc_core 9f63a100780a06565bfee99bd40bcacc0aefad08] [ 65.466675] process_one_work+0x21c/0x4a0 [ 65.466693] worker_thread+0x74/0x430 [ 65.466704] kthread+0x110/0x114 [ 65.466714] ret_from_fork+0x10/0x20 [ 65.466727] ---[ end trace 0000000000000000 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1206224] Dell notebook drains battery during sleep
by bugzilla_noreply＠suse.com 06 Jan '23

06 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206224 https://bugzilla.suse.com/show_bug.cgi?id=1206224#c3 Michal Svec <msvec(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(msvec(a)suse.com) | --- Comment #3 from Michal Svec <msvec(a)suse.com> --- It seems it works fine with 6.1.3, the nb survived whole night with just 10% of the battery consumption. That's way better! (The kernel itself has other issues like artifacts in the Konsole, etc) Just FTR, here's the link to the explanation from Dell: https://www.dell.com/community/XPS/FAQ-Modern-Standby/td-p/7514448 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206864] New: Direct Rendering Manager trouble upon resume from suspend to RAM
by bugzilla_noreply＠suse.com 06 Jan '23

06 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206864 Bug ID: 1206864 Summary: Direct Rendering Manager trouble upon resume from suspend to RAM 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: karl.mistelberger(a)nefkom.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863857 --> http://bugzilla.opensuse.org/attachment.cgi?id=863857&action=edit journal The system readily suspends. But resume is very slow and exhibits trouble with drm: [ 195.129982] kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400300000). [ 195.831331] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 196.343309] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 196.855320] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 197.367318] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 197.879296] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 198.391313] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 198.903334] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 199.415327] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 199.927300] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 200.439297] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 200.951299] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 201.463085] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 201.975089] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 202.487089] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 202.999090] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 203.511090] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 204.023091] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 204.535091] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 205.047358] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 205.123518] kernel: [drm] UVD and UVD ENC initialized successfully. [ 205.223510] kernel: [drm] VCE initialized successfully. See also attached journal. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1206916] New: Resume from hibernation fails hcd_pci_suspend returns -16
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206916 Bug ID: 1206916 Summary: Resume from hibernation fails hcd_pci_suspend returns -16 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: wguy4biz(a)comcast.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863907 --> http://bugzilla.opensuse.org/attachment.cgi?id=863907&action=edit System log of hibernation resume After a normal successful hibernation, resume fails after successfully loading the disk image. -- You are receiving this mail because: You are the assignee for the bug.

1 0