Re: physmem is 0 on this G5 macppc

2018-07-04 Thread Peter J. Philipp
Hi, Can you let us know if the PowerMac11,2 has 4 DIMM slots or more?  If it is 4, then that means a DIMM can be 4 GB in size, which means my second update patch may fail and a 16 GB memory PowerMac may get the same 0 MB that my PowerMac7,3 is getting. The fix isn't trivial for that though

Re: physmem is 0 on this G5 macppc

2018-07-04 Thread Bryan Vyhmeister
On Thu, Jul 05, 2018 at 01:12:32AM +0200, Peter J. Philipp wrote: > According to wikipedia only the PowerMac11,2 supports up to 16 GB the rest > are all maximum 4GB, and I don't think the PowerMac11,2 is supported. > > https://en.wikipedia.org/wiki/Power_Mac_G5 I'm not sure what the correct fix

Re: physmem is 0 on this G5 macppc

2018-07-04 Thread Peter J. Philipp
On Wed, Jul 04, 2018 at 08:19:25PM +0200, Peter J. Philipp wrote: > Hi again, > > I came up with a fix, but not sure if it's correct. The problem is that the > physical memory here is 32 bits (paddr_t defined in > arch/powerpc/include/_types.h). > So when we have 4 banks of 1 GB we end up with

Re: physmem is 0 on this G5 macppc

2018-07-04 Thread Peter J. Philipp
Hi again, I came up with a fix, but not sure if it's correct. The problem is that the physical memory here is 32 bits (paddr_t defined in arch/powerpc/include/_types.h). So when we have 4 banks of 1 GB we end up with 2^32 which wraps around to 0 on the paddr_t so we report as 0MB. My

Re: panic witness_warn

2018-07-04 Thread Kenneth R Westerback
On Wed, Jul 04, 2018 at 05:48:21PM +0200, Alexander Bluhm wrote: > On Mon, Jun 04, 2018 at 08:53:49PM +0200, Alexander Bluhm wrote: > > userret: returning with the following locks held: > > exclusive rrwlock inode r = 0 (0xff023d492b48) locked @ > > /usr/src/sys/ufs/uf > > s/ufs_vnops.c:1559

Re: panic witness_warn

2018-07-04 Thread Alexander Bluhm
On Mon, Jun 04, 2018 at 08:53:49PM +0200, Alexander Bluhm wrote: > userret: returning with the following locks held: > exclusive rrwlock inode r = 0 (0xff023d492b48) locked @ > /usr/src/sys/ufs/uf > s/ufs_vnops.c:1559 > #0 witness_lock+0x254 > #1 _rw_enter+0x29b > #2 _rrw_enter+0x3e > #3

physmem is 0 on this G5 macppc

2018-07-04 Thread pjp
>Synopsis: physmem is reported as 0 on this G5 macppc >Category: kernel >Environment: System : OpenBSD 6.3 Details : OpenBSD 6.3-current (GENERIC.MP) #106: Tue Jul 3 18:16:21 MDT 2018

Re: certbot problem on sparc64 (probably python)

2018-07-04 Thread Stuart Henderson
On 2018/07/03 19:29, and...@grillet.co.uk wrote: > >Synopsis:Unable to use certbot > >Category:very annoying > >Environment: > System : OpenBSD 6.3 > Details : OpenBSD 6.3 (GENERIC.MP) #486: Sat Mar 24 22:37:16 MDT > 2018 > >

Re: certbot problem on sparc64 (probably python)

2018-07-04 Thread Daniel Jakots
On Tue, 3 Jul 2018 19:29:07 +0100 (BST), and...@grillet.co.uk wrote: > From the log, it looks like bits are missing from the python > install, but I don't know python, and I could be wrong. Can you share the log (so we don't have to guess) please? Cheers, Daniel

2012 Mac Mini shows ~45% intr in CPU thread 0

2018-07-04 Thread pjp
>Synopsis: 2012 Mac Mini shows ~50% intr in CPU thread 0 >Category: system >Environment: System : OpenBSD 6.3 Details : OpenBSD 6.3-current (GENERIC.MP) #83: Mon Jul 2 10:36:36 MDT 2018

certbot problem on sparc64 (probably python)

2018-07-04 Thread andrew
>Synopsis: Unable to use certbot >Category: very annoying >Environment: System : OpenBSD 6.3 Details : OpenBSD 6.3 (GENERIC.MP) #486: Sat Mar 24 22:37:16 MDT 2018 dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC.MP