| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1330725132.11728.52.camel@pasglop> Date: Sat, 03 Mar 2012 08:52:12 +1100 From: Benjamin Herrenschmidt <benh@...nel.crashing.org> To: Bjorn Helgaas <bhelgaas@...gle.com> Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Jesse Barnes <jbarnes@...tuousgeek.org>, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org, ppc-dev <linuxppc-dev@...ts.ozlabs.org> Subject: Re: linux-next: boot failure for next-20120227 and later (pci tree related) On Fri, 2012-03-02 at 10:10 -0700, Bjorn Helgaas wrote: > On Thu, Mar 1, 2012 at 11:06 PM, Stephen Rothwell <sfr@...b.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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists