[haiku-commits] Re: Aw: haiku: hrev45566 - src/add-ons/kernel/drivers/power/x86_cpuidle build/jam
- From: Jessica Hamilton <jessica.l.hamilton@xxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Mon, 29 Apr 2013 23:13:18 +1200
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
>
>
Other related posts:
