public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: "Carlos R. Mafra" <crmafra2@gmail.com>,
	linux-kernel@vger.kernel.org, tomas.winkler@intel.com,
	kernel@nn7.de
Subject: Re: Suspend to RAM regression in 2.6.28-rc2 (bisected)
Date: Mon, 27 Oct 2008 14:06:56 -0700	[thread overview]
Message-ID: <1225141616.5396.15.camel@brick> (raw)
In-Reply-To: <200810272159.52947.borntraeger@de.ibm.com>

On Mon, 2008-10-27 at 21:59 +0100, Christian Borntraeger wrote:
> Am Montag, 27. Oktober 2008 schrieb Carlos R. Mafra:
> > Hi,
> > 
> > So I managed to bisect my suspend to RAM regression in 2.6.27-rc2
> > to commit 3b7ee69d0caefbdb85a606a98bff841b8c63b97e ("mac80211: disassociate 
> > when moving to new BSS") by Tomas Winkler (Cc:-ed).
> 
> I was also bisecting a suspend to RAM regression in 2.6.28-rc1 but I had to 
> stop the bisect due to another problem in that bisection. I can confirm that 
> this patch was among the ~50 patches left to test.

This also looks like a regression I've been looking at, 
but suspend-to-disk, and b43 driver.  On resume, nothing but a blackscreen and
unresponsive.

I'll try reverting that one patch and see if it fixes it.

Harvey


      reply	other threads:[~2008-10-27 21:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-27 16:20 Suspend to RAM regression in 2.6.28-rc2 (bisected) Carlos R. Mafra
2008-10-27 17:32 ` Rafael J. Wysocki
2008-10-27 18:07   ` Soeren Sonnenburg
2008-10-27 18:31     ` Johannes Berg
2008-10-27 18:44       ` Johannes Berg
2008-10-27 19:00         ` Carlos R. Mafra
2008-10-27 19:03           ` Johannes Berg
2008-10-27 19:11             ` Carlos R. Mafra
2008-10-27 19:13               ` Johannes Berg
2008-10-27 20:39                 ` Carlos R. Mafra
2008-10-27 20:51                   ` Rafael J. Wysocki
2008-10-27 20:52                     ` Carlos R. Mafra
2008-10-27 21:07                       ` Rafael J. Wysocki
2008-10-27 22:05                         ` Carlos R. Mafra
2008-10-27 21:07                     ` Tomas Winkler
2008-10-27 22:28                       ` Carlos R. Mafra
2008-10-27 22:40                         ` Tomas Winkler
2008-10-27 22:50                           ` Rafael J. Wysocki
2008-10-27 23:12                             ` Tomas Winkler
2008-10-27 23:23                               ` Harvey Harrison
2008-10-28 15:30                               ` Rafael J. Wysocki
2008-10-28 16:12                                 ` Tomas Winkler
2008-10-28  6:32                       ` Christian Borntraeger
2008-10-27 19:06           ` Jens Axboe
2008-10-27 19:09             ` Johannes Berg
2008-10-27 19:13               ` Jens Axboe
2008-10-27 19:16                 ` Johannes Berg
2008-10-27 19:20                   ` Jens Axboe
2008-10-27 17:39 ` Rafael J. Wysocki
2008-10-27 17:57   ` Carlos R. Mafra
2008-10-27 18:00     ` John W. Linville
2008-10-27 18:16     ` Rafael J. Wysocki
2008-10-27 18:36       ` Carlos R. Mafra
2008-10-27 18:51         ` Carlos R. Mafra
2008-10-27 20:59 ` Christian Borntraeger
2008-10-27 21:06   ` Harvey Harrison [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=1225141616.5396.15.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=borntraeger@de.ibm.com \
    --cc=crmafra2@gmail.com \
    --cc=kernel@nn7.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomas.winkler@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