From: Pavel Machek <pavel@ucw.cz>
To: John Mock <kd6pag@qsl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: swsusp in test8 fails with intel-agp and i830
Date: Mon, 20 Oct 2003 14:20:12 +0200 [thread overview]
Message-ID: <20031020122011.GR1659@openzaurus.ucw.cz> (raw)
In-Reply-To: <E1ABV7L-0001Os-00@penngrove.fdns.net>
Hi!
> Pavel - I looked in intel_agp and placed printk+mdelay all over
> agp_intel_resume(struct pci_dev *pdev), but something strange happened: I saw
> those print outs during _suspend_ and not during resume - does that make any
> sense?
They should be called both during suspend and during
resume. If they are not called during resume... Trace that
it looks like problem.
> I wasn't able to find anything that looked like suspend/resume support in
> 'drivers/char/drm/*', and i'm starting to wonder if DRI in general has any
> chance of working with software suspend. After all, i think the X server
> reaches in and hacks the hardware, so i don't understand how the DRM code
> can manage to restore that state after being powered down, 'cause i don't
Well, X should only hit hw when it owns the console,
that's why -test8 swsusp is doing console switch.
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
next prev parent reply other threads:[~2003-10-23 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 8:10 swsusp in test8 fails with intel-agp and i830 John Mock
2003-10-20 12:20 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-18 22:18 John Mock
2003-10-18 23:06 ` Aviram Jenik
2003-10-15 21:47 Suspend to disk very unstable Aviram Jenik
2003-10-16 20:21 ` Pavel Machek
2003-10-18 15:17 ` swsusp in test8 fails with intel-agp and i830 Aviram Jenik
2003-10-18 18:05 ` Pavel Machek
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=20031020122011.GR1659@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=kd6pag@qsl.net \
--cc=linux-kernel@vger.kernel.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).