From: "Georg C. F. Greve" <greve-mXXj517/zsQ@public.gmane.org>
To: ncunningham-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org
Cc: ACPI List
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
SoftwareSuspend-Devel
<softwaresuspend-devel-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org>
Subject: Re: [SoftwareSuspend-devel] status update for current development on ASUS M2N
Date: Thu, 30 Sep 2004 11:59:54 +0200 [thread overview]
Message-ID: <m3oejo84bp.fsf@brain.gnuhh.org> (raw)
In-Reply-To: <1096279213.4222.5.camel-AdgCB+f5QAxwBzq2CxEN2SkBHpOjBR89@public.gmane.org> (Nigel Cunningham's message of "Mon, 27 Sep 2004 20:11:41 +1000")
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
|| On Mon, 27 Sep 2004 20:11:41 +1000
|| Nigel Cunningham <ncunningham-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org> wrote:
nc> Could I get you to compile kdb in as well. If you then press the
nc> Sys Rq key when the CPU is being chewed, you should be able to
nc> use ps and btp <process number> to get an idea of what is going
nc> on.
I am now running kernel
[-- Attachment #2: patch-2.6.9-rc2-plus_5.txt --]
[-- Type: text/plain, Size: 551 bytes --]
Patches contained:
linux-2.6.8
patch-2.6.9-rc2
software-suspend-109-for-2.6.9-rc2 (without kdb)
build fix for swsusp 109 - see https://lists.berlios.de/pipermail/softwaresuspend-devel/2004-September/000555.html
2.6.9-rc2-mm4/bk-acpi.patch
acpi-compile-fix.patch
acpi-x86_64-build-fix.patch
bk-agpgart.patch
bk-alsa.patch
bk-cpufreq.patch
ipw2100-0.55
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 #3: Type: text/plain, Size: 803 bytes --]
and also created a version with kdb and heavy debugging.
This kernel shows the same behaviour and can suspend/resume so I can
get into kdb and do btp. Unfortunately I seem to be too stupid to find
the way to get the output somehow saved or written anywhere.
Not having the time (and motivation, to be honest) to write down all
the names and numbers -- and also not feeling that sending digital
photographs is the best way of communicating that output -- I don't
know how to give you that information.
Can you tell me how to do this, please?
Regards,
Georg
--
Georg C. F. Greve <greve-mXXj517/zsQ@public.gmane.org>
Free Software Foundation Europe (http://fsfeurope.org)
Brave GNU World (http://brave-gnu-world.org)
next prev parent reply other threads:[~2004-09-30 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 8:47 status update for current development on ASUS M2N Georg C. F. Greve
2004-09-27 10:11 ` 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 ` Georg C. F. Greve [this message]
2004-09-27 12:33 ` Karol Kozimor
2004-09-27 13:28 ` [ACPI] " Georg C. F. Greve
2004-09-27 13:29 ` Nigel Cunningham
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=m3oejo84bp.fsf@brain.gnuhh.org \
--to=greve-mxxj517/zsq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ncunningham-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org \
--cc=softwaresuspend-devel-0fE9KPoRgkgATYTw5x5z8w@public.gmane.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