linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Paul Mackerras <paulus@samba.org>,
	ppc-dev <linuxppc-dev@lists.ozlabs.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Kernel bug in 5.7 for PPC32 on PowerBook G4 - bisected to commit 697ece7
Date: Sat, 23 May 2020 19:30:20 +0200	[thread overview]
Message-ID: <3e3e2343-d674-02e0-7b23-81636b472641@csgroup.eu> (raw)
In-Reply-To: <2c361d8e-5e2a-cdd9-da8e-aa49a4f93cfd@lwfinger.net>

Hi Larry,

Le 23/05/2020 à 19:24, Larry Finger a écrit :
> Hi Christophe,
> 
> Although kernel 5.7.0-rc2 appeared to boot cleanly, it failed on my G4 
> when I tried to generate a new kernel. The following BUG message is logged:
> 

[...]

> 
> This problem was bisected to commit 697ece7 ("powerpc/32s: reorder Linux 
> PTE bits to better match Hash PTE bits").

Being reversed in new -rc , see 
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/87sgfsf4hs.fsf@mpe.ellerman.id.au/

> 
> If I had done more rigorous tests earlier, I would have found the bug 
> with more time to fix it before release of 5.7, but every other problem 
> I have found happened at boot, not when the machine had to swap.
> 
> Thanks,
> 
> Larry

Christophe

  reply	other threads:[~2020-05-23 17:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23 17:24 Kernel bug in 5.7 for PPC32 on PowerBook G4 - bisected to commit 697ece7 Larry Finger
2020-05-23 17:30 ` Christophe Leroy [this message]
2020-05-23 19:49   ` Larry Finger

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=3e3e2343-d674-02e0-7b23-81636b472641@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=Larry.Finger@lwfinger.net \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.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).