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: Mon, 6 Jun 2005 11:34:11 +0200 [thread overview]
Message-ID: <20050606093411.GB3478@halley.zuhause> (raw)
In-Reply-To: <1117838638.31082.173.camel@gaston>
[-- Attachment #1: Type: text/plain, Size: 1589 bytes --]
Hi Ben,
On Sat, Jun 04, 2005 at 08:43:57AM +1000, Benjamin Herrenschmidt wrote:
>
> > 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.
>
> Ok, what happens if you run rivafb, ssh into the box, and open a new tty
> (that is leave the box on X, but do something like echo "toto"
> >/dev/tty8) to create a new tty in the background.
>
> Does that trigger the freeze ?
>
> Ben.
OK, I tried that in some variations. If I do as you suggest, nothing
happens, I can login and use X as normal. But as soon as I try to switch
to tty1, the machine freezes. Without this ssh-stuff I can switch to
tty1 and back and be happy.
Then I rebooted, ssh'd into the box and added the line
8:23:respawn:/sbin/getty 38400 tty8
to open getty on tty8. I did telinit q to reload the init config and got
the same thing as described above. After a reboot and leaving the line
intact I could switch to tty8 and be happy.
Again, I ssh'd into the box and opened tty9 via echo... which lead to
the behaviour already described.
This looks to me as if it fails to switch to a tty which was not
allocated before.
Thanks for looking into this,
Wolfi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-06 9:34 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
2005-06-03 22:43 ` Benjamin Herrenschmidt
2005-06-06 9:34 ` Wolfram Quester [this message]
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=20050606093411.GB3478@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).