Just to clarify: The first post of this bug (message #5) shows boot
parameter `intel_iommu=off`. With that parameter, the bug does NOT
reproduce. I was just using a safe environment to practice reportbug
with, when it suddenly sent out the report already.
To reproduce the bug, use
Hi Debian kernel team,
Sorry for the short report yesterday. Reportbug sent it out earlier
than I expected. Here is the full report:
* What led up to the situation?
On Debian 10 buster, I upgraded the linux kernel packages from
4.19+105+deb10u12 (buster) to 5.10.46-4~bpo10+1
Details to follow tomorrow (bisected already, how to reproduce)
Package: src:linux
Version: 5.10.46-4~bpo10+1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was
4 matches
Mail list logo