All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alvaro Lopes <alvieboy-JkNoWtNHh5AAvxtiuMwx3w@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [ACPI] 2.5.58 hangs at boot
Date: Sun, 26 Jan 2003 13:59:55 +0000	[thread overview]
Message-ID: <3E33E9DB.2070604@alvie.com> (raw)
In-Reply-To: <3E300BCE.9080909-JkNoWtNHh5AAvxtiuMwx3w@public.gmane.org>

> This repeats 'ad infinitum'. Didn't wait for more than a few minutes, 
> but it looks like it will.
>
> The interrupts are handled at acpi_ev_gpe_detect (), which returns 1. 
> At this point in_irq() returns 0x00010000 (or 0x00001000, don't have a 
> serial console :/)
>
I have done some debugging, and here are the not-so-exciting results:

GPE08 is dispatched. My debug shows something like this:

* Is a control method
* Method at AML address d08047a4 length 39D
* Begin method parse Entry=cff43904 obj=cff4238c
* State=cff4ec00
* Completed one call  to walk loop, AE_OK, state=cff4ec00
* Parser exiting, status AE_OK
* Begin method execution Entry=cff43904 obj=cff4238c
* State=cff4ec00
* Completed one call to walk loop, AE_CTRL_TRANSFER State=cff4ec00
* Execute Method 00000000, current state cff4ec00
* State=cff4e800
* Completed one call to walk loop, AE_OK, State=cff4e800
* Parser exiting, status AE_OK
* Starting nested execution, newstate=cff4e800
* Completed one call to walk loop, AE_OK, state=cff4e800
* Completed one call to walk loop, AE_OK, state=cff4ec00
* Parser exiting, status AE_OK

And keeps doing this every time GPE08 is enabled.

Any ideas ? Right now I have disabled the GPE and can trigger an enable 
via /proc, so if you need more info, please tell me.

The hex dump at 0xd08047a4 + 1 shows something like:

5c 2f 04 5f 53 42 5f 50 43 49 30 50 43 49 42 42 52 47 42 60 79 60 0a 18 
60 0c 0b b1 20 00 60 70 0a af
5c 2f 03 5f 53 42 5f 4d 45 4d 5f 49 45 44 49 53 4d 42 52 0b 00 ff 60 0a 
00 0a 00 0a b2 a2 4b 35 91
5c 2f 03 5f 53 42 5f 4d 45 4d 5f 47 50 35 30 91
....

And now a stupid question: on the second line I believe it reads as 
"Root" "Multiname" "3 Segments", but it looks like it has 4 
(_SB_.MEM_.IEDI.SMBR). Is this correct ?

-- 

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

WARNING: multiple messages have this Message-ID (diff)
From: Alvaro Lopes <alvieboy@alvie.com>
To: linux-kernel@vger.kernel.org
Cc: acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] 2.5.58 hangs at boot
Date: Sun, 26 Jan 2003 13:59:55 +0000	[thread overview]
Message-ID: <3E33E9DB.2070604@alvie.com> (raw)
In-Reply-To: <3E300BCE.9080909@alvie.com>

> This repeats 'ad infinitum'. Didn't wait for more than a few minutes, 
> but it looks like it will.
>
> The interrupts are handled at acpi_ev_gpe_detect (), which returns 1. 
> At this point in_irq() returns 0x00010000 (or 0x00001000, don't have a 
> serial console :/)
>
I have done some debugging, and here are the not-so-exciting results:

GPE08 is dispatched. My debug shows something like this:

* Is a control method
* Method at AML address d08047a4 length 39D
* Begin method parse Entry=cff43904 obj=cff4238c
* State=cff4ec00
* Completed one call  to walk loop, AE_OK, state=cff4ec00
* Parser exiting, status AE_OK
* Begin method execution Entry=cff43904 obj=cff4238c
* State=cff4ec00
* Completed one call to walk loop, AE_CTRL_TRANSFER State=cff4ec00
* Execute Method 00000000, current state cff4ec00
* State=cff4e800
* Completed one call to walk loop, AE_OK, State=cff4e800
* Parser exiting, status AE_OK
* Starting nested execution, newstate=cff4e800
* Completed one call to walk loop, AE_OK, state=cff4e800
* Completed one call to walk loop, AE_OK, state=cff4ec00
* Parser exiting, status AE_OK

And keeps doing this every time GPE08 is enabled.

Any ideas ? Right now I have disabled the GPE and can trigger an enable 
via /proc, so if you need more info, please tell me.

The hex dump at 0xd08047a4 + 1 shows something like:

5c 2f 04 5f 53 42 5f 50 43 49 30 50 43 49 42 42 52 47 42 60 79 60 0a 18 
60 0c 0b b1 20 00 60 70 0a af
5c 2f 03 5f 53 42 5f 4d 45 4d 5f 49 45 44 49 53 4d 42 52 0b 00 ff 60 0a 
00 0a 00 0a b2 a2 4b 35 91
5c 2f 03 5f 53 42 5f 4d 45 4d 5f 47 50 35 30 91
....

And now a stupid question: on the second line I believe it reads as 
"Root" "Multiname" "3 Segments", but it looks like it has 4 
(_SB_.MEM_.IEDI.SMBR). Is this correct ?

-- 

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



  parent reply	other threads:[~2003-01-26 13:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16 21:38 [ACPI] 2.5.58 hangs at boot Grover, Andrew
2003-01-16 21:38 ` Grover, Andrew
     [not found] ` <F760B14C9561B941B89469F59BA3A847137F76-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-01-16 22:26   ` Michael Dreher
2003-01-23 15:35 ` [ACPI] " Alvaro Lopes
     [not found]   ` <3E300BCE.9080909-JkNoWtNHh5AAvxtiuMwx3w@public.gmane.org>
2003-01-26 13:59     ` Alvaro Lopes [this message]
2003-01-26 13:59       ` Alvaro Lopes
  -- strict thread matches above, loose matches on Subject: below --
2003-01-16 21:15 Michael Dreher

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