Bug 93590 - pinctrl_cherryview module will freeze intel NUC5CPYH on boot most of the time
Summary: pinctrl_cherryview module will freeze intel NUC5CPYH on boot most of the time
Status: CLOSED NOTOURBUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-05 12:42 UTC by Jussi Alanärä
Modified: 2017-07-24 22:43 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg output (179.12 KB, text/plain)
2016-01-05 12:42 UTC, Jussi Alanärä
no flags Details

Description Jussi Alanärä 2016-01-05 12:42:04 UTC
Created attachment 120811 [details]
dmesg output

If CONFIG_PINCTRL_CHERRYVIEW=m is enabled in config, intel NUC5CPYH (also NUC5PPYH tested, same thing) will freeze on boot 9 out of 10 times. Also, after succesful boot reboot will most likely fail, HDMI will turn of and hang there.

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

With above BIOS settings, it boots just fine and also reboot works.

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

Following information is gathered when BIOS setting for OS Selection is Windows 8/10

Kernel used http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2016-01-05-wily/linux-image-4.4.0-994-generic_4.4.0-994.201601042100_amd64.deb

ft@ft-desktop:~$ uname -a
Linux ft-desktop 4.4.0-994-generic #201601042100 SMP Tue Jan 5 02:02:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

ft@ft-desktop:~$ uname -r
4.4.0-994-generic

Ubuntu 15.10

Intel NUC5CPYH (also NUC5PPYH)

root@ft-desktop:/home/ft# dmidecode -s bios-version && dmidecode -s bios-release-date
PYBSWCEL.86A.0047.2015.1123.0950
11/23/2015

Base Board Information
        Manufacturer: Intel Corporation
        Product Name: NUC5CPYB
        Version: H61145-404
        Serial Number: GEPY54700FNR

HDMI display output used in testing

ft@ft-desktop:~$ lspci
00:00.0 Host bridge: Intel Corporation Device 2280 (rev 21)
00:02.0 VGA compatible controller: Intel Corporation Device 22b1 (rev 21)
00:13.0 SATA controller: Intel Corporation Device 22a3 (rev 21)
00:14.0 USB controller: Intel Corporation Device 22b5 (rev 21)
00:1a.0 Encryption controller: Intel Corporation Device 2298 (rev 21)
00:1b.0 Audio device: Intel Corporation Device 2284 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 22c8 (rev 21)
00:1c.1 PCI bridge: Intel Corporation Device 22ca (rev 21)
00:1c.2 PCI bridge: Intel Corporation Device 22cc (rev 21)
00:1f.0 ISA bridge: Intel Corporation Device 229c (rev 21)
00:1f.3 SMBus: Intel Corporation Device 2292 (rev 21)
02:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
Comment 1 Jani Nikula 2016-01-05 14:22:22 UTC
(In reply to Jussi Alanärä from comment #0)
> If CONFIG_PINCTRL_CHERRYVIEW=m is enabled in config, intel NUC5CPYH (also
> NUC5PPYH tested, same thing) will freeze on boot 9 out of 10 times. Also,
> after succesful boot reboot will most likely fail, HDMI will turn of and
> hang there.

Can you reproduce the hang if you blacklist i915 (and ensure it is not probed at boot), or add "nomodeset" module parameter?

Can you reproduce the hang if you blacklist pinctrl-cherryview (and ensure it is not probed at boot)? If it doesn't hang, what if you modprobe it manually after the boot?

Despite what you've been told at launchpad, this does not seem like a graphics issue to me. The maintainers for the pinctrl driver are:

$ scripts/get_maintainer.pl -f drivers/pinctrl/intel/pinctrl-cherryview.c
Mika Westerberg <mika.westerberg@linux.intel.com> (maintainer:PIN CONTROLLER - INTEL)
Heikki Krogerus <heikki.krogerus@linux.intel.com> (maintainer:PIN CONTROLLER - INTEL)
Linus Walleij <linus.walleij@linaro.org> (maintainer:PIN CONTROL SUBSYSTEM)
linux-gpio@vger.kernel.org (open list:PIN CONTROL SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)

Please mail them (with the lists in Cc:) and/or file a bug at http://bugzilla.kernel.org.

I'll leave this open for a while still, but smells like RESOLVED NOTOURBUG.
Comment 2 Jani Nikula 2016-01-05 15:11:04 UTC
Mika Westerberg says, please try CONFIG_DW_DMAC=n. Possibly a known issue.
Comment 3 Jussi Alanärä 2016-01-05 20:11:55 UTC
(In reply to Jani Nikula from comment #1)
> (In reply to Jussi Alanärä from comment #0)
> > If CONFIG_PINCTRL_CHERRYVIEW=m is enabled in config, intel NUC5CPYH (also
> > NUC5PPYH tested, same thing) will freeze on boot 9 out of 10 times. Also,
> > after succesful boot reboot will most likely fail, HDMI will turn of and
> > hang there.
> 
> Can you reproduce the hang if you blacklist i915 (and ensure it is not
> probed at boot), or add "nomodeset" module parameter?

Tried, blacklisting i915 has no effect, still hangs.

> 
> Can you reproduce the hang if you blacklist pinctrl-cherryview (and ensure
> it is not probed at boot)? If it doesn't hang, what if you modprobe it
> manually after the boot?

If I blacklist pinctrl-cherryview, everything works, no hang. Also, if modprobe it later, no problems. Freezes only when modprobed during boot.

> 
> Despite what you've been told at launchpad, this does not seem like a
> graphics issue to me. The maintainers for the pinctrl driver are:
> 
> $ scripts/get_maintainer.pl -f drivers/pinctrl/intel/pinctrl-cherryview.c
> Mika Westerberg <mika.westerberg@linux.intel.com> (maintainer:PIN CONTROLLER
> - INTEL)
> Heikki Krogerus <heikki.krogerus@linux.intel.com> (maintainer:PIN CONTROLLER
> - INTEL)
> Linus Walleij <linus.walleij@linaro.org> (maintainer:PIN CONTROL SUBSYSTEM)
> linux-gpio@vger.kernel.org (open list:PIN CONTROL SUBSYSTEM)
> linux-kernel@vger.kernel.org (open list)
> 
> Please mail them (with the lists in Cc:) and/or file a bug at
> http://bugzilla.kernel.org.
> 
> I'll leave this open for a while still, but smells like RESOLVED NOTOURBUG.

Thanks, and you're correct. I'll look in to that direction.
Comment 4 Jussi Alanärä 2016-01-05 20:12:55 UTC
(In reply to Jani Nikula from comment #2)
> Mika Westerberg says, please try CONFIG_DW_DMAC=n. Possibly a known issue.

Thanks, I'll try that and search with info given.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.