linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: MX28 poweroff issue
Date: Wed, 4 Jul 2012 10:45:06 +0200	[thread overview]
Message-ID: <20120704084506.GE5398@pengutronix.de> (raw)
In-Reply-To: <20120704082049.GI16319@n2100.arm.linux.org.uk>

On Wed, Jul 04, 2012 at 09:20:49AM +0100, Russell King - ARM Linux wrote:
> On Wed, Jul 04, 2012 at 09:07:51AM +0200, Uwe Kleine-K?nig wrote:
> > Hi Marek,
> > 
> > On Wed, Jul 04, 2012 at 05:47:36AM +0200, Marek Vasut wrote:
> > > Dear Fabio Estevam,
> > > 
> > > > On Tue, Jul 3, 2012 at 11:12 PM, Marek Vasut <marex@denx.de> wrote:
> > > > > Dunno, can you try on mx28 please?
> > > > 
> > > > I get the same crash as you reported.
> > > > 
> > > > On a mx27 (also ARM926EJS) I do not see this problem.
> > > 
> > > Thanks for verifying this, Fabio. The mx28 generates timer interrupt after it 
> > > should be sitting in the endless loop, therefore this crash. I think it's 
> > > because the mx28 (mxs at al) is using the new clock framework (compared to mxc) 
> > > and the timer isn't deinited by then ...
> > On an i.MX35 with v3.5-rc4 (which is using the new clock framework in
> > the meantime, but is an ARM11) I don't see this crash.
> 
> Are you who aren't seeing it waiting around 30 seconds after "System halted" ?
I waited longer and had

	CONFIG_DETECT_HUNG_TASK=y
	CONFIG_LOCKUP_DETECTOR=y

in my .config.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2012-07-04  8:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 22:30 MX28 poweroff issue Marek Vasut
2012-07-03 22:46 ` Russell King - ARM Linux
2012-07-04  0:13   ` Marek Vasut
2012-07-04  1:10 ` Fabio Estevam
2012-07-04  2:12   ` Marek Vasut
2012-07-04  3:14     ` Fabio Estevam
2012-07-04  3:47       ` Marek Vasut
2012-07-04  7:07         ` Uwe Kleine-König
2012-07-04  8:20           ` Russell King - ARM Linux
2012-07-04  8:45             ` Uwe Kleine-König [this message]
2012-07-04 14:30               ` Marek Vasut
2012-07-04  7:38       ` Attila Kinali
2012-07-04 14:31         ` Marek Vasut
2012-07-04 14:53           ` Shawn Guo
2012-07-04 15:19           ` Russell King - ARM Linux
2012-07-05 16:08             ` Shawn Guo
2012-07-05 16:23               ` Marek Vasut
2012-07-05 20:32                 ` Fabio Estevam
2012-07-05 20:59                   ` Fabio Estevam
2012-07-05 20:10               ` Russell King - ARM Linux
2012-07-06  4:49                 ` Shawn Guo
2012-07-06  7:32                 ` Lothar Waßmann
2012-07-19 17:04                   ` Marek Vasut
2012-07-20  0:48                     ` Shawn Guo
2012-07-20  1:53                       ` Marek Vasut

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=20120704084506.GE5398@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).