The x11-drivers/ nvidia-drivers-550 series driver was recently stabilized but seems to be causing issues for me (and a lot of other people) in regards of crashes, kernel OOPS messages and several other issues. Please see: https://forums.developer.nvidia.com/t/series-550-freezes-laptop/284772/107 for details. Reproducible: Always Steps to Reproduce: 1.Emerge a x11-drivers/ nvidia-drivers-550 series driver. 2.Work for several hours on your machine. 3.It will either hang during work or give a kernel oops when trying to shut the machine down. Actual Results: A hanging machine or a kernel oops on shutdown Expected Results: A stable working machine Please see: https://forums.developer.nvidia.com/t/series-550-freezes-laptop/284772/107 (and perhaps: https://bugzilla.kernel.org/show_bug.cgi?id=218818) for details. Reverting back to the 535 series driver, resolves the issue. Please consider moving the 550 series driver back to ~arch
An additional note to add (also written in the forums): The driver versions 550.90.07 and 555.52.04 were released yesterday containing the following information: “Fixed a bug that could lead to a kernel panic, due to a failure to release a spinlock under some conditions.” Perhaps this could resolve the issue, in that case it's best so stabilize the new version?
Been aware of that thread for a very long time, formerly delayed 550 stable but users started to want the things that it fixes (esp. with wayland). Not everyone has an affected laptop, and can't hold back stabilization forever because a few users are affected. Anyhow, that's why we keep several branches in-tree and 535 hasn't been deleted. If you have issues please do stick to the 535 branch which is still supported. > An additional note to add (also written in the forums): The driver versions > 550.90.07 and 555.52.04 were released yesterday containing the following > information: “Fixed a bug that could lead to a kernel panic, due to a > failure to release a spinlock under some conditions.” > > Perhaps this could resolve the issue, in that case it's best so stabilize > the new version? These are not even in ~arch, they are unkeyworded. Not only a "new feature branch" (we never stabilized these, only production branches) but are also marked BETA/Pre-Release by nvidia. Also, the spinlock fix is in 550.90.07 as well -- it was *just* released so not stabilized yet, but it will be in a few days. You could accept keywords it to see if it helps you. If it does, I could speed up stabilization.
> > An additional note to add (also written in the forums): The driver versions > > 550.90.07 and 555.52.04 were released yesterday containing the following > > information: “Fixed a bug that could lead to a kernel panic, due to a > > failure to release a spinlock under some conditions.” > > > > Perhaps this could resolve the issue, in that case it's best so stabilize > > the new version? > These are not even in ~arch, they are unkeyworded. Not only a "new feature > branch" (we never stabilized these, only production branches) but are also > marked BETA/Pre-Release by nvidia. Oops sorry, I misread, thought said 555.42.02 and 555.52.04 for some reason. To re-answer that bit, it's a bit early to stabilize but it's planned.
