On 11/12/2018 15:23, Mark Brown wrote:
On Tue, Dec 11, 2018 at 05:10:16AM -0800, kernelci.org bot wrote:
Today's -next fails to boot on D05:
defconfig: hip07-d05: lab-collabora: new failure (last pass: next-20181210)It takes an oops during IPMI initialization:
09:51:45.224591 [ 87.646247] ipmi_si: Adding SMBIOS-specified bt state machine 09:51:45.242352 [ 87.652129] ipmi_si: Trying SMBIOS-specified bt state machine at i/o address 0xe4, slave address 0x0, irq 0 09:51:45.242646 [ 87.661875] Unable to handle kernel paging request at virtual address ffff7dfffee000e4
...
09:51:45.429194 [ 87.845965] Call trace: 09:51:45.429426 [ 87.848400] logic_inb+0x80/0xb8 09:51:45.429640 [ 87.851620] port_inb+0x18/0x20 [ipmi_si] 09:51:45.443075 [ 87.855620] bt_detect+0x40/0x250 [ipmi_si] 09:51:45.443320 [ 87.859793] try_smi_init+0x1a8/0x868 [ipmi_si] 09:51:45.443539 [ 87.864313] init_ipmi_si+0x190/0x220 [ipmi_si]
...
09:51:45.479097 [ 87.910207] udevd[2569]: worker [2589] terminated by signal 11 (Segmentation fault) 09:51:45.501664 [ 87.917863] udevd[2569]: worker [2589] failed while handling '/devices/platform/dmi-ipmi-si.0'
Hi Mark,
I have seen this issue previously. It would be specific to D05. I think that there is an issue with the FW in this board, in that DMI reports IPMI support incorrectly.
Could we add a kernel command-line to avoid IPMI detection from DMI, ipmi_si.trydmi=0
Thanks, John
Full details here, including bisection information and full logs:
https://kernelci.org/boot/id/5c0f88d259b514823d4925c0/
Unfortunately it looks like the bug has actually been around for a while but wasn't stopping us getting to a prompt:
https://storage.kernelci.org/next/master/next-20181210/arm64/defconfig/lab-c...
and it might still be some unrelated hang there.