Klemens Nanni <k...@openbsd.org> wrote: > Snapshots with 'disable inteldrm' to reduce corruption/hangs on a > Intel T14 gen 3 always print the following on shutdown/reboot: > > syncing disks... done > wsdisplay_switch2: not switching > rebooting... > > Unmodified bsd.mp does not show this. > > It is always a single "wsdisplay_switch2: not switching" line, i.e. never > "wsdisplay_switch1" or "wsdisplay_switch3" as wsdisplay also provides. > > I do not observe any other misbehaviour wrt. this, reboot/shutdown works. > > Is this a bug or expected behaviour when manually forcing efifb(4) in UKC? > The wsdisplay code returns EINVAL when logging this, so it reads like an > error case to me, but I don't know anything about wsdisplay.
x13s gives this also, so it has nothing to do with "disable inteldrm". It is suspend/resume wscons acting on non-drm framebuffers clearly. That said, noone is going to be interested in non-drm amd64 effects gained from using config -e. Relying on config -e to make things work is a great way to avoid hunting for the real problem. It's why I have occasionally argued for removing config -e, because of how often it is used as a crutch.
