Mac Mini 2018 kernel panic
The user says this Mac Mini worked fine with Tails 3. It now crashes with Tails 4 (see attached image) and does the same with Debian Live (Buster).
A user sent us this link which may contain some hints, but no solution yet:
- Status changed from New to Confirmed
- Assignee set to intrigeri
another mac user reported a kernel panic with tails 4.1 with two different mac (one is a macbook pro 9,1 and the other one is not described). this user says that tails 4.0 worked perfectly on those computers.
Bug report: 6c589ea7443b70b3592ec58f3f8137ca
and I just noticed that the kernel panic message is not the same so it might not be related :
[ 1.991319] Call Trace: [ 1.991342] dump_stack+0x5c/0x80 [ 1.991365] panic+0x101/0x2d7 [ 1.991388] mount_block_root+0x2c4/0x2e8 [ 1.991415] prepare_namespace+0x136/0x16c [ 1.991441] kernel_init_freeable+0x1ff/0x20a [ 1.991468] ? rest_init+0xaa/0xaa [ 1.991491] kernel_init+0xa/0x106 [ 1.991512] ret_from_fork+0x35/0x40 [ 1.991569] Kernel Offset: 0x10400000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 1.991633] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
- Assignee changed from intrigeri to numbat
Please ask the affected users to trying the following sets of boot options in syslinux:
Note (mostly to myself): the kernel error happens in the
get_cert_list function from
security/integrity/platform_certs/load_uefi.c, which reads extracts a list of certificates from an EFI variable. I'm a bit surprised this code path is triggered at all on a system that does not support Secure Boot.