You are not logged in.
Pages: 1
Hi everyone
my hardware is macbook air 2013 ,
i recently upgraded to osx 10.10 & it upgraded the firmware ( could be the issue ) ,
tried upgrading to 3.17.1 from testing with no luck .
found this in dmesg :
ACPI Warning: SystemIO range 0x000000000000efa0-0x000000000000efbf conflicts with OpRegion 0x000000000000efa0-0x000000000000efaf (\_SB_.PCI0.SBUS.SMBI) (20140724/utaddress-258)
any help is appreciated .
Offline
anyone ??
Offline
I have the same problem. I'm going to try to downgrade the firmware but not sure if that is even possible. I'll keep you posted if I find some way to fix this.
Offline
Seems we're stuck in a loop when searching the ACPI namespace. I'll see if I can patch this.
Offline
I have the same problem. I'm going to try to downgrade the firmware but not sure if that is even possible. I'll keep you posted if I find some way to fix this.
i don't think firmware downgrading is even possible , if it did , then great ,
i am sure the problem started after upgrading to osx 10.10 , so it's a firmware issue ,
tried downgrading to osx 10.8 with no luck , it's seems the problem in the firmware not the os ,
hope someone help .
Offline
Hello!
Disabling the interrupt gpe66 worked for me:
echo disable > /sys/firmware/acpi/interrupts/gpe66
Source: https://bugzilla.kernel.org/show_bug.cgi?id=85881
Hope this helps!
Offline
I'm experiencing the exact same problem. Not sure if it started after installing OS X 10.10 or after the last kernel update. Either way, the solution hfcpereira mentioned seems to be effective.
Offline
Hello!
Disabling the interrupt gpe66 worked for me:
echo disable > /sys/firmware/acpi/interrupts/gpe66
Source: https://bugzilla.kernel.org/show_bug.cgi?id=85881
Hope this helps!
thanks a lot , that did it ,
but i wonder if it's a permanent solution ?
Offline
Thanks! Runs like a clock again.
Offline
yep
the problem comes back after a reboot
have to enter the command again
Offline
Pages: 1