All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: S3 sleep regression / 2.6.16-rc1+acpi-release-20060113
Date: Sat, 4 Feb 2006 17:12:25 +1000	[thread overview]
Message-ID: <200602041712.30428.ncunningham@cyclades.com> (raw)
In-Reply-To: <E1F5FZL-0001sP-00@skye.ra.phy.cam.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]

Hi.

On Saturday 04 February 2006 15:02, Sanjoy Mahajan wrote:
> The gory details are at
> <http://bugzilla.kernel.org/show_bug.cgi?id=5989>, but the short
> summary:
>
> With 2.6.15, S3 sleep and wake were 98% fine (once in a while waking
> would hang, but I haven't managed to reproduce it).  However, with
> 2.6.16-rc1 with the acpi-20060113 patch, the first sleep and wake goes
> fine and the second sleep hangs at the 'Stopping tasks'.

After the first suspend, do you have any processes sucking all available 
cpu? This sounds like a thread that has been added since 2.6.15, which is 
being told to enter the freezer, but isn't doing it. They usually end up 
sucking cpu afterwards.

Regards,

Nigel

> With tons of debugging turned on, the second sleep does not hang, but
> the wakeup hangs.  With 0x1F as the acpi debug_level, the second sleep
> still hangs and produces some output across a serial console.  In the
> second sleep (after the second 'Stopping tasks'), it endlessly repeats
> a short sequence of
>
> exregion-0182 ...
> exregion-0287 ...
> exregion-0182 ...
>
> The machine is a TP 600X with the latest (1.11) BIOS and a fixed DSDT
> so that it can S3 sleep at all.
>
> -Sanjoy
>
> `Never underestimate the evil of which men of power are capable.'
>          --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

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

  reply	other threads:[~2006-02-04  7:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-04  5:02 S3 sleep regression / 2.6.16-rc1+acpi-release-20060113 Sanjoy Mahajan
2006-02-04  7:12 ` Nigel Cunningham [this message]
2006-02-04 20:53   ` Sanjoy Mahajan
2006-03-13  5:23     ` Nigel Cunningham
2006-03-13  5:25     ` Nigel Cunningham
2006-03-13  5:39       ` 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=200602041712.30428.ncunningham@cyclades.com \
    --to=ncunningham@cyclades.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sanjoy@mrao.cam.ac.uk \
    /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.