Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pulseaudio pulseaudio
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 855
    • Issues 855
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 58
    • Merge requests 58
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PulseAudio
  • pulseaudiopulseaudio
  • Issues
  • #177

Closed
Open
Created Apr 21, 2016 by Bugzilla Migration User@bugzilla-migration

pulseaudio blocked in kernel

Submitted by Brian J. Murrell

Assigned to pul..@..op.org

Link to original bug (#95055)

Description

I have a pulseaudio process that seems to be blocked in the kernel:

kernel: sysrq: SysRq : Show Blocked State kernel: task PC stack pid father kernel: pulseaudio D ffff8801191a3b98 0 26427 1 0x00000004 kernel: ffff8801191a3b98 ffffffff81c10500 ffff880002788000 ffff8801191a4000 kernel: ffff8804afa0e080 ffff8801191a3bd0 ffff8804afa0e080 ffff88049b053000 kernel: ffff8801191a3bb0 ffffffff81795895 0000000205922d36 ffff8801191a3c60 kernel: Call Trace: kernel: [<ffffffff81795895>] schedule+0x35/0x80 kernel: [<ffffffff817986b3>] schedule_timeout+0x123/0x240 kernel: [<ffffffff8110b7c0>] ? trace_event_raw_event_tick_stop+0x120/0x120 kernel: [<ffffffff817993de>] ? _raw_spin_unlock_irqrestore+0xe/0x10 kernel: [<ffffffffa0477f05>] snd_power_wait+0xb5/0x110 [snd] kernel: [<ffffffff810cc790>] ? wake_up_q+0x70/0x70 kernel: [<ffffffffa0479901>] snd_ctl_elem_info_user+0x61/0xf0 [snd] kernel: [<ffffffffa047c33c>] snd_ctl_ioctl+0x5ec/0x6c0 [snd] kernel: [<ffffffff8133baac>] ? selinux_file_ioctl+0x10c/0x1c0 kernel: [<ffffffff8123e7f8>] do_vfs_ioctl+0x298/0x480 kernel: [<ffffffff81333323>] ? security_file_ioctl+0x43/0x60 kernel: [<ffffffff8123ea59>] SyS_ioctl+0x79/0x90 kernel: [<ffffffff8179996e>] entry_SYSCALL_64_fastpath+0x12/0x71

Not sure how it got that way though.

Any advise or hints?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking