Skip to content

pldm: Verbose pldmd sensor and effecter log messages#66

Merged
spargaon merged 1 commit intointeg_sp8from
fwdev-188854-review
Apr 30, 2026
Merged

pldm: Verbose pldmd sensor and effecter log messages#66
spargaon merged 1 commit intointeg_sp8from
fwdev-188854-review

Conversation

@spargaon
Copy link
Copy Markdown
Collaborator

Display sensor and effecter related log entries
only if pldmd is running in verbose mode.

@spargaon
Copy link
Copy Markdown
Collaborator Author

Log sensor read or parse errors only if pldmd is
running in verbose mode.

Signed-off-by: Shirish Pargaonkar <Shirish.Pargaonkar@amd.com>
@spargaon spargaon force-pushed the fwdev-188854-review branch from 995de10 to 112b6e6 Compare April 24, 2026 19:48
@spargaon
Copy link
Copy Markdown
Collaborator Author

Such errors are logged only if the pldmd is running in verbose mode (e.g. /usr/bin/pldmd -vvvv)

Tx: 98 02 11 1e 00 00
Rx: 18 02 11 01
<3> Failed to decode response GetSensorReading for terminus ID 1, sensor Id 30, error 3.
<3> Failed to get sensor value for terminus 1, error: 3
Tx: 99 02 11 1f 00 00
Rx: 19 02 11 00 06 00 00 01 01 01 07 40 15 f3 14 25 83 00
Tx: 9a 02 11 21 00 00
Rx: 1a 02 11 02
<3> Failed to decode response GetSensorReading for terminus ID 1, sensor Id 33, error 3.
<3> Failed to get sensor value for terminus 1, error: 3

@spargaon
Copy link
Copy Markdown
Collaborator Author

The concern is, the logs can flood journalctl entries and crowd out other debugging messages

Tx: 9d 02 11 1e 00 00
Rx: 1d 02 11 01
<3> Failed to decode response GetSensorReading for terminus ID 1, sensor Id 30, error 3.
<3> Failed to get sensor value for terminus 1, error: 3
: This is normal as default fuse state is invalid, so would return rc=1

@spargaon spargaon merged commit ca6de4e into integ_sp8 Apr 30, 2026
@spargaon spargaon deleted the fwdev-188854-review branch April 30, 2026 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants