From: "P. Christeas" <p_christ-U04EIuiosng@public.gmane.org>
To: Knut Neumann
<knut.neumann-4bfl1RV3iZDOEhgYWvzSCYQuADTiUCJX@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: 2.5.39 Insomniac, any first dbg?
Date: Mon, 30 Sep 2002 16:12:28 +0300 [thread overview]
Message-ID: <200209301612.28344.p_christ@hol.gr> (raw)
In-Reply-To: <1033398342.7338.5.camel-s1IKGncK6J2OERECOqmV57dB6IYNvbhm87tLKu7D3g4@public.gmane.org>
> > I echo to /proc/acpi/sleep. Nothing happens, nothing gets logged for 1,4.
> > I looked into kernel/suspend.c and acpi/sleep.c . Which fn's can cause
> > the sleep procedure to fail w/o notices?
>
> Not quite sure...I would start making sure that the kernel actually
> notices that something has been echoed to sleep. There must be some
> handling of sleep as a proc filesystem entry - maybe in sleep.c. Look
> for it. I think starting there makes sense. If you find anything..let me
> know...I would not have to do double work then.
>
> -Knut
I guess that's the point to start from. Did you say there was some code
splitting in sleep.c? Last kernel that runned fine for me was 2.5.36 (I
couldn't cleanly compile .37 and .38).
It seems as if the code code in sleep.c doesn't call anything. It was
interesting, though that S2 did something, where it really wasn't supposed
to. The /proc entries should be fine. So, the bug must be after the
'switch(state){ \n case 1: '. You 'll need to add some trace messages in the
early state of those fn's.
Thanks for the help.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-09-30 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 12:41 2.5.39 Insomniac, any first dbg? P. Christeas
[not found] ` <200209301541.47910.p_christ-U04EIuiosng@public.gmane.org>
2002-09-30 15:05 ` Knut Neumann
[not found] ` <1033398342.7338.5.camel-s1IKGncK6J2OERECOqmV57dB6IYNvbhm87tLKu7D3g4@public.gmane.org>
2002-09-30 13:12 ` P. Christeas [this message]
[not found] ` <200209301612.28344.p_christ-U04EIuiosng@public.gmane.org>
2002-09-30 15:44 ` Knut Neumann
[not found] ` <1033400645.7338.17.camel-s1IKGncK6J2OERECOqmV57dB6IYNvbhm87tLKu7D3g4@public.gmane.org>
2002-09-30 16:32 ` Sleeping pills for the 2.5.39 Insomnia P. Christeas
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=200209301612.28344.p_christ@hol.gr \
--to=p_christ-u04eiuiosng@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=knut.neumann-4bfl1RV3iZDOEhgYWvzSCYQuADTiUCJX@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