[haiku-commits] Re: Aw: haiku: hrev45566 - src/add-ons/kernel/drivers/power/x86_cpuidle build/jam
- From: Fredrik Holmqvist <fredrik.holmqvist@xxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Mon, 29 Apr 2013 13:37:18 +0200
Some more info about cpu_idle[1]:
"In my gsoc proposal, I mentioned the local APIC timer issue--APIC timers
may be shutdown when entering deeper C-States. For intel CPUs, this issue
will only happen after we adds the so called cpuidle support. But for AMD
CPUs, I think we already have this problem. Please refer to
http://dev.haiku-os.org/ticket/8111 for details. But I'm not sure whether
the root cause of #8111 is the APIC issue."
"The real fix should be switch to another reliable timer before hlt
instruction. But this need more haiku timer subsystem changes. I put this
into goal after gsoc."
/Fredrik Holmqvist, TQH
[1]
//www.freelists.org/post/haiku-development/patch-x86-AMD-C1E-with-no-ARATAlways-Running-APIC-Timer-idle-support,1
2013/4/29 Jessica Hamilton <jessica.l.hamilton@xxxxxxxxx>:
> The intel_extreme driver is at fault in terms of booting any further. I
> removed it and can now boot Haiku fine on my new IvyBridge. I can give you
> an updated syslog if it's helpful for this cpuidle stuff, or any further
> testing you need done. I got it purposefully for Haiku dev afterall...
>
>
> On 29 April 2013 22:07, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
>>
>> ingo_weinhold@xxxxxx wrote:
>>
>> Just in case anyone is interested ...
>>
>> > a83983a: acpi_cpuidle: Fix driver initialization
>> >
>> > * For some reason the code in acpi_processor_init() assumed that the
>> > CPU index returned by ACPI was 1-based. On my machines it is 0-based
>> > and the syslogs on Trac from the last months don't show any
>> > exception. The code even contained a hack to force satisifying that
>> > assumption for a single-CPU machine.
>>
>> I just saw a new syslog that shows 1-based indexing [1], apparently on an
>> IvyBridge system.
>>
>> > 31bc74d: Remove x86_cpuidle driver from image
>> >
>> > Apparently it isn't ready yet. I haven't found a single syslog on Trac
>> > that shows a successful initialization of the driver, and on my
>> > machine, where it does that at least, the system freezes during boot.
>>
>> ... and it even reports successful initialization. Since Haiku doesn't
>> seem to boot much farther, it's hard to say whether the driver actually
>> works on this system, though.
>>
>> CU, Ingo
>>
>> [1] http://dev.haiku-os.org/attachment/ticket/9718/syslog.txt
>>
>
--
Fredrik Holmqvist
Chaordic: things that thrive on the edge of chaos with just enough order to
give them pattern, but not so much to slow their adaptation and learning.
Other related posts:
