From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] mackerel: Do not enable TMU timer in default config
Date: Tue, 28 Feb 2012 06:09:09 +0000 [thread overview]
Message-ID: <20120228060908.GJ9994@linux-sh.org> (raw)
In-Reply-To: <1329111377-15676-1-git-send-email-horms@verge.net.au>
On Tue, Feb 28, 2012 at 02:23:45AM +0100, Rafael J. Wysocki wrote:
> However, having looked at both sh_tmu and sh_cmt I don't see why the former
> should break things (during boot), while the latter doesn't, so I've done
> some more testing and, surprisingly enough, it turns out that disabling runtime
> PM in sh-sci makes the boot hang with sh_tmu enabled go away. So perhaps sh_tmu
> is just a messenger here and the real problem is with sh-sci.
>
> I think that more investigation is needed.
>
Do you see any different behaviour with early printk enabled vs disabled?
We did have the ordering issues before with the pm calls hanging or
oopsing in the early path, but all of those should have been fixed
already. There have been quite a few sh-sci changes though, so if it
worked previously it should be bisectable at least.
next prev parent reply other threads:[~2012-02-28 6:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 5:36 [PATCH] mackerel: Do not enable TMU timer in default config Simon Horman
2012-02-13 23:33 ` Paul Mundt
2012-02-14 0:35 ` Simon Horman
2012-02-23 10:06 ` Simon Horman
2012-02-23 15:30 ` Paul Mundt
2012-02-23 22:14 ` Rafael J. Wysocki
2012-02-26 22:57 ` Rafael J. Wysocki
2012-02-27 0:55 ` Simon Horman
2012-02-27 6:06 ` Paul Mundt
2012-02-27 22:30 ` Rafael J. Wysocki
2012-02-28 1:23 ` Rafael J. Wysocki
2012-02-28 1:38 ` Simon Horman
2012-02-28 6:09 ` Paul Mundt [this message]
2012-02-28 9:29 ` Simon Horman
2012-02-28 23:59 ` Rafael J. Wysocki
2012-02-29 1:32 ` Simon Horman
2012-03-02 23:27 ` Rafael J. Wysocki
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=20120228060908.GJ9994@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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).