On Sat, Sep 06, 2014 at 05:33:19PM +0200, Andrea Arcangeli wrote: > without weaking any /sysfs pm runtime related file, and I'll let you > know if it hangs again. No luck... it already hung again with the patches applied. try #1: [ 1484.886330] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [ 1492.387055] xhci_hcd 0000:00:14.0: remove, state 1 [ 1492.387060] usb usb2: USB disconnect, device number 1 [ 1492.387062] usb 2-2: USB disconnect, device number 2 [ 1497.404610] xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command. [ 1497.404615] xhci_hcd 0000:00:14.0: Assuming host is dying, halting host. [ 1497.404638] xhci_hcd 0000:00:14.0: HC died; cleaning up [ 1497.404643] ax88179_178a 2-2:1.0 enp0s20u2: unregister 'ax88179_178a' usb-0000:00:14.0-2, ASIX AX88179 USB 3.0 Gigabit Ethernet [ 1497.404657] ax88179_178a 2-2:1.0 enp0s20u2: Failed to read reg index 0x0002: -19 [ 1497.404660] ax88179_178a 2-2:1.0 enp0s20u2: Failed to write reg index 0x0002: -19 [ 1497.431477] ax88179_178a 2-2:1.0 (unregistered net_device): Failed to write reg index 0x0002: -19 [ 1497.431481] ax88179_178a 2-2:1.0 (unregistered net_device): Failed to write reg index 0x0001: -19 [ 1497.431482] ax88179_178a 2-2:1.0 (unregistered net_device): Failed to write reg index 0x0002: -19 [ 1497.431859] xhci_hcd 0000:00:14.0: USB bus 2 deregistered [ 1497.431868] xhci_hcd 0000:00:14.0: remove, state 4 [ 1497.431873] usb usb1: USB disconnect, device number 1 [ 1497.432070] xhci_hcd 0000:00:14.0: USB bus 1 deregistered try #2: [ 2237.795264] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [ 2248.167653] IPv6: ADDRCONF(NETDEV_UP): enp0s20u2: link is not ready [ 2252.773689] xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command. [ 2252.773697] xhci_hcd 0000:00:14.0: Assuming host is dying, halting host. [ 2252.773744] xhci_hcd 0000:00:14.0: HC died; cleaning up [ 2252.773786] usb 4-2: USB disconnect, device number 2 [ 2252.773847] ax88179_178a 4-2:1.0 enp0s20u2: unregister 'ax88179_178a' usb-0000:00:14.0-2, ASIX AX88179 USB 3.0 Gigabi t Ethernet [ 2252.787032] ax88179_178a 4-2:1.0 (unregistered net_device): Failed to write reg index 0x0002: -19 [ 2252.787036] ax88179_178a 4-2:1.0 (unregistered net_device): Failed to write reg index 0x0001: -19 [ 2252.787037] ax88179_178a 4-2:1.0 (unregistered net_device): Failed to write reg index 0x0002: -19 [ 2253.721716] xhci_hcd 0000:00:14.0: remove, state 1 [ 2253.721721] usb usb4: USB disconnect, device number 1 [ 2253.721916] xhci_hcd 0000:00:14.0: USB bus 4 deregistered [ 2253.721920] xhci_hcd 0000:00:14.0: remove, state 4 [ 2253.721923] usb usb3: USB disconnect, device number 1 [ 2253.722461] xhci_hcd 0000:00:14.0: USB bus 3 deregistered Earlier run from yesterday using upstream 17-rc3: [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up IPv6: ADDRCONF(NETDEV_UP): enp0s20u2: link is not ready ax88179_178a 2-2:1.0 enp0s20u2: ax88179 - Link status is: 1 ax88179_178a 2-2:1.0 enp0s20u2: ax88179 - Link status is: 1 IPv6: ADDRCONF(NETDEV_CHANGE): enp0s20u2: link becomes ready IPv6: ADDRCONF(NETDEV_UP): enp0s20u2: link is not ready ax88179_178a 2-2:1.0 enp0s20u2: ax88179 - Link status is: 1 ax88179_178a 2-2:1.0 enp0s20u2: ax88179 - Link status is: 1 IPv6: ADDRCONF(NETDEV_CHANGE): enp0s20u2: link becomes ready xhci_hcd 0000:00:14.0: remove, state 1 usb usb2: USB disconnect, device number 1 I noticed that sometime before the hang there's the drm error message... I tried also to "xset dpms force off" or "xset dpms force standby" during the network load, or to switch to console (CTRL+ALT+F1) but it doesn't hang that way. And it also happily hangs when there are no messages from drm. So I think it's just an accident the hang is shortly preceeded by the drm msg, but mentioning it just in case. There should be no obvious connection at least. In normal usage it tends to work fine, it's just my flooding stress test that triggers the problem eventually. It's quite simple: netcat otherhost discard </dev/zero netcat otherhost chargen >/dev/null It only requires to enable discard and chargen services in xinetd to reproduce. I cannot exclude it's a problem in my laptop xhci hardware though (I tested two different usb devices with this same chip and same driver, and they both hang eventually). I also need to be logged in the GUI to reproduce quicker. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
