[gentoo-user] Flaky USB 3.0

[gentoo-user] Flaky USB 3.0

[Håkon Alstadheim]

In a nutshell:
My PCIE USB 3.0 card keeps quitting, eg. no light from my laser mouse.
No life in anything I plug in.
Lately I've had three cold starts (that usually will revive the thing) ,
but still no go. Will try unplugging for a couple of minutes next time I
am able to reboot.

General note about the commands and switches below: Most have been found
by trial and error, and the setup used may be utterly WRONG. If you spot
any mistakes, please point them out to me.

Googling around led me to run then following, with the output seen
below. Similar output can be seen right after boot.

------------
root@steam:~# echo 1 > /sys/bus/pci/devices/0000:00:05.0/remove
root@steam:~# dmesg -c
root@steam:~# echo "1" > /sys/bus/pci/rescan
root@steam:~# dmesg -c
[ 3164.999480] pci 0000:00:05.0: [1106:3483] type 00 class 0x0c0330
[ 3165.008397] pci 0000:00:05.0: reg 0x10: [mem 0xf42a4000-0xf42a4fff 64bit]
[ 3165.051792] pci 0000:00:05.0: BAR 0: assigned [mem
0xf4000000-0xf4000fff 64bit]
[ 3165.059245] pci 0000:00:05.0: can't find IRQ for PCI INT A; probably
buggy MP table
[ 3165.075349] pci 0000:00:05.0: xHCI HW did not halt within 16000 usec
status = 0x1004
[ 3165.075961] xhci_hcd 0000:00:05.0: can't find IRQ for PCI INT A;
probably buggy MP table
[ 3165.076150] xhci_hcd 0000:00:05.0: xHCI Host Controller
[ 3165.076157] xhci_hcd 0000:00:05.0: new USB bus registered, assigned
bus number 1
[ 3165.100651] xhci_hcd 0000:00:05.0: Host not halted after 16000
microseconds.
[ 3165.100653] xhci_hcd 0000:00:05.0: can't setup: -110
[ 3165.100655] xhci_hcd 0000:00:05.0: USB bus 1 deregistered
[ 3165.100774] xhci_hcd 0000:00:05.0: init 0000:00:05.0 fail, -110
[ 3165.100776] xhci_hcd: probe of 0000:00:05.0 failed with error -110
-----------------------

This happens on Asus hardware viz:

-------------
# smbios-sys-info
Libsmbios version:      2.2.28
Product Name:           Z10PE-D8 WS
Vendor:                 ASUSTeK COMPUTER INC.
BIOS Version:           1001
-------------
On top of this I'm running Xen, viz:
0:gentoo ~ # xl info
host                   : gentoo
release                : 4.0.9-gentoo
version                : #1 SMP Tue Sep 1 01:10:52 CEST 2015
machine                : x86_64
...
cpu_mhz                : 2394
hw_caps                :
bfebfbff:2c100800:00000000:00007f00:77fefbff:00000000:00000021:000037ab
virt_caps              : hvm hvm_directio
...
xen_version            : 4.5.1
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
...
xen_commandline        : ssd-xen-g-4-00-marker  loglvl=warn
guest_loglvl=warn noreboot iommu=1,verbose iommu_inclusive_mapping=1
com1=115200,8n1 console=com1 dom0_max_vcpus=4 dom0_vcpus_pin=1
dom0_mem=8G,max:8G cpufreq=xen,performance,verbose tmem=1 
dom0_nodes=0,relaxed sched_smt_power_savings=1
cc_compiler            : x86_64-pc-linux-gnu-gcc (Gentoo 4.9.3 p1.2,
pie-0.6.3) 4.9.3
cc_compile_by          :
cc_compile_domain      : alstadheim.priv.no
cc_compile_date        : Mon Aug 31 05:54:06 CEST 2015
xend_config_format     : 4
--------------
Note: 4.0.9 is the gcc compiler version.
--------------
Dom 0 is:
# uname -a
Linux gentoo 4.0.9-gentoo #1 SMP Tue Sep 1 01:10:52 CEST 2015 x86_64
Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz GenuineIntel GNU/Linux
--------------
# cat /proc/cmdline
placeholder root=LABEL=ssdroot ro
xen-pciback.hide=(00:1b.0)(02:00.0)(04:00.0)(81:00.0)(82:00.0)(09:00.0)
console=hvc0 console=vga domodules domdadm dolvm intel_iommu=on
earlyprintk=xen usbip_core.usbip_debug_flag=0 usbcore.autosuspend=-1
----------
The USB card in question is:
root@steam:~# lspci -vvv -s 0000:00:05.0
00:05.0 USB controller: VIA Technologies, Inc. Device 3483 (rev 01)
(prog-if 30 [XHCI])
    Subsystem: VIA Technologies, Inc. Device 3483
    Physical Slot: 5
    Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
    Interrupt: pin A routed to IRQ 10
    Region 0: Memory at f4000000 (64-bit, non-prefetchable) [size=4K]
    Capabilities: [80] Power Management version 3
        Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
        Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
    Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit+
        Address: 0000000000000000  Data: 0000
    Capabilities: [c4] Express (v2) Endpoint, MSI 00
        DevCap:    MaxPayload 256 bytes, PhantFunc 0, Latency L0s <64ns,
L1 <1us
            ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
        DevCtl:    Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
            RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
            MaxPayload 128 bytes, MaxReadReq 512 bytes
        DevSta:    CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+
TransPend-
        LnkCap:    Port #2, Speed 5GT/s, Width x1, ASPM L0s L1, Exit
Latency L0s <2us, L1 <16us
            ClockPM+ Surprise- LLActRep- BwNot-
        LnkCtl:    ASPM Disabled; RCB 64 bytes Disabled- CommClk-
            ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
        LnkSta:    Speed 5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
        DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR-, OBFF
Not Supported
        DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-,
OBFF Disabled
        LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-,
EqualizationPhase1-
             EqualizationPhase2-, EqualizationPhase3-,
LinkEqualizationRequest-
-------------------
... which is pased through to a debian system,  SMP Debian
3.16.7-ckt11-1+deb8u3.
The same flakyness can be observed if I try to use the card in Dom0.
----steam.cfg-file for the DomU----
name = "steam.hvm"
builder = "hvm"
vcpus = 8
cpus="16-23"
memory = 6144
no_migrate = 1
device_model_version="qemu-xen-traditional"
disk = [ '/dev/system/steam,raw,xvda,rw',
'/dev/system/steam-swap,raw,xvdb,rw',
'file:/usr/local/share/xen/cd-images/debian-8.1.0-amd64-netinst.iso,xvdc:cdrom,r'
]
vif = [ 'mac=02:16:3e:00:00:08,model=e1000']
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
boot = 'cd'
acpi = '1'
xen_platform_pci = '1'
sdl = '0'
vnc = '0'
serial = 'pty'
gfx_passthru=1
---
I'v also tried with 'acpi=0'

xen command-line to create the vm: /usr/sbin/xl create steam.hvm
pci=["04:00.0","82:00.0","00:1b.0"]
---
I'm using "soft cpu pinning" (is that the correct term? )  so I do not
think the vcpus are being moved around at all.

What to do ? Is there someplace other than gentoo-user better suited to
helping me getting this card working?

I'v also tried running a Windows 8.1 vm with the same USB-card, no luck
there either, this time around. My hunch is that this is somewhat
hardware-related, but I'm hoping there is some tweak that can be done to
the card to make it more reliable. I'm seeing a lot of similar reports
while googling, but no bulletproof solutions.

I rarely have the time to boot gentoo directly on the bare metal, so I
will not do that unless someone has very good reason to think doing so
could help find a fix that will work under Xen.

Re: [gentoo-user] Flaky USB 3.0 -- typo-fix

[Håkon Alstadheim]

Den 07. sep. 2015 20:26, skrev Håkon Alstadheim:
> In a nutshell:
> My PCIE USB 3.0 card keeps quitting, eg. no light from my laser mouse.
> No life in anything I plug in.
> Lately I've had three cold starts (that usually will revive the thing) ,
> but still no go. Will try unplugging for a couple of minutes next time I
> am able to reboot.
>
> General note about the commands and switches below: Most have been found
> by trial and error, and the setup used may be utterly WRONG. If you spot
> any mistakes, please point them out to me.
>
> Googling around led me to run then following, with the output seen
> below. Similar output can be seen right after boot.
>
> ------------
> root@steam:~# echo 1 > /sys/bus/pci/devices/0000:00:05.0/remove
> root@steam:~# dmesg -c
> root@steam:~# echo "1" > /sys/bus/pci/rescan
> root@steam:~# dmesg -c
> [ 3164.999480] pci 0000:00:05.0: [1106:3483] type 00 class 0x0c0330
> [ 3165.008397] pci 0000:00:05.0: reg 0x10: [mem 0xf42a4000-0xf42a4fff 64bit]
> [ 3165.051792] pci 0000:00:05.0: BAR 0: assigned [mem
> 0xf4000000-0xf4000fff 64bit]
> [ 3165.059245] pci 0000:00:05.0: can't find IRQ for PCI INT A; probably
> buggy MP table
> [ 3165.075349] pci 0000:00:05.0: xHCI HW did not halt within 16000 usec
> status = 0x1004
> [ 3165.075961] xhci_hcd 0000:00:05.0: can't find IRQ for PCI INT A;
> probably buggy MP table
> [ 3165.076150] xhci_hcd 0000:00:05.0: xHCI Host Controller
> [ 3165.076157] xhci_hcd 0000:00:05.0: new USB bus registered, assigned
> bus number 1
> [ 3165.100651] xhci_hcd 0000:00:05.0: Host not halted after 16000
> microseconds.
> [ 3165.100653] xhci_hcd 0000:00:05.0: can't setup: -110
> [ 3165.100655] xhci_hcd 0000:00:05.0: USB bus 1 deregistered
> [ 3165.100774] xhci_hcd 0000:00:05.0: init 0000:00:05.0 fail, -110
> [ 3165.100776] xhci_hcd: probe of 0000:00:05.0 failed with error -110
> -----------------------
>
> This happens on Asus hardware viz:
>
> -------------
> # smbios-sys-info
> Libsmbios version:      2.2.28
> Product Name:           Z10PE-D8 WS
> Vendor:                 ASUSTeK COMPUTER INC.
> BIOS Version:           1001
> -------------
> On top of this I'm running Xen, viz:
> 0:gentoo ~ # xl info
> host                   : gentoo
> release                : 4.0.9-gentoo
> version                : #1 SMP Tue Sep 1 01:10:52 CEST 2015
> machine                : x86_64
> ...
> cpu_mhz                : 2394
> hw_caps                :
> bfebfbff:2c100800:00000000:00007f00:77fefbff:00000000:00000021:000037ab
> virt_caps              : hvm hvm_directio
> ...
> xen_version            : 4.5.1
> xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
> hvm-3.0-x86_32p hvm-3.0-x86_64
> ...
> xen_commandline        : ssd-xen-g-4-00-marker  loglvl=warn
> guest_loglvl=warn noreboot iommu=1,verbose iommu_inclusive_mapping=1
> com1=115200,8n1 console=com1 dom0_max_vcpus=4 dom0_vcpus_pin=1
> dom0_mem=8G,max:8G cpufreq=xen,performance,verbose tmem=1 
> dom0_nodes=0,relaxed sched_smt_power_savings=1
> cc_compiler            : x86_64-pc-linux-gnu-gcc (Gentoo 4.9.3 p1.2,
> pie-0.6.3) 4.9.3
> cc_compile_by          :
> cc_compile_domain      : alstadheim.priv.no
> cc_compile_date        : Mon Aug 31 05:54:06 CEST 2015
> xend_config_format     : 4
> --------------
Corrected: My gcc-version is x86_64-pc-linux-gnu-4.9.3
> --------------
> Dom 0 is:
> # uname -a
> Linux gentoo 4.0.9-gentoo #1 SMP Tue Sep 1 01:10:52 CEST 2015 x86_64
> Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz GenuineIntel GNU/Linux
> --------------
> # cat /proc/cmdline
> placeholder root=LABEL=ssdroot ro
> xen-pciback.hide=(00:1b.0)(02:00.0)(04:00.0)(81:00.0)(82:00.0)(09:00.0)
> console=hvc0 console=vga domodules domdadm dolvm intel_iommu=on
> earlyprintk=xen usbip_core.usbip_debug_flag=0 usbcore.autosuspend=-1
> ----------
> The USB card in question is:
> root@steam:~# lspci -vvv -s 0000:00:05.0
> 00:05.0 USB controller: VIA Technologies, Inc. Device 3483 (rev 01)
> (prog-if 30 [XHCI])
>     Subsystem: VIA Technologies, Inc. Device 3483
>     Physical Slot: 5
>     Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
>     Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
>     Interrupt: pin A routed to IRQ 10
>     Region 0: Memory at f4000000 (64-bit, non-prefetchable) [size=4K]
>     Capabilities: [80] Power Management version 3
>         Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>         Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
>     Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit+
>         Address: 0000000000000000  Data: 0000
>     Capabilities: [c4] Express (v2) Endpoint, MSI 00
>         DevCap:    MaxPayload 256 bytes, PhantFunc 0, Latency L0s <64ns,
> L1 <1us
>             ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
>         DevCtl:    Report errors: Correctable- Non-Fatal- Fatal-
> Unsupported-
>             RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
>             MaxPayload 128 bytes, MaxReadReq 512 bytes
>         DevSta:    CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+
> TransPend-
>         LnkCap:    Port #2, Speed 5GT/s, Width x1, ASPM L0s L1, Exit
> Latency L0s <2us, L1 <16us
>             ClockPM+ Surprise- LLActRep- BwNot-
>         LnkCtl:    ASPM Disabled; RCB 64 bytes Disabled- CommClk-
>             ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
>         LnkSta:    Speed 5GT/s, Width x1, TrErr- Train- SlotClk+
> DLActive- BWMgmt- ABWMgmt-
>         DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR-, OBFF
> Not Supported
>         DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-,
> OBFF Disabled
>         LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-,
> EqualizationPhase1-
>              EqualizationPhase2-, EqualizationPhase3-,
> LinkEqualizationRequest-
> -------------------
> ... which is pased through to a debian system,  SMP Debian
> 3.16.7-ckt11-1+deb8u3.
> The same flakyness can be observed if I try to use the card in Dom0.
> ----steam.cfg-file for the DomU----
> name = "steam.hvm"
> builder = "hvm"
> vcpus = 8
> cpus="16-23"
> memory = 6144
> no_migrate = 1
> device_model_version="qemu-xen-traditional"
> disk = [ '/dev/system/steam,raw,xvda,rw',
> '/dev/system/steam-swap,raw,xvdb,rw',
> 'file:/usr/local/share/xen/cd-images/debian-8.1.0-amd64-netinst.iso,xvdc:cdrom,r'
> ]
> vif = [ 'mac=02:16:3e:00:00:08,model=e1000']
> on_poweroff = 'destroy'
> on_reboot = 'restart'
> on_crash = 'restart'
> boot = 'cd'
> acpi = '1'
> xen_platform_pci = '1'
> sdl = '0'
> vnc = '0'
> serial = 'pty'
> gfx_passthru=1
> ---
> I'v also tried with 'acpi=0'
>
> xen command-line to create the vm: /usr/sbin/xl create steam.hvm
> pci=["04:00.0","82:00.0","00:1b.0"]
> ---
> I'm using "soft cpu pinning" (is that the correct term? )  so I do not
> think the vcpus are being moved around at all.
>
> What to do ? Is there someplace other than gentoo-user better suited to
> helping me getting this card working?
>
> I'v also tried running a Windows 8.1 vm with the same USB-card, no luck
> there either, this time around. My hunch is that this is somewhat
> hardware-related, but I'm hoping there is some tweak that can be done to
> the card to make it more reliable. I'm seeing a lot of similar reports
> while googling, but no bulletproof solutions.
>
> I rarely have the time to boot gentoo directly on the bare metal, so I
> will not do that unless someone has very good reason to think doing so
> could help find a fix that will work under Xen.
>
>
>

[gentoo-user] Re: Flaky USB 3.0 -- typo-fix

[walt]

On Mon, 7 Sep 2015 21:23:51 +0200
Håkon Alstadheim <hakon@alstadheim.priv.no> wrote:

> > General note about the commands and switches below: Most have been
> > found by trial and error, and the setup used may be utterly WRONG.

> Corrected: My gcc-version is x86_64-pc-linux-gnu-4.9.3

> > # uname -a
> > Linux gentoo 4.0.9-gentoo #1 SMP Tue Sep 1 01:10:52 CEST 2015 x86_64

I went through some similar pain about a year ago with intermittent and
hard-to-reproduce usb3 errors.  I've snipped so much because I don't
know enough to comment on your details, but I did learn one thing
during my struggle:  the xhci driver is under heavy development, and
bugs are being added and fixed almost every day. 

Based on my experience, I think that trying different versions of the
kernel (maybe even vanilla-kernel?) would give you more useful info
than switching compiler/use flags, etc.

<kernel gossip>  Sarah Sharp was xhci maintainer during my troubles,
and I was sad to learn that she resigned because of Linus's foul and
abusive (and unrepentant) behavior towards other kernel devs.
</kernel gossip>

[gentoo-user] Re: Flaky USB 3.0

[James]

Håkon Alstadheim <hakon <at> alstadheim.priv.no> writes:


> In a nutshell:
> My PCIE USB 3.0 card keeps quitting, eg. no light from my laser mouse.

I see no advantage to using usb3 for a mouse. Try to plug into another
usb port. Look at your mobo manual and find one that is usb-2 and see
if the mouse does not work reliable on that usb-2 port. This should
at least get your mouse working correctly as you experiment/debug
the usb-3 with other devices that need that sort of bw.


hth,
James

Re: [gentoo-user] Re: Flaky USB 3.0

[Håkon Alstadheim]

Den 08. sep. 2015 05:32, skrev James:
> Håkon Alstadheim <hakon <at> alstadheim.priv.no> writes:
>
>
>> In a nutshell:
>> My PCIE USB 3.0 card keeps quitting, eg. no light from my laser mouse.
> I see no advantage to using usb3 for a mouse. Try to plug into another
> usb port. Look at your mobo manual and find one that is usb-2 and see
> if the mouse does not work reliable on that usb-2 port. This should
> at least get your mouse working correctly as you experiment/debug
> the usb-3 with other devices that need that sort of bw.
>
I use the mouse primarily for testing. It is a dead simple device that
always works, it is an old HP mouse. It gives off a nice red light when
the USB bus is operating, so it is easy to spot when there is any sign
of life.

I need a separate PCI device that I can pass through to a Xen domain.
Xen usb is in a bit of a flux at the moment. I've looked online for PCIE
USB 2.x cards, but there are none to be found. For my linux guests I can
use usbip, but I have not found a usbip driver for windows. Anyhow usbip
gets unwieldy when I have several domains that need keyboard&mouse.

The PCIE usb card is still dead, I've found out that ASUS released a new
bios, barely half a year after the last update. Installed the latst BIOS
last night, but the only thing that bought me was another couple of
hours re-entering (from memory) the settings that I needed to get things
working. Back to square one.

Re: [gentoo-user] Flaky USB 3.0 -- typo-fix -- more logs

[Håkon Alstadheim]

Den 07. sep. 2015 21:23, skrev Håkon Alstadheim:
> Den 07. sep. 2015 20:26, skrev Håkon Alstadheim:
>> In a nutshell:
>> My PCIE USB 3.0 card keeps quitting, eg. no light from my laser mouse.
>> No life in anything I plug in.
>> Lately I've had three cold starts (that usually will revive the thing) ,
>> but still no go. Will try unplugging for a couple of minutes next time I
>> am able to reboot.
Did a reboot and tried wiggling some knobs in the bios. Noticed the
mouse lit up while I was in there, but it goes out at once when boot
starts. :/ .
Got a dmesg output from gentoo on the bare metal:

0:gentoo ~ # echo 1 > /sys/bus/pci/devices/0000:04:00.0/remove
0:gentoo ~ # dmesg -c
0:gentoo ~ # echo 1 > /sys/bus/pci/rescan
0:gentoo ~ # dmesg -c
[  863.007306] pci 0000:04:00.0: [1106:3483] type 00 class 0x0c0330
[  863.007331] pci 0000:04:00.0: reg 0x10: [mem 0xc6500000-0xc6500fff 64bit]
[  863.007450] pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[  863.007739] dmar: [Firmware Bug]: RMRR entry for device 04:00.0 is
broken - applying workaround
[  863.018667] pci 0000:04:00.0: BAR 0: assigned [mem
0xc6500000-0xc6500fff 64bit]
[  863.018682] ast 0000:0c:00.0: BAR 6: [??? 0x00000000 flags 0x2] has
bogus alignment
[  863.034924] pci 0000:04:00.0: xHCI HW did not halt within 16000 usec
status = 0x1004
[  863.035127] xhci_hcd 0000:04:00.0: xHCI Host Controller
[  863.035138] xhci_hcd 0000:04:00.0: new USB bus registered, assigned
bus number 7
[  863.059990] xhci_hcd 0000:04:00.0: Host not halted after 16000
microseconds.
[  863.059994] xhci_hcd 0000:04:00.0: can't setup: -110
[  863.059998] xhci_hcd 0000:04:00.0: USB bus 7 deregistered
[  863.060057] xhci_hcd 0000:04:00.0: init 0000:04:00.0 fail, -110
[  863.060063] xhci_hcd: probe of 0000:04:00.0 failed with error -110

---
Now I have got to stop fiddling with this box, need to keep it up 24/7
for at least a week now before I try anything drastic again : - ~
---

>> General note about the commands and switches below: Most have been found
>> by trial and error, and the setup used may be utterly WRONG. If you spot
>> any mistakes, please point them out to me.
>>
>> Googling around led me to run then following, with the output seen
>> below. Similar output can be seen right after boot.
>>
>> ------------
>> root@steam:~# echo 1 > /sys/bus/pci/devices/0000:00:05.0/remove
>> root@steam:~# dmesg -c
>> root@steam:~# echo "1" > /sys/bus/pci/rescan
>> root@steam:~# dmesg -c
>> [ 3164.999480] pci 0000:00:05.0: [1106:3483] type 00 class 0x0c0330
>> [ 3165.008397] pci 0000:00:05.0: reg 0x10: [mem 0xf42a4000-0xf42a4fff 64bit]
>> [ 3165.051792] pci 0000:00:05.0: BAR 0: assigned [mem
>> 0xf4000000-0xf4000fff 64bit]
>> [ 3165.059245] pci 0000:00:05.0: can't find IRQ for PCI INT A; probably
>> buggy MP table
>> [ 3165.075349] pci 0000:00:05.0: xHCI HW did not halt within 16000 usec
>> status = 0x1004
>> [ 3165.075961] xhci_hcd 0000:00:05.0: can't find IRQ for PCI INT A;
>> probably buggy MP table
>> [ 3165.076150] xhci_hcd 0000:00:05.0: xHCI Host Controller
>> [ 3165.076157] xhci_hcd 0000:00:05.0: new USB bus registered, assigned
>> bus number 1
>> [ 3165.100651] xhci_hcd 0000:00:05.0: Host not halted after 16000
>> microseconds.
>> [ 3165.100653] xhci_hcd 0000:00:05.0: can't setup: -110
>> [ 3165.100655] xhci_hcd 0000:00:05.0: USB bus 1 deregistered
>> [ 3165.100774] xhci_hcd 0000:00:05.0: init 0000:00:05.0 fail, -110
>> [ 3165.100776] xhci_hcd: probe of 0000:00:05.0 failed with error -110
>> -----------------------
>>
>> This happens on Asus hardware viz:
>>
>> -------------
>> # smbios-sys-info
>> Libsmbios version:      2.2.28
>> Product Name:           Z10PE-D8 WS
>> Vendor:                 ASUSTeK COMPUTER INC.
>> BIOS Version:           1001
>> -------------
>> On top of this I'm running Xen, viz:
>> 0:gentoo ~ # xl info
>> host                   : gentoo
>> release                : 4.0.9-gentoo
>> version                : #1 SMP Tue Sep 1 01:10:52 CEST 2015
>> machine                : x86_64
>> ...
>> cpu_mhz                : 2394
>> hw_caps                :
>> bfebfbff:2c100800:00000000:00007f00:77fefbff:00000000:00000021:000037ab
>> virt_caps              : hvm hvm_directio
>> ...
>> xen_version            : 4.5.1
>> xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
>> hvm-3.0-x86_32p hvm-3.0-x86_64
>> ...
>> xen_commandline        : ssd-xen-g-4-00-marker  loglvl=warn
>> guest_loglvl=warn noreboot iommu=1,verbose iommu_inclusive_mapping=1
>> com1=115200,8n1 console=com1 dom0_max_vcpus=4 dom0_vcpus_pin=1
>> dom0_mem=8G,max:8G cpufreq=xen,performance,verbose tmem=1 
>> dom0_nodes=0,relaxed sched_smt_power_savings=1
>> cc_compiler            : x86_64-pc-linux-gnu-gcc (Gentoo 4.9.3 p1.2,
>> pie-0.6.3) 4.9.3
>> cc_compile_by          :
>> cc_compile_domain      : alstadheim.priv.no
>> cc_compile_date        : Mon Aug 31 05:54:06 CEST 2015
>> xend_config_format     : 4
>> --------------
> Corrected: My gcc-version is x86_64-pc-linux-gnu-4.9.3
>> --------------
>> Dom 0 is:
>> # uname -a
>> Linux gentoo 4.0.9-gentoo #1 SMP Tue Sep 1 01:10:52 CEST 2015 x86_64
>> Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz GenuineIntel GNU/Linux
>> --------------
>> # cat /proc/cmdline
>> placeholder root=LABEL=ssdroot ro
>> xen-pciback.hide=(00:1b.0)(02:00.0)(04:00.0)(81:00.0)(82:00.0)(09:00.0)
>> console=hvc0 console=vga domodules domdadm dolvm intel_iommu=on
>> earlyprintk=xen usbip_core.usbip_debug_flag=0 usbcore.autosuspend=-1
>> ----------
>> The USB card in question is:
>> root@steam:~# lspci -vvv -s 0000:00:05.0
>> 00:05.0 USB controller: VIA Technologies, Inc. Device 3483 (rev 01)
>> (prog-if 30 [XHCI])
>>     Subsystem: VIA Technologies, Inc. Device 3483
>>     Physical Slot: 5
>>     Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
>> Stepping- SERR- FastB2B- DisINTx-
>>     Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
>> <TAbort- <MAbort- >SERR- <PERR- INTx-
>>     Interrupt: pin A routed to IRQ 10
>>     Region 0: Memory at f4000000 (64-bit, non-prefetchable) [size=4K]
>>     Capabilities: [80] Power Management version 3
>>         Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
>> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>>         Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
>>     Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit+
>>         Address: 0000000000000000  Data: 0000
>>     Capabilities: [c4] Express (v2) Endpoint, MSI 00
>>         DevCap:    MaxPayload 256 bytes, PhantFunc 0, Latency L0s <64ns,
>> L1 <1us
>>             ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
>>         DevCtl:    Report errors: Correctable- Non-Fatal- Fatal-
>> Unsupported-
>>             RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
>>             MaxPayload 128 bytes, MaxReadReq 512 bytes
>>         DevSta:    CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+
>> TransPend-
>>         LnkCap:    Port #2, Speed 5GT/s, Width x1, ASPM L0s L1, Exit
>> Latency L0s <2us, L1 <16us
>>             ClockPM+ Surprise- LLActRep- BwNot-
>>         LnkCtl:    ASPM Disabled; RCB 64 bytes Disabled- CommClk-
>>             ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
>>         LnkSta:    Speed 5GT/s, Width x1, TrErr- Train- SlotClk+
>> DLActive- BWMgmt- ABWMgmt-
>>         DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR-, OBFF
>> Not Supported
>>         DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-,
>> OBFF Disabled
>>         LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-,
>> EqualizationPhase1-
>>              EqualizationPhase2-, EqualizationPhase3-,
>> LinkEqualizationRequest-
>> -------------------
>> ... which is pased through to a debian system,  SMP Debian
>> 3.16.7-ckt11-1+deb8u3.
>> The same flakyness can be observed if I try to use the card in Dom0.
>> ----steam.cfg-file for the DomU----
>> name = "steam.hvm"
>> builder = "hvm"
>> vcpus = 8
>> cpus="16-23"
>> memory = 6144
>> no_migrate = 1
>> device_model_version="qemu-xen-traditional"
>> disk = [ '/dev/system/steam,raw,xvda,rw',
>> '/dev/system/steam-swap,raw,xvdb,rw',
>> 'file:/usr/local/share/xen/cd-images/debian-8.1.0-amd64-netinst.iso,xvdc:cdrom,r'
>> ]
>> vif = [ 'mac=02:16:3e:00:00:08,model=e1000']
>> on_poweroff = 'destroy'
>> on_reboot = 'restart'
>> on_crash = 'restart'
>> boot = 'cd'
>> acpi = '1'
>> xen_platform_pci = '1'
>> sdl = '0'
>> vnc = '0'
>> serial = 'pty'
>> gfx_passthru=1
>> ---
>> I'v also tried with 'acpi=0'
>>
>> xen command-line to create the vm: /usr/sbin/xl create steam.hvm
>> pci=["04:00.0","82:00.0","00:1b.0"]
>> ---
>> I'm using "soft cpu pinning" (is that the correct term? )  so I do not
>> think the vcpus are being moved around at all.
>>
>> What to do ? Is there someplace other than gentoo-user better suited to
>> helping me getting this card working?
>>
>> I'v also tried running a Windows 8.1 vm with the same USB-card, no luck
>> there either, this time around. My hunch is that this is somewhat
>> hardware-related, but I'm hoping there is some tweak that can be done to
>> the card to make it more reliable. I'm seeing a lot of similar reports
>> while googling, but no bulletproof solutions.
>>
>> I rarely have the time to boot gentoo directly on the bare metal, so I
>> will not do that unless someone has very good reason to think doing so
>> could help find a fix that will work under Xen.
>>
>>
>>
>
>

[gentoo-user] Re: Flaky USB 3.0

[James]

Håkon Alstadheim <hakon <at> alstadheim.priv.no> writes:


> >> My PCIE USB 3.0 card keeps quitting, eg. no light from my laser mouse.

> > I see no advantage to using usb3 for a mouse. Try to plug into another
> > usb port. Look at your mobo manual and find one that is usb-2 and see
> > if the mouse does not work reliable on that usb-2 port. This should
> > at least get your mouse working correctly as you experiment/debug
> > the usb-3 with other devices that need that sort of bw.

USB negotiates with devices as to what speed/standard to use. If your 
device only needs a lesser speed (usb 1.1) it's not going to negoiate
with the host for a usb-3 speed. If you want to debug usb3 speeds
you'll need a truly usb 3.0 device. A hi res usb 3.0 camera device
would be keen to test your usb 3.0 buss/chip/negotiations.


> I use the mouse primarily for testing. It is a dead simple device that
> always works, it is an old HP mouse. It gives off a nice red light when
> the USB bus is operating, so it is easy to spot when there is any sign
> of life.


You need to find some usb sniffer software and see what the negotiations
are doing when the device is first hooked up and then running a while.
There are sniffers for windows aplenty, so you might have to do this
diagnostic work under windows. [1] I do not think this list is
complete so look around. Also look in the sources for the usb 3.0
kernel as often the comments are most excellent for device and driver
debugging. Some vendors use several different chipsets for the same
product name, so start looking for the usb chipset for that card/board/device.

Also go through your kernel configs and verify what you need is set
in the kernel properly (and loading if as a module).


hth,
James




[1] http://www.linux-usb.org/tools.html

Re: [gentoo-user] Re: Flaky USB 3.0

[Håkon Alstadheim]

> Den 8. sep. 2015 kl. 17.07 skrev James <wireless@tampabay.rr.com>:
> 
> Håkon Alstadheim <hakon <at> alstadheim.priv.no> writes:
> 
> 
>>>> My PCIE USB 3.0 card keeps quitting, eg. no light from my laser mouse.
> 
>>> I see no advantage to using usb3 for a mouse. Try to plug into another
>>> usb port. Look at your mobo manual and find one that is usb-2 and see
>>> if the mouse does not work reliable on that usb-2 port. This should
>>> at least get your mouse working correctly as you experiment/debug
>>> the usb-3 with other devices that need that sort of bw.


I need the separate PCIE device so I can pass it through to a virtual machine. There are no USB 2.x PCIE cards that I know of. 
> 
> USB negotiates with devices as to what speed/standard to use. If your 
> device only needs a lesser speed (usb 1.1) it's not going to negoiate
> with the host for a usb-3 speed. If you want to debug usb3 speeds
> you'll need a truly usb 3.0 device. A hi res usb 3.0 camera device
> would be keen to test your usb 3.0 buss/chip/negotiations.
> 
I posted a log saying something about interrupt not working, so I would think it fails before there is any traffic on the USB bus. If there is anything to see, wireshark is supposed to be able to capture it. I'll see if I can get it set up.
> 
>> I use the mouse primarily for testing. It is a dead simple device that
>> always works, it is an old HP mouse. It gives off a nice red light when
>> the USB bus is operating, so it is easy to spot when there is any sign
>> of life.
> 
> 
> You need to find some usb sniffer software and see what the negotiations
> are doing when the device is first hooked up and then running a while.
> There are sniffers for windows aplenty, so you might have to do this
> diagnostic work under windows. [1] I do not think this list is
> complete so look around. Also look in the sources for the usb 3.0
> kernel as often the comments are most excellent for device and driver
> debugging. Some vendors use several different chipsets for the same
> product name, so start looking for the usb chipset for that card/board/device.
> 
> Also go through your kernel configs and verify what you need is set
> in the kernel properly (and loading if as a module).
> 
> 
Yes, I'm sure my settings are worth a look, (kernel and BIOS). Problem is I don't know what I'm looking for. Currently I'm on alert for anything to do with MSI, irq, DMA, RMRR and a whole slew of other thing I barely understand.
> 
> 
> [1] http://www.linux-usb.org/tools.html
Thanks for the link!

Re: [gentoo-user] Re: Flaky USB 3.0

[Fernando Rodriguez]

[-- Attachment #1: Type: text/plain, Size: 2713 bytes --]

On Tuesday, September 08, 2015 3:07:12 PM James wrote:
> Håkon Alstadheim <hakon <at> alstadheim.priv.no> writes:
> 
> 
> > >> My PCIE USB 3.0 card keeps quitting, eg. no light from my laser mouse.
> 
> > > I see no advantage to using usb3 for a mouse. Try to plug into another
> > > usb port. Look at your mobo manual and find one that is usb-2 and see
> > > if the mouse does not work reliable on that usb-2 port. This should
> > > at least get your mouse working correctly as you experiment/debug
> > > the usb-3 with other devices that need that sort of bw.
> 
> USB negotiates with devices as to what speed/standard to use. If your 
> device only needs a lesser speed (usb 1.1) it's not going to negoiate
> with the host for a usb-3 speed. If you want to debug usb3 speeds
> you'll need a truly usb 3.0 device. A hi res usb 3.0 camera device
> would be keen to test your usb 3.0 buss/chip/negotiations.
> 
> 
> > I use the mouse primarily for testing. It is a dead simple device that
> > always works, it is an old HP mouse. It gives off a nice red light when
> > the USB bus is operating, so it is easy to spot when there is any sign
> > of life.
> 
> 
> You need to find some usb sniffer software and see what the negotiations
> are doing when the device is first hooked up and then running a while.
> There are sniffers for windows aplenty, so you might have to do this
> diagnostic work under windows. [1] I do not think this list is
> complete so look around. Also look in the sources for the usb 3.0
> kernel as often the comments are most excellent for device and driver
> debugging. Some vendors use several different chipsets for the same
> product name, so start looking for the usb chipset for that 
card/board/device.
> 
> Also go through your kernel configs and verify what you need is set
> in the kernel properly (and loading if as a module).
> 
> 
> hth,
> James
> 
> 
> 
> 
> [1] http://www.linux-usb.org/tools.html

You can use wireshark to sniff usb traffic, it's not as good at parsing/analyzing 
usb traffic as some windows tools but it works on linux. Though if I understand 
the OP correctly I think he's trying to say that the USB controller is dies, 
if that's the case a usb sniffer won't be very helpful.

Hakon, I googled the errors that you're getting and there's a lot of results, 
mostly related to UEFI booting. There's also some patches but they're old and 
I don't know if they've been commited. You can try disabling all PCI power 
management features on the kernel and see if makes any difference or booting in 
BIOS mode if you're using efi. I would also try the kernel mailing lists.



-- 
Fernando Rodriguez

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [gentoo-user] Re: Flaky USB 3.0

[Daniel Frey]

On 09/08/2015 12:52 PM, Håkon Alstadheim wrote:
> 
>> Den 8. sep. 2015 kl. 17.07 skrev James <wireless@tampabay.rr.com>:
>>
>> Håkon Alstadheim <hakon <at> alstadheim.priv.no> writes:
>>
>>
>>>>> My PCIE USB 3.0 card keeps quitting, eg. no light from my laser mouse.
>>
>>>> I see no advantage to using usb3 for a mouse. Try to plug into another
>>>> usb port. Look at your mobo manual and find one that is usb-2 and see
>>>> if the mouse does not work reliable on that usb-2 port. This should
>>>> at least get your mouse working correctly as you experiment/debug
>>>> the usb-3 with other devices that need that sort of bw.
> 
> 
> I need the separate PCIE device so I can pass it through to a virtual machine. There are no USB 2.x PCIE cards that I know of. 

How about this one?
http://www.startech.com/Cards-Adapters/USB-2/Card/5-Port-USB-20-PCI-Express-Card~PEX400USB2

Startech model # PEX400USB2

It is a 5 port USB2 PCI-e adapter. 4 external, one internal.

That was a bugger to find.

Dan

Re: [gentoo-user] Re: Flaky USB 3.0

[Fernando Rodriguez]

On Tuesday, September 08, 2015 1:26:17 PM Daniel Frey wrote:
> On 09/08/2015 12:52 PM, Håkon Alstadheim wrote:
> > 
> >> Den 8. sep. 2015 kl. 17.07 skrev James <wireless@tampabay.rr.com>:
> >>
> >> Håkon Alstadheim <hakon <at> alstadheim.priv.no> writes:
> >>
> >>
> >>>>> My PCIE USB 3.0 card keeps quitting, eg. no light from my laser mouse.
> >>
> >>>> I see no advantage to using usb3 for a mouse. Try to plug into another
> >>>> usb port. Look at your mobo manual and find one that is usb-2 and see
> >>>> if the mouse does not work reliable on that usb-2 port. This should
> >>>> at least get your mouse working correctly as you experiment/debug
> >>>> the usb-3 with other devices that need that sort of bw.
> > 
> > 
> > I need the separate PCIE device so I can pass it through to a virtual 
machine. There are no USB 2.x PCIE cards that I know of. 
> 
> How about this one?
> http://www.startech.com/Cards-Adapters/USB-2/Card/5-Port-USB-20-PCI-Express-Card~PEX400USB2
> 
> Startech model # PEX400USB2
> 
> It is a 5 port USB2 PCI-e adapter. 4 external, one internal.
> 
> That was a bugger to find.
> 
> Dan

There's a few on ebay too for less than half that price.

-- 
Fernando Rodriguez

Re: [gentoo-user] Re: Flaky USB 3.0

[Håkon Alstadheim]

>>> 
>>> I need the separate PCIE device so I can pass it through to a virtual 
> machine. There are no USB 2.x PCIE cards that I know of. 
>> 
>> How about this one?
>> http://www.startech.com/Cards-Adapters/USB-2/Card/5-Port-USB-20-PCI-Express-Card~PEX400USB2
>> 
>> Startech model # PEX400USB2
>> 
>> It is a 5 port USB2 PCI-e adapter. 4 external, one internal.
>> 

Looks discontinued  "may be available at resellers"

>> That was a bugger to find.
>> 
>> Dan
> 
> There's a few on ebay too for less than half that price.
> 
Yes, ebay may turn out to be my only option. Feels wrong to buy outdated tech though.

Trying a 3.1 card first. Different chipset. Might allow full "docking" functionality, which would be just perfect.

Re: [gentoo-user] Re: Flaky USB 3.0

[Daniel Frey]

On 09/08/2015 04:42 PM, Håkon Alstadheim wrote:
> Yes, ebay may turn out to be my only option. Feels wrong to buy outdated tech though.
> 
> Trying a 3.1 card first. Different chipset. Might allow full "docking" functionality, which would be just perfect.
> 
> 
> 

You're right. It is discontinued, this is its replacement:

http://www.startech.com/Cards-Adapters/USB-2/Card/4-Port-PCI-Express-Low-Profile-High-Speed-USB-Card~PEXUSB4DP

Model PEXUSB4DP. Lots of stock, but ebay will certainly prove to be cheaper.

It comes with both a low profile and normal bracket.

Hopefully the 3.1 card works.

Dan