NUC NUC5CPYH Does not boot on Ubuntu 15.10 (4.2.0-22-generic) most of the time

Bug #1529353 reported by Jussi Alanärä
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
High
Unassigned

Bug Description

Ubuntu 15.10 (4.2.0-22-generic) boots approximately 1 out of 10 times.

WORKAROUND: BIOS > Boot > Boot Configuration > OS Selection > set Linux

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-22-generic 4.2.0-22.27
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
Uname: Linux 4.2.0-22-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ft 1129 F.... pulseaudio
Date: Sat Dec 26 10:05:57 2015
HibernationDevice: RESUME=UUID=626569d7-4b44-48b3-899f-7ddbba3e91cf
InstallationDate: Installed on 2015-12-26 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp.
 Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
 Bus 001 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic.efi.signed root=UUID=c4ff92fb-cd16-4cc1-a933-f7224b033416 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-22-generic N/A
 linux-backports-modules-4.2.0-22-generic N/A
 linux-firmware 1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: PYBSWCEL.86A.0047.2015.1123.0950
dmi.board.name: NUC5CPYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H61145-402
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0047.2015.1123.0950:bd11/23/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-402:cvn:ct3:cvr:

Revision history for this message
Jussi Alanärä (jusii) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Jussi Alanärä (jusii) wrote :

This time testing Ubuntu booted maybe once per 10 tries.

Revision history for this message
penalvch (penalvch) wrote :

Jussi Alanärä, thank you for reporting this and helping make Ubuntu better.

At your earliest convenience, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-0047
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
description: updated
Revision history for this message
Jussi Alanärä (jusii) wrote :

Tried the latest kernel Linux ft-desktop 4.4.0-040400rc6-generic #201512202030 SMP Mon Dec 21 01:32:09 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux and it made no difference.

Then started to go back and see which is the last kernel that always boots reliable, and that one seems to be

Linux ft-desktop 3.18.25-031825-generic #201512152250 SMP Wed Dec 16 03:52:48 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

around 30 succesful boots now, will leave it in reboot loop until tomorrow.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Jussi Alanärä, the next step is to fully commit bisect from kernel 3.18 to 3.19 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

After the offending commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.4-rc6 needs-bisect regression-release
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jussi Alanärä (jusii) wrote :

I'm a bit lost now, here's what I've done:

First tried bisecting vanilla kernel from linus tree and they seem to work just fine upto 4.4-rc7 so this is something Ubuntu specific. I tried also v4.4-rc7-wily from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D and problem is still there.

I can't use git://kernel.ubuntu.com/ubuntu/ubuntu-wily.git because even the first kernel tag won't work so I backed to //kernel.ubuntu.com/ubuntu/ubuntu-vivid.git

I have git tags that I should bisect between and those are Ubuntu-3.18.0-13.14 and Ubuntu-3.19.0-7.7 which will list with: git tag command

But then I run into this problem (debian and debian.master directories missing) https://wiki.ubuntu.com/Kernel/KernelBisection#Why_did_the_folders_debian_and_debian.master_disappear.3F

and when I run
git rev-list Ubuntu-3.19.0-7.7 | grep $(git log --pretty=oneline -1 Ubuntu-3.18.0-13.14 | cut -d' ' -f1)
as suggested here https://wiki.ubuntu.com/Kernel/KernelBisection#Commit_bisecting_Ubuntu_kernel_versions_across_non-linear_tags

I get no sha1 so that suggests that tags aren't linear.

And from here I looked for the git tags http://people.canonical.com/~kernel/info/kernel-version-map.html

Revision history for this message
Jussi Alanärä (jusii) wrote :

Ok., got it.

root@compile:/Devel/Bisect/ubuntu-vivid# git bisect bad
6b960cc46469ef40ae4f23ff2ad63ab094834de7 is the first bad commit
commit 6b960cc46469ef40ae4f23ff2ad63ab094834de7
Author: Andy Whitcroft <email address hidden>
Date: Thu Jan 22 18:48:32 2015 +0000

    UBUNTU: [Config] apply Device Drivers >> Pin controllers config defaults

    Signed-off-by: Andy Whitcroft <email address hidden>

:040000 040000 b6fc06ffcfb12018b7b52e72b4f492992249c8b2 327eb4e8852ee82ef39134e73d459f3832f0efc9 M debian.master

root@compile:/Devel/Bisect/ubuntu-vivid# git diff 6b960cc46469ef40ae4f23ff2ad63ab094834de7^!
diff --git a/debian.master/config/config.common.ubuntu b/debian.master/config/config.common.ubuntu
index e731fd7..7a90788 100644
--- a/debian.master/config/config.common.ubuntu
+++ b/debian.master/config/config.common.ubuntu
@@ -5351,7 +5351,7 @@ CONFIG_PINCTRL_BERLIN=y
 CONFIG_PINCTRL_BERLIN_BG2=y
 CONFIG_PINCTRL_BERLIN_BG2CD=y
 CONFIG_PINCTRL_BERLIN_BG2Q=y
-# CONFIG_PINCTRL_CHERRYVIEW is not set
+CONFIG_PINCTRL_CHERRYVIEW=m
 CONFIG_PINCTRL_DOVE=y
 CONFIG_PINCTRL_EXYNOS=y
 CONFIG_PINCTRL_EXYNOS5440=y
@@ -5371,7 +5371,7 @@ CONFIG_PINCTRL_PFC_R8A7740=y
 CONFIG_PINCTRL_PFC_R8A7779=y
 CONFIG_PINCTRL_PFC_R8A7790=y
 CONFIG_PINCTRL_PFC_R8A7791=y
-# CONFIG_PINCTRL_QCOM_SPMI_PMIC is not set
+CONFIG_PINCTRL_QCOM_SPMI_PMIC=m
 CONFIG_PINCTRL_SAMSUNG=y
 CONFIG_PINCTRL_SH_PFC=y
 CONFIG_PINCTRL_SINGLE=y

And sure enough, by removing pinctrl-cherryview.ko Ubuntu will boot nicely even with the latest linux-image-4.2.0-22-generic

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: bisect-done
removed: needs-bisect
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jussi Alanärä (jusii) wrote :

I f I enable CONFIG_PINCTRL_CHERRYVIEW=m in 4.4-rc7 then it won't boot.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Jussi Alanärä (jusii) wrote :

And add to that comment from hackeron in here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749

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

above holds true, if Linux is chosen in Bios, then pinctrl_cherryview.ko will load just fine and Ubuntu will boot.

penalvch (penalvch)
description: updated
tags: added: kernel-bug-exists-upstream-4.4-rc7
removed: kernel-bug-exists-upstream-4.4-rc6
Revision history for this message
penalvch (penalvch) wrote :

Jussi Alanärä, in order to engage Intel upstream, could you please test for this via drm-intel-nightly and advise to the results?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jussi Alanärä (jusii) wrote :

Just tested with linux-image-4.4.0-994-generic_4.4.0-994.201512302100_amd64.deb from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/ and same thing, won't boot.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Revision history for this message
Jussi Alanärä (jusii) wrote :

Looks like intel-gfx wasn't correct place. I'll follow info and instructions given there and will update here.

https://bugs.freedesktop.org/show_bug.cgi?id=93590

Revision history for this message
penalvch (penalvch) wrote :

Jussi Alanärä, as per the maintainer list, one would want to send TO Mika Westerberg, and Heikki Krogerus, CC linux-gpio.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.