kernel-packages team mailing list archive

[Jussi Alanärä <jussi@xxxxxxxxxxxx>]

As I've been struggling with this same thing for couple of weeks, I'll
provide the info requested.

I have 3 NUC models and 2 of them are affected by this same thing. The
one that works is the i3 version NUC5i3RYKH.

These have this problem, they  will boot maybe 1 time out of 20 tries,
reboot tends to hang too:

NUC5PPYH and NUC5CPYH, one is Pentium version and the other one is
Celeron version. These both share same BIOS code. I didn't have such
luck that the old BIOS version 0043 would work, they all behave the same
as reported earlier in this post.

Information requested:

PYBSWCEL.86A.0047.2015.1123.0950
11/23/2015

-- 
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/1521749

Title:
  NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Intel NUC NUC5CPYH. This is the unit:
  http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5cpyh.html

  It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-
  image-3.19.0-34-generic -- but when I try to boot with  linux-
  image-4.2.0-19-generic  I simply see the following:

  https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0

  The keyboard stops responding after this line: systemd[1]: Started
  udev Kernel Device Manager.

  Here is output from lspci -vnvn < http://pastie.org/10596250 - I am
  running headless, so there is no Xorg (or any other X server)
  installed.

  - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (also: noacpi noapic)
  - I tried disabling devices in the bios like audio
  - Tried selecting "Ubuntu, with Linux 4.2.0-19-generic (recovery mode)" from the list, it does not boot into the recovery console either :(
  - I tried installing a clean 15.10 version on a blank hard drive (with debootstrap so latest packages)

  I am able to boot if I add systemd.unit=emergency.target to the kernel
  line. I can run "systemctl start networking" for example and it works,
  but if I run "systemctl start apport" (or ssh even) - I see this and
  the system freezes:

  https://www.dropbox.com/s/gmpse7bx0c70e4v/IMG_1479.jpg?dl=0

  I am not sure how to troubleshoot further. When I reboot and select
  Kernel 3.19, there is nothing in /var/log/syslog or journalctl from
  the failed boot :(

  Any suggestions?

  - EDIT: It seems downgrading from the latest PY0044 BIOS version to
  PY0043 allows me to boot the system, but it freezes if running
  "reboot" - more details in this bug report:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201

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