linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <aystarik@gmail.com>
To: Thomas Lindroth <thomas.lindroth@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Problem: ACPI related soft lockup on Fujitsu-Siemens AMILO Si 2636
Date: Wed, 08 Oct 2008 12:49:52 +0400	[thread overview]
Message-ID: <48EC7430.1010001@gmail.com> (raw)
In-Reply-To: <48EC6465.8060200@gmail.com>

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

Alexey Starikovskiy wrote:
> Thomas Lindroth wrote:
>> I've done some debugging of this problem myself and reached some 
>> conclusions.
>>
>> I tried activating the ACPI_LV_INFO ACPI debug mode and observed what 
>> happens
>> when the system is under load. I saved one trace and put it in the file
>> acpi_debug_log at http://www.cyd.liu.se/~tholi945/acpi-bug-2008-10-06/
>>
>> When the temp goes over the ACPI passive trip point the processor gets
>> throttled. It usually never goes over T4 before the temp falls below the
>> passive temp but sometimes it reaches the highest T7. If it reach T7 the
>> next call to _TMP or _L18 never returns. I've confirmed this by running
>> echo T7 > /proc/acpi/processor/CPU*/throttling and then tried to read
>> from /proc/acpi/thermal_zone/TZ00/temperature and it fails in the 
>> same way.
>>
>> I've tried activating the ACPI_LV_PARSE ACPI debug mode, enter T7 and 
>> read
>> from temp. I put the result of that in the trace_debug file at the 
>> same adress.
>>
>> The AML call chain looks like this _TMP -> PMRD -> RCMD -> WIBF
>> WIBF always returns 1 causing the interpreter to get stuck in the while
>> loop in PMRD.
>>
>> While (RCMD (0x80, Local0))
>> {
>>     Noop
>>     Noop
>>     Store (PMUC, Local5)
>>     If (And (Local5, One, Local2))
>>     {
>>         Store (PMUD, Local5)
>>     }
>> }
>>
>>   
> This is AML implementation of EC driver... it relies on certain speed
> of AML interpreter to work properly (look for Noop inserted as delay).
>
> It is possible to replace this driver with the native Linux one, which 
> might be
> more robust, but this involves heavy DSDT hacking.
>
> Overall, it is heavily mis-designed BIOS, so don't expect it to be 
> fixed on Linux side.
>
> Regards,
> Alex.
Please check if making Noop a small delay helps





[-- Attachment #2: x.patch --]
[-- Type: text/x-diff, Size: 387 bytes --]

diff --git a/drivers/acpi/dispatcher/dsopcode.c b/drivers/acpi/dispatcher/dsopcode.c
index 6a81c44..acd5fb6 100644
--- a/drivers/acpi/dispatcher/dsopcode.c
+++ b/drivers/acpi/dispatcher/dsopcode.c
@@ -1368,6 +1368,7 @@ acpi_ds_exec_end_control_op(struct acpi_walk_state * walk_state,
 	case AML_NOOP_OP:
 
 		/* Just do nothing! */
+		udelay(100);
 		break;
 
 	case AML_BREAK_POINT_OP:

  reply	other threads:[~2008-10-08  8:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-06 11:23 Problem: ACPI related soft lockup on Fujitsu-Siemens AMILO Si 2636 Thomas Lindroth
2008-10-08  7:20 ` Thomas Lindroth
2008-10-08  7:42   ` Alexey Starikovskiy
2008-10-08  8:49     ` Alexey Starikovskiy [this message]
2008-10-08 10:48       ` Thomas Lindroth
2008-10-08 11:08         ` Thomas Renninger
2008-10-08 11:52           ` Alexey Starikovskiy
2008-10-08 22:19             ` Thomas Renninger
2008-10-09  1:50   ` Len Brown
2008-10-09  7:46     ` Thomas Lindroth

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=48EC7430.1010001@gmail.com \
    --to=aystarik@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=thomas.lindroth@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).