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