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.shilimkar@xxxxxx> wrote: > TAO, >> -----Original Message----- >> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- >> owner@xxxxxxxxxxxxxxx] 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.wu@xxxxxxxxxxxxx> > 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 <tghk48@xxxxxxxxxxxx> 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- >> team@xxxxxxxxxxxxxxxx/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(kkkkkkkkkkkkkkk) 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
