Control: tag -1 moreinfo Control: severity -1 important Justification: does not affect all users Hi, Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> writes: > Package: linux-image-5.10.0-trunk-amd64-unsigned > Version: 5.10.1-1~exp1 > Severity: grave > Justification: renders package unusable > I just confirmed that 5.10.1-1~exp1 + btrfs boots when using a debian-testing-amd64-netinst.iso downloaded today (once the repo has been added and the package installed from experimental, of course). I tested both signed and unsigned variants. > Dear Debian kernel maintainers, > > Debian kernel 5.10.1 in experimental does not boot on my x86_64 notebook > with btrfs rootfs. > As I am suspecting btrfs as > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977645 > > This strengthen my suspicion about 5.10.1 btrfs... > > Photo of booting console is found at > https://photos.app.goo.gl/zyCg4ZH8zDgwoiBr8 > Is it possible to shift+page-up to reveal the backtrace? The backtrace section ends with "---[ end trace 75435… ]---" If that's not possible, see if you can get a copy from /var/log after rebooting with a working kernel or when using a network disk. If that's not possible, and you have good reflexes, you could try ctr+s or scroll-lock to pause the kernel output at just the right moment, but it's probably easier to just set up remote logs: https://wiki.debian.org/Rsyslog Finally, what btrfs features (profiles, compression, layers of storage, etc) are being used? Thank you, Nicholas
Attachment:
signature.asc
Description: PGP signature