Jump to content

shutdown troubles - reboots instead

sailor25462

By sailor25462,
in OSx86 10.10 (Yosemite)

 Share
122 posts in this topic

Recommended Posts

sailor25462
sailor25462
Posted
Posted

Hi All,

 

I hope someone can help me to sort out one of the last "itches" I have with my installation.

My problem is that the system will not shutdown completely, but only reboot.

 

My setup is as follows:

 

Gigabyte z68ap-d3 rev.2 board with i5-2500

UEFI Bios (UA9) with clover 2795 (which was proposed to use with yosemite for the time being?)

nvidia GT640, intel graphics HD 3000 activated

yosemite public beta 2

 

clover config :

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>ACPI</key>
	<dict>
		<key>DSDT</key>
		<dict>
			<key>Debug</key>
			<false/>
			<key>DropOEM_DSM</key>
			<dict>
				<key>ATI</key>
				<false/>
				<key>Firewire</key>
				<false/>
				<key>HDA</key>
				<false/>
				<key>HDMI</key>
				<false/>
				<key>IDE</key>
				<false/>
				<key>IntelGFX</key>
				<false/>
				<key>LAN</key>
				<true/>
				<key>LPC</key>
				<false/>
				<key>NVidia</key>
				<false/>
				<key>SATA</key>
				<false/>
				<key>SmBUS</key>
				<false/>
				<key>USB</key>
				<false/>
				<key>WIFI</key>
				<false/>
			</dict>
			<key>Fixes</key>
			<dict>
				<key>AddHDMI_8000000</key>
				<true/>
				<key>FixDisplay_0100</key>
				<true/>
				<key>FixHDA_8000</key>
				<true/>
				<key>FixUSB_1000</key>
				<true/>
			</dict>
			<key>ReuseFFFF</key>
			<false/>
		</dict>
		<key>SSDT</key>
		<dict>
			<key>DropOem</key>
			<false/>
			<key>EnableC6</key>
			<true/>
			<key>Generate</key>
			<dict>
				<key>CStates</key>
				<true/>
				<key>PStates</key>
				<true/>
			</dict>
		</dict>
	</dict>
	<key>Boot</key>
	<dict>
		<key>Arguments</key>
		<string>-v kext-dev-mode=1</string>
		<key>DefaultVolume</key>
		<string>OS X</string>
		<key>Legacy</key>
		<string>PBR</string>
		<key>Log</key>
		<false/>
		<key>Secure</key>
		<false/>
		<key>Timeout</key>
		<integer>5</integer>
		<key>XMPDetection</key>
		<false/>
	</dict>
	<key>CPU</key>
	<dict>
		<key>FrequencyMHz</key>
		<integer>3800</integer>
	</dict>
	<key>Devices</key>
	<dict>
		<key>Audio</key>
		<dict>
			<key>Inject</key>
			<string>1</string>
			<key>ResetHDA</key>
			<true/>
		</dict>
		<key>FakeID</key>
		<dict>
			<key>ATI</key>
			<string>0x0</string>
			<key>IMEI</key>
			<string>0x0</string>
			<key>IntelGFX</key>
			<string>0x0</string>
			<key>LAN</key>
			<string>0x0</string>
			<key>NVidia</key>
			<string>0x0</string>
			<key>SATA</key>
			<string>0x0</string>
			<key>WIFI</key>
			<string>0x0</string>
			<key>XHCI</key>
			<string>0x0</string>
		</dict>
		<key>USB</key>
		<dict>
			<key>AddClockID</key>
			<true/>
			<key>FixOwnership</key>
			<false/>
			<key>HighCurrent</key>
			<true/>
			<key>Inject</key>
			<true/>
		</dict>
		<key>UseIntelHDMI</key>
		<true/>
	</dict>
	<key>DisableDrivers</key>
	<array>
		<string>Nothing</string>
	</array>
	<key>GUI</key>
	<dict>
		<key>Hide</key>
		<array>
			<string>\EFI\BOOT\BOOTX64.EFI</string>
			<string>Windows</string>
		</array>
		<key>Language</key>
		<string>de:0</string>
		<key>Mouse</key>
		<dict>
			<key>Enabled</key>
			<false/>
			<key>Mirror</key>
			<false/>
			<key>Speed</key>
			<integer>8</integer>
		</dict>
		<key>Scan</key>
		<dict>
			<key>Entries</key>
			<true/>
			<key>Legacy</key>
			<string>First</string>
			<key>Tool</key>
			<true/>
		</dict>
		<key>ScreenResolution</key>
		<string>1680x1050</string>
		<key>Theme</key>
		<string>bootcamp</string>
	</dict>
	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>
	</dict>
	<key>KernelAndKextPatches</key>
	<dict>
		<key>AppleRTC</key>
		<true/>
		<key>AsusAICPUPM</key>
		<true/>
		<key>KernelPm</key>
		<true/>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>t1-10.9/AppleHDA/Realtek ALC889</string>
				<key>Find</key>
				<data>
				ixnUEQ==
				</data>
				<key>Name</key>
				<string>AppleHDA</string>
				<key>Replace</key>
				<data>
				iQjsEA==
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>t1-10.9/AppleHDA/Resources/xml>zml</string>
				<key>Find</key>
				<data>
				eG1sLnps
				</data>
				<key>Name</key>
				<string>AppleHDA</string>
				<key>Replace</key>
				<data>
				em1sLnps
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>External icons patch</string>
				<key>Find</key>
				<data>
				RXh0ZXJuYWw=
				</data>
				<key>Name</key>
				<string>AppleAHCIPort</string>
				<key>Replace</key>
				<data>
				SW50ZXJuYWw=
				</data>
			</dict>
		</array>
	</dict>
	<key>RtVariables</key>
	<dict>
		<key>LogLineCount</key>
		<integer>3000</integer>
	</dict>
	<key>SMBIOS</key>
	<dict>
		<key>BiosReleaseDate</key>
		<string>09/04/2012</string>
		<key>BiosVendor</key>
		<string>Apple Inc.</string>
		<key>BiosVersion</key>
		<string>IM131.88Z.010A.B05.1209042338</string>
		<key>Board-ID</key>
		<string>Mac-00BE6ED71E35EB86</string>
		<key>BoardManufacturer</key>
		<string>Apple Inc.</string>
		<key>BoardType</key>
		<integer>10</integer>
		<key>ChassisAssetTag</key>
		<string>iMac-Aluminum</string>
		<key>ChassisManufacturer</key>
		<string>Apple Inc.</string>
		<key>ChassisType</key>
		<string>13</string>
		<key>Family</key>
		<string>iMac</string>
		<key>Manufacturer</key>
		<string>Apple Inc.</string>
		<key>Mobile</key>
		<false/>
		<key>ProductName</key>
		<string>iMac13,1</string>
		<key>SerialNumber</key>
		<string>############</string>
		<key>SmUUID</key>
		<string>########-####-####-####-############</string>
		<key>Trust</key>
		<false/>
		<key>Version</key>
		<string>1.0</string>
	</dict>
	<key>SystemParameters</key>
	<dict>
		<key>CustomUUID</key>
		<string>########-####-####-####-############</string>
		<key>InjectKexts</key>
		<string>Yes</string>
		<key>InjectSystemID</key>
		<true/>
		<key>NoCaches</key>
		<false/>
	</dict>
</dict>
</plist>

Shutdown under Mavericks worked well, even sleep did as told (of course with exception of USB 3 attached devices like my time machine external HDD)

 

I was playing a bit with clover options, i.e. tried halt enabler, shutdown fix, but no luck.

 

So, I'm a bit stuck here and need some kind advice!

Link to comment
Share on other sites
alexanderq
alexanderq
Posted
Posted
 
 

You can try this setings

<key>Fixes</key>
<dict>
        <key>FixShutdown_0004</key>
        <true/>
</dict>

or

<key>SlpSmiAtWake</key>
<true>

It adds SLP_SMI_EN=0 at every wake. It may help solve sleep and shutdown issues on UEFI boot.

 

but please read clover wiki  http://clover-wiki.zetam.org/Home

it may help you solve a lot of problems and clean your config.plist a bit.

 

  • Like 1
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

Well, this fixed it for me. Finally!  I got sick of shutting down my computer using the power button, cause it was always going into reboot instead of shutdown. But...I had to have both activated. I had FixShutdown set to true for the longest time. And my computer was going into reboot 99.99% of the times, even though I was always selecting Shut Down option in the menu. I don't quite understand this... Is this a bug in Clover? Isn't the first option supposed to fix the Shutdown and the second one supposed to fix the Sleep issues? Why do I have to have both selected? Or ...do I? Cause if I don't, it means that FixShutdown doesn't actually fix anything and SlpSmiAtWake actually fixes both.

 

Update1: I didn't have these issues in Mavericks. So if this has something to do with Clover (and it seems like it does), it applies only to Yosemite.

Update2: It's still going into reboot from time to time...

Link to comment
Share on other sites
sailor25462
sailor25462
Posted
  • Author
Posted

 

 
 

You can try this setings

<key>Fixes</key>

<dict>

        <key>FixShutdown_0004</key>

        <true/>

</dict>

or

<key>SlpSmiAtWake</key>

<true>

It adds SLP_SMI_EN=0 at every wake. It may help solve sleep and shutdown issues on UEFI boot.

 

Thanks' a lot for your support and input on this issue! I really appreciate it.

 

Actually I had tried those options already, but just to double check I went through all possible combinations again. Tried to run with none of them, both of them and each of them.

However, no luck, it still reboots instead of shutting down completely.

 

 

but please read clover wiki  http://clover-wiki.zetam.org/Home

it may help you solve a lot of problems

 

Believe me, I have read the clover wiki up and down, but frankly speaking, comments like :

  • FixSBUS_0080

    Adds SMBUS device into DSDT, with some sub-device. I don't know the reason for the patch but it's advised in many forums. Never seen any problem with this bit.

really don't help to build confidence...  :angel_not:

You may of course call this a "bad" example, I know, but from a certain point you just feel a bit lost in space at times.

But isn't this the point were the community comes in?

 

Anyway, what wonders me is the fact that it all used to work perfectly well under Mavericks and even under Yosemite's first public beta. Only after the update to beta 2, all this started to go down the river. 

Makes me guess something has changed with this version, which is not yet handled by clover in an appropriate way?

 

If I knew were to start having a deeper look into it, I'd certainly do, but I'm afraid I'll need some guidance though this. So any advice will be highly welcome.

I'd just be surprised if I'm the only one having this strange behaviour, unless this is something specific related to the z68ap-d3 rev.2 board with UEFI boot?

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

Since I posted the same issue above, no, you're not the only one having it. And your mobo is definitely not the only one with this issue (assuming it's something motherboard related).

 

I also don't have it with Mavericks. But, if I remember correctly, I did encounter it with PB1, as well. So I can't really confirm that.... Anyway, for as far as I understood, this kind of behavior is really hard to debug, especially since not many seems to have it. So maybe that's why not many people are offering their support here.

 

Anyway, if it is an issue with PB2 only, I think the best way would be to wait for the final version to be released. Which should be pretty soon.

Link to comment
Share on other sites
sailor25462
sailor25462
Posted
  • Author
Posted

You're right, best will be to wait for the final. Either it will go away by itself, or others will run into this soon.

 

While you say you did have this also under beta 1, frankly if someone would put me on a lie detector, I'm not sure if I would pass...  B)  Maybe I just didn't realise?

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

lol I don't know, man... Maybe. I know I had this issues for a very long time. And it's annoying as hell! Every time I have to shut down my computer using the power button.

 

I also tried shutting down from command line

sudo shutdown -h now
[password]

No success, in my particular case. What is really weird is that, once in a blue moon, it DOES shut down properly. But it's so rare and so hard to predict that I wouldn't call it an accomplishment.

  • Like 1
Link to comment
Share on other sites
sailor25462
sailor25462
Posted
  • Author
Posted

 

 

What is really weird is that once in a blue moon, it DOES shut down properly. But it's so rare and so hard to predict that I wouldn't call it an accomplishment.

 

Now that you say it, yes I can confirm this too. It did during my fiddling with the clover config, maybe twice in total.... But even without changing anything then, next shutdown turned bad again.

So, even if it worked, it wasn't stable at all.

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

Now that you say it, yes I can confirm this too. It did during my fiddling with the clover config, maybe twice in total.... But even without changing anything then, next shutdown turned bad again.

So, even if it worked, it wasn't stable at all.

Yep, it's really weird. I don't believe in random. I'm pretty sure there is no such thing. But this thing is really hard to reproduce. At first I thought it might be because I have some apps running in background when I turn off my computer. So, I tried to quit all the apps and then shut down. It went into Reboot instead. Other times I tried to shut down without waiting for any apps to load or opening any apps myself. Same result. It's a hit and miss situation. Mostly miss.

 

Actually, today, just about 3 shutdowns (aka reboots) before, I got a real shutdown. But I'm still not sure if this is something that happens once in X tries. I will try to keep track of successful shutdowns vs failed ones. Maybe there is a ratio somewhere... God knows what the hell is triggering this to work or not work at a given time.

Link to comment
Share on other sites
sailor25462
sailor25462
Posted
  • Author
Posted

I found this post: http://forum.osdev.org/viewtopic.php?t=16990 when lurking around the web to find a hint.

 

 

 

The ACPI shutdown is technically a really simple thing all that is needed is a outw(PM1a_CNT, SLP_TYPa | SLP_EN ); and the computer is powered off. 
The problem lies in the gathering of these values especialy since the SLP_TYPa is in the \_S5 object which is in the DSDT and therefore AML encoded.

 

I'm really not deep in ACPI things to rate the relevance of it, but what I understand is that if the reading of the DSDT info is not working properly, the necessary ACPI command might fail.

Actually, since using UEFI bios for my board, I don't use a specific DSDT file. Does this make some potential starter for a research?

  • Like 1
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

I found this post: http://forum.osdev.org/viewtopic.php?t=16990 when lurking around the web to find a hint.

 

 

I'm really not deep in ACPI things to rate the relevance of it, but what I understand is that if the reading of the DSDT info is not working properly, the necessary ACPI command might fail.

Actually, since using UEFI bios for my board, I don't use a specific DSDT file. Does this make some potential starter for a research?

I don't use a modded DSDT file either. Just Clover's patching on the fly.

 

To me, that page looks like klingon. Pretty in its own way, but really hard to understand.

 

I just wanted to point out that I, on another hand, tried to keep track of that ratio I mentioned above. And, just 2 shutdowns before, I had another successful reboot. So far the ratio seems to be around 1/7 (1 success, 6 fails). I'm still trying. And...if I remember correctly, the last successful one, was also about 5-6 reboots before. So...so far, it looks consistent. But I need to investigate more.

Link to comment
Share on other sites
sailor25462
sailor25462
Posted
  • Author
Posted (edited)

I was again playing around with the settings and - tattooer - I found one setup which has caused a proper shutdown (twice now).

 

Check this out:

<key>ACPI</key>
	<dict>
		<key>DSDT</key>
		<dict>
			<key>Debug</key>
			<false/>
			<key>DropOEM_DSM</key>
			<true/>
			<key>Fixes</key>
			<dict>
				<key>AddHDMI_8000000</key>
				<true/>
				<key>FIX_S3D_2000000</key>
				<true/>
				<key>FixDarwin_0002</key>
				<true/>
				<key>FixDisplay_0100</key>
				<true/>
				<key>FixFirewire_0800</key>
				<true/>
				<key>FixHDA_8000</key>
				<true/>
				<key>FixShutdown_0004</key>
				<true/>
				<key>FixUSB_1000</key>
				<true/>
			</dict>
			<key>ReuseFFFF</key>
			<false/>
			<key>SlpSmiAtWake</key>
			<true/>
			<key>SuspendOverride</key>
			<true/>
		</dict>
		<key>HaltEnabler</key>
		<true/>
		<key>SSDT</key>
		<dict>
			<key>DropOem</key>
			<false/>
			<key>EnableC6</key>
			<true/>
			<key>Generate</key>
			<dict>
				<key>CStates</key>
				<true/>
				<key>PStates</key>
				<true/>
			</dict>
		</dict>
	</dict>

as well as 

<key>USB</key>
		<dict>
			<key>AddClockID</key>
			<true/>
			<key>FixOwnership</key>
			<true/>
			<key>HighCurrent</key>
			<true/>
			<key>Inject</key>
			<true/>
		</dict>

Basically I added the 

 

FIX_S3D_2000000

FixDarwin_0002
FixFirewire_0800 (I have a firewire card inserted, so I thought it might help as well)

 

and finally the USB

 

FixOwnership

 

I'm pretty sure that not all of them are necessary, but will try to sort out by taking each away and see what happens over the time.

 

Let me know if this changes anything on your setup!

 

 

Edit: Removed the S3D fix and ended up with reboot again. Re-applied S3d and it's shutting down properly. 

Edited by sailor25462
  • Like 1
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

I was again playing around with the settings and - tattooer - I found one setup which has caused a proper shutdown (twice now).

 

Check this out:

<key>ACPI</key>
	<dict>
		<key>DSDT</key>
		<dict>
			<key>Debug</key>
			<false/>
			<key>DropOEM_DSM</key>
			<true/>
			<key>Fixes</key>
			<dict>
				<key>AddHDMI_8000000</key>
				<true/>
				<key>FIX_S3D_2000000</key>
				<true/>
				<key>FixDarwin_0002</key>
				<true/>
				<key>FixDisplay_0100</key>
				<true/>
				<key>FixFirewire_0800</key>
				<true/>
				<key>FixHDA_8000</key>
				<true/>
				<key>FixShutdown_0004</key>
				<true/>
				<key>FixUSB_1000</key>
				<true/>
			</dict>
			<key>ReuseFFFF</key>
			<false/>
			<key>SlpSmiAtWake</key>
			<true/>
			<key>SuspendOverride</key>
			<true/>
		</dict>
		<key>HaltEnabler</key>
		<true/>
		<key>SSDT</key>
		<dict>
			<key>DropOem</key>
			<false/>
			<key>EnableC6</key>
			<true/>
			<key>Generate</key>
			<dict>
				<key>CStates</key>
				<true/>
				<key>PStates</key>
				<true/>
			</dict>
		</dict>
	</dict>

as well as 

<key>USB</key>
		<dict>
			<key>AddClockID</key>
			<true/>
			<key>FixOwnership</key>
			<true/>
			<key>HighCurrent</key>
			<true/>
			<key>Inject</key>
			<true/>
		</dict>

Basically I added the 

 

FIX_S3D_2000000

FixDarwin_0002

FixFirewire_0800 (I have a firewire card inserted, so I thought it might help as well)

 

and finally the USB

 

FixOwnership

 

I'm pretty sure that not all of them are necessary, but will try to sort out by taking each away and see what happens over the time.

 

Let me know if this changes anything on your setup!

 

 

Edit: Removed the S3D fix and ended up with reboot again. Re-applied S3d and it's shutting down properly. 

Unfortunately that didn't change anything for me. I already had all those fixes in place and...no change.

Link to comment
Share on other sites
  • 4 weeks later...
arsradu
arsradu
Posted
Posted

Actually, my shutdown seemed to have improved a lot. But after a few cycles, it appears that it reboots again now. I haven't changed anything at all!

Hey, man

 

Are you using Chrome as browser? If so, let's try the following scenario:

 

1. Update to Clover 2953 (not sure it's got anything to do with this but it wouldn't hurt anyway)

2. Each time you want to shut down your computer, remember to close Chrome using the X button on the browser window.

3. Shut down your computer using the Apple Menu -> Shut Down... -> CLICK the Shut Down button on the pop-up window. (It would probably be the same if you just press the Enter key on your keyboard. But...just for the sake of it, let's try with mouse click on the Shut Down button.)

 

So far...I got all the shutdowns (5 so far) to be successful using this method. I'm thinking it might be something related to the opened apps after all, that keeps the computer from shutting down completely.

 

If you've got the time to try this, I would really appreciate your feedback. :)

 

By the way, I'm using Yosemite PB5 now (latest public beta). I'm not sure it makes any difference, but just so you know.

Link to comment
Share on other sites
sailor25462
sailor25462
Posted
  • Author
Posted

Hey, man

 

Are you using Chrome as browser? If so, let's try the following scenario:

 

1. Update to Clover 2953 (not sure it's got anything to do with this but it wouldn't hurt anyway)

2. Each time you want to shut down your computer, remember to close Chrome using the X button on the browser window.

3. Shut down your computer using the Apple Menu -> Shut Down... -> CLICK the Shut Down button on the pop-up window. (It would probably be the same if you just press the Enter key on your keyboard. But...just for the sake of it, let's try with mouse click on the Shut Down button.)

 

So far...I got all the shutdowns (5 so far) to be successful using this method. I'm thinking it might be something related to the opened apps after all, that keeps the computer from shutting down completely.

 

If you've got the time to try this, I would really appreciate your feedback. :)

 

By the way, I'm using Yosemite PB5 now (latest public beta). I'm not sure it makes any difference, but just so you know.

 

First of all I'm happy to hear you seem to have moved forward in this mystic issue.

 

After I read your post, I closed all open apps, however, chrome was already closed (completely). I gave the shutdown a try and - hey - it turned off completely. Now that was promising I thought, although it used to happen every now and then already.

 

Then I started again, shutdown immediately after finishing the startup, without having chrome even started, I made sure all apps were closed though. Damn, no shutdown but again only a restart. Surprisingly to me, this time it even broke during the next boot and restarted even before it finished. The after the 2nd boot, it completed. I didn't have a verbose boot, so I couldn't see why or at least at which point the boot process crashed.

 

I then updated clover to the newest version. Tried again, but still it reboots. So it seems I cannot duplicate your finding :-(

Frankly speaking, I would have been very surprised if a normal app like chrome would have such an impact on the shutdown...

 

In any case I find it promising that you got a 5 times shutdown success. Maybe it's a good start from there to see and compare all (clover) settings and running services in the background?

 

Maybe just another thought: Could this be related to any left overs from previous hibernate/sleep attempts?

To me it seems that if certain properties are not "cleared", it may do this reboot till - form time to time - those properties are cleared by another mechanism?

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

First of all I'm happy to hear you seem to have moved forward in this mystic issue.

 

After I read your post, I closed all open apps, however, chrome was already closed (completely). I gave the shutdown a try and - hey - it turned off completely. Now that was promising I thought, although it used to happen every now and then already.

 

Then I started again, shutdown immediately after finishing the startup, without having chrome even started, I made sure all apps were closed though. Damn, no shutdown but again only a restart. Surprisingly to me, this time it even broke during the next boot and restarted even before it finished. The after the 2nd boot, it completed. I didn't have a verbose boot, so I couldn't see why or at least at which point the boot process crashed.

 

I then updated clover to the newest version. Tried again, but still it reboots. So it seems I cannot duplicate your finding :-(

Frankly speaking, I would have been very surprised if a normal app like chrome would have such an impact on the shutdown...

 

In any case I find it promising that you got a 5 times shutdown success. Maybe it's a good start from there to see and compare all (clover) settings and running services in the background?

 

Maybe just another thought: Could this be related to any left overs from previous hibernate/sleep attempts?

To me it seems that if certain properties are not "cleared", it may do this reboot till - form time to time - those properties are cleared by another mechanism?

You know, I'm pretty sure that what you just said might sound alien to anyone else, but to me, it doesn't. It might be something to it.

 

Anyway, about Chrome, I tried to just start up the computer and shut it down shortly after that before. That did not work. So don't go that way.

 

Just start up your computer, open up Chrome, press the X button to close it (I don't think it will shut it down completely, like when you Quit the program, but that's irrelevant right now), shut down the computer using your mouse, not the keyboard. I also had other apps running in the background in my previous tests, like Mail, Safari, VLC, iMessage, but closing Chrome this way was the only thing that had any effect (so far) to the shutdown/restart issue.

 

To me, it's not that hard to believe that a third party app, like Chrome, can cause this kind of issues. Because the system tries to close everything up before shutting down completely. And if it can't, it might trigger a restart instead so that you shut down that process manually. So...I'm not sure it's a Chrome issue (maybe the app has some bugs or Yosemite has some bugs when it comes to Chrome's processes or something). It might be Yosemite's + motherboard + God knows what else, otherwise everyone using Chrome and not closing it properly, would have the same issues.

 

So, I don't know if it's just Chrome or Chrome + other stuff. But I'm continuing my investigation.

 

If you wanna give the thing I told you above another try, please, let me know your results. Don't try just start up + shut down. That rarely worked for me, even though Chrome is not even started. Let's see if this: startup + open Chrome + close Chrome from the X button + shutting down computer using only the mouse, has any effect. If not...we'll keep digging.

5 complete shutdowns in a row is good and I don't think it was a coincidence. But there are plenty of variables to exclude before reaching a final decision. And I'm willing to try. I've got no other solution so far. So...I don't see why not. :)

 

Update: make that 6 successful shutdowns in a row. :D

Link to comment
Share on other sites
sailor25462
sailor25462
Posted
  • Author
Posted

You know, I'm pretty sure that what you just said might sound alien to anyone else, but to me, it doesn't. It might be something to it.

 

Anyway, about Chrome, I tried to just start up the computer and shut it down shortly after that before. That did not work. So don't go that way.

 

Just start up your computer, open up Chrome, press the X button to close it (I don't think it will shut it down completely, like when you Quit the program, but that's irrelevant right now), shut down the computer using your mouse, not the keyboard. I also had other apps running in the background in my previous tests, like Mail, Safari, VLC, iMessage, but closing Chrome this way was the only thing that had any effect (so far) to the shutdown/restart issue.

 

To me, it's not that hard to believe that a third party app, like Chrome, can cause this kind of issues. Because the system tries to close everything up before shutting down completely. And if it can't, it might trigger a restart instead so that you shut down that process manually. So...I'm not sure it's a Chrome issue (maybe the app has some bugs or Yosemite has some bugs when it comes to Chrome's processes or something). It might be Yosemite's + motherboard + God knows what else, otherwise everyone using Chrome and not closing it properly, would have the same issues.

 

So, I don't know if it's just Chrome or Chrome + other stuff. But I'm continuing my investigation.

 

If you wanna give the thing I told you above another try, please, let me know your results. Don't try just start up + shut down. That rarely worked for me, even though Chrome is not even started. Let's see if this: startup + open Chrome + close Chrome from the X button + shutting down computer using only the mouse, has any effect. If not...we'll keep digging.

5 complete shutdowns in a row is good and I don't think it was a coincidence. But there are plenty of variables to exclude before reaching a final decision. And I'm willing to try. I've got no other solution so far. So...I don't see why not. :)

 

Update: make that 6 successful shutdowns in a row. :D

 

I tried it exactly the way you proposed. Twice. One time with re-open all sessions and once without. Same result - it just reboots.

 

Just before you shutdown. If you open your terminal and type ps -A, can you post what's running at that time?

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

I tried it exactly the way you proposed. Twice. One time with re-open all sessions and once without. Same result - it just reboots.

 

Just before you shutdown. If you open your terminal and type ps -A, can you post what's running at that time?

Do you have it set to reopen all windows when logging back in? Cause I don't... I unchecked that the first time I shut down my computer (you can check out the attached screenshot for more details on what I'm talking about). I don't like that feature. I don't always open up the same things so I don't like to wait for everything to be reopened every time I start up my computer... Anyway, maybe that's just me.

 

About the stuff it's running right now, sure, you can see it below. Please, note that I'm trying to see if it's really something related to Chrome or something related to the sessions (being shut down successfully or not). And for that, in this log you're not gonna find Chrome. Since it's not started. But I do have Opera on, along with some other apps.

Last login: Sun Oct 12 21:16:39 on console
192-168-0-103:~ radu$ ps -A
  PID TTY           TIME CMD
    1 ??         0:02.20 /sbin/launchd
   18 ??         0:00.42 /usr/libexec/UserEventAgent (System)
   19 ??         0:00.37 /usr/sbin/syslogd
   21 ??         0:00.33 /usr/libexec/kextd
   22 ??         0:01.05 /System/Library/Frameworks/CoreServices.framework/Vers
   24 ??         0:00.01 /usr/libexec/thermald
   26 ??         0:00.06 /System/Library/CoreServices/appleeventsd --server
   27 ??         0:00.93 /usr/libexec/configd
   28 ??         0:00.26 /System/Library/CoreServices/powerd.bundle/powerd
   31 ??         0:00.02 /usr/libexec/airportd
   33 ??         0:00.05 /usr/libexec/warmd
   34 ??         0:03.36 /System/Library/Frameworks/CoreServices.framework/Fram
   38 ??         0:00.02 /System/Library/CoreServices/iconservicesd
   39 ??         0:00.01 /System/Library/CoreServices/iconservicesagent
   40 ??         0:00.07 /usr/libexec/diskarbitrationd
   43 ??         0:00.32 /usr/libexec/coreduetd
   44 ??         0:00.01 /usr/libexec/wdhelper
   46 ??         0:00.03 /System/Library/PrivateFrameworks/WirelessDiagnostics.
   47 ??         0:01.44 /usr/libexec/opendirectoryd
   48 ??         0:00.03 /usr/sbin/wirelessproxd
   50 ??         0:00.18 /usr/libexec/discoveryd --udsocket standard --loglevel
   51 ??         0:00.30 /System/Library/PrivateFrameworks/ApplePushService.fra
   52 ??         0:00.54 /System/Library/CoreServices/launchservicesd
   53 ??         0:00.02 /System/Library/PrivateFrameworks/MobileDevice.framewo
   54 ??         0:00.57 /usr/sbin/securityd -i
   59 ??         0:00.04 /usr/sbin/blued
   60 ??         0:00.01 autofsd
   61 ??         0:00.01 /bin/bash /Library/Application Support/Clover/CloverDa
   65 ??         0:00.01 /usr/libexec/stackshot -t -O
   66 ??         0:00.04 /System/Library/PrivateFrameworks/GenerationalStorage.
   67 ??         0:00.73 /System/Library/CoreServices/loginwindow.app/Contents/
   68 ??         0:00.01 /System/Library/CoreServices/logind
   69 ??         0:00.00 /usr/sbin/KernelEventAgent
   71 ??         0:00.01 /usr/libexec/hidd
   72 ??         0:02.87 /usr/sbin/notifyd
   73 ??         0:00.66 /usr/libexec/taskgated -s
   75 ??         0:00.44 /usr/sbin/distnoted daemon
   78 ??         0:00.12 /System/Library/Frameworks/Security.framework/Versions
   79 ??         0:02.54 /System/Library/CoreServices/coreservicesd
   82 ??         0:00.54 /usr/sbin/cfprefsd daemon
  103 ??         0:00.01 /usr/libexec/diagnosticd
  158 ??         0:00.00 sleep 86400
  162 ??         0:00.07 /usr/libexec/watchdogd
  175 ??         0:00.01 /System/Library/Frameworks/PCSC.framework/Versions/A/X
  177 ??         0:43.61 /System/Library/Frameworks/ApplicationServices.framewo
  178 ??         0:00.01 /System/Library/Frameworks/CryptoTokenKit.framework/ct
  179 ??         0:00.02 /usr/libexec/secinitd
  188 ??         0:00.00 /usr/libexec/discoveryd_helper --loglevel Detailed --l
  189 ??         0:00.11 /usr/libexec/networkd
  190 ??         0:00.02 /usr/libexec/nsurlsessiond --privileged
  191 ??         0:00.10 /usr/libexec/nehelper
  192 ??         0:00.06 /usr/libexec/usbd
  193 ??         0:00.01 /System/Library/CryptoTokenKit/com.apple.ifdreader.slo
  194 ??         0:00.06 sysmond
  195 ??         0:00.01 /usr/libexec/networkd_privileged
  196 ??         0:00.16 /usr/sbin/ntpd -c /private/etc/ntp-restrict.conf -n -g
  197 ??         0:01.38 /usr/libexec/ApplicationFirewall/socketfilterfw
  200 ??         0:01.61 /System/Library/Frameworks/CoreServices.framework/Fram
  215 ??         0:00.05 /System/Library/Frameworks/OpenGL.framework/Versions/A
  217 ??         0:00.03 /System/Library/PrivateFrameworks/AmbientDisplay.frame
  225 ??         0:00.03 /System/Library/Frameworks/Security.framework/Versions
  233 ??         0:00.01 /System/Library/PrivateFrameworks/AccountPolicy.framew
  235 ??         0:00.02 /System/Library/PrivateFrameworks/TCC.framework/Resour
  245 ??         0:00.02 /usr/sbin/netbiosd
  246 ??         0:00.04 /usr/libexec/findmydeviced
  247 ??         0:00.09 /usr/libexec/locationd
  248 ??         0:06.04 /System/Library/CoreServices/Software Update.app/Conte
  249 ??         0:00.04 /System/Library/PrivateFrameworks/SoftwareUpdate.frame
  254 ??         0:00.07 /usr/libexec/securityd_service
  255 ??         0:00.21 /usr/libexec/UserEventAgent (Aqua)
  257 ??         0:00.25 /usr/sbin/distnoted agent
  259 ??         0:00.89 /usr/sbin/cfprefsd agent
  260 ??         0:00.07 /usr/libexec/sandboxd -n PluginProcess -n 
  261 ??         0:00.01 /System/Library/PrivateFrameworks/CoreSymbolication.fr
  263 ??         0:03.39 /System/Library/CoreServices/Dock.app/Contents/MacOS/D
  265 ??         0:00.22 /System/Library/CoreServices/SystemUIServer.app/Conten
  266 ??         0:04.96 /System/Library/CoreServices/Finder.app/Contents/MacOS
  267 ??         0:16.59 /usr/sbin/coreaudiod
  268 ??         0:00.03 /System/Library/Frameworks/CoreAudio.framework/Version
  271 ??         0:00.00 /usr/sbin/pboard
  273 ??         0:00.11 /System/Library/PrivateFrameworks/CacheDelete.framewor
  275 ??         0:00.05 /System/Library/CoreServices/backupd.bundle/Contents/R
  276 ??         0:00.10 /usr/libexec/sharingd
  277 ??         0:04.43 /System/Library/CoreServices/Spotlight.app/Contents/Ma
  278 ??         0:00.61 /System/Library/Frameworks/ApplicationServices.framewo
  280 ??         0:00.17 /usr/libexec/pkd
  281 ??         0:00.21 /usr/sbin/usernoted
  282 ??         0:00.14 /System/Library/PrivateFrameworks/TCC.framework/Resour
  283 ??         0:00.35 /System/Library/PrivateFrameworks/CalendarAgent.framew
  284 ??         0:00.02 /usr/libexec/nsurlsessiond
  285 ??         0:00.14 /usr/libexec/secinitd
  286 ??         0:00.09 /System/Library/PrivateFrameworks/CloudDocsDaemon.fram
  289 ??         0:00.06 /System/Library/CoreServices/pbs
  290 ??         0:00.15 /System/Library/PrivateFrameworks/CalendarAgent.framew
  293 ??         0:00.14 /System/Library/CoreServices/iconservicesagent
  295 ??         0:00.08 /usr/libexec/secd
  296 ??         0:00.23 /System/Library/PrivateFrameworks/InternetAccounts.fra
  297 ??         0:00.01 /System/Library/PrivateFrameworks/CommerceKit.framewor
  298 ??         0:00.04 /System/Library/CoreServices/mapspushd
  299 ??         0:00.02 /System/Library/PrivateFrameworks/AskPermission.framew
  300 ??         0:00.04 /System/Library/PrivateFrameworks/CallHistory.framewor
  301 ??         0:00.07 /usr/libexec/fmfd
  302 ??         0:00.49 /System/Library/PrivateFrameworks/IDS.framework/identi
  303 ??         0:00.12 /System/Library/PrivateFrameworks/CloudKitDaemon.frame
  304 ??         0:00.05 /System/Library/Frameworks/Accounts.framework/Versions
  305 ??         0:00.18 /System/Library/PrivateFrameworks/TelephonyUtilities.f
  306 ??         0:00.09 /System/Library/PrivateFrameworks/IMCore.framework/ima
  307 ??         0:00.03 /System/Library/PrivateFrameworks/IMDPersistence.frame
  308 ??         0:00.01 /System/Library/CoreServices/CrashReporterSupportHelpe
  309 ??         0:00.22 /usr/libexec/nsurlstoraged
  310 ??         0:00.02 /usr/sbin/filecoordinationd
  311 ??         0:00.15 /System/Library/CoreServices/Dock.app/Contents/XPCServ
  312 ??         0:00.15 /System/Library/CoreServices/CoreServicesUIAgent.app/C
  314 ??         0:00.01 /usr/libexec/spindump_agent
  316 ??         0:00.02 /System/Library/CoreServices/SocialPushAgent.app/Conte
  318 ??         0:00.07 /System/Library/CoreServices/Keychain Circle Notificat
  321 ??         0:00.82 /System/Library/CoreServices/NotificationCenter.app/Co
  323 ??         0:00.10 /System/Library/CoreServices/AppleIDAuthAgent
  325 ??         0:00.16 /bin/bash /usr/local/bin/antipopd
  326 ??         0:00.17 /Users/radu/Library/Application Support/Spotify/Spotif
  329 ??         0:14.40 /Applications/Utilities/Adobe Creative Cloud/ACC/Creat
  330 ??         0:00.01 /System/Library/PrivateFrameworks/HelpData.framework/V
  333 ??         0:00.07 /System/Library/CoreServices/diagnostics_agent
  336 ??         0:00.13 /System/Library/PrivateFrameworks/MessagesKit.framewor
  337 ??         0:00.06 /usr/libexec/amfid
  345 ??         0:02.47 /System/Library/Frameworks/ApplicationServices.framewo
  347 ??         0:00.11 /Applications/iTunes.app/Contents/MacOS/iTunesHelper.a
  349 ??         0:00.08 /Users/radu/Library/Application Support/Google/Android
  350 ??         0:00.02 /System/Library/PrivateFrameworks/CallHistory.framewor
  351 ??         0:00.01 /System/Library/Frameworks/Security.framework/Versions
  352 ??         0:00.01 /System/Library/Frameworks/AudioToolbox.framework/XPCS
  353 ??         0:00.02 /System/Library/Frameworks/AudioToolbox.framework/XPCS
  354 ??         0:00.57 /System/Library/PrivateFrameworks/CommerceKit.framewor
  355 ??         0:00.11 /Applications/Degrees.app/Contents/MacOS/Degrees
  356 ??         0:00.02 /System/Library/PrivateFrameworks/Notes.framework/Vers
  358 ??         0:00.14 /System/Library/CoreServices/Spotlight.app/Contents/XP
  359 ??         0:00.02 /System/Library/CoreServices/NotificationCenter.app/Co
  367 ??         0:00.16 /Applications/Utilities/Adobe Application Manager/IPC/
  370 ??         0:00.01 /System/Library/PrivateFrameworks/CommerceKit.framewor
  376 ??         0:31.99 /Applications/Opera.app/Contents/MacOS/Opera
  377 ??         0:00.48 /System/Library/PrivateFrameworks/CommerceKit.framewor
  379 ??         0:00.07 /System/Library/PrivateFrameworks/CommerceKit.framewor
  380 ??         0:00.03 /System/Library/PrivateFrameworks/CommerceKit.framewor
  384 ??         0:19.16 /Applications/Opera.app/Contents/Versions/24.0.1558.64
  390 ??         0:10.15 /Applications/Opera.app/Contents/Versions/24.0.1558.64
  393 ??         0:00.82 /Applications/Opera.app/Contents/Versions/24.0.1558.64
  401 ??         0:00.36 /Applications/Utilities/Adobe Creative Cloud/HEX/Adobe
  408 ??         0:00.08 /System/Library/Services/AppleSpell.service/Contents/M
  410 ??         0:19.40 /Applications/Opera.app/Contents/Versions/24.0.1558.64
  411 ??         0:00.02 /System/Library/Frameworks/InputMethodKit.framework/Ve
  441 ??         0:00.01 /System/Library/Frameworks/CoreServices.framework/Fram
  468 ??         0:00.01 /usr/sbin/spindump
  481 ??         1:00.68 /Volumes/Mavericks/Applications/VLC.app/Contents/MacOS
  483 ??         0:00.01 /usr/libexec/syspolicyd
  491 ??         0:00.05 /System/Library/Frameworks/CoreServices.framework/Fram
  506 ??         0:00.06 /usr/libexec/systemstatsd
 1168 ??         0:02.17 /Applications/Mail.app/Contents/MacOS/Mail
 1173 ??         0:00.13 /usr/sbin/ocspd
 1175 ??         0:00.31 /System/Library/Frameworks/WebKit.framework/Versions/A
 1177 ??         0:00.10 /System/Library/PrivateFrameworks/CoreRecents.framewor
 1178 ??         0:00.18 /System/Library/Frameworks/WebKit.framework/Versions/A
 1179 ??         0:00.06 /System/Library/PrivateFrameworks/DataDetectorsCore.fr
 1209 ??         0:27.02 /Applications/uTorrent.app/Contents/MacOS/uTorrent
 1304 ??         0:40.15 /Applications/Opera.app/Contents/Versions/24.0.1558.64
 1547 ??         0:34.18 /Applications/Opera.app/Contents/Versions/24.0.1558.64
 1584 ??         0:00.10 /System/Library/PrivateFrameworks/CommerceKit.framewor
 1585 ??         0:00.02 /System/Library/PrivateFrameworks/CommerceKit.framewor
 1587 ??         0:00.02 /System/Library/PrivateFrameworks/CommerceKit.framewor
 1611 ??         0:00.01 /System/Library/PrivateFrameworks/StoreXPCServices.fra
 1615 ??         0:00.01 /usr/libexec/nsurlstoraged
 1617 ??         0:00.00 /System/Library/Frameworks/CoreServices.framework/Fram
 1650 ??         0:00.01 /System/Library/Frameworks/CoreServices.framework/Fram
 1651 ??         0:00.03 /System/Library/Frameworks/CoreServices.framework/Fram
 1652 ??         0:00.03 /System/Library/Frameworks/CoreServices.framework/Fram
 1653 ??         0:00.02 /System/Library/Frameworks/CoreServices.framework/Fram
 1768 ??         0:00.03 /usr/libexec/warmd_agent
 1778 ??         0:00.10 /System/Library/Frameworks/QuickLook.framework/Resourc
 1779 ??         0:00.11 /System/Library/Frameworks/QuickLook.framework/Version
 1802 ??         0:00.22 /Applications/Utilities/Terminal.app/Contents/MacOS/Te
 1812 ??         0:00.00 sleep 10
 1804 ttys000    0:00.03 login -pf radu
 1805 ttys000    0:00.00 -bash
 1813 ttys000    0:00.00 ps -A
192-168-0-103:~ radu$

Going to try a shut down now. BRB.

 

Update: 7 successful shutdowns in a row (no Chrome this time, but Opera was closed from the X, and the computer shut down using only the mouse...if that has any relevance; right now I'm not sure, so in order to have some common ground for test results, I'm using the same method and change only one variable at a time).

post-1303722-0-02923900-1413140587_thumb.png

Link to comment
Share on other sites
sailor25462
sailor25462
Posted
  • Author
Posted

As for the reopen, I tried both. Makes no difference.

 

Your process list is very much truncated, probably due to the small terminal window. I will need to go through it line by line to really find any difference. This might take some time, though.

 

When you say you don't have chrome in the ps list, what happens when you shutdown then? reboot or shutdown?

 

If I close the last tab of chrome with the X, it will leave chrome open in the background. ps -A will give me the following line: 

591 ??         0:01.05 /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
595 ??         0:00.19 /Applications/Google Chrome.app/Contents/Versions/39.0.2171.13/Google Chrome Helper.app/Contents/MacOS/Google Chrome Helper --type=gpu-process --channel=591.0.2010592763 --supports-dual-gpus=false --gpu-driver-bug-workarounds=4,12,23,33,34,38,43,49 --disable-accelerated-video-decode --gpu-vendor-id=0x10de --gpu-device-id=0x0fc1 --gpu-driver-vendor --gpu-driver-version 

What's interesting to me is the number of parameters chrome helper is having!

 

Nevertheless, it seems I still need to dig in the dark. I can't really get the same result as you do with the chrome.app

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

As for the reopen, I tried both. Makes no difference.

 

Your process list is very much truncated, probably due to the small terminal window. I will need to go through it line by line to really find any difference. This might take some time, though.

 

When you say you don't have chrome in the ps list, what happens when you shutdown then? reboot or shutdown?

 

If I close the last tab of chrome with the X, it will leave chrome open in the background. ps -A will give me the following line: 

591 ??         0:01.05 /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
595 ??         0:00.19 /Applications/Google Chrome.app/Contents/Versions/39.0.2171.13/Google Chrome Helper.app/Contents/MacOS/Google Chrome Helper --type=gpu-process --channel=591.0.2010592763 --supports-dual-gpus=false --gpu-driver-bug-workarounds=4,12,23,33,34,38,43,49 --disable-accelerated-video-decode --gpu-vendor-id=0x10de --gpu-device-id=0x0fc1 --gpu-driver-vendor --gpu-driver-version 

What's interesting to me is the number of parameters chrome helper is having!

 

Nevertheless, it seems I still need to dig in the dark. I can't really get the same result as you do with the chrome.app

Uhm, you're right about the log. It was made with a small window. I didn't know the Terminal will actually cut the lines to the window's size... Kinda stupid, in my opinion, but anyway...

I exported it into a txt file. So you can check it out in the attachment.

 

Also....if this really has anything to do with Chrome....uninstalling it should solve it, right?

 

Let me know if I can help with any other info. So far, it seems to work for me. But if I find out more info, be sure that I will post it here.

Terminal Saved Output.txt

Link to comment
Share on other sites
sailor25462
sailor25462
Posted
  • Author
Posted

I just tried a sudo shutdown -h now in the terminal. What can I say: It worked. It was a quite aggressive shutdown I think, but it turned off the system. The next boot was also a bit rough, the system reopened all sessions, although it was turned off in gui. Then, after a few minutes, the system performed a reboot, like a cold start.

 

I'll try a regular shutdown now. 

 

 

Update: worked! Regular shutdown, no other apps open.

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

I just tried a sudo shutdown -h now in the terminal. What can I say: It worked. It was a quite aggressive shutdown I think, but it turned off the system. The next boot was also a bit rough, the system reopened all sessions, although it was turned off in gui. Then, after a few minutes, the system performed a reboot, like a cold start.

 

I'll try a regular shutdown now. 

To me...the shutdown from the terminal had no effect before. I used "sudo shutdown -h now". The force reboot is another story (Graphics injection or Flash Player). If you're using Safari or Opera, make sure you get the latest Flash Player plugin (v15) from Adobe Beta Labs. The previous versions had some issues and caused computer freezes and such. The last one I downloaded today still has some issues with Safari (though the video playback is ok and I encountered no freezing anymore and no restarts). I had no issues with the Flash Player on Opera. It's also one of my favorite browsers. But that's another story.

 

If you choose to update your Flash Player, make sure you select the right version (there are two versions: one for Opera and Chrome and one for Safari/Firefox etc). Chrome doesn't need a Flash Plugin since it comes with one pre-installed. But Opera does need one. So make sure you get the right one.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...