CP-49659: Test modinfo
returning non-ASCII characters and fix the triggered error
#112
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.
Fix CP-49659:
modinfo
returning non-ASCII characters andXS8: If these kernel modules are loaded, the bugtool file modinfo.out is broken:
That means it should only happen if the server uses one of the two I2C sensors or the
cb710
, or the customer sets up very specific network filtering rules manually in Dom0.In these rare cases, the issue surfaces by the bugtool file
modinfo.out
having this content:Reproduced by loading one of the kernel modules using:
This command would gather data to diagnose the trigger in a specific case:
Script to produce or confirm the list of kernel modules triggering this issue on such kernel: