From: jjhdiederen <jjhdiederen@zonnet.nl>
To: Romain Dolbeau <romain@dolbeau.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
PowerPC List Debian <debian-powerpc@lists.debian.org>,
linuxppc-dev@lists.ozlabs.org,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: Call for report - G5/PPC970 status
Date: Thu, 12 Dec 2019 08:32:07 +0100 [thread overview]
Message-ID: <716dc1da300bb8e9132b4ff44c02110f@zonnet.nl> (raw)
In-Reply-To: <CADuzgbq-P8mgf9zLaxhdqUfQcqfRpSzjgRoofF84rp+-S064xg@mail.gmail.com>
PowerMac 7,3 G5 2.5 DP PCI-X Mid-2004 is affected with this bug. The
machine freezes at boot due to the new ppc64 kernel.
Regards,
Jeroen Diederen
Romain Dolbeau schreef op 2019-12-11 08:19:
> Le mer. 11 déc. 2019 à 03:20, Aneesh Kumar K.V
> <aneesh.kumar@linux.ibm.com> a écrit :
>> The PowerMac system we have internally was not able to recreate this.
>
> To narrow down the issue - is that a PCI/PCI-X (7,3 [1]) or PCIe G5
> (11,2 [1]) ?
> Single, dual or quad ?
>
> Same question to anyone else with a G5 / PPC970 - what is it and does
> it boot recent PPC64 Linux kernel ?
>
> Christian from the original report has a quad, like me (so
> powermac11,2).
>
> There was also a report of a powermac7.3 working in the original
> discussion,
> single or dual unspecified.
>
> So this might be a Quad thing, or a more general 11,2 thing...
>
>> At this point, I am not sure what would cause the Machine check with
>> that patch series because we have not changed the VA bits in that
>> patch.
>
> Any test I could run that would help you tracking the bug ?
>
> Cordially,
>
> Romain
>
> [1]
> <https://en.wikipedia.org/wiki/Power_Mac_G5#Product_revision_history>
>
>
> --
> Romain Dolbeau
next prev parent reply other threads:[~2019-12-12 7:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADuzgbqYpv40NvAMGjo1cU2cNnij-2p4SYpWgM-Xn0v-8Qapsg@mail.gmail.com>
[not found] ` <e87e2397-a8d4-c928-d3d4-7ae700603770@physik.fu-berlin.de>
[not found] ` <CA+7wUsxBkmG-jW_UVBUuMriZbDkJko3kg0hzmMrVMoJLu2+rPw@mail.gmail.com>
2019-11-10 10:45 ` 5.3.7 64-bits kernel doesn't boot on G5 Quad Romain Dolbeau
2019-11-16 16:34 ` Found the commit for: " Romain Dolbeau
2019-11-16 16:41 ` John Paul Adrian Glaubitz
2019-12-10 8:35 ` Found the commit for: 5.3.7 64-bits kernel doesn't boot on G5 Quad [regression] Romain Dolbeau
2019-12-10 10:22 ` John Paul Adrian Glaubitz
2019-12-11 2:20 ` Aneesh Kumar K.V
2019-12-11 7:19 ` Call for report - G5/PPC970 status (was: Re: Found the commit for: 5.3.7 64-bits kernel doesn't boot on G5 Quad [regression]) Romain Dolbeau
2019-12-11 7:24 ` Call for report - G5/PPC970 status jjhdiederen
2019-12-12 7:32 ` jjhdiederen [this message]
2019-12-12 8:00 ` Romain Dolbeau
2019-12-12 8:07 ` John Paul Adrian Glaubitz
2019-12-12 18:12 ` Romain Dolbeau
2019-12-12 18:20 ` Andreas Schwab
2019-12-12 18:43 ` Romain Dolbeau
2019-12-12 21:40 ` Andreas Schwab
2019-12-13 7:47 ` PPC64: G5 & 4k/64k page size (was: Re: Call for report - G5/PPC970 status) Romain Dolbeau
2019-12-14 9:32 ` Jeroen Diederen
2020-01-05 15:06 ` Bertrand Dekoninck
2020-01-06 18:30 ` Romain Dolbeau
2020-01-07 15:27 ` PPC64: G5 & 4k/64k page size Bertrand
2020-01-07 15:54 ` Bertrand
2020-01-07 17:13 ` Romain Dolbeau
2020-01-07 17:51 ` Bertrand
2020-01-07 18:34 ` Patch for '5.3.7 64-bits kernel doesn't boot on G5 Quad' found (was: Re: PPC64: G5 & 4k/64k page size) Romain Dolbeau
2019-12-21 4:31 ` PPC64: G5 & 4k/64k page size (was: Re: Call for report - G5/PPC970 status) Aneesh Kumar K.V
2020-01-05 13:03 ` Romain Dolbeau
2020-01-06 14:06 ` Aneesh Kumar K.V
2020-01-06 18:18 ` Romain Dolbeau
2020-01-06 18:54 ` Lennart Sorensen
2020-01-06 19:11 ` Romain Dolbeau
2020-01-06 19:26 ` Lennart Sorensen
2020-01-07 9:40 ` Michel Dänzer
2020-01-07 0:39 ` Michael Ellerman
2024-08-06 20:56 ` John Paul Adrian Glaubitz
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=716dc1da300bb8e9132b4ff44c02110f@zonnet.nl \
--to=jjhdiederen@zonnet.nl \
--cc=aneesh.kumar@linux.ibm.com \
--cc=debian-powerpc@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=romain@dolbeau.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).