From: Jason Cooper <jason@lakedaemon.net>
To: "Kevin's boot bot" <khilman@linaro.org>,
Corey Minyard <minyard@acm.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Gregory CLEMENT <gregory.clement@free-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org,
openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>
Subject: IPMI misbehaving on ARM defconfigs, was [Re: stable boot: 18 pass, 4 fail (v3.10.39)]
Date: Wed, 7 May 2014 10:20:56 -0400 [thread overview]
Message-ID: <20140507142056.GD28159@titan.lakedaemon.net> (raw)
In-Reply-To: <5369063f.4291420a.03aa.495e@mx.google.com>
Cory, all,
On our ARM boot farm, we've started seeing the following:
On Tue, May 06, 2014 at 08:56:47AM -0700, Kevin's boot bot wrote:
>
> Tree/Branch: stable
> Git describe: v3.10.39
> Failed boot tests (console logs at the end)
> ===========================================
> da850-evm: FAIL: arm-davinci_all_defconfig
> armada-xp-openblocks-ax3-4: FAIL: arm-multi_v7_defconfig
> armada-370-mirabox: FAIL: arm-multi_v7_defconfig
> sun4i-a10-cubieboard: FAIL: arm-multi_v7_defconfig
>
...
> arm-multi_v7_defconfig
> ----------------------
>
> armada-xp-openblocks-ax3-4: FAIL: last 80 lines of boot log:
> ------------------------------------------------------------
>
> pps_core: LinuxPPS API ver. 1 registered
> pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
> PTP clock support registered
> EDAC MC: Ver: 3.0.0
> Switching to clocksource armada_370_xp_clocksource
> bounce pool size: 64 pages
> Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
> io scheduler noop registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> armada-xp-pinctrl d0018000.pinctrl: registered pinctrl driver
> ipmi message handler version 39.2
> IPMI System Interface driver.
> ipmi_si: Adding default-specified kcs state machine
> ipmi_si: Trying default-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
> ipmi_si: Could not set up I/O space
> Trying to free nonexistent resource <0000000000000ca2-0000000000000ca2>
> Trying to free nonexistent resource <0000000000000ca3-0000000000000ca3>
> ipmi_si: Adding default-specified smic state machine
> ipmi_si: Trying default-specified smic state machine at i/o address 0xca9, slave address 0x0, irq 0
> ipmi_si: Could not set up I/O space
> Trying to free nonexistent resource <0000000000000ca9-0000000000000ca9>
> Trying to free nonexistent resource <0000000000000caa-0000000000000caa>
> Trying to free nonexistent resource <0000000000000cab-0000000000000cab>
> ipmi_si: Adding default-specified bt state machine
> ipmi_si: Trying default-specified bt state machine at i/o address 0xe4, slave address 0x0, irq 0
> ipmi_si: Could not set up I/O space
> Trying to free nonexistent resource <00000000000000e4-00000000000000e4>
> Trying to free nonexistent resource <00000000000000e5-00000000000000e5>
> Trying to free nonexistent resource <00000000000000e6-00000000000000e6>
> ipmi_si: Unable to find any System Interface(s)
> Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
...
It appears to be unrelated to the failure this original message was
about. However, the failure brought the above to our attention. :)
Is the IPMI driver used on ARM? Documentation/IPMI.txt indicates a
dependency on ACPI, but that isn't reflected in the Kconfig. At any
rate, it seems rather unhappy. :(
thx,
Jason.
next parent reply other threads:[~2014-05-07 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5369063f.4291420a.03aa.495e@mx.google.com>
2014-05-07 14:20 ` Jason Cooper [this message]
2014-05-07 14:31 ` Corey Minyard
2014-05-07 15:12 ` Jason Cooper
2014-05-07 14:44 ` Arnd Bergmann
2014-05-07 14:56 ` Jason Cooper
2014-05-07 19:36 ` Kevin Hilman
2014-05-07 20:28 ` Jason Cooper
2014-05-07 20:31 ` Kevin Hilman
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=20140507142056.GD28159@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=andrew@lunn.ch \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=khilman@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=sebastian.hesselbarth@googlemail.com \
--cc=thomas.petazzoni@free-electrons.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
all inboxes | Powered by JetHome®