I need some help diagnosing what I think is a hardware issue on my Dell Precision laptop causing crashes that happen both randomly and, e.g., whenever I load up a youtube video on firefox. I haven’t been able to recreate the crashes on Windows yet but this hardware feels like the likely cause because I have an old install that I used last year on kernel 5.10 XFCE Manjaro and I’ve been able to reproduce the crash there.
I’ve been running Manjaro Gnome for a few months and they’ve started happening pretty recently, maybe a month or so. I’ve since tried updating the kernel and tried running a live USB with KDE on it, but neither of these things fixed the issue. Not sure if it’s relevant but the computer did last a few minutes longer watching a youtube version on firefox when I was running the old XFCE install.
Whenever the crash happens the computer powers down and immediately shows the dell (yep) flash logo like it’s restarting or never got the signal that it turned off. When I look at journalctl logs before the crash there’s nothing, I can post this output if called for but am on the Windows install currently. Whenever the system finishes powering up this way the battery is shown as unplugged and will not charge, even though it was plugged in and charging up until the crash. I then have to shut down the computer, unplug and replug the charger, then power the system on and it will continue to be charging. This crash does still happen even when the laptop is on battery power only.
Any tips for diagnosing this would be really appreciated, also if there are any software-side ideas that would be helpful too. I’m open to having it repaired but want as much info as I can going into it to make sure it will solve the problem, whatever the suggestion ends up being from a third-party repair service.
does it only crashes when watching video on firefox?
you should provide logs from when the crash happens: journalctl -b-1 -p5 --no-pager
also provide formatted output from: inxi -Fazy
It crashes on google maps on chrome and firefox, it crashes sometimes when starting up games, and sometimes it crashes when I’m just running gvim and a terminal doing some light python coding, or sometimes just dragging windows around or switching workspaces. If I’m playing a game once it’s running for a few minutes it won’t crash for as long as I’m playing.
Oh, I also think there’s an overall trend where if I put the laptop on performance mode it crashes much faster than if it’s on power saving mode.
I reproduced another crash via firefox/youtube. This is 20 seconds of log data before the crash happened, cutting out some logs related to my keyboard and mouse disconnecting for some reason.
>>> journalctl -b-1 -p5 --no-pager
Jun 24 19:05:18 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (**) Option "AccelerationScheme" "none"
Jun 24 19:05:18 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (**) SteelSeries SteelSeries Rival 3 Wireless: (accel) selected scheme none/0
Jun 24 19:05:18 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (**) SteelSeries SteelSeries Rival 3 Wireless: (accel) acceleration factor: 2.000
Jun 24 19:05:18 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (**) SteelSeries SteelSeries Rival 3 Wireless: (accel) acceleration threshold: 4
Jun 24 19:05:18 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) event3 - SteelSeries SteelSeries Rival 3 Wireless: is tagged by udev as: Mouse
Jun 24 19:05:18 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) event3 - SteelSeries SteelSeries Rival 3 Wireless: device is a pointer
Jun 24 19:05:18 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): EDID vendor "SHP", prod id 5329
Jun 24 19:05:18 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Printing DDC gathered Modelines:
Jun 24 19:05:18 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 -hsync -vsync (74.0 kHz eP)
Jun 24 19:05:18 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1920x1200"x0.0 123.20 1920 1968 2000 2080 1200 1203 1209 1235 -hsync -vsync (59.2 kHz e)
Jun 24 19:05:19 trevormax-precision5550 gnome-shell[2084]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x564601738320] is on because it needs an allocation.
Jun 24 19:05:19 trevormax-precision5550 gnome-shell[2084]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x564603034b50] is on because it needs an allocation.
Jun 24 19:05:19 trevormax-precision5550 gnome-shell[2084]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x564603038a30] is on because it needs an allocation.
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): EDID vendor "ACI", prod id 9368
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Using hsync ranges from config file
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Using vrefresh ranges from config file
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Printing DDC gathered Modelines:
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): EDID vendor "ACI", prod id 9368
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Using hsync ranges from config file
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Using vrefresh ranges from config file
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Printing DDC gathered Modelines:
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
Jun 24 19:05:20 trevormax-precision5550 /usr/lib/gdm-x-session[1837]: (II) modeset(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
Jun 24 19:05:26 trevormax-precision5550 nautilus[7182]: Unable to initialize tag manager: SQL logic error
Jun 24 19:05:27 trevormax-precision5550 gnome-calculato[7186]: search-provider.vala:117: Failed to spawn Calculator: Child process killed by signal 9
Jun 24 19:05:28 trevormax-precision5550 nautilus[7182]: Connecting to org.freedesktop.Tracker3.Miner.Files
Jun 24 19:05:29 trevormax-precision5550 gnome-character[7188]: JS LOG: Characters Application started
Jun 24 19:05:39 trevormax-precision5550 gnome-character[7188]: JS LOG: Characters Application exiting
i have no idea … drivers looks good… wanted to suggest to uninstall nvidia and use only linux drivers, to see if the problem still remains, but since the crash happened also with free drivers, i dont know what to do next…
Thanks for the help. Literally no worries because this still tells me what I need to know - it’s a hardware issue and I can’t diagnose it further in software alone.
>>> journalctl -b0 -p3 --no-pager
Jun 25 23:59:04 trevormax-precision5550 kernel: Spectre V2 : WARNING: Unprivileged eBPF is enabled with eIBRS on, data leaks possible via Spectre v2 BHB attacks!
Jun 25 23:59:05 trevormax-precision5550 kernel: psmouse serio1: elantech: elantech_send_cmd query 0x02 failed.
Jun 25 23:59:05 trevormax-precision5550 kernel: psmouse serio1: elantech: failed to query capabilities.
Jun 25 23:59:05 trevormax-precision5550 kernel:
Jun 25 23:59:07 trevormax-precision5550 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jun 25 23:59:08 trevormax-precision5550 kernel: ucsi_acpi USBC000:00: unknown error 0
Jun 25 23:59:08 trevormax-precision5550 kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)
Jun 25 23:59:10 trevormax-precision5550 kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
Jun 26 00:00:34 trevormax-precision5550 systemd[1]: Timed out waiting for device /dev/disk/by-uuid/00723683-4aee-4f02-8c01-95a13d81a9fc.
Jun 26 00:00:37 trevormax-precision5550 gnome-session-binary[1611]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Jun 26 00:00:37 trevormax-precision5550 gnome-session-binary[1611]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Jun 26 00:00:53 trevormax-precision5550 gdm-password][1922]: gkr-pam: unable to locate daemon control file
Jun 26 00:00:55 trevormax-precision5550 systemd[1933]: Failed to start Application launched by gnome-session-binary.
Jun 26 00:01:00 trevormax-precision5550 systemd[1933]: Failed to start Application launched by gnome-session-binary.
Jun 26 00:01:06 trevormax-precision5550 gdm-launch-environment][1558]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
I think this is from my last boot event looking at the time.
It may happen on windows but I just haven’t seen it/it’s harder to cause? I still don’t get why an old manjaro/xfce install that never had crashes would suddenly start crashing as soon as I went back to it after several months too. Feels more like there’s some privileged windows coupling w/ the firmware that lets it avoid the crash.
I’ll check fastboot and report back if I still get crashes with an edit. Secure boot is disabled, it needed to be to be able to boot from live USB. edit no dice after “turning” fastboot off. I put it in quotes because I’m not sure if it was on in the first place, although it may have been.
I finally tried switching kernel to 5.4. I tested it out last night watching a youtube video on firefox (which caused crashes in the past) and was elated that there was no crash for the several minutes I was watching. Then when I sat down this morning to show my girlfriend that it wasn’t crashing and unpaused the video, it shortly crashed.
That said I was running factorio last night and experiencing hiccups and relatevely poor fps, but after downgrading to 5.4 I’m seeing back to crystal-clean performance. So overall I’m still very happy with this fix, even if it is only a partial fix.
I do see a bunch of temperature events on my journalctl now but none from the time the crash actually happened so not sure it’s relevant.
Jul 09 07:22:13 trevormax-precision5550 kernel: mce: CPU11: Core temperature above threshold, cpu clock throttled (total events = 218)
Jul 09 07:22:13 trevormax-precision5550 kernel: mce: CPU5: Core temperature above threshold, cpu clock throttled (total events = 218)
Jul 09 07:22:13 trevormax-precision5550 kernel: mce: CPU11: Package temperature above threshold, cpu clock throttled (total events = 1114)
Jul 09 07:22:13 trevormax-precision5550 kernel: mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 1114)
Jul 09 07:22:13 trevormax-precision5550 kernel: mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 1114)
Jul 09 07:22:13 trevormax-precision5550 kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1114)
Jul 09 07:22:13 trevormax-precision5550 kernel: mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 1114)
Jul 09 07:22:13 trevormax-precision5550 kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 1114)
Jul 09 07:22:13 trevormax-precision5550 kernel: mce: CPU8: Package temperature above threshold, cpu clock throttled (total events = 1114)
Jul 09 07:22:13 trevormax-precision5550 kernel: mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 1114)
Jul 09 07:22:13 trevormax-precision5550 kernel: mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 1114)
Jul 09 07:22:13 trevormax-precision5550 kernel: mce: CPU10: Package temperature above threshold, cpu clock throttled (total events = 1114)
Jul 09 07:22:13 trevormax-precision5550 kernel: mce: CPU9: Package temperature above threshold, cpu clock throttled (total events = 1114)
Jul 09 07:22:13 trevormax-precision5550 kernel: mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 1114)
No, and certainly I’m not doing anything overnight that should be causing an overheat. Looking at the temperature profile the CPU is currently at ~45-50 so not overheating. The fans aren’t running right now because nothing is happening. If I run an infinite loop the cpu does seem to heat up to 100c pretty quickly and the fans don’t seem to turn on all that much. Going to read through the wiki, conveniently there is a section on dell laptop fan control specifically, and see if I can configure the fans to kick on more aggressively.
Could it be that this whole crashing issue is CPU related, if the CPU has been consistently hitting 100 degrees C for the last good while, leading to damage over time?
yes, the overheating is very likely the reason for the crashes… also you mentioned that it happened on the live usb… yes check the fans… also you coudl try a live usb of linux mint for example, and test if the crashes occur there too…
I’m working with the i8kutils and it looks like changing the config settings does not result in changes to fan behavior, even when using BIOS_overriding_fan_control. It feels less like the fans aren’t working effectively and more like the fans just aren’t kicking on to full when they need to, since running windows the fans instantly crank up to full when I’m just on the desktop, therefore I know that sound very well and it’s not happening on linux no matter what I do.
The last two lines here show that the fan states are [0, 0], which I set to be [4900, 0]. However, they are both off when I look at psensor. That said, I did notice that starting i8kmon when temperature was high ~70 and the fan was off (for some reson) did make the fans kick on and cause the temperature to go down rapidly. So it is turning fans on and off more or less as expected, but doesn’t seem to have left/right granularity or access to any speeds other than ~3100 rpm. Not sure where to go from here other than trying out a different liveUSB which I will give an update on later.
Side note, there is a thermal control section in the BIOS and changing it to the profile that seemed to claim to just crank the fans to max all the time had no effect on behavior in my manjaro install as far as I can tell. Obviously disabling bios control was supposed to disable this but since I wasn’t able to change behavior as expected in linux I wanted to see if trying to change via bios did anything and it didn’t.
Actually, I can debug “hardware” problems by checking if there is similar weird temp behavior in windows. I put quotes around that because dust isn’t hardware, but if something is preventing the fans from doing their job I should see spikes in temp on windows too.