Thanks,
I've probably attempted a reboot 5-10 times.
As stated in the initial post, rebooting does not help.
(Doesn't it follow that removing and installing the usb modules should not
work either?)
I suspect that the USB port is powered throughout the reboot process,
leaving something in a non-virgin state???
After a recent reboot:
dmesg |grep -i usb
[ 0.406628] usbcore: registered new interface driver usbfs
[ 0.406628] usbcore: registered new interface driver hub
[ 0.406628] usbcore: registered new device driver usb
[ 1.195031] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.195259] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus
number 1
[ 1.212027] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 1.212340] hub 1-0:1.0: USB hub found
[ 1.212523] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.212569] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.212775] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus
number 2
[ 1.213142] hub 2-0:1.0: USB hub found
[ 1.213442] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus
number 3
[ 1.213821] hub 3-0:1.0: USB hub found
[ 1.214118] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus
number 4
[ 1.214495] hub 4-0:1.0: USB hub found
[ 1.214790] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus
number 5
[ 1.215161] hub 5-0:1.0: USB hub found
[ 1.215439] usbcore: registered new interface driver libusual
[ 1.524036] usb 1-1: new high-speed USB device number 2 using ehci_hcd
[ 2.128052] usb 4-1: new full-speed USB device number 2 using uhci_hcd
[ 11.763968] usbcore: registered new interface driver usbserial
[ 11.772954] USB Serial support registered for generic
[ 11.773238] usbcore: registered new interface driver usbserial_generic
[ 11.773247] usbserial: USB Serial Driver core
[ 11.776780] USB Serial support registered for FTDI USB Serial Device
[ 11.776983] ftdi_sio 4-1:1.0: FTDI USB Serial Device converter detected
[ 11.777157] usb 4-1: Detected FT232RL
[ 11.777165] usb 4-1: Number of endpoints 2
[ 11.777171] usb 4-1: Endpoint 1 MaxPacketSize 64
[ 11.777178] usb 4-1: Endpoint 2 MaxPacketSize 64
[ 11.777183] usb 4-1: Setting MaxPacketSize 64
[ 11.778648] r8712u: USB_SPEED_HIGH with 4 endpoints
[ 11.779607] usb 4-1: FTDI USB Serial Device converter now attached to
ttyUSB0
[ 11.779728] usbcore: registered new interface driver ftdi_sio
[ 11.779734] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
[ 12.800699] usbcore: registered new interface driver r8712u
dmesg |grep -i uhci
[ 1.212569] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.212622] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) ->
IRQ 23
[ 1.212647] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 1.212653] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 1.212775] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus
number 2
[ 1.212819] uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000b880
[ 1.213292] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) ->
IRQ 19
[ 1.213313] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 1.213319] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 1.213442] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus
number 3
[ 1.213503] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000bc00
[ 1.213969] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) ->
IRQ 18
[ 1.213990] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 1.213996] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 1.214118] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus
number 4
[ 1.214178] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000c000
[ 1.214645] uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) ->
IRQ 16
[ 1.214666] uhci_hcd 0000:00:1d.3: setting latency timer to 64
[ 1.214672] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[ 1.214790] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus
number 5
[ 1.214849] uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000c080
[ 2.128052] usb 4-1: new full-speed USB device number 2 using uhci_hcd
Arne
>You could, of course, ssh in and reboot. Or a watchdog process -- no data
>for 1/2 hour -> reboot.
On Mon, Dec 9, 2013 at 2:41 PM, Jan Kandziora <jjj@...> wrote:
> Am 09.12.2013 18:23, schrieb Arne Raaen:
> >
> > This is easily fixed by briefly disconnecting the LinkUSBi usb contact,
> > but the roundtrip to the cabin is 5 hours...
> >
> Most likely this is a problem either with the adapter itself or with a
> USB hub inbetween. Check the kernel log with
>
> # dmesg | grep -i usb
>
> if there are any USB errors.
>
>
> > Is there any way to reset the system remotely?
> >
> I would try to reload the uhci_hcd or ohci_hcd module. If the hardware
> supports USB2.0, this should be enclosed into reloading the ehci_hcd
> module.
>
> # rmmod uhci_hcd ehci_hcd ; modprobe ehci_hcd ; modprobe uhci_hcd
>
> (or ohci_hcd if your system uses this instead of uhci_hcd)
>
> If the USB errors are related to overcurrent, you can try disabling the
> overcurrent detection with the ignore_oc module option. Overcurrent
> detection sometimes fails because the firmware of host controllers and
> hubs is crappy.
>
> Kind regards
>
> Jan
>
>
>
>
>
>
------------------------------------------------------------------------------
> Sponsored by Intel(R) XDK
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
>
>http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@...
>https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
