From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Matthias Bläsing" <matthias.blaesing@rwth-aachen.de>
Cc: Subodh Shrivastava <subodh.shrivastava@gmail.com>,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, bcollins@debian.org,
scjody@modernduck.com
Subject: Re: ieee1394 failed to work after S3 resume.
Date: Mon, 20 Feb 2006 22:18:23 +0100 [thread overview]
Message-ID: <43FA321F.50100@s5r6.in-berlin.de> (raw)
In-Reply-To: <1140454826.30310.6.camel@prometheus.glx>
Matthias Bläsing wrote:
>>Subodh Shrivastava wrote:
>>>Suspend to Ram works fine here with 2.6.16-rc3 kernel except ieee1394
>>>fails to resume properly.
...
> A workaround till then is the usage of a script (I use hibernate and
> have blacklisted ohci1394), that unloads ohci1394 prior to suspending
> and reloading the module after resume.
Note, -mm contains a patch which lets sbp2 raise ohci1394's use count
while it is logged in to a target.
http://www.kernel.org/git/?p=linux/kernel/git/scjody/ieee1394.git;a=commitdiff;h=d415a9a9685578058800f2677bfeb8090fc212a1
If you run -mm or once this patch is merged, you have to adapt your
script to either unload sbp2 before ohci1394, or you have to detach sbp2
via sysfs before attempting to unload ohci1394:
# echo 1 > /sys/bus/ieee1394/drivers/sbp2/${guid}-${ud}/ignore_driver
(for each device)
The corresponding sequence after reloading ohci1394 would be
# echo 0 > /sys/bus/ieee1394/devices/${guid}-${ud}/ignore_driver
(for each device)
# echo 1 > /sys/bus/ieee1394/rescan
(once)
--
Stefan Richter
-=====-=-==- --=- =-=--
http://arcgraph.de/sr/
prev parent reply other threads:[~2006-02-20 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-19 19:37 Subodh Shrivastava
2006-02-20 15:58 ` Stefan Richter
2006-02-20 17:00 ` Matthias Bläsing
2006-02-20 21:18 ` Stefan Richter [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=43FA321F.50100@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=matthias.blaesing@rwth-aachen.de \
--cc=scjody@modernduck.com \
--cc=subodh.shrivastava@gmail.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
Powered by JetHome