linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Sebastian Heutling <sheutlin@gmx.de>
Cc: linuxppc-dev@ozlabs.org, debian-powerpc@lists.debian.org
Subject: Re: [Fwd: Re: iBook G3 owners]
Date: Tue, 05 Apr 2005 14:10:27 +0200	[thread overview]
Message-ID: <jeacodv2z0.fsf@sykes.suse.de> (raw)
In-Reply-To: <425266E2.7060605@gmx.de> (Sebastian Heutling's message of "Tue, 05 Apr 2005 12:22:26 +0200")

Sebastian Heutling <sheutlin@gmx.de> writes:

> Sleep/wakeup works with a modified arch/ppc/platform/pmac_sleep.S (bl 
> reloc_offset was missing which you send later). I still have a strange 
> problem with some programs started in init-Scripts. For example if I run 
> dbus on bootup and directly after that go to sleep and wake-up again my 
> ibook doesn't resume harddisks leaving the following last messages:
>
> eth0 resuming
> PHY ID: 4061e4, addr: 0
> eth0: Link is up at 100 Mbps, full duplex.
> eth0: Pause is disabled
>
> If I disable dbus (stop it) and go to sleep, wakeup - no problem. 

I have the same problem.  I'm also seeing the same hang when the KDED
Media Manager is running (independent of hal/dbus).  I believe the cause
for this is that the ide subsystem wakes up too late, and the cdrom
polling of hal or kded is resuming too early.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2005-04-05 12:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 10:22 [Fwd: Re: iBook G3 owners] Sebastian Heutling
2005-04-05 12:10 ` Andreas Schwab [this message]
2005-04-05 23:50   ` Benjamin Herrenschmidt

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=jeacodv2z0.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sheutlin@gmx.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;
as well as URLs for NNTP newsgroup(s).