search

kyleneideck / BackgroundMusic

Background Music, a macOS audio utility: automatically pause your music, set individual apps' volumes and record system audio.
GNU General Public License v2.0
16.04k stars 675 forks source link

kernel panic in Speaker::allocateBuffers when installing while streaming something #567

Open bloerwald opened 2 years ago

bloerwald commented 2 years ago

Example bug report template

Description of the bug panic(cpu 1 caller 0xfffffff016c256e4): "Speaker::allocateBuffers attempting to release/re-allocate DMA buffer while DMA is streaming." @AppleARMDMAAudioDevice.cpp:1607 when installing via brew when installing. A video was streaming at the same time, so the description is probably accurate.

Steps to reproduce

  1. Probably: Start streaming something. In my case it was Plex via Safari.
  2. brew install --cask background-music
  3. Enter password.
  4. Sound vanishes first, then panic a bit later.

Versions

Debug logs Kernel panic

itachi47 commented 2 years ago

I am facing the similar issue.

System Crash Report: System information: macOS Monterey Version: 12.2.1 (21D62) MacBook Pro (16-inch, 2019) Processor: 2.6 GHz 6-Core Intel Core i7 Memory: 16 GB 2667 MHz DDR4 Graphics: Intel UHD Graphics 630 1536 MB

Issue: After upgrading the macOS to Monterey, builtin speaker loosing sound suddenly, though headphones are working fine.

Troubleshooting done:

  1. Tested the sound with different application, same result for all, no audio at all.
  2. Restarting the system is fixing the issue temporarily.
  3. "sudo killall coreduioid" fixing the issue temporarily.
  4. Resetting the SMC and NVRAM does not fix the issue.
  5. Created a different user which also faces the same issue.

Other information: No device is connected to the system. Checked the audio setting, not muted or anything else.

Backtrace for the Crash:

panic(cpu 0 caller 0xfffffff02813e04c): "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: 19P744 macOS version: 21D62 Kernel version: Darwin Kernel Version 21.3.0: Wed Jan 5 20:03:37 PST 2022; root:xnu-8019.80.24~19/RELEASE_ARM64_T8010 Kernel UUID: 5C49B2CB-9833-3D8A-8E98-E628559A4D1E iBoot version: iBoot-7429.81.3 secure boot?: YES x86 EFI Boot State: 0xd x86 System State: 0x0 x86 Power State: 0x0 x86 Shutdown Cause: 0x5 x86 Previous Power Transitions: 0x40001000100 PCIeUp link state: 0x89473614 Paniclog version: 13 Kernel slide: 0x000000001fe94000 Kernel text base: 0xfffffff026e98000 mach_absolute_time: 0xe91cbca0f8 Epoch Time: sec usec Boot : 0x6210c974 0x000e99b7 Sleep : 0x621318c5 0x0000bdf1 Wake : 0x621360c8 0x000841f9 Calendar: 0x62136469 0x000b011e

Zone info: Foreign : 0xfffffff0601b0000 - 0xfffffff0601c0000 Native : 0xffffffe000124000 - 0xffffffe600124000 Readonly : 0xffffffe0e6788000 - 0xffffffe13344c000 Metadata : 0xffffffeb00834000 - 0xffffffeb049b8000 Bitmaps : 0xffffffeb02034000 - 0xffffffeb0228c000 CORE 0 is the one that panicked. Check the full backtrace for details. CORE 1: PC=0xfffffff0277c8b94, LR=0xfffffff028166348, FP=0xffffffeb0f6dbe20 Panicked task 0xffffffe3e6697140: 1230 pages, 19 threads: pid 46: bridgeaudiod Panicked thread: 0xffffffe4cca75be0, backtrace: 0xffffffeb0f05b060, tid: 21013 lr: 0xfffffff02768b6bc fp: 0xffffffeb0f05b0a0 lr: 0xfffffff02768b44c fp: 0xffffffeb0f05b110 lr: 0xfffffff0277c7008 fp: 0xffffffeb0f05b190 lr: 0xfffffff0277c61d0 fp: 0xffffffeb0f05b240 lr: 0xfffffff027cf15fc fp: 0xffffffeb0f05b250 lr: 0xfffffff02768b160 fp: 0xffffffeb0f05b5e0 lr: 0xfffffff02768b160 fp: 0xffffffeb0f05b640 lr: 0xfffffff0287eb42c fp: 0xffffffeb0f05b660 lr: 0xfffffff02813e04c fp: 0xffffffeb0f05b690 lr: 0xfffffff02813ba30 fp: 0xffffffeb0f05b700 lr: 0xfffffff0281621ec fp: 0xffffffeb0f05b720 lr: 0xfffffff02802ec14 fp: 0xffffffeb0f05b730 lr: 0xfffffff027c6d2a8 fp: 0xffffffeb0f05b790 lr: 0xfffffff027c3c2d0 fp: 0xffffffeb0f05b800 lr: 0xfffffff02802f438 fp: 0xffffffeb0f05b880 lr: 0xfffffff027c76f10 fp: 0xffffffeb0f05ba20 lr: 0xfffffff02778e308 fp: 0xffffffeb0f05bb40 lr: 0xfffffff027691734 fp: 0xffffffeb0f05bbd0 lr: 0xfffffff027666cdc fp: 0xffffffeb0f05bd00 lr: 0xfffffff02767de78 fp: 0xffffffeb0f05bd90 lr: 0xfffffff0277bb8e8 fp: 0xffffffeb0f05be60 lr: 0xfffffff0277c6598 fp: 0xffffffeb0f05bf10 lr: 0xfffffff027cf15fc fp: 0xffffffeb0f05bf20

kyleneideck commented 2 years ago

I might be wrong, but I don't think there's much we can do about this except filing Radars, i.e. reporting the bug to Apple.

Background Music doesn't install any kernel extensions, so if it can cause a kernel panic, that must be a bug in the OS. Or a hardware issue.

You could try using the latest snapshot build of Background Music, but it might not make any difference.