Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 26 Jan 2020 21:25:01 -0500
From:      Dennis Clarke <dclarke@blastwave.org>
To:        freebsd-current@freebsd.org
Subject:   Re: r356776 breaks kernel for powerpc64 users
Message-ID:  <6f8b8c41-b712-ccb0-1655-0a2e1cfc8bf7@blastwave.org>
In-Reply-To: <2EEA029D-2C24-42F2-A347-69813B928BC4@yahoo.com>
References:  <2EEA029D-2C24-42F2-A347-69813B928BC4.ref@yahoo.com> <2EEA029D-2C24-42F2-A347-69813B928BC4@yahoo.com>

index | next in thread | previous in thread | raw e-mail

On 2020-01-26 19:27, Mark Millard wrote:
> Piotr Kubaj listy at anongoth.pl wrote on
> Thu Jan 16 19:56:11 UTC 2020 :
> 
>> revision 356776 breaks booting for powerpc64 users. It reportedly works fine on POWER8, but I get kernel panic on POWER9 (Talos II) right after the usual warning: WITNESS enabled. Kernel panic is uploaded to https://pastebin.com/s8ZaUNS2.
>>
>>
>> @jeff
>> Since you commited this patch, can you fix this issue or revert this commit?
>>
> 
> Is this still a problem for powerpc64? I've not seen
> anything looking like a direct response or like a
> status update for this.
> 
> I do see arm report(s) of problems that they also
> attributed to head -r356776 . But I've no clue how
> good the evidence is generally. An example message
> is:
> 
> https://lists.freebsd.org/pipermail/freebsd-arm/2020-January/021069.html
> 
> But one part of that is for specifically for going
> from -r356767 to the next check-in to head: -r356776 .
> That problem likely has good evidence for the
> attribution to -r356776 .
> 

I will give current a try and report back. However I am hesitant to do 
so as I have a working G5 right now.

For science ... I will do the experiment.


-- 
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional


help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6f8b8c41-b712-ccb0-1655-0a2e1cfc8bf7>