public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Georg C. F. Greve" <greve@gnu.org>
To: acpi-devel@lists.sourceforge.net
Cc: SoftwareSuspend-devel@lists.berlios.de
Subject: status update for current development on ASUS M2N
Date: Mon, 27 Sep 2004 10:47:23 +0200	[thread overview]
Message-ID: <m3lleww12c.fsf@brain.gnuhh.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 50 bytes --]

Hi all,

FYI:

My latest kernel, which looks like

[-- Attachment #1.2: Patch description for 2.6.9-rc2-plus_4 --]
[-- Type: text/plain, Size: 576 bytes --]

Patches contained:

linux-2.6.8
patch-2.6.9-rc2

software-suspend-108-for-2.6.9-rc2 (without kdb)
software-suspend-108-fixes (from http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/linux-2.6-software-suspend-fixes.patch?rev=1.3)

2.6.9-rc2-mm3/bk-acpi.patch
	./acpi-compile-fix.patch
	./acpi-x86_64-build-fix.patch
	./bk-agpgart.patch
	./bk-alsa.patch
	./bk-cpufreq.patch

ipw2100-0.54

arch/i386/kernel/i8259.c: 

  * changed device_initcall(i8259A_init_sysfs);
         to late_initcall(i8259A_init_sysfs);
    (needed for suspend to RAM)

Makefile:

  * added -plus version


[-- Attachment #1.3: Type: text/plain, Size: 1140 bytes --]



seems not so bad.

Both suspend to ram and suspend to disk via swsusp2 (108) appear to
work fine. I completed a few cycles without problems.

However: If I suspend to ram once and then suspend to disk, resume
From disk works fine, but about 20 seconds to 1 minute later, the
load suddenly jumps to 100% and stays there.

The kacpid process seems to run wild and eat all available time, it
looks like some kind of wild loop, but there is no output. I can
normally shut the machine down -- although it takes a while.

I've tried compiling ACPI as modules and unloading the modules as well
as restarting the acpid before/after suspend to disk. Upon reloading
the modules things hang with "thermal" -- but that seems arbitrary,
the effect still shows up even if no thermal is loaded.

Not sure this helps anyone improve things, still wanted to give you
the feedback, though.

Regards,
Georg

-- 
Georg C. F. Greve                                       <greve@gnu.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

             reply	other threads:[~2004-09-27  8:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-27  8:47 Georg C. F. Greve [this message]
2004-09-27 10:11 ` status update for current development on ASUS M2N Nigel Cunningham
2004-09-27 16:48   ` Georg C. F. Greve
     [not found]   ` <1096279213.4222.5.camel-AdgCB+f5QAxwBzq2CxEN2SkBHpOjBR89@public.gmane.org>
2004-09-30  9:59     ` [SoftwareSuspend-devel] " Georg C. F. Greve
2004-09-27 12:33 ` Karol Kozimor
2004-09-27 13:28   ` [ACPI] " Georg C. F. Greve
2004-09-27 13:29     ` Nigel Cunningham
  -- strict thread matches above, loose matches on Subject: below --
2004-09-30 21:48 Nigel Cunningham
2004-10-01 22:31 ` Georg C. F. Greve
2004-10-04 10:05   ` Georg C. F. Greve
2004-10-05 23:44   ` Nigel Cunningham
2004-10-06 10:22     ` Georg C. F. Greve

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=m3lleww12c.fsf@brain.gnuhh.org \
    --to=greve@gnu.org \
    --cc=SoftwareSuspend-devel@lists.berlios.de \
    --cc=acpi-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox