-
All replies
-
Helpful answers
-
Oct 6, 2015 2:07 PM in response to kelleyrwby viktor222,i have the same problem - installed el capitan already twice via cmd+r
when restart or shut dow computer - i see only apple logo and empty progress bar.
macbook pro retina late 2012
-
Oct 7, 2015 12:54 PM in response to kelleyrwby ghostpos,★HelpfulHello I have this problem too. 2010 Macbook Pro.
Everything else on El Capitan is fine.
-
Oct 26, 2015 12:22 PM in response to kelleyrwby Jon Clarke,Yep, both my iMac and MacBook Pro crash when I shut down or restart.
I even went to the Apple Store.
They redownloaded the OS and it would restart.
As soon as I updated to 10.11.1 the crashing returned.
I get a grey screen with a stalled progress bar.
-
Nov 8, 2015 11:10 AM in response to Jon Clarkeby wolfak,I could "solve" this problem with the following (something more complicated) procedure:
1.) Log out as user, wait some seconds, the Log In window appears
2.) Choose Shutdown.
Afterwards El Capitan closes as expected.
-
Nov 13, 2015 7:10 AM in response to wolfakby dimitrik_fr,I can confirm that involving Shutdown from the Login screen is avoiding from OSX crash.. -- so, for "normal" activity such a workaround can help. However, it's still impossible to finish any OSX update requiring a reboot (for ex. my upgrade to 10.11.1 from 10.11 never finished as on MBP restart it was always back to the AppStore app proposing me to apply the same Update I've just started before.. So, for 10.11.1 I've just reinstalled the whole OSX from the new Install image (then restore my data from TimeMachine) -- but this was in expectation that 10.11.1 will fix the issue, and it's not the case.. So, have no idea what to do when the next Update will come, as loosing a whole day for reinstall + restore is no more my option ;-))
Rgds,
-Dimitri
-
Nov 15, 2015 2:22 AM in response to dimitrik_frby wolfak,Hi again,
rather coincidentally I have got my perfect solution to our common problem by the newest update (4.4) of my TTS4-Shareware.
When "crashing" I had got an error-hint containing "xpc cache". The above tool now recommends to rebuild the xpc-cache. This is a system cache for interprocess communication.
After rebuilding this cache I can use now all standard shutdown possibilities.
-
Nov 19, 2015 12:34 PM in response to kelleyrwby CC105,I have this problem also. Mac Pro late 2013. I will try the logout first thing, but as previously mentioned this doesn't help much when upgrades come out.
-
Nov 20, 2015 2:42 AM in response to wolfakby dimitrik_fr,Hi,
just tested the "/usr/libexec/xpchelper --rebuild-cache" and this is NOT solving the problem on my MBP..
can do a proper shutdown only after log-out, so the issue remains for me, curious if the proposed fix helped anyone here.
Rgds,
-Dimitri
-
Nov 20, 2015 4:45 AM in response to dimitrik_frby dimitrik_fr,Also, seems like in my case I have a very explicit report about from where the OSX kernel panic is coming :
*** Panic Report ***
panic(cpu 1 caller 0xffffff8017cb47df): "(default pager): [KERNEL]: default memory manager"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3247.10.11/osfmk/default _pager/default_pager.c:421
Backtrace (CPU 1), Frame : Return Address
0xffffff80b1d23db0 : 0xffffff8017ce5307
0xffffff80b1d23e30 : 0xffffff8017cb47df
0xffffff80b1d23e60 : 0xffffff8017cb462b
0xffffff80b1d23e80 : 0xffffff8017d45a31
0xffffff80b1d23ef0 : 0xffffff8018226524
0xffffff80b1d23f10 : 0xffffff8017dc13aa
0xffffff80b1d23fb0 : 0xffffff8017df4b36
so, there is even the line in the source code mentioned where the panic is involved: default_pager.c:421
any feedback from Apple on this?
Rgds,
-Dimitri
-
Nov 20, 2015 6:10 AM in response to dimitrik_frby dimitrik_fr,BTW, what are saying crash reports for other users here reporting crash on shutdown ?..
(curious if the problem is the same for everybody or different)
NOTE: you can find your kernel panic report file within: /Library/Logs/DiagnosticReports
Rgds,
-Dimitri
-
Nov 20, 2015 8:37 AM in response to dimitrik_frby dimitrik_fr,Hi All,
seems like for my case of the kernel panic on shutdown the main trouble was coming from disabled memory compression option I've enabled something like 1.5 year ago.. -- once memory compression enabled back again, no more crash on shutdown/restart! -- pretty surprising for me why such should ever happens on OSX, but this is so..
how to check if you have disabled memory compression :
$ sudo nvram -p | grep boot-args
if you see "vm_compression=1" in the output, then your memory compression is disabled..
to re-enable it again you can :
$ sudo nvram "boot-args=vm_compression=4" and reboot
or reset the whole PRAM with CMD+Opt+P+R on reboot (check the Apple doc for details)..
Rgds,
-Dimitri
-
Nov 21, 2015 7:35 PM in response to dimitrik_frby CC105,same thing for me...
*** Panic Report ***
panic(cpu 6 caller 0xffffff800bab47df): "(default pager): [KERNEL]: default memory manager"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3247.10.11/osfmk/default _pager/default_pager.c:421
Backtrace (CPU 6), Frame : Return Address
0xffffff83c0b3bdb0 : 0xffffff800bae5307
0xffffff83c0b3be30 : 0xffffff800bab47df
0xffffff83c0b3be60 : 0xffffff800bab462b
0xffffff83c0b3be80 : 0xffffff800bb45a31
0xffffff83c0b3bef0 : 0xffffff800c026524
0xffffff83c0b3bf10 : 0xffffff800bbc13aa
0xffffff83c0b3bfb0 : 0xffffff800bbf4b36
-
Nov 21, 2015 7:49 PM in response to CC105by CC105,I did also have memory compression turned off.... vm_compression=1. Seems silly to be using cpu to compress memory when I have 32GB for ideal performance. Anyway, putting it back to vm_compression=4 as mentioned above seems to have cured my crashes as well.
-
Nov 22, 2015 11:21 AM in response to CC105by dimitrik_fr,I'm considering this issue as a pure bug from Apple -- there is no any valid reason why OSX should crash if the memory compression feature is disabled.. -- sounds like a wrong test condition (or just a missed test condition) in the code. Not cool at all to see it from Apple. Very hope this will be fixed soon!
Rgds,
-Dimitri