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

[hackeron]

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

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1521749

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.

[hackeron (hackeron)]

apport information

[hackeron (hackeron)]

apport information

[hackeron (hackeron)]

apport information

[hackeron (hackeron)]

apport information

[hackeron (hackeron)]

apport information

[hackeron (hackeron)]

apport information

[hackeron (hackeron)]

apport information

[hackeron (hackeron)]

apport information

[hackeron (hackeron)]

apport information

[hackeron (hackeron)]

apport information

[hackeron (hackeron)]

apport information

[hackeron (hackeron)]

I am able to boot the system if I downgrade the BIOS to PY0043 from PY0044. However there are still side effects that are not present on linux-image-3.19.0-34-generic - for instance, I cannot reboot the system. More details in this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201

[hackeron (hackeron)]

I also reported this to Intel here: https://communities.intel.com/thread/94213

[Matthias Goldhoorn (matthias-l)]

affected kernel linux-image-4.2.0-16-generic linux-image-4.2.0-18-generic
earlier versions thatn -16 not availible in the repro and i not checked. This starts really to annoy me...

[Matthias Goldhoorn (matthias-l)]

I downgraded to:
3.19.0-28-generic

which works fine

[penalvch (penalvch)]

hackeron, thank you for reporting this and helping make Ubuntu better.

As per https://downloadcenter.intel.com/product/85254/Intel-NUC-Kit-NUC5CPYH an update to your computer's buggy and outdated BIOS is available (0047). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement or not.
3) If the issue is still reproducible, please mark this report Status Confirmed. Otherwise, please mark this as Invalid.

Thank you for your understanding.

[Jussi Alanärä (jusii)]

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

[Jussi Alanärä (jusii)]

Just tried Ubuntu Xenial Xerus

ft@ft-desktop:~$ uname -a
Linux ft-desktop 4.3.0-2-generic #11-Ubuntu SMP Fri Dec 4 20:37:48 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Xenial seems to boot way better, but not always. When it freezes on boot, it's at this point always:

https://goo.gl/photos/cMHqgxD3yU5hYzr76

[Jussi Alanärä (jusii)]

And this is from 15.10 where it freezes always on boot

https://goo.gl/photos/tKjmGeZmPbrnTPQm6

[penalvch (penalvch)]

Jussi Alanärä, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[hackeron (hackeron)]

How many people do you want to run ubuntu-bug linux? - I already ran it in the original bug report.

[penalvch (penalvch)]

hackeron, as documented in https://wiki.ubuntu.com/ReportingBugs it's not a how many issue, nor is it relevant if you ran something or not.

[hackeron (hackeron)]

I don't understand - I already ran ubuntu-bug - others have confirmed the issue. Why do you need it ran again?

[Jussi Alanärä (jusii)]

Done https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529353

[hackeron (hackeron)]

It seems the following helps: BIOS > Boot > Boot Configuration > OS Selection > set Linux

However this is not required in previous versions of the kernel and it is not practical to do this when all of your NUC machines are in different locations across the country :(

[Jussi Alanärä (jusii)]

Hackeron, you're correct, this indeed fixes it. But not completely happy with it either, so I'll continue to bisect the kernel in that other bug thread.

But thanks for this, helps a lot in meanwhile.

[Jussi Alanärä (jusii)]

Ok, found it see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529353

[hackeron (hackeron)]

Thank you for that. I've actually switched to 15.04 because 15.10 seems to be unusable on these NUCs :( -- But for those NUCs already on 15.10 I will blacklist pinctrl-cherryview as you suggest, thank you!!

[hackeron (hackeron)]

I think "blacklist pinctrl-cherryview" helps with boot, but now experiencing stability issues: the system freezes after a few days of operation which never happened before on 15.04 :( -- do you experience any similar issues? any solution?

[Launchpad Janitor (janitor)]

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

[Alan Jenkins (aj504)]

hackeron, search for "intel_idle.max_cstate=1" in relation to this hardware; it's a workaround for random freezes which (some) people are encountering.