From: Kevin Hilman <khilman@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: nfsroot problems with v3.6-rc1 on 37xx EVM and dynamic off-mode
Date: Tue, 07 Aug 2012 14:46:50 -0700 [thread overview]
Message-ID: <87boim1ik5.fsf@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1208031340310.28888@utopia.booyaka.com> (Paul Walmsley's message of "Fri, 3 Aug 2012 14:20:07 -0600 (MDT)")
Hi Paul,
Paul Walmsley <paul@pwsan.com> writes:
> NFS is broken on 37xx EVM with v3.6-rc1 after return from off-mode with
> dynamic idle. System suspend ("echo mem > /sys/power/state") with
> off-mode enabled seems to work fine.
>
> No obvious ideas here as to what could have broken this. It worked in
> v3.5-rc2 + my omap_fixes_a_3.5rc at least:
>
> http://www.pwsan.com/omap/bootlogs/20120617/omap_fixes_a_3.5rc__52a5ae406dadef781bfcf3a641dae2064e9697ff/37xxevm_bootlog.txt
>
> After that, it's hard to tell when this problem started occurring, since
> CORE stopped entering low-power states on OMAP3 on >= v3.5-rc3.
I see the same thing with vanilla v3.6-rc1, but it worked in my pm-cur
branch which has a few fixes that I'm queuing for v3.6-rc. Tracking it
down, it seems the revert patch I just sent out[1] fixes this problem,
but I'm still a bit puzzled as to why.
Can you try v3.6-rc1 + that revert[1] to see if that fixes the problem
for you as well?
Thanks,
Kevin
[1] http://marc.info/?l=linux-omap&m=134437239010649&w=2
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: nfsroot problems with v3.6-rc1 on 37xx EVM and dynamic off-mode
Date: Tue, 07 Aug 2012 14:46:50 -0700 [thread overview]
Message-ID: <87boim1ik5.fsf@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1208031340310.28888@utopia.booyaka.com> (Paul Walmsley's message of "Fri, 3 Aug 2012 14:20:07 -0600 (MDT)")
Hi Paul,
Paul Walmsley <paul@pwsan.com> writes:
> NFS is broken on 37xx EVM with v3.6-rc1 after return from off-mode with
> dynamic idle. System suspend ("echo mem > /sys/power/state") with
> off-mode enabled seems to work fine.
>
> No obvious ideas here as to what could have broken this. It worked in
> v3.5-rc2 + my omap_fixes_a_3.5rc at least:
>
> http://www.pwsan.com/omap/bootlogs/20120617/omap_fixes_a_3.5rc__52a5ae406dadef781bfcf3a641dae2064e9697ff/37xxevm_bootlog.txt
>
> After that, it's hard to tell when this problem started occurring, since
> CORE stopped entering low-power states on OMAP3 on >= v3.5-rc3.
I see the same thing with vanilla v3.6-rc1, but it worked in my pm-cur
branch which has a few fixes that I'm queuing for v3.6-rc. Tracking it
down, it seems the revert patch I just sent out[1] fixes this problem,
but I'm still a bit puzzled as to why.
Can you try v3.6-rc1 + that revert[1] to see if that fixes the problem
for you as well?
Thanks,
Kevin
[1] http://marc.info/?l=linux-omap&m=134437239010649&w=2
next prev parent reply other threads:[~2012-08-07 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 20:20 nfsroot problems with v3.6-rc1 on 37xx EVM and dynamic off-mode Paul Walmsley
2012-08-03 20:20 ` Paul Walmsley
2012-08-07 21:46 ` Kevin Hilman [this message]
2012-08-07 21:46 ` Kevin Hilman
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=87boim1ik5.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.