linux - crash during kernel initialization (module insmod) -


im using monta-vista linux 2.6.10. during kernel initialization, while registering modules "insmod", following kernel dump happens after rebooting 7,000 times.

dmy touch panel filter driver version ver.1.0.0 major=200 usbdmy_init dmy usb-driver ver.1.0.5 usbdmy_probe vendor=$afa product=$3e8 usbdmy_probe: endpoint irq-in 1 ,interval=1 unable handle kernel null pointer dereference @ virtual address 00000000 pgd = c7a28000 [00000000] *pgd=a79fd031, *pte=00000000, *ppte=00000000 internal error: oops: 817 [#1] modules linked in: usbdmy tpdmy cpu: 0 pc @ __free_pages+0x24/0x64 lr @ free_task+0x1c/0x34 pc : [<c005df04>]    lr : [<c003833c>]    tainted: p sp : c7e51eb0  ip : c7e51ec0  fp : c7e51ebc r10: c7ddf3c8  r9 : 00000005  r8 : 00000000 r7 : 00000000  r6 : c7e50000  r5 : c7ddf320  r4 : c7ddf320 r3 : ffffffff  r2 : 00000000  r1 : 00000001  r0 : c03eb900 flags: nzcv  irqs on  fiqs on  mode svc_32  segment user control: 397f  table: a7a28000  dac: 00000015 process default.hotplug (pid: 953, stack limit = 0xc7e501b0) stack: (0xc7e51eb0 0xc7e52000) 1ea0:                                     c7e51ed4 c7e51ec0 c003833c c005deec 1ec0: c7ddf320 c7ddf320 c7e51efc c7e51ed8 c003c924 c003832c c785e6c0 000003ba 1ee0: c7ddf320 c7e50000 c7ddf320 00000000 c7e51f84 c7e51f00 c003efbc c003c7b8 1f00: c785e6c0 4000cba4 c7a28000 00000000 c7a28000 c7861b60 00000000 c7861ac0 1f20: 7efff034 ffffffff 00000000 c7861ac0 c0036dec 00000000 00000000 c7e51f48 1f40: 00000000 c7861ac0 c0036dec c7861bc4 c7861bc4 c7e51fb0 00000001 ffffffea 1f60: 7efff034 ffffffff 00000072 c00231f4 c7e50000 00900072 c7e51fa4 c7e51f88 1f80: c003f404 c003e6a0 00000000 ffffffff c7e51fec 00000001 00000000 c7e51fa8 1fa0: c0022a60 c003f3d8 00000001 7efff034 ffffffff 7efff034 00000001 00000000 1fc0: 00000001 7efff034 ffffffff 000b4388 00000000 ffffffff 00000000 00000000 1fe0: 40018d30 7efff000 400f67a0 400f67c0 60000010 ffffffff 00000000 00000000 backtrace: [<c005dee0>] (__free_pages+0x0/0x64) [<c003833c>] (free_task+0x1c/0x34) [<c0038320>] (free_task+0x0/0x34) [<c003c924>] (release_task+0x178/0x188)  r4 = c7ddf320 [<c003c7ac>] (release_task+0x0/0x188) [<c003efbc>] (do_wait+0x928/0xca8)  r8 = 00000000  r7 = c7ddf320  r6 = c7e50000  r5 = c7ddf320  r4 = 000003ba [<c003e694>] (do_wait+0x0/0xca8) [<c003f404>] (sys_wait4+0x38/0x4c) [<c003f3cc>] (sys_wait4+0x0/0x4c) [<c0022a60>] (ret_fast_syscall+0x0/0x2c)  r4 = 00000001 code: e2132001 189da800 e5903004 e3730001 (05822000)  prev->state: 2 != task_running?? default.hotplug/953: bug in __schedule @ kernel/sched.c:2905 unable handle kernel null pointer dereference @ virtual address 00000000 pgd = c7a3c000 [00000000] *pgd=a79a6031, *pte=00000000, *ppte=00000000 internal error: oops: 817 [#2] modules linked in: usbdmy tpdmy cpu: 0 pc @ __free_pages+0x24/0x64 lr @ free_task+0x1c/0x34 pc : [<c005df04>]    lr : [<c003833c>]    tainted: p sp : c7a27eb0  ip : c7a27ec0  fp : c7a27ebc r10: c7861b68  r9 : 00000005  r8 : 00000000 r7 : 00000000  r6 : c7a26000  r5 : c7861ac0  r4 : c7861ac0 r3 : ffffffff  r2 : 00000000  r1 : 00000001  r0 : c03ebfc0 flags: nzcv  irqs on  fiqs on  mode svc_32  segment user control: 397f  table: a7a3c000  dac: 00000015 process default.hotplug (pid: 948, stack limit = 0xc7a261b0) stack: (0xc7a27eb0 0xc7a28000) 7ea0:                                     c7a27ed4 c7a27ec0 c003833c c005deec 7ec0: c7861ac0 c7861ac0 c7a27efc c7a27ed8 c003c924 c003832c c0016040 000003cb 7ee0: c7861ac0 c7a26000 c7861ac0 00000000 c7a27f84 c7a27f00 c003efbc c003c7b8 7f00: 00000000 00000001 c7a3c000 00000000 c7a3c000 c7ddf140 00000000 c7ddf0a0 7f20: 7efff684 ffffffff 00000000 c7ddf0a0 c0036dec 00000000 00000000 c7a27f48 7f40: 00000000 c7ddf0a0 c0036dec c7ddf1a4 c7ddf1a4 c7a27fb0 00000000 ffffffea 7f60: 7efff684 ffffffff 00000072 c00231f4 c7a26000 00900072 c7a27fa4 c7a27f88 7f80: c003f404 c003e6a0 00000000 ffffffff c7a27fec 00000001 00000000 c7a27fa8 7fa0: c0022a60 c003f3d8 00000001 7efff684 ffffffff 7efff684 00000001 00000000 7fc0: 00000001 7efff684 ffffffff 00000003 00000000 00000001 00000003 00000000 7fe0: 40018d30 7efff650 400f67a0 400f67c0 60000010 ffffffff 763074f6 0000023c backtrace: [<c005dee0>] (__free_pages+0x0/0x64) [<c003833c>] (free_task+0x1c/0x34) [<c0038320>] (free_task+0x0/0x34) [<c003c924>] (release_task+0x178/0x188)  r4 = c7861ac0 [<c003c7ac>] (release_task+0x0/0x188) [<c003efbc>] (do_wait+0x928/0xca8)  r8 = 00000000  r7 = c7861ac0  r6 = c7a26000  r5 = c7861ac0  r4 = 000003cb [<c003e694>] (do_wait+0x0/0xca8) [<c003f404>] (sys_wait4+0x38/0x4c) [<c003f3cc>] (sys_wait4+0x0/0x4c) [<c0022a60>] (ret_fast_syscall+0x0/0x2c)  r4 = 00000001 code: e2132001 189da800 e5903004 e3730001 (05822000)  prev->state: 2 != task_running?? default.hotplug/948: bug in __schedule @ kernel/sched.c:2905 usbdmy_specify : len=2 data=$06 $00 drivers/usb/core/file.c: looking minor, starting @ 181 unable handle kernel paging request @ virtual address 0000a000 pgd = c0004000 [0000a000] *pgd=00000000 internal error: oops: 817 [#3] modules linked in: usbdmy tpdmy cpu: 0 pc @ memcpy+0x5c/0x5a0 lr @ copy_process+0xbc/0xe14 pc : [<c010a4bc>]    lr : [<c0039300>]    tainted: p sp : c0467e0c  ip : 00000000  fp : c0467e34 r10: 00804111  r9 : 00000000  r8 : 00000000 r7 : 00000000  r6 : 00000000  r5 : 00000000  r4 : 00000000 r3 : 00000000  r2 : 00000030  r1 : c0466120  r0 : 00009ff4 flags: nzcv  irqs on  fiqs on  mode svc_32  segment kernel control: 397f  table: a7a38000  dac: 00000017 process khelper (pid: 5, stack limit = 0xc04661b0) stack: (0xc0467e0c 0xc0468000) 7e00:                            00009ef4 c7ddfd20 c042f2c0 00009ef4 c0466000 7e20: fffffff4 c02d8388 c0467e7c c0467e38 c0039300 c010a46c 00000000 c0467ed8 7e40: 00000000 00000000 c0467ed8 00000000 00200200 00000000 00804111 000003cc 7e60: c0466000 00000000 00000000 c0467ed8 c0467ecc c0467e80 c003a1c4 c0039250 7e80: 00000000 00000000 000003cc c0467e98 00000000 c0467e94 c0467e94 c7ddfaa0 7ea0: c0467ecc 00804111 c0467ed8 c7a01d60 c004c548 c0431ec0 c7a01d60 c0431ec8 7ec0: c0467f3c c0467ed0 c002557c c003a100 00000000 00000000 00000000 c7a01d60 7ee0: c004c548 c003d5f0 00000000 00000000 00000000 00000000 00000000 00000000 7f00: 00000000 00000000 00000000 00000000 00000000 c0024d50 00000013 00000000 7f20: c7a01d60 c7a01d28 c0466000 00000000 c0467f54 c0467f40 c004c6c4 c0025514 7f40: c7a01e1c c7a01d2c c0467fc4 c0467f58 c004cccc c004c698 c0451f2c c004c68c 7f60: ffffffff ffffffff 00000001 00000000 c0036dec 00010000 00000000 c0466000 7f80: 00000000 c042f2c0 c0036dec 00100100 00200200 00000000 c0467fc4 c0431ec0 7fa0: c0466000 c0451f28 c004cac8 fffffffc 00000000 00000000 c0467ff4 c0467fc8 7fc0: c0051b74 c004cad4 ffffffff ffffffff 00000000 00000000 00000000 00000000 7fe0: 00000000 00000000 00000000 c0467ff8 c003d5f0 c0051a98 cc33cc33 cc33cc33 backtrace: [<c010a460>] (memcpy+0x0/0x5a0) [<c0039300>] (copy_process+0xbc/0xe14)  r9 = c02d8388  r8 = fffffff4  r7 = c0466000  r6 = 00009ef4  r5 = c042f2c0  r4 = c7ddfd20  r0 = 00009ef4 [<c0039244>] (copy_process+0x0/0xe14) [<c003a1c4>] (do_fork+0xd0/0x1e8) [<c003a0f4>] (do_fork+0x0/0x1e8) [<c002557c>] (kernel_thread+0x74/0x84) [<c0025508>] (kernel_thread+0x0/0x84) [<c004c6c4>] (__call_usermodehelper+0x38/0x74)  r7 = 00000000  r6 = c0466000  r5 = c7a01d28  r4 = c7a01d60 [<c004c68c>] (__call_usermodehelper+0x0/0x74) [<c004cccc>] (worker_thread+0x204/0x2c0)  r4 = c7a01d2c [<c004cac8>] (worker_thread+0x0/0x2c0) [<c0051b74>] (kthread+0xe8/0x11c) [<c0051a8c>] (kthread+0x0/0x11c) [<c003d5f0>] (do_exit+0x0/0xd8c)  r8 = 00000000  r7 = 00000000  r6 = 00000000  r5 = 00000000  r4 = 00000000 code: f5d1f03c f5d1f05c e8b113f8 e2522020 (a8a013f8) 

i wonder if guys me on why such error appears. thanks.

i think kernel or module binaries corrupted.

because state boot device cf card, , had script continually reboot 7000 times, appears me cf card had endure quite bit of write activity.

it newer flash media devices emmc , micro-sd cards typically have hardware support flash wear leveling, , can (almost) safely used ext3/ext4 file systems.

for older flash media (like cf cards), proper flash wear leveling not typically implemented, , takes few days (sometimes hours) wear out.

my suggestion check every single file on system if check-sum matches of good, working system. in case @ least 1 file not check out correctly.


Comments

Popular posts from this blog

php - Wordpress website dashboard page or post editor content is not showing but front end data is showing properly -

How to get the ip address of VM and use it to configure SSH connection dynamically in Ansible -

javascript - Get parameter of GET request -