Desktop system won't run with Ubuntu 16.04

[Richard Emmerson]

My Intel-based desktop system was working fine with Ubuntu 16.04.3 and Linux 4.13 32/35 up to 12 Feb 18. Since then it has been unable to complete a boot-up, and will only run in recovery-mode. I have found similar symptoms as were previously raised in bug 1568211. These are the boot messages:

:~$ sudo dmesg | egrep 'drm|radeon'
[ 1.803359] [drm] VGACON disable radeon kernel modesetting.
[ 1.803429] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
[ 8.597977] [drm] VGACON disable radeon kernel modesetting.
[ 8.598047] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
[ 29.552451] [drm] VGACON disable radeon kernel modesetting.
[ 29.552497] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
---
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: richard 1817 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=4b36ebcc-b1ad-499c-96c6-a1706f5c11a7
InstallationDate: Installed on 2018-02-21 (16 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=d5aa5d6c-b0b8-4b3c-8016-25e0c3efb9ef ro recovery nomodeset
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-36-generic N/A
 linux-backports-modules-4.13.0-36-generic N/A
 linux-firmware 1.157.17
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: xenial
Uname: Linux 4.13.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/19/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: WBIBX10J.86A.0293.2010.0419.1819
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DP55WB
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE64798-205
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0293.2010.0419.1819:bd04/19/2010:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-205:cvn:ct2:cvr:

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1754571

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4

[Richard Emmerson (richard-emmerson)]

I have retested this with the upstream kernel 4.16.0-041600rc4-generic, and the symptoms are the same: boot-up only gets as far as a frozen log-in screen.

[Joseph Salisbury (jsalisbury)]

Does this bug go away if you boot into the prior kernel?

[Richard Emmerson (richard-emmerson)]

Joseph:

The results are Ubuntu build-dependent:

For 16.04.3 there was no problem with earlier builds such as 4.13 29/32 and the most recent version that worked was 4.13 32/35. All build updates with kernels beyond that show the fault and won't boot-up: they just reach a frozen log-in screen. This includes the current ISO load of 16.04 which has 4.13 36/40.

With 17.10 running on the same hardware, the current kernel is (also) 4.13 36/40 but this does not have the fault - the system boots up normally.

So the fault may not actually be in the kernel!

Regards

Richard

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Joseph Salisbury
Sent: 12 March 2018 14:18
To: <email address hidden>
Subject: [Bug 1754571] Re: Desktop system won't run with latest kernel 4.13 36/40

Does this bug go away if you boot into the prior kernel?

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1754571

Title:
  Desktop system won't run with latest kernel 4.13 36/40

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My Intel-based desktop system was working fine with Ubuntu 16.04.3 and
  Linux 4.13 32/35 up to 12 Feb 18. Since then it has been unable to
  complete a boot-up, and will only run in recovery-mode. I have found
  similar symptoms as were previously raised in bug 1568211. These are
  the boot messages:

  :~$ sudo dmesg | egrep 'drm|radeon'
  [ 1.803359] [drm] VGACON disable radeon kernel modesetting.
  [ 1.803429] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
  [ 8.597977] [drm] VGACON disable radeon kernel modesetting.
  [ 8.598047] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
  [ 29.552451] [drm] VGACON disable radeon kernel modesetting.
  [ 29.552497] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0: richard 1817 F.... pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=4b36ebcc-b1ad-499c-96c6-a1706f5c11a7
  InstallationDate: Installed on 2018-02-21 (16 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=d5aa5d6c-b0b8-4b3c-8016-25e0c3efb9ef ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic N/A
   linux-firmware 1.157.17
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags: xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/19/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WBIBX10J.86A.0293.20...

[Richard Emmerson (richard-emmerson)]

It is now clear that this fault applies to Ubuntu 16.04, not to any specific Linux kernel version. I have found that Ubuntu 17.10 with the same current Linux (4.13 35/40) does not have the fault, but 16.04.3 running on the same hardware and with the same Linux does show the fault: boot-up only progresses to a frozen log-in screen, and the build will only run in recovery mode. The previously reported screen handling problems are almost certainly due to the known reduced display support in this recovery mode, and are not the real fault, which is that these 16.04 builds won't boot-up.