Re: [zd1211-devs] AP Loss with Zd1211 2.22 driver version

2009-04-01 Thread Paco
Hi, I'm using driver zd_b.o of zd1211 with 2.4.26 kernel and during
the data transfer in WEP happens the same: *** We Lose AP for 5
seconds ***

I have solved the problem staying very close to the AP

Good Luck and if you fix your problem please tell us.

On Wed, Apr 1, 2009 at 12:20 PM, Amol Lad amol@gmail.com wrote:
 Hi,

 I am using an old USB 2.22 driver version on ARM based platform and
 2.6.18 kernel. During data transfer in WPA-PSK mode, I get below
 message:
 *** We Lose AP for 5 seconds ***
 and wireless interface stops working

 The same problem is observed on the PC

 I upgraded driver version 3.0.0.56 and it seems to be working fine on
 PC. However, it crashes in ARM platform in the network layer (crash
 log below). After comparing both the drivers I found that

 3.0.0.56: zd1205.h : #define ZD_RX_OFFSET 00
 2.22: zd1205.h: #define ZD_RX_OFFSET 0x03

 After changing ZD_RX_OFFSET to 0x03 in 3.0.0.56 the crash goes off but
 AP loss is still observed. In PC, 3.0.0.56 works find with
 ZD_RX_OFFSET == 00 .

 What is the correct value for ZD_RX_OFFSET and why value 00 value
 crashes in ARM and fine on PC. Is some structure packing issue ? I
 feel that if I'm able to avoid crash with ZD_RX_OFFSET == 0, then AP
 loss will not be observed in new driver

 Thanks
 PS:
 The crash log is below:
 Unable to handle kernel paging request at virtual address cd7a8075
 pgd = cd7fc000
 [cd7a8075] *pgd=8d60041e(bad)
 Internal error: Oops: 1 [#1]
 Modules linked in: fuse r8187 ieee80211_rtl ieee80211_crypt_ccmp_rtl
 ieee80211_crypt_tkip_rtl ieee80211_crypt_wep_rtl ieee80211_crypt_rtl
 arusb_lnx zd1211b mafv2 idecode ividio dm420_codec imanage davinci_resizer
 CPU: 0
 PC is at tcp_rcv_established+0x20/0x7e4
 LR is at tcp_v4_do_rcv+0x12c/0x3a0
 pc : [c0228ad8]    lr : [c023165c]    Tainted: P
 sp : cd7e5d24  ip : 031c  fp : cd7e5d4c
 r10:   r9 : 0f08  r8 : cc803534
 r7 : cc8031e0  r6 : cd7a8069  r5 : cfee3720  r4 : cc8031e0
 r3 : 05c8  r2 : cd7a8069  r1 : cfee3720  r0 : 003a
 Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  Segment user
 Control: 5317F  Table: 8D7FC000  DAC: 0015
 Process ftpget (pid: 1473, stack limit = 0xcd7e4250)
 Stack: (0xcd7e5d24 to 0xcd7e6000)
 5d20:          cc80348c cfee3720 cc8031e0 cc8031e0 cc803534 0f08
 
 5d40: cd7e5d84 cd7e5d50 c023165c c0228ac8 cd7e5d5c c01f199c c00476c4
 cc80348c
 5d60: cc8031e0  cc8031e0 cc803534 0f08  cd7e5da0
 cd7e5d88
 5d80: c0220624 c0231540 cd7e4000  c02e28f0 cd7e5df0 cd7e5da4
 c0220c5c
 5da0: c02205d0 05a8 cc803234 0001 cd7d2820 10f8 cd7e5e68
 7fff
 5dc0: 8d70e428 0001 cd7e5e68  c02e28f0 c3846120 c3846120
 cd7e4000
 5de0: cd7e5f78 cd7e5e1c cd7e5df4 c01f2a2c c022081c  
 cd7e5e00
 5e00:  c027daec 2000 cd538740 cd7e5e40 cd7e5e20 c01ee558
 c01f29f4
 5e20:  cd7e5eac 2000 00145010 cd7e5ef4 cd7e5ea0 cd7e5e44
 c01ee698
 5e40: c01ee4b4 0001 c07ff4d0 c07ff4d0  2000 cd538740
 4013
 5e60:  cd7e5e68   cd7e5e84 0001 
 
 5e80:  001466b0 0960 cd7e5eac cd7e5eac cd7e5f48 cd7e5ea8
 c0085f2c
 5ea0: c01ee638   000c cd7e5f04  0001
 
 5ec0: c3846120     cd7d2820 
 
 5ee0: cd7e5f00 cd7d2820 c00588c4 cd7e5eec cd7e5eec  
 cd7e5e48
 5f00: c0026724 0003 00145010 c02e0cdc  c3846120 
 
 5f20:  c3846120 00145010 2000  cd7e4000 cd7e5f78
 cd7e5f74
 5f40: cd7e5f4c c00860e0 c0085e7c c00b5a78 c3846140 c3846120 cd7e5f78
 
 5f60:  0004 cd7e5fa4 cd7e5f78 c00863ac c0085f84 
 
 5f80:  05a8 2000 00145010 0003 c0025fc4 
 cd7e5fa8
 5fa0: c0025e20 c0086370 05a8 2000 0004 00145010 2000
 07ffad06
 5fc0: 05a8 2000 00145010 0004 0005 0005 0004
 bebdaf44
 5fe0:  bebdaaf8 36d8 40173e10 6010 0004 
 
 Backtrace:
 [c0228ab8] (tcp_rcv_established+0x0/0x7e4) from [c023165c]
 (tcp_v4_do_rcv+0x12c/0x3a0)
 [c0231530] (tcp_v4_do_rcv+0x0/0x3a0) from [c0220624]
 (tcp_prequeue_process+0x64/0x90)
 [c02205c0] (tcp_prequeue_process+0x0/0x90) from [c0220c5c]
 (tcp_recvmsg+0x450/0x88c)
  r6 = C02E28F0  r5 =   r4 = CD7E4000
 [c022080c] (tcp_recvmsg+0x0/0x88c) from [c01f2a2c]
 (sock_common_recvmsg+0x48/0x5c)
 [c01f29e4] (sock_common_recvmsg+0x0/0x5c) from [c01ee558]
 (do_sock_read+0xb4/0xb8)
  r6 = CD538740  r5 = 2000  r4 = C027DAEC
 [c01ee4a4] (do_sock_read+0x0/0xb8) from [c01ee698]
 (sock_aio_read+0x74/0x7c)
  r7 = CD7E5EF4  r6 = 00145010  r5 = 2000  r4 = CD7E5EAC
 [c01ee628] (sock_aio_read+0x4/0x7c) from [c0085f2c]
 (do_sync_read+0xc0/0x108)
  r4 = CD7E5EAC
 [c0085e6c] (do_sync_read+0x0/0x108) from [c00860e0]
 (vfs_read+0x16c/0x170)
 [c0085f74] (vfs_read+0x0/0x170) from [c00863ac] (sys_read+0x4c/0x7c)
 [c0086360] 

[zd1211-devs] AP Loss with Zd1211 2.22 driver version

2009-04-01 Thread Amol Lad
Hi,

I am using an old USB 2.22 driver version on ARM based platform and
2.6.18 kernel. During data transfer in WPA-PSK mode, I get below
message:
*** We Lose AP for 5 seconds ***
and wireless interface stops working

The same problem is observed on the PC

I upgraded driver version 3.0.0.56 and it seems to be working fine on
PC. However, it crashes in ARM platform in the network layer (crash
log below). After comparing both the drivers I found that

3.0.0.56: zd1205.h : #define ZD_RX_OFFSET 00
2.22: zd1205.h: #define ZD_RX_OFFSET 0x03

After changing ZD_RX_OFFSET to 0x03 in 3.0.0.56 the crash goes off but
AP loss is still observed. In PC, 3.0.0.56 works find with
ZD_RX_OFFSET == 00 .

What is the correct value for ZD_RX_OFFSET and why value 00 value
crashes in ARM and fine on PC. Is some structure packing issue ? I
feel that if I'm able to avoid crash with ZD_RX_OFFSET == 0, then AP
loss will not be observed in new driver

Thanks
PS:
The crash log is below:
Unable to handle kernel paging request at virtual address cd7a8075
pgd = cd7fc000
[cd7a8075] *pgd=8d60041e(bad)
Internal error: Oops: 1 [#1]
Modules linked in: fuse r8187 ieee80211_rtl ieee80211_crypt_ccmp_rtl
ieee80211_crypt_tkip_rtl ieee80211_crypt_wep_rtl ieee80211_crypt_rtl
arusb_lnx zd1211b mafv2 idecode ividio dm420_codec imanage davinci_resizer
CPU: 0
PC is at tcp_rcv_established+0x20/0x7e4
LR is at tcp_v4_do_rcv+0x12c/0x3a0
pc : [c0228ad8]lr : [c023165c]Tainted: P
sp : cd7e5d24  ip : 031c  fp : cd7e5d4c
r10:   r9 : 0f08  r8 : cc803534
r7 : cc8031e0  r6 : cd7a8069  r5 : cfee3720  r4 : cc8031e0
r3 : 05c8  r2 : cd7a8069  r1 : cfee3720  r0 : 003a
Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  Segment user
Control: 5317F  Table: 8D7FC000  DAC: 0015
Process ftpget (pid: 1473, stack limit = 0xcd7e4250)
Stack: (0xcd7e5d24 to 0xcd7e6000)
5d20:  cc80348c cfee3720 cc8031e0 cc8031e0 cc803534 0f08

5d40: cd7e5d84 cd7e5d50 c023165c c0228ac8 cd7e5d5c c01f199c c00476c4
cc80348c
5d60: cc8031e0  cc8031e0 cc803534 0f08  cd7e5da0
cd7e5d88
5d80: c0220624 c0231540 cd7e4000  c02e28f0 cd7e5df0 cd7e5da4
c0220c5c
5da0: c02205d0 05a8 cc803234 0001 cd7d2820 10f8 cd7e5e68
7fff
5dc0: 8d70e428 0001 cd7e5e68  c02e28f0 c3846120 c3846120
cd7e4000
5de0: cd7e5f78 cd7e5e1c cd7e5df4 c01f2a2c c022081c  
cd7e5e00
5e00:  c027daec 2000 cd538740 cd7e5e40 cd7e5e20 c01ee558
c01f29f4
5e20:  cd7e5eac 2000 00145010 cd7e5ef4 cd7e5ea0 cd7e5e44
c01ee698
5e40: c01ee4b4 0001 c07ff4d0 c07ff4d0  2000 cd538740
4013
5e60:  cd7e5e68   cd7e5e84 0001 

5e80:  001466b0 0960 cd7e5eac cd7e5eac cd7e5f48 cd7e5ea8
c0085f2c
5ea0: c01ee638   000c cd7e5f04  0001

5ec0: c3846120     cd7d2820 

5ee0: cd7e5f00 cd7d2820 c00588c4 cd7e5eec cd7e5eec  
cd7e5e48
5f00: c0026724 0003 00145010 c02e0cdc  c3846120 

5f20:  c3846120 00145010 2000  cd7e4000 cd7e5f78
cd7e5f74
5f40: cd7e5f4c c00860e0 c0085e7c c00b5a78 c3846140 c3846120 cd7e5f78

5f60:  0004 cd7e5fa4 cd7e5f78 c00863ac c0085f84 

5f80:  05a8 2000 00145010 0003 c0025fc4 
cd7e5fa8
5fa0: c0025e20 c0086370 05a8 2000 0004 00145010 2000
07ffad06
5fc0: 05a8 2000 00145010 0004 0005 0005 0004
bebdaf44
5fe0:  bebdaaf8 36d8 40173e10 6010 0004 

Backtrace:
[c0228ab8] (tcp_rcv_established+0x0/0x7e4) from [c023165c]
(tcp_v4_do_rcv+0x12c/0x3a0)
[c0231530] (tcp_v4_do_rcv+0x0/0x3a0) from [c0220624]
(tcp_prequeue_process+0x64/0x90)
[c02205c0] (tcp_prequeue_process+0x0/0x90) from [c0220c5c]
(tcp_recvmsg+0x450/0x88c)
 r6 = C02E28F0  r5 =   r4 = CD7E4000
[c022080c] (tcp_recvmsg+0x0/0x88c) from [c01f2a2c]
(sock_common_recvmsg+0x48/0x5c)
[c01f29e4] (sock_common_recvmsg+0x0/0x5c) from [c01ee558]
(do_sock_read+0xb4/0xb8)
 r6 = CD538740  r5 = 2000  r4 = C027DAEC
[c01ee4a4] (do_sock_read+0x0/0xb8) from [c01ee698]
(sock_aio_read+0x74/0x7c)
 r7 = CD7E5EF4  r6 = 00145010  r5 = 2000  r4 = CD7E5EAC
[c01ee628] (sock_aio_read+0x4/0x7c) from [c0085f2c]
(do_sync_read+0xc0/0x108)
 r4 = CD7E5EAC
[c0085e6c] (do_sync_read+0x0/0x108) from [c00860e0]
(vfs_read+0x16c/0x170)
[c0085f74] (vfs_read+0x0/0x170) from [c00863ac] (sys_read+0x4c/0x7c)
[c0086360] (sys_read+0x0/0x7c) from [c0025e20]
(ret_fast_syscall+0x0/0x2c)
 r8 = C0025FC4  r7 = 0003  r6 = 00145010  r5 = 2000
 r4 = 05A8
Code: e1a04000 e7dc e3c1 e7c4000c (e1a06002)
 0Kernel panic - not syncing: Aiee, killing interrupt handler!



-- 
Amol
Sent from Bangalore, KA, India

--
___
Zd1211-devs