How artifcact.ci.freebsd.org's head/r356187/powerpc/powerpc/ fails to boot a PowerMac G5: lock "tfo_ccache_bucket" ... already initialized

[Mark Millard]

On 2020-Jan-1, at 18:08, Mark Millard <marklmi at yahoo.com> wrote:

> Using materials from:
> 
> https://artifact.ci.freebsd.org/snapshot/head/r356187/powerpc/powerpc/
> 
> put on an SSD, I tried booting a PowerMac G5
> with the 32-bit system (historically supported).
> Below is typed in from a screen image that
> shows a panic.
> 
> 
> . . .
> Timecounters tick every 1.000 msec
> firewire0: w nodes, maxhop <= 1 cable IRM irm(1) (me)
> firewire0: bus manager 1
> bge0: link state changes to UP
> [zone: mbuf_cluster] kern.ipc.nmbclusters limit reached
> panic: lock "tfo_ccache_bucket" 0xd2858008 already initialized
> cpuid = 0
> time = 1
> KDB: stack backtrace
> 0xd00048b0: at kdb_backtrace+0x64
> 0xd0004910: at vpanic+0x200
> 0xd0004980: at panic+0x64
> 0xd00049c0: at lock_init+0x200
> 0xd00049d0: at _mtx_init+0x7c
> 0xd00049f0: at tcp_fastopen_init+0x1e8
> 0xd0004a20: at tcp_init+0x234
> 0xd0004a50: at protosv_init+0x1d4
> 0xd0004a60: at vnet_domain_init+0x5c
> 0xd0004a80: at vnet_register_sysinit+0x154
> 0xd0004ab0: at mi_startup+0x280
> 0xd0004af0: at btext+0x74
> KDB: enter: panic
> [ thread pid 0 tid 100000 ]
> Stopped at kdb_enter+0x74: addi r3,r0,0x0
> db> 
> 
> (No ability to input to that prompt.)
> 

I've now tested both type of PowerMac G5
that I (sometimes) have access to:

G5 with 2 sockets, 2 cores each
G5 with 2 sockets, 1 core each

If fails the same way in both.

I do not have access to any 1 socket G5
PowerMacs, no matter how many cores.


Note: I make no claim that r356187 is
special for this. I've no clue what
range of versions show the problem,
other than it spans r356187. I used
r356187 because I'm updating various
machines to be at that version
(non-debug), not just PowerMacs.

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)