USB-C dmesg errors

Kernels & Hardware, configuring network, installing services

USB-C dmesg errors

Postby aqwserf » 2017-02-25 15:46

Hi everyone !
I recentyle bought a Dell XPS 13 with a Dell DA200 for ethernet/hdmi/... Everythings work fine with debian unstable on cinnamon. But I found on dmesg logs that my DA200 adaptater display some errors:

Code: Select all
[  720.852911] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
[  720.852934] xhci_hcd 0000:05:00.0: Cannot set link state.
[  720.852946] usb usb4-port1: cannot disable (err = -32)
[  724.944622] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
[  724.944634] xhci_hcd 0000:05:00.0: Cannot set link state.
[  724.944638] usb usb4-port1: cannot disable (err = -32)
[  729.040666] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
[  729.040679] xhci_hcd 0000:05:00.0: Cannot set link state.
[  729.040681] usb usb4-port1: cannot disable (err = -32)
[  733.116794] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
[  733.116817] xhci_hcd 0000:05:00.0: Cannot set link state.
[  733.116847] usb usb4-port1: cannot disable (err = -32)
...


I have to say that the network connectivity works great, as the USB (not try HDMI or VGA).
I think it's a Debian issue because I tried a live Ubuntu (16.10) and there are no errors.
Is anyone has a clue ?

Thanks !
aqwserf
 
Posts: 7
Joined: 2017-02-25 15:39

Re: USB-C dmesg errors

Postby xcablex » 2017-03-06 15:11

Hey,

no clue but the same here. Notebook (Thinkpad x230) is running on Mint 18.1 and I get the same logs on dmesg after notebook wakes up from standby.
Code: Select all
[24235.380990] xhci_hcd 0000:00:14.0: Cannot set link state.
[24235.380997] usb usb4-port1: cannot disable (err = -32)
[24238.620820] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?


This error is running infinite and I can't shutdown the notebook. Have to keep pressed the power button. Seems there is some problem with some usb3 issue.
xcablex
 
Posts: 1
Joined: 2017-03-06 14:56

Re: USB-C dmesg errors

Postby margaretH » 2017-03-11 02:45

man -k usb shows a command to show the usb status of each active device

i do not have the Debian/Linux machine with me at this time or i could find the command and print it here.

as for the power button , usr/share/doc/acpi-support

Debian web site shows these

Package acpi-support-base
jessie (stable) (admin): scripts for handling base ACPI events such as the power button
0.142-6: all

Package: acpi-support (0.142-6)
scripts for handling many ACPI events

dpkg-query -l acpi-support
if it is installed
dpkg-query -L acpi-support | less
margaretH
 
Posts: 14
Joined: 2017-01-23 20:22

Re: USB-C dmesg errors

Postby aqwserf » 2017-03-12 13:04

Hi !
Thanks for the reply.

margaretH wrote:man -k usb shows a command to show the usb status of each active device

i do not have the Debian/Linux machine with me at this time or i could find the command and print it here.

Here it is I think:
Code: Select all
$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 0bda:8153 Realtek Semiconductor Corp.
Bus 003 Device 003: ID 0835:2a01 Action Star Enterprise Co., Ltd
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0c45:670c Microdia
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hu


Or maybe:
Code: Select all
$ usb-devices
T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh=12
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=04.09
S:  Manufacturer=Linux 4.9.0-2-amd64 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=0000:00:14.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=8087 ProdID=0a2b Rev=00.01
C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

T:  Bus=01 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#=  3 Spd=480 MxCh= 0
D:  Ver= 2.01 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0c45 ProdID=670c Rev=56.26
S:  Manufacturer=CN09GTFM7248763IB7N5A01
S:  Product=Integrated_Webcam_HD
C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
I:  If#= 1 Alt= 0 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 6
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev=04.09
S:  Manufacturer=Linux 4.9.0-2-amd64 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=0000:00:14.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 2
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=04.09
S:  Manufacturer=Linux 4.9.0-2-amd64 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=0000:39:00.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 4
D:  Ver= 2.10 Cls=09(hub  ) Sub=00 Prot=02 MxPS=64 #Cfgs=  1
P:  Vendor=05e3 ProdID=0610 Rev=49.63
S:  Manufacturer=GenesysLogic_2
S:  Product=USB2.0 Hub
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#= 0 Alt= 1 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=02 Driver=hub

T:  Bus=03 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 2.01 Cls=11() Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0835 ProdID=2a01 Rev=01.36
S:  Manufacturer=BILLBOARD CLASS
S:  Product=BILLBOARD DEVICE
S:  SerialNumber=CE1611000000000071BC253A00000000
C:  #Ifs= 0 Cfg#= 1 Atr=c0 MxPwr=500mA
cat: '/sys/bus/usb/devices/usb3/3-1/3-1.3/3-*:?.*/bInterfaceNumber': Aucun fichier ou dossier de ce type
cat: '/sys/bus/usb/devices/usb3/3-1/3-1.3/3-*:?.*/bAlternateSetting': Aucun fichier ou dossier de ce type
cat: '/sys/bus/usb/devices/usb3/3-1/3-1.3/3-*:?.*/bNumEndpoints': Aucun fichier ou dossier de ce type
cat: '/sys/bus/usb/devices/usb3/3-1/3-1.3/3-*:?.*/bInterfaceClass': Aucun fichier ou dossier de ce type
cat: '/sys/bus/usb/devices/usb3/3-1/3-1.3/3-*:?.*/bInterfaceSubClass': Aucun fichier ou dossier de ce type
cat: '/sys/bus/usb/devices/usb3/3-1/3-1.3/3-*:?.*/bInterfaceProtocol': Aucun fichier ou dossier de ce type
/usr/bin/usb-devices: ligne 79 : printf: (none): nombre non valable
I:  If#= 0 Alt= 0 #EPs= 0 Cls=() Sub= Prot= Driver=

T:  Bus=03 Lev=02 Prnt=02 Port=03 Cnt=02 Dev#=  4 Spd=480 MxCh= 0
D:  Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  2
P:  Vendor=0bda ProdID=8153 Rev=30.00
S:  Manufacturer=Realtek
S:  Product=USB 10/100/1000 LAN
S:  SerialNumber=000548000000
C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=180mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=00 Driver=r8152

T:  Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 2
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev=04.09
S:  Manufacturer=Linux 4.9.0-2-amd64 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=0000:39:00.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub


The acpi-support and acpi-support-base weren't install but now yes and I still have the errors.

By the way, what's connection between acpi and the usb ?

Finally, I've tried to update the Thunderbolt firmware with a live windows (WinToUsb) and unfortunately nothing changed.... :evil:
aqwserf
 
Posts: 7
Joined: 2017-02-25 15:39

Re: USB-C dmesg errors

Postby debiman » 2017-03-13 18:51

couldn't you just assume for a while that it really could be cable/connector related?

enter
Code: Select all
dmesg -w
and ever so slightly wiggle the connectors/cables.
what happens?
User avatar
debiman
 
Posts: 827
Joined: 2013-03-12 07:18

Re: USB-C dmesg errors

Postby aqwserf » 2017-03-15 17:51

Yes, it is related to the Dell DA200 but it only happen on Debian, not a live Ubuntu 16.10.

Here is the dmesg when I unplug the DA200 (only with the ethernet cable):

Code: Select all
[ 5518.549035] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
[ 5518.549061] xhci_hcd 0000:39:00.0: Cannot set link state.
[ 5518.549074] usb usb4-port1: cannot disable (err = -32)
[ 5520.062037] r8152 3-1.4:1.0 eth0: Rx status -71
[ 5520.062106] r8152 3-1.4:1.0 eth0: Rx status -71
[ 5520.062150] r8152 3-1.4:1.0 eth0: Rx status -71
[ 5520.062189] r8152 3-1.4:1.0 eth0: Rx status -71
[ 5520.062267] r8152 3-1.4:1.0 eth0: Rx status -71
[ 5520.062306] r8152 3-1.4:1.0 eth0: Rx status -71
[ 5520.062346] r8152 3-1.4:1.0 eth0: Rx status -71
[ 5520.062385] r8152 3-1.4:1.0 eth0: Rx status -71
[ 5520.062466] r8152 3-1.4:1.0 eth0: Rx status -71
[ 5520.062506] r8152 3-1.4:1.0 eth0: Rx status -71
[ 5520.062689] usb 3-1: USB disconnect, device number 2
[ 5520.062709] usb 3-1.3: USB disconnect, device number 3
[ 5520.063324] usb 3-1.4: USB disconnect, device number 4
[ 5520.158079] xhci_hcd 0000:39:00.0: remove, state 1
[ 5520.158085] usb usb4: USB disconnect, device number 1
[ 5525.206029] xhci_hcd 0000:39:00.0: Stopped the command ring failed, maybe the host is dead
[ 5525.206055] xhci_hcd 0000:39:00.0: Host not halted after 16000 microseconds.
[ 5525.206059] xhci_hcd 0000:39:00.0: Abort command ring failed
[ 5525.206072] xhci_hcd 0000:39:00.0: HC died; cleaning up
[ 5525.206096] xhci_hcd 0000:39:00.0: Timeout while waiting for configure endpoint command
[ 5525.206620] xhci_hcd 0000:39:00.0: Host not halted after 16000 microseconds.
[ 5525.207638] xhci_hcd 0000:39:00.0: USB bus 4 deregistered
[ 5525.207774] xhci_hcd 0000:39:00.0: remove, state 1
[ 5525.207794] usb usb3: USB disconnect, device number 1
[ 5525.209085] xhci_hcd 0000:39:00.0: USB bus 3 deregistered
[ 5525.211044] pci_bus 0000:03: busn_res: [bus 03] is released
[ 5525.211339] pci_bus 0000:04: busn_res: [bus 04] is released
[ 5525.233712] pci_bus 0000:02: busn_res: [bus 02-05] is released
[ 5527.204460] ACPI Error: [SPRT] Namespace lookup failure, AE_ALREADY_EXISTS (20160831/dswload2-330)
[ 5527.204486] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20160831/psobject-227)
[ 5527.204497] ACPI Error: Method parse/execution failed [\_GPE._E42] (Node ffff9b1c360d7a28), AE_ALREADY_EXISTS (20160831/psparse-543)
[ 5527.204518] ACPI Error: Method parse/execution failed [\_GPE._E42] (Node ffff9b1c360d7a28), AE_ALREADY_EXISTS (20160831/psparse-543)
[ 5527.204544] ACPI Exception: AE_ALREADY_EXISTS, while evaluating GPE method [_E42] (20160831/evgpe-646)
[ 5527.257340] pci 0000:01:00.0: [8086:1576] type 01 class 0x060400
[ 5527.257512] pci 0000:01:00.0: supports D1 D2
[ 5527.257514] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 5527.257732] pci 0000:01:00.0: System wakeup disabled by ACPI
[ 5527.269202] pci 0000:02:00.0: [8086:1576] type 01 class 0x060400
[ 5527.269381] pci 0000:02:00.0: supports D1 D2
[ 5527.269384] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 5527.269548] pci 0000:02:01.0: [8086:1576] type 01 class 0x060400
[ 5527.269728] pci 0000:02:01.0: supports D1 D2
[ 5527.269729] pci 0000:02:01.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 5527.269850] pci 0000:02:02.0: [8086:1576] type 01 class 0x060400
[ 5527.270001] pci 0000:02:02.0: supports D1 D2
[ 5527.270002] pci 0000:02:02.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 5527.270146] pci 0000:01:00.0: PCI bridge to [bus 02-39]
[ 5527.270160] pci 0000:01:00.0:   bridge window [mem 0xc4000000-0xda0fffff]
[ 5527.270170] pci 0000:01:00.0:   bridge window [mem 0xa0000000-0xc1ffffff 64bit pref]
[ 5527.270291] pci 0000:03:00.0: [8086:1575] type 00 class 0x088000
[ 5527.270319] pci 0000:03:00.0: reg 0x10: [mem 0xda000000-0xda03ffff]
[ 5527.270335] pci 0000:03:00.0: reg 0x14: [mem 0xda040000-0xda040fff]
[ 5527.270534] pci 0000:03:00.0: supports D1 D2
[ 5527.270536] pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 5527.270704] pci 0000:02:00.0: PCI bridge to [bus 03]
[ 5527.270717] pci 0000:02:00.0:   bridge window [mem 0xda000000-0xda0fffff]
[ 5527.270819] pci 0000:02:01.0: PCI bridge to [bus 04-38]
[ 5527.270832] pci 0000:02:01.0:   bridge window [mem 0xc4000000-0xd9efffff]
[ 5527.270841] pci 0000:02:01.0:   bridge window [mem 0xa0000000-0xc1ffffff 64bit pref]
[ 5527.270955] pci 0000:39:00.0: [8086:15b5] type 00 class 0x0c0330
[ 5527.270985] pci 0000:39:00.0: reg 0x10: [mem 0xd9f00000-0xd9f0ffff]
[ 5527.271209] pci 0000:39:00.0: supports D1 D2
[ 5527.271211] pci 0000:39:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 5527.271402] pci 0000:02:02.0: PCI bridge to [bus 39]
[ 5527.271416] pci 0000:02:02.0:   bridge window [mem 0xd9f00000-0xd9ffffff]
[ 5527.271457] pci_bus 0000:02: Allocating resources
[ 5527.271508] pci 0000:02:01.0: bridge window [io  0x1000-0x0fff] to [bus 04-38] add_size 1000
[ 5527.271533] pci 0000:02:01.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
[ 5527.271537] pci 0000:01:00.0: bridge window [io  0x1000-0x0fff] to [bus 02-39] add_size 1000
[ 5527.271541] pci 0000:01:00.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
[ 5527.271544] pci 0000:01:00.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
[ 5527.271548] pci 0000:01:00.0: BAR 13: assigned [io  0x2000-0x2fff]
[ 5527.271553] pci 0000:02:01.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
[ 5527.271556] pci 0000:02:01.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
[ 5527.271559] pci 0000:02:01.0: BAR 13: assigned [io  0x2000-0x2fff]
[ 5527.271562] pci 0000:02:00.0: PCI bridge to [bus 03]
[ 5527.271571] pci 0000:02:00.0:   bridge window [mem 0xda000000-0xda0fffff]
[ 5527.271584] pci 0000:02:01.0: PCI bridge to [bus 04-38]
[ 5527.271588] pci 0000:02:01.0:   bridge window [io  0x2000-0x2fff]
[ 5527.271595] pci 0000:02:01.0:   bridge window [mem 0xc4000000-0xd9efffff]
[ 5527.271601] pci 0000:02:01.0:   bridge window [mem 0xa0000000-0xc1ffffff 64bit pref]
[ 5527.271610] pci 0000:02:02.0: PCI bridge to [bus 39]
[ 5527.271617] pci 0000:02:02.0:   bridge window [mem 0xd9f00000-0xd9ffffff]
[ 5527.271629] pci 0000:01:00.0: PCI bridge to [bus 02-39]
[ 5527.271633] pci 0000:01:00.0:   bridge window [io  0x2000-0x2fff]
[ 5527.271640] pci 0000:01:00.0:   bridge window [mem 0xc4000000-0xda0fffff]
[ 5527.271646] pci 0000:01:00.0:   bridge window [mem 0xa0000000-0xc1ffffff 64bit pref]
[ 5527.271862] pcieport 0000:01:00.0: enabling device (0006 -> 0007)
[ 5527.275006] pcieport 0000:02:01.0: enabling device (0006 -> 0007)
[ 5527.277754] xhci_hcd 0000:39:00.0: xHCI Host Controller
[ 5527.277765] xhci_hcd 0000:39:00.0: new USB bus registered, assigned bus number 3
[ 5527.279045] xhci_hcd 0000:39:00.0: hcc params 0x200077c1 hci version 0x110 quirks 0x00009810
[ 5527.279219] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[ 5527.279222] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5527.279225] usb usb3: Product: xHCI Host Controller
[ 5527.279227] usb usb3: Manufacturer: Linux 4.9.0-2-amd64 xhci-hcd
[ 5527.279229] usb usb3: SerialNumber: 0000:39:00.0
[ 5527.280399] hub 3-0:1.0: USB hub found
[ 5527.280417] hub 3-0:1.0: 2 ports detected
[ 5527.280675] xhci_hcd 0000:39:00.0: xHCI Host Controller
[ 5527.280683] xhci_hcd 0000:39:00.0: new USB bus registered, assigned bus number 4
[ 5527.280742] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[ 5527.280745] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5527.280747] usb usb4: Product: xHCI Host Controller
[ 5527.280749] usb usb4: Manufacturer: Linux 4.9.0-2-amd64 xhci-hcd
[ 5527.280752] usb usb4: SerialNumber: 0000:39:00.0
[ 5527.281619] hub 4-0:1.0: USB hub found
[ 5527.281635] hub 4-0:1.0: 2 ports detected
[ 5532.271779] xhci_hcd 0000:39:00.0: remove, state 1
[ 5532.271807] usb usb4: USB disconnect, device number 1
[ 5532.274034] xhci_hcd 0000:39:00.0: Host not halted after 16000 microseconds.
[ 5532.275074] xhci_hcd 0000:39:00.0: USB bus 4 deregistered
[ 5532.275345] xhci_hcd 0000:39:00.0: remove, state 1
[ 5532.275369] usb usb3: USB disconnect, device number 1
[ 5532.276322] xhci_hcd 0000:39:00.0: USB bus 3 deregistered
[ 5532.279164] pci_bus 0000:03: busn_res: [bus 03] is released
[ 5532.279312] pci_bus 0000:04: busn_res: [bus 04-38] is released
[ 5532.300994] pci_bus 0000:39: busn_res: [bus 39] is released
[ 5532.301074] pci_bus 0000:02: busn_res: [bus 02-39] is released


and when I reconnect it:

Code: Select all
[ 5553.379268] ACPI Error: [SPRT] Namespace lookup failure, AE_ALREADY_EXISTS (20160831/dswload2-330)
[ 5553.379297] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20160831/psobject-227)
[ 5553.379308] ACPI Error: Method parse/execution failed [\_GPE._E42] (Node ffff9b1c360d7a28), AE_ALREADY_EXISTS (20160831/psparse-543)
[ 5553.379329] ACPI Error: Method parse/execution failed [\_GPE._E42] (Node ffff9b1c360d7a28), AE_ALREADY_EXISTS (20160831/psparse-543)
[ 5553.379360] ACPI Exception: AE_ALREADY_EXISTS, while evaluating GPE method [_E42] (20160831/evgpe-646)
[ 5553.433220] pci 0000:01:00.0: [8086:1576] type 01 class 0x060400
[ 5553.433374] pci 0000:01:00.0: supports D1 D2
[ 5553.433376] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 5553.433635] pci 0000:01:00.0: System wakeup disabled by ACPI
[ 5553.445078] pci 0000:02:00.0: [8086:1576] type 01 class 0x060400
[ 5553.445260] pci 0000:02:00.0: supports D1 D2
[ 5553.445262] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 5553.445403] pci 0000:02:01.0: [8086:1576] type 01 class 0x060400
[ 5553.445583] pci 0000:02:01.0: supports D1 D2
[ 5553.445586] pci 0000:02:01.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 5553.445733] pci 0000:02:02.0: [8086:1576] type 01 class 0x060400
[ 5553.445893] pci 0000:02:02.0: supports D1 D2
[ 5553.445895] pci 0000:02:02.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 5553.446060] pci 0000:01:00.0: PCI bridge to [bus 02-39]
[ 5553.446073] pci 0000:01:00.0:   bridge window [mem 0xc4000000-0xda0fffff]
[ 5553.446081] pci 0000:01:00.0:   bridge window [mem 0xa0000000-0xc1ffffff 64bit pref]
[ 5553.446163] pci 0000:02:00.0: PCI bridge to [bus 03]
[ 5553.446175] pci 0000:02:00.0:   bridge window [mem 0xda000000-0xda0fffff]
[ 5553.446261] pci 0000:02:01.0: PCI bridge to [bus 04-38]
[ 5553.446272] pci 0000:02:01.0:   bridge window [mem 0xc4000000-0xd9efffff]
[ 5553.446280] pci 0000:02:01.0:   bridge window [mem 0xa0000000-0xc1ffffff 64bit pref]
[ 5553.446374] pci 0000:39:00.0: [8086:15b5] type 00 class 0x0c0330
[ 5553.446400] pci 0000:39:00.0: reg 0x10: [mem 0xd9f00000-0xd9f0ffff]
[ 5553.446606] pci 0000:39:00.0: supports D1 D2
[ 5553.446608] pci 0000:39:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 5553.446772] pci 0000:02:02.0: PCI bridge to [bus 39]
[ 5553.446784] pci 0000:02:02.0:   bridge window [mem 0xd9f00000-0xd9ffffff]
[ 5553.446821] pci_bus 0000:02: Allocating resources
[ 5553.446861] pci 0000:02:01.0: bridge window [io  0x1000-0x0fff] to [bus 04-38] add_size 1000
[ 5553.446884] pci 0000:02:01.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
[ 5553.446887] pci 0000:01:00.0: bridge window [io  0x1000-0x0fff] to [bus 02-39] add_size 1000
[ 5553.446891] pci 0000:01:00.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
[ 5553.446893] pci 0000:01:00.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
[ 5553.446897] pci 0000:01:00.0: BAR 13: assigned [io  0x2000-0x2fff]
[ 5553.446901] pci 0000:02:01.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
[ 5553.446903] pci 0000:02:01.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
[ 5553.446905] pci 0000:02:01.0: BAR 13: assigned [io  0x2000-0x2fff]
[ 5553.446908] pci 0000:02:00.0: PCI bridge to [bus 03]
[ 5553.446916] pci 0000:02:00.0:   bridge window [mem 0xda000000-0xda0fffff]
[ 5553.446927] pci 0000:02:01.0: PCI bridge to [bus 04-38]
[ 5553.446930] pci 0000:02:01.0:   bridge window [io  0x2000-0x2fff]
[ 5553.446937] pci 0000:02:01.0:   bridge window [mem 0xc4000000-0xd9efffff]
[ 5553.446942] pci 0000:02:01.0:   bridge window [mem 0xa0000000-0xc1ffffff 64bit pref]
[ 5553.446950] pci 0000:02:02.0: PCI bridge to [bus 39]
[ 5553.446957] pci 0000:02:02.0:   bridge window [mem 0xd9f00000-0xd9ffffff]
[ 5553.446968] pci 0000:01:00.0: PCI bridge to [bus 02-39]
[ 5553.446971] pci 0000:01:00.0:   bridge window [io  0x2000-0x2fff]
[ 5553.446978] pci 0000:01:00.0:   bridge window [mem 0xc4000000-0xda0fffff]
[ 5553.446983] pci 0000:01:00.0:   bridge window [mem 0xa0000000-0xc1ffffff 64bit pref]
[ 5553.447164] pcieport 0000:01:00.0: enabling device (0006 -> 0007)
[ 5553.447763] pcieport 0000:02:01.0: enabling device (0006 -> 0007)
[ 5553.448629] xhci_hcd 0000:39:00.0: xHCI Host Controller
[ 5553.448637] xhci_hcd 0000:39:00.0: new USB bus registered, assigned bus number 3
[ 5553.450185] xhci_hcd 0000:39:00.0: hcc params 0x200077c1 hci version 0x110 quirks 0x00009810
[ 5553.450343] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[ 5553.450346] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5553.450348] usb usb3: Product: xHCI Host Controller
[ 5553.450349] usb usb3: Manufacturer: Linux 4.9.0-2-amd64 xhci-hcd
[ 5553.450351] usb usb3: SerialNumber: 0000:39:00.0
[ 5553.450566] hub 3-0:1.0: USB hub found
[ 5553.450578] hub 3-0:1.0: 2 ports detected
[ 5553.450720] xhci_hcd 0000:39:00.0: xHCI Host Controller
[ 5553.450725] xhci_hcd 0000:39:00.0: new USB bus registered, assigned bus number 4
[ 5553.450772] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[ 5553.450774] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5553.450776] usb usb4: Product: xHCI Host Controller
[ 5553.450778] usb usb4: Manufacturer: Linux 4.9.0-2-amd64 xhci-hcd
[ 5553.450780] usb usb4: SerialNumber: 0000:39:00.0
[ 5553.450969] hub 4-0:1.0: USB hub found
[ 5553.450979] hub 4-0:1.0: 2 ports detected
[ 5553.780902] usb 3-1: new high-speed USB device number 2 using xhci_hcd
[ 5553.925558] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610
[ 5553.925567] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5553.925573] usb 3-1: Product: USB2.0 Hub
[ 5553.925577] usb 3-1: Manufacturer: GenesysLogic_2
[ 5553.927137] hub 3-1:1.0: USB hub found
[ 5553.927604] hub 3-1:1.0: 4 ports detected
[ 5554.216854] usb 3-1.3: new full-speed USB device number 3 using xhci_hcd
[ 5554.320420] usb 3-1.3: config 1 has no interfaces?
[ 5554.322072] usb 3-1.3: New USB device found, idVendor=0835, idProduct=2a01
[ 5554.322074] usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5554.322076] usb 3-1.3: Product: BILLBOARD DEVICE
[ 5554.322078] usb 3-1.3: Manufacturer: BILLBOARD CLASS
[ 5554.322079] usb 3-1.3: SerialNumber: CE1611000000000071BC253A00000000
[ 5554.401062] usb 3-1.4: new high-speed USB device number 4 using xhci_hcd
[ 5554.502079] usb 3-1.4: New USB device found, idVendor=0bda, idProduct=8153
[ 5554.502091] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 5554.502098] usb 3-1.4: Product: USB 10/100/1000 LAN
[ 5554.502104] usb 3-1.4: Manufacturer: Realtek
[ 5554.502110] usb 3-1.4: SerialNumber: 000548000000
[ 5554.589128] usb 3-1.4: reset high-speed USB device number 4 using xhci_hcd
[ 5554.696633] r8152 3-1.4:1.0 (unnamed net_device) (uninitialized): Using pass-thru MAC addr 28:f1:0e:4c:50:db
[ 5554.750561] r8152 3-1.4:1.0 eth0: v1.08.7
[ 5554.894423] r8152 3-1.4:1.0 enx28f10e4c50db: renamed from eth0
[ 5554.914299] IPv6: ADDRCONF(NETDEV_UP): enx28f10e4c50db: link is not ready
[ 5554.943290] IPv6: ADDRCONF(NETDEV_UP): enx28f10e4c50db: link is not ready
[ 5557.756066] IPv6: ADDRCONF(NETDEV_CHANGE): enx28f10e4c50db: link becomes ready
[ 5557.901016] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
[ 5557.901025] xhci_hcd 0000:39:00.0: Cannot set link state.
[ 5557.901027] usb usb4-port1: cannot disable (err = -32)
[ 5558.513376] pci_bus 0000:02: Allocating resources
[ 5562.029076] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
[ 5562.029099] xhci_hcd 0000:39:00.0: Cannot set link state.
[ 5562.029112] usb usb4-port1: cannot disable (err = -32)
[ 5566.116892] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
[ 5566.116915] xhci_hcd 0000:39:00.0: Cannot set link state.
[ 5566.116928] usb usb4-port1: cannot disable (err = -32)
...


Does anyone see something wrong ?

Thanks !
aqwserf
 
Posts: 7
Joined: 2017-02-25 15:39

Re: USB-C dmesg errors

Postby debiman » 2017-03-15 20:06

aqwserf wrote:Does anyone see something wrong ?

did you?
User avatar
debiman
 
Posts: 827
Joined: 2013-03-12 07:18

Re: USB-C dmesg errors

Postby aqwserf » 2017-03-16 16:42

Except these one:

Code: Select all
[ 5553.379268] ACPI Error: [SPRT] Namespace lookup failure, AE_ALREADY_EXISTS (20160831/dswload2-330)
[ 5553.379297] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20160831/psobject-227)
[ 5553.379308] ACPI Error: Method parse/execution failed [\_GPE._E42] (Node ffff9b1c360d7a28), AE_ALREADY_EXISTS (20160831/psparse-543)
[ 5553.379329] ACPI Error: Method parse/execution failed [\_GPE._E42] (Node ffff9b1c360d7a28), AE_ALREADY_EXISTS (20160831/psparse-543)
[ 5553.379360] ACPI Exception: AE_ALREADY_EXISTS, while evaluating GPE method [_E42] (20160831/evgpe-646)


which as I saw is related to a BIOS bug. If so, why everything is allright in my live Ubuntu ?

I guess these errors (usb cable...) are related to my Debian and I can't find where it come.
aqwserf
 
Posts: 7
Joined: 2017-02-25 15:39

Re: USB-C dmesg errors

Postby aqwserf » 2017-03-23 16:03

Nobody ? Did I say something stupid in my previous post? Maybe it is obvious but not for me...

Thanks !
aqwserf
 
Posts: 7
Joined: 2017-02-25 15:39

Re: USB-C dmesg errors

Postby debiman » 2017-03-24 06:16

aqwserf wrote:Did I say something stupid in my previous post? Maybe it is obvious but not for me...

no, you didn't, and no, it isn't obvious to me, either, and presumably not to anyone else, either, or they would have chimed in already.

generally speaking, you are using debian unstable, which requires an ability to deal with unstability and other issues (regularly broken package updates from what i hear - not that i have any personal experience).
it also means that if you discover a bug or similar irregularity, you'll be expected to do a lot of legwork to investigate and confirm at the very least. only then can you start looking for a solution together.
i'm not doing things like that, which is why i chose a much more stable distro.

from what i see, this:
aqwserf wrote:Yes, it is related to the Dell DA200 but it only happen on Debian, not a live Ubuntu 16.10.

could be a pointer
and so could this:
Code: Select all
AE_ALREADY_EXISTS
- if you're 100% sure that it's related to your original assumption.
searching the web for meaningful & exact string error messages like this can be helpful.

apart from that, be glad everything is working.
from what i hear, using debian unstable can be a much more exiting experience.
:mrgreen:
User avatar
debiman
 
Posts: 827
Joined: 2013-03-12 07:18

Re: USB-C dmesg errors

Postby aqwserf » 2017-03-24 17:18

oh ok ;-)

thanks for the explanation. I've done some other tests:

- debian: bandwidth around 40Mo/s on LAN (local nvme disk)
- ubuntu live 16.10: 30Mo/s on LAN (ramdisk)

I don't know why but it may related to the DA200 which can have a issue.

And actually I know for debian unstable :) I work with it for many years and I don't have any issues with it.

I'm gonna contact Dell for informations.

Thanks !

P.S: by the way, what's your distro ?
aqwserf
 
Posts: 7
Joined: 2017-02-25 15:39

Re: USB-C dmesg errors

Postby debiman » 2017-03-24 17:54

aqwserf wrote:I'm gonna contact Dell for informations.
information on why the card is misbehaving on debian unstable?? good luck with that, lol.
P.S: by the way, what's your distro ?

archlinux, debian jessie
User avatar
debiman
 
Posts: 827
Joined: 2013-03-12 07:18

Re: USB-C dmesg errors

Postby pendrachken » 2017-03-26 14:35

What kernels are you using with SID and Ubuntu? I seem to recall that there was some changes in more recent kernels for USB 3.x and USB-C drivers. You could try a kernel from the same release series in SID as the series is in Ubuntu, and see if that takes care of the problem.



Other than that, if there are no issues with the working of the devices I wouldn't worry too much about these "error" messages. You can definitely keep looking into what is causing them to file bug reports, but I wouldn't worry over-much about anything since the devices are up and actually working.
fortune -o
Your love life will be... interesting.
:twisted: How did it know?

The U.S. uses the metric system too, we have tenths, hundredths and thousandths of inches :-P
pendrachken
 
Posts: 1242
Joined: 2007-03-04 21:10
Location: U.S.A. - WI.

Re: USB-C dmesg errors

Postby aqwserf » 2017-03-28 19:02

pendrachken wrote:What kernels are you using with SID and Ubuntu?

I'm using this one:
Code: Select all
Linux foobar 4.9.0-2-amd64 #1 SMP Debian 4.9.13-1 (2017-02-27) x86_64 GNU/Linux


pendrachken wrote:I seem to recall that there was some changes in more recent kernels for USB 3.x and USB-C drivers. You could try a kernel from the same release series in SID as the series is in Ubuntu, and see if that takes care of the problem.


Good to hear !! But for now, and I'm still surpris, there is no more errors messages like this in my dmesg :mrgreen:

I don't know why. I've tried with other usb things inside (key, phones...), disable/enable network, enable/disable wifi, unplug/plug, NO MORE ERROR MESSAGES !!

In fact, yes, there are some error messages:

Code: Select all
[ 8687.728310] ACPI Error: [SPRT] Namespace lookup failure, AE_ALREADY_EXISTS (20160831/dswload2-330)
[ 8687.728332] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20160831/psobject-227)
[ 8687.728341] ACPI Error: Method parse/execution failed [\_GPE._E42] (Node ffff88ccb60d77d0), AE_ALREADY_EXISTS (20160831/psparse-543)
[ 8687.728358] ACPI Error: Method parse/execution failed [\_GPE._E42] (Node ffff88ccb60d77d0), AE_ALREADY_EXISTS (20160831/psparse-543)
[ 8687.728380] ACPI Exception: AE_ALREADY_EXISTS, while evaluating GPE method [_E42] (20160831/evgpe-646)


when I unplug/plug the adaptator, but I can deal with it.

pendrachken wrote:Other than that, if there are no issues with the working of the devices I wouldn't worry too much about these "error" messages. You can definitely keep looking into what is causing them to file bug reports, but I wouldn't worry over-much about anything since the devices are up and actually working.


Actually, no, the adaptator works, the only issue now is the outgoing bandwidth, I'm still at 30/40 Mb/s for a gigabit network. I think i'm gonna keep this like that and test with another driver....

If somebody need informations for debbuging/forensic or anything else, ask :wink:
aqwserf
 
Posts: 7
Joined: 2017-02-25 15:39


Return to System configuration

Who is online

Users browsing this forum: No registered users and 11 guests

fashionable