linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Pfeiffer <roto@gmx.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	"debian-powerpc@lists.debian.org"
	<debian-powerpc@lists.debian.org>
Subject: Re: 2.6.14 USB vs. sleep issues
Date: Wed, 16 Nov 2005 19:09:26 +0100	[thread overview]
Message-ID: <20051116180925.GB3080@localhost> (raw)
In-Reply-To: <1130999620.4680.28.camel@gaston>

On Thu, Nov 03, 2005 at 05:33:39PM +1100, Benjamin Herrenschmidt wrote:
> For those who experience crashes on sleep and/or wakeup (typically due
> to USB) with 2.6.14, I made a test patch that might help. [ ... ]

Ben, I just compiled and installed a 2.6.14.1 from kernel.org with
none of your patches from this thread applied to it, and I have no
sleep/wakeup probs with it so far: about 3 instances of sleep/wakeup
until now, all of them successful.

Maybe I even made it a bit more complicated for the system, as I
connected a USB HUB, with 4 ports, to the machine: It just seems to
work ...

-------------------------------------
$ cat /proc/cpuinfo 
processor       : 0
cpu             : 7455, altivec supported
clock           : 867MHz
revision        : 0.2 (pvr 8001 0302)
bogomips        : 865.18
machine         : PowerBook3,5
motherboard     : PowerBook3,5 MacRISC2 MacRISC Power Macintosh
detected as     : 80 (PowerBook Titanium IV)
pmac flags      : 0000001b
L2 cache        : 256K unified
memory          : 768MB
pmac-generation : NewWorld
-----------------------------------

HTH

Best Regards
Wolfgang

-- 
Wolfgang Pfeiffer
http://profiles.yahoo.com/wolfgangpfeiffer

Key ID: E3037113
Key fingerprint = A8CA 9D8C 54C4 4CC1 0B26  AA3C 9108 FB42 E303 7113

  parent reply	other threads:[~2005-11-16 18:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03  6:33 2.6.14 USB vs. sleep issues Benjamin Herrenschmidt
2005-11-03  9:03 ` Eddy Petrişor
2005-11-03 21:21   ` Benjamin Herrenschmidt
2005-11-04  7:13     ` Eddy Petrişor
2005-11-04  7:18       ` Benjamin Herrenschmidt
2005-11-04 19:32         ` Vivenzio Pagliari
2005-11-04 21:48           ` Benjamin Herrenschmidt
2005-11-05 21:58 ` Bin Zhang
2005-11-05 22:17   ` Benjamin Herrenschmidt
2005-11-06 10:54     ` Bin Zhang
2005-11-11 21:47     ` Eddy Petrisor
2005-11-11 21:52       ` Benjamin Herrenschmidt
2005-11-12  8:53         ` Eddy Petrisor
2005-11-12  9:45           ` Eddy Petrişor
2005-11-14  7:19         ` Arkadiusz Miskiewicz
2005-11-14  8:06           ` Benjamin Herrenschmidt
2005-11-23 21:55         ` Gaudenz Steinlin
2005-11-23 22:09           ` Benjamin Herrenschmidt
2005-11-07  9:13 ` Charles-Edouard Ruault
2005-11-07 14:54   ` Wolfram Quester
2005-11-07 21:00   ` Benjamin Herrenschmidt
2005-11-10  1:12     ` Eddy Petrişor
2005-11-10  1:51       ` Benjamin Herrenschmidt
2005-11-11  0:24 ` Wolfgang Pfeiffer
2005-11-16 18:09 ` Wolfgang Pfeiffer [this message]
2005-11-16 18:25   ` Wolfgang Pfeiffer
2005-11-16 21:01   ` Benjamin Herrenschmidt
2005-11-16 23:21     ` Eddy Petrisor

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=20051116180925.GB3080@localhost \
    --to=roto@gmx.net \
    --cc=benh@kernel.crashing.org \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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).