Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Recurring system crash

Hello,


Every now and then, my Macbook Pro gives the following error:


panic(cpu 1 caller 0xfffffff019d6d8c4): "Speaker::allocateBuffers attempting to release/re-allocate DMA buffer while DMA is streaming." @AppleARMDMAAudioDevice.cpp:1607

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 19P647

macOS version: 21C52

Kernel version: Darwin Kernel Version 21.2.0: Sun Nov 28 20:41:46 PST 2021; root:xnu-8019.61.5~2/RELEASE_ARM64_T8010

Kernel UUID: 096BFE9E-1498-32D9-A90D-40F573034F7C

iBoot version: iBoot-7429.61.2

secure boot?: YES

x86 EFI Boot State: 0xd

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0x5

x86 Previous Power Transitions: 0x10001000100

PCIeUp link state: 0x89473614

Paniclog version: 13

Kernel slide:      0x0000000011ac0000

Kernel text base:  0xfffffff018ac4000

mach_absolute_time: 0x1957034bac7

Epoch Time:        sec       usec

  Boot    : 0x61e82990 0x0000f79c

  Sleep   : 0x61eabbc5 0x000627af

  Wake    : 0x61eac055 0x0008e8e6

  Calendar: 0x61eac056 0x000c99d6


Zone info:

Foreign   : 0xfffffff0561bc000 - 0xfffffff0561cc000

Native    : 0xffffffe00055c000 - 0xffffffe60055c000

Readonly  : 0xffffffe0e6bc0000 - 0xffffffe133884000

Metadata  : 0xffffffeb00a6c000 - 0xffffffeb04bc4000

Bitmaps   : 0xffffffeb0226c000 - 0xffffffeb024cc000

CORE 0: PC=0xfffffff0193f4924, LR=0xfffffff0192e1e24, FP=0xffffffeb0ec0ad10

CORE 1 is the one that panicked. Check the full backtrace for details.

Panicked task 0xffffffe3e6ab5ec8: 1079 pages, 19 threads: pid 46: bridgeaudiod

Panicked thread: 0xffffffe3e5d4c6f8, backtrace: 0xffffffeb03f93060, tid: 45289

  lr: 0xfffffff0192b76b4  fp: 0xffffffeb03f930a0

  lr: 0xfffffff0192b7444  fp: 0xffffffeb03f93110

  lr: 0xfffffff0193f2d98  fp: 0xffffffeb03f93190

  lr: 0xfffffff0193f1f60  fp: 0xffffffeb03f93240

  lr: 0xfffffff0199215fc  fp: 0xffffffeb03f93250

  lr: 0xfffffff0192b7158  fp: 0xffffffeb03f935e0

  lr: 0xfffffff0192b7158  fp: 0xffffffeb03f93640

  lr: 0xfffffff01a41742c  fp: 0xffffffeb03f93660

  lr: 0xfffffff019d6d8c4  fp: 0xffffffeb03f93690

  lr: 0xfffffff019d6b2a8  fp: 0xffffffeb03f93700

  lr: 0xfffffff019d91b6c  fp: 0xffffffeb03f93720

  lr: 0xfffffff019c5e514  fp: 0xffffffeb03f93730

  lr: 0xfffffff01989b584  fp: 0xffffffeb03f93790

  lr: 0xfffffff01986a5ac  fp: 0xffffffeb03f93800

  lr: 0xfffffff019c5ed38  fp: 0xffffffeb03f93880

  lr: 0xfffffff0198a51ec  fp: 0xffffffeb03f93a20

  lr: 0xfffffff0193ba09c  fp: 0xffffffeb03f93b40

  lr: 0xfffffff0192bd72c  fp: 0xffffffeb03f93bd0

  lr: 0xfffffff019292cd8  fp: 0xffffffeb03f93d00

  lr: 0xfffffff0192a9e70  fp: 0xffffffeb03f93d90

  lr: 0xfffffff0193e7678  fp: 0xffffffeb03f93e60

  lr: 0xfffffff0193f2328  fp: 0xffffffeb03f93f10

  lr: 0xfffffff0199215fc  fp: 0xffffffeb03f93f20


Most of the time, I don't even realise it crashed (since it seems to happen when I close my screen) until I start my Mac up again. What could it be? I don't run any big or demanding programs on it (other than Microsoft office, etc.)

MacBook Pro 13″, macOS 10.14

Posted on Jan 21, 2022 6:28 AM

Reply
Question marked as Best reply

Posted on Jan 21, 2022 8:24 AM

Miranda_Quint wrote:

Hello,

Every now and then, my Macbook Pro gives the following error:

panic(cpu 1 caller 0xfffffff019d6d8c4): "Speaker::allocateBuffers attempting to release/re-allocate DMA buffer while DMA is streaming." @AppleARMDMAAudioDevice.cpp:1607
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 19P647
macOS version: 21C52
Kernel version: Darwin Kernel Version 21.2.0: Sun Nov 28 20:41:46 PST 2021; root:xnu-8019.61.5~2/RELEASE_ARM64_T8010
Kernel UUID: 096BFE9E-1498-32D9-A90D-40F573034F7C
iBoot version: iBoot-7429.61.2
secure boot?: YES
x86 EFI Boot State: 0xd
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0x5
x86 Previous Power Transitions: 0x10001000100
PCIeUp link state: 0x89473614
Paniclog version: 13
Kernel slide:      0x0000000011ac0000
Kernel text base:  0xfffffff018ac4000
mach_absolute_time: 0x1957034bac7
Epoch Time:        sec       usec
  Boot    : 0x61e82990 0x0000f79c
  Sleep   : 0x61eabbc5 0x000627af
  Wake    : 0x61eac055 0x0008e8e6
  Calendar: 0x61eac056 0x000c99d6

Zone info:
Foreign   : 0xfffffff0561bc000 - 0xfffffff0561cc000
Native    : 0xffffffe00055c000 - 0xffffffe60055c000
Readonly  : 0xffffffe0e6bc0000 - 0xffffffe133884000
Metadata  : 0xffffffeb00a6c000 - 0xffffffeb04bc4000
Bitmaps   : 0xffffffeb0226c000 - 0xffffffeb024cc000
CORE 0: PC=0xfffffff0193f4924, LR=0xfffffff0192e1e24, FP=0xffffffeb0ec0ad10
CORE 1 is the one that panicked. Check the full backtrace for details.
Panicked task 0xffffffe3e6ab5ec8: 1079 pages, 19 threads: pid 46: bridgeaudiod
Panicked thread: 0xffffffe3e5d4c6f8, backtrace: 0xffffffeb03f93060, tid: 45289
  lr: 0xfffffff0192b76b4  fp: 0xffffffeb03f930a0
  lr: 0xfffffff0192b7444  fp: 0xffffffeb03f93110
  lr: 0xfffffff0193f2d98  fp: 0xffffffeb03f93190
  lr: 0xfffffff0193f1f60  fp: 0xffffffeb03f93240
  lr: 0xfffffff0199215fc  fp: 0xffffffeb03f93250
  lr: 0xfffffff0192b7158  fp: 0xffffffeb03f935e0
  lr: 0xfffffff0192b7158  fp: 0xffffffeb03f93640
  lr: 0xfffffff01a41742c  fp: 0xffffffeb03f93660
  lr: 0xfffffff019d6d8c4  fp: 0xffffffeb03f93690
  lr: 0xfffffff019d6b2a8  fp: 0xffffffeb03f93700
  lr: 0xfffffff019d91b6c  fp: 0xffffffeb03f93720
  lr: 0xfffffff019c5e514  fp: 0xffffffeb03f93730
  lr: 0xfffffff01989b584  fp: 0xffffffeb03f93790
  lr: 0xfffffff01986a5ac  fp: 0xffffffeb03f93800
  lr: 0xfffffff019c5ed38  fp: 0xffffffeb03f93880
  lr: 0xfffffff0198a51ec  fp: 0xffffffeb03f93a20
  lr: 0xfffffff0193ba09c  fp: 0xffffffeb03f93b40
  lr: 0xfffffff0192bd72c  fp: 0xffffffeb03f93bd0
  lr: 0xfffffff019292cd8  fp: 0xffffffeb03f93d00
  lr: 0xfffffff0192a9e70  fp: 0xffffffeb03f93d90
  lr: 0xfffffff0193e7678  fp: 0xffffffeb03f93e60
  lr: 0xfffffff0193f2328  fp: 0xffffffeb03f93f10
  lr: 0xfffffff0199215fc  fp: 0xffffffeb03f93f20

Most of the time, I don't even realise it crashed (since it seems to happen when I close my screen) until I start my Mac up again. What could it be? I don't run any big or demanding programs on it (other than Microsoft office, etc.)



Kernel Panics are predominately caused by hardware faults or faulty third-party kernel extensions.


Learn what to do if your computer restarts or shuts down unexpectedly, or you get a message that your computer restarted or shut down because of a problem.


If your Mac spontaneously restarts or displays a ... - Apple Support

https://support.apple.com/en-us/HT200553




Call Customer Support (800) MY–APPLE (800–692–7753)

or on line https://getsupport.apple.com/

or call AppleCare Support at 1-800-APLCARE (800-275-2273)


Outside the USA—Contact Apple for support and service by phone

See a list of Apple phone numbers around the world.

https://support.apple.com/en-us/HT201232




Similar questions

1 reply
Question marked as Best reply

Jan 21, 2022 8:24 AM in response to Miranda_Quint

Miranda_Quint wrote:

Hello,

Every now and then, my Macbook Pro gives the following error:

panic(cpu 1 caller 0xfffffff019d6d8c4): "Speaker::allocateBuffers attempting to release/re-allocate DMA buffer while DMA is streaming." @AppleARMDMAAudioDevice.cpp:1607
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 19P647
macOS version: 21C52
Kernel version: Darwin Kernel Version 21.2.0: Sun Nov 28 20:41:46 PST 2021; root:xnu-8019.61.5~2/RELEASE_ARM64_T8010
Kernel UUID: 096BFE9E-1498-32D9-A90D-40F573034F7C
iBoot version: iBoot-7429.61.2
secure boot?: YES
x86 EFI Boot State: 0xd
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0x5
x86 Previous Power Transitions: 0x10001000100
PCIeUp link state: 0x89473614
Paniclog version: 13
Kernel slide:      0x0000000011ac0000
Kernel text base:  0xfffffff018ac4000
mach_absolute_time: 0x1957034bac7
Epoch Time:        sec       usec
  Boot    : 0x61e82990 0x0000f79c
  Sleep   : 0x61eabbc5 0x000627af
  Wake    : 0x61eac055 0x0008e8e6
  Calendar: 0x61eac056 0x000c99d6

Zone info:
Foreign   : 0xfffffff0561bc000 - 0xfffffff0561cc000
Native    : 0xffffffe00055c000 - 0xffffffe60055c000
Readonly  : 0xffffffe0e6bc0000 - 0xffffffe133884000
Metadata  : 0xffffffeb00a6c000 - 0xffffffeb04bc4000
Bitmaps   : 0xffffffeb0226c000 - 0xffffffeb024cc000
CORE 0: PC=0xfffffff0193f4924, LR=0xfffffff0192e1e24, FP=0xffffffeb0ec0ad10
CORE 1 is the one that panicked. Check the full backtrace for details.
Panicked task 0xffffffe3e6ab5ec8: 1079 pages, 19 threads: pid 46: bridgeaudiod
Panicked thread: 0xffffffe3e5d4c6f8, backtrace: 0xffffffeb03f93060, tid: 45289
  lr: 0xfffffff0192b76b4  fp: 0xffffffeb03f930a0
  lr: 0xfffffff0192b7444  fp: 0xffffffeb03f93110
  lr: 0xfffffff0193f2d98  fp: 0xffffffeb03f93190
  lr: 0xfffffff0193f1f60  fp: 0xffffffeb03f93240
  lr: 0xfffffff0199215fc  fp: 0xffffffeb03f93250
  lr: 0xfffffff0192b7158  fp: 0xffffffeb03f935e0
  lr: 0xfffffff0192b7158  fp: 0xffffffeb03f93640
  lr: 0xfffffff01a41742c  fp: 0xffffffeb03f93660
  lr: 0xfffffff019d6d8c4  fp: 0xffffffeb03f93690
  lr: 0xfffffff019d6b2a8  fp: 0xffffffeb03f93700
  lr: 0xfffffff019d91b6c  fp: 0xffffffeb03f93720
  lr: 0xfffffff019c5e514  fp: 0xffffffeb03f93730
  lr: 0xfffffff01989b584  fp: 0xffffffeb03f93790
  lr: 0xfffffff01986a5ac  fp: 0xffffffeb03f93800
  lr: 0xfffffff019c5ed38  fp: 0xffffffeb03f93880
  lr: 0xfffffff0198a51ec  fp: 0xffffffeb03f93a20
  lr: 0xfffffff0193ba09c  fp: 0xffffffeb03f93b40
  lr: 0xfffffff0192bd72c  fp: 0xffffffeb03f93bd0
  lr: 0xfffffff019292cd8  fp: 0xffffffeb03f93d00
  lr: 0xfffffff0192a9e70  fp: 0xffffffeb03f93d90
  lr: 0xfffffff0193e7678  fp: 0xffffffeb03f93e60
  lr: 0xfffffff0193f2328  fp: 0xffffffeb03f93f10
  lr: 0xfffffff0199215fc  fp: 0xffffffeb03f93f20

Most of the time, I don't even realise it crashed (since it seems to happen when I close my screen) until I start my Mac up again. What could it be? I don't run any big or demanding programs on it (other than Microsoft office, etc.)



Kernel Panics are predominately caused by hardware faults or faulty third-party kernel extensions.


Learn what to do if your computer restarts or shuts down unexpectedly, or you get a message that your computer restarted or shut down because of a problem.


If your Mac spontaneously restarts or displays a ... - Apple Support

https://support.apple.com/en-us/HT200553




Call Customer Support (800) MY–APPLE (800–692–7753)

or on line https://getsupport.apple.com/

or call AppleCare Support at 1-800-APLCARE (800-275-2273)


Outside the USA—Contact Apple for support and service by phone

See a list of Apple phone numbers around the world.

https://support.apple.com/en-us/HT201232




Recurring system crash

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.