Kconfig: Temporarily disable HAVE_HW_BREAKPOINT feature flag
Recent 8660 bootup failures on the .38 kernel have been traced to changes in hw_breakpoint.c that occasionally trigger a debug_event on bootup, invoking a preconfigured hardware breakpoint which causes the Scorpion cores to halt execution. This prevents the target from booting successfully, and the exact cause of these debug events is not yet known. This patch simply disables hardware breakpoint support for the time being; this is only meant to be a stopgap measure to unblock automation testing. This is done by manually disabling the HAVE_HW_BREAKPOINTS feature flag in the Kconfig. Currently there is no Kconfig menu option to disable this flag in a "clean" way without also disabling PERF_EVENTS (this is still needed for performance profiling). Change-Id: Iedbd5690908a3ce2bcbf289a2a9cb09fd1ce7d67 Conflicts: arch/arm/Kconfig Signed-off-by: David Garibaldi <dgaribal@codeaurora.org>
This commit is contained in:
parent
a21ec56a1e
commit
480a82f597
|
@ -24,7 +24,7 @@ config ARM
|
|||
select HAVE_PERF_EVENTS
|
||||
select PERF_USE_VMALLOC
|
||||
select HAVE_REGS_AND_STACK_ACCESS_API
|
||||
select HAVE_HW_BREAKPOINT if (PERF_EVENTS && (CPU_V6 || CPU_V6K || CPU_V7))
|
||||
#select HAVE_HW_BREAKPOINT if (PERF_EVENTS && (CPU_V6 || CPU_V6K || CPU_V7))
|
||||
select HAVE_C_RECORDMCOUNT
|
||||
select HAVE_GENERIC_HARDIRQS
|
||||
select HAVE_SPARSE_IRQ
|
||||
|
|
Loading…
Reference in New Issue