Date: Sat, 3 Jan 2015 22:37:03 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Alfred Perlstein <bright@mu.org> Cc: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: odd behaviour with graphics, vt(4), VGA, and probing the text region leading to NMIs at boot Message-ID: <CAJ-VmonM4%2Bq%2B7neh3xtbiqAtEyhXSKVofjJz7pOJbtG4PHKDUg@mail.gmail.com> In-Reply-To: <2F715AD9-CF34-4516-B75E-E14C77BFD2E3@mu.org> References: <CAJ-Vmon2BZZbMRAJVAN=cngZmqu8XRQ8LzswqETsfwrLmfB53w@mail.gmail.com> <2F715AD9-CF34-4516-B75E-E14C77BFD2E3@mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3 January 2015 at 09:31, Alfred Perlstein <bright@mu.org> wrote: > Sounds like the virtualization code is sensitive to the mode. Meaning that whatever is virtualizing the graphics card doesn't do the proper thing when you're in a graphical mode. Can't the probes be turned off? So it's happening quite late in the boot process - when the ISA bus is being probed. So, maybe we can just avoid probing the dev/vga stuff like this. I'll have to talk to Ed/ray about how the syscons and vt devices hold together. I'm kinda shocked that we're re-probing things via an ISA probe so late in the boot process. > Basically when the "card" is in gfx mode, it doesn't do the right thing for those memory addresses. Sounds like the fix would be to not touch those regions unless you're actually in text mode. -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonM4%2Bq%2B7neh3xtbiqAtEyhXSKVofjJz7pOJbtG4PHKDUg>