[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <305c16960701191003k3e69cf65o135cc2a9b1249943@mail.gmail.com>
Date: Fri, 19 Jan 2007 16:03:01 -0200
From: "Matheus Izvekov" <mizvekov@...il.com>
To: "Len Brown" <lenb@...nel.org>
Cc: "Arjan van de Ven" <arjan@...radead.org>,
"Luming Yu" <luming.yu@...il.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: BUG: linux 2.6.19 unable to enable acpi
On 1/19/07, Len Brown <lenb@...nel.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists