From: Andreas Steinmetz <ast@domdv.de>
To: Cal Peake <cp@absolutedigital.net>
Cc: Andrew Morton <akpm@osdl.org>,
Michal Schmidt <xschmi00@stud.feec.vutbr.cz>,
pavel@suse.cz, davej@codemonkey.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: amd64-agp vs. swsusp
Date: Fri, 05 Aug 2005 12:32:02 +0200 [thread overview]
Message-ID: <42F34022.9040201@domdv.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0508041741540.4557@lancer.cnet.absolutedigital.net>
Cal Peake wrote:
> On Thu, 4 Aug 2005, Andrew Morton wrote:
>
>
>>Michal Schmidt <xschmi00@stud.feec.vutbr.cz> wrote:
>>
>>>Does resuming from swsuspend work for anyone with amd64-agp loaded?
>>
>>It would seem not ;)
>
>
> Must have missed the OP. Yes I can resume fine from swsusp with amd64-agp.
>
> System is an Averatec 3270 (Mobile Sempron(K8)).
>
> Not that this helps at all other than confirming it is possible ;)
>
> -cp
>
AFAIK it works when agp is built into the kernel. You will get problems
when it is built as a module. In the module case you may want to try if
loading the module before resuming helps.
--
Andreas Steinmetz SPAMmers use robotrap@domdv.de
next prev parent reply other threads:[~2005-08-05 10:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 20:51 amd64-agp vs. swsusp Michal Schmidt
2005-07-19 21:03 ` Andreas Steinmetz
2005-07-19 21:26 ` Michal Schmidt
2005-07-20 9:15 ` Rafael J. Wysocki
2005-07-20 22:07 ` Michal Schmidt
2005-07-20 23:23 ` Rafael J. Wysocki
2005-07-21 1:25 ` Michal Schmidt
2005-07-21 9:41 ` Rafael J. Wysocki
2005-07-21 5:31 ` Pavel Machek
2005-07-21 10:43 ` Michal Schmidt
2005-07-21 15:20 ` Pavel Machek
2005-07-21 15:24 ` Michal Schmidt
2005-07-21 20:05 ` Rafael J. Wysocki
2005-08-04 21:25 ` Andrew Morton
2005-08-04 21:40 ` Pavel Machek
2005-08-07 22:17 ` Michal Schmidt
2005-08-04 21:54 ` Cal Peake
2005-08-05 10:32 ` Andreas Steinmetz [this message]
2005-08-05 22:38 ` Cal Peake
2005-08-06 10:40 ` Andreas Steinmetz
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=42F34022.9040201@domdv.de \
--to=ast@domdv.de \
--cc=akpm@osdl.org \
--cc=cp@absolutedigital.net \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=xschmi00@stud.feec.vutbr.cz \
/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