Crashtool.py: Automated crashtool #890
Open
Conversation
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
shirishaganta1
force-pushed
the
crashtool
branch
from
9cfb6b6 to
b026c38
Compare
|
working fine on sles15sp7 and rhel97 as well |
|
@PraveenPenguin Do we need to add package installation for kdump-debuginfo / or Will that be added to top level script that takes care all the required packages? |
sacsant
reviewed
Jul 3, 2025
testcases/Crashtool.py
Outdated
| # | ||
| # OpenPOWER Automated Test Project | ||
| # | ||
| # Contributors Listed Below - COPYRIGHT 2022 |
There was a problem hiding this comment.
yeah will take care of that
testcases/Crashtool.py
Outdated
| self.cv_HOST = conf.host() | ||
| self.console = self.cv_SYSTEM.console.get_console() | ||
| self.cv_SYSTEM.goto_state(OpSystemState.OS) | ||
| self.commands = ["log", "bt", "ps", "runq", "kmem -i", "kmem -o", "kmem -h", "vm"] |
There was a problem hiding this comment.
Can you also capture o/p of following commands?
- sys
- mach
- bt -a
- kmem -s
- mod
There was a problem hiding this comment.
Even can this command can be command line driven as well
| vmlinux = f"{vmlinux} {debug_info}" | ||
|
|
||
| elif 'SLES' in res[0] or 'SLES' in res[1]: | ||
| vmlinux = f"/boot/vmlinux-{kernel_version}" |
There was a problem hiding this comment.
Don't we need debug vmlinux with previous SLES releases?
There was a problem hiding this comment.
tested on sles15sp7 .. it worked fine
1.Detects and validates the latest crash dump (vmcore) under /var/crash/ 2.Identifies appropriate debug symbols (vmlinux) based on the OS (e.g., RHEL or SLES) 3.Launches crash vmlinux vmcore in interactive mode on the console 4.Executes a sequence of commands (log, bt, ps, etc.) in a single session 5.Verifies command output and exits cleanly from the crash shell 6. Done changes to OptestConfiguration.py in order to make crash-commands as command line driven as well Signed-off-by: Shirisha G <shirisha@linux.ibm.com>
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.
1.Detects and validates the latest crash dump (vmcore) under /var/crash/
2.Identifies appropriate debug symbols (vmlinux) based on the OS (e.g., RHEL or SLES)
3.Launches crash vmlinux vmcore in interactive mode on the console
4.Executes a sequence of commands (log, bt, ps, etc.) in a single session
5.Verifies command output and exits cleanly from the crash shell