January 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1206681] New: Massive btrfs errors
by bugzilla_noreply＠suse.com 15 Jan '23

15 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206681 Bug ID: 1206681 Summary: Massive btrfs errors 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: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Made an update with 22/12/2022. I have included dmesg and journalctl logs to show what happens -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1207011] kernel-default recommends kernel-firmware which will pull in kernel-firmware-all
by bugzilla_noreply＠suse.com 15 Jan '23

15 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207011 https://bugzilla.suse.com/show_bug.cgi?id=1207011#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |YaST2 Assignee|kernel-bugs(a)opensuse.org |yast2-maintainers(a)suse.de QA Contact|qa-bugs(a)suse.de |jsrain(a)suse.com --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Since some time ago (years?), it has been asked YaST team for considering a new way of installation and the detection of firmware files. After that part is finished, we may drop the Recommends from kernel-default. Tossed to YaST team. FWIW, kernel-default-base doesn't have the Recommends. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207148] New: Sound broken on Lenovo ideapad 3 using sof-hda-dsp with kernel-5.14.21-150400.38-default, using plasma/kde
by bugzilla_noreply＠suse.com 14 Jan '23

14 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207148 Bug ID: 1207148 Summary: Sound broken on Lenovo ideapad 3 using sof-hda-dsp with kernel-5.14.21-150400.38-default, using plasma/kde 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: tuxuser(a)quantentunnel.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- System: Lenovo ideapad 3 OS: openSUSE Leap 15.4, all updates installed Kernel: 5.14.21-150400.38-default Sound driver: sof-hda-dsp Desktop: plasma/kde Problem: no sound in amarok, firefox, etc Steps to reproduce 1. boot laptop to Leap 15.4 2. login to kde plasma (x11) 3. start amarok, play anything (for example amarok theme) 4. problem: no sound There was no problem with older kernel 5.14.21-150400.33-default. There is also no problem with kernel from http://download.opensuse.org/repositories/Kernel:/SLE15-SP4/pool/ I've tried 5.14.21-150400.322.g49b518d-default. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1207011] New: kernel-default recommends kernel-firmware which will pull in kernel-firmware-all
by bugzilla_noreply＠suse.com 11 Jan '23

11 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207011 Bug ID: 1207011 Summary: kernel-default recommends kernel-firmware which will pull in kernel-firmware-all 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: luc14n0(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The kernel-firmware package [1] has been split many moons ago to provide sub-package such as: > kernel-firmware-amdgpu, kernel-firmware-intel, kernel-firmware-bluetooth, kernel-firmware-network, etc, etc. And supplementation facilities has been put in place too. The kernel-firmware package has a get_supplements.sh shell script which automatically generates Suplemments tags such as: > modalias(pci:v00001002d*sv*sd*bc03sc00i00*) In the amdgpu sub-package, among many others modaliases. > modalias(of:N*T*Cusb1286,204e) in the bluetooth sub-package, also among many others modaliases. I don't know if that split was discussed somewhere - I searched the mailing list (or at least tried to), but didn't find anything meaningful. If it was and someone can provide a link, I'd appreciate it. From my perspective, this split was made to avoid having a monolithic kernel-firmware package (which has almost 500MB of size) that makes updating the system more painful than it should. So the end-user's system would install only what's needed by them - with the help of the Supplements tags -, rather than installing everything. Despite the split and supplementation facilities, the Kernel still recommends "kernel-firmware", which is provided by two packages. One is the monolithic kernel-firmware package - that we're still providing (I don't know why though). And the other is "kernel-firmware-all", a compatibility metapackage that pulls in every kernel-firmware-* sub-package. And this has the effect of negating completely the split of the kernel-firmware package in sub-packages, since kernel-default is recommending kernel-firmware: > $ rpm -q --whatrecommends kernel-firmware > kernel-default-6.0.12-1.1.x86_64 > kernel-default-6.1.1-1.1.x86_64 In other words, virtually every system installation is still ending up with all the kernel-firmware files as before the split occurred. TLDR, shouldn't we remove that recommendation from the kernel-default and let the supplementation facilities do their work? Sadly I'm lacking a good laptop/PC for the time being and can't do much experimentation. [1] https://build.opensuse.org/package/show/openSUSE:Factory/kernel-firmware -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1206926] New: process exit status not set by leader thread, when all threads exit using SYS_exit
by bugzilla_noreply＠suse.com 11 Jan '23

11 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206926 Bug ID: 1206926 Summary: process exit status not set by leader thread, when all threads exit using SYS_exit 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: tdevries(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- [ Corresponding upstream gdb PR: https://sourceware.org/bugzilla/show_bug.cgi?id=29965 ] Consider the following gdb testsuite test-case: ... $ cat src/gdb/testsuite/gdb.threads/process-exit-status-is-leader-exit-status.c /* This testcase is part of GDB, the GNU debugger. Copyright 2022-2023 Free Software Foundation, Inc. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. */ #include <pthread.h> #include <unistd.h> #include <sys/syscall.h> #define NUM_THREADS 32 pthread_barrier_t barrier; static void do_exit (int exitcode) { /* Synchronize all threads up to here so that they all exit at roughly the same time. */ pthread_barrier_wait (&barrier); /* All threads exit with SYS_exit, even the main thread, to avoid exiting with a group-exit syscall, as that syscall changes the exit status of all still-alive threads, thus potentially masking a bug. */ syscall (SYS_exit, exitcode); } static void * start (void *arg) { int thread_return_value = *(int *) arg; do_exit (thread_return_value); } int main(void) { pthread_t threads[NUM_THREADS]; int thread_return_val[NUM_THREADS]; int i; pthread_barrier_init (&barrier, NULL, NUM_THREADS + 1); for (i = 0; i < NUM_THREADS; ++i) { thread_return_val[i] = i + 2; pthread_create (&threads[i], NULL, start, &thread_return_val[i]); } do_exit (1); } ... Compile like this: ... $ gcc -lpthread src/gdb/testsuite/gdb.threads/process-exit-status-is-leader-exit-status.c ... On x86_64 openSUSE Tumbleweed 20230102 with kernel 6.1.1-1-default, we have: ... $ ./a.out; echo $? 32 ... Expected value (which I get on say openSUSE Leap 15.4 with kernel 5.14.21) is 1. Possible kernel commit causing this change in behaviour: ... commit d80f7d7b2c75c5954d335dffbccca62a5002c3e0 Author: Eric W. Biederman <ebiederm(a)xmission.com> Date: Tue Jun 21 14:38:52 2022 -0500 signal: Guarantee that SIGNAL_GROUP_EXIT is set on process exit Track how many threads have not started exiting and when the last thread starts exiting set SIGNAL_GROUP_EXIT. This guarantees that SIGNAL_GROUP_EXIT will get set when a process exits. In practice this achieves nothing as glibc's implementation of _exit calls sys_group_exit then sys_exit. While glibc's implemenation of pthread_exit calls exit (which cleansup and calls _exit) if it is the last thread and sys_exit if it is the last thread. This means the only way the kernel might observe a process that does not set call exit_group is if the language runtime does not use glibc. With more cleanups I hope to move the decrement of quick_threads earlier. Link: https://lkml.kernel.org/r/87bkukd4tc.fsf_-_@email.froward.int.ebiederm.org Signed-off-by: "Eric W. Biederman" <ebiederm(a)xmission.com> ... -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1207060] New: [Build 20230110] openQA test fails in btrfs_autocompletion because of call trace
by bugzilla_noreply＠suse.com 11 Jan '23

11 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207060 Bug ID: 1207060 Summary: [Build 20230110] openQA test fails in btrfs_autocompletion because of call trace Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 URL: https://openqa.opensuse.org/tests/3030367/modules/btrf s_autocompletion/steps/11 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: zluo(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_filesystem@64bit fails in [btrfs_autocompletion](https://openqa.opensuse.org/tests/3030367/modules/btr… ## Test suite description Maintainer: QE Core Filesystem related tests, for example snapper and btrfs features. ## Reproducible Fails since (at least) Build [20230106](https://openqa.opensuse.org/tests/3019669) ## Expected result Last good: [20230105](https://openqa.opensuse.org/tests/3016289) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… see https://openqa.opensuse.org/tests/3030367/logfile?filename=serial0.txt -- [ 243.176590][ T7778] ------------[ cut here ]------------ [ 243.177307][ T7778] WARNING: CPU: 0 PID: 7778 at fs/btrfs/qgroup.c:2756 btrfs_qgroup_account_extents+0x1ae/0x260 [btrfs] [ 243.178611][ T7778] Modules linked in: dm_mirror dm_region_hash dm_log xfs algif_hash af_alg isofs loop af_packet 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_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 rfkill nf_tables nfnetlink qrtr intel_rapl_msr intel_rapl_common intel_uncore_frequency_common kvm_intel snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec kvm ppdev snd_hda_core snd_hwdep snd_pcm snd_timer irqbypass virtio_net pcspkr net_failover snd failover soundcore i2c_piix4 parport_pc parport tiny_power_button button joydev fuse efi_pstore configfs dmi_sysfs ip_tables x_tables hid_generic usbhid crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 xhci_pci xhci_pci_renesas sr_mod xhci_hcd cdrom aesni_intel crypto_simd ata_generic usbcore bochs cryptd drm_vram_helper drm_ttm_helper virtio_blk [ 243.178660][ T7778] virtio_scsi ttm ata_piix floppy serio_raw btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua qemu_fw_cfg virtio_rng [ 243.191699][ T7778] CPU: 0 PID: 7778 Comm: snapperd Not tainted 6.1.3-1-default #1 openSUSE Tumbleweed 94c09e59bead22c7d4264bd28427f55de54538c2 [ 243.193186][ T7778] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b-rebuilt.opensuse.org 04/01/2014 [ 243.194569][ T7778] RIP: 0010:btrfs_qgroup_account_extents+0x1ae/0x260 [btrfs] [ 243.195482][ T7778] Code: 85 c0 74 0f 48 8b 78 08 4c 89 fa 4c 89 ee e8 59 54 f5 ff 65 ff 0d 52 ed be 3f 0f 85 b8 fe ff ff 0f 1f 44 00 00 e9 ae fe ff ff <0f> 0b 49 8b 57 18 45 31 c9 4d 8d 47 38 31 c9 4c 89 ee e8 1b 71 ff [ 243.198145][ T7778] RSP: 0018:ffffb2a2c2713cb8 EFLAGS: 00010246 [ 243.199075][ T7778] RAX: ffff9b7703c2d000 RBX: 0000000000000000 RCX: 000000001e6b0000 [ 243.200195][ T7778] RDX: ffff9b7703c2d000 RSI: f0a9e0f90cef6b04 RDI: 0000000000000000 [ 243.201383][ T7778] RBP: ffff9b770349b760 R08: ffffb2a2c2713bc8 R09: 0000000000000c40 [ 243.202371][ T7778] R10: ffff9b7743ce9448 R11: 0000000000000001 R12: 0000000000000001 [ 243.203191][ T7778] R13: ffff9b770740a000 R14: ffff9b7706545e38 R15: ffff9b7703c2d000 [ 243.204019][ T7778] FS: 00007f305e0706c0(0000) GS:ffff9b775e400000(0000) knlGS:0000000000000000 [ 243.205088][ T7778] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 243.205789][ T7778] CR2: 00007fad4119ee20 CR3: 0000000003fba004 CR4: 0000000000370ef0 [ 243.206597][ T7778] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 243.207413][ T7778] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 243.208221][ T7778] Call Trace: [ 243.208579][ T7778] <TASK> [ 243.208933][ T7778] btrfs_commit_transaction+0x30c/0xb40 [btrfs db8db32c679239d3b334df0acddfa9a4f194b39b] [ 243.210071][ T7778] ? start_transaction+0xc3/0x5b0 [btrfs db8db32c679239d3b334df0acddfa9a4f194b39b] [ 243.211411][ T7778] btrfs_qgroup_rescan+0x42/0xc0 [btrfs db8db32c679239d3b334df0acddfa9a4f194b39b] [ 243.212907][ T7778] btrfs_ioctl+0x1ab9/0x25c0 [btrfs db8db32c679239d3b334df0acddfa9a4f194b39b] [ 243.214298][ T7778] ? call_rcu+0xd5/0xa10 [ 243.214946][ T7778] ? __seccomp_filter+0x319/0x4d0 [ 243.215685][ T7778] __x64_sys_ioctl+0x90/0xd0 [ 243.216949][ T7778] do_syscall_64+0x5b/0x80 [ 243.217475][ T7778] ? syscall_exit_to_user_mode+0x17/0x40 [ 243.218050][ T7778] ? do_syscall_64+0x67/0x80 [ 243.218523][ T7778] ? do_syscall_64+0x67/0x80 [ 243.219002][ T7778] ? syscall_exit_to_user_mode+0x17/0x40 [ 243.219579][ T7778] ? do_syscall_64+0x67/0x80 [ 243.220050][ T7778] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 243.220656][ T7778] RIP: 0033:0x7f305e70d9bf [ 243.221249][ T7778] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 243.224023][ T7778] RSP: 002b:00007f305e06f7e0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 243.225418][ T7778] RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 00007f305e70d9bf [ 243.226591][ T7778] RDX: 00007f305e06f840 RSI: 000000004040942c RDI: 0000000000000007 [ 243.227863][ T7778] RBP: 00007f305e06f840 R08: 0000000000000000 R09: 0000000000000000 [ 243.229862][ T7778] R10: 0000000000001000 R11: 0000000000000246 R12: 00005572b3bdccc0 [ 243.231652][ T7778] R13: 00007f305e06fa30 R14: 00007f305e06fa60 R15: 00007f305e06fa1f [ 243.233484][ T7778] </TASK> [ 243.234540][ T7778] ---[ end trace 0000000000000000 ]--- logs can be found at: https://openqa.opensuse.org/tests/3030367#downloads -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 11 Jan '23

11 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1205576 http://bugzilla.opensuse.org/show_bug.cgi?id=1205576#c14 Philippe Cond� <conde.philippe(a)skynet.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #14 from Philippe Cond� <conde.philippe(a)skynet.be> --- Bisection of kernel let me to patch usb:dwc3:gadget: Don't delay End Transfer on delayed_status which seems strange: Why a usb patch should trigger this error? OTOH I found that the system freeze doesn't more occur with kernel 6.1.3 and last PysolFC. So this bug report can be closed. Regards Philippe -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200000] qla2xxx no longer detects LTO drive starting from kernel 5.17.4
by bugzilla_noreply＠suse.com 11 Jan '23

11 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1200000 https://bugzilla.suse.com/show_bug.cgi?id=1200000#c5 Daniel Wagner <daniel.wagner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Daniel Wagner <daniel.wagner(a)suse.com> --- Sorry to hear this. Anyway, the HW vendor is listening on their website which adapter is currently supported. If you have any supported HW, it's possible to get support. For non trivial bug reports this is essential. Closing report. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200000] qla2xxx no longer detects LTO drive starting from kernel 5.17.4
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1200000 https://bugzilla.suse.com/show_bug.cgi?id=1200000#c4 --- Comment #4 from Andreas Bolsch <andreas.bolsch(a)alumni.tu-berlin.de> --- I'm afraid I can't test anymore. As the tape drive accessability is vital, I had to get fc adapter with a different chipset right away. Old one had been scrapped ... -- 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 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206224 https://bugzilla.suse.com/show_bug.cgi?id=1206224#c9 Michal Svec <msvec(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(msvec(a)suse.com) | --- Comment #9 from Michal Svec <msvec(a)suse.com> --- Created attachment 863982 --> https://bugzilla.suse.com/attachment.cgi?id=863982&action=edit 6.1.3 hwinfo -- 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 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206224 https://bugzilla.suse.com/show_bug.cgi?id=1206224#c8 --- Comment #8 from Michal Svec <msvec(a)suse.com> --- Created attachment 863981 --> https://bugzilla.suse.com/attachment.cgi?id=863981&action=edit 5.14.21 hwinfo -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206846 https://bugzilla.suse.com/show_bug.cgi?id=1206846#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ivan.ivanov(a)suse.com --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- The bug about the Broadcom WiFi firmware is a known issue. In anyway, it seems to be a RPi-specific problem. Adding Ivan to Cc. -- 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 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206224 https://bugzilla.suse.com/show_bug.cgi?id=1206224#c7 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(msvec(a)suse.com) --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Could you give hwinfo output from both Leap 15.4 and TW kernels for comparison? -- 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 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206224 https://bugzilla.suse.com/show_bug.cgi?id=1206224#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Oh well, the report is about Leap 15.4 kernel. Hmm, this might be hard to trace all fixes... -- 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 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206224 https://bugzilla.suse.com/show_bug.cgi?id=1206224#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Michal Suchanek from comment #4) > 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. Right, and now most device drivers are behaving politely :) As it seems working, let's close now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206408] Kernel panic after upgrading to kernel 6.0.10 (or 6.0.12) from 6.0.8
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206408 https://bugzilla.suse.com/show_bug.cgi?id=1206408#c13 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED Flags|needinfo?(rainer.klute@gmx. | |de) | --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- OK, then there was some fix, apparently ;) Let's close now. Feel free to reopen if you encounter the very same problem with 6.1.x kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206847] BUG: unable to handle page fault for address: ffff8cc50d0c3680
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206847 https://bugzilla.suse.com/show_bug.cgi?id=1206847#c6 --- Comment #6 from Matwey Kornilov <matwey.kornilov(a)gmail.com> --- Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206847] BUG: unable to handle page fault for address: ffff8cc50d0c3680
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206847 https://bugzilla.suse.com/show_bug.cgi?id=1206847#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- There was a bug with sbitmap and SCSI, and this must be it. The fix has been already merged in SLE15-SP4 git branch (the reference bsc#1206602), so it'll be fixed in the next release. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206847] BUG: unable to handle page fault for address: ffff8cc50d0c3680
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206847 https://bugzilla.suse.com/show_bug.cgi?id=1206847#c4 --- Comment #4 from Matwey Kornilov <matwey.kornilov(a)gmail.com> --- Additional crash-dumps are available at https://disk.yandex.ru/d/CFnvLHeqclSXjA -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187195] tumbleweed battery drain
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1187195 http://bugzilla.opensuse.org/show_bug.cgi?id=1187195#c17 Sebastian Turza��ski <dpbasti(a)wp.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #17 from Sebastian Turza��ski <dpbasti(a)wp.pl> --- Seems to be resolved with current tumbleweed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c18 --- Comment #18 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Hmmmmm, seems it stopped working. -- 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 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206848 https://bugzilla.suse.com/show_bug.cgi?id=1206848#c10 Vlastimil Babka <vbabka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mgorman(a)suse.com Assignee|kernel-bugs(a)opensuse.org |vbabka(a)suse.com Flags|needinfo?(vbabka(a)suse.com) | --- Comment #10 from Vlastimil Babka <vbabka(a)suse.com> --- Thanks, I have found that compaction triggered from khugepaged to allocate a huge page is stuck in a loop of isolating the same ranges for migration over and over: khugepaged-106 [001] 35328.677790: mm_compaction_isolate_migratepages: range=(0x11ce00 ~ 0x11d000) nr_scanned=41 nr_taken=15 khugepaged-106 [001] 35328.677800: mm_compaction_isolate_migratepages: range=(0x11ce00 ~ 0x11d000) nr_scanned=41 nr_taken=5 khugepaged-106 [001] 35328.677805: mm_compaction_isolate_migratepages: range=(0x14ee00 ~ 0x14f000) nr_scanned=36 nr_taken=16 khugepaged-106 [001] 35328.677817: mm_compaction_isolate_migratepages: range=(0x14ee00 ~ 0x14f000) nr_scanned=36 nr_taken=16 khugepaged-106 [001] 35328.677828: mm_compaction_isolate_migratepages: range=(0x140600 ~ 0x140800) nr_scanned=56 nr_taken=24 khugepaged-106 [001] 35328.677845: mm_compaction_isolate_migratepages: range=(0x149800 ~ 0x149958) nr_scanned=51 nr_taken=32 khugepaged-106 [001] 35328.677867: mm_compaction_isolate_migratepages: range=(0x149958 ~ 0x149a00) nr_scanned=25 nr_taken=16 khugepaged-106 [001] 35328.677879: mm_compaction_isolate_migratepages: range=(0x146000 ~ 0x146200) nr_scanned=47 nr_taken=12 khugepaged-106 [001] 35328.677887: mm_compaction_isolate_migratepages: range=(0x151e00 ~ 0x152000) nr_scanned=34 nr_taken=1 khugepaged-106 [001] 35328.677890: mm_compaction_isolate_migratepages: range=(0x158400 ~ 0x158460) nr_scanned=39 nr_taken=32 khugepaged-106 [001] 35328.677913: mm_compaction_isolate_migratepages: range=(0x158460 ~ 0x1584d0) nr_scanned=36 nr_taken=32 khugepaged-106 [001] 35328.677935: mm_compaction_isolate_migratepages: range=(0x1584d0 ~ 0x158600) nr_scanned=22 nr_taken=16 khugepaged-106 [001] 35328.677947: mm_compaction_isolate_migratepages: range=(0x165200 ~ 0x165258) nr_scanned=45 nr_taken=32 khugepaged-106 [001] 35328.677969: mm_compaction_isolate_migratepages: range=(0x165258 ~ 0x165400) nr_scanned=43 nr_taken=25 khugepaged-106 [001] 35328.677986: mm_compaction_isolate_migratepages: range=(0x15b600 ~ 0x15b800) nr_scanned=50 nr_taken=8 khugepaged-106 [001] 35328.677992: mm_compaction_isolate_migratepages: range=(0x163400 ~ 0x163464) nr_scanned=42 nr_taken=32 khugepaged-106 [001] 35328.678015: mm_compaction_isolate_migratepages: range=(0x163464 ~ 0x163514) nr_scanned=34 nr_taken=32 khugepaged-106 [001] 35328.678039: mm_compaction_isolate_migratepages: range=(0x163514 ~ 0x163600) nr_scanned=106 nr_taken=92 khugepaged-106 [001] 35328.678099: mm_compaction_isolate_migratepages: range=(0x134000 ~ 0x1340c8) nr_scanned=40 nr_taken=32 khugepaged-106 [001] 35328.678121: mm_compaction_isolate_migratepages: range=(0x1340c8 ~ 0x134200) nr_scanned=54 nr_taken=25 khugepaged-106 [001] 35328.678139: mm_compaction_isolate_migratepages: range=(0x12a200 ~ 0x12a400) nr_scanned=40 nr_taken=25 khugepaged-106 [001] 35328.678155: mm_compaction_isolate_migratepages: range=(0x12a200 ~ 0x12a400) nr_scanned=40 nr_taken=15 khugepaged-106 [001] 35328.678168: mm_compaction_isolate_migratepages: range=(0x16de00 ~ 0x16e000) nr_scanned=75 nr_taken=47 khugepaged-106 [001] 35328.678200: mm_compaction_isolate_migratepages: range=(0x16a200 ~ 0x16a400) nr_scanned=88 nr_taken=29 khugepaged-106 [001] 35328.678219: mm_compaction_isolate_migratepages: range=(0x174a00 ~ 0x174c00) nr_scanned=32 nr_taken=8 khugepaged-106 [001] 35328.678227: mm_compaction_isolate_migratepages: range=(0x167400 ~ 0x1674e0) nr_scanned=55 nr_taken=32 khugepaged-106 [001] 35328.678250: mm_compaction_isolate_migratepages: range=(0x1674e0 ~ 0x167500) nr_scanned=32 nr_taken=32 khugepaged-106 [001] 35328.678271: mm_compaction_isolate_migratepages: range=(0x167500 ~ 0x167600) nr_scanned=7 nr_taken=0 khugepaged-106 [001] 35328.678272: mm_compaction_isolate_migratepages: range=(0x165000 ~ 0x165100) nr_scanned=48 nr_taken=32 khugepaged-106 [001] 35328.678295: mm_compaction_isolate_migratepages: range=(0x165100 ~ 0x1651f8) nr_scanned=43 nr_taken=32 khugepaged-106 [001] 35328.678316: mm_compaction_isolate_migratepages: range=(0x1651f8 ~ 0x165200) nr_scanned=8 nr_taken=8 khugepaged-106 [001] 35328.678323: mm_compaction_isolate_migratepages: range=(0x156e00 ~ 0x157000) nr_scanned=52 nr_taken=16 khugepaged-106 [001] 35328.678334: mm_compaction_isolate_migratepages: range=(0x148800 ~ 0x148a00) nr_scanned=33 nr_taken=9 khugepaged-106 [001] 35328.678341: mm_compaction_isolate_migratepages: range=(0x11ce00 ~ 0x11d000) nr_scanned=41 nr_taken=15 khugepaged-106 [001] 35328.678351: mm_compaction_isolate_migratepages: range=(0x11ce00 ~ 0x11d000) nr_scanned=41 nr_taken=5 All of the isolated pages fail migration. Normally the range should be linearly increasing, but here it's taking the ranges via fast_find_migrateblock(). This should not be looping forever as each range should be tried only once. However there's a commit in v6.1 - 7efc3b726103 ("mm/compaction: fix set skip in fast_find_migrateblock") that removes recording the information to not repeat a range from one place, and looks like it's possible under certain circumstances to avoid the recording in the other places, and that's probably happened for you. I'm building a kernel with that commit reverted so you can test and confirm whether that was it. I will post a link soon. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190007] openSUSE Kernel version is old, can't install on my laptop.
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1190007 https://bugzilla.suse.com/show_bug.cgi?id=1190007#c18 Daniel Wagner <daniel.wagner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #18 from Daniel Wagner <daniel.wagner(a)suse.com> --- No feedback. Closing report. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200000] qla2xxx no longer detects LTO drive starting from kernel 5.17.4
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1200000 https://bugzilla.suse.com/show_bug.cgi?id=1200000#c3 Daniel Wagner <daniel.wagner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andreas.bolsch(a)alumni.tu-be | |rlin.de Flags| |needinfo?(andreas.bolsch@al | |umni.tu-berlin.de) --- Comment #3 from Daniel Wagner <daniel.wagner(a)suse.com> --- We have updated the driver a bit. Is it still a problem? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200541] Tumbleweed Kernel 5.18.1 nvme SUBNQN not valid quirk is likely not enabled
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1200541 https://bugzilla.suse.com/show_bug.cgi?id=1200541#c6 Daniel Wagner <daniel.wagner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Daniel Wagner <daniel.wagner(a)suse.com> --- Fix has landed long ago in the TW kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206937 Michal Hocko <mhocko(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |mhocko(a)suse.com -- 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 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206925 https://bugzilla.suse.com/show_bug.cgi?id=1206925#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tiwai(a)suse.com Resolution|--- |FIXED --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Good to hear, let's close. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206916 https://bugzilla.suse.com/show_bug.cgi?id=1206916#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oneukum(a)suse.com, | |tiwai(a)suse.com, | |wguy4biz(a)comcast.net Flags| |needinfo?(wguy4biz@comcast. | |net) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Could you check whether it's the case for yours, too? https://bugzilla.kernel.org/show_bug.cgi?id=216171#c1 Do "Port change event" messages appear in the log? -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206937 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mgorman(a)suse.com, | |mhocko(a)suse.com, | |tiwai(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206948] Kernel Oops in Leap 15.4 from 6.1.3-lp153.4.g2e19141-default backport kernel
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206948 https://bugzilla.suse.com/show_bug.cgi?id=1206948#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oneukum(a)suse.com, | |tiwai(a)suse.com, | |zeitlinie(a)yahoo.de Flags| |needinfo?(zeitlinie(a)yahoo.d | |e) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Looks like some issue in type-C. Does the problem still persist with the latest 6.1.x kernel? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c17 --- Comment #17 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Hi, With 6.1.3-1, the problem is not as bad: As before, if I connect my phone before resuming, the laptop won't recognize the device. With 6.1.3-1, if I reconnect it when the laptop is up, it'll be recognized. Previously, in this state, the only solution was a reboot. We're making progress! :) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180649] amdgpu: [drm] Failed to updateMST allocation table forpipe idx:1
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1180649 Alexander Bergmann <abergmann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(abergmann(a)suse.co | |m) | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c89 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #89 from Jiri Slaby <jslaby(a)suse.com> --- As per comment 88. -- 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 09 Jan '23

09 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206925 http://bugzilla.opensuse.org/show_bug.cgi?id=1206925#c2 --- Comment #2 from Wojciech Rosiak <opensuse(a)wolli.com> --- This issue seems to be fixed in the latest kernel 6.1.3-1.1. It work fine :-) -- 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 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206848 https://bugzilla.suse.com/show_bug.cgi?id=1206848#c9 --- Comment #9 from Martin Koller <kollix(a)aon.at> --- Created attachment 863934 --> https://bugzilla.suse.com/attachment.cgi?id=863934&action=edit trace-cmd logfile as requested. The 100% cpu was here less than a minute -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206943] New: mkinitrd with self-build nonmodular kernel, building initrd for kernel-default kernel, fails to include mdraid modules
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206943 Bug ID: 1206943 Summary: mkinitrd with self-build nonmodular kernel, building initrd for kernel-default kernel, fails to include mdraid modules 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: patrick.schaaf(a)yalwa.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm happy to see this report closed right away as exotic, but thought I'd report anyway... I'm used to run tumbleweed, for quite a few years and very happily, on production machines (host + kvm virtual machines), using my own, almost-nomodular kernel builds. On the host side, that includes initrds, built the normal way with mkinitrd + dracut and no customization needed. Good. Now I ran into an issue when, for a different reported issue, I got asked to try + reproduce with actual tumbleweed kernel-default. So I installed that, mkinitrd ran normally - and it failed to boot properly. The system (host) where that happened, uses RAID1 (md raid) disks (and LVM on top) for boot + root. What I found is that mkinitrd, apparently because the currently running kernel (my own) has MD drivers built in (not loaded as modules), fails to include the drivers/md modules into the initrd. If I change "instmods '=drivers/md'" to "hostonly='' instmods '=drivers/md'", in 90mdraid/module-setup.sh, I get it to include the modules + get a working boot. If I revert that change + rebuild the initrd again while the suse kernel-default is running (with raid1.ko in lsmod), again I get a working initrd with the modules included. Hope this report helps someone who may stumble across the same issue, even if no change results from it. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1206380] intel pseudoraid C220 fails after upgrade to 6.0.12
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206380 https://bugzilla.suse.com/show_bug.cgi?id=1206380#c3 --- Comment #3 from Dmitry Markov <werwolf131313(a)gmail.com> --- (In reply to Takashi Iwai from comment #2) > Could you verify whether the problem persists with 6.1.x TW kernel? it was ugly for me to do this, but this situation was the last straw for my patience and I transferred all my services to another server and put this one in the closet. I want to ask for forgiveness. I promise that in the next few days I will find another disk for testing and check the situation with the new kernel on this disk and unsubscribe here. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

08 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206848 Bug ID: 1206848 Summary: khugepaged at 100% CPU Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: kollix(a)aon.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since recent update to 6.1.0-1-default I often see khugepaged staying at 100% CPU for a long time (some minutes). Operating System: openSUSE Tumbleweed 20221225 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.0-1-default (64-bit) Graphics Platform: X11 Processors: 4 �� Intel�� Core�� i5-6300U CPU @ 2.40GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel�� HD Graphics 520 Manufacturer: HP Product Name: HP ProBook 650 G2 -- You are receiving this mail because: You are the assignee for the bug.

1 2

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

08 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206848 https://bugzilla.suse.com/show_bug.cgi?id=1206848#c7 --- Comment #7 from Vlastimil Babka <vbabka(a)suse.com> --- Besides the compaction isolated counter, the migrate failure counter grows at same high speed. Yet the compaction scanner counters move much slowly, which would suggest isolations and migrations being retried excessively without scanning, but I don't see how that's possible. Tracepoints could indeed help. Please install trace-cmd and run (while the problem is occuring) as root: trace-cmd record -e compaction:* -e migrate:* (wait for e.g. a minute, check khugepaged keeps using 100% cpu during the time, and then stop by ctrl+c) this should produce a file trace.dat, please upload (e.g. compressed). Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206408] New: Kernel panic after upgrading from to kernel 6.0.10 (or 6.0.12) from 6.0.8
by bugzilla_noreply＠suse.com 08 Jan '23

08 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206408 Bug ID: 1206408 Summary: Kernel panic after upgrading from to kernel 6.0.10 (or 6.0.12) from 6.0.8 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: rainer.klute(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading from kernel 6.0.8 to 6.0.10, the system no longer boots. Instead, it stops relatively early in the boot process with the shift lock LED blinking. No error message is shown on the screen. The last message it shows is regarding the IBM trackpoint device on my Lenovo Thinkpad P50 notebook. Same behaviour with kernel 6.0.12. Luckily, I can still boot the 6.0.8 kernel, but I am stuck with that on this particular machine. -- You are receiving this mail because: You are the assignee for the bug.

1 13

[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 06 Jan '23

06 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

[Bug 1206900] hibernation not working. normal operation resumed
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206900 http://bugzilla.opensuse.org/show_bug.cgi?id=1206900#c3 --- Comment #3 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- Agree (or re-open and adjust the version field) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206900] hibernation not working. normal operation resumed
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206900 http://bugzilla.opensuse.org/show_bug.cgi?id=1206900#c2 --- Comment #2 from Lars-G�ran Andersson <larsg(a)vetulusit.se> --- This is only a problem from a 'saving energy' perspective, so I will upgrade to 15.4 and check if the problem remains. If it's still there I will re-issue a bug report. -- 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 05 Jan '23

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206848 https://bugzilla.suse.com/show_bug.cgi?id=1206848#c3 --- Comment #3 from Martin Koller <kollix(a)aon.at> --- Created attachment 863890 --> https://bugzilla.suse.com/attachment.cgi?id=863890&action=edit another log after more than 15 minutes 100% CPU -- 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 05 Jan '23

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206848 https://bugzilla.suse.com/show_bug.cgi?id=1206848#c2 Martin Koller <kollix(a)aon.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kollix(a)aon.at) | --- Comment #2 from Martin Koller <kollix(a)aon.at> --- Created attachment 863888 --> https://bugzilla.suse.com/attachment.cgi?id=863888&action=edit captured log file -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206900] hibernation not working. normal operation resumed
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206900 http://bugzilla.opensuse.org/show_bug.cgi?id=1206900#c1 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |Andreas.Stieger(a)gmx.de, | |larsg(a)vetulusit.se Component|Basesystem |Kernel Resolution|--- |WONTFIX Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org Flags| |needinfo?(larsg(a)vetulusit.s | |e) --- Comment #1 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- (In reply to Lars-G�ran Andersson from comment #0) > Started after a normal update, but cannot remember exactly when. Backtrack and binary search. Start with the kernels, and specify the update. openSUSE Leap 15.3 is EOL now and will not be receiving further updates. Upgrade to Leap 15.4 and try again. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks for the info update. AFAIK, oft-seen problems with those docs are about the Realtek Ethernet driver (r8152). You can try to unload r8152 before the suspend, if any. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c2 --- Comment #2 from Christian Goll <cgoll(a)suse.com> --- This seems to be related to my old Dell docking station, which shows also other malfunctions. I will test again with a new Lenovo docking station and report if the problem persists. -- 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 05 Jan '23

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206848 https://bugzilla.suse.com/show_bug.cgi?id=1206848#c1 Michal Hocko <mhocko(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kollix(a)aon.at Flags| |needinfo?(kollix(a)aon.at) --- Comment #1 from Michal Hocko <mhocko(a)suse.com> --- Could you collect /proc/vmstat during that time period (say every second)[1]? [1] You can use collect_logs from mmdebug-tools package from https://build.opensuse.org/package/binaries/home:mhocko/mmdebug-tools/openS… The command then would be collect_logs -t1s -i /proc/vmstat -o vmstat.log -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206847] BUG: unable to handle page fault for address: ffff8cc50d0c3680
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206847 https://bugzilla.suse.com/show_bug.cgi?id=1206847#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Not sure whether it's already broken in USB side-storage side or a bug in the scsi layer. At least, the Oops happens at the sbitmap_put() call in scsi_device_unbusy(), at it seems. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206864 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |karl.mistelberger(a)nefkom.ne | |t Flags| |needinfo?(karl.mistelberger | |(a)nefkom.net) -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206864 https://bugzilla.suse.com/show_bug.cgi?id=1206864#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Looks like a problem of amdgpu. I suppose it's something new in 6.1.x, and not happening with 6.0.x kernel? If yes, please report to the upstream, e.g. gitlab.freedesktop.org Issues. In anyway, please give the hardware details. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c16 --- Comment #16 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Unless instructed otherwise, I'll keep following the head of TW: �� $ uname -sr Linux 6.1.2-1-default -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c15 --- Comment #15 from Pablo Sanchez <pablo(a)blueoakdb.com> --- (In reply to Oliver Neukum from comment #8) > It is possible that it is just not resumed without a device. Hey Oliver, Well, another excellent question. Clearly you understand how everything is supposed to work under the hood. Nice. I tried to gather more fine-grained data in the hopes it might help. If not, meh, I burned a few minutes. :p ::: Test 1 ::: 1. Connect phone and note laptop recognizes it. 2. Leave phone connected and suspend. 3. Do not disconnect phone. 4. Resume the laptop. ... Result ... Worked! ::: Test 2 ::: Same as the previous test but replace step 3 with a disconnect/reconnect: 1. Connect phone and note laptop recognizes it. 2. Leave phone connected and suspend. 3a. Disconnect phone. 3b. Wait for a few seconds. 3c. Reconnect phone 4. Resume the laptop. ... Result ... Problem tickled. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206846 https://bugzilla.suse.com/show_bug.cgi?id=1206846#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seppe.hoogzaad(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(seppe.hoogzaad@gm | |ail.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- There are actually two kernel warnings: one is about the duplicated sysfs entry for /bus/nvmem/devices/rmem0, while another is the firmware update timeout for rpi. Are both new warnings, or only the former? In anyway, TW already moved to 6.1 kernel. Could you verify whether the issue still persists with the latest kernel or not? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cgoll(a)suse.com, | |tiwai(a)suse.com Flags| |needinfo?(cgoll(a)suse.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you check whether it's a regression in the update kernel(s) or it's been broken in all Leap 15.4 kernels? In anyway, please give hwinfo output from Leap 15.4 kernel. When TW kernel works, give the hwinfo output from there, too, in addition to the dmesg outputs from both cases. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c14 --- Comment #14 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Created attachment 863848 --> https://bugzilla.suse.com/attachment.cgi?id=863848&action=edit working phone: lsusb + dmesg (In reply to Oliver Neukum from comment #12) > > Sorry, this probably needs a long explanation. > > [ trimmed for brevity ] Thank you Oliver for taking the time to explain. I appreciate it! > Please attach the output of "lsusb -v" in the working state with that second > phone connected. Done! The tar-ball contains the following files: o 3/dmesg.nord.txt o 3/lsusb.nord.aft.suspend.txt o 3/lsusb.nord.b4.suspend.txt dmesg captures when I disconnected the phone, suspended and resumed with the phone connected. Thanks again! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206847] New: BUG: unable to handle page fault for address: ffff8cc50d0c3680
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206847 Bug ID: 1206847 Summary: BUG: unable to handle page fault for address: ffff8cc50d0c3680 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: matwey.kornilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863845 --> http://bugzilla.opensuse.org/attachment.cgi?id=863845&action=edit dmesg.txt Hello, I am running openSUSE Leap 15.4 with kernel-default-5.14.21-150400.24.38.1.x86_64 I've faced a system crash and have to kdump outputs for it. The crash occurred during an attempt to connect external hard drive using USB 3.0 adapter. The drive itself has some bad sectors and performs badly, so this seems to triggered the issue. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1206843] New: Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206843 Bug ID: 1206843 Summary: Lenovo T14s Gen3 AMD resume from sleep broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: cgoll(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The actual Leap15.4 kernel does not wake up after a `systemctl suspend` but works fine with the tumbleweed kernel. The `/var/log/messages` just shows the next boot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c13 --- Comment #13 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Created attachment 863840 --> https://bugzilla.suse.com/attachment.cgi?id=863840&action=edit pcie_aspm=off test > dmesg output > Could you check with pcie_aspm=off boot option? Hi, Unfortunately this test didn't pan out. Previously, the phone would work on the first boot. With the test, it failed at first-boot. I'm attaching the output of dmesg. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206774] dvb driver fails
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c8 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #8 from Jiri Slaby <jslaby(a)suse.com> --- The TODO says: +The saa7146-based drivers are one of the few drivers still not using +the vb2 framework, so these drivers are now deprecated with the intent of +removing them altogether by the beginning of 2023. + +In order to keep these drivers they have to be converted to vb2. +If someone is interested in doing this work, then contact the +linux-media mailinglist (https://linuxtv.org/lists.php). So if there are no volunteers, the driver is going away. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206774] dvb driver fails
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c7 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com Flags|needinfo?(Gerhard@Dr-Lorbee | |r.de) | --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- The driver was moved to staging and marked as deprecated by: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c12 Oliver Neukum <oneukum(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #12 from Oliver Neukum <oneukum(a)suse.com> --- (In reply to Pablo Sanchez from comment #10) > (In reply to Oliver Neukum from comment #8) > > The failure you are seeing is on the PCI level. From your logs it is unclear > > whether the HC that fails to resume is hosting other busses. It is possible > > that it is just not resumed without a device. > > Hi, > > My work-around is to resume, *then* connect the device. Sorry, this probably needs a long explanation. From usbcore's viewpoint your roothub on the XHCI without any device connected to it will be in the state (suspended w. remote wakeup) after your system resumes that is the desired state of the root hub, too. So without devices if your system is suspended, no PM transitions will be done on the roothub. If, however, your system is connected to your phone, the roothub and the phone need to be in (active) before and after the system sleeps. So PM transitions are certainly done. My theory was that your system is generally incapable of a PM transition on the PCI level at that time. If that theory were true, your system should crash with any device that is in (active) attached and it should also crash if you artificially force the roothub into a PM transition on resume, which was my second suggestion. > > > Do you have other devices to test to make sure it is not specific to your > > phone? > > What an excellent idea. As my phone is a Samsung S21, non-root, I hadn't > thought it might be an issue. > > Using another phone (OnePlus Nord), it works. Please attach the output of "lsusb -v" in the working state with that second phone connected. > > Alternatively, if not, it would be necessary to set the "control" > > attribute for your root hub to "on". > > I think you're saying a work-around is for me to create a udev rule. No, that was for testing purposes only. Something is failing on the PCI level. You cannot fix that with a udev rule. So please test whether the fault is related to ASPM by doing Takashi's test. From your log: [26232.379255] xhci_hcd 0000:a4:00.0: Unable to change power state from D3cold to D0, device inaccessible [26232.457787] xhci_hcd 0000:a4:00.0: Unable to change power state from D3cold to D0, device inaccessible These must not happen. If they do, everything after that is as expected, though not as desired. Unfortunately everything before them is as it should be. Hence tests to determine the cause of this issue are needed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206451] New: wlan device QCNFA765 not detected
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206451 Bug ID: 1206451 Summary: wlan device QCNFA765 not detected Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: cgoll(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The wireless network adapter Qualcomm QCNFA765 is not detected with the actual leap kernel. As workaround I am using the kernel from kernel:stable:backport (kernel-default-6.1.0-lp153.2.1.gc3232e1.x86_64) -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c11 --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- So it's a Thunderbolt PCI controller, as expected. This might be a similar issue as the upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=216728 Could you check with pcie_aspm=off boot option? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c10 --- Comment #10 from Pablo Sanchez <pablo(a)blueoakdb.com> --- (In reply to Oliver Neukum from comment #8) > The failure you are seeing is on the PCI level. From your logs it is unclear > whether the HC that fails to resume is hosting other busses. It is possible > that it is just not resumed without a device. Hi, My work-around is to resume, *then* connect the device. > Do you have other devices to test to make sure it is not specific to your > phone? What an excellent idea. As my phone is a Samsung S21, non-root, I hadn't thought it might be an issue. Using another phone (OnePlus Nord), it works. > Alternatively, if not, it would be necessary to set the "control" > attribute for your root hub to "on". I think you're saying a work-around is for me to create a udev rule. I can certainly do this but given that my phone is very generic, non-rooted, I'm not sure whether that's a good solution for regular users. Thoughts? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c9 Pablo Sanchez <pablo(a)blueoakdb.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(pablo(a)blueoakdb.c | |om) | --- Comment #9 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Created attachment 863813 --> https://bugzilla.suse.com/attachment.cgi?id=863813&action=edit hwinfo, lspci and dmesg Hi, This data was captured with the latest kernel (6.1.1.1-default) This tar-ball contains the following files: 2/hwinfo.phone.bad.txt 2/hwinfo.phone.ok.txt 2/lspci.phone.bad.txt 2/lspci.phone.ok.txt 2/dmesg.bad.txt where, o hwinfo: hwinfo --all --log ... o lspci: lspci -vvxxx o Files with 'ok' are the /before/ state o Files with 'bad' are the /after/, borked state and 'dmesg.txt' is trimmed to capture the resume with the phone connected (borking the driver). Thank you! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206797] New: [RPi3] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206797 Bug ID: 1206797 Summary: [RPi3] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/3008872/modules/jour nal_check/steps/10 OS: Other Status: NEW Severity: Normal 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, ivan.ivanov(a)suse.com, mbrugger(a)suse.com Found By: openQA Blocker: Yes With kernel 6.1, openQA shows the following kernel trace on RPi3: kernel: brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1206697] Wireless network disappears on Raspberry Pi 4B after kernel-default 6.0.12
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206697 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |ivan.ivanov(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c8 --- Comment #8 from Oliver Neukum <oneukum(a)suse.com> --- The failure you are seeing is on the PCI level. From your logs it is unclear whether the HC that fails to resume is hosting other busses. It is possible that it is just not resumed without a device. Do you have other devices to test to make sure it is not specific to your phone? Alternatively, if not, it would be necessary to set the "control" attribute for your root hub to "on". -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206794] Frequent Kernel Crashes due to problem in af_key.c
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206794 https://bugzilla.suse.com/show_bug.cgi?id=1206794#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tiwai(a)suse.com Resolution|--- |FIXED --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for the report. I backported the upstream commit b97df039a68b2f3e848e238df5d5d06343ea497b to SLE15-SP4 git branch now. It'll be included in the next maintenance update kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206718] [Build 366.2] openQA test fails in opensuse_welcome - opensuse-welcome crashed
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206718 https://bugzilla.suse.com/show_bug.cgi?id=1206718#c1 Max Lin <mlin(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |kernel-bugs(a)suse.de --- Comment #1 from Max Lin <mlin(a)suse.com> --- Since Leap15's kernel is from SLE15, lets assign it to the internal kernel team. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c7 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pablo(a)blueoakdb.com Flags| |needinfo?(pablo(a)blueoakdb.c | |om) --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks. Could you give hwinfo output as well as the dmesg output? Also check the lspci output and see which device is the failing xhci_hcd (in the case of the original post dmesg.txt, it's 0000:a4:00.0). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206794] New: Frequent Kernel Crashes due to problem in af_key.c
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206794 Bug ID: 1206794 Summary: Frequent Kernel Crashes due to problem in af_key.c Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: Manfred.Haertel(a)lotto-rlp.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We experienced frequent kernel crashes on some of our OpenSuse based IPSEC Gateways. The crash dump looks like this: [141226.000411][ T3410] BUG: kernel NULL pointer dereference, address: 0000000000000000 [141226.093721][ T3410] #PF: supervisor write access in kernel mode [141226.166051][ T3410] #PF: error_code(0x0002) - not-present page [141226.237334][ T3410] PGD 0 P4D 0 [141226.277176][ T3410] Oops: 0002 [#1] PREEMPT SMP PTI [141226.336929][ T3410] CPU: 13 PID: 3410 Comm: pluto Tainted: G I N 5.14.21-150400.24.33-default #1 SLE15-SP4 018fa6ac9e6418760457307f6579fc12335772aa [141226.513033][ T3410] Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 11/13/2019 [141226.625191][ T3410] RIP: 0010:__xfrm_state_delete+0xc0/0x1e0 [141226.694385][ T3410] Code: 02 74 04 48 89 50 08 8b 93 cc 00 00 00 48 b8 22 01 00 00 00 00 ad de 48 89 43 20 85 d2 74 22 48 8b 43 38 48 8b 53 40 48 85 c0 <48> 89 02 74 04 48 89 50 08 48 b8 22 01 00 00 00 00 ad de 48 89 43 [141226.930232][ T3410] RSP: 0018:ffffb6bd410879d0 EFLAGS: 00010246 [141227.002562][ T3410] RAX: 0000000000000000 RBX: ffff9c29c543a700 RCX: 00000000fffffffd [141227.097953][ T3410] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffffb84e1700 [141227.193343][ T3410] RBP: ffffffffb84e0840 R08: 0000000000000001 R09: 0000000000000002 [141227.288736][ T3410] R10: 0000000000000002 R11: 0000000000000032 R12: ffffffffb84e1700 [141227.384127][ T3410] R13: 0000000000000000 R14: 0000000000000000 R15: ffffffffb84e0840 [141227.479517][ T3410] FS: 00007fe961572040(0000) GS:ffff9c2c70140000(0000) knlGS:0000000000000000 [141227.586435][ T3410] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [141227.665053][ T3410] CR2: 0000000000000000 CR3: 0000000110a4c001 CR4: 00000000007706e0 [141227.760443][ T3410] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [141227.855831][ T3410] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [141227.951222][ T3410] PKRU: 55555554 [141227.993154][ T3410] Call Trace: [141228.031944][ T3410] <TASK> [141228.066541][ T3410] xfrm_state_delete+0x1e/0x40 [141228.123155][ T3410] xfrm_del_sa+0xcf/0x130 [xfrm_user 056771028dad419158fe83c515fe22924b96b850] [141228.230080][ T3410] xfrm_user_rcv_msg+0x26c/0x2e0 [xfrm_user 056771028dad419158fe83c515fe22924b96b850] [141228.344341][ T3410] ? __kmalloc_node_track_caller+0x1ba/0x3b0 [141228.415632][ T3410] ? netlink_deliver_tap+0x3a/0x1f0 [141228.477490][ T3410] ? copy_to_user_tmpl.part.21+0x150/0x150 [xfrm_user 056771028dad419158fe83c515fe22924b96b850] [141228.602229][ T3410] netlink_rcv_skb+0x4e/0x100 [141228.657796][ T3410] xfrm_netlink_rcv+0x30/0x40 [xfrm_user 056771028dad419158fe83c515fe22924b96b850] [141228.768914][ T3410] netlink_unicast+0x1b3/0x280 [141228.825527][ T3410] netlink_sendmsg+0x320/0x450 [141228.882143][ T3410] sock_sendmsg+0x5c/0x70 [141228.933515][ T3410] sock_write_iter+0x97/0x100 [141228.989082][ T3410] new_sync_write+0x1a1/0x1c0 [141229.044648][ T3410] vfs_write+0x220/0x280 [141229.094972][ T3410] ksys_write+0x50/0xe0 [141229.144246][ T3410] ? do_syscall_64+0x67/0x80 [141229.198758][ T3410] ? __x64_sys_poll+0x37/0x140 [141229.255372][ T3410] do_syscall_64+0x58/0x80 [141229.307788][ T3410] ? __task_pid_nr_ns+0x97/0xb0 [141229.365449][ T3410] ? syscall_exit_to_user_mode+0x18/0x40 [141229.432544][ T3410] ? do_syscall_64+0x67/0x80 [141229.487061][ T3410] ? do_syscall_64+0x67/0x80 [141229.541572][ T3410] ? do_syscall_64+0x67/0x80 [141229.596083][ T3410] ? irq_exit_rcu+0x41/0xc0 [141229.649553][ T3410] entry_SYSCALL_64_after_hwframe+0x61/0xcb [141229.719793][ T3410] RIP: 0033:0x7fe960995af3 [141229.772207][ T3410] Code: 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 64 8b 04 25 18 00 00 00 85 c0 75 14 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 55 f3 c3 0f 1f 00 41 54 55 49 89 d4 53 48 89 [141230.008050][ T3410] RSP: 002b:00007ffd0916cad8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [141230.108679][ T3410] RAX: ffffffffffffffda RBX: 00007ffd0916cf80 RCX: 00007fe960995af3 [141230.204070][ T3410] RDX: 0000000000000028 RSI: 00007ffd0916cf80 RDI: 0000000000000017 [141230.299458][ T3410] RBP: 0000000000000028 R08: 00007ffd0916d4f0 R09: 00007ffd0916cf80 [141230.394847][ T3410] R10: 00007ffd0916d23b R11: 0000000000000246 R12: 000055d3d8f12139 [141230.490237][ T3410] R13: 00007ffd0916d4f0 R14: 00007ffd0916d400 R15: 00000000680f3536 [141230.585630][ T3410] </TASK> [141230.621277][ T3410] Modules linked in: binfmt_misc authenc echainiv cmac rmd160 camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 cast6_generic cast5_avx_x86_64 cast5_generic cast_common deflate gcm ccm serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic blowfish_generic blowfish_x86_64 blowfish_common twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common xcbc sha256_ssse3 sha512_ssse3 des_generic libdes xfrm_user ah6 ah4 esp6 esp4 xfrm4_tunnel tunnel4 ipcomp ipcomp6 xfrm6_tunnel xfrm_ipcomp tunnel6 af_key xfrm_algo nfnetlink bluetooth ecdh_generic iptable_nat xt_nat nf_nat nf_conntrack ipt_REJECT nf_reject_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_LOG nf_log_syslog iptable_filter xt_policy xt_TCPMSS xt_tcpudp bpfilter af_packet iscsi_ibft iscsi_boot_sysfs rfkill dmi_sysfs intel_rapl_msr intel_rapl_common ipmi_ssif nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp coretemp [141230.621341][ T3410] kvm_intel nls_iso8859_1 kvm nls_cp437 vfat fat cdc_eem ses usbnet pl2303 usbserial irqbypass pcspkr efi_pstore(N) enclosure mii tg3 mei_me libphy mei lpc_ich mfd_core hpilo acpi_ipmi intel_pch_thermal ioatdma ipmi_si dca ipmi_devintf ipmi_msghandler acpi_tad(N) button fuse configfs ip_tables x_tables ext4 crc16 mbcache jbd2 hid_generic usbhid uas usb_storage sr_mod sd_mod cdrom t10_pi crc32_pclmul crc32c_intel ghash_clmulni_intel mgag200 drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core xhci_pci aesni_intel xhci_pci_renesas drm xhci_hcd ahci smartpqi crypto_simd cryptd libahci ehci_pci ehci_hcd scsi_transport_sas usbcore libata i2c_algo_bit hpwdt wmi sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod msr efivarfs [141232.491336][ T3410] Supported: No, Unsupported modules are loaded [141232.565764][ T3410] CR2: 0000000000000000 [141232.615034][ T3410] ---[ end trace 7154d1cff8910ed6 ]--- [141232.759152][ T3410] RIP: 0010:__xfrm_state_delete+0xc0/0x1e0 [141232.828350][ T3410] Code: 02 74 04 48 89 50 08 8b 93 cc 00 00 00 48 b8 22 01 00 00 00 00 ad de 48 89 43 20 85 d2 74 22 48 8b 43 38 48 8b 53 40 48 85 c0 <48> 89 02 74 04 48 89 50 08 48 b8 22 01 00 00 00 00 ad de 48 89 43 [141233.064192][ T3410] RSP: 0018:ffffb6bd410879d0 EFLAGS: 00010246 [141233.136524][ T3410] RAX: 0000000000000000 RBX: ffff9c29c543a700 RCX: 00000000fffffffd [141233.231919][ T3410] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffffb84e1700 [141233.327309][ T3410] RBP: ffffffffb84e0840 R08: 0000000000000001 R09: 0000000000000002 [141233.422697][ T3410] R10: 0000000000000002 R11: 0000000000000032 R12: ffffffffb84e1700 [141233.518087][ T3410] R13: 0000000000000000 R14: 0000000000000000 R15: ffffffffb84e0840 [141233.613477][ T3410] FS: 00007fe961572040(0000) GS:ffff9c2c70140000(0000) knlGS:0000000000000000 [141233.720401][ T3410] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [141233.799019][ T3410] CR2: 0000000000000000 CR3: 0000000110a4c001 CR4: 00000000007706e0 [141233.894409][ T3410] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [141233.989799][ T3410] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [141234.085189][ T3410] PKRU: 55555554 [141234.127122][ T3410] Kernel panic - not syncing: Fatal exception in interrupt [141234.241007][ T3410] Kernel Offset: 0x35800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [141234.450223][ T3410] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]--- We found out that this problem is actually a known problem in af_key.c and a one line patch exists, see https://patchwork.kernel.org/project/netdevbpf/patch/20221102101848.ibvumax… However, it seems that the current OpenSuse 15.4 kernel does NOT include this patch. Applying the patch manually fixed the problem for us. We would like to see the patch included in the OpenSuse kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c6 --- Comment #6 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Hi, Thank you for instructions on how to proceed. Unfortunately, the problem exists in the earliest 6.0[1]: 6.0.12 kernel-default-6.0.12-1.1.x86_64 I'd like to confirm I'm testing properly. Aside from installing the 'kernel-default' RPM and booting it, do I need to install any other RPMs? For my initial test, I confirmed that I booted the test kernel with 'uname -a' Thx! ::: References ::: [1] - https://download.opensuse.org/history/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206782] New: SND_SOC_QCOM_COMMON got disabled on armv7hl
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206782 Bug ID: 1206782 Summary: SND_SOC_QCOM_COMMON got disabled on armv7hl 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dmueller(a)suse.com, mkubecek(a)suse.com, tiwai(a)suse.com Found By: --- Blocker: --- Due to our: commit a60b1c275c2e99e2b1c9d12a0ce871f2338cf7c6 Author: Takashi Iwai <tiwai(a)suse.de> Date: Mon Nov 30 11:39:07 2020 +0100 Update config files: make CONFIG_SOUNDWIRE=m (bsc#1179201) Also turned it off for unrelated platforms and upstream's (6.1.2 and 6.2-rc1): commit 8d89cf6ff229ff31cd4f73f5b3928564b81fc41e Author: Srinivas Kandagatla <srinivas.kandagatla(a)linaro.org> Date: Thu Nov 24 14:03:51 2022 +0000 ASoC: qcom: cleanup and fix dependency of QCOM_COMMON stable currently has: config/armv7hl/default:# CONFIG_SND_SOC_QCOM_COMMON is not set config/armv7hl/lpae:CONFIG_SND_SOC_QCOM_COMMON=m It needs CONFIG_SOUNDWIRE which is enabled only in lpae. Is this OK? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- I'd check at first with 6.0 kernel. For example, install the kernel package found in TW history repo: http://download.opensuse.org/history/ and see whether the problem persists. You can find older kernel packages in my OBS kernel repos, too, e.g. OBS home:tiwai:kernel:5.19: http://download.opensuse.org/repositories/home:/tiwai:/kernel:/5.19/standar… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c4 --- Comment #4 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Suspending my laptop is a recent modification to my workflow. Consequently, I don't know when the issue first cropped up. To check when the issue might have first started, assuming I can suspend, I could test with a Live CD. Is it worth trying Leap 15.4? Reading the feature-set[1], it ships with kernel 5.14.21 Thank you. ::: References ::: [1] - https://en.opensuse.org/Features_15.4 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206774] dvb driver fails
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c6 Gerhard Lorbeer <Gerhard(a)Dr-Lorbeer.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #863767|0 |1 is obsolete| | --- Comment #6 from Gerhard Lorbeer <Gerhard(a)Dr-Lorbeer.de> --- Created attachment 863771 --> https://bugzilla.suse.com/attachment.cgi?id=863771&action=edit hwinfo 6.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206774] dvb driver fails
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c5 --- Comment #5 from Gerhard Lorbeer <Gerhard(a)Dr-Lorbeer.de> --- Created attachment 863770 --> https://bugzilla.suse.com/attachment.cgi?id=863770&action=edit hwinfo 6.0 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206774] dvb driver fails
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c4 --- Comment #4 from Gerhard Lorbeer <Gerhard(a)Dr-Lorbeer.de> --- Created attachment 863769 --> https://bugzilla.suse.com/attachment.cgi?id=863769&action=edit dmesg 6.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206774] dvb driver fails
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c3 --- Comment #3 from Gerhard Lorbeer <Gerhard(a)Dr-Lorbeer.de> --- Created attachment 863767 --> https://bugzilla.suse.com/attachment.cgi?id=863767&action=edit dmesg 6.0 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206774] dvb driver fails
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c2 --- Comment #2 from Gerhard Lorbeer <Gerhard(a)Dr-Lorbeer.de> --- Created attachment 863766 --> https://bugzilla.suse.com/attachment.cgi?id=863766&action=edit dmesg 6.0 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206575] BUG: kernel NULL pointer dereference
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206575 https://bugzilla.suse.com/show_bug.cgi?id=1206575#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- It's hard to judge, as the dmesg snippet doesn't really show much useful info, as it's a NULL dereference at the early code path... I close this bug as it's not reproduced. Please reopen if this happens again, and hopefully reproducible at will. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206380] intel pseudoraid C220 fails after upgrade to 6.0.12
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206380 https://bugzilla.suse.com/show_bug.cgi?id=1206380#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo?(werwolf131313@gma | |il.com) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Could you verify whether the problem persists with 6.1.x TW kernel? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206316] add_drivers+=" i915 " included in /etc/dracut.d/*, cause drm/dri issue(s) that delay initial X startup ~90 seconds
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206316 https://bugzilla.suse.com/show_bug.cgi?id=1206316#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- If i915 driver isn't included in initrd automatically even if it's a valid graphics, then that's the problem to be addressed at first. The manual tweak like yours might have some side effect, so likely a WONTFIX issue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206745] Unnecessary log entries for rtkit
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206745 https://bugzilla.suse.com/show_bug.cgi?id=1206745#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Component|Kernel |Basesystem Assignee|kernel-bugs(a)opensuse.org |sreeves(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Reassigned to rtkit package maintainer. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206774] dvb driver fails
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Gerhard(a)Dr-Lorbeer.de, | |tiwai(a)suse.com Flags| |needinfo?(Gerhard@Dr-Lorbee | |r.de) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you give dmesg outputs from both working and non-working cases? Also give the hwinfo outputs from both, too. Please upload the outputs as Bugzilla attachments. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Is it a regression from the earlier releases? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206774] New: dvb driver fails
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206774 Bug ID: 1206774 Summary: dvb driver fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: Gerhard(a)Dr-Lorbeer.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since kernel 6.1.n dvb-driver for older cards (eg SAA7146) failed to load. These cards are installed in many installations of long living vdr's. With new kernel all dvb-server with these cards are bricked. Test to verifiy: Boot with older kernel: driver OK Boot with newer kernel: fail -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206683] kernel 6.1.1 freezes before the gui appears
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206683 https://bugzilla.suse.com/show_bug.cgi?id=1206683#c42 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #42 from Takashi Iwai <tiwai(a)suse.com> --- OK, the fix for the original WiFi problem from Scott has been merged to stable branch for the next TW kernel (along with 6.1.2 update). For rtw88 issue for Dave, it's tracked in another bug 1206767. Let's close the bug entry now. -- You are receiving this mail because: You are the assignee for the bug.

1 0