On Wed, Jun 02, 2010 at 08:46:39AM +0530, sanjeev sharma wrote: > By Seeing Log cat messaged problem is in "driver_probe_device" function.
The oops message indicates pretty clearly where the error happened. > > PC is at bcm_get_stats > > +0x68/0xc8 > > pc : [<c01c4f1c>] lr : [<c01c4f08>] psr: > > 80000113 bcm_get_stats+0x68, or c01c4f1c. addr2line should be able to tell you which line of your source this corresponds to. The oops message also shows what opcode is at this address. > > sp : cf9a59b8 ip : cf9a59b8 fp : > > cf9a59e4 > > r10: 00000000 r9 : 00000000 r8 : > > 00000000 > > r7 : cfd0e494 r6 : cfd0e400 r5 : cfd0eb60 r4 : > > 00000000 > > r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : > > 00000008 > > Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment > > kernel > > Control: 10c5387d Table: 8fd40019 DAC: > > 00000017 > > > > PC: > > 0xc01c4e9c: > > 4e9c 0001716c 0001716f c041164a 00017174 c0411fa7 c041166b e1a0c00d > > e92dd830 > > 4ebc e24cb004 e24dd018 e59f30a0 e2805e36 e59fe09c e1a0c000 e5954004 > > e3a0100f > > 4edc e5932000 e3a00002 e58de000 e3a0e063 e58de004 e59fe07c e59f307c > > e58dc00c > > 4efc e58de008 e58d4010 ebfff3e0 e5951068 e3a03000 e1d526bc e2840008 > > e0822801 > > 4f1c e5842008 e5952070 e5951078 e0812002 e5842010 e595207c e5842020 The opcode is e5842008, which translates to 'str r2, [r4, #8]'. The register dump shows that r4 is 0, so this is a null pointer dereference (but the oops already told you that as well). -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
