On Tue, Aug 9, 2011 at 2:57 PM, Jason Kridner <jkrid...@beagleboard.org> wrote: > On Tue, Aug 9, 2011 at 5:48 PM, Joel A Fernandes <agnel.j...@gmail.com> wrote: >> Hi Jason, >> >> Thanks, >> >> On Tue, Aug 9, 2011 at 3:48 PM, Jason Kridner <jkrid...@beagleboard.org> >> wrote: >>> Adding Steve... >>> >>> On Tue, Aug 9, 2011 at 4:19 PM, Joel A Fernandes <agnel.j...@gmail.com> >>> wrote: >>>> I am seeing some very erratic memory corruption issues all morning, >>>> both with NFS and MMC cards. The traces are at the end of this email. >>>> >>>> I have narrowed down the issue to one of the 13 Sakoman patches: > ... >>>> file://sakoman/0009-rtc-twl-Switch-to-using-threaded-irq.patch \ >>> >>> I'm not familiar with the impact or the arguments being passed. If >>> some upstream changes happened in this area, this one might be a bit >>> dangerous. >>> >> >> This is it! Adding 0009 back causes the same irq problems to show up. >> Do we need this patch for now?
Interesting -- that patch has been queued for inclusion upstream and I've been using it for a while with no issues. I wonder what is different in our setups. Looking at linux-omap I see that a new version of the patch was submitted on July 27: [PATCH 1/2] rtc: twl: Use threaded IRQ, remove IRQ enable in interrupt handler [PATCH 2/2] rtc: twl: Fix registration vs. init order Steve > > I think you can leave it out for now. Are all the other ones back in? > Will you be sharing another test image? > >> >> [ 13.945648] LR is at run_timer_softirq+0x18c/0x22c >> [..] >> [ 14.091674] [<c0077744>] (run_timer_softirq+0x18c/0x22c) from >> [<c0073064>] (__do_softirq+0x6c/0xf4) >> [ 14.101165] [<c0073064>] (__do_softirq+0x6c/0xf4) from [<c0073228>] >> (irq_exit+0x40/0x8c) >> [ 14.109619] [<c0073228>] (irq_exit+0x40/0x8c) from [<c003c064>] >> (asm_do_IRQ+0x64/0x84) >> [ 14.117919] [<c003c064>] (asm_do_IRQ+0x64/0x84) from [<c0041278>] >> (__irq_svc+0x38/0xc0) >> [ 14.126281] Exception stack(0xc0655f40 to 0xc0655f88) >> [ 14.131591] 5f40: c065bd80 c067dea0 40000013 40000013 00000c0e >> 00000000 f3b00000 000039bd >> [ 14.140136] 5f60: 3dd059da 00000003 ffff70f5 ffff70f5 00000108 >> c0655f88 c0068718 c00915ac >> [ 14.148681] 5f80: 40000013 ffffffff >> [ 14.152343] [<c0041278>] (__irq_svc+0x38/0xc0) from [<c00915ac>] >> (tick_nohz_stop_sched_tick+0x35c/0x3a4) >> [ 14.162261] [<c00915ac>] (tick_nohz_stop_sched_tick+0x35c/0x3a4) >> from [<c00425e8>] (cpu_idle+0x1c/0xac) >> [ 14.172088] [<c00425e8>] (cpu_idle+0x1c/0xac) from [<c0008904>] >> (start_kernel+0x290/0x2f0) >> [ 14.180755] [<c0008904>] (start_kernel+0x290/0x2f0) from >> [<8000803c>] (0x8000803c) >> [ 14.188659] Code: 00000000 00000000 00000000 c37e0000 (e7f39999) >> [ 14.195648] ---[ end trace c21d9089cb6595cf ]--- >> [ 14.200469] Kernel panic - not syncing: Fatal exception in interrupt >> >> >> Thanks, >> Joel >> >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core >> > > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
