From: Gleb Natapov <gleb@redhat.com>
To: gcosta@redhat.com
Cc: mingo@elte.hu, linux-next@vger.kernel.org
Subject: S3 sleep no longer works on x86_64 in 2.6.27
Date: Thu, 23 Oct 2008 14:24:05 +0200 [thread overview]
Message-ID: <20081023122405.GC14838@redhat.com> (raw)
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?
--
Gleb.
next reply other threads:[~2008-10-23 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 12:24 Gleb Natapov [this message]
2008-10-23 12:51 ` S3 sleep no longer works on x86_64 in 2.6.27 Ingo Molnar
2008-10-23 13:08 ` Gleb Natapov
2008-10-24 2:44 ` H. Peter Anvin
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=20081023122405.GC14838@redhat.com \
--to=gleb@redhat.com \
--cc=gcosta@redhat.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).