From: Len Brown <lenb@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>, Pavel Machek <pavel@ucw.cz>,
Len Brown <len.brown@intel.com>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
jbohac@suse.cz, kernel list <linux-kernel@vger.kernel.org>,
jikos@suse.cz, "Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@osdl.org>
Subject: Re: tsc breaks atkbd suspend
Date: Tue, 19 Feb 2008 19:17:36 -0500 [thread overview]
Message-ID: <200802191917.36641.lenb@kernel.org> (raw)
In-Reply-To: <alpine.LFD.1.00.0802191748110.7583@apollo.tec.linutronix.de>
On Tuesday 19 February 2008 11:51, Thomas Gleixner wrote:
> On Tue, 19 Feb 2008, Ingo Molnar wrote:
> > * Pavel Machek <pavel@ucw.cz> wrote:
> >
> > > TSC is used even on machines when CONFIG_X86_TSC is not set (X86_TSC
> > > means _require_ TSC), but it is not properly disabled when it is
> > > unusable, because acpi code understood the config switch as "may use
> > > TSC".
> > >
> > > This actually fixes suspend problems on my x60.
> >
> > ah! This makes tons of sense. I've applied your patch
please do not.
> > - but i guess it should go via the ACPI tree.
yes.
> Right. The breakage was introduced there when IA64 switched to
> GENERIC_TIME and the X86_TSC dependency was added.
so do we need a patch for 2.6.23.stable and 2.6.24.stable?
thanks,
-Len
next prev parent reply other threads:[~2008-02-20 0:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 13:38 tsc breaks atkbd suspend Pavel Machek
2008-02-18 14:26 ` Thomas Gleixner
2008-02-18 14:37 ` Pavel Machek
2008-02-18 15:12 ` Thomas Gleixner
2008-02-19 9:20 ` Pavel Machek
2008-02-19 9:37 ` Pavel Machek
2008-02-19 10:00 ` Pavel Machek
2008-02-19 14:05 ` Ingo Molnar
2008-02-19 16:51 ` Thomas Gleixner
2008-02-20 0:17 ` Len Brown [this message]
2008-02-20 6:51 ` Thomas Gleixner
2008-02-19 10:02 ` notsc is ignored on common configurations Pavel Machek
2008-02-19 11:26 ` Ingo Molnar
2008-02-19 11:29 ` Pavel Machek
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=200802191917.36641.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=akpm@osdl.org \
--cc=jbohac@suse.cz \
--cc=jikos@suse.cz \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox