From: Thomas Gleixner <tglx@linutronix.de>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: Len Brown <lenb@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Arjan van de Ven <arjan@infradead.org>,
Venkatesh Pallipadi <venki@google.com>
Subject: Re: Performance/resume issues on Toshiba NB305
Date: Tue, 1 Mar 2011 21:22:46 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1103012117010.2701@localhost6.localdomain6> (raw)
In-Reply-To: <20110301200446.GA2235@thinkpad-t410>
On Tue, 1 Mar 2011, Seth Forshee wrote:
> On Fri, Feb 25, 2011 at 10:47:16PM +0100, Thomas Gleixner wrote:
> > On Fri, 25 Feb 2011, Seth Forshee wrote:
> > > On Fri, Feb 25, 2011 at 09:37:39PM +0100, Thomas Gleixner wrote:
> > > > On Fri, 25 Feb 2011, Seth Forshee wrote:
> > > > That seems to be related to low power states. When the machine goes
> > > > idle we switch into lower power states and that requires to use the
> > > > hpet instead of the local apic timer as that one stops.
> > > >
> > > > You could verify that theory by booting with processor.max_cstate=1
> > >
> > > This fixes the performance in combination with intel_idle.max_cstate=0.
> > > Alternately, intel_idle.max_cstate=1 works. But the resume still hangs.
> >
> > That was expected :)
> >
> > > Is the answer to quirk the machine to avoid deep C-states, or is there
> > > some better way I can fix this?
> >
> > Let's wait for the intel and acpi folks. It would be interesting what
> > the new intel toy says to your BIOS.
>
> Since the discussion on this issue died without really getting anywhere,
> I went ahead and threw together the patch below to disable anything
> deeper than C1 for this machine. I hope a better solution can be found,
> but if not would something like this be an acceptable workaround?
>
> As for the hangs during resume, unless someone has a better suggestion I
> guess I'll start looking into forcing the HPET to remain in periodic
> mode throughout suspend.
The problem with such DMI quirks is that it's hard to get rid of them
when a fixed BIOS version comes out while simply adding nohpet to the
kernel command line, is a non permanent, but sensible workaround.
Thanks,
tglx
prev parent reply other threads:[~2011-03-01 20:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 16:42 Seth Forshee
2011-02-25 20:17 ` Steven Rostedt
2011-02-25 20:27 ` Seth Forshee
2011-02-25 22:11 ` Thomas Gleixner
2011-02-25 22:33 ` Seth Forshee
2011-02-25 20:37 ` Thomas Gleixner
2011-02-25 21:21 ` Seth Forshee
2011-02-25 21:47 ` Thomas Gleixner
2011-02-25 22:29 ` Seth Forshee
2011-02-25 22:40 ` Thomas Gleixner
2011-02-26 5:58 ` Burt Triplett
2011-02-26 15:00 ` Seth Forshee
2011-02-27 20:17 ` Burt Triplett
2011-02-28 15:10 ` Seth Forshee
2011-03-05 5:55 ` Burt Triplett
2011-02-26 8:49 ` [tip:timers/urgent] clockevents: Prevent oneshot mode when broadcast device is periodic tip-bot for Thomas Gleixner
2011-03-01 20:04 ` Performance/resume issues on Toshiba NB305 Seth Forshee
2011-03-01 20:22 ` Thomas Gleixner [this message]
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=alpine.LFD.2.00.1103012117010.2701@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seth.forshee@canonical.com \
--cc=venki@google.com \
/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
all inboxes | Powered by JetHome®