erasing Dblk sometimes throws SD cmd fail #65
Description
on TIB4
0.3.361 (cire831/mm@5576d5d)
mon reset
c to ImageManager
set DblkManagerP__do_erase=1
*** Panic: 18(d), w: 48(d), a: 0040 0000 0000 0000
(gdb) bt
#0 PanicP__Panic__panic (pcode=0x12, where=0x30, arg0=0x40, arg1=arg1@entry=0x0, arg2=arg2@entry=0x0, arg3=arg3@entry=0x0) at /home/cire/tag/mm_cur/tos/system/panic/PanicP.nc:755
#1 0x00000c88 in SDspP__0__Panic__panic (pcode=pcode@entry=0x12, where=where@entry=0x30, arg0=<optimized out>, arg1=arg1@entry=0x0, arg2=arg2@entry=0x0, arg3=arg3@entry=0x0) at /home/cire/tag/t2_cur/tos/interfaces/Panic.nc:101
#2 0x0000a7d2 in SDspP__0__sd_panic_idle (where=where@entry=0x30, arg=<optimized out>) at /home/cire/tag/mm_cur/tos/chips/sd/SDspP.nc:196
#3 0x0000a83e in SDspP__0__SDread__read (cid=cid@entry=0x1, blk_id=0x4041, data=0x20004454 <SSWriteP__ssw_handles+8> "\353X\220mkfs.fat") at /home/cire/tag/mm_cur/tos/chips/sd/SDspP.nc:915
#4 0x0000ae36 in DblkManagerP__SDread__read (blk_id=<optimized out>, buf=<optimized out>) at /home/cire/tag/mm_cur/tos/chips/sd/SDread.nc:37
#5 0x0000ae74 in DblkManagerP__SDResource__granted () at /home/cire/tag/mm_cur/tos/mm/DblkManagerP.nc:160
#6 0x0000af3c in ArbiterP__0__Resource__granted (arg_0x2b0b1ab31830=<optimized out>) at /home/cire/tag/t2_cur/tos/interfaces/Resource.nc:102
#7 0x0000af92 in ArbiterP__0__grantedTask__runTask () at /home/cire/tag/t2_cur/tos/system/ArbiterP.nc:356
#8 0x000121d0 in SchedulerBasicP__TaskBasic__runTask (arg_0x2b0b196639c0=<optimized out>) at /home/cire/tag/t2_cur/tos/interfaces/TaskBasic.nc:75
#9 0x0001229e in SchedulerBasicP__Scheduler__taskLoop () at /home/cire/tag/t2_cur/tos/system/SchedulerBasicP.nc:164
#10 0x000122b2 in RealMainP__Scheduler__taskLoop () at /home/cire/tag/t2_cur/tos/interfaces/Scheduler.nc:72
#11 0x000122fc in main () at /home/cire/tag/t2_cur/tos/system/RealMainP.nc:107
Strange that the SD is throwing an error.
It looks like Dblk is getting erased. But needs to be investigated.