http://bugzilla.kernel.org/show_bug.cgi?id=7499


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[EMAIL PROTECTED]




------- Comment #25 from [EMAIL PROTECTED]  2007-08-16 13:55 -------
Puhh.
Some ideas (I couldn't really find anything):
  - compile ACPI_DEBUG in and increase /proc/acpi/debug_level to 0x11F before  
    suspend. At least last lines which AML stuff got executed shortly before
the
    hang might be interesting.
  - The machine implements a PTS and a WAK function. Does it work if you
comment 
    out kernel code that invokes these, just comment out these in drivers/acpi/
    hardware/hwsleep.c:
        /* Run the _PTS and _GTS methods */
        status = acpi_evaluate_object(NULL, METHOD_NAME__PTS, &arg_list, NULL);
        if (ACPI_FAILURE(status) && status != AE_NOT_FOUND) {
                return_ACPI_STATUS(status);
        }
        and:
        status = acpi_evaluate_object(NULL, METHOD_NAME__WAK, &arg_list, NULL);
        if (ACPI_FAILURE(status) && status != AE_NOT_FOUND) {
                ACPI_EXCEPTION((AE_INFO, status, "During Method _WAK"));
        }
  - Maybe these iasl warnings are related:
DSDT.dsl  2702:                             Wait (\_SB.PCI0.DKSQ, 0x0BB8)
Warning  1103 -                   Possible operator timeout is ignored ^
    I also have never seen ASL code playing around with signal() and event()
    things.
    Do you know how to override an DSDT table? If not, just ask.
    If you do:
    acpidump >acpidump
    apcixtract -a acpidump
    iasl -d DSDT.dat
    iasl -sa DSDT.dsl
    you get above warnings.
    Do a grep DKSQ DSDT.dsl and comment out these lines in DSDT.dsl with:
    //
    recompile the DSDT.dsl with iasl -tc DSDT.dsl (AFAIK the output file you
    need is xy.hex (dsdt.hex or DSDT.hex)
    then you have two variables in .config:
    ACPI_CUSTOM_DSDT
    and
    ACPI_CUSTOM_DSDT_FILE
    The first one must be enabled.
    The second one is a string config and must point to the above .hex file.
    The recompile the kernel and reboot and you have overridden your DSDT table
    and got rid of these strange DSKQ elements.

-> Also adding Alexey, he has deep knowledge in this stuff...
Alexey, it seems like we get a deadlock on a spinlock when waking up from
suspend to ram. If above suggestions don't bring anything, I am out of ideas...


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to