[Q] Kernel panic - not syncing: EXT4-fs . Please help diagnose, fix the issue

People..

I have been having an issue with random boots, no matter what kernel or ROM I try. So I tried to peek in to the kernel messages and it appears there are bad blocks. Is this the actual problem or there is a hidden problem somewhere else which manifests in t this. If bad block is the problem, how do I get by this. I tried running e2fsck on all mmcblk that I could. Can someone please look at this log and help me diagnose or correct this? This is a GSM phone i9250

[ 65.844818] dhd_set_suspend: force extra Suspend setting
[ 65.853912] dhd_get_dtim_skip beacom=100 msec bcn_li_dtim=1 DTIM=1 Listen=10
[ 66.850738] init: untracked pid 182 exited
[ 73.293121] mmcblk0: error -110 transferring data, sector 2399352, nr 136, cm
d response 0x900, card status 0xd00
[ 73.293487] end_request: I/O error, dev mmcblk0, sector 2399352
[ 73.293731] end_request: I/O error, dev mmcblk0, sector 2399360
[ 73.293884] end_request: I/O error, dev mmcblk0, sector 2399368
[ 73.294128] end_request: I/O error, dev mmcblk0, sector 2399376
[ 73.294250] end_request: I/O error, dev mmcblk0, sector 2399384
[ 73.294494] end_request: I/O error, dev mmcblk0, sector 2399392
[ 73.294616] end_request: I/O error, dev mmcblk0, sector 2399400
[ 73.294860] end_request: I/O error, dev mmcblk0, sector 2399408
[ 73.295104] end_request: I/O error, dev mmcblk0, sector 2399416
[ 73.295227] end_request: I/O error, dev mmcblk0, sector 2399424
[ 73.295471] end_request: I/O error, dev mmcblk0, sector 2399432
[ 73.295593] end_request: I/O error, dev mmcblk0, sector 2399440
[ 73.295837] end_request: I/O error, dev mmcblk0, sector 2399448
[ 73.295959] end_request: I/O error, dev mmcblk0, sector 2399456
[ 73.296203] end_request: I/O error, dev mmcblk0, sector 2399464
[ 73.296325] end_request: I/O error, dev mmcblk0, sector 2399472
[ 73.296569] end_request: I/O error, dev mmcblk0, sector 2399480
[ 73.297027] Aborting journal on device mmcblk0p12-8.
[ 73.300842] EXT4-fs error (device mmcblk0p12) in ext4_reserve_inode_write:566
9: Journal has aborted
[ 73.304840] EXT4-fs error (device mmcblk0p12) in ext4_reserve_inode_write:566
9: Journal has aborted
[ 73.373870] journal commit I/O error
[ 73.374206] journal commit I/O error
[ 73.670410] Kernel panic - not syncing: EXT4-fs (device mmcblk0p12): panic fo
rced after error
[ 73.670440]
[ 73.670959] CPU0: stopping
[ 73.671142] Backtrace:
[ 73.671478] [<c00672e0>] (dump_backtrace+0x0/0x138) from [<c065016c>] (dump_s
tack+0x18/0x1c)
[ 73.671813] r6:c07df290 r5:c0850e08 r4:00000000 r3:00000000
[ 73.672607] [<c0650154>] (dump_stack+0x0/0x1c) from [<c005cad0>] (do_IPI+0x1e
0/0x218)
[ 73.672790] [<c005c8f0>] (do_IPI+0x0/0x218) from [<c0062748>] (__irq_svc+0x48
/0xe4)
[ 73.673095] Exception stack(0xc07d1ec8 to 0xc07d1f10)
[ 73.673278] 1ec0: c07d1f10 00004360 26b9c9c5 00000011 26b52
1ad 00000011
[ 73.673614] 1ee0: c11e1210 c005c5d4 c11e1210 c0850c5c c0850c00 c07d1f44 00000
011 c07d1f10
[ 73.673919] 1f00: c0096940 c007f3c4 600f0013 ffffffff
[ 73.674133] [<c007f380>] (omap4_enter_idle_wfi+0x0/0xd8) from [<c0458c24>] (c
puidle_idle_call+0xb0/0x13c)
[ 73.674438] r8:c0850cd0 r7:c08d1998 r6:c11e1210 r5:c07d0000 r4:c11e1220
[ 73.675506] [<c0458b74>] (cpuidle_idle_call+0x0/0x13c) from [<c0064244>] (cpu
_idle+0xe0/0x120)
[ 73.675689] r7:c082df5c r6:c0733708 r5:c07f5958 r4:c07d0000
[ 73.676605] [<c0064164>] (cpu_idle+0x0/0x120) from [<c0641078>] (rest_init+0x
a8/0xc4)
[ 73.676910] r8:c07def84 r7:c004ec5c r6:00000002 r5:c005c5d4 r4:c07d0000
[ 73.677703] r3:00000001
[ 73.678161] [<c0640fd0>] (rest_init+0x0/0xc4) from [<c0008a8c>] (start_kernel
+0x304/0x360)
[ 73.678466] r6:00000000 r5:c0850c80 r4:c07df120 r3:00000000
[ 73.679412] [<c0008788>] (start_kernel+0x0/0x360) from [<80008040>] (0x800080
40)
[ 73.679565] Rebooting in 5 seconds..
[ 77.797241] Restarting Linux version 3.0.101-franco.Kernel-nightly (francisco
@francisco) (gcc version 4.7 (GCC) ) #394 SMP PREEMPT Thu Nov 28 02:43:50 WET 20
13
[ 77.797271]