Re: kern/56087: dual-CPU macppc panic: pr_phinpage_check: [pmap_upvopl] ...

[Havard Eidnes <he%NetBSD.org@localhost>]

The following reply was made to PR kern/56087; it has been noted by GNATS.

From: Havard Eidnes <he%NetBSD.org@localhost>
To: rokuyama.rk%gmail.com@localhost
Cc: gnats-bugs%netbsd.org@localhost
Subject: Re: kern/56087: dual-CPU macppc panic: pr_phinpage_check:
 [pmap_upvopl] ...
Date: Thu, 01 Apr 2021 15:08:17 +0200 (CEST)

 > Probably same problem as reported by port-powerpc/55325:
 > 	http://gnats.netbsd.org/55325
 >
 > The patch attached to the PR may improve the situation, but
 > we need real fix for pmap for powepc/oea...
 
 First, thanks for the suggestion!
 
 Sadly, in my case it didn't.  I applied the patch quoted in the
 PR to -current, and built the GENERIC.MP kernel and tried booting
 it.  It seemed to have a negative influence on the interrupt
 system, and I didn't fully get the new kernel up; the console
 showed (transcribed from a photo of the screen):
 
 [   4.6999901] virq != 0, value 10
 [   4.6999901] virq != 0, value 10
 [   4.6999901] virq != 0, value 10
 [   4.6999901] virq != 0, value 10
 [   4.6999901] virq != 0, value 10
 [   4.7100758] virq != 0, value 10
 [   4.7100758] virq != 0, value 10
 [   4.7100758] virq != 0, value 10
 [   4.7100758] virq != 0, value 10
 [   4.7100758] virq != 0, value 10
 [   4.7200755] uhidev 0 at uhub2 port 1 configuration 1
 [   4.7200755] uhidev0: Mitsumi Electric (0x05ac) Apple Extended USB Keyboard
 [   4.7200755] virq != 0, value 10
 [   4.7200755] virq != 0, value 10
 [   4.7200755] virq != 0, value 10
 [   4.7200755] ukbd0 at uhiddev0
 [   4.7200755] virq != 0, value 1
 [   4.7200755] virq != 0, value 10
 [   4.7200755] virq != 0, value 1
 [   4.7200755] virq != 0, value 10
 
 etc. ending in
 
 [   5.0999900] virq != 0, value 10
 [   5.1299891] virq != 0, value 1
 [   5.1299891] wskbd0 at ukbd0: console keyboard using wsdisplay0
 [   5.1299891] uhidev1 at uhub2 port 1 configurat
 
 and that's it; it seems to be wedged there.
 
 Also, as far as I know there is no serial console possibility on
 this machine, so I can't capture the start of the boot messages,
 and the power button is the only possible next action.
 
 Aand... I just now heard the "gong" sound from my basement where
 this Mac is placed, indicating that this, perhaps unsurprisingly,
 is also a problem for single-CPU systems (I got the same
 backtrace as originally reported in this PR in my kernel message
 buffer).
 
 Regards,
 
 - Havard