You are not logged in.

#26 2021-08-29 15:19:16

loqs
Member
Registered: 2014-03-06
Posts: 17,196

Re: kernel panic with linux-hardened-5.13.13

That explains what is happening.  linux-hardened's use of CONFIG_PANIC_ON_OOPS results in an OOPS in amdgpu triggering a kernel panic which ends execution.
What is causing the OOPS needs further investigation.
Edit:
https://drive.google.com/file/d/1x6gCti … sp=sharing linux-5.13.13.arch1-3-x86_64.pkg.tar.zst linux-hardened config with CONFIG_PANIC_ON_OOPS not set.

Last edited by loqs (2021-08-29 16:03:34)

Offline

#27 2021-08-30 11:03:04

TheBPN
Member
Registered: 2021-08-28
Posts: 18

Re: kernel panic with linux-hardened-5.13.13

Hi,

First try with my default kernel boot parameters:

-- Journal begins at Mon 2021-08-23 13:00:40 UTC, ends at Mon 2021-08-30 10:57:01 UTC. --
Aug 30 10:51:28 xx kernel: Linux version 5.13.13-arch1-3 (linux@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Sun, 29 Aug 2021 15:42:25 +0000
Aug 30 10:51:28 xx kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=c97b6628-f326-4cbb-bc8e-cff3ba9dd301 rw cryptdevice=/dev/nvme0n1p2:cryptroot:allow-discards root=/dev/mapper/cryptroot mem_encrypt=off ipv6.disable=1 msr.allow_writes=on l1tf=full, force mds=full,nosmt mitigations=auto,nosmt nosmt=force loglevel=3 quiet
Aug 30 10:51:28 xx kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Aug 30 10:51:28 xx kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Aug 30 10:51:28 xx kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Aug 30 10:51:28 xx kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Aug 30 10:51:28 xx kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Aug 30 10:51:28 xx kernel: BIOS-provided physical RAM map:
.
.
Aug 30 10:52:00 xx systemd[1]: Stopped Create Volatile Files and Directories.
Aug 30 10:52:00 xx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? ter>
Aug 30 10:52:00 xx systemd[1]: Stopped target Local File Systems.
Aug 30 10:52:00 xx systemd[1]: Unmounting /boot...
Aug 30 10:52:00 xx systemd[1]: Unmounting /run/credentials/systemd-sysusers.service...
Aug 30 10:52:00 xx systemd[1]: Unmounting Temporary Directory /tmp...
Aug 30 10:52:00 xx systemd[1]: run-credentials-systemd\x2dsysusers.service.mount: Deactivated successfully.
Aug 30 10:52:00 xx systemd[1]: Unmounted /run/credentials/systemd-sysusers.service.
Aug 30 10:52:00 xx systemd[1]: boot.mount: Deactivated successfully.
Aug 30 10:52:00 xx systemd[1]: Unmounted /boot.
Aug 30 10:52:00 xx systemd[1]: tmp.mount: Deactivated successfully.
Aug 30 10:52:00 xx systemd[1]: Unmounted Temporary Directory /tmp.
Aug 30 10:52:00 xx systemd[1]: Stopped target Swaps.
Aug 30 10:52:00 xx systemd[1]: Reached target Unmount All Filesystems.
Aug 30 10:52:00 xx systemd[1]: systemd-fsck@dev-disk-by\x2duuid-be97ea89\x2d19a8\x2d4a3d\x2db82a\x2d7ed158d221a6.service: Deactivated successfully.
Aug 30 10:52:00 xx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-be97ea89\x2d19a8\x2d4a3d\x2db82a\x2d7ed158d221a6 comm="sy>
Aug 30 10:52:00 xx systemd[1]: Stopped File System Check on /dev/disk/by-uuid/be97ea89-19a8-4a3d-b82a-7ed158d221a6.
Aug 30 10:52:00 xx systemd[1]: Removed slice Slice /system/systemd-fsck.
Aug 30 10:52:00 xx systemd[1]: Stopped target Preparation for Local File Systems.
Aug 30 10:52:00 xx systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Aug 30 10:52:00 xx systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
Aug 30 10:52:00 xx systemd[1]: Stopped Create Static Device Nodes in /dev.
Aug 30 10:52:00 xx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Aug 30 10:52:00 xx systemd[1]: systemd-sysusers.service: Deactivated successfully.
Aug 30 10:52:00 xx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysusers comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=>
Aug 30 10:52:00 xx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termina>
Aug 30 10:52:00 xx systemd[1]: Stopped Create System Users.
Aug 30 10:52:00 xx systemd[1]: systemd-remount-fs.service: Deactivated successfully.
Aug 30 10:52:00 xx systemd[1]: Stopped Remount Root and Kernel File Systems.
Aug 30 10:52:00 xx systemd[1]: lvm2-monitor.service: Deactivated successfully.
Aug 30 10:52:00 xx systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Aug 30 10:52:00 xx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re>
Aug 30 10:52:00 xx systemd[1]: Reached target System Shutdown.
Aug 30 10:52:00 xx systemd[1]: Reached target Late Shutdown Services.
Aug 30 10:52:00 xx systemd[1]: systemd-poweroff.service: Deactivated successfully.
Aug 30 10:52:00 xx systemd[1]: Finished System Power Off.
Aug 30 10:52:00 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal>
Aug 30 10:52:00 xx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=>
Aug 30 10:52:00 xx systemd[1]: Reached target System Power Off.
Aug 30 10:52:00 xx systemd[1]: Shutting down.
Aug 30 10:52:00 xx audit: BPF prog-id=5 op=UNLOAD
Aug 30 10:52:00 xx audit: BPF prog-id=4 op=UNLOAD
Aug 30 10:52:00 xx audit: BPF prog-id=3 op=UNLOAD
Aug 30 10:52:00 xx audit: BPF prog-id=8 op=UNLOAD
Aug 30 10:52:00 xx audit: BPF prog-id=7 op=UNLOAD
Aug 30 10:52:00 xx audit: BPF prog-id=6 op=UNLOAD
Aug 30 10:52:00 xx systemd-shutdown[1]: Syncing filesystems and block devices.
Aug 30 10:52:00 xx systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Aug 30 10:52:00 xx systemd-journald[433]: Journal stopped
lines 1560-1608/1608 (END)

Second try with the kernel boot parameters you gave me yesterday:

-- Journal begins at Mon 2021-08-23 13:00:40 UTC, ends at Mon 2021-08-30 10:57:51 UTC. --
Aug 30 10:54:16 xx kernel: Linux version 5.13.13-arch1-3 (linux@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Sun, 29 Aug 2021 15:42:25 +0000
Aug 30 10:54:16 xx kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=c97b6628-f326-4cbb-bc8e-cff3ba9dd301 rw cryptdevice=/dev/nvme0n1p2:cryptroot:allow-discards root=/dev/mapper/cryptroot mem_encrypt=off ipv6.disable=1 msr.allow_writes=on pti=off page_alloc.shuffle=0 init_on_free=0 mitigations=off page_poison=0 loglevel=3 quiet
Aug 30 10:54:16 xx kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Aug 30 10:54:16 xx kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Aug 30 10:54:16 xx kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Aug 30 10:54:16 xx kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Aug 30 10:54:16 xx kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Aug 30 10:54:16 xx kernel: BIOS-provided physical RAM map:
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009d7ffff] usable
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x0000000009d80000-0x0000000009ffffff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x000000000a000000-0x00000000db391fff] usable
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000db392000-0x00000000dc87afff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000dc87b000-0x00000000dc8acfff] ACPI data
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000dc8ad000-0x00000000dcd8cfff] ACPI NVS
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000dcd8d000-0x00000000dd7d1fff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000dd7d2000-0x00000000deffffff] usable
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000fdf00000-0x00000000fdffffff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Aug 30 10:54:16 xx kernel: BIOS-e820: [mem 0x0000000100000000-0x000000081f37ffff] usable
Aug 30 10:54:16 xx kernel: NX (Execute Disable) protection: active
Aug 30 10:54:16 xx kernel: SMBIOS 3.0.0 present.
Aug 30 10:54:16 xx kernel: DMI: ASUSTeK COMPUTER INC. GL702ZC/GL702ZC, BIOS GL702ZC.306 07/05/2019
Aug 30 10:54:16 xx kernel: tsc: Fast TSC calibration failed
Aug 30 10:54:16 xx kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Aug 30 10:54:16 xx kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Aug 30 10:54:16 xx kernel: last_pfn = 0x81f380 max_arch_pfn = 0x400000000
Aug 30 10:54:16 xx kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
Aug 30 10:54:16 xx kernel: total RAM covered: 3568M
Aug 30 10:54:16 xx kernel: Found optimal setting for mtrr clean up
Aug 30 10:54:16 xx kernel:  gran_size: 64K         chunk_size: 1G         num_reg: 3          lose cover RAM: 0G
Aug 30 10:54:16 xx kernel: e820: update [mem 0xdf000000-0xffffffff] usable ==> reserved
Aug 30 10:54:16 xx kernel: last_pfn = 0xdf000 max_arch_pfn = 0x400000000
Aug 30 10:54:16 xx kernel: Using GB pages for direct mapping
lines 1-49
.
.
Aug 30 10:54:41 xx systemd[1]: Stopped Remount Root and Kernel File Systems.
Aug 30 10:54:41 xx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termina>
Aug 30 10:54:41 xx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Aug 30 10:54:41 xx systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
Aug 30 10:54:41 xx systemd[1]: Stopped Create Static Device Nodes in /dev.
Aug 30 10:54:41 xx systemd[1]: lvm2-monitor.service: Deactivated successfully.
Aug 30 10:54:41 xx systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Aug 30 10:54:41 xx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re>
Aug 30 10:54:41 xx systemd[1]: Reached target System Shutdown.
Aug 30 10:54:41 xx systemd[1]: Reached target Late Shutdown Services.
Aug 30 10:54:41 xx systemd[1]: systemd-poweroff.service: Deactivated successfully.
Aug 30 10:54:41 xx systemd[1]: Finished System Power Off.
Aug 30 10:54:41 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal>
Aug 30 10:54:41 xx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=>
Aug 30 10:54:41 xx systemd[1]: Reached target System Power Off.
Aug 30 10:54:41 xx systemd[1]: Shutting down.
Aug 30 10:54:41 xx audit: BPF prog-id=5 op=UNLOAD
Aug 30 10:54:41 xx audit: BPF prog-id=4 op=UNLOAD
Aug 30 10:54:41 xx audit: BPF prog-id=3 op=UNLOAD
Aug 30 10:54:41 xx audit: BPF prog-id=8 op=UNLOAD
Aug 30 10:54:41 xx audit: BPF prog-id=7 op=UNLOAD
Aug 30 10:54:41 xx audit: BPF prog-id=6 op=UNLOAD
Aug 30 10:54:41 xx systemd-shutdown[1]: Syncing filesystems and block devices.
Aug 30 10:54:41 xx systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Aug 30 10:54:41 xx systemd-journald[443]: Journal stopped
lines 1564-1612/1612 (END)

Offline

#28 2021-08-30 11:15:33

TheBPN
Member
Registered: 2021-08-28
Posts: 18

Re: kernel panic with linux-hardened-5.13.13

I am willing to create the Bug Report, and I just created a https://bugs.archlinux.org account.
Also I am able to find the package and see the open bug reports.
But I do not know how to create a new bug report.
Also, I do not know how to **caracterize** the problem properly.
Would you be willing to create it?

I could help you to try kernel_parameters / kernels combinations if needed.

Regards.

Last edited by TheBPN (2021-08-30 11:16:14)

Offline

#29 2021-08-30 23:01:51

loqs
Member
Registered: 2014-03-06
Posts: 17,196

Re: kernel panic with linux-hardened-5.13.13

Just to confirm the boots in #27 were both successful?  If they were can you try https://aur.archlinux.org/packages/linux-mainline/ link see pinned comment in link to repo version if you prefer that to self building.  To see if the issue has already been fixed upstream.
The problem appears to be an issue in the amdgpu module which causes an OOPS which is not fatal unless combined with CONFIG_PANIC_ON_OOPS which is only set in linux-hardened as one of its hardening measures.
Edit:
You will need to use the boot parameter oops=panic with 5.14 to replicate the option linux-hardened uses.

Last edited by loqs (2021-08-30 23:06:12)

Offline

#30 2021-08-31 03:29:22

JonL
Member
Registered: 2021-06-05
Posts: 7

Re: kernel panic with linux-hardened-5.13.13

Reverting the following debugfs changes seems to have corrected all my stability issues from these past few months.

7271a5c2aefc142ba9380842c58fea6c47fc635d
98d28ac2f511a29d608326e50e3b1061ec18e9f
373720f79d56697f0f63cbda50111d6eb6dbad2f
afd3a359c452c5ee529a6b1d660ebf1176765463
88293c03c87e4db28890dd4e4ccb3640eadb4a08

Offline

#31 2021-08-31 03:48:24

loqs
Member
Registered: 2014-03-06
Posts: 17,196

Re: kernel panic with linux-hardened-5.13.13

@JonL can you please report your findings to https://gitlab.freedesktop.org/drm/amd/-/issues/1686 thanks

Offline

#32 2021-08-31 15:30:54

TheBPN
Member
Registered: 2021-08-28
Posts: 18

Re: kernel panic with linux-hardened-5.13.13

loqs wrote:

Just to confirm the boots in #27 were both successful?  If they were can you try https://aur.archlinux.org/packages/linux-mainline/ link see pinned comment in link to repo version if you prefer that to self building.  To see if the issue has already been fixed upstream.
The problem appears to be an issue in the amdgpu module which causes an OOPS which is not fatal unless combined with CONFIG_PANIC_ON_OOPS which is only set in linux-hardened as one of its hardening measures.
Edit:
You will need to use the boot parameter oops=panic with 5.14 to replicate the option linux-hardened uses.


Hi,

Nope those two boots were not successull.
Or may be I am not very clear right now.
After the system did not do anything more, I pressed the power button then the system stoped.
So it didn't work properly but the system didn't frooze.
Hope I answered "clearly enough" to your question.

Id needed could you please build me a 5.14 kernel with all CONFIG you want, then make a PKG ?
I could test them.

Last edited by TheBPN (2021-08-31 15:49:37)

Offline

#33 2021-08-31 22:08:32

loqs
Member
Registered: 2014-03-06
Posts: 17,196

Re: kernel panic with linux-hardened-5.13.13

@JonL What commit did you start your revert from?  Using 5.13.13 I could not revert afd3a359c452c5ee529a6b1d660ebf1176765463 cleanly:

git describe 
v5.13.13
git revert -n 7271a5c2aefc142ba9380842c58fea6c47fc635d 98d28ac2f511a29d608326e50e3b1061ec18e9f 373720f79d56697f0f63cbda50111d6eb6dbad2f afd3a359c452c5ee529a6b1d660ebf1176765463 88293c03c87e4db28890dd4e4ccb3640eadb4a08
Auto-merging drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
Auto-merging drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h
Auto-merging drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
Auto-merging drivers/gpu/drm/amd/amdgpu/amdgpu_object.h
Auto-merging drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c
Auto-merging drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c
Auto-merging drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
Auto-merging drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
Auto-merging drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
Auto-merging drivers/gpu/drm/amd/amdgpu/amdgpu.h
Auto-merging drivers/gpu/drm/amd/pm/amdgpu_pm.c
Auto-merging drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
Auto-merging drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_debugfs.h
CONFLICT (content): Merge conflict in drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_debugfs.h
Auto-merging drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_debugfs.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_debugfs.c
Auto-merging drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
error: could not revert afd3a359c452... drm/amd/display: do not use drm middle layer for debugfs

@TheBPN thank you for the clarification,  the next test disables debugfs,  if the issue is in amdgpu's debugfs entries then disabling debugfs should avoid the issue
https://drive.google.com/file/d/1lxabrV … sp=sharing linux-hardened-5.13.13.hardened1-3-x86_64.pkg.tar.zst
Edit:
The kernel parameter debugfs=off if it works would save you having to install another test kernel.

Last edited by loqs (2021-08-31 22:26:32)

Offline

#34 2021-09-01 10:35:46

TheBPN
Member
Registered: 2021-08-28
Posts: 18

Re: kernel panic with linux-hardened-5.13.13

Booting the kernel local/linux-hardened 5.13.13.hardened1-1
with the kernel boot parameter debugfs=off does not workaround the issue, so it does not boot but hangs as with other try before.

- Journal begins at Mon 2021-08-23 13:41:07 UTC, ends at Wed 2021-09-01 10:31:45 UTC. --
Sep 01 10:28:55 xx kernel: Linux version 5.13.13-hardened1-1-hardened (linux-hardened@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Thu, 26 Aug 2021 20:57:19 +0000
Sep 01 10:28:55 xx kernel: Command line: BOOT_IMAGE=/vmlinuz-linux-hardened root=UUID=c97b6628f326-4cbb-bc8e-cff3ba9dd301 rw cryptdevice=/dev/nvme0n1p2:cryptroot:allow-discards root=/dev/mapper/cryptroot mem_encrypt=off ipv6.disable=1 msr.allow_writes=on l1tf=full, force mds=full,nosmt mitigations=auto,nosmt nosmt=force loglevel=3 quiet debugfs=off
Sep 01 10:28:55 xx kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Sep 01 10:28:55 xx kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Sep 01 10:28:55 xx kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
.
.
Sep 01 10:28:55 xx systemd[1]: Starting Create Static Device Nodes in /dev...
Sep 01 10:28:55 xx systemd[1]: Finished Load Kernel Modules.
Sep 01 10:28:55 xx kernel: audit: type=1130 audit(1630492135.388:7): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/syste>
Sep 01 10:28:55 xx systemd[1]: Starting Apply Kernel Variables...
Sep 01 10:28:55 xx systemd[1]: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Sep 01 10:28:55 xx kernel: audit: type=1130 audit(1630492135.392:8): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" host>
Sep 01 10:28:55 xx systemd[1]: Finished Apply Kernel Variables.
Sep 01 10:28:55 xx kernel: audit: type=1130 audit(1630492135.395:9): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" ho>
Sep 01 10:28:55 xx systemd[1]: Finished Create Static Device Nodes in /dev.
Sep 01 10:28:55 xx kernel: audit: type=1130 audit(1630492135.415:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/system>
Sep 01 10:28:55 xx systemd[1]: Reached target Preparation for Local File Systems.
Sep 01 10:28:55 xx systemd[1]: Condition check resulted in Virtual Machine and Container Storage (Compatibility) being skipped.
Sep 01 10:28:55 xx kernel: audit: type=1334 audit(1630492135.415:11): prog-id=6 op=LOAD
Sep 01 10:28:55 xx systemd[1]: Starting Rule-based Manager for Device Events and Files...
Sep 01 10:28:55 xx systemd-journald[436]: Journal started
Sep 01 10:28:55 xx systemd-journald[436]: Runtime Journal (/run/log/journal/fa692dd7c37147518bc63870768c8efb) is 8.0M, max 1.5G, 1.5G free.
Sep 01 10:28:55 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termin>
Sep 01 10:28:55 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termi>
Sep 01 10:28:55 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? r>
Sep 01 10:28:55 xx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re>
Sep 01 10:28:55 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysusers comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal>
Sep 01 10:28:55 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? term>
Sep 01 10:28:55 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? r>
Sep 01 10:28:55 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?>
Sep 01 10:28:55 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=>
Sep 01 10:28:55 xx audit: BPF prog-id=6 op=LOAD
Sep 01 10:28:55 xx audit: BPF prog-id=7 op=LOAD
Sep 01 10:28:55 xx audit: BPF prog-id=8 op=LOAD
Sep 01 10:28:55 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal>
Sep 01 10:28:55 xx systemd-modules-load[437]: Inserted module 'sg'
Sep 01 10:28:55 xx systemd-modules-load[437]: Inserted module 'vboxdrv'
Sep 01 10:28:55 xx systemd-modules-load[437]: Inserted module 'vboxnetadp'
Sep 01 10:28:55 xx systemd-modules-load[437]: Inserted module 'vboxnetflt'
Sep 01 10:28:55 xx systemd[1]: Starting Flush Journal to Persistent Storage...
Sep 01 10:28:55 xx systemd[1]: Started Journal Service.
Sep 01 10:28:55 xx systemd-journald[436]: Time spent on flushing to /var/log/journal/fa692dd7c37147518bc63870768c8efb is 8.686ms for 960 entries.
lines 914-962/962 (END)

I gonna try with the kernel that you last posted in GoogleDrive.
Will be back in a couple of minutes to tell you.

Offline

#35 2021-09-01 10:48:06

TheBPN
Member
Registered: 2021-08-28
Posts: 18

Re: kernel panic with linux-hardened-5.13.13

@loqs your customized kernel boots without I change my /etc/default/grub kernel boot parameters !!!
Good job.

-- Journal begins at Mon 2021-08-23 13:41:07 UTC, ends at Wed 2021-09-01 10:43:48 UTC. --
Sep 01 10:39:41 xx kernel: Linux version 5.13.13-hardened1-3-hardened (linux-hardened@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Tue, 31 Aug 2021 21:40:52 +0000
Sep 01 10:39:41 xx kernel: Command line: BOOT_IMAGE=/vmlinuz-linux-hardened root=UUID=c97b628-f326-4cbb-bc8e-cff3ba9dd301 rw cryptdevice=/dev/nvme0n1p2:cryptroot:allow-discards root=/dev/mapper/cryptroot mem_encrypt=off ipv6.disable=1 msr.allow_writes=on l1tf=full, force mds=full,nosmt mitigations=auto,nosmt nosmt=force loglevel=3 quiet
Sep 01 10:39:41 xx kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Sep 01 10:39:41 xx kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Sep 01 10:39:41 xx kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Sep 01 10:39:41 xx kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Sep 01 10:39:41 xx kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
.
.
.
Sep 01 10:43:48 xx wpa_supplicant[666]: wlp7s0: CTRL-EVENT-BEACON-LOSS
lines 1766-1814/1814 (END)

Regards.

Offline

#36 2021-09-01 15:27:46

loqs
Member
Registered: 2014-03-06
Posts: 17,196

Re: kernel panic with linux-hardened-5.13.13

https://drive.google.com/file/d/1ob-t9w … sp=sharing linux-hardened-5.13.13.hardened1-4-x86_64.pkg.tar.zst
This test checks some pointers before dereferencing them,  it will print an error message if any of the pointers is null and return from the function.

diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
index d5cbc51c5eaa..34e3923010f8 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
@@ -2379,8 +2379,29 @@ static const struct file_operations amdgpu_ttm_iomem_fops = {
 void amdgpu_ttm_debugfs_init(struct amdgpu_device *adev)
 {
 #if defined(CONFIG_DEBUG_FS)
-	struct drm_minor *minor = adev_to_drm(adev)->primary;
-	struct dentry *root = minor->debugfs_root;
+	struct drm_minor *minor;
+	struct dentry *root;
+	struct drm_device *ddev;
+
+	if(!adev) {
+		pr_err("adev is null\n");
+		return;
+	}
+	ddev = adev_to_drm(adev);
+	if(!ddev) {
+		pr_err("ddev is null\n");
+		return;
+	}
+	minor = ddev->primary;
+	if (!minor) {
+		pr_err("minor is null\n");
+		return;
+	}
+	root = minor->debugfs_root;
+	if (!root) {
+		pr_err("root is null\n");
+		return;
+	}
 
 	debugfs_create_file_size("amdgpu_vram", 0444, root, adev,
 				 &amdgpu_ttm_vram_fops, adev->gmc.mc_vram_size);

Offline

#37 2021-09-01 16:42:51

TheBPN
Member
Registered: 2021-08-28
Posts: 18

Re: kernel panic with linux-hardened-5.13.13

I am not able to boot the last kernel.
I don't know whether I had to change kernel boot parameters therefore I haven't changed anything:

-- Journal begins at Mon 2021-08-23 13:56:18 UTC, ends at Wed 2021-09-01 16:39:12 UTC. --
Sep 01 16:36:49 xx kernel: Linux version 5.13.13-hardened1-4-hardened (linux-hardened@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Wed, 01 Sep 2021 14:59:2>
Sep 01 16:36:49 xx kernel: Command line: BOOT_IMAGE=/vmlinuz-linux-hardened root=UUID=c97b6628-f326-4cbb-bc8e-cff3ba9dd301 rw cryptdevice=/dev/nvme0n1p2:cryptroot:allow-discards root=/dev/mapper/cryptroot mem_encrypt=off ipv6.disable=1 msr.allow_writes=on l1tf=full, force mds=full,nosmt mitigations=auto,nosmt nosmt=force loglevel=3 quiet
Sep 01 16:36:49 xx kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Sep 01 16:36:49 xx kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Sep 01 16:36:49 xx kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Sep 01 16:36:49 xx kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Sep 01 16:36:49 xx kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Sep 01 16:36:49 xx kernel: BIOS-provided physical RAM map:
.
.
Sep 01 16:36:49 xx systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Sep 01 16:36:49 xx systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Sep 01 16:36:49 xx systemd[1]: Starting Load/Save Random Seed...
Sep 01 16:36:49 xx systemd[1]: Starting Apply Kernel Variables...
Sep 01 16:36:49 xx systemd[1]: Starting Create System Users...
Sep 01 16:36:49 xx systemd[1]: Finished Set Up Additional Binary Formats.
Sep 01 16:36:49 xx kernel: audit: type=1130 audit(1630514209.868:4): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-binfmt comm="systemd" exe="/usr/lib/systemd/systemd" ho>
Sep 01 16:36:49 xx systemd[1]: Finished Apply Kernel Variables.
Sep 01 16:36:49 xx kernel: audit: type=1130 audit(1630514209.871:5): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" ho>
Sep 01 16:36:49 xx systemd[1]: Finished Load/Save Random Seed.
Sep 01 16:36:49 xx kernel: audit: type=1130 audit(1630514209.874:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/system>
Sep 01 16:36:49 xx systemd[1]: Condition check resulted in First Boot Complete being skipped.
Sep 01 16:36:49 xx systemd[1]: modprobe@drm.service: Deactivated successfully.
Sep 01 16:36:49 xx systemd[1]: Finished Load Kernel Module drm.
Sep 01 16:36:49 xx kernel: audit: type=1130 audit(1630514209.874:7): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" host>
Sep 01 16:36:49 xx kernel: audit: type=1131 audit(1630514209.874:8): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" host>
Sep 01 16:36:49 xx systemd[1]: Finished Create System Users.
Sep 01 16:36:49 xx kernel: audit: type=1130 audit(1630514209.894:9): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysusers comm="systemd" exe="/usr/lib/systemd/systemd" >
Sep 01 16:36:49 xx systemd[1]: Starting Create Static Device Nodes in /dev...
Sep 01 16:36:49 xx systemd[1]: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Sep 01 16:36:49 xx kernel: audit: type=1130 audit(1630514209.894:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hos>
Sep 01 16:36:49 xx systemd[1]: Finished Create Static Device Nodes in /dev.
Sep 01 16:36:49 xx kernel: audit: type=1130 audit(1630514209.918:11): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/system>
Sep 01 16:36:49 xx systemd[1]: Reached target Preparation for Local File Systems.
Sep 01 16:36:49 xx systemd[1]: Condition check resulted in Virtual Machine and Container Storage (Compatibility) being skipped.
Sep 01 16:36:49 xx systemd[1]: Starting Rule-based Manager for Device Events and Files...
Sep 01 16:36:49 xx systemd-journald[432]: Journal started
Sep 01 16:36:49 xx systemd-journald[432]: Runtime Journal (/run/log/journal/fa692dd7c37147518bc63870768c8efb) is 8.0M, max 1.5G, 1.5G free.
Sep 01 16:36:49 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? term>
Sep 01 16:36:49 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termin>
Sep 01 16:36:49 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-binfmt comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?>
Sep 01 16:36:49 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?>
Sep 01 16:36:49 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termi>
Sep 01 16:36:49 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? r>
Sep 01 16:36:49 xx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re>
Sep 01 16:36:49 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysusers comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal>
Sep 01 16:36:49 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? r>
Sep 01 16:36:49 xx systemd[1]: Started Journal Service.
Sep 01 16:36:49 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=>
Sep 01 16:36:49 xx audit: BPF prog-id=6 op=LOAD
Sep 01 16:36:49 xx audit: BPF prog-id=7 op=LOAD
Sep 01 16:36:49 xx audit: BPF prog-id=8 op=LOAD
Sep 01 16:36:49 xx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal>
Sep 01 16:36:49 xx systemd-modules-load[433]: Inserted module 'sg'
Sep 01 16:36:49 xx systemd-modules-load[433]: Failed to find module 'vboxdrv'
Sep 01 16:36:49 xx systemd-modules-load[433]: Failed to find module 'vboxnetadp'
Sep 01 16:36:49 xx systemd-modules-load[433]: Failed to find module 'vboxnetflt'
Sep 01 16:36:49 xx systemd[1]: Starting Flush Journal to Persistent Storage...
Sep 01 16:36:49 xx systemd-journald[432]: Time spent on flushing to /var/log/journal/fa692dd7c37147518bc63870768c8efb is 22.946ms for 961 entries.
lines 915-963/963 (END)

Offline

#38 2021-09-01 23:41:26

JonL
Member
Registered: 2021-06-05
Posts: 7

Re: kernel panic with linux-hardened-5.13.13

loqs wrote:

@JonL can you please report your findings to https://gitlab.freedesktop.org/drm/amd/-/issues/1686 thanks

loqs wrote:

@JonL What commit did you start your revert from?  Using 5.13.13 I could not revert afd3a359c452c5ee529a6b1d660ebf1176765463 cleanly:

It's far from a clean revert and isn't appropriate for upstream yet, but it builds cleanly and is stable for my uses. I still need to sift through it some more in order to understand the driver better.

https://pastebin.com/trfk98Mz

Last edited by JonL (2021-09-02 00:26:19)

Offline

#39 2021-09-02 10:05:48

loqs
Member
Registered: 2014-03-06
Posts: 17,196

Re: kernel panic with linux-hardened-5.13.13

https://drive.google.com/file/d/1YONVY7 … sp=sharing linux-hardened-5.13.13.hardened1-5-x86_64.pkg.tar.zst
Applies fix from upstream https://github.com/nirmoy/linux/commit/ … 5b3b.patch
Edit:
Please test and report results in https://gitlab.freedesktop.org/drm/amd/-/issues/1686

Last edited by loqs (2021-09-02 10:06:43)

Offline

#40 2021-09-02 14:55:16

TheBPN
Member
Registered: 2021-08-28
Posts: 18

Re: kernel panic with linux-hardened-5.13.13

Hello!

I can confirm that your last kernel boots without any problem!
Many thanks!

-- Journal begins at Mon 2021-08-23 13:56:18 UTC, ends at Thu 2021-09-02 14:52:30 UTC. --
Sep 02 14:51:59 xx kernel: Linux version 5.13.13-hardened1-5-hardened (linux-hardened@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Thu, 02 Sep 2021 09:45:4>
Sep 02 14:51:59 xx kernel: Command line: BOOT_IMAGE=/vmlinuz-linux-hardened root=UUID=c97b6628-f326-4cbb-bc8e-cff3ba9dd301 rw cryptdevice=/dev/nvme0n1p2:cryptroot:allow-discards root=/dev/mapper/cryptroot mem_encrypt=off mem_encrypt=off ipv6.disable=1 msr.allow_writes=on l1tf=full, force mds=full,nosmt mitigations=auto,nosmt nosmt=force loglevel=3 quiet
Sep 02 14:51:59 xx kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Sep 02 14:51:59 xx kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Sep 02 14:51:59 xx kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Sep 02 14:51:59 xx kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Sep 02 14:51:59 xx kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Sep 02 14:51:59 xx kernel: BIOS-provided physical RAM map:
Sep 02 14:51:59 xx kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
Sep 02 14:51:59 xx kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
.
.
Sep 02 14:52:30 xx kernel: audit: type=1334 audit(1630594350.157:75): prog-id=12 op=UNLOAD
Sep 02 14:52:40 xx dbus-daemon[718]: [session uid=1000 pid=718] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.51' (uid=1000 pid=1488 comm=">
Sep 02 14:52:40 xx systemd[666]: Starting User preferences database...
Sep 02 14:52:40 xx dbus-daemon[718]: [session uid=1000 pid=718] Successfully activated service 'ca.desrt.dconf'
Sep 02 14:52:40 xx systemd[666]: Started User preferences database.
Sep 02 14:52:44 xx wpa_supplicant[664]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
lines 1511-1561/1561 (END)

Offline

#41 2021-09-09 22:18:21

raneon
Member
Registered: 2013-11-02
Posts: 57

Re: kernel panic with linux-hardened-5.13.13

linux-hardened-5.13.14 is still broken.

Offline

#42 2021-09-09 22:32:37

loqs
Member
Registered: 2014-03-06
Posts: 17,196

Re: kernel panic with linux-hardened-5.13.13

Try the boot parameter debugfs=no-mount or debugfs=on as a work around.

Offline

#43 2021-09-13 07:32:39

raneon
Member
Registered: 2013-11-02
Posts: 57

Re: kernel panic with linux-hardened-5.13.13

Thanks, I'm using linux-lts as a workaround. I just wanted to provide some feedback here. linux-hardened-5.13.15 and linux-hardened-5.13.16 are still broken.

Offline

#44 2021-09-13 18:52:36

NiceGuy
Member
Registered: 2018-02-19
Posts: 50

Re: kernel panic with linux-hardened-5.13.13

The website links loqs posted, especially https://gitlab.freedesktop.org/drm/amd/-/issues/1686, reveal that one of the kernel DRM maintainers is reworking the patch and addressing more issues at once. That's even based on our Arch leader's feedback. So until Nirmoy Das, or another AMD DRM kernel developer rewrites the patch in final form and upstreams that to Linux Torvalds' master branch, which is necessary for stable patches to be considered and backported, we can either wait for a stable minor release occurring officially or grab those patches and have it applied beforehand. It's just a short amount of time before it happens.

Don't worry, be happy. smile

Offline

#45 2021-09-19 15:05:01

NiceGuy
Member
Registered: 2018-02-19
Posts: 50

Re: kernel panic with linux-hardened-5.13.13

5.14.7 contains the fix: https://git.kernel.org/pub/scm/linux/ke … apis.patch

Some time ago I tracked Nimoy Das' commits down, which should fix the issue here, but I am not exactly sure what else is needed.  At least it officially is in the next minor stable release, although more patches pending.

For a list of potential patches and backports prior to release: https://git.kernel.org/pub/scm/linux/ke … queue-5.14

Offline

Board footer

Powered by FluxBB