![acpi mat001f panasonic acpi mat001f panasonic](https://passlhunter.weebly.com/uploads/1/2/6/8/126894478/503330413_orig.jpg)
x86/fpu: xstate_offset: 896, xstate_sizes: 64 x86/fpu: xstate_offset: 832, xstate_sizes: 64 x86/fpu: xstate_offset: 576, xstate_sizes: 256 x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' microcode: microcode updated early to revision 0xe0, date = If I remember it correctly, all files are lzo-compressed. > Finally, what btrfs features (profiles, compression, layers of storage, I found that once in ten times, booting succeeds and I got dmesg and /proc/mounts > kernel output at just the right moment, > have good reflexes, you could try ctr+s or scroll-lock to pause the var/log/kern.log does not have information of 5.10.1. > see if you can get a copy from /var/log after rebooting with a working (but I do not have a way to type a username.)īoot failures themselves are unreliable. I tried today, booting failed at a later point than reported originally In addition, I tried to boot it several times, and almost everytime Shift+arrow-up shows mixture of console and gdm starting up screen My laptop has combined page-up + arrow-up. > Is it possible to shift+page-up to reveal the backtrace? The backtrace
![acpi mat001f panasonic acpi mat001f panasonic](https://cstan.io/wp-content/uploads/2016/04/ASUS_P9D-M.jpg)
Kernel output at just the right moment, but it's probably easier to justįinally, what btrfs features (profiles, compression, layers of storage,ĭate: Sat, 11:30:47 +0900 (JST) Hi Nicholas, Have good reflexes, you could try ctr+s or scroll-lock to pause the See if you can get a copy from /var/log after rebooting with a working Section ends with "-" If that's not possible, Is it possible to shift+page-up to reveal the backtrace? The backtrace > This strengthen my suspicion about 5.10.1 btrfs. > Debian kernel 5.10.1 in experimental does not boot on my x86_64 notebook Tested both signed and unsigned variants. I just confirmed that 5.10.1-1~exp1 + btrfs boots when using aĭebian-testing-amd64-netinst.iso downloaded today (once the repo hasīeen added and the package installed from experimental, of course). > Justification: renders package unusable > Package: linux-image-5.10.0-trunk-amd64-unsigned