6378 Views Previous 1 2 Next 19 Replies Latest reply: Dec 1, 2010 8:55 AM by dfgfgre Go to original post
To add to that, from Wikipedia:
It was originally implemented by the Intel 82093AA and 82489DX, and is found in most x86 SMP motherboards. It is one of several attempts to solve interrupt routing efficiency issues in multiprocessor computer systems.
There are a number of known bugs in implementations of APIC systems, especially with concern to how the 8254 is connected. Defective BIOSes may not set up interrupt routing properly, or provide incorrect ACPI tables and Intel Multiprocessor Specification tables.
Finally, the APIC can also be a cause of system failure when the operating system does not support it properly.
*On older operating systems*, people often had to disable the I/O and local APICs. While this is not possible anymore due to the prevalence of simultaneous multi-threading and multi-core systems, the bugs in the firmware and the operating systems are now a rare occurrence.
Just another thought. Have you added extra RAM to your MacBook Pro? The newer Macs need to use matched RAM. At least the Mac Pros do. You can't just match up the same specs such as speed, latency, etc. If you put in more RAM, you must remove the existing RAM and put in sticks from the same manufacturer that is designed to work with your system.
So if you added extra RAM from another vendor, take that out so the MacBook Pro is running only on the RAM as it came from Apple and see if that helps.
I have the exact same problem, with the difference, that I do not want to install Windows but to boot my OS X install. After a nightly freeze of my MacBook the system didn't come up any more. Not from the hdd and not from the original install DVD! After days of trial and error I succeeded booting Linux with the noapic kernel boot flag.
So guys, how could someone pass the noapic XNU kernel flag on boot? I have an obvious hardware bug with the APIC controller, but my MacBook still works fine under Linux.
aaar, what did the Apple Store say??