i've got the same thing.
i can boot the 9.8.0 v1.7 with option cpus=15
i can't boot with cpus=16

---

My OSX
System:DELL Precision T5500
OS:Mac OS X Leopard w/ANV Kernel 9.6.0 for boot with the 16 cpus
CPU:Intel XEON 2xE5520 @ 2.27 GHz
Memory:12 GB DDR2 SDRAM @ 1066 MHz
Graphics Chip: GForce 7300GT

Thats because osx starts the cpu count at 0, so you have 16 threads and if you have dsdt patched it has cpu 0-15 and when you try and boot it with one more cpu it will crash.

---

GA-Z68XP-UD3: Lion 10.7.3, Windows 7 Professional 64bit SP1 and FreeBSD 9-RELEASE, Core i5 2500K @ 3.3GHz, 16GB 1333 Mhz DDR3 ram(Soon), 1GB GDDR5 Nvidia Geforce GTX 560 Ti, 2X 1TB Samsung F3 SATA HDDs, 1X WDC Blue 500GB HDD; Dell Mini 10v: Obsidian Black, 2GB DDR2 533MHz Ram, 1.6GHz Intel Atom N270, 120GB HDD, 6-Cell, Mac OS X Snow Leopard 10.6.8 Build 10K549

Interesting...
It does misdetect the cpu count thus.
Perhaps I should put in a check but if it's DSDT related it should be fixed there

Hi,

I am using an AMD 4400 X2 on ASUS M3A78-EM 780G Motherboard. I was previously using you kernel 9.6.0 v1.4 on chameleon bootloader v1 which was working fine. However as soon as I upgraded the kernel to v 9.8.0 I have started getting kernel panics. I have also tried using Chameleon 2 RC1 and RC2 by I am still getting kernel panics. I have also tried your kernels 9.7.0 and 9.8.0 v1 and any kernel higher than 9.6.0 is giving KPs.

Surprisingly the new kernel is working fine when i am booting using my usb boot-132 but gives KP when I try to use it on chameleon bootloader on HDD. I am using the current latest system kext along with dsmos, intel pm disabler, smbios kexts.

I have attached an image of the Kernel Panic I am getting. Please Help.
kp.jpg

Thanks

Ankit

hello,
here a part of mys dsdt.
Scope (_PR)
{
Processor (CPU1, 0x01, 0x00000810, 0x06) {}
Processor (CPU2, 0x02, 0x00000000, 0x00) {}
Processor (CPU3, 0x03, 0x00000000, 0x00) {}
Processor (CPU4, 0x04, 0x00000000, 0x00) {}
Processor (CPU5, 0x05, 0x00000000, 0x00) {}
Processor (CPU6, 0x06, 0x00000000, 0x00) {}
Processor (CPU7, 0x07, 0x00000000, 0x00) {}
Processor (CPU8, 0x08, 0x00000000, 0x00) {}
Processor (CPU9, 0x09, 0x00000000, 0x00) {}
Processor (CP10, 0x0A, 0x00000000, 0x00) {}
Processor (CP11, 0x0B, 0x00000000, 0x00) {}
Processor (CP12, 0x0C, 0x00000000, 0x00) {}
Processor (CP13, 0x0D, 0x00000000, 0x00) {}
Processor (CP14, 0x0E, 0x00000000, 0x00) {}
Processor (CP15, 0x0F, 0x00000000, 0x00) {}
Processor (CP16, 0x10, 0x00000000, 0x00) {}
}

i think everything is ok.
no??

---

My OSX
System:DELL Precision T5500
OS:Mac OS X Leopard w/ANV Kernel 9.6.0 for boot with the 16 cpus
CPU:Intel XEON 2xE5520 @ 2.27 GHz
Memory:12 GB DDR2 SDRAM @ 1066 MHz
Graphics Chip: GForce 7300GT

use the system.kext provided in the AnV-XNU-980-V1.7.zip to make it work.

---

GA-Z68XP-UD3: Lion 10.7.3, Windows 7 Professional 64bit SP1 and FreeBSD 9-RELEASE, Core i5 2500K @ 3.3GHz, 16GB 1333 Mhz DDR3 ram(Soon), 1GB GDDR5 Nvidia Geforce GTX 560 Ti, 2X 1TB Samsung F3 SATA HDDs, 1X WDC Blue 500GB HDD; Dell Mini 10v: Obsidian Black, 2GB DDR2 533MHz Ram, 1.6GHz Intel Atom N270, 120GB HDD, 6-Cell, Mac OS X Snow Leopard 10.6.8 Build 10K549

I am using the system kext provided with the kernel

Try repairing permission + booting with -f

I've checked and this is wrong...
replace as follows:
This should fix booting up with all cores right...
I've checked this in a Mac Pro DSDT dump...
Apple starts CPU entries from 0 rather than 1.
Hereby the CPU count is probably misdetected etc...
Try modding your DSDT and let me know
This will also fix your IOService node in IORegistry btw

How come any mention of this release on insanelymac get's the thread instantly deleted?

I hope this doesn't get me banned from here and this thread ninja-ed by the secret police in blackhawk helicopters.