[Voyage-linux] miniPCI express card USB disconnects when eth0 used
jarl
(spam-protected)
Fri Mar 19 05:18:31 HKT 2010
Strange that your USB modules are loading in a different order than mine. On
my board, first the EHCI controller is detected and loaded, afterwards the
OHCI controller. I'm no expert, but I don't believe that this would be
related to the problem.
What do you have as base addresses for your eth0 & eth1? Is it possible to
include a lspci -vv listing?
Does anyone know who would be able to lay his technical expert-eye on this
matter perhaps?
Thanks & regards,
Jarl
2010/3/18 Teco Boot <teco at inf-net.nl>
> I can report similar results, with Sierra MC8700 and Alix6e2 running Voyage
> 0.6.5.
> I see it often 5 hours after reboot.
> I do not relate this to eth0 (in my case).
>
> Is the starting order of uhci_hcd and ohci_hcd important?
> And USB interface number?
>
> Currently, I use a watchdog script checking ttyUSB0 to ttyUSB3. When
> mismatch, the box is rebooted.
>
> Regards, Teco
>
>
>
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 6.848539] usbcore: registered new
> interface driver usbfs
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 6.848884] usbcore: registered new
> interface driver hub
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 6.849872] usbcore: registered new
> device driver usb
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 6.868521] ohci_hcd: USB 1.1 'Open'
> Host Controller (OHCI) Driver
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 6.921315] ehci_hcd: USB 2.0
> 'Enhanced' Host Controller (EHCI) Driver
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 6.921764] Warning! ehci_hcd should
> always be loaded before uhci_hcd and ohci_hcd, not after
> ==> Teco: not sure if this is important
>
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 7.734496] ohci_hcd 0000:00:0f.4:
> OHCI Host Controller
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 7.734910] ohci_hcd 0000:00:0f.4: new
> USB bus registered, assigned bus number 1
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 7.735808] ohci_hcd 0000:00:0f.4: irq
> 12, io mem 0xefffe000
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 7.822249] usb usb1: configuration #1
> chosen from 1 choice
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 7.822952] hub 1-0:1.0: USB hub found
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 7.823794] hub 1-0:1.0: 4 ports
> detected
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 7.825827] ehci_hcd 0000:00:0f.5:
> EHCI Host Controller
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 7.826884] ehci_hcd 0000:00:0f.5: new
> USB bus registered, assigned bus number 2
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 7.848873] ehci_hcd 0000:00:0f.5: irq
> 12, io mem 0xefffd000
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 7.855783] ehci_hcd 0000:00:0f.5: USB
> 2.0 started, EHCI 1.00
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 7.857367] usb usb2: configuration #1
> chosen from 1 choice
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 7.857960] hub 2-0:1.0: USB hub found
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 7.858795] hub 2-0:1.0: 4 ports
> detected
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 8.264802] usb 2-2: new high speed
> USB device using ehci_hcd and address 3
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 8.380795] usb 2-2: config 1 has an
> invalid interface number: 7 but max is 4
> ==> Teco: not sure if this is important
>
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 8.381767] usb 2-2: config 1 has no
> interface number 2
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 8.384881] usb 2-2: configuration #1
> chosen from 1 choice
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 8.611789] usb 1-1: new full speed
> USB device using ohci_hcd and address 2
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 8.750334] usb 1-1: configuration #1
> chosen from 1 choice
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 10.485081] udevd version 125 started
>
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.248557] cdc_acm 1-1:1.0: ttyACM0:
> USB ACM device
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.279579] usbcore: registered new
> interface driver cdc_acm
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.279781] cdc_acm: v0.26:USB
> Abstract Control Model driver for USB modems and ISDN adapters
>
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.329245] usbcore: registered new
> interface driver usbserial
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.329834] USB Serial support
> registered for generic
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.330982] usbcore: registered new
> interface driver usbserial_generic
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.331764] usbserial: USB Serial
> Driver core
>
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.526539] USB Serial support
> registered for Sierra USB modem
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.527818] sierra 2-2:1.0: Sierra USB
> modem converter detected
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.530945] usb 2-2: APM supported,
> enabling autosuspend.
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.532458] usb 2-2: Sierra USB modem
> converter now attached to ttyUSB0
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.533739] sierra 2-2:1.1: Sierra USB
> modem converter detected
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.534414] usb 2-2: APM supported,
> enabling autosuspend.
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.535436] usb 2-2: Sierra USB modem
> converter now attached to ttyUSB1
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.536807] sierra 2-2:1.3: Sierra USB
> modem converter detected
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.538802] usb 2-2: APM supported,
> enabling autosuspend.
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.540345] usb 2-2: Sierra USB modem
> converter now attached to ttyUSB2
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.541816] sierra 2-2:1.4: Sierra USB
> modem converter detected
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.544293] usb 2-2: APM supported,
> enabling autosuspend.
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.545451] usb 2-2: Sierra USB modem
> converter now attached to ttyUSB3
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.547158] usbcore: registered new
> interface driver sierra
> Jan 1 00:01:28 hgm-57-22 vmunix: [ 18.547766] sierra: v.1.7.30:USB
> Driver for Sierra Wireless USB modems
>
>
> Jan 1 00:01:35 hgm-57-22 pppd[3378]: pppd 2.4.4 started by root, uid 0
> Jan 1 00:01:37 hgm-57-22 pppd[3378]: Serial connection established.
> Jan 1 00:01:38 hgm-57-22 pppd[3378]: Using interface ppp0
> Jan 1 00:01:38 hgm-57-22 pppd[3378]: Connect: ppp0 <--> /dev/ttyUSB3
> Jan 1 00:01:39 hgm-57-22 pppd[3378]: CHAP authentication succeeded
> Jan 1 00:01:39 hgm-57-22 pppd[3378]: CHAP authentication succeeded
> Jan 1 00:01:39 hgm-57-22 vmunix: [ 70.839919] PPP Deflate Compression
> module registered
> Jan 1 00:01:42 hgm-57-22 pppd[3378]: Could not determine remote IP
> address: defaulting to 10.64.64.64
> Jan 1 00:01:42 hgm-57-22 pppd[3378]: local IP address 89.200.94.41
> Jan 1 00:01:42 hgm-57-22 pppd[3378]: remote IP address 10.64.64.64
> Jan 1 00:01:42 hgm-57-22 pppd[3378]: primary DNS address 62.133.126.28
> Jan 1 00:01:42 hgm-57-22 pppd[3378]: secondary DNS address 62.133.126.29
>
> ==> Teco: Here and messages below, the usb device is resetted, reason
> unknown
> Jan 1 04:55:33 hgm-57-22 vmunix: [17704.735878] usb 2-2: USB disconnect,
> address 3
> Jan 1 04:55:33 hgm-57-22 vmunix: [17704.740222] sierra ttyUSB0: Sierra USB
> modem converter now disconnected from ttyUSB0
> Jan 1 04:55:33 hgm-57-22 vmunix: [17704.740969] sierra 2-2:1.0: device
> disconnected
> Jan 1 04:55:33 hgm-57-22 vmunix: [17704.743106] sierra ttyUSB1: Sierra USB
> modem converter now disconnected from ttyUSB1
> Jan 1 04:55:33 hgm-57-22 vmunix: [17704.743916] sierra 2-2:1.1: device
> disconnected
> Jan 1 04:55:33 hgm-57-22 vmunix: [17704.756382] sierra ttyUSB2: Sierra USB
> modem converter now disconnected from ttyUSB2
> Jan 1 04:55:33 hgm-57-22 vmunix: [17704.756883] sierra 2-2:1.3: device
> disconnected
> Jan 1 04:55:33 hgm-57-22 pppd[3378]: Hangup (SIGHUP)
> Jan 1 04:55:33 hgm-57-22 pppd[3378]: Modem hangup
> Jan 1 04:55:33 hgm-57-22 pppd[3378]: Connect time 293.9 minutes.
> Jan 1 04:55:33 hgm-57-22 pppd[3378]: Sent 1248626 bytes, received 741702
> bytes.
> Jan 1 04:55:33 hgm-57-22 vmunix: [17704.772457] sierra ttyUSB3: Sierra USB
> modem converter now disconnected from ttyUSB3
> Jan 1 04:55:33 hgm-57-22 vmunix: [17704.772922] sierra 2-2:1.4: device
> disconnected
> Jan 1 04:55:33 hgm-57-22 pppd[3378]: Connection terminated.
> Jan 1 04:55:34 hgm-57-22 vmunix: [17704.982285] usb 2-2: new high speed
> USB device using ehci_hcd and address 4
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.099394] usb 2-2: config 1 has an
> invalid interface number: 7 but max is 4
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.100033] usb 2-2: config 1 has no
> interface number 2
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.103276] usb 2-2: configuration #1
> chosen from 1 choice
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.108907] sierra 2-2:1.0: Sierra USB
> modem converter detected
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.112007] usb 2-2: APM supported,
> enabling autosuspend.
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.113454] usb 2-2: Sierra USB modem
> converter now attached to ttyUSB0
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.115519] sierra 2-2:1.1: Sierra USB
> modem converter detected
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.116684] usb 2-2: APM supported,
> enabling autosuspend.
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.117483] usb 2-2: Sierra USB modem
> converter now attached to ttyUSB1
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.122972] sierra 2-2:1.3: Sierra USB
> modem converter detected
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.125491] usb 2-2: APM supported,
> enabling autosuspend.
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.126598] usb 2-2: Sierra USB modem
> converter now attached to ttyUSB4
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.129315] sierra 2-2:1.4: Sierra USB
> modem converter detected
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.130819] usb 2-2: APM supported,
> enabling autosuspend.
> Jan 1 04:55:34 hgm-57-22 vmunix: [17705.132893] usb 2-2: Sierra USB modem
> converter now attached to ttyUSB5
>
>
> Op 17 mrt 2010, om 23:01 heeft jarl het volgende geschreven:
>
> > Hi all,
> >
> > I hope that this question hasn't been answered already 10 times, but
> haven't found any such reference, so I take my chance.
> >
> > When using Sierra Wireless miniPCI express modules on the Alix board with
> voyage 0.6.2 or 0.6.5, and only when eth0 is both up and connected, there
> are constant USB disconnects and reconnects from that module, as in (this is
> 0.6.5):
> >
> > [ 1740.985847] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
> > [ 1740.986735] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> > [ 1741.455468] usb 2-2: USB disconnect, address 2
> > [ 1741.459013] sierra ttyUSB0: Sierra USB modem converter now
> disconnected from ttyUSB0
> > [ 1741.459925] sierra ttyUSB1: Sierra USB modem converter now
> disconnected from ttyUSB1
> > [ 1741.460938] sierra ttyUSB2: Sierra USB modem converter now
> disconnected from ttyUSB2
> > [ 1741.461478] sierra 2-2:1.0: device disconnected
> > [ 1764.881421] usb 2-2: new full speed USB device using ohci_hcd and
> address 3
> > [ 1765.020598] usb 2-2: configuration #1 chosen from 1 choice
> > [ 1765.024616] sierra 2-2:1.0: Sierra USB modem converter detected
> > [ 1765.027124] usb 2-2: Sierra USB modem converter now attached to
> ttyUSB0
> > [ 1765.028032] usb 2-2: Sierra USB modem converter now attached to
> ttyUSB1
> > [ 1765.028945] usb 2-2: Sierra USB modem converter now attached to
> ttyUSB2
> >
> > This is repeated until infinity (or at least that's what I suppose).
> >
> > I had contact with mr. Dornier from PCEngines, and we concluded that the
> Ethernet drivers possibly were to be suspected of this behaviour. The reason
> is that (for 0.6.2 at least), the base addresses found in ifconfig were
> conflicting with the addresses of other devices on the board. I can provide
> some documentation, but I'm not aware if it is accepted to attach files
> here.
> >
> > Anyone else having seen such things? I've seen this happening with MC8775
> and MC8780 and MC8792V modules, so both voice and non-voice modules.
> >
> > Thanks for any ideas.
> >
> > Jarl
> > _______________________________________________
> > Voyage-linux mailing list
> > Voyage-linux at list.voyage.hk
> > http://list.voyage.hk/mailman/listinfo/voyage-linux
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20100318/58fe23bc/attachment.html>
More information about the Voyage-linux
mailing list