mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jan De Luyck <lkml@kcore.org>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	linux-kernel@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net
Subject: Re: ACPI S3 and ieee1394 don't get along
Date: Wed, 14 Sep 2005 22:54:32 +0200	[thread overview]
Message-ID: <20050914205432.GA3460@elf.ucw.cz> (raw)
In-Reply-To: <200509140708.12281.lkml@kcore.org>

Hi!

> > > after putting my laptop into S3 and reviving it at home, the firewire
> > > interface was unusable, no response when plugging in my external disk,
> > > loading sbp2 manually didn't trigger anything.
> >
> > [...]
> >
> > > I saw this thread:
> > > http://marc.theaimsgroup.com/?l=linux1394-user&m=111262313930798&w=2
> > > tho I'm not sure if it's relevant to this.
> >
> > IEEE 1394 power management (i.e. management of bus power consumption or
> > of other nodes' internal power states) is not related to ACPI suspend/
> > resume of the local controller AFAICS.
> 
> I thought so. It was the only thing even remotely relevant I found on the mailinglists tho.
> 
> > According to your log, the cause is to be looked for in ohci1394's
> > purely hardware related parts or perhaps even outside of the ieee1394
> > subsystem.
> 
> I've attached the lspci -vvx before and after suspending to S3. There are a lot of differences, 
> but I have no idea how to interprete them :/

pci_save_state/pci_restore_state missing somewhere?
									Pavel

-- 
if you have sharp zaurus hardware you don't need... you know my address

  reply	other threads:[~2005-09-14 20:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13  9:56 Jan De Luyck
2005-09-13 10:20 ` Pavel Machek
2005-09-14  0:20   ` Stefan Richter
2005-09-14  8:46     ` Pavel Machek
2005-09-14  0:17 ` Stefan Richter
2005-09-14  5:08   ` Jan De Luyck
2005-09-14 20:54     ` Pavel Machek [this message]
2005-09-15 14:21 Lukas Hejtmanek

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=20050914205432.GA3460@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=lkml@kcore.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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

all inboxes | Powered by JetHome®