All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Steinmetz <ast@domdv.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@suse.cz>,
	Eric Sandall <eric@sandall.us>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Suspend to ram with 2.6 kernels
Date: Tue, 12 Sep 2006 13:05:56 +0200	[thread overview]
Message-ID: <45069494.8070904@domdv.de> (raw)
In-Reply-To: <20060911235920.GA24597@srcf.ucam.org>

Matthew Garrett wrote:
> On Tue, Sep 12, 2006 at 12:28:20AM +0200, Andreas Steinmetz wrote:
> 
> 
>>Nope,
>>but the hint from this thread was good: s2ram works with
>>"acpi_skip_timer_override" and probably "enable_timer_pin_1" (I have to
>>try without this one, yet). Radeon, however, remains as a problem.
> 
> 
> Can you test with the following patch (without 
> acpi_skip_timer_override)?
> 

Yes, the patch fixes s2ram without acpi_skip_timer_override for me (x86_64).

There is, however, one difference during boot that may be a hint:
When booting without acpi_skip_timer_override the following message appears:

MP-BIOS bug: 8254 timer not connected to IO-APIC

As a sidenote booting without enable_timer_pin_1 doesn't make any
difference as expected.
-- 
Andreas Steinmetz                       SPAMmers use robotrap@domdv.de

  reply	other threads:[~2006-09-12 11:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07  2:35 Suspend to ram with 2.6 kernels Eric Sandall
2006-09-07 19:33 ` Pavel Machek
2006-09-08 22:24   ` Eric Sandall
2006-09-09 19:16     ` Pavel Machek
2006-09-11 10:13   ` Andreas Steinmetz
2006-09-11 20:27     ` Rafael J. Wysocki
2006-09-11 22:28       ` Andreas Steinmetz
2006-09-11 23:59         ` Matthew Garrett
2006-09-12 11:05           ` Andreas Steinmetz [this message]
2006-09-12 12:46             ` Matthew Garrett

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=45069494.8070904@domdv.de \
    --to=ast@domdv.de \
    --cc=eric@sandall.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=pavel@suse.cz \
    --cc=rjw@sisk.pl \
    /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.