From: Zhang Rui <rui.zhang@intel.com>
To: Mattia Dongili <malattia@linux.it>
Cc: "linux-acpi@vger" <linux-acpi@vger.kernel.org>,
linux-pm@lists.linux-foundation.org,
David Brownell <dbrownell@users.sourceforge.net>,
Len Brown <lenb@kernel.org>, Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2.6.22-rc1-mm1] vaio laptop (SZ72B) immediately resumes after STR
Date: Tue, 19 Jun 2007 17:55:40 +0800 [thread overview]
Message-ID: <1182246940.5411.116.camel@localhost.localdomain> (raw)
In-Reply-To: <20070619093033.GA3507@inferi.kami.home>
On Tue, 2007-06-19 at 18:30 +0900, Mattia Dongili wrote:
> On Tue, Jun 19, 2007 at 04:57:55PM +0800, Zhang Rui wrote:
> > On Sun, 2007-05-20 at 15:14 +0900, Mattia Dongili wrote:
> > > On Sat, May 19, 2007 at 12:04:13AM -0700, Andrew Morton wrote:
> > > > On Sat, 19 May 2007 15:48:29 +0900 Mattia Dongili <malattia@linux.it> wrote:
> > > >
> > > > > On Fri, May 18, 2007 at 12:22:40AM -0700, Andrew Morton wrote:
> > > > > > On Fri, 18 May 2007 16:15:24 +0900 Mattia Dongili <malattia@linux.it> wrote:
> > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > After finally catching fw-{ohci,core} to be problematic during resume,
> > > > > > > I'm now experiencing an immediate resume after suspending.
> > > > > > >
> > > > > > > 2.6.21-rc7-mm* didn't even suspend, my last known suspend-and-resuming
> > > > > > > kernel was 2.6.21-rc5-mm3 (I know one other vaio SZ user could STR with
> > > > > > > 2.6.21-rc6-mm* after the cpuidle fixes).
> > > > > > >
> > > > > > > my .config is: http://oioio.altervista.org/linux/config-2.6.22-rc1-mm1-1
> > > > > > > and a str cycle with PM_DEBUG=y:
> > > > > > > http://oioio.altervista.org/linux/dmesg-SRT-immediately-resumes.txt
> > > > > ...
> > > > > > > Any idea where to start from? (bisecting is ok, but it'll take some
> > > > > > > time...)
> > > > > >
> > > > > > Bisecting isn't that bad ;) I'd pick git-acpi.patch as the starting point.
> > > > >
> > > > > ok, git-acpi.patch is not the bad boy :)
> > >
> > > but very very close:
> > > acpi-driver-model-flags-and-platform_enable_wake.patch
> > >
> > Hi, Mattia,
> >
> > I tested this patch on several platforms but can not reproduce the bug.
> > Could you please help me do a simple test please?
> >
> > Any kernel release later than 2.6.22-rc1 is ok. You don't need to apply
> > acpi-driver-model-flags-and-platform_enable_wake.patch.
> >
> > Try to enable the wakeup GPE for all the USB devices first.
> > e.g. "#echo USB1 >/proc/acpi/wakeup" will enable GPE for USB1.
> > USB1 S3 disabled pci:0000:00:1d.0
> > USB2 S3 disabled pci:0000:00:1d.1
> > USB3 S3 disabled pci:0000:00:1d.2
> > USB4 S3 disabled pci:0000:00:1d.3
> > USB7 S3 disabled pci:0000:00:1d.7
> >
> > Try STR and check if it resumes immediately after suspend.
> > I think the same problem will happen without this patch.
>
> ok, building right now.
> Anyway, I don't remember the details but ehci and uhci were already
> spotted as being part of the problem. See the rest of the thread
> starting here http://lkml.org/lkml/2007/5/20/223
>
Yes, I've noticed this.
The above test is just to confirm that
acpi-driver-model-flags-and-platform_enable_wake.patch is not the root
cause of the problem.
Buggy drivers may cause this problem, but I can not debug further as I
can not reproduce this bug here.
> Anyway I'm currently on 22-rc4-mm1 and having problems (=not even
> suspending) but lack the necessary time to investigate/bisect
That's ok.
It would be great if you can verify the problem still exists,
i.e. try STR with this patch applied. :)
thanks,
Rui
next prev parent reply other threads:[~2007-06-19 9:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 7:15 [2.6.22-rc1-mm1] vaio laptop (SZ72B) immediately resumes after STR Mattia Dongili
2007-05-18 7:22 ` Andrew Morton
2007-05-19 6:48 ` Mattia Dongili
2007-05-19 7:04 ` Andrew Morton
2007-05-19 15:11 ` 2.6.22-rc1 regression: tifm prevents suspending [was: Re: [2.6.22-rc1-mm1] vaio laptop (SZ72B) immediately resumes after STR] Mattia Dongili
2007-05-19 16:43 ` Mattia Dongili
2007-05-19 17:17 ` Michal Piotrowski
2007-05-19 18:29 ` Rafael J. Wysocki
2007-05-19 20:50 ` Michal Piotrowski
2007-05-20 6:14 ` [2.6.22-rc1-mm1] vaio laptop (SZ72B) immediately resumes after STR Mattia Dongili
2007-05-20 6:47 ` Andrew Morton
2007-05-20 6:59 ` Mattia Dongili
2007-05-20 18:38 ` David Brownell
2007-05-21 0:41 ` Mattia Dongili
2007-05-21 1:22 ` David Brownell
2007-05-21 2:05 ` Mattia Dongili
2007-06-19 8:57 ` Zhang Rui
2007-06-19 9:30 ` Mattia Dongili
2007-06-19 9:55 ` Zhang Rui [this message]
2007-06-19 11:26 ` Rafael J. Wysocki
2007-06-20 1:52 ` Zhang Rui
2007-06-20 21:39 ` Rafael J. Wysocki
2007-06-22 10:08 ` David Brownell
2007-06-22 14:33 ` [linux-pm] " Alan Stern
2007-06-19 10:09 ` Mattia Dongili
2007-06-19 14:20 ` Alan Stern
2007-06-20 14:45 ` [linux-pm] " Mattia Dongili
2007-06-20 16:33 ` Alan Stern
2007-06-21 6:42 ` Mattia Dongili
2007-06-21 7:28 ` Zhang Rui
2007-06-21 9:22 ` Mattia Dongili
2007-06-21 15:45 ` Alan Stern
2007-06-22 9:22 ` Mattia Dongili
2007-06-22 9:43 ` David Brownell
2007-06-22 14:07 ` Alan Stern
2007-06-22 10:02 ` David Brownell
2007-06-22 14:22 ` Alan Stern
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=1182246940.5411.116.camel@localhost.localdomain \
--to=rui.zhang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=greg@kroah.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=malattia@linux.it \
/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