public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: "Hu, Fenghua" <fenghua.hu@intel.com>
Cc: linux-acpi@vger.kernel.org, linux-pm@lists.osdl.org,
	lhcs-devel@lists.sourceforge.net
Subject: Re: [linux-pm] Kernel panic after resuming from S4 on Napa dual-core.
Date: Sat, 15 Jul 2006 12:04:05 +0000	[thread overview]
Message-ID: <20060715120405.GB9849@ucw.cz> (raw)
In-Reply-To: <076F541A621E59428B837DCEA0AEDB587A227B@bjsmsx401>

On Wed 12-07-06 09:29:40, Hu, Fenghua wrote:
> Hi all,
> 
> I am struggling with a S4 issue. On a Napa dual-core laptop, sometimes
> when resuming from S4, kernel panic occurs, then system reboots. After
> some investigation, I found it's due to CPU1(AP) can't be woken up in
> time, and
> this can be alleviated, even eliminated by introducing more delay in
> function wakeup_secondary_cpu().In official kernel tree, there were
> three lines in this function for delaying: mdelay(10), udelay(300) and
> udelay(200), now I changed them all to mdelay(500). Seems incorrect
> timing has led to the issue. Could you help me to root cause it? Thanks.

Do you have a copy of panic message and a patch? Or perhaps you just
want to ask on lkml for testing?

-- 
Thanks for all the (sleeping) penguins.

  reply	other threads:[~2006-07-15 12:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12  1:29 Kernel panic after resuming from S4 on Napa dual-core Hu, Fenghua
2006-07-15 12:04 ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-26  5:45 Hu, Fenghua
2006-07-26  6:19 ` [linux-pm] " 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=20060715120405.GB9849@ucw.cz \
    --to=pavel@suse.cz \
    --cc=fenghua.hu@intel.com \
    --cc=lhcs-devel@lists.sourceforge.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@lists.osdl.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