Jump to content

[KP][SLEEP][SOLUTION][AppleACPIPlatform] ASUS - Fan Issue! BT & USB


3 posts in this topic

Recommended Posts

Guys today I discovered something and I feel obligated to share it with you. I hope that won't be 'rediscovering' and reposting the issue. :-)

Some of you may have problems with Clover and sleep and have KP on wake. KP which looks like:

Sat Jul  6 23:45:46 2013
panic(cpu 0 caller 0xffffff80002b7e95): Kernel trap at 0xffffff7f81ba7dc3, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x000000010d6ea120, CR3: 0x000000000782c000, CR4: 0x00000000000606e0
[...]
RFL: 0x0000000000010206, RIP: 0xffffff7f81ba7dc3, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x000000010d6ea120, Error code: 0x0000000000000000, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address
0xffffff80e457b780 : 0xffffff800021d626 
[...]
0xffffff80e457bfb0 : 0xffffff80002b2977 
      Kernel Extensions in backtrace:
         com.apple.driver.AppleACPIPlatform(1.7)[D49DC2E0-97DF-32E6-A8ED-7A12EF1AA51B]@0xffffff7f81b88000->0xffffff7f81be5fff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[A35915E8-C1B0-3C0F-81DF-5515BC9002FC]@0xffffff7f80e25000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f80844000

May be caused by... FANS... On my Asus P8Z68-V/GEN3 it can cause the issue for sure. 

 

About the case:

Today I decided to clean up my case and i reconnected fan cables but I did it a bit differently as one of the sockets seemed to be not responding to PWM signals. - both on windows and os x. All of the fans -  except for the CPU fan - are 3pin fans. I have on my mobo 3pin and 4pin sockets. For begginers 3pin fans have PWM control and 4pin fans have PWM and VR control. I thought that I can connect 3pin fan to 4pin socket as it was working pretty well and the 4pin socket was responding to PWM signals but... I couldn't wake my PC! I got KP as above.

I spend last 2 hours trying to figure out what happened as I performed some other changes at the same time - stupid me...

When I disconnected all the Fans the problem was gone!

The problem must be the Apple kext that doesn't allow to connect to the socket that supports VR a fan that doesn't support it. Or maybe it's just a bug.

 

Anyway I hope it will be another solution for 0xffffff80002b7e95 KP. 

Link to comment
Share on other sites

Little update on how to fix it.

Just connecting fans into another ports doesn't fix the issue, it's not that simple.

To get the problem I only needed to connect 3pi fan into 4pin socket but to get rid of it connecting it back to 3pin socket does nothing.

I needed to clear NVRAM and run KextUtility... All of this is quite strange to me. It feels not logical that fans can cause such trouble.

 

It would be gr8 if anyone can test if the issue will show up if he perform those fan reconnecting.

Link to comment
Share on other sites

Sorry for the long post but I messed up a bit. If you don't like reading just skip to the last paragraph.

 

First of all I must admit that I was wrong. 

I was thinking about how illogically my idea must have sounded and I started further investigation.

 

The steps below helped indeed but the fans wasn't the cause of the problems. After I posted the solution here I plugged back all my external devices. I got some errors from USB bus so I decided to rebuild the kextcache. The problem got back.

 

Then I figured out new cause of the problems which was a mistake as well. I found some errors in Console about USB bus errors and some stuff about enumerating the devices. It was related to Kinect for XBOX 360 and my USB Hub, that I connected along with cleaning my case, which - as far as I remember - was incompatible with Lion. - that's why I stopped using it in the first place few months ago.

 

After removing usb hub and kinect I restarted my OS X few times, in a mean time rebuild kextcache AND removed Firmware.scap also booted into Windows to get back my BT to life. With all of those step performed in random order my system got back to work. 

 

As I had working system I decided to update AppleIntelE1000e.kext to check if I can bring my WoL ability back to life. So update of kextcache and kexts permissions and... again. The problem got back!  This time I was sure it is something I just don't see(I rolled back the kext in the first place ofc). I shut down my PC and went to sleep.

 

This morning I had a Revelation. I turned on my hMac and the BT WAS ON! As it doesn't have to be obvious:

On my mobo I had BT working ONLY if I booted into Windows in the first place and than using restart booted into Mac - so that Mac can use firmware already loaded into BT by Windows. My BT Firmware was loaded but by Mac! In the /EFI/Apple/Extensions I had new Firmware.scap. I removed that s**t again and rebooted into windows. Than I shut down PC from windows so that I was sure that firmware was unloaded and got back to Mac. This time BT was off.

I rebuild kextcache one more time and finally it is working and I know why it wasn't. I just don't know what causes the system to load the firmware and - what's more important - how the hell it created the firmware image! I heard that Clover doesn't care about /EFI/Apple/Extensions/Firmware.scap file... Maybe it came from another source? 

 

PS. Is there anyone that can explain it to me or have any kind of theory what could have happened?

Link to comment
Share on other sites

 Share

×
×
  • Create New...