Possibly similar issues:
  dnf update today, kernel 4 14 4 ?
Rebooted, system totally unresponsive.

Reboot to revert to previous kernel, boot is past that before I can
select an alternative.

System comes up. I can log in.
   Taking between 5 and 20 seconds to respond to mouse actions.
How to slow down boot to allow reversion to previous kernel please?



On 21 February 2018 at 08:57,  <h...@mimosa.com> wrote:
> I'm running F27 using RPM Fusion's nvidia drivers.  I've been using these 
> packages for several years (thanks!).  I did updates yesterday.  Twice.
>
> My video card is a GTX 650.  It is driving an UltraHD TV at 30 HZ, something 
> that nouveau fails at when I've tried it.
>
> After the updates, my system was extremely sluggish.  The CPU has 4 cores and 
> 8 hyperthreads.  Top says gnome-shell is using close to 800% of a CPU -- in 
> other words, all that it can.  (I run top by sshing into the system from 
> another.)
>
> If I don't use the console, keyboard, or mouse, CPU usage goes down to well 
> below 100%.  But moving the mouse even the slightest bit causes it to go back 
> up.
>
> After the first updates, the system log showed some errors:
>
> Feb 20 13:21:22 redeye kernel: WARNING: CPU: 0 PID: 617 at 
> /tmp/akmodsbuild.8EJAaQVu/BUILD/nvidia-kmod-390.25/_kmod_build_4.15.3-300.fc27.x86_64/nvidia-drm/nvidia-drm-modeset.c:241
>  nv_drm_handle_flip_occurred+0xe5/0x110 [nvidia_drm]
>
> Feb 20 13:21:22 redeye kernel: WARNING: CPU: 4 PID: 35 at 
> drivers/gpu/drm/drm_atomic_helper.c:1950 
> drm_atomic_helper_commit_hw_done+0xd5/0xe0 [drm_kms_helper]
>
> At this point, something like OOPS output appeared.  Tainted, of course.
>
> Subsequently, errors with "flip" in them appeared:
>
> Feb 20 13:21:33 redeye kernel: [drm:drm_atomic_helper_wait_for_dependencies 
> [drm_kms_helper]] *ERROR* [CRTC:32:crtc-0] flip_done timed out
>
> Feb 20 13:21:43 redeye kernel: [drm:drm_atomic_helper_wait_for_dependencies 
> [drm_kms_helper]] *ERROR* [PLANE:31:plane-1] flip_done timed out
>
> After more updates, CPU-eating behaviour persisted.
>
> I then tried to downgrade but failed:
>
> [root@redeye log]# dnf downgrade xorg-x11-drv-nvidia-libs 
> xorg-x11-drv-nvidia-kmodsrc xorg-x11-drv-nvidia akmod-nvidia 
> kmod-nvidia-4.14.18-300.fc27.x86_64
> Last metadata expiration check: 2:19:38 ago on Tue 20 Feb 2018 11:41:12 PM 
> EST.
> Packages for argument kmod-nvidia-4.14.18-300.fc27.x86_64 available, but not 
> installed.
> Error:
>  Problem 1: package kmod-nvidia-4.15.3-300.fc27.x86_64-3:390.25-3.fc27.x86_64 
> requires nvidia-kmod-common >= 3:390.25, but none of the providers can be 
> installed
>   - cannot install both xorg-x11-drv-nvidia-2:387.22-3.fc27.x86_64 and 
> xorg-x11-drv-nvidia-3:390.25-4.fc27.x86_64
>   - conflicting requests
>   - problem with installed package 
> kmod-nvidia-4.15.3-300.fc27.x86_64-3:390.25-3.fc27.x86_64
>  Problem 2: package 
> kmod-nvidia-4.14.18-300.fc27.x86_64-3:390.25-3.fc27.x86_64 requires 
> nvidia-kmod-common >= 3:390.25, but none of the providers can be installed
>   - package xorg-x11-drv-nvidia-3:390.25-4.fc27.x86_64 requires 
> libnvidia-glcore.so.390.25()(64bit), but none of the providers can be 
> installed
>   - cannot install both xorg-x11-drv-nvidia-libs-2:387.22-3.fc27.x86_64 and 
> xorg-x11-drv-nvidia-libs-3:390.25-4.fc27.x86_64
>   - conflicting requests
>   - problem with installed package 
> kmod-nvidia-4.14.18-300.fc27.x86_64-3:390.25-3.fc27.x86_64
> (try to add '--allowerasing' to command line to replace conflicting packages 
> or '--skip-broken' to skip uninstallable packages)
>
> Any suggestions?
> _______________________________________________
> rpmfusion-users mailing list -- rpmfusion-users@lists.rpmfusion.org
> To unsubscribe send an email to rpmfusion-users-le...@lists.rpmfusion.org



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
_______________________________________________
rpmfusion-users mailing list -- rpmfusion-users@lists.rpmfusion.org
To unsubscribe send an email to rpmfusion-users-le...@lists.rpmfusion.org

Reply via email to