Skip to content

boot_test_parser: capture standard Oops messages as multiline

Anders Roxellrequested to merge
capture-new-oops-pattern into main

Standard Oops messages (e.g., "Oops: 0000 [#1] PREEMPT SMP") were only captured as single-line entries by the oneliner pattern, losing valuable diagnostic information like register dumps, call traces, and code context. The existing multiline patterns only handled special cases:

  • "exception" pattern required "---[ cut here ]---" at the start
  • "internal-error-oops" only matched ARM's "Internal error: Oops" Standard x86/x86_64 Oops messages that start directly with "Oops:" and end with "---[ end trace ]---" had no multiline pattern to capture them.

Added "oops-multiline" pattern that matches from "Oops:" to "---[ end trace ]---", capturing the complete diagnostic information including CPU state, register dump, call trace, and code context. This pattern is placed in MULTILINERS before the oneliner pattern, ensuring complete Oops reports are captured when end trace markers are present. Added test to verify multiline Oops detection.

Signed-off-by: Anders Roxell anders.roxell@linaro.org

Merge request reports