Thanks ...
Oracle Advanced Lights Out Manager CMT v1.7.9
Sun-Fire-T2000 System Firmware 6.7.10 2010/07/14 16:35
Host flash versions:
OBP 4.30.4.b 2010/07/09 13:48
Hypervisor 1.7.3.c 2010/07/09 15:14
POST 4.30.4.b 2010/07/09 14:24
AFAIK, this is the latest available publicly.
I had to recreate the factory default each time.
Now I have the system running, I am quite reluctant to go back and mess it
up.
If you look in my zip, you will see two config directories. These were each
built with a fresh factory-default and the exact same ldom.conf (its there
for
you to check if I messed up!)
The process is:
1) do a factory reset
2) download the one you wish to test
3) attempt to boot.
The bsd63 one will boot and run fine.
The oct2021 version will give :
----%<----------------------
{0} ok boot
SC Alert: Host System has Reset
ERROR: /pci@780: Invalid hypervisor argument(s). function: b4
ERROR: /pci@780: Invalid hypervisor argument(s). function: b4
ERROR: /pci@780: Invalid hypervisor argument(s). function: b5
Sun Fire(TM) T1000, No Keyboard
Copyright (c) 1998, 2011, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.30.4.d, 2048 MB memory available, Serial #77558134.
Ethernet address 0:14:4f:9f:71:76, Host ID: 849f7176.
Boot device: net File and args:
ERROR: boot-read fail
Evaluating:
Can't locate boot device
----%<----------------------
After this, my device tree is empty.
Resetting to factory-default recovers the device tree, and the system will
boot.
(Note this is from the T1000, but the T2000 results were the same apart
from some differences in
ID numbers and white space AFAICR).
I can continue to test on the T1000, but I am preparing the T2000 for
active duty, and would rather not
disturb it now it boots. (I have two, and bounce them each time I upgrade
to a new version of OBSD -
have been doing this with different Sparc64 hardware since about OBSD
5.1). (Postgresql WAL
logging to V100's).
regards
Andrew
On Wed, 27 Oct 2021 at 15:31, Klemens Nanni <[email protected]> wrote:
> (moving Cc to bugs@)
>
> On Wed, Oct 27, 2021 at 02:33:55PM +0100, Andrew Grillet wrote:
> > I reported this problem in 2019, and was asked to provide data for
> > diagnosis.
> > Unfortunately, I was not able to do so at the time.
>
> Thanks for coming back to this.
>
> Please provide boot logs, specifically what the hypervisor says.
> Which firmware version is installed?
>
> > I can now confirm that the problem - incorrect mapping of the PCI -
> occurs
> > with both
> > T1000 and T2000s, and probably also with T5x20s.
>
> T5xx0 boxes seem fairly common, I've been using T5220 and T5240 ones
> myself without problems since around 6.6 (and latest firmware).
>
> > The problem causes the machine to become unbootable, until restored to
> > factory-default.
>
> What is the error message?
>
> > Compiling the exact same ldom.conf with 6.3 works OK, and with 6.9 still
> > produces
> > the same problem.
>
> Did you copy over the factory-default dump or did you start with the
> existing bsd63 one?
>
> Please provide exact steps to reproduce.
>
> ldomctl(8) is still rough around the edges -- the entire dance is easy
> to mess up with dump/copy/edit/init-system/delete/download and not all
> configs are guaranteed to be accepted by the hypervisor.
>
> > A config generated with 6.3 will run 6.9 correctly.
>
> That is expected. Once the hypervisor has a valid configuration, it
> doesn't matter which OpenBSD version you are running in your domains.
>
> > I have attached the test code (in tar format).
>
> That could provide helpful details but I am reluctant to dig through
> them with `mdprint' (from packages) without the bits requested above.
>
