Date: Sat, 09 Jul 2022 22:34:34 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 265121] system will get stuck when dragonfly DAC plugged in and being used Message-ID: <bug-265121-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D265121 Bug ID: 265121 Summary: system will get stuck when dragonfly DAC plugged in and being used Product: Base System Version: 13.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: jon@xyinn.org Hey all, I'm running 13.1-RELEASE FreeBSD 13.1-RELEASE releng/13.1-n250148-fc952ac22= 12 GENERIC amd64 on a Thinkpad X260. When using a Dragonfly DAC (USB), the aud= io plays fine and all, but if the device happens to be plugged in and being us= ed in any capacity by any process (Even if the music is paused), doing a suspe= nd (zzz) will cause the system to wait for the process using the audio device = to stop. However, this never happens to essentially you end up with a stuck system. I can switch ttys but since the system is in the middle of a suspen= d, no keyboard input is accepted. The only way out if to hard power off. Device:=20 ugen0.3: <AudioQuest AudioQuest DragonFly Cobalt v1.0> at usbus0 (disconnec= ted) uaudio0: at uhub0, port 2, addr 2 (disconnected) This is the message I get (loops forever): pcm3: unregister: channel pcm3:virtual:dsp3.vp0 busy (pid 23287) pcm3: Waiting for sound application to exit! I think for these situations, it may be fine to have a timeout where the process gets killed. I could see how some people may think that's a dangero= us operation however so I'm open to other workarounds, but I don't think it ju= st waiting forever it acceptable. - Jonathan --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-265121-227>