linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Quester <wolfi@mittelerde.physik.uni-konstanz.de>
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: ppc32: Rework power management take #3
Date: Fri, 3 Jun 2005 11:33:18 +0200	[thread overview]
Message-ID: <20050603093316.GA4777@halley.zuhause> (raw)
In-Reply-To: <1117750504.31082.76.camel@gaston>

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

On Fri, Jun 03, 2005 at 08:15:03AM +1000, Benjamin Herrenschmidt wrote:
> 
> > Today I applied the two mentioned patches to rc5-git6. There were quite
> > a lot of offsets and one time fuzz 2 (hunk 10 in via-pm.c). But still I
> > get a freeze on my PowerBook6,2 (12", 1Ghz from Dec. 2004) when I
> > suspend to disk from X. If I suspend from tty1 the first time, the
> > following suspends work well even from X.
> > 
> > Thanks for your work,
> 
> Bizarre... The kernel is normally first opens a new tty and switches to
> it before suspend. It seems that this opening of a new tty is
> conflicting in some way with X "nv" driver and causing that freeze. Are
> you also using an fbdev like rivafb or nvidiafb or are you defaulting to
> offb ? If you do, Can you try booting with video=ofonly and tell me if
> it helps ?
> 
> Ben.
Normally I use rivafb, but I tried video=ofonly and did not get a
freeze. I tried it three times and I hope that this is good statistics.
With 2.6.12-rc2 and riva fb I got the freeze in about 80% of all initial
suspends, with rc{4,5-git6} and riva fb I had it everytime. But it may
still well be that there is a random component since I learned to
workaround the problem by switching to tty1 and thus don't trigger the
freeze condition that often.


Thanks,

Wolfi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-06-03  9:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-30  3:35 [PATCH] ppc32: Rework power management take #3 Benjamin Herrenschmidt
2005-05-30 21:59 ` Mickael Royer
2005-06-02 13:05   ` Wolfram Quester
2005-06-02 22:15     ` Benjamin Herrenschmidt
2005-06-03  9:33       ` Wolfram Quester [this message]
2005-06-03 22:43         ` Benjamin Herrenschmidt
2005-06-06  9:34           ` Wolfram Quester
2005-06-06 11:38             ` Benjamin Herrenschmidt
2005-06-02 22:33 ` [PATCH] " Geoff Levand
2005-06-02 23:06   ` Benjamin Herrenschmidt
2005-06-02 23:23     ` Geoff Levand

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=20050603093316.GA4777@halley.zuhause \
    --to=wolfi@mittelerde.physik.uni-konstanz.de \
    --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).