On Thu, 26 Jun 2014 10:57:19 -0400 (EDT), Alan Stern wrote: > On Thu, 26 Jun 2014, Dennis New wrote: > > [...] > > echo 0000:00:13.0 >/sys/bus/pci/drivers/ohci_pci/unbind > > > > [39522.284135] ohci-pci 0000:00:13.0: remove, state 1 > > [39522.284152] usb usb2: USB disconnect, device number 1 > > [39522.285706] ohci-pci 0000:00:13.0: USB bus 2 deregistered > > > > echo 0000:00:13.0 >/sys/bus/pci/drivers/ohci_pci/bind > > > > [39530.642947] ohci-pci 0000:00:13.0: OHCI PCI host controller > > [39530.643269] ohci-pci 0000:00:13.0: new USB bus registered, > > assigned bus number 2 > > [39530.643323] ohci-pci 0000:00:13.0: irq 19, io > > mem 0xc0000000 > > [other plugged-in ohci devices (i.e. 4port hub) detected] > > > > I wonder if this unbind'ing and bind'ing should be done > > automatically, when a crash is detected? > > That's a separate discussion. To a large degree it doesn't matter, > because most hardware is designed not to crash during use. > > In fact, if you wanted to, you could write a shell script that would > monitor your system, looking for one of these crashes maybe once every > few seconds. When a crash occurred, the script could then do the > unbind and rebind. It doesn't need to be handled automatically in > the kernel. That sounds like an ugly workaround, since the kernel already has a direct "hook" with the crash event :p. Why would one prefer to simply "disconnect" the device (and then maybe have the user manually rebind it) rather than "reconnect" it right away? Unless it's assumed that such crashes are unrecoverable? -- 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
