[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170406181318.GE10363@amd>
Date: Thu, 6 Apr 2017 20:13:18 +0200
From: Pavel Machek <pavel@....cz>
To: Tony Lindgren <tony@...mide.com>
Cc: pali.rohar@...il.com, sre@...nel.org,
kernel list <linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-omap@...r.kernel.org, khilman@...nel.org,
aaro.koskinen@....fi, ivo.g.dimitrov.75@...il.com,
patrikbachan@...il.com, serge@...lyn.com, abcloriens@...il.com
Subject: Re: N900 failure in next-20170321
On Tue 2017-03-21 08:38:52, Tony Lindgren wrote:
> * Pavel Machek <pavel@....cz> [170321 06:59]:
> > Hi!
> >
> > Tony asked me to test linux-next from time to time. I did... today I
> > moved from next-20170309 to next-20170321. Kernel boots and seems to
> > work fine (including audio and X startup), but if I leave it sitting
> > for a while RGB LED reverts from "system alive" to charging indication
> > that was disabled before and system does not react to any input.
> >
> > Any ideas?
>
> Not much there I could see affecting this.. Try reverting commit
> 179125085bd4 ("ARM: OMAP3: Fix smartreflex platform data regression")?
>
> Maybe smartreflex now attempts to do something but we're missing
> or have wrong dts configuration for n900?
I tried today's next, and it did not hang for a few hours. So I guess
problem is gone now.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists