WLAN: known issues and how to help - uptime test - more results

[Werner Almesberger]

Philip Rhoades wrote:
> I upgraded to 7.00.4 but it still only lasted a few hours.

:-(

> Hereunder the results from the last test - nothing jumps out.

Thanks ! The first one looks good, except for this little oddity:

> 0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0        0 eth0
> 0.0.0.0         192.168.1.200   0.0.0.0         UG    0      0        0 usb0

This doesn't seem to cause the connectivity problem we're examining,
but two default routes with the same metric may cause confusion.

In the second case, we seem to have an unhappy PHY:

> eth0      AR6000 802.11g  ESSID:"linksys"
>           Mode:Managed  Frequency:2.472 GHz  Access Point:  
> 00:1C:10:09:8E:32
>           Bit Rate=65.535 Mb/s   Tx-Power=0 dBm   Sensitivity=0/3

Both bit rate and TX power are off. This looks like
http://docs.openmoko.org/trac/ticket/1285

Besides the duplicate default route, things look good at the IP
layer. So DHCP is exonerated.

What's the system been doing between being good and going bad ?
Did it suspend ?

Could you please also do an iwlist scan when WLAN is happy and
again when it isn't ?

This has actually some similarity to what happens when the AR6k
firmware has crashed. Let me roll a debugging image ...

Thanks,
- Werner