All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles-Edouard Ruault <ce@idtect.com>
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: Mon, 07 Nov 2005 10:13:02 +0100	[thread overview]
Message-ID: <436F1A9E.80105@idtect.com> (raw)
In-Reply-To: <1130999620.4680.28.camel@gaston>

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. Please let me
>know if it makes things more reliable.
>
>http://gate.crashing.org/~benh/fix-ohci-sleep.diff
>
>Note that the patch is totally untested here so it may be just plain
>bogus :)
>
>Ben.
>
>
>
>  
>
Hi Ben,
i've applied your patch and it seems that when i put my powerbook to
sleep ( by closing the lid ) the kernel just crashes since everytime i
come back, the machine is turned off. I had a look at the logs and i see
that i'm having a reboot almost immediateley after the lid is closed.
However i've got no trace of a kernel panic .....
my conf:

Linux kaluha 2.6.14 #1 PREEMPT Mon Oct 31 10:28:22 CET 2005 ppc GNU/Linux
processor       : 0
cpu             : 7447/7457, altivec supported
clock           : 612MHz
revision        : 0.1 (pvr 8002 0101)
bogomips        : 406.52
machine         : PowerBook5,2
motherboard     : PowerBook5,2 MacRISC3 Power Macintosh
detected as     : 287 (PowerBook G4 15")
pmac flags      : 0000001b
L2 cache        : 512K unified
memory          : 768MB
pmac-generation : NewWorld

I have a usb mouse that i unplug before closing the lid.
Anything else that can be usefull ?
Thanks for your time.
Regards.


-- 
Charles-Edouard Ruault

+33 1 55 34 76 65
ce@idtect.com

Idtect SA
37 Bd des Capucines 
75002 Paris, France
www.idtect.com

  parent reply	other threads:[~2005-11-07  9:37 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 [this message]
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
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=436F1A9E.80105@idtect.com \
    --to=ce@idtect.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.