From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: pali.rohar@gmail.com, sre@kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, khilman@kernel.org,
aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com
Subject: Re: N900 failure in next-20170321
Date: Thu, 6 Apr 2017 20:13:18 +0200 [thread overview]
Message-ID: <20170406181318.GE10363@amd> (raw)
In-Reply-To: <20170321153851.GA10760@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
On Tue 2017-03-21 08:38:52, Tony Lindgren wrote:
> * Pavel Machek <pavel@ucw.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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2017-04-06 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 13:57 N900 failure in next-20170321 Pavel Machek
2017-03-21 15:38 ` Tony Lindgren
2017-04-06 18:13 ` Pavel Machek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170406181318.GE10363@amd \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=abcloriens@gmail.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=patrikbachan@gmail.com \
--cc=serge@hallyn.com \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox