Date: Fri, 16 Oct 2015 16:10:56 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Hans Petter Selasky <hps@selasky.org> Cc: account lost <accountlostin@gmx.com>, "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org> Subject: Re: suspend broken when disconnecting an usb audio device Message-ID: <CAN6yY1sWq50KFUEm2PpbJcxhB7UFPmaKhP9shJ2ES45sDX8HSg@mail.gmail.com> In-Reply-To: <5621097F.20705@selasky.org> References: <trinity-486efcff-1027-407a-b7d4-033c9617d6a6-1445004546917@3capp-mailcom-bs16> <5621097F.20705@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 16, 2015 at 7:28 AM, Hans Petter Selasky <hps@selasky.org> wrote: > On 10/16/15 16:09, account lost wrote: > >> Hi, I'm using FreeBSD 10.2-RELEASE-p5 amd64 on a thinkpad t430. >> >> I have suspend and resume functionality working by using newcons and >> i915kms.ko as the video driver, but whenever I plug in and use my usb DAC, >> either by choosing it in applications supporting OSS or by setting it as >> the hw.snd.default_unit and then disconnect it without terminating the >> audio applications, I can't enter acpi s3. >> >> When trying to suspend the system I get repeated messages on the console: >> "Waiting for sound application to exit!" (as documented here: >> http://baitisj.blogspot.it/2015/05/usb-audio-disconnect-woes-in-freebsd.html) >> but I can't react by killing the incriminated pid since ttys are already >> unavailable, and I'm forced to perform an hard reset >> > > Hi, > > There is a bug in pulseaudio or some mixer application, that it doesn't > close the /dev/mixer or /dev/dsp, when receiving a read/write error from > the USB audio device. > > Try killing pulseaudio. > > --HPS You might also try lsof(8) or fstat(1) to confirm what is holding it open. (I really wish I could avoid using pulseaudio at all. It's a giant pain in the rear and pretty useless, but my MATE desktop insists.) I'd be curious if both fstat and lsof work. Of late I have not had success with fstat on a hung device, but lsof works fine. I realy need to try to track the fstat ossue down and, if it's not cockpit error, open a bug report.) -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1sWq50KFUEm2PpbJcxhB7UFPmaKhP9shJ2ES45sDX8HSg>