> Date: Sun, 28 Jun 2020 13:38:37 +0200
> From: Klemens Nanni <k...@openbsd.org>
> 
> On Sun, Jun 28, 2020 at 12:59:10PM +0200, Mark Kettenis wrote:
> > Would be nice if we could give a hint about the firmware revisions
> > that are known to work.
> https://www.oracle.com/servers/technologies/firmware/release-history-jsp.html#T4-2
> 
> SysFW 8.9.11 from 10.01.2019 produces the following versions on my T4-2:
> 
>       hypervisor_version = Hypervisor 1.15.16 2018/11/28 07:41
>       obp_version = OpenBoot 4.38.16 2018/11/28 07:24
>       sysfw_version = Sun System Firmware 8.9.11 2018/11/28 07:59
> 
> I *assume* 8.9.x to work as well because that is what used to run on my
> machine prior to updating it, buts it's guess-work and none of the
> publicly available information puts actual dates next to the SysFW
> versions listed on above mentioned link, so I have no means to pick a
> version based on `-> show /HOST' output from Koakuma listing their known
> to be broken versions.
> 
> Here's a diff that explicitly mentions "SysFW 8.9.11" becuase that is
> all I can guarantee;  users with other firmware versions are encouraged
> to help bisect the breaking^Wfixing change.
> 
> OK?

yeah, I think that's the best we can do.

> Index: sparc64.html
> ===================================================================
> RCS file: /cvs/www/sparc64.html,v
> retrieving revision 1.403
> diff -u -p -r1.403 sparc64.html
> --- sparc64.html      19 May 2020 02:02:10 -0000      1.403
> +++ sparc64.html      28 Jun 2020 11:38:18 -0000
> @@ -230,6 +230,11 @@ and SPARC Enterprise T5120/T5220 may req
>  before OpenBSD can be successfully installed.  The SPARC Enterprise
>  T5120/T5220 needs at least OBP 4.28.0.
>  
> +On machines like the Oracle SPARC T4-2, older firmware versions from
> +around 2011 are known to cause kernel panics and crashes in
> +<a href="https://man.openbsd.org/sparc64/ldomd.8";>ldomd</a>;  later
> +versions, at least SysFW 8.9.11 from 2018, are known to work.
> +
>  <h4>Supported devices</h4>
>  
>  <ul>
> 

Reply via email to