Bug 104821

Summary:	Driver changes by itself after waking the system
Product:	PulseAudio	Reporter:	Adam <padreadamo>
Component:	clients	Assignee:	pulseaudio-bugs
Status:	RESOLVED NOTOURBUG	QA Contact:	pulseaudio-bugs
Severity:	normal
Priority:	medium	CC:	lennart
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Adam 2018-01-28 18:56:55 UTC

Hello! I'm relatively new to the Linux world and I'm trying to do my part in posting bugs. I recently encountered one but I'm not sure if it's PulseAudio or my OS (OpenSUSE Tumbleweed). Basically, I use a Fiio USB Dac. The driver should always be: FiiO USB DAC E17K. However, when the system wakes from suspend, hibernate, or even normal sleep, the driver changes to: Bravo X-USB. I have posted two logs that I hope can assist with narrowing down the issue. The fix currently is to either: A. unplug the device and plug it back after waiting a few moments. B. Pressing the "input" button on the DAC and cycling a few times until finally ending back at USB input.

The device does have a "SLEEP" mode and it's turned off and has been.

NORMAL DRIVER AND USE:
https://pastebin.com/81QS2Rv9

AFTER RESUME FROM SLEEP/HIBERNATE/SUSPEND:
https://pastebin.com/anLVa4vV

Comment 1 Robert Wahlstedt 2018-01-29 00:30:07 UTC

Hello, according to this forum http://www.fiio.me/forum.php?mod=viewthread&tid=41872 the FIIO does not work properly with USB 3 and higher interfaces. Please plug the FIIO into a USB 2 port. USB ports are often blue and a USB 2 port is either white or black. I have marked the bug as “needing more information” requesting that you follow up with us on this thread should the problem persist. The USB 3 port is capable of downgrading itself to the USB 2 specification but it looks as though the IRQ port causes an IRQ conflict. Interrupt request (PC architecture) In a computer, an interrupt request (or IRQ) is a hardware signal sent to the processor that temporarily stops a running program and allows a special program, an interrupt handler, to run instead.

Comment 2 Adam 2018-01-31 02:25:36 UTC

Thank you!  I have plugged the device into a USB2 port and am currently rebooting, hibernating and suspending to see if I can invoke the change. As of right now, after 20 minutes of testing, everything is fine. I will report further findings in two days.

Comment 3 Adam 2018-02-01 02:13:19 UTC

I came back today from work and pulled the computer out of "Suspend" mode. The USB DAC was not detected and was only detected after unplugging the device from USB, then plugging it back in. This is certainly similar functionality as using the USB3 port. The device does have a Sleep mode. This mode is turned off.

Comment 4 Tanu Kaskinen 2018-02-01 08:45:36 UTC

This is a kernel driver bug (i.e. falls under the alsa project), not a PulseAudio bug, so I'm closing this bug. If Robert is able to help you, I don't mind continuing the discussion here, but please keep the bug closed.

Here's some information about reporting alsa bugs:
http://alsa-project.org/main/index.php/Bug_Tracking

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.