From: Francesco VIRLINZI <francesco.virlinzi@st.com>
To: Francesco VIRLINZI <francesco.virlinzi@st.com>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: Need help on Suspend on RAM
Date: Tue, 30 Sep 2008 11:07:18 +0200 [thread overview]
Message-ID: <48E1EC46.9090103@st.com> (raw)
In-Reply-To: <48E1D492.5040606@st.com>
Hi all
I think I find a fix (?)
In the file:
kernel/time/timekeeping.c
I'm removing the functions:
- timekeeping_suspend and
- timekeeping_resume
I forgot to say that I have no real ClockSource (this means that in
suspend also the clocksource is suspended...)
Could it be a fix or there is an other solution?
Regards
Francesco
Francesco VIRLINZI ha scritto:
> Hi all
> I'm working on Suspend on RAM on kernel 2.6.23.17 on a Sh4 based platform.
> The suspend on RAM seems really working.
> But it I suspend the board more then 3/4 times than the system doesn't
> resume the user space
> but via JTAG I see the kernel is running.
>
> I enabled CONFIG_DETECT_SOFTLOCKUP and the kernel prints:
>
> |BUG: soft lockup detected on CPU#0|
>
> Moreover I installed the patch suggested in http://lwn.net/Articles/287024/
> and it seems the kernel is running in:
> - run_timer_softirq
>
>
> and doing some other test I can confirm the kernel is really there...
>
> In the board there is no real RTC... All the 'time' is based on the
> system timer
> and between suspend/resume the timer is really stopped.
>
> Do you have some suggestion?
>
> Regards
> Ciao
> Francesco
> _______________________________________________
> linux-pm mailing list
> linux-pm@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/linux-pm
>
>
next prev parent reply other threads:[~2008-09-30 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 7:26 Need help on Suspend on RAM Francesco VIRLINZI
2008-09-30 9:07 ` Francesco VIRLINZI [this message]
2008-10-08 17:01 ` Pavel Machek
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=48E1EC46.9090103@st.com \
--to=francesco.virlinzi@st.com \
--cc=linux-pm@lists.linux-foundation.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