From: "Georg C. F. Greve" <greve-mXXj517/zsQ@public.gmane.org>
To: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: acpi-20040715: functional regression on ASUS M2N
Date: Tue, 27 Jul 2004 15:40:56 +0200 [thread overview]
Message-ID: <m3k6wpmutz.fsf@reason.gnu-hamburg> (raw)
In-Reply-To: <1090927462.4412.26.camel-myFlNLNQP+Q@public.gmane.org> (Matthew Garrett's message of "Tue, 27 Jul 2004 12:24:22 +0100")
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
|| On Tue, 27 Jul 2004 12:24:22 +0100
|| Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org> wrote:
>> Which narrows the problem down to patch (b) as the one breaking
>> suspend to ram on ASUS M2N. Hope this helps tracking things down.
mg> Can you try doing the following:
mg> 1) Open arch/i386/kernel/time.c
mg> 2) Find sysdev_class pit_sysclass
mg> 3) Change
mg> .resume = time_resume,
mg> to
mg> // .resume = time_resume,
mg> 4) Rebuild the kernel
Tried it. No effect.
Did not change anything as far as I could tell. Problem persists.
mg> You'll need to change your resume script to do a hwclock
mg> --hwtosys once the system comes back up.
I've actually always had that. :)
mg> If this works then it's the same problem that
mg> I have - I have no idea what's causing it.
It seems to be a different problem, then.
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)
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2004-07-27 13:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 23:31 acpi-20040715: functional regression on ASUS M2N Georg C. F. Greve
[not found] ` <m3d62rzi9a.fsf-eMhNhoSsuh6q92djB/mqZw@public.gmane.org>
2004-07-20 19:03 ` Matthew Garrett
[not found] ` <1090350197.4828.5.camel-myFlNLNQP+Q@public.gmane.org>
2004-07-21 8:17 ` Georg C. F. Greve
[not found] ` <m3acxthizw.fsf-eMhNhoSsuh6q92djB/mqZw@public.gmane.org>
2004-07-27 11:14 ` Georg C. F. Greve
[not found] ` <m3oem1u2gg.fsf-glUV91rXKAHWIjgkaejU9x2eb7JE58TQ@public.gmane.org>
2004-07-27 11:24 ` Matthew Garrett
[not found] ` <1090927462.4412.26.camel-myFlNLNQP+Q@public.gmane.org>
2004-07-27 13:40 ` Georg C. F. Greve [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-27 12:24 Li, Shaohua
[not found] ` <B44D37711ED29844BEA67908EAF36F036BCD7C-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-07-27 13:42 ` Georg C. F. Greve
2004-08-02 16:45 Nathan Bryant
[not found] ` <410E6F9C.2040904-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-04 0:23 ` Georg C. F. Greve
2004-08-05 18:49 Nathan Bryant
[not found] ` <4112814C.2070808-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-06 11:21 ` Georg C. F. Greve
[not found] ` <m37jsc3424.fsf-glUV91rXKAHWIjgkaejU9x2eb7JE58TQ@public.gmane.org>
2004-08-06 13:36 ` Nathan Bryant
[not found] ` <41138944.3060309-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-06 16:54 ` Georg C. F. Greve
[not found] ` <m3u0vgurzy.fsf-glUV91rXKAHWIjgkaejU9x2eb7JE58TQ@public.gmane.org>
2004-08-06 17:07 ` Nathan Bryant
[not found] ` <4113BAD5.1030909-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-06 20:50 ` Georg C. F. Greve
2004-08-31 8:15 ` Georg C. F. Greve
2004-08-06 15:23 ` Matthew Garrett
2004-08-06 15:50 ` Nathan Bryant
2004-08-06 16:38 ` Nate Lawson
2004-08-06 19:32 ` Nathan Bryant
2004-08-09 8:10 Li, Shaohua
2004-08-31 8:45 Li, Shaohua
[not found] ` <B44D37711ED29844BEA67908EAF36F03AC6ACF-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-31 13:38 ` Georg C. F. Greve
[not found] ` <m3zn4bbf6x.fsf-eMhNhoSsuh6q92djB/mqZw@public.gmane.org>
2004-09-01 15:16 ` 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=m3k6wpmutz.fsf@reason.gnu-hamburg \
--to=greve-mxxj517/zsq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@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 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.