From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: Reboot hangs on Kirkwood ns2 boards with 3.8-rc2
Date: Sun, 6 Jan 2013 09:35:21 +0100 [thread overview]
Message-ID: <20130106083521.GO17242@lunn.ch> (raw)
In-Reply-To: <20130106033455.GH1357@kw.sim.vm.gnt>
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.
We have been a bit slow recently pushing fixes into 3.8-rc, vacations,
etc. I plan to spend some time today collecting the fixes together and
sending them upstream.
Andrew
next prev parent reply other threads:[~2013-01-06 8:35 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 [this message]
2013-01-07 15:09 ` Simon Guinot
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=20130106083521.GO17242@lunn.ch \
--to=andrew@lunn.ch \
--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