co...@sdf.org writes:
> There appears to be a memory corruption bug that only happens on AMD
> CPUs running NetBSD (or OpenBSD). The same code doesn't fail on Intel.
> This affects Go and they've made some bug reports investigating it[1][2].
>
> People have narrowed it down to this simple Go repr
Hi all,
There appears to be a memory corruption bug that only happens on AMD
CPUs running NetBSD (or OpenBSD). The same code doesn't fail on Intel.
This affects Go and they've made some bug reports investigating it[1][2].
People have narrowed it down to this simple Go reproducer
(install lang/go1
On Wed, Nov 24, 2021 at 08:39:37AM +, Emmanuel Dreyfus wrote:
> I found three problems:
And I found some workarounds.
On resume, the machine is not crashed. It just has screen brightness
set to 0 and the keyboard is unresponsive.
I can recover the keyboard using:
drvctl -d uhidev0; drvctl -
