From: simon.guinot@sequanux.org (Simon Guinot)
To: linux-arm-kernel@lists.infradead.org
Subject: Reboot hangs on Kirkwood ns2 boards with 3.8-rc2
Date: Mon, 7 Jan 2013 16:09:18 +0100 [thread overview]
Message-ID: <20130107150918.GI1357@kw.sim.vm.gnt> (raw)
In-Reply-To: <20130106083521.GO17242@lunn.ch>
On Sun, Jan 06, 2013 at 09:35:21AM +0100, Andrew Lunn wrote:
> On Sun, Jan 06, 2013 at 04:34:55AM +0100, Simon Guinot wrote:
> > Hi Andrew and Jason,
> >
> > While testing 3.8-rc2 on the ns2 boards (DT based), I noticed that
> > reboot is not working. After issuing a reboot, the kernel hangs. No
> > error messages are displayed. Moreover, on my non-DT Kirkwood boards,
> > reboot is working as expected.
> >
> > Am I the only one to experiment this issue ?
>
> Hi Simon
>
> No you are not the only one. There is a patch available, authored by
> me, which is identical to what you found.
Arf, it's a shame I have missed this reports. It could have spared some
time by asking at you earlier.
About the issue itself. I understand that a clock is needed by the
orion-ehci driver. But even if the clock is not provided by the DT, it
should have been fixed by kirkwood_legacy_clk_init(), isn't ? What's
wrong with this workaround ?
Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130107/97467bf1/attachment.sig>
next prev parent reply other threads:[~2013-01-07 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 3:34 Reboot hangs on Kirkwood ns2 boards with 3.8-rc2 Simon Guinot
2013-01-06 8:35 ` Andrew Lunn
2013-01-07 15:09 ` Simon Guinot [this message]
2013-01-07 15:25 ` Andrew Lunn
2013-01-07 15:32 ` Simon Guinot
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=20130107150918.GI1357@kw.sim.vm.gnt \
--to=simon.guinot@sequanux.org \
--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