----- Original Message ----- From: "Christophe Couronne" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, June 15, 2003 11:01 PM Subject: [speedtouch] Re: problems on 440LX chipset
> > Le Dimanche 15 Juin 2003 20:47, Gilles Espinasse a �crit : > > Many people have seen this sort of event with IPCop firewall V1.3 (kernel > > 2.4.20) and SpeedTouch USB V1.2beta when using emule or and upload. > > This is not specific to 440LX chipset. > > > > The complete log look like that > > May 18 05:36:47 ipcop pppoa3[186]: Error reading usb urb > > May 18 05:36:47 ipcop pppoa3[175]: Woken by a sem_post event -> Exiting > > May 18 05:36:47 ipcop pppoa3[175]: Read from usb Canceled > > May 18 05:36:47 ipcop kernel: usb-uhci.c: interrupt, status 3, frame# 1633 > > May 18 05:36:47 ipcop kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x7 > > len 1537 ret -110 > > May 18 05:36:47 ipcop modem_run[171]: Error reading interrupts > > May 18 05:36:47 ipcop kernel: usbdevfs: process 171 (modem_run) did not > > claim interface 0 before use > > May 18 05:36:47 ipcop kernel: hub.c: already running port 1 disabled by hub > > (EMI?), re-enabling... > > May 18 05:36:47 ipcop kernel: usb.c: USB disconnect on device 00:07.2-1 > > address 2 > > May 18 05:36:47 ipcop pppoa3[175]: Exiting > > May 18 05:36:47 ipcop kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x7 > > len 106 ret -110 > > May 18 05:36:47 ipcop modem_run[171]: Error reading interrupts > > May 18 05:36:47 ipcop modem_run[171]: Device disconnected, shutting down > > May 18 05:36:47 ipcop pppd[174]: Modem hangup > > May 18 05:36:47 ipcop pppd[174]: Connection terminated. > > May 18 05:36:47 ipcop pppd[174]: Connect time 1122.3 minutes. > > May 18 05:36:48 ipcop pppd[174]: Sent 924109595 bytes, received 701080204 > > bytes. > > May 18 05:36:48 ipcop kernel: hub.c: new USB device 00:07.2-1, assigned > > address 3 > > May 18 05:36:48 ipcop pppd[174]: Using interface ppp0 > > May 18 05:36:48 ipcop kernel: usb.c: USB device 3 (vend/prod 0x6b9/0x4061) > > is not claimed by any active driver. > > May 18 05:36:48 ipcop pppd[174]: Connect: ppp0 <--> /dev/ttyp0 > > May 18 05:36:48 ipcop ipcop: PPP has gone down on ppp0 > > May 18 05:36:49 ipcop dnsmasq[7138]: started, version 1.11 cachesize 150 > > May 18 05:36:49 ipcop dnsmasq[7138]: reading /etc/hosts > > May 18 05:36:49 ipcop dnsmasq[7138]: reading /var/ipcop/red/resolv.conf > > May 18 05:36:49 ipcop dnsmasq[7138]: using nameserver 193.252.19.4 > > May 18 05:36:49 ipcop dnsmasq[7138]: using nameserver 193.252.19.3 > > May 18 05:36:49 ipcop pppoa3[7118]: pppoa3 version 1.2-beta1 started by > > root (uid 0) > > May 18 05:36:49 ipcop dnsmasq[7138]: reading /var/lib/dhcp/dhcpd.leases > > May 18 05:36:49 ipcop pppoa3[7118]: Control thread ready > > May 18 05:36:49 ipcop pppoa3[7149]: host --> pppoa3 --> modem stream ready > > May 18 05:36:50 ipcop pppoa3[7150]: modem --> pppoa3 --> host stream ready > > May 18 05:36:50 ipcop pppoa3[7150]: Error reading usb urb > > > > The modem is reset by the 'disabled by hub (EMI?)' and receive a new device > > number. > > So modem_run and pppoa3 fall but the firmware stay inside. > > First, you have to reset usb (umount usbdevfs and modprobe -r > > usb-controller) to be able to start modem_run succesfully by loading the > > firmware > > Secondly, you have to erase /var/run/pppoa3-modem*.pid to avoid detection > > by the new pppoa3 of an old pppoa3 which look still running by the presence > > of this pid but is not visible by ps -ef. Also the new pppoa3 will wait > > undefinitly the old pppoa3 was killed and the pid withdrawed. > > Third, you can connect again normaly. > > > > I think the main problem is why the modem is reset and message 'hub.c: > > already running port 1 disabled by hub (EMI?), re-enabling... ' is for me > > the core of the problem. I don't know if it's a kernel/usb bug or something > > related to pppoa3 driver. For me, it's clear it's not EMI but something > > related to uplink trafic charge. > > > > Personnaly I have seen exactly the same message 'disabled by hub > > (EMI?),...' with ECI usb driver rarely in PPPoA mode but often in PPPoE > > mode. And Benoit is named as the author of pppoeci wich should be derivated > > from pppoa3 > > > > One people wich had regulary the problem is going back to V1.1 driver > > version and the problem desappeared. > > Good news: all is very clear now. > > Bad news: I've upgraded to 1.2-beta1 because I've had the same problem with > 1.1. What firmware version (md5sum) do you use? I have made a list more up-to-date as the old list in FAQ (I add the size is when I find the firmware) 7d0e028a8e3901bc0b5b569c575203ef alcaudsl.sys windows version 1.3.1 (BTO CDROM?) 3423810ba8d43ec7cdd01dd83698762b alcaudsl.sys windows version 1.3.4 aae9dd2d6ad69878d7899b24fa40cb08 alcaudsl.sys windows version 1.3.4 b1bc2524451b8b238fca773d8642f60a alcaudsl.sys windows version 1.4.0 d77a03513c8abddc6f95395515f2973e alcaudsl.sys windows versionV1.4.1b 161.1R size 591 408 aefca4891a64fd6f76d517406abd9407 alcaudsl.sys windows version V1.6 161.1.0.1800 161.1R size 735 568 e3a564dde82b7fdc92a3128d80418b24 alcaudsl.sys windows version 16 8080b5ea17a763bbce6c92bbc6ceefe8 alcaudsl.sys windows version 200.7.0.0 size 743 136 d6652432d103b4228ffad7a754a374b5 alcaudsl.sys windows version 201.2.0.0 size 748 544 adae14d607b8caa6acc253feb1d82705 firmware.bin size 671 653 ed70254b584fec3f0b5277d0550b39a1 KQD6P2.eni size 677 641 b35276ce6871cc2ba8c23e50a87043ab mgmt.o linux original version? 0ee210ea42613cf43c72310672aae6c6 mgmt.o linux version 1.3.3 ce3582cc9c3b967baa0e918f2708075d mgmt.o linux version 1.3.4 size 535 856 I don't know if bigger is better but it's look like linux firmware are always smaller than windows fimware. Is it old code comparing to windows size or a lighter shell of the code? Liste de diffusion modem ALCATEL SpeedTouch USB Pour se d�sinscrire : mailto:[EMAIL PROTECTED]
