FYI...
armada-370-mirabox started failing boot tests in linux-next as of next-20141117. Excerpt of boot report below, or you can see all the recent boots of mirabox here:
http://status.armcloud.us/boot/?mirabox
I bisected it down to a PCI commit[2], but it didn't revert cleanly on top of next/master so didn't fully verify it is the root cause. I'll let one of you MVEBU maintainers take it the next step.
Thanks,
Kevin
[1]
Full Build report: http://status.armcloud.us/build/next/kernel/next-20141117/ Full Boot report: http://status.armcloud.us/boot/all/job/next/kernel/next-20141117/
Tree/Branch: next Git describe: next-20141117
Failed boot tests
armada-370-mirabox: FAIL: arm-multi_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y http://storage.armcloud.us/kernel-ci/next/next-20141117/arm-multi_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y/boot-armada-370-mirabox.html armada-370-mirabox: FAIL: arm-multi_v7_defconfig http://storage.armcloud.us/kernel-ci/next/next-20141117/arm-multi_v7_defconfig/boot-armada-370-mirabox.html
[...]
armada-370-mirabox: FAIL: arm-mvebu_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y http://storage.armcloud.us/kernel-ci/next/next-20141117/arm-mvebu_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y/boot-armada-370-mirabox.html armada-370-mirabox: FAIL: arm-mvebu_v7_defconfig http://storage.armcloud.us/kernel-ci/next/next-20141117/arm-mvebu_v7_defconfig/boot-armada-370-mirabox.html
[2] 7ea945f0bb49423451dbf222f62c6fabc857aaac is the first bad commit commit 7ea945f0bb49423451dbf222f62c6fabc857aaac Author: Myron Stowe myron.stowe@redhat.com Date: Thu Oct 30 11:54:43 2014 -0600
PCI: Shrink decoding-disabled window while sizing BARs
__pci_read_base() disables decoding while sizing device BARs. We can't print while decoding is disabled, which leads to some rather messy exit logic.
Coalesce the sizing logic to minimize the time decoding is disabled. This lets us print errors where they're detected.
The refactoring also takes advantage of the symmetry of obtaining the BAR's extent (pci_size) and storing the result as the 'region' for both the 32-bit and 64-bit BARs, consolidating both cases.
No functional change intended.
Signed-off-by: Myron Stowe myron.stowe@redhat.com Signed-off-by: Bjorn Helgaas bhelgaas@google.com CC: Matthew Wilcox willy@linux.intel.com
:040000 040000 6f2ac18e742572f4d3e4f8bd80c4d4b2e2dedafa 11c2f2defdb6330477e1b03e8dcc57438e406789 M drivers bisect run success
Dear Kevin Hilman,
On Mon, 17 Nov 2014 08:09:56 -0800, Kevin Hilman wrote:
FYI...
armada-370-mirabox started failing boot tests in linux-next as of next-20141117. Excerpt of boot report below, or you can see all the recent boots of mirabox here:
http://status.armcloud.us/boot/?mirabox
I bisected it down to a PCI commit[2], but it didn't revert cleanly on top of next/master so didn't fully verify it is the root cause. I'll let one of you MVEBU maintainers take it the next step.
Thanks a lot for the report, very useful. I haven't yet looked at the PCI commit itself, but reading the commit log indicates that it plays with sizing the BARs, and we're doing some fairly funky stuff with this in pci-mvebu, so I'm not entirely surprised such a commit can break stuff. I'll have a look tomorrow.
Thanks!
Thomas
kernel-build-reports@lists.linaro.org