tasklet_action() - Bad Kernel Trap

["Tony Mouawad" <tonym.ace@xxxxxxxxx>]

Greetings All,

 

I'm new to this group and to Linux in general.  For the last six months I have been developing Linux embedded software and have learned alot... but apparantly not enough to be able to decipher the problem I am about to describe.  At a very intermittent rate, we'll see the kernel spit out the following bad kernel trap:

 

*** ILLEGAL INSTRUCTION ***   FORMAT=4
Current process id is 824
BAD KERNEL TRAP: 00000000
Modules linked in: i2c_4bit_pcm
PC: [<c00102bc>] tasklet_action+0xbe/0xd2

SR: 2010  SP: c0733ae0  a2: c2dd92c0
d0: 00000024    d1: 00000074    d2: c01f4c60    d3: 00000009
d4: c30f230c    d5: c30b6ca0    a0: c2dd9486    a1: c01b37e8
Process cinemaprojector (pid: 824, stackpage=c2ddb2c0)
Stack from c0733ae0:
        00000074 c01f4c60 00000009 c30f230c c30b6ca0 c2dd9486 c01b37e8 c2dd92c0
        00000024 ffffffff 00000000 c30b4f90 00000000 40102010 c00102bc c018efe7
        c0190a04 000000f8 00000001 c01f3190 c00100de c01f3190 00002004 c325f814
        00000000 c0010166 0000008c c00101e8 c016a1ea 00000000 c30b6ca0 00000000
        c0733c38 c30f230c c30b6ca0 c325f810 c325f810 c0166eae c30f230c 00000000
        00000000 c30f230c c30b6ca0 c3286de4 c0733c48 c016c0a8 c30f230c 00000000
Call Trace: [<c016717e>] rpc_call_setup+0x58/0x5c
 [<c016c578>] rpc_execute+0x2e/0x60
 [<c01673d6>] rpc_call_sync+0x92/0xd8
 [<c0167344>] rpc_call_sync+0x0/0xd8
 [<c0083a6a>] nfs3_rpc_wrapper+0x36/0x84
 [<c0084418>] nfs3_proc_getattr+0x42/0x80
 [<c0079e62>] __nfs_revalidate_inode+0xce/0x7ac
 [<c007a540>] nfs_revalidate_inode+0x0/0x4a
 [<c0007a32>] recalc_task_prio+0xe6/0x1b0
 [<c0003528>] buserr_c+0x10e/0x156
 [<c000241e>] buserr+0x42/0x4c
 [<c007a55e>] nfs_revalidate_inode+0x1e/0x4a
 [<c00767a2>] nfs_lookup_revalidate+0x330/0x42a
 [<c00fd2c0>] sock_def_readable+0x70/0x72
 [<c015c28c>] unix_dgram_sendmsg+0x484/0x54a
 [<c001ea06>] autoremove_wake_function+0x0/0x3c
 [<c0003528>] buserr_c+0x10e/0x156
 [<c000241e>] buserr+0x42/0x4c
 [<c016d690>] rpcauth_lookup_credcache+0x26c/0x318
 [<c016dcae>] rpcauth_lookupcred+0x40/0x8a
 [<c005878a>] __d_lookup+0x128/0x154
 [<c004eab2>] do_lookup+0x3a/0x150
 [<c0050918>] link_path_walk+0x7ba/0xea6
 [<c00511f0>] path_lookup+0x7e/0x166
 [<c0051faa>] open_namei+0x74/0x606
 [<c003ec3c>] filp_open+0x34/0x5e
 [<c003eca0>] sys_open+0x3a/0xc6
 [<c0002538>] system_call+0x4c/0x6a

Kernel panic - not syncing: Aiee, killing interrupt handler!

The kernel version is 2.6.10 and specifically because the arch is MCF547x, a variation of m68K  and no other port has been made after that version for that arch.

Questions:

1) Can someone describe circumstance that may cause this Kernel trap to occur?

2) Can someone point me to some good documentation on how to read this kind of dump?

Your help is appreciated!

Cheerio,

Tony