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: LKML <linux-kernel@vger.kernel.org>,
	"Linux-pm mailing list" <linux-pm@lists.linux-foundation.org>,
	Maxim Levitsky <maximlevitsky@gmail.com>
Subject: Re: [Regression] firewire_ohci causes system resume to fail
Date: Sun, 5 Dec 2010 17:09:47 +0100	[thread overview]
Message-ID: <20101205170947.6b4e2d09@stein> (raw)
In-Reply-To: <20101205161758.2d75c65d@stein>

On Dec 05 Stefan Richter wrote:
> On Dec 05 Rafael J. Wysocki wrote:
> > There is a regression I can reproduce 100% of the time on a AMD-based desktop
> > box that resume from hibernation (or suspend) fails because of the firewire_ohci
> > module.  The box just hangs when firewire_ohci resume runs, apparently, and it
> > is sufficient to do:
> > 
> > # echo devices > /sys/power/pm_test
> > # echo disk > /sys/power/state
> > 
> > to reproduce the issue.
> 
> Do you have anything attached to the FireWire bus?  What controller do
> you have?

I just now tested the above on an Intel Mac mini, running
unmodified 2.6.37-rc4 x86-32, without and with a camera on the FireWire
port, and could not reproduce the problem.  I also got an AMD based PC
here with an array of different FireWire controllers which I shall make
available to the same test...
-- 
Stefan Richter
-=====-==-=- ==-- --=-=
http://arcgraph.de/sr/

  parent reply	other threads:[~2010-12-05 16:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-05 14:42 [Regression] firewire_ohci causes system resume to fail Rafael J. Wysocki
2010-12-05 15:17 ` Stefan Richter
2010-12-05 15:17   ` Stefan Richter
2010-12-05 16:09   ` Stefan Richter
2010-12-05 16:09   ` Stefan Richter [this message]
2010-12-16 23:47     ` Rafael J. Wysocki
2010-12-17 20:38       ` Stefan Richter
2010-12-17 20:38       ` Stefan Richter
2010-12-16 23:47     ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2010-12-05 14:42 Rafael J. Wysocki

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=20101205170947.6b4e2d09@stein \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=maximlevitsky@gmail.com \
    --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.