From: Finn Thain <fthain@telegraphics.com.au>
To: Christophe Leroy <christophe.leroy@c-s.fr>
Cc: linuxppc-dev@lists.ozlabs.org, Stan <userm57@yahoo.com>
Subject: Re: Bisected regression in v5.1 on PowerBook G3 (Wallstreet)
Date: Thu, 27 Jun 2019 10:25:19 +1000 (AEST) [thread overview]
Message-ID: <alpine.LNX.2.21.1906271019060.21@nippy.intranet> (raw)
In-Reply-To: <03df9f3c-003a-b4ae-6f76-ba8a20742b25@c-s.fr>
On Wed, 26 Jun 2019, Christophe Leroy wrote:
> Hi Finn,
>
> On 06/26/2019 02:06 AM, Finn Thain wrote:
> > Hi Christophe,
> >
> > I received a report of a regression between v5.0 and v5.1 which causes
> > the current release to crash during boot with a machine check
> > exception. Please see console log below.
> >
> > Stan (whom I've Cc'd) tells me that this happens on every attempt to
> > boot. I asked him to try 'git bisect'. The results are given below.
> > Can you see anything in commit 93c4a162b014 that might explain this?
>
> Might be a false positive. That commit has a problem, but that problem
> is fixed by 4622a2d43101 ("powerpc/6xx: fix setup and use of
> SPRN_SPRG_PGDIR for hash32")
>
> I would bet your problem is related to commit f7354ccac844 ("powerpc/32:
> Remove CURRENT_THREAD_INFO and rename TI_CPU"). That problem is fixed by
> commit 397d2300b08c ("powerpc/32s: fix flush_hash_pages() on SMP")
> upstream, and in linux 5.1.4 by commit fda49aec2515 on
> stable/linux-5.1.y
>
I see. I've just discovered that this issue has already been covered on
this list. I should have done a bit more research.
> Can you test ?
>
Stan did some more tests and confirmed that the problem has been fixed in
397d2300b08c and stable/linux-5.1.y.
Thanks.
--
> Thanks
> Christophe
>
prev parent reply other threads:[~2019-06-27 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 2:06 Bisected regression in v5.1 on PowerBook G3 (Wallstreet) Finn Thain
2019-06-26 5:49 ` Christophe Leroy
2019-06-27 0:25 ` Finn Thain [this message]
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=alpine.LNX.2.21.1906271019060.21@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=christophe.leroy@c-s.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=userm57@yahoo.com \
/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).