Kernel panic after visiting website
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
I am a member!
Someone on IRC linked me to this "New California" website. My screen
froze, my CAPS LOCK light started flashing, and my computer rebooted
itself. I got a kernel panic.
Why was this?
I have also gotten this when running the web program Twitch in my Abrowser.
Oof kernel panics aren’t easy to debug, especially if you didn’t take a photo of the message. Look here for some useful information: https://wiki.ubuntu.com/Kernel/KernelDebuggingTricks
Most of the time, it’s faulty hardware. And then most of the time it’s faulty RAM. When your RAM is having problems, crashes and reboots happen pretty much randomly, because it’s not clearly defined when the faulty section of your RAM will be accessed. But in my experience, crashes due to faulty RAM occur most often when watching videos on the web. In case you mean this website, https://www.newcaliforniastate.com/, it fits the bill, since the entire background of the website is a shitty video.
I recommend running memtest86+ to test your RAM. Sadly, if your machine is Librebooted, this won’t work because Libreboot doesn’t support memtest86+. In that case, if you have multiple RAM chips, first take one out and see if the issue comes back. Then try with the other. If it only happens with one of them, you’ll know which one to replace. If you only have one RAM chip, I’m afraid your best bet is to buy a new one and just give it a shot. But again, if you’re using Libreboot, be sure to get supported RAM: https://libreboot.org/docs/install/x200_external.html#memory
This has happened to me before also. In my case, it was a very random occurance. Possibly from getting overheated. Not sure beyond that though. -_-
PS, it has happened to me on rare occasions in general. Very rare... like ever since the meltdown spectre nonsense.
Then again, I use a different distro. But yeah, it might happen on other distros too. Probably I am sure.
I am a member!
Thanks for the response. I'll chalk it up to RAM, then!
On 12/12/2019 03:36 PM, name at domain wrote:
> This has happened to me before also. In my case, it was a very random
> occurance. Possibly from getting overheated. Not sure beyond that
> though. -_-
My laptop was not hot.
- Vous devez vous identifier ou créer un compte pour écrire des commentaires