UA-101, ALSA playback was disrupted when disconnecting an already unmounted USB hard disk

[Michael Mess]

While VLC was playing video with sound via ALSA, I have disconnected an USB hard drive (after I have unmounted the file system). Then the sound stopped working while VLC was still playing video.

The USB-LED on the device was blinking green (error condition), while normally it lights red when the device is ready to use.

Also the pulseaudio system which uses the UA-101 via ALSA was hanging.
I had do turn the UA-101 off to stop pulseaudio hanging and let apport-bug continue to finish creating the bug report.
apport-bug then suggested the bug title "UA-101 - UA-101, playback Pulseaudio fails to detect card", but this is not the bug to be reported here.
Note: Such a bug in pulseaudio exists: see https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/986817 for that issue.

The bug to be reported here is that the USB connection to the UA-101 got out of sync, because another device has been disconnected.
This seems to be an issue with ALSA and USB.

Dmesg showed these lines:

[173549.193823] NVRM: os_pci_init_handle: invalid context!
[173549.193829] NVRM: os_pci_init_handle: invalid context!
[173549.193838] NVRM: os_map_kernel_space: can't map 0xd0000000, invalid context!
[173549.193842] NVRM: os_pci_init_handle: invalid context!
[173592.474016] NVRM: os_pci_init_handle: invalid context!
[173592.474022] NVRM: os_pci_init_handle: invalid context!
[173592.474032] NVRM: os_map_kernel_space: can't map 0xd0000000, invalid context!
[173592.474036] NVRM: os_pci_init_handle: invalid context!
[173759.693800] NVRM: os_pci_init_handle: invalid context!
[173759.693805] NVRM: os_pci_init_handle: invalid context!
[173759.693814] NVRM: os_map_kernel_space: can't map 0xd0000000, invalid context!
[173759.693818] NVRM: os_pci_init_handle: invalid context!
[173888.314092] NVRM: os_pci_init_handle: invalid context!
[173888.314096] NVRM: os_pci_init_handle: invalid context!
[173888.314105] NVRM: os_map_kernel_space: can't map 0xd0000000, invalid context!
[173888.314107] NVRM: os_pci_init_handle: invalid context!
[174010.113854] NVRM: os_pci_init_handle: invalid context!
[174010.113858] NVRM: os_pci_init_handle: invalid context!
[174010.113867] NVRM: os_map_kernel_space: can't map 0xd0000000, invalid context!
[174010.113869] NVRM: os_pci_init_handle: invalid context!
[174341.656866] usb 1-3: USB disconnect, device number 5
[174488.916110] usb 1-4: interface reset failed; error -110: unknown error
[174493.916106] usb 1-4: interface reset failed; error -110: unknown error
[174498.948113] usb 1-4: interface reset failed; error -110: unknown error
[174503.948110] usb 1-4: interface reset failed; error -110: unknown error
[174508.972116] usb 1-4: interface reset failed; error -110: unknown error
[174513.972118] usb 1-4: interface reset failed; error -110: unknown error
[174518.996111] usb 1-4: interface reset failed; error -110: unknown error
[174523.996113] usb 1-4: interface reset failed; error -110: unknown error
[174529.020119] usb 1-4: interface reset failed; error -110: unknown error
[174534.020124] usb 1-4: interface reset failed; error -110: unknown error
[174539.044123] usb 1-4: interface reset failed; error -110: unknown error
[174544.044125] usb 1-4: interface reset failed; error -110: unknown error
...

michael@quad:~/download$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0582:007d Roland Corp. EDIROL UA-101
Bus 005 Device 002: ID 046a:0001 Cherry GmbH My3000 Keyboard
Bus 008 Device 003: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse

After turning the UA-101 off and on again, dmesg showed these lines and the unknown error lines didn't occur again:
[175170.560164] usb 1-4: interface reset failed; error -110: unknown error
[175175.560163] usb 1-4: interface reset failed; error -110: unknown error
[175180.576167] usb 1-4: interface reset failed; error -110: unknown error
[175184.800815] usb 1-4: USB disconnect, device number 2
[175210.512024] usb 1-4: new high-speed USB device number 6 using ehci_hcd

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu11
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: michael 28667 F.... pulseaudio
 /dev/snd/controlC1: michael 28667 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'UA101'/'EDIROL UA-101 (serial ZT82634), 192000 Hz at usb-0000:00:1a.7-4, high speed'
   Mixer name : ''
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card0.Amixer.values:
 Simple mixer control 'MIDI Input Mode',0
   Capabilities: enum
   Items: 'High Load' 'Light Load'
   Item0: 'Light Load'
Card1.Amixer.info:
 Card hw:1 'Intel'/'HDA Intel at 0xf6ff8000 irq 44'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,1043829f,00100002'
   Controls : 45
   Simple ctrls : 21
Card2.Amixer.info:
 Card hw:2 'CX8811'/'Conexant CX8811 at 0xfb000000'
   Mixer name : 'CX88'
   Components : ''
   Controls : 3
   Simple ctrls : 2
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=ab789354-f06e-4173-82a4-1e34e7bdec37
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer P5K
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic-pae root=UUID=66db0a4d-a8a9-40f4-b1fd-222710b3195e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-27-generic-pae N/A
 linux-backports-modules-3.2.0-27-generic-pae N/A
 linux-firmware 1.79
RfKill:

Tags: precise running-unity precise running-unity
Uname: Linux 3.2.0-27-generic-pae i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 10/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1201
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5K
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd10/14/2008:svnSystemmanufacturer:pnP5K:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5K
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Michael Mess (michael-michaelmess)]

When audio was disrupted, VLC was playing with ALSA directly, bypassing Pulseaudio, thus it is very unlikely a pulseaudio-bug.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1030326

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[Michael Mess (michael-michaelmess)]

apport information

[penalvch (penalvch)]

Michael Mess, thank you for reporting this and helping make Ubuntu better. Could you please confirm this issue exists with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.