NUC NUC5CPYH Does not reboot 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 and reboots 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 on the latest PY0044 BIOS version, it freezes on boot almost every time, reported bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749

If I downgrade the BIOS to PY0043, it boots most of the time, but when I run "reboot" it freezes almost every single time. This is what I see on the screen when it freezes:

https://www.dropbox.com/s/fxy4opcqwnmjmwo/IMG_1489.jpg?dl=0

I am also attaching the full syslog, dmesg and the relevant part of the syslog when the system froze.

I tried to boot with acpi_osi="Windows 2013" as well as Windows 2015 and Windows 2009, that did not seem to make any difference.

Any ideas?

---
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
DistroRelease: Ubuntu 15.10

ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=4fa37335-eed0-4580-ae4b-62c996dfc275 ro vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-19-generic N/A
 linux-backports-modules-4.2.0-19-generic N/A
 linux-firmware 1.149.3
RfKill: Error: [Errno 2] No such file or directory
Tags: wily
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.2.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 09/04/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
dmi.board.name: NUC5CPYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H61145-404
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

[hackeron (hackeron)]

Dmesg on booted system with old BIOS version (does not boot with latest BIOS version)

[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)]

apport information

[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 1522201

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)]

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

[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.

[hackeron (hackeron)]

When the bug was reported, I used the latest version of the BIOS available for download. I am presently abroad, but I will download and try with PY0047 when I am back on the 26th.

[szotman (szotman)]

I can confirm reboot issue with NUC5CPYH under Linux (no post, no signal on monitor). Tested with PY0043, 44 and 47, problem affects ~20 devices at me. Have you tried unplug ethernet cable? This somehow "fixes" the problem. Maybe this could guide for a solution?

[Jussi Alanärä (jusii)]

I'll confirm this too, bios information:

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

reboot seems to work

[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.

[Launchpad Janitor (janitor)]

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