RE: OMAP4 ES2.0 Unhandled fault: imprecise external abort
-Original Message- From: TAO HU [mailto:tgh...@motorola.com] Sent: Friday, January 14, 2011 1:29 PM To: Santosh Shilimkar Cc: Bryan Wu; TAO HU; linux-omap Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort Hi, Santosh I think it depends on whether IRQ is enabled. It is a limitation for current L3 error logging mechanism. L3 IRQ is always enabled except low power states. I guess we patched this part as well so that error is not lost and its logged. It's not a limitation L3 interrupt but behavior of CPU. Because scenario's where the I bit is cleared at CPU level (Interrupt disable), it's immune to interrupts. Note the interrupt is not lost but just got delayed a bit -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort
Hi, Santosh I think it depends on whether IRQ is enabled. It is a limitation for current L3 error logging mechanism. On Fri, Jan 14, 2011 at 3:17 PM, Santosh Shilimkar santosh.shilim...@ti.com wrote: -Original Message- From: coolo...@gmail.com [mailto:coolo...@gmail.com] On Behalf Of Bryan Wu Sent: Friday, January 14, 2011 3:08 AM To: Santosh Shilimkar Cc: TAO HU; TAO HU; linux-omap Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort On Wed, Nov 24, 2010 at 2:23 PM, Santosh Shilimkar santosh.shilim...@ti.com wrote: -Original Message- From: TAO HU [mailto:tgh...@motorola.com] Sent: Wednesday, November 24, 2010 11:40 AM To: Santosh Shilimkar Cc: TAO HU; Bryan Wu; linux-omap Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort Hi, Santosh Could you point out the specific kernel option for L3 error debugging? System Type --- [*] Enable L3 error logging I've enabled that for my Panda kernel. How to get the error log? I still got the same Unhandled fault: imprecise external abort message. Maybe L3 does not have any error at all. Strange. It should have triggered an L3 eror interrupt. -- Best Regards Hu Tao -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort
On Fri, Jan 14, 2011 at 4:06 PM, Santosh Shilimkar santosh.shilim...@ti.com wrote: -Original Message- From: TAO HU [mailto:tgh...@motorola.com] Sent: Friday, January 14, 2011 1:29 PM To: Santosh Shilimkar Cc: Bryan Wu; TAO HU; linux-omap Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort Hi, Santosh I think it depends on whether IRQ is enabled. It is a limitation for current L3 error logging mechanism. L3 IRQ is always enabled except low power states. I guess we patched this part as well so that error is not lost and its logged. It's not a limitation L3 interrupt but behavior of CPU. Because scenario's where the I bit is cleared at CPU level (Interrupt disable), it's immune to interrupts. Note the interrupt is not lost but just got delayed a bit Is there any testcase I can try to make sure the L3 error interrupt is working? Thanks, -- Bryan Wu bryan...@canonical.com Kernel Developer +86.138-1617-6545 Mobile Ubuntu Kernel Team Canonical Ltd. www.canonical.com Ubuntu - Linux for human beings | www.ubuntu.com -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: OMAP4 ES2.0 Unhandled fault: imprecise external abort
-Original Message- From: coolo...@gmail.com [mailto:coolo...@gmail.com] On Behalf Of Bryan Wu Sent: Friday, January 14, 2011 11:24 PM To: Santosh Shilimkar Cc: TAO HU; TAO HU; linux-omap Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort On Fri, Jan 14, 2011 at 4:06 PM, Santosh Shilimkar santosh.shilim...@ti.com wrote: -Original Message- From: TAO HU [mailto:tgh...@motorola.com] Sent: Friday, January 14, 2011 1:29 PM To: Santosh Shilimkar Cc: Bryan Wu; TAO HU; linux-omap Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort Hi, Santosh I think it depends on whether IRQ is enabled. It is a limitation for current L3 error logging mechanism. L3 IRQ is always enabled except low power states. I guess we patched this part as well so that error is not lost and its logged. It's not a limitation L3 interrupt but behavior of CPU. Because scenario's where the I bit is cleared at CPU level (Interrupt disable), it's immune to interrupts. Note the interrupt is not lost but just got delayed a bit Is there any testcase I can try to make sure the L3 error interrupt is working? I guess with simple readmem to some non-initalised modules should trigger the error. Just read the change log of the patch. I guess there are couple of examples -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort
On Wed, Nov 24, 2010 at 2:23 PM, Santosh Shilimkar santosh.shilim...@ti.com wrote: -Original Message- From: TAO HU [mailto:tgh...@motorola.com] Sent: Wednesday, November 24, 2010 11:40 AM To: Santosh Shilimkar Cc: TAO HU; Bryan Wu; linux-omap Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort Hi, Santosh Could you point out the specific kernel option for L3 error debugging? System Type --- [*] Enable L3 error logging I've enabled that for my Panda kernel. How to get the error log? I still got the same Unhandled fault: imprecise external abort message. Maybe L3 does not have any error at all. Thanks a lot, -- Bryan Wu bryan...@canonical.com Kernel Developer +86.138-1617-6545 Mobile Ubuntu Kernel Team Canonical Ltd. www.canonical.com Ubuntu - Linux for human beings | www.ubuntu.com -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: OMAP4 ES2.0 Unhandled fault: imprecise external abort
-Original Message- From: coolo...@gmail.com [mailto:coolo...@gmail.com] On Behalf Of Bryan Wu Sent: Friday, January 14, 2011 3:08 AM To: Santosh Shilimkar Cc: TAO HU; TAO HU; linux-omap Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort On Wed, Nov 24, 2010 at 2:23 PM, Santosh Shilimkar santosh.shilim...@ti.com wrote: -Original Message- From: TAO HU [mailto:tgh...@motorola.com] Sent: Wednesday, November 24, 2010 11:40 AM To: Santosh Shilimkar Cc: TAO HU; Bryan Wu; linux-omap Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort Hi, Santosh Could you point out the specific kernel option for L3 error debugging? System Type --- [*] Enable L3 error logging I've enabled that for my Panda kernel. How to get the error log? I still got the same Unhandled fault: imprecise external abort message. Maybe L3 does not have any error at all. Strange. It should have triggered an L3 eror interrupt. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
OMAP4 ES2.0 Unhandled fault: imprecise external abort
Hi, All We got following errors on OMAP ES2.0 board. And noticed a similar case was reported at below link http://www.opensubscriber.com/message/kernel-t...@lists.ubuntu.com/14591440.html Is any conclusion/fix available? 1[ 348.873840] Unhandled fault: imprecise external abort (0x1406) at 0x462d301c 1[ 348.885040] Unhandled fault: imprecise external abort (0x1406) at 0xbe8fec78 1[ 348.897247] Unhandled fault: imprecise external abort (0x1406) at 0xbe8fec78 1[ 348.954772] Unhandled fault: imprecise external abort (0x1406) at 0xb000c454 1[ 348.967590] Unhandled fault: imprecise external abort (0x1406) at 0xb000c454 1[ 348.989471] Unhandled fault: imprecise external abort (0x1406) at 0xbeb02fb8 4[ 349.006683] Process 2664(coredump) has RLIMIT_CORE set to 1 4[ 349.012481] Aborting core 1[ 349.023040] Unhandled fault: imprecise external abort (0x1406) at 0xbeb02fb8 1[ 349.041625] Unhandled fault: imprecise external abort (0x1406) at 0xbed6cfbc 4[ 349.061370] Process 2665(kkk) has RLIMIT_CORE set to 1 4[ 349.067810] Aborting core 0[ 349.077362] Kernel panic - not syncing: Attempted to kill init! -- Best Regards Hu Tao -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort
Tao Hu, Did you try the similar solution in our Ubuntu kernel? We suspect it related to HIGHMEM, SMP and cache control code. And how about your test case? Thanks a lot, -Bryan On Wed, Nov 24, 2010 at 11:11 AM, TAO HU tgh...@motorola.com wrote: Hi, All We got following errors on OMAP ES2.0 board. And noticed a similar case was reported at below link http://www.opensubscriber.com/message/kernel-t...@lists.ubuntu.com/14591440.html Is any conclusion/fix available? 1[ 348.873840] Unhandled fault: imprecise external abort (0x1406) at 0x462d301c 1[ 348.885040] Unhandled fault: imprecise external abort (0x1406) at 0xbe8fec78 1[ 348.897247] Unhandled fault: imprecise external abort (0x1406) at 0xbe8fec78 1[ 348.954772] Unhandled fault: imprecise external abort (0x1406) at 0xb000c454 1[ 348.967590] Unhandled fault: imprecise external abort (0x1406) at 0xb000c454 1[ 348.989471] Unhandled fault: imprecise external abort (0x1406) at 0xbeb02fb8 4[ 349.006683] Process 2664(coredump) has RLIMIT_CORE set to 1 4[ 349.012481] Aborting core 1[ 349.023040] Unhandled fault: imprecise external abort (0x1406) at 0xbeb02fb8 1[ 349.041625] Unhandled fault: imprecise external abort (0x1406) at 0xbed6cfbc 4[ 349.061370] Process 2665(kkk) has RLIMIT_CORE set to 1 4[ 349.067810] Aborting core 0[ 349.077362] Kernel panic - not syncing: Attempted to kill init! -- Best Regards Hu Tao -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort
Hi, Bryan Thanks. Unfortunately, it is not easy to reproduce the problem in our HW. We only observed 2~3 times so far. But we do enable HIGHMEM, SMP and L2 cache in our config. That's why I'd like to know the root cause. On Wed, Nov 24, 2010 at 12:21 PM, Bryan Wu bryan...@canonical.com wrote: Tao Hu, Did you try the similar solution in our Ubuntu kernel? We suspect it related to HIGHMEM, SMP and cache control code. And how about your test case? Thanks a lot, -Bryan On Wed, Nov 24, 2010 at 11:11 AM, TAO HU tgh...@motorola.com wrote: Hi, All We got following errors on OMAP ES2.0 board. And noticed a similar case was reported at below link http://www.opensubscriber.com/message/kernel-t...@lists.ubuntu.com/14591440.html Is any conclusion/fix available? 1[ 348.873840] Unhandled fault: imprecise external abort (0x1406) at 0x462d301c 1[ 348.885040] Unhandled fault: imprecise external abort (0x1406) at 0xbe8fec78 1[ 348.897247] Unhandled fault: imprecise external abort (0x1406) at 0xbe8fec78 1[ 348.954772] Unhandled fault: imprecise external abort (0x1406) at 0xb000c454 1[ 348.967590] Unhandled fault: imprecise external abort (0x1406) at 0xb000c454 1[ 348.989471] Unhandled fault: imprecise external abort (0x1406) at 0xbeb02fb8 4[ 349.006683] Process 2664(coredump) has RLIMIT_CORE set to 1 4[ 349.012481] Aborting core 1[ 349.023040] Unhandled fault: imprecise external abort (0x1406) at 0xbeb02fb8 1[ 349.041625] Unhandled fault: imprecise external abort (0x1406) at 0xbed6cfbc 4[ 349.061370] Process 2665(kkk) has RLIMIT_CORE set to 1 4[ 349.067810] Aborting core 0[ 349.077362] Kernel panic - not syncing: Attempted to kill init! -- Best Regards Hu Tao -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Best Regards Hu Tao -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort
Hu Tao, We hit this issue every time when we build the kernel on the board. Are you running some stress testing program on the board? Thanks, -Bryan On Wed, Nov 24, 2010 at 12:34 PM, TAO HU tgh...@motorola.com wrote: Hi, Bryan Thanks. Unfortunately, it is not easy to reproduce the problem in our HW. We only observed 2~3 times so far. But we do enable HIGHMEM, SMP and L2 cache in our config. That's why I'd like to know the root cause. On Wed, Nov 24, 2010 at 12:21 PM, Bryan Wu bryan...@canonical.com wrote: Tao Hu, Did you try the similar solution in our Ubuntu kernel? We suspect it related to HIGHMEM, SMP and cache control code. And how about your test case? Thanks a lot, -Bryan On Wed, Nov 24, 2010 at 11:11 AM, TAO HU tgh...@motorola.com wrote: Hi, All We got following errors on OMAP ES2.0 board. And noticed a similar case was reported at below link http://www.opensubscriber.com/message/kernel-t...@lists.ubuntu.com/14591440.html Is any conclusion/fix available? 1[ 348.873840] Unhandled fault: imprecise external abort (0x1406) at 0x462d301c 1[ 348.885040] Unhandled fault: imprecise external abort (0x1406) at 0xbe8fec78 1[ 348.897247] Unhandled fault: imprecise external abort (0x1406) at 0xbe8fec78 1[ 348.954772] Unhandled fault: imprecise external abort (0x1406) at 0xb000c454 1[ 348.967590] Unhandled fault: imprecise external abort (0x1406) at 0xb000c454 1[ 348.989471] Unhandled fault: imprecise external abort (0x1406) at 0xbeb02fb8 4[ 349.006683] Process 2664(coredump) has RLIMIT_CORE set to 1 4[ 349.012481] Aborting core 1[ 349.023040] Unhandled fault: imprecise external abort (0x1406) at 0xbeb02fb8 1[ 349.041625] Unhandled fault: imprecise external abort (0x1406) at 0xbed6cfbc 4[ 349.061370] Process 2665(kkk) has RLIMIT_CORE set to 1 4[ 349.067810] Aborting core 0[ 349.077362] Kernel panic - not syncing: Attempted to kill init! -- Best Regards Hu Tao -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Best Regards Hu Tao -- Bryan Wu bryan...@canonical.com Kernel Developer +86.138-1617-6545 Mobile Ubuntu Kernel Team Canonical Ltd. www.canonical.com Ubuntu - Linux for human beings | www.ubuntu.com -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: OMAP4 ES2.0 Unhandled fault: imprecise external abort
TAO, -Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of TAO HU Sent: Wednesday, November 24, 2010 10:05 AM To: Bryan Wu Cc: TAO HU; linux-omap Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort Hi, Bryan Thanks. Unfortunately, it is not easy to reproduce the problem in our HW. We only observed 2~3 times so far. But we do enable HIGHMEM, SMP and L2 cache in our config. That's why I'd like to know the root cause. On Wed, Nov 24, 2010 at 12:21 PM, Bryan Wu bryan...@canonical.com wrote: Tao Hu, Did you try the similar solution in our Ubuntu kernel? We suspect it related to HIGHMEM, SMP and cache control code. And how about your test case? Thanks a lot, -Bryan On Wed, Nov 24, 2010 at 11:11 AM, TAO HU tgh...@motorola.com wrote: Hi, All We got following errors on OMAP ES2.0 board. And noticed a similar case was reported at below link http://www.opensubscriber.com/message/kernel- t...@lists.ubuntu.com/14591440.html Is any conclusion/fix available? 1[ 348.873840] Unhandled fault: imprecise external abort (0x1406) at 0x462d301c 1[ 348.885040] Unhandled fault: imprecise external abort (0x1406) at 0xbe8fec78 1[ 348.897247] Unhandled fault: imprecise external abort (0x1406) at 0xbe8fec78 1[ 348.954772] Unhandled fault: imprecise external abort (0x1406) at 0xb000c454 1[ 348.967590] Unhandled fault: imprecise external abort (0x1406) at 0xb000c454 1[ 348.989471] Unhandled fault: imprecise external abort (0x1406) at 0xbeb02fb8 4[ 349.006683] Process 2664(coredump) has RLIMIT_CORE set to 1 4[ 349.012481] Aborting core 1[ 349.023040] Unhandled fault: imprecise external abort (0x1406) at 0xbeb02fb8 1[ 349.041625] Unhandled fault: imprecise external abort (0x1406) at 0xbed6cfbc 4[ 349.061370] Process 2665(kkk) has RLIMIT_CORE set to 1 4[ 349.067810] Aborting core 0[ 349.077362] Kernel panic - not syncing: Attempted to kill init! Can you enable the L3 error debugging and see the crash log?? On your build this option should be available. It should point you to offending HW initiator/target. I still don't have a cleaned up version I could submit to LO Regards, Santosh -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort
Hi, Santosh Could you point out the specific kernel option for L3 error debugging? On Wed, Nov 24, 2010 at 1:40 PM, Santosh Shilimkar santosh.shilim...@ti.com wrote: TAO, -Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of TAO HU Sent: Wednesday, November 24, 2010 10:05 AM To: Bryan Wu Cc: TAO HU; linux-omap Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort Hi, Bryan Thanks. Unfortunately, it is not easy to reproduce the problem in our HW. We only observed 2~3 times so far. But we do enable HIGHMEM, SMP and L2 cache in our config. That's why I'd like to know the root cause. On Wed, Nov 24, 2010 at 12:21 PM, Bryan Wu bryan...@canonical.com wrote: Tao Hu, Did you try the similar solution in our Ubuntu kernel? We suspect it related to HIGHMEM, SMP and cache control code. And how about your test case? Thanks a lot, -Bryan On Wed, Nov 24, 2010 at 11:11 AM, TAO HU tgh...@motorola.com wrote: Hi, All We got following errors on OMAP ES2.0 board. And noticed a similar case was reported at below link http://www.opensubscriber.com/message/kernel- t...@lists.ubuntu.com/14591440.html Is any conclusion/fix available? 1[ 348.873840] Unhandled fault: imprecise external abort (0x1406) at 0x462d301c 1[ 348.885040] Unhandled fault: imprecise external abort (0x1406) at 0xbe8fec78 1[ 348.897247] Unhandled fault: imprecise external abort (0x1406) at 0xbe8fec78 1[ 348.954772] Unhandled fault: imprecise external abort (0x1406) at 0xb000c454 1[ 348.967590] Unhandled fault: imprecise external abort (0x1406) at 0xb000c454 1[ 348.989471] Unhandled fault: imprecise external abort (0x1406) at 0xbeb02fb8 4[ 349.006683] Process 2664(coredump) has RLIMIT_CORE set to 1 4[ 349.012481] Aborting core 1[ 349.023040] Unhandled fault: imprecise external abort (0x1406) at 0xbeb02fb8 1[ 349.041625] Unhandled fault: imprecise external abort (0x1406) at 0xbed6cfbc 4[ 349.061370] Process 2665(kkk) has RLIMIT_CORE set to 1 4[ 349.067810] Aborting core 0[ 349.077362] Kernel panic - not syncing: Attempted to kill init! Can you enable the L3 error debugging and see the crash log?? On your build this option should be available. It should point you to offending HW initiator/target. I still don't have a cleaned up version I could submit to LO Regards, Santosh -- Best Regards Hu Tao -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: OMAP4 ES2.0 Unhandled fault: imprecise external abort
-Original Message- From: TAO HU [mailto:tgh...@motorola.com] Sent: Wednesday, November 24, 2010 11:40 AM To: Santosh Shilimkar Cc: TAO HU; Bryan Wu; linux-omap Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort Hi, Santosh Could you point out the specific kernel option for L3 error debugging? System Type --- [*] Enable L3 error logging -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
