4.8.0-rc1: Invalid memory access at $SRR0: 0140f86c $SRR1: 00003030
mpe at ellerman.id.au
Wed Aug 10 17:02:03 AEST 2016
Christian Kujau <lists at nerdbynature.de> writes:
> On Wed, 10 Aug 2016, Michael Ellerman wrote:
>> Benjamin Herrenschmidt <benh at kernel.crashing.org> writes:
>> > On Tue, 2016-08-09 at 02:06 -0700, Christian Kujau wrote:
>> >> On Mon, 8 Aug 2016, Christian Kujau wrote:
>> >> >
>> >> > while trying to upgrade this PowerBook G4 from 4.7-rc7 to 4.8-rc1,
>> >> > it's
>> >> > unable to boot the Yaboot (v1.3.16 from Debian/stable) boot loader:
>> > There should already be a fix for that:
>> > http://patchwork.ozlabs.org/patch/654560/
>> > It should be in Michael's tree if not already in Linus.
>> That fix is in rc1, so this must be a different bug.
> Does the git bisect help?
No it doesn't sorry.
Because as soon as you bisected prior to that fix, you would have been
hitting the bug fixed by that commit.
To make the bisect work you need to try and apply the above fix at every
stage with patch. If the point you're bisecting already has the fix then
obviously you don't need to apply it again. You then build the kernel,
test it, and unapply the patch before doing git bisect good/bad.
$ git bisect start
$ git bisect good xxx
$ git bisect bad yyy
<checks out some version>
$ git show 2c0f99516f53 | patch -p1
... test kernel ....
$ git reset --hard
$ git bisect good/bad
More information about the Linuxppc-dev