Comment 3 for bug 1950448

Thanks for your last comment.

It would be more useful if you ran the `apport-collect` using the last good kernel (5.11.0-38 you mention) that worked; instead of not running apport-collect.

You can just note it was run using a different kernel due to this issue. Currently no architecture, release details, etc have been provided, ie. details usually collected by apport-collect. As a result the issue risks being missed due to missing details.

Thank you especially for providing the link to commit & reason for the issue. That is appreciated.