e7440 KP with latest BIOS on every boot

[Sorcerer]

Just updated from A05 to A18 on the e7440 and it is giving me a kernel panic on each boot up unless i set CPUS=1.. 

 

 Any help here appreciated.

 

Here is the Boot Log after a successful boot with CPUS=1.. 

Although it also booted OK with verbose mode Hmmm.  May have been a freak occurrence though.

 

 

 

Anonymous UUID:       014D04E1-BB15-5E9D-9373-8B446A600C62

 

Wed May  4 23:04:37 2016

 

*** Panic Report ***

panic(cpu 3 caller 0xffffff80003ceeca): "Double fault at 0xffffff80003acd8f, registers:\n" "CR0: 0x000000008001003b, CR2: 0xffffff809dd138e8, CR3: 0x0000000008840000, CR4: 0x00000000001627e0\n" "RAX: 0x00000000001627e0, RBX: 0xffffff8000aee6d0, RCX: 0x0000000000162760, RDX: 0xffffff8000a2cee0\n" "RSP: 0xffffff809dd138f0, RBP: 0xffffff809dd13980, RSI: 0x0000000008840000, RDI: 0x0000000000000001\n" "R8:  0x0000000000000000, R9:  0x0000000000000000, R10: 0xbfffffffffffff01, R11: 0x0000000000000001\n" "R12: 0x0000000000000001, R13: 0x0000000000000010, R14: 0x0000000000000001, R15: 0x0000000000000004\n" "RFL: 0x0000000000010202, RIP: 0xffffff80003acd8f, CS:  0x0000000000000008, SS:  0x0000000000000000\n" "Error code: 0x0000000000000000\n"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3248.40.184/osfmk/i386/trap_native.c:168

Backtrace (CPU 3), Frame : Return Address

0xffffff8097e15e90 : 0xffffff80002dab12 

0xffffff8097e15f10 : 0xffffff80003ceeca 

0xffffff8097e16070 : 0xffffff80003ecb2f 

No mapping exists for frame pointer

Backtrace terminated-invalid frame pointer 0xffffff809dd13980

 

BSD process name corresponding to current thread: kernel_task

Boot args: dart=0 kext-dev-mode=1 slide=0 

 

Mac OS version:

Not yet set

 

Kernel version:

Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016; root:xnu-3248.40.184~3/RELEASE_X86_64

Kernel UUID: 4E7B4496-0B81-34E9-97AF-F316103B0839

__HIB  text base: 0xffffff8000100000

System model name: MacBookPro11,1 (Mac-189A3D4F975D5FFC)

 

System uptime in nanoseconds: 2190380556

last loaded kext at 1980405081: com.apple.driver.CoreStorageFsck 517.20.1 (addr 0xffffff7f8202b000, size 106496)

loaded kexts:

org.apple.driver.PS2Trackpad 1.8.11

org.apple.driver.PS2Keyboard 1.8.11

org.hwsensors.driver.LPCSensors 1655

com.insanelymac.IntelMausiEthernet 2.0.0d2

org.rehabman.driver.FakePCIID 1.2.0

org.hwsensors.driver.ACPISensors 1655

org.apple.driver.PS2Controller 1.8.11

org.hwsensors.driver.CPUSensors 1655

org.rehabman.driver.AppleSmartBatteryManager 1.60.5

org.netkas.driver.FakeSMC 1655

com.apple.driver.CoreStorageFsck 517.20.1

com.apple.iokit.IOAHCIBlockStorage 2.8.5

com.apple.driver.AppleFileSystemDriver 3.0.1

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0

com.apple.BootCache 38

com.apple.driver.AppleAHCIPort 3.1.8

com.apple.driver.usb.AppleUSBEHCIPCI 1.0.1

com.apple.driver.AirPort.Atheros40 700.74.5

com.apple.driver.AppleSDXC 1.7.0

com.apple.driver.AppleACPIButtons 4.0

com.apple.driver.AppleACPIEC 4.0

com.apple.driver.AppleRTC 2.0

com.apple.driver.AppleHPET 1.8

com.apple.driver.AppleSMBIOS 2.1

com.apple.driver.AppleAPIC 1.7

com.apple.nke.applicationfirewall 163

com.apple.security.quarantine 3

com.apple.security.TMSafetyNet 8

com.apple.driver.CoreStorage 517.20.1

com.apple.driver.AppleXsanScheme 3

com.apple.driver.usb.cdc 5.0.0

com.apple.driver.usb.networking 5.0.0

com.apple.driver.usb.AppleUSBHostCompositeDevice 1.0.1

com.apple.driver.usb.AppleUSBHub 1.0.1

com.apple.iokit.IOAHCIFamily 2.8.1

com.apple.driver.usb.AppleUSBEHCI 1.0.1

com.apple.iokit.IO80211Family 1110.26

com.apple.driver.corecapture 1.0.4

com.apple.driver.AppleIntelLpssGspi 2.0.60

com.apple.driver.AppleEFINVRAM 2.0

com.apple.driver.usb.AppleUSBXHCIPCI 1.0.1

com.apple.driver.usb.AppleUSBXHCI 1.0.1

com.apple.iokit.IONetworkingFamily 3.2

com.apple.driver.AppleEFIRuntime 2.0

com.apple.iokit.IOUSBFamily 900.4.1

com.apple.iokit.IOUSBHostFamily 1.0.1

com.apple.driver.AppleUSBHostMergeProperties 1.0.1

com.apple.iokit.IOHIDFamily 2.0.0

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 300.0

com.apple.kext.AppleMatch 1.0.0d1

com.apple.driver.AppleKeyStore 2

com.apple.driver.AppleMobileFileIntegrity 1.0.5

com.apple.driver.AppleCredentialManager 1.0

com.apple.driver.DiskImages 417.2

com.apple.iokit.IOStorageFamily 2.1

com.apple.iokit.IOReportFamily 31

com.apple.driver.AppleFDEKeyStore 28.30

com.apple.driver.AppleACPIPlatform 4.0

com.apple.iokit.IOPCIFamily 2.9

com.apple.iokit.IOACPIFamily 1.4

com.apple.kec.pthread 1

com.apple.kec.Libm 1

com.apple.kec.corecrypto 1.0

Model: MacBookPro11,1, BootROM MBP111.0138.B03, 2 processors, Intel Core i5, 2.49 GHz, 4 GB, SMC 2.16f58

Graphics: Intel HD 4400, Intel HD 4400, Built-In

Memory Module: BANK0/DIMM0, 4 GB, DDR3, 1600 MHz, Hynix Semiconductor, HMT351S6EFR8A-PBN0

AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0xE007), Atheros 9280: 4.0.74.0-P2P

Network Service: Wi-Fi, AirPort, en1

PCI Card: O2 Micro SD Card Reader, Built-in

Serial ATA Device: LITEONIT LMT-128M6M mSATA 128GB, 128.04 GB

USB Device: USB 3.0 Bus

USB Device: Optical USB Mouse

USB Device: Laptop_Integrated_Webcam_HD

USB Device: USB 2.0 Bus

USB Device: Hub

Thunderbolt Bus: 

 

 

[Sorcerer]

ok confirmed now that booting in Verbose mode and the system boots normally without cpus=1.. 

 

but if booting in non verbose mode, i get a Kernel Panic..  

 

tried verbose 2 ways, 

1) space bar in clover to boot in verbose. 

and

2) -v boot flag in the boot string. 

 

both will boot OSX normally without cpus=1 in the boot string.

 

not sure whats going on.  why would verbose boot work and non verbose give Kernel Panics.   Does not make sense....

[Hervé]

It's also probably worth checking if any new parameter was made available with that latest BIOS or if existing ones were possibly reset or

modified.

 

If everything looks similar, try and rebuild your cache. If still KP, maybe you shoud revert to the older BIOS version. This being said, I've had no trouble when updating my E6440 BIOS from A05 to A08, then to A13 and A14 (this very day).

 

I think there is something fishy with your own build because I've personally tested (albeit remotely) a Clover installation on another member's E7440 and the laptop never displayed the issues you've encountered (for instance, it can run the VoodooPS2Controller without issue in 10.11.4).

[Bronxteck]

one of the differences booting verbose is that it performs an fsck  to the drive.

[Sorcerer]

It's also probably worth checking if any new parameter was made available with that latest BIOS or if existing ones were possibly reset or

modified.

 

If everything looks similar, try and rebuild your cache. If still KP, maybe you shoud revert to the older BIOS version. This being said, I've had no trouble when updating my E6440 BIOS from A05 to A08, then to A13 and A14 (this very day).

 

I think there is something fishy with your own build because I've personally tested (albeit remotely) a Clover installation on another member's E7440 and the laptop never displayed the issues you've encountered (for instance, it can run the VoodooPS2Controller without issue in 10.11.4).

 

Well i am starting to believe this as well now.. 

I started building OSX 10.11.1 on the e6440 using the OCX drive and that worked OK.. got to the setup stage where it asks to set up as a new Mac or restore from a backup or another Mac and that is where i left it. 

 

after updating the e7440 BIOS i thought i would throw the OCX drive into the e7440, and low and behold it booted (in verbose mode) into the OCX drive no kernel panics.  I proceeded to restore the system from the LITEONIT SSD drive (still installed)  and all went well. 

 

I mounted the EFI partitions of bothe the OCX and LITEONIT drives and copied the Clover and Boot Folders from the LITEONIT to the OCX. then shut down. I removed the LITEONIT SSD from the system and voila it booted from the OCX drive without KP (still in Verbose).

 

so i edited the clover config.plist file, removed the -v from the boot string, also checked other things and found the ASUSAICPUPM flag was set in Kernel and Kext Patches.. Since this is a Dell and not an ASUS i set this to No, saved the config.plist and rebooted.. 

 

The system booted normally (no Verbose) no kernel panics either.

 

Mind you it is still 10.11.1  But it is functional

Also no Recovery Partition created (No biggie as these are fairly useless anyway when you have a Clover USB Installer ) 

 

Next step Update to 10.11.4 and see what breaks...

[Hervé]

AsusAICPUPM is Clover's AppleIntelCPUPowerManagement kext on-the-fly patch required for Sandy and Ivy Bridge CPUs. Nothing specific to Asus really, the name is more historical than anything else.

 

But, as you've found out, it's useless on your Haswell platforms. What you require is the kernelPM patch because CPU power management is handled at kernel level on Haswell (and Broadwell) platforms.

[Sorcerer]

Ah thanks for that tidbit of information.. 
i wonder if this is why my system was crashing after wake.. 
time to try before updating to .4

[Sorcerer]

confirmed sleep is functional hoorah!!!

 

at least under 10.11.1

[Sorcerer]

Brilliant.. Updated to 10.11.4 and everything (including Sleep ) is fully functional. 

 

booting of the OCZ Trion 100 500gb SSD and no kernel panics .. 

 

Although still early days yet only had 2 manual shutdown and restarts since the update to .4.. 

 

i will wait a day or two before declaring this a full success. But at the moment all is good.

[Sorcerer]

4 days in and no issues so this thread can be marked as resolved.

 

only issue i am still having is with HDMI audio and Audio in general being intermittently non functional and fresh boot requiring a restart to get audio working. 

 

i will investigate these causes and post a new thread about it if necessary.