[Bug 93590] pinctrl_cherryview module will freeze intel NUC5CPYH on boot most of the time
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Jan 5 12:11:55 PST 2016
https://bugs.freedesktop.org/show_bug.cgi?id=93590
Jussi Alanärä <jussi at firstview.fi> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution|--- |NOTOURBUG
--- Comment #3 from Jussi Alanärä <jussi at firstview.fi> ---
(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 at linux.intel.com> (maintainer:PIN CONTROLLER
> - INTEL)
> Heikki Krogerus <heikki.krogerus at linux.intel.com> (maintainer:PIN CONTROLLER
> - INTEL)
> Linus Walleij <linus.walleij at linaro.org> (maintainer:PIN CONTROL SUBSYSTEM)
> linux-gpio at vger.kernel.org (open list:PIN CONTROL SUBSYSTEM)
> linux-kernel at 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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160105/d67239e0/attachment.html>
More information about the intel-gfx-bugs
mailing list