Coming from the kernel? No there's no kernel lines right before that
that have to do with USB. The kernel line before that is: Oct  2
22:21:45 user-desktop kernel: [   38.122133] Bluetooth: BNEP socket
layer initialized. And that's quite a ways up in the file. Also my
knowledge of git isn't that extensive and I got the source from the
download on the site not from the git repo so it tells me there's no
.git file but if I can figure out how to run that I'll give it a go.

On Mon, Oct 3, 2016 at 1:21 AM, Greg KH <gre...@linuxfoundation.org> wrote:
> On Mon, Oct 03, 2016 at 12:58:48AM -0700, Ashton Holmes wrote:
>> This happened back in the 4.8 release candidate and I thought it would
>> be fixed when the kernel went stable but I'm still having the issue.
>> The kernel seems to randomly reset my USB controller or do something
>> to that effect. Basically all my USB devices stop will randomly stop
>> working and I have to force reboot the system to get them to come back
>> only to have them work for 5 minutes or so before doing it again. I've
>> rolled back to 4.7.6 so I can use my system but 4.8 just doesn't seem
>> to want to work with USB. I've attached a segment from my syslog that
>> I think shows the issue.
>
>> Oct  2 22:23:31 user-desktop kernel: [  143.307247] ohci-pci 0000:00:12.0: 
>> HcDoneHead not written back; disabled
>> Oct  2 22:23:31 user-desktop kernel: [  143.307251] ohci-pci 0000:00:12.0: 
>> HC died; cleaning up
>> Oct  2 22:23:31 user-desktop kernel: [  143.307292] usb 10-1: USB 
>> disconnect, device number 2
>
> Ick, that's not good, anything right before these lines?
>
> And you can always let us know that we broke something during the -rc
> releases, that way we have a chance to fix it :)
>
> Along those lines, any chance you can run 'git bisect' to find the
> problem patch?
>
> thanks,
>
> greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to