From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: Pavel Machek <pavel@ucw.cz>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10-mm2: swsusp problem with resuming on batteries (AMD64)
Date: Wed, 12 Jan 2005 00:34:01 +0100 [thread overview]
Message-ID: <200501120034.02238.rjw@sisk.pl> (raw)
In-Reply-To: <20050111221412.GC4378@ip68-4-98-123.oc.oc.cox.net>
On Tuesday, 11 of January 2005 23:14, Barry K. Nathan wrote:
> > > The box is an Athlon 64 laptop on NForce 3.
> >
> > Can you try without cpufreq support? If we attempt to do 2GHz on AC
> > power, machine may die ugly death.
>
> Athlon 64 probably means it's running an x86_64 kernel. Wasn't there
> another thread on lkml about -mm2 swsusp and x86_64?
Yes, there was.
> I wonder if it's the same problem (or a related one).
The other thread was about the hang caused by the timer driver on suspend
(which I'm still trying to understand, but it takes time ;-)).
That problem is rather not related to this one, because I'm currently using a
slightly modified kernel in which the function timer_resume() (that caused
the hang) is a noop.
Greets,
RJW
--
- 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-01-11 23:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 21:20 2.6.10-mm2: swsusp problem with resuming on batteries (AMD64) Rafael J. Wysocki
2005-01-11 21:26 ` Pavel Machek
2005-01-11 22:14 ` Barry K. Nathan
2005-01-11 23:34 ` Rafael J. Wysocki [this message]
2005-01-11 21:27 ` Pavel Machek
2005-01-11 21:33 ` Rafael J. Wysocki
2005-01-11 21:55 ` Pavel Machek
2005-01-12 17:24 ` Rafael J. Wysocki
2005-01-12 20:45 ` 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=200501120034.02238.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=barryn@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.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 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.