Random Reboots on friend's laptop
Since a few days my friend is getting random reboots. They say that their screen suddenly turns black and the laptop reboots itself, no matter what they were doing before.
This is also horrible timing as something bad is going on in their life right now and the last thing they want is computer issues, so I would appreciate any quick help I can get on this 🙏
41 Replies

Their specs
There is a
ujust get-logs
command it will give you a link to the logs last boot and current boot. The "last boot" one will probably be the most helpful link to posthttps://paste.centos.org/view/1e518ca8
This is a lot tho
If you add last boot after ujust get-logs it only shows the last one?
Or that is not how it works
Ah it's also nvidia so if they suddenly started having issues. it might be worth rebasing back to a time when they weren't having issues
The nvidia drivers sometimes improve things and sometimes they break things so I usually use
bazzite-rollback-helper list
and manually pick the image and I then manually update. Then to update run bazzite-rollback-helper rebase <insert image name>
and I rebase when I'm feeling lucky lolI understand but Random reboots sounds like something out of Nvidia's range
Unless the user allows it i don't think bazzite can randomly reboot itself no?
No random reboots can very well be a graphics driver
Hmm, is worth a try then
Maybe they can rollback to the previous image
if they do that then they'll need to disable the auto updates for a while too (else the machine will just auto update again to the version that is breaking). Try the rollback and see what happens
How to disable?
It's
ujust toggle-updates
to disable the auto updates
O hope it's just a bad update since debugging restarting issues can be challenging.The previous version produces freezes instead of rebooting
What they could try is trying out the propietary branch instead of the open one, as GSP may be acting up
Is there a way to do this

This seems contradictory
Hmmm, wait a minute. GSP is not enabled in the open branch, so that can't be it
https://cdn.discordapp.com/attachments/1043085280657289236/1337812452557193377/log.txt?ex=67a8ce70&is=67a77cf0&hm=c5dba3e636eaa1908dccfe87c288cff24b651add065dc1cd0dc0ac573c77222a&
@wolfyreload
Their last log boot
Well idk who else to ping 😅
It could be an Asus issue
Sounds like it's a hardware problem
Probably
@Kyle Gospo
Does rolling back to the old release not solve the problem?
you wrote the command wrong
It brings back the older problem
The older problem being: random freezes
bazzite-asus-nvidia-stable
should be bazzite-asus-nvidia:stable
Basically now they don't have random freezes, just random reboots
But to me that sounds like the issue is elsewhere
I see
Hmm but would that really fix the reboot issue though? Seems unrelated
probably wont unless an older image works, what i pointed out was just why the bazzite-rollback-helper was being weird for you and would make it easier to try older images
Ohh i get it, thanks
Judging by the logs, is there anything weird there?
nothing sticks out for me but im also on from a phone atm
i also dont use nvidia on linux
the only thing i do see is that there was an attempt to change the charge threshold and it failed, thats it
Hmm
Welp
Maybe another hybrid laptop shenanigan
Or an SSD failing?
But it's weird because it started after the latest updates
Before, like i mentioned, it was only random freezes
Man, laptops are complicated
if the ssd was failing you would know it was the ssd very fast
driver had a subversion bump
You're right
570.xx.15 --> 570.xx.16
xx stayed the same i just dont remember it in my head
Hmm
The freezes are from the 565
They stayed in 570
So that wasn't it
yeah but 570 had a subversion bump
meaning super minor version change
so if they rollback to last week and reboots stop, it might be from that
I see
What would last week version be?
Just simply rollback?
brh list
pick one with a date from last week(or closest to at least sometime last week, not this week)
yyyymmdd
rebase to it with brh rebase stable-41-date
if you want to change image then its bazziteimage:stable-41-date
They're afk, will report back later
Okay, they are gonna try rollbacking

We got hardware errors now
Maybe this is a lead to something
Possibly a hardware / OpenGL issue @Kyle Gospo
Reboots still happen in any image
Idk how are they gonna fix it since the laptop doesn't have a warranty
It seems OpenGL programs consistently cause the reboots, too
This makes sense considering the previous freezes occurred while using OpenGL applications
So OpenGL doesn't seem to like asus
I'd check if the issue also occurs in Windows. Then you can see if it's specific to Linux or a hardware issue in general. Also what are the temperatures like? That might also be causing random reboots
That's not really possible rn, i don't think they dualboot windows
Will ask about the temperature tho
They say the temperature doesn't increase, it stays normal
What they do notice is that the nVidia driver usage goes from 0 to 100
When a reboot is about to happen
Doesn't matter the image, they tried the build from January and same issue
100 degrees celcius or 100% GPU utilisation?
Gpu utilisation
Is it a desktop or a laptop? Sometimes the issue can just be dust. I had an issue with restarts and I had a small amount of dust that had gotten between the GPU and the it's slot. It reboot randomly when I ran anything that used GPU
Some compressed air and reseating the comments and the problem disappeared
Laptop
more info regarding openGL @wolfyreload

Seems updating the Bios fixed the issue
I'm gonna mark it as solved for the time being
Issue resurfaced
Apparently is related to the power daemon: performance mode works well, Balanced may occasionate reboots for them