Hello all,
Great news: Aneesh sent me a patch that solves the problem on my G5 Quad :-)
I don't know whether he considers it a 'workaround' or if it's the
'proper' patch for upstream, so beware. It's a one-liner so I attach
it to this message: those affected can test it as well to confirm if
Le mer. 11 déc. 2019 à 03:20, Aneesh Kumar K.V
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
John Paul Adrian Glaubitz writes:
> Hi!
>
> On 12/10/19 9:35 AM, Romain Dolbeau wrote:
>> Le sam. 16 nov. 2019 à 17:34, Romain Dolbeau a écrit :
>>> So it seems to me that 0034d395f89d9c092bb15adbabdca5283e258b41
>>> introduced the bug that crashes the PowerMac G5
>>
>> There's been some
Hi!
On 12/10/19 9:35 AM, Romain Dolbeau wrote:
> Le sam. 16 nov. 2019 à 17:34, Romain Dolbeau 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
Hello,
Le sam. 16 nov. 2019 à 17:34, Romain Dolbeau 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
Hi Romain!
Great detective work!
On 11/16/19 5:34 PM, Romain Dolbeau wrote:
> So it seems to me that 0034d395f89d9c092bb15adbabdca5283e258b41
> introduced the bug that crashes the PowerMac G5 (as/could anyone
> tried/try on some other PPC970-based system, like a JS20 ? to see if
> it's
Le dim. 10 nov. 2019 à 11:45, Romain Dolbeau a écrit :
> Any suggestion, advice, or patch to try welcome :-)
>From my bisect, I figured that
0034d395f89d9c092bb15adbabdca5283e258b41 was the likely culprit, but
that the bug was masked by the printk() issues that were fixed later:
commit
Hello,
Following my bug report on debian-powerpc and the following, I'm
adding linuxppc-dev to my answer.
Le jeu. 7 nov. 2019 à 11:09, Mathieu Malaterre a écrit :
> On Thu, Nov 7, 2019 at 9:34 AM John Paul Adrian Glaubitz
> > The answer here would be git bisect [1]. I would first start
Salut Romain,
On Thu, Nov 7, 2019 at 9:34 AM John Paul Adrian Glaubitz
wrote:
>
> Hi Romain!
>
> On 11/7/19 9:18 AM, Romain Dolbeau wrote:
> > Any suggestion on how to identify/fix the bug ?
>
> The answer here would be git bisect [1]. I would first start downloading
> the current kernel source
Hi Romain!
On 11/7/19 9:18 AM, Romain Dolbeau wrote:
> Any suggestion on how to identify/fix the bug ?
The answer here would be git bisect [1]. I would first start downloading
the current kernel source tarball for 5.3.7 from upstream and build the
kernel with "make localmodconfig" to see whether
Hello,
The current linux-image package (5.3.7-1) in debian-ports won't boot
on my G5 Quad (dual 970MP).
I'm currently running the powerpc ports (32 bits userland), not ppc64,
but I assume it makes no difference for the 64 bits kernel.
I have the same error as previously reported for 5.2.7 in:
11 matches
Mail list logo