Fedora 43 / dnf / General issues

Ask Fedora
1

Fedora / dnf / General Issues

Hi Everyone,

I got a bit of a weird issue, and I’m not really sure at this point what it could be.

I have the following system:

MSI z790 (bios fully updated)

Intel 14900k

Corsair DDR5 64gb dominator ram (no xmp profile loaded)

Nvidia 4090

So I’ve gone through quite a few Fedora 43 installs, each time so far it seems like I get some issue. Applets crashing when I log in, black screens when doing system updates. dnf throwing off disk image is malformed, etc.

I’ve ruled out most everything I can at the moment.

Did an hour long OCCT test on my processor, no errors.

Did a passmark memtest, did 4 passes and no errors.

I decided to take the hard drive out of the equation and install it on a brand new fresh.

I still seem to be having issues, and tbh I’m not sure at this point if it’s just Fedora or perhaps my motherboard. I’m not overclocking, the only thing I have done is limit the power draw in the motherboard, and that is it.

When doing a google chrome install just now, I got a segmentation fault from dnf. Here is the dmesg output for the error:

[ 77.899492] systemd[1]: Detected architecture x86-64.

[ 78.024557] systemd[1]: bpf-restrict-fs: LSM BPF program attached

[ 131.345535] BUG: Bad page map in process dnf pte:80000002b0a41867

[ 131.345539] pgd:24db8d067 p4d:24db8d067 pud:235309067 pmd:234137067

[ 131.345541] addr:00007f3e6965f000 vm_flags:08100073 anon_vma:ffff8f2ab15429c0 mapping:0000000000000000 index:7f3e6965f

[ 131.345542] file:(null) fault:0x0 mmap:0x0 mmap_prepare: 0x0 read_folio:0x0

[ 131.345562] CPU: 9 UID: 0 PID: 5250 Comm: dnf Tainted: G O 6.18.12-200.fc43.x86_64 #1 PREEMPT(lazy)

[ 131.345563] Tainted: [O]=OOT_MODULE

[ 131.345563] Hardware name: Micro-Star International Co., Ltd. MS-7D86/MEG Z790 ACE (MS-7D86), BIOS 1.F0 08/07/2025

[ 131.345564] Call Trace:

[ 131.345566] <TASK>

[ 131.345567] dump_stack_lvl+0x5d/0x80

[ 131.345570] print_bad_page_map.cold+0xeb/0x15a

[ 131.345572] ? __lruvec_stat_mod_folio+0x85/0xd0

[ 131.345574] vm_normal_page+0xf4/0x100

[ 131.345575] zap_present_ptes.constprop.0+0x39/0x750

[ 131.345576] ? __entry_text_end+0x6730/0x101e39

[ 131.345577] zap_pte_range+0x1b4/0x590

[ 131.345579] zap_pmd_range.isra.0+0xfd/0x210

[ 131.345580] ? mas_update_gap.part.0+0xbd/0x200

[ 131.345582] unmap_page_range+0x246/0x410

[ 131.345583] unmap_vmas+0xa1/0x180

[ 131.345584] vms_clear_ptes+0x10a/0x160

[ 131.345586] vms_complete_munmap_vmas+0x61/0x180

[ 131.345587] do_vmi_align_munmap+0x15f/0x1e0

[ 131.345589] do_vmi_munmap+0xd0/0x170

[ 131.345589] __vm_munmap+0xad/0x170

[ 131.345591] __x64_sys_munmap+0x1b/0x30

[ 131.345592] do_syscall_64+0x7e/0x7f0

[ 131.345593] ? do_syscall_64+0xb6/0x7f0

[ 131.345594] ? do_syscall_64+0xb6/0x7f0

[ 131.345594] ? do_syscall_64+0xb6/0x7f0

[ 131.345594] ? irqentry_exit_to_user_mode+0x2c/0x1c0

[ 131.345596] entry_SYSCALL_64_after_hwframe+0x76/0x7e

[ 131.345596] RIP: 0033:0x7f3eb48ff22b

[ 131.345598] Code: 73 01 c3 48 8b 0d d5 6b 0f 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 0b 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a5 6b 0f 00 f7 d8 64 89 01 48

[ 131.345599] RSP: 002b:00007fffa1445218 EFLAGS: 00000207 ORIG_RAX: 000000000000000b

[ 131.345600] RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f3eb48ff22b

[ 131.345601] RDX: 0000000000000000 RSI: 0000000045ae1000 RDI: 00007f3e4a51f000

[ 131.345601] RBP: 00007fffa1445260 R08: 00007f3e4a51f000 R09: 00007f3eb49f6ac0

[ 131.345601] R10: 0000000045ae1000 R11: 0000000000000207 R12: 00005621f81d3188

[ 131.345602] R13: 00005621f9ef9c38 R14: 00005621f81d3188 R15: ffffffffffffffff

[ 131.345602] </TASK>

[ 131.345603] Disabling lock debugging due to kernel taint

[ 132.174286] BUG: Bad rss-counter state mm:00000000c037721a type:MM_ANONPAGES val:1 Comm:dnf Pid:5250

[ 161.286743] show_signal_msg: 17 callbacks suppressed

[ 161.286746] dnf[5551]: segfault at 558186640d5d ip 00007fa7a51549ef sp 00007fff1a85fa58 error 6 in libc.so.6[1479ef,7fa7a500d000+16f000] likely on CPU 8 (core 16, socket 0)

[ 161.286751] Code: 8d 54 17 80 48 83 cf 1f 48 ff c7 c5 fd e7 07 c5 fd e7 47 20 c5 fd e7 47 40 c5 fd e7 47 60 48 83 ef 80 48 39 d7 72 e4 0f ae f8 <c5> fe 7f 02 c5 fe 7f 42 20 c5 fe 7f 42 40 c5 fe 7f 42 60 c5 f8 77

And looking at journalctl. I just see this:

Feb 25 17:39:50 fedora systemd-coredump[5566]: Resource limits disable core dumping for process 5551 (dnf).

Feb 25 17:39:50 fedora systemd-coredump[5566]: [🡕] Process 5551 (dnf) of user 0 terminated abnormally without generating a coredump.

And also when doing a dnf upgrade --refresh I’ll randomly get errors (which are eluding me at the moment).

Does this look like hardware issues? Or is this just Fedora 43 at this point?

Thanks for any help!

2

Hi Terry,

It shouldn’t be this hard to get Fedora installed on a near current gen peecee.

I would start with the memory. I read that you ran passmark for 4 cycles. Your combo feels to me that it should AOK Okie Dokie for Fedora 43.

Have you tried memtest+ and let it run for a day or so?

Is your RAM on the supported list for your motherboard?

You didn’t break down the RAM kit makeup, are the DIMMs in the right slots for the composition of the kit?

Is your RAM using the default auto-detect values?

No timing tweaks or overclocking tweaks to the FSB/RAM/voltages/etc?

I also saw that you aren’t using a XMP Profile. I usually run XMP 1 Profile or on AMD the EXPO 1/default one. And I don’t fiddle with anything else. I also don’t use the “run analysis to find the fastest/best RAM settings” option either.

You could also do a non-GUI install to elimnate the Wayland/XOrg/NVIDIA drivers. I am assuming you are using either the propriety driver or nvidia-open driver b/c of your RTX 4090. I doubt there’s an issue here, but if you’ve been having issues with multiple installs, reducing the install down to no graphics/UI could make it easier to troubleshoot.

3

What are actual userspace problems you encounter?

DNF will spit perfectly normal errors it self recovers from.

The chrome errors Im not sure, but if chrome works dont worry about it. I prefer Firefox as its in the Fedora repo, but of course browser choice is up to you :slight_smile:

4

Random non-repeating errors are usually hardware. Try booting the standalone memtest86+ and running it overnight for several nights. Old, marginal capacity, or low quality power supplies may provide unclean power.

From https://memtest.org/readme#trouble-shooting-memory-errors

The time required for a complete pass of Memtest86+ will vary greatly depending on CPU speed, memory speed, and memory size. Memtest86+ executes indefinitely. The pass counter increments each time that all of the selected tests have been run. Generally a single pass is sufficient to catch all but the most obscure errors. However, for complete confidence when intermittent errors are suspected testing for a longer period is advised.

5

Do the memtests suggested, but I have found that Nvidia is often the problem with these types of problems. So make sure the correct nvidia driver is installed.

6

I’d try undoing that, and make sure SecureBoot is disabled in BIOS

7

The kernel crashed…

8

I second the idea to undo power limit, but I highly recommend not disabling SecureBoot. If the system is properly set up, disabling SecureBoot will make it unbootable.

Correction: Thanks to @barryascott, I think I thought that SecureBoot==UEFI Boot, but I guess you are right, and they are not the same, so you can have UEFI Boot without secure boot. Sorry for the confusion

9

Really? Maybe for Windows but not for linux systems.

10

Thank you everyone for all the replies! Sorry for my late reply back, but it turns out to be a hardware issues. Looks like it is either something with my ram or CPU. So going to be replacing some items and I’m going to try again when it is all done.

2 Likes
11

Please, let it not be RAM… I feel for you right now.

(it will be RAM. Accept it, sell a kidney and move on with your one kidney life… Or just say fsck it and put DDR4 in there, which is cheaper(ish) and you won’t notice any difference.)

Edit: Apply an XMPP profile to it - you never know - might be running with utterly shite settings. Nothing to lose - if it’s knackered, it’ll still be knackered later)

1 Like
12

I didn’t see any MCE errors so I’d guess the CPU part of the CPU is ok. The virtual memory page faults are the concern to me. That’s either going to be RAM or the memory controller in the CPU itself. There is also the possibility of the VRMs on the motherboard…

Good luck. :crossed_fingers: you can avoid what Steve referenced: the RAM/DIMM market is a complete and utter mess. It could be very painful to your wallet, it’s that bad.