vm86 problem in -CURRENT

2001-07-18 Thread Kazutaka YOKOTA
I am trying to track down a vm86 problem in -CURRENT. The trouble is that this is an intermittent problem and is not always reproducible. The last one I managed to capture was: == VESA: set_mode(): 24(18) - 259(103) VESA

Re: vm86 problem in -CURRENT

2001-07-18 Thread Jonathan Lemon
In article local.mail.freebsd-current/[EMAIL PROTECTED] you write: As far as I understand, the entire 1M bytes of lower physical memory is supposed to be mapped when vm86_intcall() is run. Apparently 0xc, where the video BIOS ROM resides, is mapped OK. But, somehow 0xa, where the