From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Phil Turmel <philip@turmel.org>
Cc: Boqun Feng <boqun.feng@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Thomas Gleixner <tglx@linutronix.de>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: Bisected Regression 4.3.5 => 4.4.1 booting HP ZBook in EFI mode
Date: Fri, 5 Feb 2016 14:29:36 -0800 [thread overview]
Message-ID: <20160205222936.GA7139@kroah.com> (raw)
In-Reply-To: <56B518C4.8030007@turmel.org>
On Fri, Feb 05, 2016 at 04:48:52PM -0500, Phil Turmel wrote:
> Hello all,
>
> I tried to get off of v4.3.x today by moving to v4.4.1.
> My laptop failed to boot -- stuck with the BIOS boot logo still
> showing. I'm direct-booting a merged kernel & initramfs in
> EFI mode.
>
> I bisected to badc688 "powerpc: Make {cmp}xchg* and their atomic_ versions fully ordered"
> which is upstream commit 81d7a329.
>
> I'm stumped as to how that powerpc patch can affect my x86 laptop, an
> HP ZBook 17 w/ i7 processor & nouveau graphics, but it certainly
> does. The bisect was stable and I confirmed by reverting it on
> top of the intended v4.4.1.
That's crazy, nothing should even be rebuilt if you revert that patch,
so I don't see how that could affect things here.
Can you verify that nothing does get rebuilt when you do this?
thanks,
greg k-h
next prev parent reply other threads:[~2016-02-05 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 21:48 Bisected Regression 4.3.5 => 4.4.1 booting HP ZBook in EFI mode Phil Turmel
2016-02-05 22:29 ` Greg Kroah-Hartman [this message]
2016-02-05 23:41 ` Phil Turmel
2016-02-06 1:09 ` Greg Kroah-Hartman
2016-02-06 4:03 ` Phil Turmel
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=20160205222936.GA7139@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benh@kernel.crashing.org \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=philip@turmel.org \
--cc=tglx@linutronix.de \
/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).