Duncan Sands wrote:
>Hi,
>
>
>
>>After one week trying to get that green thing (Alcatal SpeedTouch USB)
>>to work I decided to ask for some external help. I've managed to establish
>>connection and everything seems running just fine. But approx. once an hour
>>the modem (or driver or something) locks up and connection is broken.
>>
>>
>
>what does "locks up" mean? Do you just mean that it stops working?
>
>
>
It means that no packets are passing through and therefore pppoe (and so
pppd) times out and disconnects (see syslog part below from previous post).
>>Actually,
>>I'm able to reproduce this lockup quite reliably by downloading one specific
>>file from Internet. Logs don't give much info about this problem, pppoe just
>>fails reading and times out waiting for PADO offer:
>>
>>pppoe[394]: read (asyncReadFromPPP): Session 4552: Input/output error
>>pppoe[515]: Timeout waiting for PADO packets
>>
>>After this lockup I'm not able to reconnect and I'm forced to reload usb
>>module
>>and modem microcode to connect again. I'm using kernel driver for SpeedTouch
>>together with RFC 2684 bridge (my provider supports PPPoE only) and
>>rp-pppoe.
>>
>>I tried to trace the packets in "frozen" state by using "pppoe -A" command
>>(access concentrator discovery). The packets are comming through nas0
>>interface
>>(RFC 2684 bridge) and they arrive to ATM AAL5 layer. Unfortunately, I
>>was not
>>able to find out whether they actually arrive to modem via USB.
>>
>>
>
>In the speedtouch module source, you will find the following:
>
>/*
>#define DEBUG
>#define VERBOSE_DEBUG
>*/
>
>If you change this to
>
>#define DEBUG
>#define VERBOSE_DEBUG
>
>then the contents of all packets plus a bunch of other stuff will be dumped
>to your system logs.
>
>
I enabled debugging in speedtch module and found out, that when in
"frozen" state, the packets were leaving the driver. I found dump of
three discovery PADI packets sent by 'pppoe -A' in my system log with a
message that they were sent. This means, that packets can pass through
2684 bridge and the driver. It seems that problem is burried 'somewhere
deeper'. Is there any way to figure out whether the modem is still in
synchronised ?
Richard A Lough adviced me to check PCI timings:
<quote>
If you are running a pentium-133 you may want to increase the latency on
your pci bus. I use a pentiumpro-200 and this occasionally had problems
with latency. The command is setpci, and you probably want to read the
stuff from the list before deciding what setting to use. That may be
totally unrelated to your problem however
</quote>
I played a bit with PCI latency setting of USB with no apparent effect. I tried to
boost latency of USB while lowering latency of the other devices, but this seems to
have no effect. I also checked latency settings under Win98 a found out that they're
set to default value of 32 clocks just as in Linux.
>I hope this helps,
>
>Duncan.
>
>
Thanks
Andrej
Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se désinscrire : mailto:[EMAIL PROTECTED]
