ioctl: Set lsp to action in nvme_get_log_persistent_event#270
Merged
igaw merged 1 commit intolinux-nvme:masterfrom Mar 2, 2022
Merged
ioctl: Set lsp to action in nvme_get_log_persistent_event#270igaw merged 1 commit intolinux-nvme:masterfrom
igaw merged 1 commit intolinux-nvme:masterfrom
Conversation
Retrieving PEL fails because the lsp is set to NVME_LOG_LSP_NONE instead of action: # nvme -persistent-event-log -a 1 /dev/nvme0 NVMe status: Command Sequence Error: The command was aborted due to a protocol violation in a multi- command sequence(0xc) Signed-off-by: Wen Xiong <wenxiong@linux.ibm.com> [dwagner: updated commit message] Signed-off-by: Daniel Wagner <dwagner@suse.de>
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
2 participants
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.
Retrieving PEL fails because the lsp is set to NVME_LOG_LSP_NONE
instead of action:
nvme -persistent-event-log -a 1 /dev/nvme0
NVMe status: Command Sequence Error: The command was aborted due to a protocol violation in a multi- command sequence(0xc)
Signed-off-by: Wen Xiong wenxiong@linux.ibm.com
[dwagner: updated commit message]
Signed-off-by: Daniel Wagner dwagner@suse.de