Kernel problem with CentOS 7 on Dell D630 laptop

[magicBeast]

Hi,

I've recently installed CentOS on an old Dell D630 laptop and I'm getting the following problem (apologies if this has been solved elsewhere, I've had a search on the forum but couldn't find anything):

WHILE BOOTING (from dmesg):

[ 13.291169] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:29:pipe A] flip_done timed out
[ 24.607170] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out
[ 34.973165] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out
[ 75.580295] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out
[ 85.923232] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out
[ 98.009248] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out
[ 108.429157] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out
[ 119.117256] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out
[ 132.476291] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out
[ 343.164262] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out
[ 353.543259] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out
[ 363.964293] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out
[ 377.847251] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out
[ 598.319091] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out
[ 608.726077] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out
[ 1650.356257] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe B] flip_done timed out

FROM ABRT-CLI

The Autoreporting feature is disabled. Please consider enabling it by issuing
'abrt-auto-reporting enabled' as a user with root privileges
id 241e960292addc35ec7383451e0c3f62cc81246f
reason: WARNING: CPU: 1 PID: 292 at drivers/gpu/drm/drm_irq.c:1237 drm_wait_one_vblank+0x184/0x1d0 [drm]
time: Tue 19 Dec 2017 19:39:54 GMT
cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-693.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.luks.uuid=luks-b0902490-13
39-4b98-9780-369adef6a275 rd.lvm.lv=centos/swap rhgb quiet LANG=en_GB.UTF-8
package: kernel
uid: 0 (root)
count: 78
Directory: /var/spool/abrt/oops-2017-12-19-19:39:54-1636-3
Reported: cannot be reported

id 42e1915afe7373336bcb5bafc84b0cdade302b02
reason: WARNING: CPU: 1 PID: 14646 at drivers/gpu/drm/drm_irq.c:1237 drm_wait_one_vblank+0x184/0x1d0 [drm]
time: Tue 19 Dec 2017 19:41:48 GMT
cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-693.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.luks.uuid=luks-b0902490-13
39-4b98-9780-369adef6a275 rd.lvm.lv=centos/swap rhgb quiet LANG=en_GB.UTF-8
package: kernel
uid: 0 (root)
count: 68
Directory: /var/spool/abrt/oops-2017-12-19-19:41:48-14719-0
Reported: cannot be reported

id 129c03991b7966e659d64c26b58f4419c2213ead
reason: WARNING: CPU: 1 PID: 67 at drivers/gpu/drm/drm_irq.c:1237 drm_wait_one_vblank+0x184/0x1d0 [drm]
time: Tue 19 Dec 2017 19:39:54 GMT
cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-693.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.luks.uuid=luks-b0902490-13
39-4b98-9780-369adef6a275 rd.lvm.lv=centos/swap rhgb quiet LANG=en_GB.UTF-8
package: kernel
uid: 0 (root)
count: 5
Directory: /var/spool/abrt/oops-2017-12-19-19:39:54-1636-4
Reported: cannot be reported

id 47801d437d737823285ec5bf33932ccb8790a89c
reason: WARNING: CPU: 1 PID: 43 at drivers/gpu/drm/drm_irq.c:1237 drm_wait_one_vblank+0x184/0x1d0 [drm]
time: Tue 19 Dec 2017 19:39:54 GMT
cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-693.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.luks.uuid=luks-b0902490-13
39-4b98-9780-369adef6a275 rd.lvm.lv=centos/swap rhgb quiet LANG=en_GB.UTF-8
package: kernel
uid: 0 (root)
count: 5
Directory: /var/spool/abrt/oops-2017-12-19-19:39:54-1636-1
Reported: cannot be reported

id 05944c1a336b4d9b7789705d672f9b664c7dac13
reason: WARNING: CPU: 1 PID: 43 at drivers/gpu/drm/drm_irq.c:1237 drm_wait_one_vblank+0x184/0x1d0 [drm]
time: Tue 19 Dec 2017 20:10:46 GMT
cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-693.11.1.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.luks.uuid=luks-b09024
90-1339-4b98-9780-369adef6a275 rd.lvm.lv=centos/swap rhgb quiet LANG=en_GB.UTF-8
package: kernel
uid: 0 (root)
count: 4
Directory: /var/spool/abrt/oops-2017-12-19-20:10:46-1207-0

RUNNING:

CentOS Linux release 7.4.1708 (Core)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

CentOS Linux release 7.4.1708 (Core)
CentOS Linux release 7.4.1708 (Core)

Apologies if I haven't provided all the required information, as I'm only just learning Linux.

[TrevorH]

Well, first thing is that your life will be much easier if you yum remove abrt\* as no-one ever looks at those bug reports anyway.

A quick google says that appending "video=SVIDEO-1:d" to the kernel command line should help. You can do this in several ways.

The first is a one-shot and will need to be done each time you boot but would be a good way to test if it works without changing anything permanently. When you see the grub menu with the list of kernels to boot, hit 'e' to edit the default entry, scroll down until you find the linux16 (or linuxefi if on a UEFI install) line and append a space followed by video=SVIDEO-1:d to the end of the line then hit Ctrl-x to boot up using that modification.

Test using that first and see if it helps. If it does then make it permanent by either editing /boot/grub2/grub.cfg directly and adding the same parameter to the end of the linux16/linuxefi line for the latest kernel or by editing /etc/default/grub and add the same thing to the GRUB_CMDLINE_LINUX= string there and rerun grub2-mkconfig pointing it to the /boot/grub2/grub.cfg file to overwrite it. If you edit the grub.cfg file directly then it may also be good to edit /etc/default/grub to guard against a subsequent run of grub2-mkconfig backing the change out. Nothing runs grub2-mkconfig directly - only a human does - so this step isn't strictly necessary if you never run it yourself.

If you're on a UEFI system then grub.cfg resides in a different location and runnning find /boot -type f -name "grub.cfg" should find it for you.

[magicBeast]

Thank you for the rapid and detailed response! I tried the fix which worked perfectly, and then updated the GRUB entries. I had come across the solution with reference to another flavour of Linux from several months back when searching Google myself, but wasn't sure that it was applicable to my build.
What exactly is this command to the video doing anyway - and if it's a known issue, why is it still in the most recent build?

[TrevorH]

As far as I can tell, it's telling the video driver to ignore the SVIDEO connector (which isn't even present on a D630) and not try to drive it to emit a video signal.

[roytrubshaw]

Thanks from me also. I too use a Dell Latitude D630 and I found this topic whilst researching the fact that the latest release (1804) broke my X-Windows to the extent that I can no longer boot directly to the graphical target.

This is true of all attempts to boot 7.5: new install, live DVD, or upgrade from a working 7.4 installation (I tried upgrading a pristine 7.4 and my existing 7.4).

I'm fairly certain that it's to do with a difference in the boot sequence, as once I've logged in from the command line I can start X-windows manually and everything is fine.

Not sure if this is a fix for the booting to graphical target, but it does remove a bunch of errors and speeds up my boot process!

PS I'm an old dinosaur that thinks systemd and Gnome3 represent pretty much everything that's wrong with modern software development philosophy

[desertcat]

Well, first thing is that your life will be much easier if you yum remove abrt\* as no-one ever looks at those bug reports anyway.

Thanks TrevorH. I have nuked this too. All those messages have driven me CRAZY I tried to disable abrt thinking the packages needed to be installed with little to no success. This should solve the problem for good. Again thanks for the tip.