kernel-packages team mailing list archive

[Launchpad Bug Tracker <1486378@xxxxxxxxxxxxxxxxxx>]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1486378

Title:
  Can't boot to GUI or shut down cleanly with kernel 3.13.0-62

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Trusty:
  Expired

Bug description:
  I was prompted today to update to a new kernel, linux-
  image-3.13.0-62-generic, along with its accompanying headers.

  I install kernel updates frequently on my system without any problems.
  To date, Trusty 14.04.3 LTS has been very trusty. But after installing
  linux-image-3.13.0-62-generic, I found my system hanging as it tried
  to reboot. It gave me this message:

  ModemManager[833]: <warn> Could not acquire the
  'org.freedesktop.ModemManager1' service name

  ModemManager[833]: <info> ModemManager is shut down

  It just sat there like that for a long time. Finally I powered it off.

  Upon restarting, the system refused to boot to the GUI. It normally
  flashes an NVDIA logo before showing the login prompt (I use Kubuntu).
  But this time it simply showed a black screen.

  I logged in to check for updates. There were none available.

  I tried rebooting. The system got stuck again. I got it unstuck; still
  it would not boot to the GUI or shut down cleanly.

  After several cycles of this I went into the recovery mode and
  selected the grub option. That allowed me to boot to the GUI. But
  still the system wouldn't shut down cleanly. It showed me a number of
  different messages during the various times I tested its capacity to
  reboot, some similar to the one above and others different. The
  messages were not consistent.

  The command sudo shutdown -r 0 sometimes prevented the system from
  hanging on reboot, but not always.

  At last my suspicion fell on the kernel, since it had just been
  updated and there hadn't been any other packages changed with it. The
  next go-around, I started up with the previous kernel, 3.13.0-61, by
  selecting it in grub on startup. Sure enough, after choosing this
  previous kernel, the system started with no fuss, and it shut down
  gracefully without hanging, too. I promptly uninstalled the kernel
  update and its associated headers so I wouldn't have to hold down the
  shift key on every boot cycle. With linux-image-3.13.0-62-generic
  gone, my system is back to normal operation.

  I can't understand why a kernel update pushed out to a long term
  support release would break my system so horribly. I specifically run
  the LTS release on my main systems to avoid these kinds of issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486378/+subscriptions