From: mutex@kerneli.org
To: Michel D?nzer <michel@daenzer.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: new ATI sleep code freezes
Date: Wed, 23 Jul 2003 20:24:29 -0700 [thread overview]
Message-ID: <20030724032429.GC1987@heliosphan.linuxsymposium.org> (raw)
In-Reply-To: <1055016895.17021.74.camel@thor.holligenstrasse29.lan>
> The permissions don't cause the crash directly, it's the fact that
> the X server has no way of dealing with the sleep without using
> /dev/apm_bios.
I was able to re-create this crash the other day entirely reproduceably.
If I unplug my USB apple mouse while the computer is in between sleeping
and running normally the crash condition i described occurs, namely:
> Usually, when the sleep operation completes, there is a quick
> screen power blank. Then about another 1.5 seconds of the LCD being
> illuminated, with what looks like some random part of video memory
> being displayed, then finally the machine goes to sleep. Occasionally
> I am seeing a freeze during the step where the machine stays on for
> 1.5 seconds and has not quite been put to sleep.
Maybe there's a deadlock somewhere in the USB layer sleep code ? I
haven't tried this with other USB devices, but I plan on doing that as
so on as I get back from OLS.
Regards,
Dave
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-24 3:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 21:16 new ATI sleep code freezes Mich Lanners
2003-06-07 19:28 ` mutex
2003-06-07 20:14 ` Michel Dänzer
2003-07-24 3:24 ` mutex [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-29 15:41 mutex
2003-06-01 19:36 ` Michel Dänzer
2003-06-04 16:28 ` mutex
2003-06-04 17:15 ` Benjamin Herrenschmidt
2003-06-05 16:35 ` mutex
2003-06-05 16:47 ` Benjamin Herrenschmidt
2003-06-05 20:20 ` Michel Dänzer
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=20030724032429.GC1987@heliosphan.linuxsymposium.org \
--to=mutex@kerneli.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michel@daenzer.net \
/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.