Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Unexpected Shutdown

871 views
Skip to first unread message

RJH

unread,
Sep 22, 2020, 7:56:40 PM9/22/20
to
My 2020 iMac shut down for no apparent reason - first time it's done it since
new (month or so). I'm curious about the cause. Terminal gives this reason:

--
Bob@Bobs-iMac ~ % log show --predicate 'eventMessage contains "Previous
shutdown cause"' --last 24h
Filtering the log data using "composedMessage CONTAINS "Previous shutdown
cause""
Skipping info and debug messages, pass --info and/or --debug to include.
Timestamp Thread Type Activity
PID TTL
2020-09-22 23:56:56.868997+0100 0xd0 Default 0x0 0
0 kernel: (AppleSMC) Previous shutdown cause: -14
-----------------------------------------------------------------------------
---------------------------------------
Log - Default: 1, Info: 0, Debug: 0,
Error: 0, Fault: 0
Activity - Create: 0, Transition: 0, Actions: 0
Bob@Bobs-iMac ~ %
--

There doesn't seem to be a 'cause -14'.

Looking in Library/Logs/DiagnosticReports/ProxiedDevice-Bridge there's an iOS
crashlog file:

--
{"bug_type":"115","timestamp":"2020-09-22 19:32:31.00 +0000","name":"Reset
count","os_version":"Bridge OS 4.6
(17P6610)","incident_id":"3DB351BC-2966-4B9B-B110-2D3EABA85855"}
Incident Identifier: 3DB351BC-2966-4B9B-B110-2D3EABA85855
CrashReporter Key: c0dec0dec0dec0dec0dec0dec0dec0dec0de0001
Date: 2020-09-22 19:32:31.52 +0000
Reset count: 0
Boot failure count: 1
Boot faults: rst vdd_hi chg_pok vdd_hi_chg
Boot stage: 255
Boot app: 0
--

which looks to be the only crash related activity that happened around the
time of the shutdown. There's 6 similar files over the past 6 days.

Any ideas? The only thing I can think of is an unpowered generic USB hub, but
that's been plugged in for a good few weeks.
--
Cheers, Rob


nospam

unread,
Sep 22, 2020, 9:02:10 PM9/22/20
to
In article <rke2vh$1t97$1...@gioia.aioe.org>, RJH <patch...@gmx.com>
wrote:

> My 2020 iMac shut down for no apparent reason - first time it's done it since
> new (month or so). I'm curious about the cause. Terminal gives this reason:
>
...

>
> There doesn't seem to be a 'cause -14'.

<https://georgegarside.com/blog/macos/shutdown-causes/>
-14
Electricity spike/surge.
On Mac Pro, this can indicate an electricity issue to the built-in
power supply, or an issue with the power supply itself.

what do you see in
pmset -g log

>
> Looking in Library/Logs/DiagnosticReports/ProxiedDevice-Bridge there's an iOS
> crashlog file:
>
> --
> {"bug_type":"115","timestamp":"2020-09-22 19:32:31.00 +0000","name":"Reset
> count","os_version":"Bridge OS 4.6

bridge os, what runs on the t2 chip, crashed.



> Any ideas? The only thing I can think of is an unpowered generic USB hub, but
> that's been plugged in for a good few weeks.

almost certainly not, but you could try removing it and see if it has
any effect.

RJH

unread,
Sep 22, 2020, 9:38:35 PM9/22/20
to
On 23 Sep 2020 at 02:02:03 BST, "nospam" <nos...@nospam.invalid> wrote:

> In article <rke2vh$1t97$1...@gioia.aioe.org>, RJH <patch...@gmx.com>
> wrote:
>
>> My 2020 iMac shut down for no apparent reason - first time it's done it
>> since
>> new (month or so). I'm curious about the cause. Terminal gives this reason:
>>
> ...
>
>>
>> There doesn't seem to be a 'cause -14'.
>
> <https://georgegarside.com/blog/macos/shutdown-causes/>
> -14
> Electricity spike/surge.
> On Mac Pro, this can indicate an electricity issue to the built-in
> power supply, or an issue with the power supply itself.
>
> what do you see in
> pmset -g log

A lot! The logs start on 16th September, with several mentions of: UPSB driver
is slow

Last couple of lines before the shutdown:

--
2020-09-22 20:20:30 +0100 Assertions PID 410(UserEventAgent)
Released BackgroundTask "com.apple.AddressBook.ScheduledSync" 00:00:30
id:0x0xb00008fb5 [System: PrevIdle]
2020-09-22 20:29:38 +0100 Assertions PID 5507(Usenapp) Summary
PreventUserIdleSystemSleep "Downloading started background" 04:53:04
id:0x0x100008ab9 [System: PrevIdle]
2020-09-22 20:29:38 +0100 Assertions PID 5507(Usenapp) Summary
PreventUserIdleSystemSleep "Downloading in the background" 12:04:21
id:0x0x10000a30c [System: PrevIdle]
2020-09-22 23:57:01 +0100 ShutdownCause SMC shutdown cause: -14:

Sleep/Wakes since boot at 2020-09-20 13:42:50 +0100 :15 Dark Wake Count in
this sleep cycle:7
--

Hundreds of these for the past few days:

PID 116(powerd) Created InternalPreventSleep "Assertion to change proximity
monitoring state"
PID 116(powerd) Released InternalPreventSleep "Assertion to change proximity
monitoring state"


>
>
>>
>> Looking in Library/Logs/DiagnosticReports/ProxiedDevice-Bridge there's an
>> iOS
>> crashlog file:
>>
>> --
>> {"bug_type":"115","timestamp":"2020-09-22 19:32:31.00 +0000","name":"Reset
>> count","os_version":"Bridge OS 4.6
>
> bridge os, what runs on the t2 chip, crashed.
>
>
>
>> Any ideas? The only thing I can think of is an unpowered generic USB hub,
>> but
>> that's been plugged in for a good few weeks.
>
> almost certainly not, but you could try removing it and see if it has
> any effect.

Yes, will do.

Is 16th Sept of any significance - all the weird logs etc seem to have started
about then. Or is it simply a week's worth of records are kept/displayed?

--
Cheers, Rob


nospam

unread,
Sep 22, 2020, 10:12:54 PM9/22/20
to
In article <rke8ul$1pbt$1...@gioia.aioe.org>, RJH <patch...@gmx.com>
wrote:

> >> My 2020 iMac shut down for no apparent reason - first time it's done it
> >> since
> >> new (month or so). I'm curious about the cause. Terminal gives this
> >> reason:
> >>

...

> >
> > what do you see in
> > pmset -g log
>
> A lot! The logs start on 16th September, with several mentions of: UPSB driver
> is slow
>
> Last couple of lines before the shutdown:
>
> --
> 2020-09-22 20:20:30 +0100 Assertions PID 410(UserEventAgent)
> Released BackgroundTask "com.apple.AddressBook.ScheduledSync" 00:00:30
> id:0x0xb00008fb5 [System: PrevIdle]
> 2020-09-22 20:29:38 +0100 Assertions PID 5507(Usenapp) Summary
> PreventUserIdleSystemSleep "Downloading started background" 04:53:04
> id:0x0x100008ab9 [System: PrevIdle]
> 2020-09-22 20:29:38 +0100 Assertions PID 5507(Usenapp) Summary
> PreventUserIdleSystemSleep "Downloading in the background" 12:04:21
> id:0x0x10000a30c [System: PrevIdle]
> 2020-09-22 23:57:01 +0100 ShutdownCause SMC shutdown cause: -14:

there's the same -14, which the other link states is a power supply
issue, although for a mac pro.

since it's a 2020 mac and still under warranty, take it to an apple
store (if possible) and let them figure it out.

you could also run apple diagnostics, but it's not as thorough as what
apple has:
<https://support.apple.com/en-us/HT202731>

Jaimie Vandenbergh

unread,
Sep 23, 2020, 5:07:15 AM9/23/20
to
On 23 Sep 2020 at 03:12:49 BST, "nospam" <nos...@nospam.invalid> wrote:

> you could also run apple diagnostics, but it's not as thorough as what
> apple has:
> <https://support.apple.com/en-us/HT202731>

Although not mentioned in that support article, pressing cmd-E after the
basic D/opt-D (for internet booted Diags) test has completed runs a
hidden, extended hardware test on the modern cut-down Diagnostics boot.

Cheers - Jaimie
--
[Chlorine trifluoride] is also hypergolic with such things as cloth,
wood,
and test engineers, not to mention asbestos, sand, and water -- with
which
it reacts explosively.
- "Ignition! An Informal History of Liquid Rocket Propellants", J D
Clarke


Basil Jet

unread,
Sep 23, 2020, 8:20:46 AM9/23/20
to

I used to have a problem with unexpected shutdowns.
I don't any more, because I've come to expect them.

--
Basil Jet recently enjoyed listening to
Albert Ayler - 1965 - Bells

RJH

unread,
Sep 23, 2020, 10:56:03 AM9/23/20
to
On 23 Sep 2020 at 10:07:12 BST, "Jaimie Vandenbergh"
<jai...@usually.sessile.org> wrote:

> On 23 Sep 2020 at 03:12:49 BST, "nospam" <nos...@nospam.invalid> wrote:
>
>> you could also run apple diagnostics, but it's not as thorough as what
>> apple has:
>> <https://support.apple.com/en-us/HT202731>
>
> Although not mentioned in that support article, pressing cmd-E after the
> basic D/opt-D (for internet booted Diags) test has completed runs a
> hidden, extended hardware test on the modern cut-down Diagnostics boot.
>
>
Thanks both - no errors from both tests. I'll just see if it does it again and
think about my options if it does.

--
Cheers, Rob


0 new messages