Hi Vincent! On Sun, Oct 03, 2021 at 09:36:10PM +0200, Vincent Blut wrote: > Le 2021-10-03 20:58, Salvatore Bonaccorso a écrit : > > Hi Vincent, > > > > On Sun, Oct 03, 2021 at 03:55:21PM +0200, Vincent Blut wrote: > > > Hi, > > > > > > Le 2021-10-03 11:40, Nathanael Schweers a écrit : > > > > > > > > Salvatore Bonaccorso <car...@debian.org> writes: > > > > > > > > > Control: tags -1 + moreinfo > > > > > > > > > > Hi Nathanael, > > > > > > > > > > On Sun, Oct 03, 2021 at 10:02:35AM +0200, Nathanael Schweers wrote: > > > > >> Package: src:linux > > > > >> Version: 5.14.6-3 > > > > >> Severity: grave > > > > >> Justification: renders package unusable > > > > >> > > > > >> Dear Maintainer, > > > > >> > > > > >> using this kernel, my machine no longer boots. Instead of showing a > > > > >> prompt to > > > > >> enter the LUKS passphrase (as is done in version > > > > >> linux-image-5.10.0-7-amd64) a > > > > >> non-blinking cursor is shown. Nothing happens afterwards. > > > > >> > > > > >> Version linux-image-5.10.0-7-amd64 still works, but newer versions > > > > >> (linux-image-5.10.0-8-amd64 and the version this report is for) > > > > >> produce the > > > > >> behaviour mentioned above. > > > > >> > > > > >> I’m afraid that I don’t have a decent idea on what extra information > > > > >> to provide. > > > > > > > > > > Could you please confirm that booting with the 'mem_encrypt=off' > > > > > kernel command line heps? > > > > > > > > With this option the kernel does indeed boot. Thanks for the tip! > > > > > > Salvatore, given the increase in bug reports that this feature generates, > > > I think it would be sensible to unset AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT > > > until > > > those incompatibilities are fixed, like I proposed in [1]. One would have > > > to > > > use the "mem_encrypt=on" command line option to enable the AMD Secure > > > Memory > > > Encryption. If it sounds reasonable to you and the rest of the kernel > > > team, > > > I can send a merge request. > > > > Yes I think at this point is reasonable, as people wanting the feature > > still can enable it, but we do not break usual setups as it has hit > > severral people arleady. Can you post the reference [1], it was not > > included. No need for a merge request, as I have the change already > > in debian/config/kernelarch-x86/config . > > Oops, sorry about that. [1] was supposed to point to > https://salsa.debian.org/kernel-team/linux/-/merge_requests/322/diffs
Ah thanks! We should have done that probably already at that time. Pushed now the change to sid branch, so will be included in next upload for unstable. Regards, Salvatore
