Hello;

with the latest git on a macbook the system can barely boot without

freezing, a work around for me at leat is either disable smp, or once

booted  turn on glxgears,or compiling the kernel i.g. when using the

processors I'm not receiving a freeze, only when everything starts

lowering down. in dmesg I'm noticing BIOS bug, APIC version is 0 for

CPU#0! fixing up to 0x10. (tell you're hw vendor) could this be the

reason for the system freezes?, also I didnt have a camera handy on me

but the screen spit out = Bug spinlock lockup on CPU#0

swapper/0. c17fa7c0 PID 0, comm: swapper not tainted.

I dont have a problem disabling smp, except when I cat /proc/cpuinfo I

don't see anything about my cores. I know this is a stupid question

but will it hurt the system if smp is disabled

for the macbook pro ati chipset.?

regards;
--

Justin P. Mattock

I don't think so. On my machine there's no freezes with latest git and:

ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)

BIOS bug, APIC version is 0 for CPU#0! fixing up to 0x10. (tell your hw vendor)

ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)

BIOS bug, APIC version is 0 for CPU#0! fixing up to 0x10. (tell your hw vendor)
No it won't.
-Jacek

--

under smp I see cpu cores. disabling smp I dont see cpu cores, under
Cool as long as the system Is o.k. disabling smp.  What about x86: PAT

support is disabled. how do I enable this option?

regards;
--

Justin P. Mattock

--

well.. SMP is kindof support for multiple processors, be it in one

socket, or multiple sockets.. without SMP you will only be able to use 1
--

Thanks for the feedback, well I guess this would be either a

regression or a bug. I think the best would be to have somebody else

with a macbook pro 15' ati chipset confirm this freezeing as well,

before going out and jumping the gun, and filing a bug report.

regards;
--

Justin P. Mattock

--

What's the current status of this issue?
Rafael

--

I reported this issue too but got ignored .. No one of the x86 maintainer did answer my questions.
http://www.ussg.iu.edu/hypermail/linux/kernel/0805.0/1258.html
However it does not do any bad on my boxes ( so far I can tell ) is just plain annoying and wrong some who since

is *only* occurs on 32bit kernels. HW is broken or even isn't.
It seems to me this issue is related to the move of generic_processor_info() and fiends to apic_32.c ( but I'm not really sure ) ,
Regards,
Gabriel
--

It will be listed as http://bugzilla.kernel.org/show_bug.cgi?id=10613.
Please add yourself to the Cc list in there.
Thanks,

Rafael

--

Cool, thanks for informing me. As of now I've decided to revert to

2.6.25-rc9 due to it running smoothly on a macbook pro,

and everything working. I'll try a go at a later kernel, whenever ATI

decides to add support for fault.

regards;
--

Justin P. Mattock

--

Hello; well having something in dmesg give you a BUG signal is a bit

worrysome but there is probably a good reason for that there.

Probably with all of the other changes going on in the kernel, this

would be a temporary solution, until other areas were attended too.

who knows;

regards;
--

Justin P. Mattock

--

Right now I loaded 2.6.26-rc1 and everything seems to be O.K., The

freezing was resolved With a patch from peter Zijlstra I think it was

called

idle-lockdep-1.patch. From what I can remember this patch was put upstream.

regards;
--

Justin P. Mattock

--