All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Fabio Comolli <fabio.comolli@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jay Fenlason <fenlason@redhat.com>
Subject: Re: Regression in 2.6.28-rc and 2.6.27-stable - hibernate related
Date: Wed, 26 Nov 2008 02:03:02 +0100	[thread overview]
Message-ID: <492CA046.9010501@s5r6.in-berlin.de> (raw)
In-Reply-To: <200811260031.20079.rjw@sisk.pl>

Rafael J. Wysocki wrote:
>>>>> On Sun, Nov 23, 2008 at 7:24 PM, Fabio Comolli <fabio.comolli@gmail.com> wrote:
>>>>> The bisection pointed to:
>>>>>
>>>>> ------------------------------------------------------------------------------------------------------------------------------------------------
>>>>> fcomolli@hawking:~/software/GIT-TREES/linux-2.6.27.y> git bisect good
>>>>> ff0f8d16839cd02dc95bd92c212cbd5d433a4d2b is first bad commit
>>>>> commit ff0f8d16839cd02dc95bd92c212cbd5d433a4d2b
>>>>> Author: Jay Fenlason <fenlason@redhat.com>
>>>>> Date:   Mon Oct 27 23:28:14 2008 +0100
>>>>>
>>>>>     firewire: fix struct fw_node memory leak
>>>>>
>>>>>     commit 77e557191701afa55ae7320d42ad6458a2ad292e upstream

(I still have a suspicion that this commit, or firewire even, is not the
actual culprit.  But one never knows.)

> Also, on a possibly related note, I've just found a report from a Mac Mini user
> who told me his machine hanged during resume from hibernation if his external
> firewire drive was connected to the port.  He worked around the problem by
> switching to the new firewire stack that worked for him.

The above bisection result is about the new stack = drivers/firewire/.
The old stack is drivers/ieee1394/ and I prefix all its changes with
"ieee1394:".

Of course the old stack is supposed to hibernate + restore properly too.
I personally tested only suspend + resume though, and that's quite long
ago...
-- 
Stefan Richter
-=====-==--- =-== ==-=-
http://arcgraph.de/sr/

  reply	other threads:[~2008-11-26  1:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23 16:17 Regression in 2.6.28-rc and 2.6.27-stable - hibernate related Fabio Comolli
2008-11-23 18:14 ` Rafael J. Wysocki
2008-11-23 18:24   ` Fabio Comolli
2008-11-23 20:23     ` Fabio Comolli
2008-11-23 23:31       ` Rafael J. Wysocki
2008-11-24  7:18         ` Stefan Richter
2008-11-24  8:57           ` Fabio Comolli
2008-11-25 23:15           ` Rafael J. Wysocki
2008-11-25 23:31             ` Rafael J. Wysocki
2008-11-26  1:03               ` Stefan Richter [this message]
2008-11-26  8:19                 ` Fabio Comolli
2008-11-26 12:28                   ` Stefan Richter
2008-11-26 19:45                     ` Fabio Comolli
2008-11-26 20:07                       ` Stefan Richter
2008-11-26 23:02                         ` Rafael J. Wysocki
2008-11-27 15:17                           ` Fabio Comolli
2008-11-27 21:54                             ` Fabio Comolli
2008-12-05  0:24                               ` Rafael J. Wysocki
2008-12-12 18:58                               ` Pavel Machek
2008-12-12 19:01                                 ` Fabio Comolli

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=492CA046.9010501@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=fabio.comolli@gmail.com \
    --cc=fenlason@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.