https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254381
Jung-uk Kim <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Affects Only Me |Affects Some People CC| |[email protected] --- Comment #11 from Jung-uk Kim <[email protected]> --- I have a similar problem. My guess is the frame buffer does not set memory attribute properly. Note we do not have this problem as soon as kernel is loaded because we unconditionally set it as write-combining: https://cgit.freebsd.org/src/commit/sys/dev/vt/hw/efifb/efifb.c?id=7ef5e8bc80065821d8f277a41f8184e7990d27bc Later, we added "hw.efifb.cache_attr" tunable to allow uncacheable type. https://cgit.freebsd.org/src/commit/sys/dev/vt/hw/efifb/efifb.c?id=8dff0b6761407357c5bb42ee799c5c9f465557a3 We may be able to set it from loader via SetVirtualAddressMap(), I guess? -- You are receiving this mail because: You are the assignee for the bug.
