Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754011AbbGANJO (ORCPT ); Wed, 1 Jul 2015 09:09:14 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:53428 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753572AbbGANJF (ORCPT ); Wed, 1 Jul 2015 09:09:05 -0400 Date: Wed, 1 Jul 2015 15:09:03 +0200 From: Pavel Machek To: Tony Lindgren Cc: Pali =?iso-8859-1?Q?Roh=E1r?= , sre@debian.org, sre@ring0.de, kernel list , linux-arm-kernel , linux-omap@vger.kernel.org, khilman@kernel.org, aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com, patrikbachan@gmail.com Subject: Re: n900 in 4.2-rc0: repeating oopses Message-ID: <20150701130903.GG7969@amd> References: <20150416093234.GA17423@amd> <20150629091146.GA5103@amd> <20150630092404.GA19285@amd> <20150630095310.GF27720@pali> <20150701065932.GS4156@atomide.com> <20150701072255.GA17577@pali> <20150701095954.GD7969@amd> <20150701103421.GV4156@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150701103421.GV4156@atomide.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1728 Lines: 47 On Wed 2015-07-01 03:34:22, Tony Lindgren wrote: > * Pavel Machek [150701 03:02]: > > On Wed 2015-07-01 09:22:55, Pali Roh?r wrote: > > > On Tuesday 30 June 2015 23:59:33 Tony Lindgren wrote: > > > > * Pali Roh?r [150630 02:55]: > > > > > > > > > > I will try 4.2 at the end of week. > > > > > > > > At least today's 4.1.0-11549-g05a8256 boots just fine on my n900. > > > > > > > > Regards, > > > > > > > > Tony > > > > > > So, Pavel can you re-test? Maybe there can be problem with some driver > > > which Tony did not compiled into zImage? Just speculation... > > > > I re-tested with today's git, and it seems to boot. Thanks for help... > > OK good to hear. > > > Now. "echo mem > /sys/power/state" is broken, as in "returns > > immediately in about 50% cases". The messages are > > > > Powerdomain (per_pwrdm) didn't enter target state 1 > > Powerdomain (core_pwerdm) didn't enter target state 1 > > > > Any ideas? Thanks, > > Works for me after enabling the idle timeouts with the following > script and blanking the screen and disconnecting USB: Um. I'm forcing suspend with "echo mem > /sys/power/state" . (It worked in 4.1). That should just make it sleep, no autosuspend-related trickery... (But yes, I guess I should set up the leds and try autosuspend, too.) Regards, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/