linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Mark Brown <broonie@kernel.org>, <catalin.marinas@arm.com>,
	<will.deacon@arm.com>, Wei Xu <xuwei5@hisilicon.com>
Cc: linux-arm-kernel@lists.infradead.org,
	kernel-build-reports@lists.linaro.org
Subject: Re: next/master boot: 175 boots: 18 failed, 143 passed with 10 offline, 1 untried/unknown, 3 conflicts (next-20181211)
Date: Tue, 11 Dec 2018 16:24:10 +0000	[thread overview]
Message-ID: <e6995b4a-184a-d8d4-f4d4-9ce75d8f47c0@huawei.com> (raw)
In-Reply-To: <20181211152311.GK6686@sirena.org.uk>

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-collabora/boot-hip07-d05.html
>
> and it might still be some unrelated hang there.
>



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2018-12-11 16:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5c0fb738.1c69fb81.f62ad.3f45@mx.google.com>
2018-12-11 15:23 ` next/master boot: 175 boots: 18 failed, 143 passed with 10 offline, 1 untried/unknown, 3 conflicts (next-20181211) Mark Brown
2018-12-11 16:24   ` John Garry [this message]
2018-12-11 16:50     ` Mark Brown
2018-12-11 17:23       ` Guillaume Tucker
2018-12-11 20:15       ` Wei Xu
2018-12-13 16:16         ` John Garry
2018-12-11 16:35   ` Will Deacon
2018-12-11 16:48     ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e6995b4a-184a-d8d4-f4d4-9ce75d8f47c0@huawei.com \
    --to=john.garry@huawei.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=will.deacon@arm.com \
    --cc=xuwei5@hisilicon.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).