Bug#1003160:

[Batwam]

as an update to the report above, I since noticed that this issue also
occurs if I try to boot from the 5.10.0-10 kernel instead of the
original 5.10.0-09