From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: Bjorn Helgaas <bhelgaas@google•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Jesse Barnes <jbarnes@virtuousgeek•org>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
ppc-dev <linuxppc-dev@lists•ozlabs.org>
Subject: Re: linux-next: boot failure for next-20120227 and later (pci tree related)
Date: Sat, 03 Mar 2012 08:52:12 +1100 [thread overview]
Message-ID: <1330725132.11728.52.camel@pasglop> (raw)
In-Reply-To: <CAErSpo6xQa4Rnv+RkkXCRjQ2HDZdBhorRv2c6pmWyXqRzhM4Vw@mail.gmail.com>
On Fri, 2012-03-02 at 10:10 -0700, Bjorn Helgaas wrote:
> On Thu, Mar 1, 2012 at 11:06 PM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> > Hi Jesse,
> >
> > Staring with next-20120227, one of my boot tests is failing like this:
>
> Hi Stephen,
>
> Thanks a lot for the test report and the bisection. I wish I had a
> machine to test on so I wouldn't have to bother you about it.
>
> Any chance you could point me at the complete before/after dmesg logs?
> There should be information about the PCI host bridge apertures and
> offsets in the "after" log. If that's not enough, we might need to
> collect new before/after logs with something like this
> (whitespace-mangled):
Or give me a chance to dig :-) I'll have a look next week.
Cheers,
Ben.
next prev parent reply other threads:[~2012-03-02 21:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 6:06 linux-next: boot failure for next-20120227 and later (pci tree related) Stephen Rothwell
2012-03-02 17:10 ` Bjorn Helgaas
2012-03-02 21:52 ` Benjamin Herrenschmidt [this message]
2012-03-05 3:34 ` Benjamin Herrenschmidt
2012-03-05 16:14 ` Bjorn Helgaas
2012-03-02 22:26 ` Stephen Rothwell
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=1330725132.11728.52.camel@pasglop \
--to=benh@kernel$(echo .)crashing.org \
--cc=bhelgaas@google$(echo .)com \
--cc=jbarnes@virtuousgeek$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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