From: Christian Borntraeger <borntraeger@de.ibm.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Alan Stern <stern@rowland.harvard.edu>,
lkml <linux-kernel@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
linux-usb@vger.kernel.org
Subject: Re: Regression 2.6.28-git: suspend/resume failure. git bisected to usb suspend/resume patch
Date: Tue, 13 Jan 2009 09:07:13 +0100 [thread overview]
Message-ID: <200901130907.13820.borntraeger@de.ibm.com> (raw)
In-Reply-To: <200901121341.51674.rjw@sisk.pl>
Am Montag 12 Januar 2009 schrieb Rafael J. Wysocki:
> > Please try if suspend-resume works for you if you make commit
> > fa58d305d9925b01830e535896a7227a868a9e15
> > (PCI PM: Add suspend counterpart of pci_reenable_device) the head of your
> > tree ('git checkout -b test-branch
fa58d305d9925b01830e535896a7227a868a9e15').
> >
> > If it does, please check the same for commit
> > 571ff7584bb9e05fca0eb79752ae55a46faf3a98
> > (PCI PM: Power-manage devices without drivers during suspend-resume).
>
> Ah, please do the above with the USB commit
> a0d4922da2e4ccb0973095d8d29f36f6b1b5f703 reverted.
Will do.
In the meantime I have bisected another problem:
commit 7503bfbae89eba07b46441a5d1594647f6b8ab7d
Author: Mike Travis <travis@sgi.com>
Date: Sun Jan 4 05:18:09 2009 -0800
cpumask: use work_on_cpu in acpi-cpufreq.c for drv_read and drv_write
but I just see that this is already known.
O dear. How many patches do we know that broke S2R in this merge window? 4? 5?
Christian
next prev parent reply other threads:[~2009-01-13 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 12:48 Regression 2.6.28-git: suspend/resume failure. git bisected to usb suspend/resume patch Christian Borntraeger
2009-01-12 0:03 ` Rafael J. Wysocki
2009-01-12 12:41 ` Rafael J. Wysocki
2009-01-12 17:25 ` Rafael J. Wysocki
2009-01-13 4:44 ` Jeff Chua
2009-01-13 11:44 ` Rafael J. Wysocki
2009-01-13 8:07 ` Christian Borntraeger [this message]
2009-01-13 11:45 ` Rafael J. Wysocki
2009-01-13 11:46 ` Ingo Molnar
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=200901130907.13820.borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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