linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Romain Dolbeau <romain@dolbeau.org>,
	linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au
Cc: PowerPC List Debian <debian-powerpc@lists.debian.org>
Subject: Re: Found the commit for: 5.3.7 64-bits kernel doesn't boot on G5 Quad [regression]
Date: Wed, 11 Dec 2019 07:50:31 +0530	[thread overview]
Message-ID: <87eexbk3gw.fsf@linux.ibm.com> (raw)
In-Reply-To: <b2256437-efe1-909d-1488-174b6522f9e0@physik.fu-berlin.de>

John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> writes:

> Hi!
>
> On 12/10/19 9:35 AM, Romain Dolbeau wrote:
>> Le sam. 16 nov. 2019 à 17:34, Romain Dolbeau <romain@dolbeau.org> a écrit :
>>> So it seems to me that 0034d395f89d9c092bb15adbabdca5283e258b41
>>> introduced the bug that crashes the PowerMac G5
>> 
>> There's been some commits in that subsystem, so I tried again; as of
>> 6794862a16ef41f753abd75c03a152836e4c8028, the kernel still crashes
>> when trying to boot my PowerMac G5.
>
> If Aneesh is currently unable to look at the problem, I would suggest reverting
> the commit in question since I don't think it's acceptable that users are unable
> to boot their machines anymore after a kernel upgrade.
>

The PowerMac system we have internally was not able to recreate this.
Hence we have not been able to make progress on this.

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.

-aneesh

  reply	other threads:[~2019-12-11  2:23 UTC|newest]

Thread overview: 33+ 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 [this message]
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
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

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=87eexbk3gw.fsf@linux.ibm.com \
    --to=aneesh.kumar@linux.ibm.com \
    --cc=debian-powerpc@lists.debian.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --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).