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 an
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 commit
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 ker
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 PowerMac-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 2ac5a3bf70
