Repository navigation
arm64: dts: exynos: google: gs101-raven: add the ramoops region - #111
Merged
derekross merged 1 commit intoOct 28, 2026
Merged
Conversation
Raven's kernel has CONFIG_PSTORE_RAM, but its device tree has no ramoops region, so a panic or a watchdog reset leaves nothing in /sys/fs/pstore: an unexplained reset on raven could not be traced. Describe the region Google's gs101 kernel uses (gs101-rmem.dtsi), with its console and pmsg sizes, as gs201-cheetah does. On raven, 0xfd3ff000-0xfd7fefff is System RAM between the bootloader's debug-kinfo region below and its log region at 0xfd800000 above, and no reserved-memory node in the bootloader's tree overlaps it. Tested on raven (as an overlay on 7.3.0-rc6, gb3d6253b0d61): ramoops binds at 0xfd3ff000 with 2 MiB console and 2 MiB pmsg. A pmsg record survived a PSCI warm reset (reboot mode warm, SYSTEM_RESET2) and was gone after the default cold one. The console zone comes back holding the bootloader's own log, which it writes there at every boot, including the reset status (RST_STAT) and reboot reason it read, so the cause of the last reset is recorded either way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: saiththerobo <the.tom.sharp@gmail.com>
Owner
|
Thanks. The region is exactly Google's Merging. Your other raven DT PRs from today all add at the end of |
This was referenced Oct 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Raven's kernel has
CONFIG_PSTORE_RAM, but its device tree has no ramoops region, so a panic or a watchdog reset leaves nothing in/sys/fs/pstore, and an unexplained reset on raven can't be traced.This describes the region Google's gs101 kernel uses (
gs101-rmem.dtsi), with its console and pmsg sizes, as gs201-cheetah does. On raven, 0xfd3ff000–0xfd7fefff is System RAM between the bootloader's debug-kinfo region and its log region, and no reserved-memory node in the bootloader's tree overlaps it.Tested on raven (7.3.0-rc6): ramoops binds at 0xfd3ff000 with 2 MiB console and 2 MiB pmsg. A pmsg record survived a PSCI warm reset and was gone after the default cold one. The console zone comes back holding the bootloader's own log, including the reset status (
RST_STAT) and reboot reason, so the cause of the last reset is recorded either way. The phone has run it since 2026-10-27.tools/kernel-pr-checkpasses with--build; the 2 checkpatch warnings are theCo-Authored-By:trailer, as in #8.🤖 Generated with Claude Code