2010-03-11 02:10:11 driver of vnt6656 on BF561 uClinux (２)
chaotian jing (AFGHANISTAN)
Message: 87070
ＯＫ,Thank you for the support of this problem. the schedule problem is resolved(Because I made a mistake)
Now, sometime the driver is working well. But sometimes It will miss a old problem is:
NULL pointer access (probably)
then the system is reboot.I don't know how this problem is caused.
Just this command
insmod vntwusb.ko
ifconfig eth1 up
then the NULL pointer will access.. ，No other tips can help me trace the mistake. when this two command running when system start by added into /etc/inittab.this trace will printed
vntwusb: no version magic, tainting kernel.
vntwusb: module license 'unspecified' taints kernel.
Symbol _usb_register_driver is being used by a non-GPL module, which will not be allowed in the future
Please see the file Documentation/feature-removal-schedule.txt in the kernel source tree for more details.
Symbol _usb_deregister is being used by a non-GPL module, which will not be allowed in the future
Please see the file Documentation/feature-removal-schedule.txt in the kernel source tree for more details.
/home/besovideo/uClinux-dist-2008R1.5/VT6656_linux_src_v1.19.19_bfin/driver/main_usb.c: VIA Networking Wireless LAN USB Driver 1.19.19
usbcore: registered new interface driver vntwusb
Read Zonetype file sucess,use default zonetype setting[02]
***BBbVT3184Init,1450
***BBbVT3184Init,1470
NULL pointer access (probably)
CURRENT PROCESS:
COMM=busybox PID=702
TEXT = 0x01880040-0x018c6160 DATA = 0x018c6164-0x018d9d24
BSS = 0x018d9d24-0x018ef584 USER-STACK = 0x018fff7c
return address: [0x0188d11e]; contents of:
0x0188d0f0: 0c00 17f5 6000 e801 0000 0528 0010 434b
0x0188d100: c682 8043 5603 c682 8280 e146 7efe e147
0x0188d110: 8101 3212 5748 e106 feff e107 0100 [9012]
0x0188d120: 5032 43d1 5808 5438 0c00 1408 5815 5070
RETE: 00000000 RETN: 007e3f84 RETX: 0188d11e RETS: 0188d628
IPEND: 8030 SYSCFG: 0006
SEQSTAT: 00000027 SP: 007e3ea8
R0: 00002f2f R1: 2f2f0000 R2: 00000000 R3: 0000002f
R4: 0189a798 R5: 2f2f2f2f R6: 7efefeff R7: 81010100
P0: 007e3f79 P1: 00000003 P2: 00000000 P3: 007e4004
P4: 00260438 P5: 018c6164 FP: 007e3f84
A0.w: 00000000 A0.x: 00000000 A1.w: 00000000 A1.x: 00000000
LB0: 0188cfe8 LT0: 0188cfe8 LC0: 00000000
LB1: 00292be9 LT1: 00292be2 LC1: 00000000
B0: 00000000 L0: 00000000 M0: 00000000 I0: 007e3f19
B1: 00000000 L1: 00000000 M1: 00000000 I1: 00517e28
B2: 00000000 L2: 00000000 M2: 00000000 I2: 00000000
B3: 00000000 L3: 00000000 M3: 00000000 I3: 00000000
USP: 018fff7c ASTAT: 02002020
DCPLB_FAULT_ADDR=00000000
ICPLB_FAULT_ADDR=0188d11e
Hardware Trace:
0 Target : <0x000046ac> { _trap_c + 0x0 }
Source : <0xffa00ab8> { _exception_to_level5 + 0xb4 }
1 Target : <0xffa00a04> { _exception_to_level5 + 0x0 }
Source : <0xffa00a02> { _ex_trap_c + 0x4e }
2 Target : <0xffa009b4> { _ex_trap_c + 0x0 }
Source : <0xffa00b58> { _trap + 0x28 }
3 Target : <0xffa00b30> { _trap + 0x0 }
Source : <0x0188d11a> [ busybox + 0xd0da ]
4 Target : <0x0188d0fe> [ busybox + 0xd0be ]
Source : <0x0188d0ce> [ busybox + 0xd08e ]
5 Target : <0x0188d0c0> [ busybox + 0xd080 ]
Source : <0x0188d624> [ busybox + 0xd5e4 ]
6 Target : <0x0188d620> [ busybox + 0xd5e0 ]
Source : <0x0188d618> [ busybox + 0xd5d8 ]
7 Target : <0x0188d608> [ busybox + 0xd5c8 ]
Source : <0x01895502> [ busybox + 0x154c2 ]
8 Target : <0x018954e6> [ busybox + 0x154a6 ]
Source : <0x0188b7bc> [ busybox + 0xb77c ]
9 Target : <0x0188b7aa> [ busybox + 0xb76a ]
Source : <0x0188db1c> [ busybox + 0xdadc ]
10 Target : <0x0188db14> [ busybox + 0xdad4 ]
Source : <0x0188dc58> [ busybox + 0xdc18 ]
11 Target : <0x0188dc50> [ busybox + 0xdc10 ]
Source : <0x0188cfea> [ busybox + 0xcfaa ]
12 Target : <0x0188cfd8> [ busybox + 0xcf98 ]
Source : <0x0188cfd4> [ busybox + 0xcf94 ]
13 Target : <0x0188cfa8> [ busybox + 0xcf68 ]
Source : <0x0188dc4c> [ busybox + 0xdc0c ]
14 Target : <0x0188dc48> [ busybox + 0xdc08 ]
Source : <0x0188d094> [ busybox + 0xd054 ]
15 Target : <0x0188d08c> [ busybox + 0xd04c ]
Source : <0x0188cf30> [ busybox + 0xcef0 ]
Stack from 007e3e08:
00008000 0000000b 00000000 0003000b 0188d11e 01883431 0188dc20 ffa011a0
02002020 00292be9 0188cfe8 00292be2 0188cfe8 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ffa00abc 00202768 00202768 00202764 007e3f48 018ebb24 007e4004
0188d11e 00008030 00000027 00000000 007e3f84 0188d11e 0188d11e 0188d628
Call Trace:
[<00002f2f>] _do_signal+0x53/0xce0
[<00002f2f>] _do_signal+0x53/0xce0
[<00002f2f>] _do_signal+0x53/0xce0
NULL pointer access (probably)
CURRENT PROCESS:
COMM=busybox PID=702
TEXT = 0x01880040-0x018c6160 DATA = 0x018c6164-0x018d9d24
BSS = 0x018d9d24-0x018ef584 USER-STACK = 0x018fff7c
return address: [0x0188d11e]; contents of:
0x0188d0f0: 0c00 17f5 6000 e801 0000 0528 0010 434b
0x0188d100: c682 8043 5603 c682 8280 e146 7efe e147
0x0188d110: 8101 3212 5748 e106 feff e107 0100 [9012]
0x0188d120: 5032 43d1 5808 5438 0c00 1408 5815 5070
RETE: 00000000 RETN: 007e3f84 RETX: 0188d11e RETS: 0188d628
IPEND: 8030 SYSCFG: 0006
SEQSTAT: 00060027 SP: 007e3ea8
R0: 00002f2f R1: 2f2f0000 R2: 00000000 R3: 0000002f
R4: 0189a798 R5: 2f2f2f2f R6: 7efefeff R7: 81010100
P0: 007e3f79 P1: 00000003 P2: 00000000 P3: 007e4004
P4: 00260438 P5: 018c6164 FP: 007e3f84
A0.w: 00000000 A0.x: 00000000 A1.w: 00000000 A1.x: 00000000
LB0: 0188cfe8 LT0: 0188cfe8 LC0: 00000000
LB1: 00292be9 LT1: 00292be2 LC1: 00000000
B0: 00000000 L0: 00000000 M0: 00000000 I0: 007e3f19
B1: 00000000 L1: 00000000 M1: 00000000 I1: 00517e28
B2: 00000000 L2: 00000000 M2: 00000000 I2: 00000000
B3: 00000000 L3: 00000000 M3: 00000000 I3: 00000000
USP: 018fff7c ASTAT: 02002020
DCPLB_FAULT_ADDR=00000000
ICPLB_FAULT_ADDR=0188d11e
Hardware Trace:
0 Target : <0x000046ac> { _trap_c + 0x0 }
Source : <0xffa00ab8> { _exception_to_level5 + 0xb4 }
1 Target : <0xffa00a04> { _exception_to_level5 + 0x0 }
Source : <0xffa00a02> { _ex_trap_c + 0x4e }
2 Target : <0xffa009b4> { _ex_trap_c + 0x0 }
Source : <0xffa00b58> { _trap + 0x28 }
3 Target : <0xffa00b30> { _trap + 0x0 }
Source : <0xffa0103c> { __common_int_entry + 0xd8 }
4 Target : <0xffa00fda> { __common_int_entry + 0x76 }
Source : <0xffa00e1a> { _return_from_int + 0x4e }
5 Target : <0xffa00e1a> { _return_from_int + 0x4e }
Source : <0xffa00dfa> { _return_from_int + 0x2e }
6 Target : <0xffa00dcc> { _return_from_int + 0x0 }
Source : <0xffa00fd6> { __common_int_entry + 0x72 }
7 Target : <0xffa00fd4> { __common_int_entry + 0x70 }
Source : <0xffa01246> { _do_irq + 0xa2 }
8 Target : <0xffa01242> { _do_irq + 0x9e }
Source : <0xffa004fc> { _asm_do_IRQ + 0x88 }
9 Target : <0xffa004ec> { _asm_do_IRQ + 0x78 }
Source : <0x00013ffc> { _irq_exit + 0x38 }
10 Target : <0x00013ff8> { _irq_exit + 0x34 }
Source : <0x00013d12> { ___do_softirq + 0x96 }
11 Target : <0x00013d0c> { ___do_softirq + 0x90 }
Source : <0x00013c7a> { __local_bh_enable + 0xae }
12 Target : <0x00013c62> { __local_bh_enable + 0x96 }
Source : <0x00013c28> { __local_bh_enable + 0x5c }
13 Target : <0x00013c20> { __local_bh_enable + 0x54 }
Source : <0x00013be6> { __local_bh_enable + 0x1a }
14 Target : <0x00013bcc> { __local_bh_enable + 0x0 }
Source : <0x00013d08> { ___do_softirq + 0x8c }
15 Target : <0x00013d08> { ___do_softirq + 0x8c }
Source : <0x00013ce6> { ___do_softirq + 0x6a }
Stack from 007e3e08:
0000000a 0000000b 00000000 0003000b 0188d11e 00000006 ffa00382 007e3e24
007e3e24 00013cd4 00538f84 0053a9f0 00013d0c 00538f84 00029e76 ff800180
00000006 00013ff8 ffc00014 00260438 007e4004 0182fa5c 7efefeff 2f2f2f2f
00000000 ffa004b6 ffc00014 ffa004ec 00000000 00000000 00000000 ffa01242
81010100 ffa00abc 0020276c 0020276c 00202764 007e3f48 018ebb24 007e4004
01
---
who can give me some clue about it ?
***BBbVT3184Init,1450
***BBbVT3184Init,1470
NULL pointer access (probably)
may be NULL pointer access (probably) will appear when the ifconfig eth1 up is successed next time.
and may it will not appear in sometime.
QuoteReplyEditDelete
2010-03-11 02:14:11 Re: driver of vnt6656 on BF561 uClinux (２)
Sonic Zhang (CHINA)
Message: 87071
Could you share with other developers on how you solved the schedule problem?
QuoteReplyEditDelete
2010-03-11 02:32:28 Re: driver of vnt6656 on BF561 uClinux (２)
Yi Li (CHINA)
Message: 87072
chaotian,
I think you can analyze trace and debug accordingly:
docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:analyzing_traces
-Yi
QuoteReplyEditDelete
2010-03-11 03:03:33 Re: driver of vnt6656 on BF561 uClinux (２)
chaotian jing (AFGHANISTAN)
Message: 87074
It is my fault. I replaced mdelay with msleep but forgot to restore it.
QuoteReplyEditDelete
2010-03-11 03:04:28 Re: driver of vnt6656 on BF561 uClinux (２)
chaotian jing (AFGHANISTAN)
Message: 87075
Could you share with other developers on how you solved the schedule problem?
--- It is my fault. I replaced mdelay with msleep but forgot to restore it.