New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 652506 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

Feedback report cros_ec log should persist across reboots and sysjumps, if possible

Project Member Reported by jwer...@chromium.org, Oct 3 2016

Issue description

During a problem where the system goes into recovery mode and back, the EC gets rebooted multiple times. With our current EC console logging infrastructure, all we see in the feedback report is the time before the problem happened and right after that the "UART initialized after sysjump" from when it's all done and the EC switches back to EC-RW on the next normal boot. The interesting part in between is lost because the AP didn't retrieve it while it was happening and the EC throws it away on reboot/sysjump.

Ideally, it would be very cool if we could preserve that somehow. Shawn tells me this is hard because the console buffer is just a part of the .data section and moves around between image versions. I guess if you moved it to its own special place with a linker script that could work? (I also don't know if EC RAM get's preserved across reboots/sysjumps...?)
 
Cc: -vpalatin@chromium.org drinkcat@chromium.org
Cc: vpalatin@chromium.org
Across sysjump, we are storing at the end of RAM some preserved information with the system_add_jump_tag() mechanism, this includes a copy so it's not suitable for this use case, but we might store the console buffer close to the 'jdata' pointer.
Across real EC reboot, we are saving a few half words somewhere (eg in the RTC) nowhere near the amount you would need (and the SRAM might have been reset)
Owner: nvaccaro@chromium.org
Status: Assigned (was: Untriaged)

Sign in to add a comment