From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: MX28 poweroff issue
Date: Wed, 4 Jul 2012 05:47:36 +0200 [thread overview]
Message-ID: <201207040547.37021.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5Ab-Zibnn-tVfTz5BNJsqJer88jZLVa5Een9DDZ3tdssg@mail.gmail.com>
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 ...
Disabling interrupts might be just the right solution, though I'm not sure if
it's not hiding bugs ...
> Regards,
>
> Fabio Estevam
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-07-04 3:47 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 [this message]
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
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=201207040547.37021.marex@denx.de \
--to=marex@denx.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).