MX28 poweroff issue
Marek Vasut
marex at denx.de
Wed Jul 4 10:30:05 EDT 2012
Dear Uwe Kleine-König,
> 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 at 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.
Good, so we can trim this down the being mxs specific bug I guess?
> Best regards
> Uwe
Best regards,
Marek Vasut
More information about the linux-arm-kernel
mailing list