Oliver Neukum changed bug 1161232
What Removed Added
CC   opensuse@mike.franken.de
Flags needinfo?(oneukum@suse.com) needinfo?(opensuse@mike.franken.de)

Comment # 10 on bug 1161232 from
(In reply to Jiri Slaby from comment #6)
> Oliver, any idea why this happens?
> 
> > usb usb1: root hub lost power or was reset
> > usb usb2: root hub lost power or was reset
> > ACPI: EC: event unblocked
> > usb usb3: root hub lost power or was reset
> > usb usb4: root hub lost power or was reset
> > xhci_hcd 0000:3c:00.0: Host halt failed, -19
> > xhci_hcd 0000:3c:00.0: Host not accessible, reset failed.
> > usb usb5: root hub lost power or was reset
> > usb usb6: root hub lost power or was reset
> > xhci_hcd 0000:3d:00.0: Host halt failed, -19
> > usb usb7: root hub lost power or was reset
> > usb usb8: root hub lost power or was reset
> > xhci_hcd 0000:3d:00.0: Host not accessible, reset failed.
> > xhci_hcd 0000:3e:00.0: Host halt failed, -19
> > xhci_hcd 0000:3e:00.0: Host not accessible, reset failed.

[ 5390.147140] pcieport 0000:03:00.0: Refused to change power state, currently
in D3
[ 5390.150504] pcieport 0000:04:01.0: Refused to change power state, currently
in D3
[ 5390.150505] pcieport 0000:04:00.0: Refused to change power state, currently
in D3
[ 5390.150506] pcieport 0000:04:02.0: Refused to change power state, currently
in D3
[ 5390.150507] pcieport 0000:04:04.0: Refused to change power state, currently
in D3
[ 5390.156540] pcieport 0000:3a:00.0: Refused to change power state, currently
in D3
[ 5390.156545] thunderbolt 0000:05:00.0: Refused to change power state,
currently in D3
[ 5390.159558] pcieport 0000:3b:00.0: Refused to change power state, currently
in D3
[ 5390.159559] pcieport 0000:3b:01.0: Refused to change power state, currently
in D3
[ 5390.159560] pcieport 0000:3b:02.0: Refused to change power state, currently
in D3


This is basically a PCI issue, which in turn crashes USB. But the second dmesg
is inconsistent with that. Could we have two or three crashes with the same
kernel as dmesg, so we can be sure that we are not seeing memory corruption?


You are receiving this mail because: