-
Notifications
You must be signed in to change notification settings - Fork 5.2k
failure in pulseaudio if the HDMI TV is temporarily powered off #2710
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can you describe how you configured audio to use the MAI PCM vc4 driver? |
I do have the gl module enabled.
We built an RTlinux Rasbian Stretch with a gl compositor MATE desktop for our clubs machine control projects, and the frozen-version can be downloaded here if you wish to investigate the working configuration: sudo amixer lsmod |
Can you confirm if the breakage was due to the kernel update or pulse audio? |
I found a working setup for the screen standby audio-loss issue with Oct 12, 2018 Pi firmware and kernel: /boot/config.txt flags that now work:
Do not power off the HDMI LCD at any time during this process, or you will need to redo from step 1. |
Although, the setup above will no longer immediately hang the audio device during TV standby. it does seem to still occur after about 15 minutes after the screen goes dark (although now can be fixed by just rebooting). I played a stream with vlc on the tv for awhile to see if some other variable is at play. |
Got it |
Uh oh!
There was an error while loading. Please reload this page.
Raspbian Debian Stretch oct 8, 2018 apt update causes a reproducible failure in pulseaudio TV HDMI output if the TV is temporarily powered off.
This did not occur with the older Kernel 4.14.52 (with old firmware), and now also occurs on the current 4.14.70-v7+ #1144 SMP Tue Sep 18 17:34:46 BST 2018 armv7l GNU/Linux
Therefore, it may be related to the current pulseaudio or new raspbian-firmware packages
Symptoms:
/var/log/syslog
Oct 11 02:46:08 neptune pulseaudio[1430]: [alsa-sink-MAI PCM vc4-hdmi-hifi-0] alsa-sink.c: Error opening PCM device iec958:0: Device or resource busy
Oct 11 02:46:08 neptune pulseaudio[1430]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.
Oct 11 02:46:08 neptune pulseaudio[1430]: [alsa-sink-MAI PCM vc4-hdmi-hifi-0] alsa-sink.c: Error opening PCM device iec958:0: Device or resource busy
Oct 11 02:46:08 neptune pulseaudio[1430]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.
Oct 11 02:46:08 neptune pulseaudio[1430]: [alsa-sink-MAI PCM vc4-hdmi-hifi-0] alsa-sink.c: Error opening PCM device iec958:0: Device or resource busy
Oct 11 02:46:08 neptune pulseaudio[1430]: [alsa-sink-MAI PCM vc4-hdmi-hifi-0] alsa-sink.c: Error opening PCM device iec958:0: Device or resource busy
Oct 11 02:46:08 neptune pulseaudio[1430]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.
Oct 11 02:46:10 neptune kernel: [ 5462.905558] ------------[ cut here ]------------
Oct 11 02:46:10 neptune kernel: [ 5462.905643] WARNING: CPU: 0 PID: 1820 at drivers/gpu/drm/vc4/vc4_crtc.c:668 vc4_crtc_atomic_flush+0x124/0x128 [vc4]
Oct 11 02:46:10 neptune kernel: [ 5462.905652] Modules linked in: cmac rfcomm bnep hci_uart btbcm serdev bluetooth ecdh_generic binfmt_misc joydev evdev spidev brcmfmac brcmutil cfg80211 rfkill snd_bcm2835(C) spi_bcm2835 uio_pdrv_genirq uio i2c_dev sunrpc ip_tables x_tables ipv6 overlay hid_microsoft vc4 drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec drm snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd i2c_bcm2835 fixed
Oct 11 02:46:10 neptune kernel: [ 5462.905738] CPU: 0 PID: 1820 Comm: kworker/u8:0 Tainted: G WC 4.14.52-rt34-v7+ #3
Oct 11 02:46:10 neptune kernel: [ 5462.905740] Hardware name: BCM2835
Oct 11 02:46:10 neptune kernel: [ 5462.905771] Workqueue: events_unbound commit_work [vc4]
Oct 11 02:46:10 neptune kernel: [ 5462.905791] [<8010fdf0>] (unwind_backtrace) from [<8010bf4c>] (show_stack+0x20/0x24)
Oct 11 02:46:10 neptune kernel: [ 5462.905802] [<8010bf4c>] (show_stack) from [<80747eac>] (dump_stack+0xbc/0x100)
Oct 11 02:46:10 neptune kernel: [ 5462.905811] [<80747eac>] (dump_stack) from [<8011dbf0>] (__warn+0xf8/0x110)
Oct 11 02:46:10 neptune kernel: [ 5462.905817] [<8011dbf0>] (__warn) from [<8011dcd8>] (warn_slowpath_null+0x30/0x38)
Oct 11 02:46:10 neptune kernel: [ 5462.905845] [<8011dcd8>] (warn_slowpath_null) from [<7f19cf08>] (vc4_crtc_atomic_flush+0x124/0x128 [vc4])
Oct 11 02:46:10 neptune kernel: [ 5462.905951] [<7f19cf08>] (vc4_crtc_atomic_flush [vc4]) from [<7f163ab0>] (drm_atomic_helper_commit_planes+0x1c4/0x2b0 [drm_kms_helper])
Oct 11 02:46:10 neptune kernel: [ 5462.906029] [<7f163ab0>] (drm_atomic_helper_commit_planes [drm_kms_helper]) from [<7f1a431c>] (vc4_atomic_complete_commit+0x54/0xd8 [vc4])
Oct 11 02:46:10 neptune kernel: [ 5462.906084] [<7f1a431c>] (vc4_atomic_complete_commit [vc4]) from [<7f1a44ec>] (commit_work+0x1c/0x20 [vc4])
Oct 11 02:46:10 neptune kernel: [ 5462.906119] [<7f1a44ec>] (commit_work [vc4]) from [<801384c4>] (process_one_work+0x1fc/0x588)
Oct 11 02:46:10 neptune kernel: [ 5462.906128] [<801384c4>] (process_one_work) from [<801394e8>] (worker_thread+0x60/0x5e4)
Oct 11 02:46:10 neptune kernel: [ 5462.906134] [<801394e8>] (worker_thread) from [<8013ec8c>] (kthread+0x144/0x174)
Oct 11 02:46:10 neptune kernel: [ 5462.906143] [<8013ec8c>] (kthread) from [<80107d54>] (ret_from_fork+0x14/0x20)
Oct 11 02:46:10 neptune kernel: [ 5462.906179] ---[ end trace 0000000000000003 ]---
The text was updated successfully, but these errors were encountered: