December 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1205774] New: Kernel 6.0.8 + nvidia 525.53 crash on BUG: kernel NULL pointer dereference, #PF: supervisor instruction fetch in kernel mode
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205774 Bug ID: 1205774 Summary: Kernel 6.0.8 + nvidia 525.53 crash on BUG: kernel NULL pointer dereference, #PF: supervisor instruction fetch in kernel mode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bruno(a)ioda-net.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863125 --> http://bugzilla.opensuse.org/attachment.cgi?id=863125&action=edit Last kernel 6.0.8 boot and crash Hello I need help to find the root cause of crashes (complete freeze of the workstation). Since the introduction of kernel 6.0.8 and latest nvidia 525.53 I constantly face complete machine freeze, when I'm using my external monitors. nov 25 16:05:34 qt-kt kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 nov 25 16:05:34 qt-kt kernel: #PF: supervisor instruction fetch in kernel mode nov 25 16:05:34 qt-kt kernel: #PF: error_code(0x0010) - not-present page nov 25 16:05:34 qt-kt kernel: PGD 0 P4D 0 nov 25 16:05:34 qt-kt kernel: Oops: 0010 [#1] PREEMPT SMP PTI nov 25 16:05:34 qt-kt kernel: CPU: 3 PID: 1004 Comm: nvidia-modeset/ Tainted: P OE 6.0.8-1-default #1 openSUSE Tumbleweed 9d20364b934f5aab0a9bdf84e8f45cfdfae39dab nov 25 16:05:34 qt-kt kernel: Hardware name: Dell Inc. Precision 7510/0YH43H, BIOS 1.29.3 09/18/2022 nov 25 16:05:34 qt-kt kernel: RIP: 0010:0x0 nov 25 16:05:34 qt-kt kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6. nov 25 16:05:34 qt-kt kernel: RSP: 0018:ffffadc300703c90 EFLAGS: 00010207 nov 25 16:05:34 qt-kt kernel: RAX: 0000000000000000 RBX: ffff9b2996c75378 RCX: 0000000000000004 nov 25 16:05:34 qt-kt kernel: RDX: 0000000000000010 RSI: ffff9b2996c75378 RDI: ffffadc300703a10 nov 25 16:05:34 qt-kt kernel: RBP: ffff9b292ef8b560 R08: 0000000000000000 R09: 0000000000000040 nov 25 16:05:34 qt-kt kernel: R10: ffff9b2886b28008 R11: ffffadc300703c00 R12: 0000000000000000 nov 25 16:05:34 qt-kt kernel: R13: 0000000000000000 R14: ffffffffc4fbee70 R15: ffffffffc4eb7580 nov 25 16:05:34 qt-kt kernel: FS: 0000000000000000(0000) GS:ffff9b37c44c0000(0000) knlGS:0000000000000000 nov 25 16:05:34 qt-kt kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 nov 25 16:05:34 qt-kt kernel: CR2: ffffffffffffffd6 CR3: 000000075be10001 CR4: 00000000003706e0 nov 25 16:05:34 qt-kt kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 nov 25 16:05:34 qt-kt kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 nov 25 16:05:34 qt-kt kernel: Call Trace: nov 25 16:05:34 qt-kt kernel: <TASK> nov 25 16:05:34 qt-kt kernel: _nv001281kms+0x194/0x1a0 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv001274kms+0x9a/0xd0 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv001466kms+0x172/0x180 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv001149kms+0xf3/0xa50 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? schedule+0x5a/0xd0 nov 25 16:05:34 qt-kt kernel: ? schedule_timeout+0x10e/0x150 nov 25 16:05:34 qt-kt kernel: ? nvkms_sema_up+0x10/0x10 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? __down_common+0x10b/0x1e0 nov 25 16:05:34 qt-kt kernel: ? nvkms_sema_up+0x10/0x10 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv002457kms+0x2d/0x70 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? nvkms_kthread_q_callback+0x88/0xf0 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _main_loop+0x77/0x130 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? kthread+0xd7/0x100 nov 25 16:05:34 qt-kt kernel: ? kthread_complete_and_exit+0x20/0x20 nov 25 16:05:34 qt-kt kernel: ? ret_from_fork+0x1f/0x30 nov 25 16:05:34 qt-kt kernel: </TASK> nov 25 16:05:34 qt-kt kernel: Modules linked in: rfcomm snd_seq_dummy snd_hrtimer snd_seq nf_nat_sip nft_objref af_packet nf_conntrack_sip nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct n> nov 25 16:05:34 qt-kt kernel: processor_thermal_device_pci_legacy irqbypass iwlwifi processor_thermal_device pcspkr ledtrig_audio processor_thermal_rfim snd_usbmidi_lib efi_pstore snd_intel_sdw_acpi sparse_keymap processor_thermal_mbox cdc_wdm videob> nov 25 16:05:34 qt-kt kernel: fuse configfs dmi_sysfs ip_tables x_tables cmac algif_hash algif_skcipher af_alg hid_logitech_hidpp hid_logitech_dj hid_generic dm_crypt usbhid essiv authenc trusted asn1_encoder tee bnep btusb btrtl btbcm btintel btmtk > nov 25 16:05:34 qt-kt kernel: CR2: 0000000000000000 nov 25 16:05:34 qt-kt kernel: ---[ end trace 0000000000000000 ]--- Most of the time this happen after resuming the screens, the primary one get on, but the second is always in suspend mode, I have to open neither display settings in plasma or nvidia-settings to set on the second monitor (displayport slave link) after switching off and on the monitor. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1206058] New: Leap 15.4 kernel do not work on a RX 5700 XT
by bugzilla_noreply＠suse.com 06 Dec '22

06 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206058 Bug ID: 1206058 Summary: Leap 15.4 kernel do not work on a RX 5700 XT 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: giuliano.belinassi(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The current kernel in openSUSE leap 15.4 do not work on AMD RX 5700 XT, and I assume it doesn't work on all generations of AMD RDNA1 and RDNA2 cards as well. The kernel loops printing the following message: PCIe bus error: severity=Uncorrected (Non-fatal), type=Transactional Layer device [1002:1479] error status/mask=00100000/00000000 Unsup Req (First) Loading Leap 15.4 installer with AMDGPU driver loaded results in a crash after the graphics screen is loaded. Switching to CTRL-ALT-F1 it reports: gzip: stdout: No space left on device Switching to CTRL-ALT-F4 it reports the PCIe bus error mentioned above. Blacklisting the AMDGPU driver results in the installer loading correctly. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1206106] New: [Build 345.2] hung system on ppc64le
by bugzilla_noreply＠suse.com 06 Dec '22

06 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206106 Bug ID: 1206106 Summary: [Build 345.2] hung system on ppc64le Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: LittleEndian URL: https://openqa.opensuse.org/tests/2926909/modules/user _gui_login/steps/16 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation # wait_serial expected: qr/sysrq\s*:\s+show\s+blocked\s+state/i # Result: [ 2029.551933][ C2] sysrq: Show State [ 2029.899886][ C2] sysrq: Show Blocked State openQA test in scenario opensuse-15.5-DVD-ppc64le-gnome@ppc64le fails in [user_gui_login](https://openqa.opensuse.org/tests/2926909/modules/user_gui_… ## Test suite description Revert schedule to working settings - dleuenberger, 20211117 ## Reproducible Fails since (at least) Build [332.1](https://openqa.opensuse.org/tests/2896364) ## Expected result Last good: [330.2](https://openqa.opensuse.org/tests/2894666) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=ppc64le&distri=opensu… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205891] System freeze
by bugzilla_noreply＠suse.com 06 Dec '22

06 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205891 https://bugzilla.suse.com/show_bug.cgi?id=1205891#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- That's interesting. Can any try to downgrade systemd from TW history repo and verify whether it fixes the problem or not? http://download.opensuse.org/history/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206084] New: pynfs fails in test nfs4.0 on x86-64 and aarch64
by bugzilla_noreply＠suse.com 06 Dec '22

06 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206084 Bug ID: 1206084 Summary: pynfs fails in test nfs4.0 on x86-64 and aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: yosun(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There have some failures on pynfs test(nfs_pynfs_nfs40_all) in openqa.opensuse.org Tumbleweed tests. The fails only in x86_64 and aarch64, and all ppc64le passed. x86_64: https://openqa.opensuse.org/tests/2927483#next_previous aarch64: https://openqa.opensuse.org/tests/2928317#next_previous ppc64le: https://openqa.opensuse.org/tests/2926634#next_previous The fails contains following logs: nfs4lib.BadCompoundRes: operation OP_SETCLIENTID should return NFS4_OK, instead got NFS4ERR_DELAY e.g. https://openqa.opensuse.org/tests/2927483#step/run/9 [version] pynfs: d09d098ccd17a40bf44a21c6ec749d9c96447969 (could also use latest in git://git.linux-nfs.org/projects/bfields/pynfs.git) nfs-kernel-server-2.6.2-36.1 [steps] Install some dependency: git krb5-devel python3-devel swig python3-gssapi python3-ply nfs-client nfs-kernel-server Then setup nfs4.0 server env and trigger all tests. (./testserver.py -v --rundeps --hidepass --json results.json --maketree localhost:/exportdir all) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205259] WIth kernel 6.0.7-1 on raspberry pi400 nothing displayed on HDMI ports
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205259 https://bugzilla.suse.com/show_bug.cgi?id=1205259#c13 --- Comment #13 from Scott Bradnick <scott.bradnick(a)suse.com> --- (In reply to Ivan Ivanov from comment #12) > (In reply to Scott Bradnick from comment #11) > > Now on VERSION="20221202" (6.0.10-1-default) my RPi4's HDMI is behaving as > > it did before, thanks! > > And by this you mean it is working again? Correct -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206033] Missing dependency after package split suse-module-tools/suse-module-tools-scriplets
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206033 https://bugzilla.suse.com/show_bug.cgi?id=1206033#c2 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Ludwig Nussel <lnussel(a)suse.com> --- your package lacks "BuildRequires: %kernel_module_package_buildreqs" *** This bug has been marked as a duplicate of bug 1205149 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205149] %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205149 https://bugzilla.suse.com/show_bug.cgi?id=1205149#c15 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner(a)suse.com --- Comment #15 from Ludwig Nussel <lnussel(a)suse.com> --- *** Bug 1206033 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205149] %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205149 https://bugzilla.suse.com/show_bug.cgi?id=1205149#c13 --- Comment #13 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Ludwig Nussel from comment #10) > No, the failing packages just lack "BuildRequires: > %kernel_module_package_buildreqs" and need to be fixed. Indeed. Strange that this hasn't caused errors earlier. It's documented that this is required for KMPs since SLE11. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205149] %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205149 https://bugzilla.suse.com/show_bug.cgi?id=1205149#c12 --- Comment #12 from Ludwig Nussel <lnussel(a)suse.com> --- crash https://build.opensuse.org/request/show/1040305 drbd https://build.opensuse.org/request/show/1040304 pcfclock https://build.opensuse.org/request/show/1040303 vhba-kmp https://build.opensuse.org/request/show/1040302 -- You are receiving this mail because: You are the assignee for the bug.

1 0