SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It probably isn't a hardware fault on your video card itself (I'm guessing, hoping), though swapping it may change the behaviour if it's at all related.
Another thing to consider, is PCI Express link state power management (ASPM). You can try booting with that disabled.
To your kernel command line, try adding:
Code:
pcie_aspm=off
Hrm. Is that going to mess up how my video card gets power? It's one of those that doesn't need a PSU plug. (Geforce 1050ti)
No, it's just going to mean that clever power management isn't going to reduce power to the PCI Express bus. I always run with that disabled, I don't like that idea on a non-laptop system.
That's actually something the BIOS does, but the kernel has a driver so it can be controlled by policy, or disabled.
Definitely worth looking into, while it's a 2017 bug report, there are some fairly recent posts. Possibly something a BIOS update, or microcode firmware blob could fix.
I presume if you're on -current you're using the distro's current 4.19 longterm kernel, not some ancient one.
Yup, I'm on current. BIOS flashed this morning, and I'm using rcu_nocbs (set to the proper amount of cores). Marking this one solved, because it's not a firefox issue. Thanks for all the help, folks!
Fingers crossed that it's mitigated? We had a family dinner, and I let things idle. Screensaver did kick on, so I'm not sure if that's enough activity to make it not crash.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.