From: Michael Ellerman <mpe@ellerman.id.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Christian Zigotzky <chzigotzky@xenosoft.de>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: PASEMI: PA6T board doesn't boot with the RC1 of kernel 4.2 anymore
Date: Thu, 09 Jul 2015 11:42:15 +1000 [thread overview]
Message-ID: <1436406135.18682.3.camel@ellerman.id.au> (raw)
In-Reply-To: <1436394990.3948.113.camel@kernel.crashing.org>
On Thu, 2015-07-09 at 08:36 +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2015-07-08 at 20:00 +0200, Christian Zigotzky wrote:
> > Dear Linuxppc-dev mailing list,
> >
> > I used git bisect and found out that the following commit is the problem.
> >
> > commit 3ceaccdf92073d193f0bfbe24280dd736e3fed86
> > Author: Dave Hansen <dave.hansen@linux.intel.com>
>
> There is no way that commit affects anything on that platform, it only
> changes a file in arch/x86 that isn't compiled on a powerpc build. You
> must have made a mistake in your bisection, possibly the one "sometimes
> boots" should be considered good, but I can't say for sure.
>
> Michael has a PA6T board at work, so I assume he will see if he can
> reproduce.
Yeah I can't reproduce here.
I think you need to bisect again and look for the particular crash you
reported. If you see that crash then mark it bad, else mark it good.
cheers
next prev parent reply other threads:[~2015-07-09 1:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 4:27 [PATCH 00/10] Move MSI related PCI controller ops to pci_controller_ops Daniel Axtens
2015-04-14 4:27 ` [PATCH 01/10] powerpc: Add MSI operations to pci_controller_ops struct Daniel Axtens
2015-04-14 4:27 ` [PATCH 02/10] powerpc/powernv: Move MSI-related ops to pci_controller_ops Daniel Axtens
2015-04-14 4:27 ` [PATCH 03/10] powerpc/cell: " Daniel Axtens
2015-04-14 4:27 ` [PATCH 04/10] powerpc/pseries: " Daniel Axtens
2015-04-14 4:27 ` [PATCH 05/10] powerpc/fsl_msi: " Daniel Axtens
2015-04-14 4:27 ` [PATCH 06/10] powerpc/ppc4xx_msi: " Daniel Axtens
2015-04-14 4:28 ` [PATCH 07/10] powerpc/ppc4xx_hsta_msi: " Daniel Axtens
2015-04-14 4:28 ` [PATCH 08/10] powerpc/mpic_pasemi_msi: " Daniel Axtens
2015-07-07 10:50 ` PASEMI: PA6T board doesn't boot with the RC1 of kernel 4.2 anymore Christian Zigotzky
2015-07-07 11:25 ` Christian Zigotzky
2015-07-07 12:44 ` Christian Zigotzky
2015-07-08 18:00 ` Christian Zigotzky
2015-07-08 22:36 ` Benjamin Herrenschmidt
2015-07-09 1:42 ` Michael Ellerman [this message]
2015-07-09 5:19 ` Christian Zigotzky
2015-07-09 7:07 ` Michael Ellerman
2015-07-09 7:53 ` Benjamin Herrenschmidt
2015-07-09 8:50 ` Christian Zigotzky
2015-07-09 9:12 ` Christian Zigotzky
2015-07-09 9:52 ` Denis Kirjanov
2015-07-09 10:37 ` Christian Zigotzky
2015-07-13 6:47 ` Benjamin Herrenschmidt
2015-07-13 9:33 ` Denis Kirjanov
2015-07-09 22:27 ` Christian Zigotzky
2015-07-10 6:51 ` Christian Zigotzky
2015-07-13 6:44 ` Benjamin Herrenschmidt
2015-04-14 4:28 ` [PATCH 09/10] powerpc/mpic_u3msi: Move MSI-related ops to pci_controller_ops Daniel Axtens
2015-04-14 4:28 ` [PATCH 10/10] powerpc: Remove MSI-related PCI controller ops from ppc_md Daniel Axtens
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=1436406135.18682.3.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=chzigotzky@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).