All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Johannes Stezenbach <js@sig21.net>
Cc: linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: 2.6.30: hibernation/swsusp stuck in disable_nonboot_cpus
Date: Thu, 11 Jun 2009 22:21:57 +0200	[thread overview]
Message-ID: <200906112221.57926.rjw@sisk.pl> (raw)
In-Reply-To: <20090611165608.GA4908@sig21.net>

On Thursday 11 June 2009, Johannes Stezenbach wrote:
> Hi,
> 
> on my work machine susend-to-disk is broken in 2.6.30.  Last
> known working kernel was 2.6.29.1. I'm running a 32bit kernel.
> CPU is an AMD Athlon(tm) Dual Core Processor 4850e.
> Board is a Gigabyte GA-MA78GM-S2H rev 1.1.
> 
> - usually it stops on suspend after the message
>   "Suspending console(s) (use no_console_suspend to debug)"
> 
> - I booted with no_console_suspend using serial console
>   as recommended in Documentation/power/basic-pm-debugging.txt.
> 
>   No joy, apparently the serial driver is disabled during suspend
>   and no interesting output on serial console...
> 
> - no_console_suspend on VESA fb console worked better, last msg is
>   "Disabling non-boot CPUs ..."
> 
> - I stripped down my config, and after serveral retries
>   it _sometimes_ gets past the "Disabling non-boot CPUs ...".
>   Then the last lines are (penciled from screen):
> 
>       Enabling non-boot CPUs ...
>       SMP alternatives: switching to SMP code
>       Booting processor 1 APIC 0x1 ip 0x6000
>       Initializing CPU#1
>       Stuck ??
>       Error taking CPU#1 up: -5
> 
>   I also got past this point once, but then it hung at the
>   same spot on resume.
> 
> - I tried    echo 0 > /sys/devices/system/cpu/cpu1/online
> 
>      CPU 1 is now offline
>      SMP alternatives: switching to UP code
>      CPU0 attaching NULL sched-domain.
>      CPU1 attaching NULL sched-domain.
>      CPU0 attaching NULL sched-domain.
>      PM: Removing info for No Bus:msr1
>      PM: Removing info for No Bus:cpu1
> 
> - and     echo 1 > /sys/devices/system/cpu/cpu1/online
> 
>      PM: Adding info for No Bus:msr1
>      PM: Adding info for No Bus:cpu1
>      SMP alternatives: switching to SMP code
>      Booting processor 1 APIC 0x1 ip 0x6000
>      Initializing CPU#1
>      Calibrating delay using timer specific routine.. 5022.45 BogoMIPS (lpj=10044915)
>      CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
>      CPU: L2 Cache: 512K (64 bytes/line)
>      CPU: Physical Processor ID: 0
>      CPU: Processor Core ID: 1
>      Intel machine check architecture supported.
>      Intel machine check reporting enabled on CPU#1.
>      CPU1: AMD Athlon(tm) Dual Core Processor 4850e stepping 02
>      CPU0 attaching NULL sched-domain.
>      Switched to high resolution mode on CPU 1
>      CPU0 attaching sched-domain:
>       domain 0: span 0-1 level CPU
>        groups: 0 1
>      CPU1 attaching sched-domain:
>       domain 0: span 0-1 level CPU
>        groups: 1 0
>      Warning: Processor Platform Limit event detected, but not handled.
>      Consider compiling CPUfreq support into your kernel.
> 
> 
> Kernel config, dmesg and lspci below.  Is there anyting I could
> try besides git bisect?

Perhaps.  Please check if the kernel where the following commit is the head:

commit 2ed8d2b3a81bdbb0418301628ccdb008ac9f40b7
Author: Rafael J. Wysocki <rjw@sisk.pl>
Date:   Mon Mar 16 22:34:06 2009 +0100

    PM: Rework handling of interrupts during suspend-resume

is also broken.

Best,
Rafael

  parent reply	other threads:[~2009-06-11 20:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 16:56 2.6.30: hibernation/swsusp stuck in disable_nonboot_cpus Johannes Stezenbach
2009-06-11 20:21 ` Rafael J. Wysocki
2009-06-11 20:21 ` Rafael J. Wysocki [this message]
2009-06-11 20:32 ` Pavel Machek
2009-06-12 14:42   ` Johannes Stezenbach
2009-06-12 15:22     ` Johannes Stezenbach

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=200906112221.57926.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=hpa@zytor.com \
    --cc=js@sig21.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mingo@redhat.com \
    --cc=pavel@ucw.cz \
    --cc=tglx@linutronix.de \
    /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.