AR6000 hickup

2009-05-13 Thread Joachim Ott 
See the excerpt from /var/log/messages below. Normally the AR6000
disconnects every 20 minutes from the AP and reconnects immediately -
sometimes it goes out of order tho. Look at 13:03:17 - the next
disconnect should happen around 13:17:20, this is much too early. And
the reconnect is about 60 seconds later. After that, the 20 minute
interval is gone. My last typing was at 13:45, my next try was at
15:36, I got no echo when typing. Again, it took 60 seconds to
reconnect.

Has anyone else noticed this problem?

May 13 12:17:17 gta02v6 user.warn kernel: [ 5740.63] AR6000
connected event on freq 2452 with bssid 00:1c:4a:d1:5a:af
listenInterval=100, beaconInterval = 100, beaconIeLen = 26
assocReqLen=57 assocRespLen =22
May 13 12:17:17 gta02v6 user.warn kernel: [ 5740.635000] Network: Infrastructure
May 13 12:37:18 gta02v6 user.warn kernel: [ 6940.69] AR6000
disconnected from 00:1c:4a:d1:5a:af
May 13 12:37:18 gta02v6 user.warn kernel: [ 6940.725000] AR6000
connected event on freq 2452 with bssid 00:1c:4a:d1:5a:af
listenInterval=100, beaconInterval = 100, beaconIeLen = 26
assocReqLen=57 assocRespLen =22
May 13 12:37:18 gta02v6 user.warn kernel: [ 6940.73] Network: Infrastructure
May 13 12:57:18 gta02v6 user.warn kernel: [ 8140.785000] AR6000
disconnected from 00:1c:4a:d1:5a:af
May 13 12:57:18 gta02v6 user.warn kernel: [ 8140.82] AR6000
connected event on freq 2452 with bssid 00:1c:4a:d1:5a:af
listenInterval=100, beaconInterval = 100, beaconIeLen = 26
assocReqLen=57 assocRespLen =22
May 13 12:57:18 gta02v6 user.warn kernel: [ 8140.825000] Network: Infrastructure
May 13 13:03:17 gta02v6 user.warn kernel: [ 8500.435000] AR6000 disconnected
May 13 13:04:19 gta02v6 user.warn kernel: [ 8561.77] AR6000
connected event on freq 2452 with bssid 00:1c:4a:d1:5a:af
listenInterval=100, beaconInterval = 100, beaconIeLen = 26
assocReqLen=57 assocRespLen =22
May 13 13:04:19 gta02v6 user.warn kernel: [ 8561.775000] Network: Infrastructure
May 13 13:05:12 gta02v6 auth.err sshd[2040]: error: Could not load
host key: /etc/ssh/ssh_host_dsa_key
May 13 13:05:13 gta02v6 auth.info sshd[2040]: Accepted publickey for
root from 192.168.7.21 port 40679 ssh2
May 13 13:05:13 gta02v6 auth.err sshd[2042]: error: setlogin failed:
Function not implemented
May 13 15:36:33 gta02v6 user.warn kernel: [17696.395000] AR6000 disconnected
May 13 15:36:34 gta02v6 user.info kernel: [17697.155000] pcf50633
0-0073: usb curlim to 1000 mA
May 13 15:37:28 gta02v6 auth.info sshd[2040]: Timeout, client not responding.
May 13 15:37:35 gta02v6 user.warn kernel: [17757.73] AR6000
connected event on freq 2452 with bssid 00:1c:4a:d1:5a:af
listenInterval=100, beaconInterval = 100, beaconIeLen = 26
assocReqLen=57 assocRespLen =22
May 13 15:37:35 gta02v6 user.warn kernel: [17757.735000] Network: Infrastructure
May 13 15:38:25 gta02v6 auth.err sshd[2425]: error: Could not load
host key: /etc/ssh/ssh_host_dsa_key
May 13 15:38:26 gta02v6 auth.info sshd[2425]: Accepted publickey for
root from 192.168.7.21 port 50449 ssh2
May 13 15:38:26 gta02v6 auth.err sshd[2427]: error: setlogin failed:
Function not implemented

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Qi causes WSOD (was Re: [2008.testing] WSOD)

2009-05-13 Thread Chris Jenks 

On Mon, 23 Feb 2009, Jeffrey Ratcliffe wrote:

 2009/2/22 Jeffrey Ratcliffe jeffrey.ratcli...@gmail.com:
 The only other thing I did around the same time was to replace uBoot with Qi.

 To test this, I booted into NOR, thereby using uBoot, and then booted
 the 2.4.24 image again (which I had reflashed). Resume then works
 without WSOD.

 i.e. Qi, for me at least, causes WSOD.
[...]

I've been playing with the beta Om 2009 consisting of fso-paroli-image, 
uImage 2.6.38 and Qi 1.0.2 dated 5/8-5/9 but was getting the WSOD when 
resuming from suspend. I replaced Qi with u-boot 1.3.1 and can now resume 
properly.

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Qi causes WSOD (was Re: [2008.testing] WSOD)

2009-05-13 Thread Jeffrey Ratcliffe 
2009/5/13 Chris Jenks ch...@jenks.us:
 I've been playing with the beta Om 2009 consisting of fso-paroli-image,
 uImage 2.6.38 and Qi 1.0.2 dated 5/8-5/9 but was getting the WSOD when
 resuming from suspend. I replaced Qi with u-boot 1.3.1 and can now resume
 properly.

Although, from what I understand, 2.6.28  uboot don't suspend
properly. I have Qi and 2.6.29 in flash, which works fine, and 2.6.28
on an SD, which gives me WSOD - i.e. the kernel is really at fault,
not Qi.

Regards

Jeff

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Qi causes WSOD (was Re: [2008.testing] WSOD)

2009-05-13 Thread einstein 
Chris Jenks wrote:
 On Mon, 23 Feb 2009, Jeffrey Ratcliffe wrote:

   
 2009/2/22 Jeffrey Ratcliffe jeffrey.ratcli...@gmail.com:
 
 The only other thing I did around the same time was to replace uBoot with 
 Qi.
   
 To test this, I booted into NOR, thereby using uBoot, and then booted
 the 2.4.24 image again (which I had reflashed). Resume then works
 without WSOD.

 i.e. Qi, for me at least, causes WSOD.
 [...]
 

 I've been playing with the beta Om 2009 consisting of fso-paroli-image, 
 uImage 2.6.38 and Qi 1.0.2 dated 5/8-5/9 but was getting the WSOD when 
 resuming from suspend. I replaced Qi with u-boot 1.3.1 and can now resume 
 properly.
   
i have the same problem. i switch to uboot back so i can use the 
suspend. where i can find the 2.6.29 kernel?
with the 2.6.29 kernel the problem is fixed?

 ___
 support mailing list
 support@lists.openmoko.org
 https://lists.openmoko.org/mailman/listinfo/support

   


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Re: Qi causes WSOD (was Re: [2008.testing] WSOD)

2009-05-13 Thread jeffrey . ratcliffe 

On May 13, 2009 11:11pm, einstein mailingl...@freeyourphone.de wrote:

i have the same problem. i switch to uboot back so i can use the
suspend. where i can find the 2.6.29 kernel?
with the 2.6.29 kernel the problem is fixed?


I use the 2.6.29 kernel from SHR-testing, and with that and Qi,  
suspend/resume works properly.


Regards

Jeff
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support