From: "Matheus Izvekov" <mizvekov@gmail.com>
To: "Len Brown" <lenb@kernel.org>
Cc: "Arjan van de Ven" <arjan@infradead.org>,
"Luming Yu" <luming.yu@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: BUG: linux 2.6.19 unable to enable acpi
Date: Fri, 19 Jan 2007 21:10:11 -0200 [thread overview]
Message-ID: <305c16960701191510g2ed9ef4ev184d09c7b7d75408@mail.gmail.com> (raw)
In-Reply-To: <305c16960701191003k3e69cf65o135cc2a9b1249943@mail.gmail.com>
On 1/19/07, Matheus Izvekov <mizvekov@gmail.com> wrote:
> On 1/19/07, Len Brown <lenb@kernel.org> wrote:
> > I guess I'm losing my mind, because when I read this code,
> > there are only two ways out of the while(retry) loop.
> > Either return with success, or retry is 0.
> > So how the heck is retry printed as 142?!
> >
> > did you notice any delay between the last two lines of printout above?
> >
> > please boot with "acpi_dbg_layer=2" "acpi_dbg_level=0xffffffff"
> > so that we can see each read and write of the hardware look like.
> > Success is measured here by looking for SCI_EN being set
> > to indicate that we successfully entered ACPI mode.
> >
> > I guess we should see about 142 reads looking for SCI_EN...
> >
> > It would be interesting if you could boot a windows disk on this box
> > to see if they are able to get into ACPI mode. You'd be able to
> > tell by dumping the interrupt list, looking at the device tree,
> > or observing if the power button gives immediate poweroff
> > or does an OS shutdown.
> >
> > thanks,
> > -Len
>
> printk("ACPI: retry %d\n") -> printk("ACPI: retry %d\n", retry)
> ;)
> ill try this again soon.
>
Ok, here is what i got:
hwacpi-0207 [C031D380] [04] hw_get_mode : ----Entry
hwregs-0273 [C031D380] [05] get_register : ----Entry
hwregs-0487 [C031D380] [06] hw_register_read : ----Entry
hwregs-0810 [C031D380] [06] hw_low_level_read : Read: 00000000
width 16 from 0000000000000404 (SystemIO)
hwregs-0575 [C031D380] [06] hw_register_read : ----Exit- AE_OK
hwregs-0300 [C031D380] [05] get_register : Read value
00000000 register 3
hwregs-0303 [C031D380] [05] get_register : ----Exit- AE_OK
hwacpi-0226 [C031D380] [04] hw_get_mode : ----Exit- 0000000000000002
ACPI: retry 0
ACPI Error (hwacpi-0185): Hardware did not change modes [20060707]
hwacpi-0186 [C031D380] [03] hw_set_mode : ----Exit-
****Exception****: AE_NO_HARDWARE_RESPONSE
ACPI Error (evxfevnt-0084): Could not transition to ACPI mode [20060707]
ACPI Warning (utxface-0154): AcpiEnable failed [20060707]
ACPI: Unable to enable ACPI
next prev parent reply other threads:[~2007-01-19 23:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 4:01 Matheus Izvekov
2007-01-17 4:14 ` Arjan van de Ven
2007-01-17 4:25 ` Matheus Izvekov
2007-01-17 6:26 ` Luming Yu
2007-01-17 7:35 ` Matheus Izvekov
2007-01-17 7:42 ` Matheus Izvekov
2007-01-17 9:08 ` Len Brown
2007-01-17 21:10 ` Matheus Izvekov
2007-01-19 8:36 ` Len Brown
2007-01-19 18:03 ` Matheus Izvekov
2007-01-19 23:10 ` Matheus Izvekov [this message]
2007-01-17 10:34 ` Sunil Naidu
2007-01-17 19:44 ` Matheus Izvekov
[not found] ` <200701190338.33147.lenb@kernel.org>
2007-01-20 2:59 ` Sunil Naidu
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=305c16960701191510g2ed9ef4ev184d09c7b7d75408@mail.gmail.com \
--to=mizvekov@gmail.com \
--cc=arjan@infradead.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@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
all inboxes | Powered by JetHome®