[elrepo] Today's nvidia 340xx update

[Graham Allan]

On Mon, Aug 03, 2015 at 08:30:02PM +0100, Phil Perry wrote:
> Hi Graham,
> 
> On 03/08/15 19:30, Graham Allan wrote:
> > I've had a handful of machines update their nvidia driver and after
> > reboot X no longer works.
> > 
> > I notice that kmod-nvidia updated to kmod-nvidia-340xx-340.76-2 but
> > the x11 driver stayed at nvidia-x11-drv-340xx-340.76-1. Could that be a
> > problem? 
> 
> No

Had a feeling that wasn't likely :-)
 
> > Downgrading the kmod to kmod-nvidia-340xx-340.76-1 gets things
> > working again.
> > 
> > Is it an oversight that there's no 340.76-2 x11 driver, or am I looking
> > in the wrong place for my issue?
> > 
> 
> kmod-nvidia-340xx was rebuilt against the RHEL-6.7 kernel
> (kernel-2.6.32-573.el6) to fix this issue:
> 
> http://elrepo.org/bugs/view.php?id=583
> 
> What kernel are you running?

Sorry for my delay in reply. Been having a bunch of different machines acting
in different ways, and trying to put together a coherent picture.

We're actually running Scientific Linux 6.6, and kernel-2.6.32-504.30.3.el6.x86_64

It does seem like most of the issues I see are with machines using
kmod-nvidia-340xx (but not all, I've seen at least one with the updated
kmod-nvidia-352.30-1 - was that also rebuilt against RHEL-6.7?).

Some of them fail to start X erratically on boot, some are apparently locking
up during use, and I see a lot of odd call traces in /var/log/messages (not
exclusively X-related). The common message here seems to be
"kernel: BUG: scheduling while atomic"

>From what I can see so far, rebooting into an earlier kernel doesn't make any
difference, but downgrading (eg kmod-nvidia-340xx to 340.76-1) does make things
stable again.

Thanks again,

Graham