From: Wolfram Quester <wolfi@mittelerde.physik.uni-konstanz.de>
To: Charles-Edouard Ruault <ce@idtect.com>
Cc: "debian-powerpc@lists.debian.org"
<debian-powerpc@lists.debian.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: 2.6.14 USB vs. sleep issues
Date: Mon, 7 Nov 2005 15:54:33 +0100 [thread overview]
Message-ID: <20051107145433.GA15372@halley.zuhause> (raw)
In-Reply-To: <436F1A9E.80105@idtect.com>
[-- Attachment #1: Type: text/plain, Size: 1818 bytes --]
Hi Charles-Edouard,
On Mon, Nov 07, 2005 at 10:13:02AM +0100, Charles-Edouard Ruault wrote:
[...snip...]
> 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.
In a recent email to this list, Benjamin Herrenschmidt wrote:
> > >
> > > I would say your first mistake is to use PREEMPT :) There are
> > > various
> > > issues with PREEMPT on ppc32 that have not really been addressed so
> > > far,
> > > and the USB code has some "holes" that I wouldn't trust in a PREEMPT
> > > environment.
> > >
> >
> > What do you mean exactly? Should CONFIG_PREEMPT not be used?
> > And what about CONFIG_PREEMPT_VOLUNTARY?
>
> I would avoid both for now.
>
> Ben.
If I interpret your version string correctly, you also havre preemption
enabled. Please try without and report back success and/or problems.
With best regards,
Wolfi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-07 15:15 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 [this message]
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=20051107145433.GA15372@halley.zuhause \
--to=wolfi@mittelerde.physik.uni-konstanz.de \
--cc=ce@idtect.com \
--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).