[#4056] Sometimes irdaping will cause kernel hang up
Submitted By: Vivi Li
Open Date
2008-04-23 07:52:45 Close Date
2009-03-03 02:50:34
Priority:
Very Low Assignee:
Graf Yang
Status:
Closed Fixed In Release:
N/A
Found In Release:
2008R1.5-RC3 Release:
Category:
N/A Board:
N/A
Processor:
BF537 Silicon Revision:
Is this bug repeatable?:
Yes Resolution:
Fixed
Uboot version or rev.:
Toolchain version or rev.:
08r1-rc8
App binary format:
N/A
Summary: Sometimes irdaping will cause kernel hang up
Details:
On BF537-STAMP, kernel sometimes hang up after irdaping several times.
Eg: irdaping 100 times from borad A to B and then irdaping from B to A. This hang up usually happens when one of the borad is v1.3.
For those are both v1.1 borad, hang up is not that frequent.
Eg:
on board A which is hang up, we can see before hang up, it send a file to board B.
root:/> modprobe bfin_sir
root:/> irattach irda0 -s &
159
root:/> ircp /bin/busybox
Connecting...done
Sending /bin/busybox...done
Disconnecting...done
root:/>
On board B, it's not hang up and we can see:
Case 4 ...PASS
daddr=0x28132886
irdaping 0x28132886
IrDA ping (0x28132886 on irda0): 32 bytes
32 bytes from 0x28132886: irda_seq=1 time=124.00 ms.
32 bytes from 0x28132886: irda_seq=2 time=104.00 ms.
32 bytes from 0x28132886: irda_seq=4 time=116.00 ms.
32 bytes from 0x28132886: irda_seq=5 time=108.00 ms.
32 bytes from 0x28132886: irda_seq=7 time=116.00 ms.
32 bytes from 0x28132886: irda_seq=8 time=112.00 ms.
32 bytes from 0x28132886: irda_seq=10 time=124.00 ms.
32 bytes from 0x28132886: irda_seq=11 time=104.00 ms.
32 bytes from 0x28132886: irda_seq=13 time=108.00 ms.
32 bytes from 0x28132886: irda_seq=14 time=112.00 ms.
32 bytes from 0x28132886: irda_seq=16 time=116.00 ms.
32 bytes from 0x28132886: irda_seq=17 time=116.00 ms.
32 bytes from 0x28132886: irda_seq=19 time=116.00 ms.
32 bytes from 0x28132886: irda_seq=20 time=124.00 ms.
32 bytes from 0x28132886: irda_seq=22 time=104.00 ms.
32 bytes from 0x28132886: irda_seq=23 time=116.00 ms.
32 bytes from 0x28132886: irda_seq=25 time=116.00 ms.
32 bytes from 0x28132886: irda_seq=26 time=112.00 ms.
32 bytes from 0x28132886: irda_seq=28 time=124.00 ms.
32 bytes from 0x28132886: irda_seq=29 time=104.00 ms.
32 bytes from 0x28132886: irda_seq=31 time=108.00 ms.
32 bytes from 0x28132886: irda_seq=32 time=112.00 ms.
32 bytes from 0x28132886: irda_seq=34 time=116.00 ms.
32 bytes from 0x28132886: irda_seq=35 time=120.00 ms.
32 bytes from 0x28132886: irda_seq=37 time=120.00 ms.
32 bytes from 0x28132886: irda_seq=38 time=108.00 ms.
32 bytes from 0x28132886: irda_seq=40 time=116.00 ms.
32 bytes from 0x28132886: irda_seq=41 time=108.00 ms.
32 bytes from 0x28132886: irda_seq=43 time=120.00 ms.
32 bytes from 0x28132886: irda_seq=44 time=112.00 ms.
32 bytes from 0x28132886: irda_seq=46 time=112.00 ms.
32 bytes from 0x28132886: irda_seq=47 time=112.00 ms.
32 bytes from 0x28132886: irda_seq=49 time=108.00 ms.
32 bytes from 0x28132886: irda_seq=50 time=116.00 ms.
32 bytes from 0x28132886: irda_seq=52 time=116.00 ms.
32 bytes from 0x28132886: irda_seq=53 time=124.00 ms.
32 bytes from 0x28132886: irda_seq=55 time=104.00 ms.
32 bytes from 0x28132886: irda_seq=56 time=104.00 ms.
32 bytes from 0x28132886: irda_seq=58 time=120.00 ms.
32 bytes from 0x28132886: irda_seq=59 time=112.00 ms.
32 bytes from 0x28132886: irda_seq=61 time=112.00 ms.
32 bytes from 0x28132886: irda_seq=62 time=104.00 ms.
32 bytes from 0x28132886: irda_seq=64 time=108.00 ms.
32 bytes from 0x28132886: irda_seq=65 time=112.00 ms.
32 bytes from 0x28132886: irda_seq=67 time=116.00 ms.
32 bytes from 0x28132886: irda_seq=68 time=120.00 ms.
32 bytes from 0x28132886: irda_seq=70 time=120.00 ms.
32 bytes from 0x28132886: irda_seq=71 time=108.00 ms.
32 bytes from 0x28132886: irda_seq=73 time=116.00 ms.
32 bytes from 0x28132886: irda_seq=74 time=112.00 ms.
32 bytes from 0x28132886: irda_seq=76 time=120.00 ms.
32 bytes from 0x28132886: irda_seq=77 time=120.00 ms.
32 bytes from 0x28132886: irda_seq=79 time=116.00 ms.
32 bytes from 0x28132886: irda_seq=80 time=104.00 ms.
Follow-ups
--- Graf Yang 2008-08-05 00:06:54
This issue existed when three irda devices connected together. Put the priority
to low.
--- Robin Getz 2008-08-05 15:16:01
Graf:
How do we know that this is an issue that can be pushed off until we understand
it better?
If you can't recreate the issue with 3 non-Blackfin devices - then it is
something in our driver which needs to be fixed - isn't it?
-Robin
--- Graf Yang 2008-08-22 08:31:48
I recreate this issue, when connected one blackfin and two none blackfin.
The driver do have some problem. The root cause is IR module not respond to
incoming data (no interrupt come).
Now have fixed driver issue. I need investigate why IR module not respond to
the incoming data.
Files
Changes
Commits
Dependencies
Duplicates
Associations
Tags
File Name File Type File Size Posted By
No Files Were Found