All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>, stable@kernel.org
Cc: Gleb Natapov <gleb@redhat.com>,
	gcosta@redhat.com, linux-next@vger.kernel.org,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: S3 sleep no longer works on x86_64 in 2.6.27
Date: Thu, 23 Oct 2008 19:44:39 -0700	[thread overview]
Message-ID: <49013697.2040902@zytor.com> (raw)
In-Reply-To: <20081023125104.GA9506@elte.hu>

Ingo Molnar wrote:
> * Gleb Natapov <gleb@redhat.com> wrote:
> 
>> Hi,
>>
>> S3 sleep no longer works on x86_64 (at least in KVM, but it looks like 
>> this is the kernel bug). Kernel 2.6.26 works. I think that the commit 
>> that caused the problem is a939098af, but I can't be 100% sure since 
>> compilation is broken at this point.
>>
>> Triple fault happens during S3 resume. It happens in 
>> arch/x86/kernel/head_64.S during access to GDT after it was loaded on 
>> line 213 (lgdt early_gdt_descr(%rip)) early_gdt_descr points to 
>> per_cpu__gdt_page and this address contains valid GDT entries during a 
>> regular boot, but on S3 resume in contains garbage. It seems that 
>> per_cpu area is reallocated somewhere, but I don't understand this 
>> magic enough to fix it. Can somebody look at this and explain what 
>> happens?
> 
> could you check whether the (post-v2.6.27) upstream fix below does the 
> trick for you?
> 
> 	Ingo
> 
> From 3038edabf48f01421c621cb77a712b446d3a5d67 Mon Sep 17 00:00:00 2001
> From: Rafael J. Wysocki <rjw@sisk.pl>
> Date: Fri, 17 Oct 2008 01:26:27 +0200
> Subject: [PATCH] x86 ACPI: fix breakage of resume on 64-bit UP systems with SMP kernel
> 
> x86 ACPI: Fix breakage of resume on 64-bit UP systems with SMP kernel
> 

Is this patch scheduled for 2.6.27-stable?  If not, it sounds like it 
should be.

	-hpa

  parent reply	other threads:[~2008-10-24  2:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 12:24 S3 sleep no longer works on x86_64 in 2.6.27 Gleb Natapov
2008-10-23 12:51 ` Ingo Molnar
2008-10-23 13:08   ` Gleb Natapov
2008-10-24  2:44   ` H. Peter Anvin [this message]
2008-10-24  6:41     ` 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=49013697.2040902@zytor.com \
    --to=hpa@zytor.com \
    --cc=gcosta@redhat.com \
    --cc=gleb@redhat.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=stable@kernel.org \
    --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.