public inbox for linux-kernel@vger.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 16:17:58 +0100	[thread overview]
Message-ID: <20101205161758.2d75c65d@stein> (raw)
In-Reply-To: <201012051542.31826.rjw@sisk.pl>

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?

> It definitely works with 2.6.34, but it fails with 2.6.37-rc4+ (latest mainline).
> I haven't tested the kernels in between, but I'm going to do that later today
> or some time next week.
> 
> If you have any idea about what may be the reason, please let me know.

As first quick thought:  While we of course need to have a look at
firewire-ohci changes, it could also be a higher-level issue in
firewire-core.  E.g. something with the 2.6.36 workqueue related core
kernel changes.  (I am only saying so because I noticed some module
unloading issues with the firewire stack lately that seem workqueue
related.)

I admit that PM suspend/resume or hibernate/restore are not part of my
personal firewire driver testing regime.  I need to address that.

I Cc'd Maxim Levitsky who has working firewire suspend/resume on
2.6.37-rc, although with some minor firewire-net related and
isochronous I/O related nits for which he sent fixes lately:
http://marc.info/?l=linux1394-devel&m=129099665721794
http://marc.info/?l=linux1394-devel&m=129099666021798
But I do not think that these could matter to your hang-at-resume issue.
-- 
Stefan Richter
-=====-==-=- ==-- --=-=
http://arcgraph.de/sr/

  reply	other threads:[~2010-12-05 15:18 UTC|newest]

Thread overview: 5+ 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 [this message]
2010-12-05 16:09   ` Stefan Richter
2010-12-16 23:47     ` Rafael J. Wysocki
2010-12-17 20:38       ` Stefan Richter

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=20101205161758.2d75c65d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox