All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alvaro Lopes <alvieboy-JkNoWtNHh5AAvxtiuMwx3w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: ACPI Lock after resume from S3 [2.5.59+latest ACPI]
Date: Thu, 06 Feb 2003 18:33:30 +0000	[thread overview]
Message-ID: <3E42AA7A.1030207@alvie.com> (raw)

Hi list

here's the problem:

My toshiba enters S3 via acpi_enter_sleep_state(). It goes to sleep 
right after writing PM1A_CONTROL with SLP_ENABLE.  It resumes then to 
the caller  [acpi_suspend()] and then calls acpi_restore_system_state() 
and finally acpi_leave_sleep_state().

The problem is that it enters a deadlock because:

    1- When setting PM1A_CONTROL with flag ACPI_MTX_LOCK, the hardware 
mutex is locked, the system enters sleep right after writing the 
register and never unlocks the mutex, because it resumes to a different 
point;

    2- in acpi_leave_sleep_state() we disable BM artbitration, and here 
it locks forever, waiting a hardware mutex release.

Disabling APCI_MTX_LOCK on the 1st point seems to go around the problem, 
and the system resumes almost OK, only HDD DMA is disabled:

Feb  6 18:19:26 supernova kernel: hda: status timeout: status=0x80 { Busy }
Feb  6 18:19:26 supernova kernel: hda: DMA disabled
Feb  6 18:19:26 supernova kernel: hda: drive not ready for command
Feb  6 18:19:27 supernova kernel: ide0: reset: master: error (0x00?)

Álvaro

-- 

Álvaro Lopes 
---------------------
A .sig is just a .sig




-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

             reply	other threads:[~2003-02-06 18:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 18:33 Alvaro Lopes [this message]
     [not found] ` <3E42AA7A.1030207-JkNoWtNHh5AAvxtiuMwx3w@public.gmane.org>
2003-02-06 20:47   ` ACPI Lock after resume from S3 [2.5.59+latest ACPI] Ducrot Bruno

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=3E42AA7A.1030207@alvie.com \
    --to=alvieboy-jknowtnhh5aavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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.