I have a TalosII with dual four-core Power9 and dual 16GB DDR4 ECC RAM.
Ubuntu installs ok but OpenBSD install is power cycling shortly after OPAL
says
"switching to big-endian OS."
A thread from September mentioned a compiled limit of 6GB of RAM. Is that
still the limit? If exceeded, what console
r VGA ports.
Anything useful I can capture by exiting Petitboot to the shell first, to
spot my mistake?
On Fri, Mar 5, 2021 at 4:15 PM Theo de Raadt wrote:
> please try a snapshot.
>
> we are running on much larger machines now.
>
> Eric Grosse wrote:
>
> > I have a Talos
George Koehler wrote:
> Which OpenBSD install image are you using? ...
I copied miniroot69.img from
cdn.openbsd.org/pub/OpenBSD/snapshots/powerpc64/
a few days ago onto a flash usb stick. Fdisk reports
*0 id=0c start=8192 size=32668 FAT32L
3 id=a6 start 40960 size=26624 OpenBSD
and mount /de
Eric wrote
> Raptor issued a 2.0 update last month
I misread at first; the v2.00 firmware is from February 2020.
Commenting on my fall 2018 system's firmware,
Theo wrote
> Pretty sure that is too old. ...
> raptor had to send me new eeproms...
I bought some blank flash parts from Digikey, got a B
Many thanks, as always, to the folks behind 7.5 upgrading smoothly on my
two TalosII power9 machines, one of which is the test build machine for the
Go team's openbsd-ppc64.
As a security move, I put PCI Intel network cards in my machines because
the (presumed vulnerable) BMC is accessible from th
On Sun, Apr 7, 2024, 11:43 Theo de Raadt wrote:
> > My usual workaround is to download the latest src tree, then sysupgrade,
> then
>
> I doubt your sysupgrade worked.
>
> It would explain why you had further trouble.
I'm sure you're right and it is my error. But FWIW, the sysupgrade reported
s
Thank you, understood.
(And apologies for the html. I'm struggling to get mobile Gmail to do
simple text.)
The openbsd-ppc64-n2vi Go builder machine is converting over to LUCI
build infrastructure and the new workload may have stepped on a
pagedaemon corner case. While running 7.5-stable I reproducibly get
kernel panics "pmap_enter: failed to allocate pted". I saw recent
powerpc64/pmap.c changes from gk
24 at 6:08 PM Jeremie Courreges-Anglas
wrote:
>
> On Tue, May 21, 2024 at 02:51:39AM +0200, Jeremie Courreges-Anglas wrote:
> > On Sat, May 18, 2024 at 01:11:56PM -0700, Eric Grosse wrote:
> > > The openbsd-ppc64-n2vi Go builder machine is converting over to LUCI
> >
openbsd-ppc64-n2vi got another crash:
UVM_PSEG_INUSE failed uvm_pager.c:227
panic
uvm_pseg_release
uvn_io
uvn_get
uvm_fault_lower
uvm_fault
trap
trapagain
type 300
during a bunch of go compiles.
On Mon, May 27, 2024 at 5:34 PM Jeremie Courreges-Anglas
wrote:
>
> On Sat, May 25, 2024 at
And, fairly quickly, another one. The load depends on what's in the Go
team build queue, which is not under my control.To avoid further
spamming the list I won't report any more of these until I can get
something reproducible under my control. Of course, anyone interested
may contact me directly if
George, thank you for the suggestion of changing membar_enter and
membar_consumer
from isync to sync. I did that and the frequency of crashes went way
down, admittedly on
a workload that is not solidly reproducible. But last night there was
finally another crash (see below)
so that's not the full s
Is the large (greater than 2^32) value of pr_nget below
exceptional? My crashes only happen for long-running
heavy workloads so a big value seems plausible but
maybe there is some limit I'm supposed to reconfigure
for such workloads?
panic: pmap_enter: failed to allocate pted
Stopped at panic
Disregard this speculation about a possible 32bit int issue. I've
reproduced the panic with a smaller pr_nget.
On Thu, Jun 6, 2024 at 11:37 PM Eric Grosse wrote:
>
> Is the large (greater than 2^32) value of pr_nget below
> exceptional? My crashes only happen for long-running
>
A bit of progress: in a kernel built with George Koehler's suggested
replacement of isync by sync and with uncommented GENERIC.MP
option MP_LOCKDEBUG
option WITNESS
and (getting rid of any dependence on Go) generating load
by running make -j64 build in /usr/src, I fairly quickly get a panic:
panic
15 matches
Mail list logo
