include em in release builds?

--000000000000d739930615860300
Content-Type: text/plain; charset="UTF-8"

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 the motherboard network
ports. Dmesg for the Go builder machine was sent as usual to
[email protected] and posted at https://n2vi.com/t.dmesg. As you can see
there, the powerpc64 release build does not include the em driver.

My usual workaround is to download the latest src tree, then sysupgrade,
then recompile the kernel including em. This time the rebuilt kernel failed
with lots of Bad system call (core dumped) messages. So I moved my network
cable back to the motherboard for the time being. It is not a bad thing for
the official Go builder to be running an official release anyway. But it
would be nice to have em.

I'd welcome advice on what I should be doing better. Maybe get a Broadcom
PCI card?

--000000000000d739930615860300
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">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&#39;s openbsd-ppc64.<div dir=3D"auto"><br></div><d=
iv dir=3D"auto">As a security move, I put PCI Intel network cards in my mac=
hines because the (presumed vulnerable) BMC is accessible from the motherbo=
ard network ports. Dmesg for the Go builder machine was sent as usual to <a=
 href=3D"mailto:[email protected]">[email protected]</a> and posted at <a h=
ref=3D"https://n2vi.com/t.dmesg">https://n2vi.com/t.dmesg</a>. As you can s=
ee there, the powerpc64 release build does not include the em driver.</div>=
<div dir=3D"auto"><br></div><div dir=3D"auto">My usual workaround is to dow=
nload the latest src tree, then sysupgrade, then recompile the kernel inclu=
ding em. This time the rebuilt kernel failed with lots of Bad system call (=
core dumped) messages. So I moved my network cable back to the motherboard =
for the time being. It is not a bad thing for the official Go builder to be=
 running an official release anyway. But it would be nice to have em.</div>=
<div dir=3D"auto"><div dir=3D"auto"><div dir=3D"auto"><br></div><div dir=3D=
"auto">I&#39;d welcome advice on what I should be doing better. Maybe get a=
 Broadcom PCI card?</div><div dir=3D"auto"><br></div></div></div></div>

--000000000000d739930615860300--