Re: USB 3.0 Isochronous audio
Can you describe the actual problem ? How can you trigger it ? What are you doing when the problem arises ? Do you hear audio glitches or does the device disconnect ? Do you have a crash ? Does the *same* device work on other setups ? Try to capture a usbmon trace of the failure, that's likely to help. -- balbi Hi, I put in a new kernel and get the response from uname -r of 3.14.0-031400-generic, apologies for the pedantry I am not that sure what I am doing. The device behaves exactly the same as default Linux kernel, buffer is erratic not stable like USB 2.0 and audio droputs every couple of seconds. The HDMI audio output does not work after installing the new kernel. I captured some data with usbmon but its a big file 4MB so I can email it separately if you are interested but a sample is as below. sudo cat /sys/kernel/debug/usb/usbmon/2u /tmp/1.mon.out Thanks Russel 8800d0230400 2003746485 C Zi:2:003:1 0:1:1116:0 1 0:0:3 4 = 00030b00 8800d0230400 2003746493 S Zi:2:003:1 -115:1:1116 1 -18:0:3 4 8802115e9540 2003746499 C Ii:2:003:3 0:32 2 = 0002 8802115e9540 2003746514 S Ii:2:003:3 -115:32 2 880036e14600 2003747539 C Zo:2:003:1 0:1:1106:0 5 0:0:264 0:264:264 0:528:264 0:792:264 0:1056:264 1320 880036e14600 2003747556 S Zo:2:003:1 -115:1:1106 5 -18:0:264 -18:264:270 -18:534:264 -18:798:264 -18:1062:264 1326 = b40e4abb e343b295 4cb72848 bc8d42bd 7341c10b 3ec4943b c2883dc8 9737cc17 8800d0230100 2003747563 C Zi:2:003:1 0:1:1117:0 1 0:0:3 4 = 00030b00 8800d0230100 2003747564 S Zi:2:003:1 -115:1:1117 1 -18:0:3 4 8800d0237900 2003748552 C Zi:2:003:1 0:1:1118:0 1 0:0:3 4 = 00030b00 8800d0237900 2003748561 S Zi:2:003:1 -115:1:1118 1 -18:0:3 4 8800d0237600 2003749520 C Zi:2:003:1 0:1:1119:0 1 0:0:3 4 = 00030b00 8800d0237600 2003749526 S Zi:2:003:1 -115:1:1119 1 -18:0:3 4 8800d0230400 2003750493 C Zi:2:003:1 0:1:1120:0 1 0:0:3 4 = 00030b00 8800d0230400 2003750498 S Zi:2:003:1 -115:1:1120 1 -18:0:3 4 8800d0230100 2003751518 C Zi:2:003:1 0:1:1121:0 1 0:0:3 4 = 00030b00 8800d0230100 2003751523 S Zi:2:003:1 -115:1:1121 1 -18:0:3 4 8800d0237900 2003752501 C Zi:2:003:1 0:1:1122:0 1 0:0:3 4 = 00030b00 8800d0237900 2003752506 S Zi:2:003:1 -115:1:1122 1 -18:0:3 4 880036e15c00 2003753507 C Zo:2:003:1 0:1::0 6 0:0:264 0:264:264 0:528:264 0:792:264 0:1056:264 1584 880036e15c00 2003753516 S Zo:2:003:1 -115:1: 5 -18:0:264 -18:264:264 -18:528:264 -18:792:264 -18:1056:264 1320 = 1537ea16 c9e808b1 f60dd5f1 f7970801 e4fdef09 10fab104 f4e00afb c103fbf6 8800d0237600 2003753520 C Zi:2:003:1 0:1:1123:0 1 0:0:3 4 = 00030b00 8800d0237600 2003753521 S Zi:2:003:1 -115:1:1123 1 -18:0:3 4 8800d0230400 2003754492 C Zi:2:003:1 0:1:1124:0 1 0:0:3 4 = 00030b00 8800d0230400 2003754494 S Zi:2:003:1 -115:1:1124 1 -18:0:3 4 8800d0230100 200371 C Zi:2:003:1 0:1:1125:0 1 0:0:3 4 = 00030b00 8800d0230100 2003755560 S Zi:2:003:1 -115:1:1125 1 -18:0:3 4 8800d0237900 2003756552 C Zi:2:003:1 0:1:1126:0 1 0:0:3 4 = 00030b00 8800d0237900 2003756561 S Zi:2:003:1 -115:1:1126 1 -18:0:3 4 8800d0237600 2003757557 C Zi:2:003:1 0:1:1127:0 1 0:0:3 4 = 00030b00 8800d0237600 2003757565 S Zi:2:003:1 -115:1:1127 1 -18:0:3 4 880036e14000 2003758499 C Zo:2:003:1 0:1:1116:0 5 0:0:264 0:264:264 0:528:264 0:792:264 0:1056:264 1320 880036e14000 2003758507 S Zo:2:003:1 -115:1:1116 6 -18:0:264 -18:264:264 -18:528:264 -18:792:264 -18:1056:264 1584 = 1761e712 8ded1cce e21323ec 1264ec08 caf607e0 f7ff1500 0823f703 28fc1409 8800d0230400 2003758511 C Zi:2:003:1 0:1:1128:0 1 0:0:3 4 = 00030b00 8800d0230400 2003758512 S Zi:2:003:1 -115:1:1128 1 -18:0:3 4 8800d0230100 2003759550 C Zi:2:003:1 0:1:1129:0 1 0:0:3 4 = 00030b00 8800d0230100 2003759559 S Zi:2:003:1 -115:1:1129 1 -18:0:3 4 8800d0237900 2003760554 C Zi:2:003:1 0:1:1130:0 1 0:0:3 4 = 00030b00 8800d0237900 2003760563 S Zi:2:003:1 -115:1:1130 1 -18:0:3 4 8800d0237600 2003761552 C Zi:2:003:1 0:1:1131:0 1 0:0:3 4 = 00030b00 8800d0237600 2003761561 S Zi:2:003:1 -115:1:1131 1 -18:0:3 4 8800d0230400 2003762512 C Zi:2:003:1 0:1:1132:0 1 0:0:3 4 = 00030b00 8800d0230400 2003762515 S Zi:2:003:1 -115:1:1132 1 -18:0:3 4 880036e14600 2003763509 C Zo:2:003:1 0:1:1121:0 5 0:0:264 0:264:270 0:534:264 0:798:264 0:1062:264 1326 880036e14600 2003763519 S Zo:2:003:1 -115:1:1121 5 -18:0:264 -18:264:264 -18:528:264 -18:792:264 -18:1056:264 1320 = 26acd81f 9fe02ac2 d423c1db 2f70d027 1fd82b7f d424d5da 28b0d623 35dc2e61 8800d0230100 2003763524 C Zi:2:003:1 0:1:1133:0 1 0:0:3 4 = 00030b00 8800d0230100 2003763526 S Zi:2:003:1 -115:1:1133 1 -18:0:3 4 8800d0237900 2003764553 C Zi:2:003:1 0:1:1134:0 1 0:0:3 4 = 00030b00 8800d0237900 2003764562 S Zi:2:003:1 -115:1:1134 1 -18:0:3 4 8800d0237600 2003765552 C Zi:2:003:1 0:1:1135:0 1 0:0:3 4 = 00030b00 8800d0237600 2003765561 S Zi:2:003:1 -115:1:1135 1 -18:0:3 4
Re: USB 3.0 Isochronous audio
On 31 March 2014 23:00, Greg KH g...@kroah.com wrote: On Mon, Mar 31, 2014 at 10:17:20PM +0200, Russel Hughes wrote: Hi, Thanks for replying. I can use a some USB audio devices, ones based around the Ti PCM2704 are fine, the DAC I want to use is called an audiolab MDAC and as I said it has an elasticity buffer, this sits at 50% full and is rock solid, as it should do, on USB 2.0 devices under Ubuntu 12.04 LTS fully patched ASRock 330 but not on the 12.04 LTS fully patched Intel NUC, where it reaches a maximum of 20% is highly erratic and drops out from time to time. The lsmod output is as follows: I have no idea what kernel release Ubuntu is using, but I suggest, if you have issues with that specific kernel, filing a bug with Ubuntu. Otherwise, if you can run a kernel.org release, can you please try 3.14 and see if that changes anything or not? thanks, greg k-h I think I have changed the kernel: uname -r 3.14.0-031400-generic But it has exactly the same problem. I will do a usbmon when I get time and post the results back here as requested. I dont know if its of any interest but the HDMI audio stopped working so I had to switch back to the old kernel, then it worked again. Thanks -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
USB 3.0 Isochronous audio
Hi, Does anyone know when isochronous audio will be implemented for USB 3.0 in Linux? I have asked Intel who make the NUC device I use and they are not interested and on Ubuntu forums got no reply. I have an Audiolab MDAC which cannot be used with USB 3.0 because of this, I have to route the audio via HDMI and out of the TV optical to get sound. USB is better as there is an elasticity buffer on the DAC which means that jitter is lower, I am a sad hi- fi nerd as you will of guessed. I cannot program but I work with hardware and have access to a USB 2.0 bus analyser, I will check if it has been updated to 3.0, so if anyone wants help looking for lost data packets etc, I may be able to help. Thanks in advance! BR -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: USB 3.0 Isochronous audio
On Mon, Mar 31, 2014 at 08:44:00AM +0200, Russel Hughes wrote: Hi, Does anyone know when isochronous audio will be implemented for USB 3.0 in Linux? What specific specification are you referring to that we do not already support? I can use a USB audio device just fine with a USB 3.0 host at the moment, what exact driver are you having problems with? thanks, greg k-h -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: USB 3.0 Isochronous audio
Hi, Thanks for replying. I can use a some USB audio devices, ones based around the Ti PCM2704 are fine, the DAC I want to use is called an audiolab MDAC and as I said it has an elasticity buffer, this sits at 50% full and is rock solid, as it should do, on USB 2.0 devices under Ubuntu 12.04 LTS fully patched ASRock 330 but not on the 12.04 LTS fully patched Intel NUC, where it reaches a maximum of 20% is highly erratic and drops out from time to time. The lsmod output is as follows: snd_usb_audio 146849 1 snd_usbmidi_lib29477 1 snd_usb_audio hid_generic12540 0 snd_hda_codec_realtek80192 1 snd_hda_codec_hdmi 37463 1 coretemp 13596 0 kvm_intel 137928 0 kvm 452238 1 kvm_intel ghash_clmulni_intel13259 0 aesni_intel55495 0 ablk_helper13597 1 aesni_intel cryptd 20530 3 ghash_clmulni_intel,aesni_intel,ablk_helper lrw13323 1 aesni_intel aes_x86_64 17255 1 aesni_intel xts12951 1 aesni_intel gf128mul 14951 2 lrw,xts snd_hda_intel 44339 5 snd_hda_codec 141761 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel snd_hwdep 13668 2 snd_usb_audio,snd_hda_codec microcode 23075 0 snd_pcm 102477 4 snd_usb_audio,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec snd_seq_midi 13324 0 snd_rawmidi30417 2 snd_usbmidi_lib,snd_seq_midi snd_seq_midi_event 14899 1 snd_seq_midi snd_seq61930 2 snd_seq_midi,snd_seq_midi_event joydev 17613 0 rfcomm 47922 0 snd_timer 29989 2 snd_pcm,snd_seq snd_seq_device 14497 3 snd_seq_midi,snd_rawmidi,snd_seq bnep 18399 2 bluetooth 247324 10 rfcomm,bnep nuvoton_cir17980 0 rc_core26422 1 nuvoton_cir parport_pc 28284 1 ppdev 17113 0 i915 621562 3 snd69533 24 snd_usb_audio,snd_usbmidi_lib,snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device drm_kms_helper 49597 1 i915 mac_hid13253 0 drm 287796 4 i915,drm_kms_helper i2c_algo_bit 13564 1 i915 lpc_ich17144 0 video 19652 1 i915 soundcore 12680 1 snd snd_page_alloc 18798 2 snd_hda_intel,snd_pcm mei45974 0 binfmt_misc17540 1 lp 17799 0 parport46562 3 parport_pc,ppdev,lp hid_logitech 26634 0 ff_memless 13097 1 hid_logitech usbhid 47346 1 hid_logitech hid 105826 3 hid_generic,hid_logitech,usbhid ahci 25879 2 libahci31636 1 ahci e1000e202746 0 On 31 March 2014 22:02, Greg KH g...@kroah.com wrote: On Mon, Mar 31, 2014 at 08:44:00AM +0200, Russel Hughes wrote: Hi, Does anyone know when isochronous audio will be implemented for USB 3.0 in Linux? What specific specification are you referring to that we do not already support? I can use a USB audio device just fine with a USB 3.0 host at the moment, what exact driver are you having problems with? thanks, greg k-h -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: USB 3.0 Isochronous audio
On Mon, Mar 31, 2014 at 10:17:20PM +0200, Russel Hughes wrote: Hi, Thanks for replying. I can use a some USB audio devices, ones based around the Ti PCM2704 are fine, the DAC I want to use is called an audiolab MDAC and as I said it has an elasticity buffer, this sits at 50% full and is rock solid, as it should do, on USB 2.0 devices under Ubuntu 12.04 LTS fully patched ASRock 330 but not on the 12.04 LTS fully patched Intel NUC, where it reaches a maximum of 20% is highly erratic and drops out from time to time. The lsmod output is as you need to grab information of the error. lsusb alone doesn't provide a lot of information (unless someone has dealt with the same error in a NUC). Can you describe the actual problem ? How can you trigger it ? What are you doing when the problem arises ? Do you hear audio glitches or does the device disconnect ? Do you have a crash ? Does the *same* device work on other setups ? Try to capture a usbmon trace of the failure, that's likely to help. -- balbi signature.asc Description: Digital signature
Re: USB 3.0 Isochronous audio
On Mon, Mar 31, 2014 at 10:17:20PM +0200, Russel Hughes wrote: Hi, Thanks for replying. I can use a some USB audio devices, ones based around the Ti PCM2704 are fine, the DAC I want to use is called an audiolab MDAC and as I said it has an elasticity buffer, this sits at 50% full and is rock solid, as it should do, on USB 2.0 devices under Ubuntu 12.04 LTS fully patched ASRock 330 but not on the 12.04 LTS fully patched Intel NUC, where it reaches a maximum of 20% is highly erratic and drops out from time to time. The lsmod output is as follows: I have no idea what kernel release Ubuntu is using, but I suggest, if you have issues with that specific kernel, filing a bug with Ubuntu. Otherwise, if you can run a kernel.org release, can you please try 3.14 and see if that changes anything or not? thanks, greg k-h -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: USB 3.0 Isochronous audio
Playing any audio via spotify, youtube, BBC iplayer, XBMC causes the problem. The problem is the audio glitches, its never crashed, as I said the same device works flawlessly on a USB2.0 device amd has done for about two years. Even with no music playing the buffer level changes, the problem. I have seen this which is interesting https://forums.presonus.com/posts/list/33427.page I will try and get usbmon working tomorrow but it seems its a known Intel issue, I dont know if you can manage a software workaround. Errata 1. USB Isoch In Transfer Error Issue Problem: If a USB full-speed inbound isochronous transaction with a packet length 190 bytes or greater is started near the end of a microframe the PCH may see more than 189 bytes in the next microframe. Implication: If the PCH sees more than 189 bytes for a microframe an error will be sent to software and the isochronous transfer will be lost. If a single data packet is lost no perceptible impact for the end user is expected. Note: Intel has only observed the issue in a synthetic test environment where precise control of packet scheduling is available, and has not observed this failure in its compatibility validation testing. * Isochronous traffic is periodic and cannot be retried thus it is considered good practice for software to schedule isochronous transactions to start at the beginning of a microframe. Known software solutions follow this practice. * To sensitize the system to the issue additional traffic such as other isochronous transactions or retries of asynchronous transactions would be required to push the inbound isochronous transaction to the end of the microframe. Workaround: None. Status: No Plan to Fix. On 31 March 2014 22:32, Felipe Balbi ba...@ti.com wrote: On Mon, Mar 31, 2014 at 10:17:20PM +0200, Russel Hughes wrote: Hi, Thanks for replying. I can use a some USB audio devices, ones based around the Ti PCM2704 are fine, the DAC I want to use is called an audiolab MDAC and as I said it has an elasticity buffer, this sits at 50% full and is rock solid, as it should do, on USB 2.0 devices under Ubuntu 12.04 LTS fully patched ASRock 330 but not on the 12.04 LTS fully patched Intel NUC, where it reaches a maximum of 20% is highly erratic and drops out from time to time. The lsmod output is as you need to grab information of the error. lsusb alone doesn't provide a lot of information (unless someone has dealt with the same error in a NUC). Can you describe the actual problem ? How can you trigger it ? What are you doing when the problem arises ? Do you hear audio glitches or does the device disconnect ? Do you have a crash ? Does the *same* device work on other setups ? Try to capture a usbmon trace of the failure, that's likely to help. -- balbi -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: USB 3.0 Isochronous audio
OK sure. I guess there are plenty guides on how to do it out there but if you have one you can recommend it would be good. Its not a disaster if the system gets trashed but it would be nice if it didnt, I did ask on Ubuntu forums but no one replied, thats why I am here!. Thanks Russel On 31 March 2014 23:00, Greg KH g...@kroah.com wrote: On Mon, Mar 31, 2014 at 10:17:20PM +0200, Russel Hughes wrote: Hi, Thanks for replying. I can use a some USB audio devices, ones based around the Ti PCM2704 are fine, the DAC I want to use is called an audiolab MDAC and as I said it has an elasticity buffer, this sits at 50% full and is rock solid, as it should do, on USB 2.0 devices under Ubuntu 12.04 LTS fully patched ASRock 330 but not on the 12.04 LTS fully patched Intel NUC, where it reaches a maximum of 20% is highly erratic and drops out from time to time. The lsmod output is as follows: I have no idea what kernel release Ubuntu is using, but I suggest, if you have issues with that specific kernel, filing a bug with Ubuntu. Otherwise, if you can run a kernel.org release, can you please try 3.14 and see if that changes anything or not? thanks, greg k-h -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: USB 3.0 Isochronous audio
Hi, (please don't top-post) On Mon, Mar 31, 2014 at 11:08:58PM +0200, Russel Hughes wrote: Playing any audio via spotify, youtube, BBC iplayer, XBMC causes the problem. The problem is the audio glitches, its never crashed, as I said the same device works flawlessly on a USB2.0 device amd has done for about two years. Even with no music playing the buffer level changes, the problem. I have seen this which is interesting https://forums.presonus.com/posts/list/33427.page I will try and get usbmon working tomorrow but it seems its a known Intel issue, I dont you really ought to use a kernel.org released kernel. v3.14 vanilla will be the best, as Greg suggested. know if you can manage a software workaround. more of a generic xhci limitation. Matthias, do you know of any bugs/limitations WRT Isoch scheduling in our current xhci driver ? (keeping rest of message below for reference) Errata 1. USB Isoch In Transfer Error Issue Problem: If a USB full-speed inbound isochronous transaction with a packet length 190 bytes or greater is started near the end of a microframe the PCH may see more than 189 bytes in the next microframe. Implication: If the PCH sees more than 189 bytes for a microframe an error will be sent to software and the isochronous transfer will be lost. If a single data packet is lost no perceptible impact for the end user is expected. Note: Intel has only observed the issue in a synthetic test environment where precise control of packet scheduling is available, and has not observed this failure in its compatibility validation testing. * Isochronous traffic is periodic and cannot be retried thus it is considered good practice for software to schedule isochronous transactions to start at the beginning of a microframe. Known software solutions follow this practice. * To sensitize the system to the issue additional traffic such as other isochronous transactions or retries of asynchronous transactions would be required to push the inbound isochronous transaction to the end of the microframe. Workaround: None. Status: No Plan to Fix. On 31 March 2014 22:32, Felipe Balbi ba...@ti.com wrote: On Mon, Mar 31, 2014 at 10:17:20PM +0200, Russel Hughes wrote: Hi, Thanks for replying. I can use a some USB audio devices, ones based around the Ti PCM2704 are fine, the DAC I want to use is called an audiolab MDAC and as I said it has an elasticity buffer, this sits at 50% full and is rock solid, as it should do, on USB 2.0 devices under Ubuntu 12.04 LTS fully patched ASRock 330 but not on the 12.04 LTS fully patched Intel NUC, where it reaches a maximum of 20% is highly erratic and drops out from time to time. The lsmod output is as you need to grab information of the error. lsusb alone doesn't provide a lot of information (unless someone has dealt with the same error in a NUC). Can you describe the actual problem ? How can you trigger it ? What are you doing when the problem arises ? Do you hear audio glitches or does the device disconnect ? Do you have a crash ? Does the *same* device work on other setups ? Try to capture a usbmon trace of the failure, that's likely to help. -- balbi -- balbi signature.asc Description: Digital signature
Re: USB 3.0 Isochronous audio
A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top On Mon, Mar 31, 2014 at 11:17:04PM +0200, Russel Hughes wrote: OK sure. I guess there are plenty guides on how to do it out there but if you have one you can recommend it would be good. Do what? Run a custom kernel? There's a whole book out there that describes how to do this called Linux Kernel in a Nutshell. It's free online if you want to just download it and use that. Otherwise there are plenty of sites that should tell you how to build a kernel and install it on Ubuntu, google is your friend... good luck. greg k-h- -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
USB 3.0 Isochronous audio
Hi, Does anyone know when isochronous audio will be implemented for USB 3.0 in Linux? I have asked Intel who make the NUC device I use and they are not interested and on Ubuntu forums got no reply. I have an Audiolab MDAC which cannot be used with USB 3.0 because of this, I have to route the audio via HDMI and out of the TV optical to get sound. USB is better as there is an elasticity buffer on the DAC which means that jitter is lower, I am a sad hi- fi nerd as you will of guessed. I cannot program but I work with hardware and have access to a USB 2.0 bus analyser, I will check if it has been updated to 3.0, so if anyone wants help looking for lost data packets etc, I may be able to help. Thanks in advance! BR Russel -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
