On 1/19/07, Matheus Izvekov <[email protected]> wrote:
On 1/19/07, Len Brown <[email protected]> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
