From: Oliver Neukum <oliver@neukum.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
rui.zhang@intel.com, shaohua.li@intel.com, yakui.zhao@intel.com,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, linux-usb@vger.kernel.org,
linux-acpi@vger.kernel.org, daniel.smoczyk@gmail.com,
imrehg@gmail.com
Subject: Re: [Bugme-new] [Bug 13145] New: Processor does not go below C2 if mouse (uhci) is plugged in.
Date: Wed, 22 Apr 2009 10:48:30 +0200 [thread overview]
Message-ID: <200904221048.35180.oliver@neukum.org> (raw)
In-Reply-To: <20090421164910.43d94457@infradead.org>
Am Mittwoch 22 April 2009 01:49:10 schrieb Arjan van de Ven:
> On Wed, 22 Apr 2009 00:22:14 +0200
>
> Oliver Neukum <oliver@neukum.org> wrote:
> > Am Dienstag 21 April 2009 23:27:51 schrieb Andrew Morton:
> > > (switched to email. Please respond via emailed reply-to-all, not
> > > via the bugzilla web interface).
> > >
> > > It looks like we need to revisit this - 2.6.26 worked OK, so why
> > > can't 2.6.28?
> >
> > Not going into C3 without autosuspend is really expected.
>
> this is not correct; if the CPU supports "C2-popup", going to C3 is
> expected.
Yes, that's possible. Does the system in question?
Regards
Oliver
next prev parent reply other threads:[~2009-04-22 8:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13145-10286@http.bugzilla.kernel.org/>
[not found] ` <bug-13145-10286-V0hAGp6uBxO456/isadD/XN4h3HLQggn@public.gmane.org/>
2009-04-21 21:27 ` [Bugme-new] [Bug 13145] New: Processor does not go below C2 if mouse (uhci) is plugged in Andrew Morton
2009-04-21 21:40 ` Arjan van de Ven
2009-04-21 22:22 ` Oliver Neukum
2009-04-21 23:49 ` Arjan van de Ven
2009-04-22 8:48 ` Oliver Neukum [this message]
[not found] ` <200904221048.35180.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2009-04-22 9:12 ` Shaohua Li
[not found] ` <20090422091247.GA28309-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2009-04-22 18:35 ` Len Brown
[not found] ` <20090421142751.b030cba7.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2009-04-22 14:51 ` Alan Stern
2009-04-22 15:09 ` Daniel Smoczyk
[not found] ` <d7131a800904220809ha96c0e5rd366abfcbae4d1c2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-22 16:39 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.0904221050110.3405-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2009-04-22 17:36 ` Oliver Neukum
[not found] ` <200904221936.38942.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2009-04-22 22:54 ` Len Brown
[not found] ` <alpine.LFD.2.00.0904221848380.21119-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-04-22 23:53 ` [RFC PATCH] ACPI: delete obsolete "bus master activity" proc field Len Brown
2009-04-23 0:40 ` [Bugme-new] [Bug 13145] New: Processor does not go below C2 if mouse (uhci) is plugged in Len Brown
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=200904221048.35180.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=daniel.smoczyk@gmail.com \
--cc=imrehg@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=shaohua.li@intel.com \
--cc=yakui.zhao@intel.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;
as well as URLs for NNTP newsgroup(s).