From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
Cc: Andreas Steinmetz <ast@domdv.de>, Pavel Machek <pavel@suse.cz>,
Dave Jones <davej@codemonkey.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: amd64-agp vs. swsusp
Date: Wed, 20 Jul 2005 11:15:07 +0200 [thread overview]
Message-ID: <200507201115.08733.rjw@sisk.pl> (raw)
In-Reply-To: <42DD7011.6080201@stud.feec.vutbr.cz>
Hi,
On Tuesday, 19 of July 2005 23:26, Michal Schmidt wrote:
> Andreas Steinmetz wrote:
> > Michal Schmidt wrote:
> >>Does resuming from swsuspend work for anyone with amd64-agp loaded?
> >>
> >>On my system when I suspend with amd64-agp loaded, I get a spontaneous
> >>reboot on resume. It reboots immediately after reading the saved image
> >>from disk.
> >>This is 100% reproducible.
> >>
> >>Athlon 64 FX-53, Asus A8V Deluxe, Linux 2.6.13-rc3-mm1.
> >
> >
> > AMD Athlon(tm) 64 Processor 3000+, Acer Aspire
> >
> > Linux gringo 2.6.13-rc3-gringo #36 Sun Jul 17 15:57:17 CEST 2005 x86_64
> > unknown unknown GNU/Linux
> >
> > CONFIG_AGP=y
> > CONFIG_AGP_AMD64=y
> >
> > swsusp works for me. Could it be mm, agp as a module or some speciality
> ^^^^^^^^^^^^^^^
> That seems to be the problem!
> > of your hardware?
>
> I have rebuilt agpgart and amd64-agp into the kernel and now it has
> resumed successfully for the first time. Thank you for the hint!
>
> But I still wonder, why that makes a difference.
Before resume the module is not present. When it gets loaded from the
image it probably runs with the assumption that the hardware was initialized
which is not correct.
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
next prev parent reply other threads:[~2005-07-20 9:15 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 [this message]
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
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=200507201115.08733.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ast@domdv.de \
--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