Linux is making my ssd really hot compared to windows, making my bios saying S.M.A.R.T status is bad when using linux long enough

if you complete the last post of mine that should fix interrupts coming from the Motherboard......so any distro should simply run without any commands being run
 


Linux made my SSD run hot...now that's funny.
1737113969533.gif


My SSD running Linux Mint is 23c right now.
1737114259408.gif


Might want to look at these...
https://www.techtarget.com/searchstorage/post/Understand-SSD-overheating-and-what-to-do-about-it
https://www.partitionwizard.com/news/can-ssd-overheat.html

1737115075960.gif
 
if you complete the last post of mine that should fix interrupts coming from the Motherboard......so any distro should simply run without any commands being run
Weirdly on endeavour os, I don't see the same result when I was on mint though.

/sys/firmware/acpi/interrupts/gpe6E: 17 STS disabled unmasked

I disabled it like you told me to, the temp is still high :(

I also put

@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe6E
in sudo crontab -e

1737187142986.png


1737187195727.png


@Condobloke, any idea why?
 
Wait I did see that nvme0n1 and nvme1n1 is swapped in endeavour os, is that a problem?

This happens frequently, sometimes it even happens on different reboots on the same distro you've been using for a long time.
It generally doesn't hurt anything. Device paths change. This is why we try to use UUIDs and Labels instead of device paths in shell scripts and especially in our /etc/fstab.
 
Last edited:
Did you run:

grep -Ev "^[ ]*0" /sys/firmware/acpi/interrupts/gpe?? | sort --field-separator=: --key=2 --numeric --reverse | head -1

on endeavour ?

was the result....

/sys/firmware/acpi/interrupts/gpe6F: 4283388 STS enabled unmasked

or similar?.....maybe gpe6E ...on yours

?

When you ran the fix to make it permanent, are you sure it 'saved'.....this is important, because if it did not save successfully, the initial fix will come undone at reboot

So, from the beginning:

grep -Ev "^[ ]*0" /sys/firmware/acpi/interrupts/gpe?? | sort --field-separator=: --key=2 --numeric --reverse | head -1

the above will tell you which 'interrupt' is responsible for keeping the cpu running and the temp rising as a result. In your case it was gpe6E

then:
sudo echo disable > /sys/firmware/acpi/interrupts/gpe6E ....(this disables that interrupt)
Then;

# crontab -e
This opens your favourite editor. Add these lines:

@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe6E
That MUST be saved...otherwise the interrupt will stay alive and continue doing what it does.

Save and Exit in nano editor:
 
Last edited:
Did you run:

grep -Ev "^[ ]*0" /sys/firmware/acpi/interrupts/gpe?? | sort --field-separator=: --key=2 --numeric --reverse | head -1

on endeavour ?

was the result....

/sys/firmware/acpi/interrupts/gpe6F: 4283388 STS enabled unmasked

or similar?.....maybe gpe6E ...on yours

?

When you ran the fix to make it permanent, are you sure it 'saved'.....this is important, because if it did not save successfully, the initial fix will come undone at reboot

So, from the beginning:

grep -Ev "^[ ]*0" /sys/firmware/acpi/interrupts/gpe?? | sort --field-separator=: --key=2 --numeric --reverse | head -1

the above will tell you which 'interrupt' is responsible for keeping the cpu running and the temp rising as a result. In your case it was gpe6E

then:
sudo echo disable > /sys/firmware/acpi/interrupts/gpe6E ....(this disables that interrupt)
Then;

# crontab -e
This opens your favourite editor. Add these lines:

@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe6E
That MUST be saved...otherwise the interrupt will stay alive and continue doing what it does.

Save and Exit in nano editor:
Yes I did all of that, I will try again and give you the full image of me doing it so that if I did something wrong, you would know about it

1737245147144.png

1737245174682.png



I did all that, still it's still really hot, weird.
 
2025-01-19_12-24.png


Something is not right....I am unsure why......perhaps @osprey would take a look for us

also....the last command where you access ....

Code:
 crontab -e

When i type that in I get the below...

1737250322170.png
 
Something is not right....I am unsure why......perhaps @osprey would take a look for us
In relation to the "Invalid argument" output mentioned in posts #67 and #68, the latest syntax looks to be (as root):
Code:
echo mask > /sys/firmware/acpi/interrupts/gpe6E
Perhaps try that and see if the "Invalid argument" is absent, which hopefully indicates the masking or neutralising of the offending interrupt.
 
@hoanghieubrant ......leave this for later after you have tried @osprey's suggestion above

Do you have a nvidia graphics card?
If yes, try disabling 'shader cache' in it.
 
In relation to the "Invalid argument" output mentioned in posts #67 and #68, the latest syntax looks to be (as root):
Code:
echo mask > /sys/firmware/acpi/interrupts/gpe6E
Perhaps try that and see if the "Invalid argument" is absent, which hopefully indicates the masking or neutralising of the offending interrupt.
The reason it has the error is that I already disabled it, so when I want to show it to you guys, I have to enable it first then disable it again, thus why down there I echo enable then the next line I run disable.
 
View attachment 23694

Something is not right....I am unsure why......perhaps @osprey would take a look for us

also....the last command where you access ....

Code:
 crontab -e

When i type that in I get the below...

View attachment 23695
the crontab -e seems still working even though mine looks different to you, since when I restarted the computer, it already made the interrupts disabled
1737257303357.png
 
@hoanghieubrant ......leave this for later after you have tried @osprey's suggestion above

Do you have a nvidia graphics card?
If yes, try disabling 'shader cache' in it.
How to disable shader cache though? like when I searched online, it's all about steam shader cache, and right now I don't have steam installed, so I don't know how to do it though.

but correct at one point, on linux mint I didn't install nvidia, on EOS then yes I did install nvidia. Do I need to uninstall nvidia drivers to test it out?
 
I think shader cache may be in the nvidia software.settings?......I dont have a graphics card, so that could be bs
Uninstalling the drivers or is it possible to disable the graphics card in any way ?...again, no card here so I am a bit clueless in that regard
If all else fails, yes, uninstall the drivers
 
How to disable shader cache though? like when I searched online, it's all about steam shader cache, and right now I don't have steam installed, so I don't know how to do it though.

but correct at one point, on linux mint I didn't install nvidia, on EOS then yes I did install nvidia. Do I need to uninstall nvidia drivers to test it out?
shader cache is application specific data, you should be able to find them in subdirectory created by game somewhere in your home directory.
or for steam maybe in steamapps directory.
shader cache does not belong to drivers or driver specific folders IMO.
 
I think shader cache may be in the nvidia software.settings?......I dont have a graphics card, so that could be bs
Uninstalling the drivers or is it possible to disable the graphics card in any way ?...again, no card here so I am a bit clueless in that regard
If all else fails, yes, uninstall the drivers

Uninstall the nvidia driver doesn't fix it :( man this sucks. now I'm again stuck.
 

Members online


Latest posts

Top