VESA is broked. Remove VESA from your config. Been this way for months.
It also will panic once in a VESA mode, such as my favorite and yours, 132x60, when
switching from vty to vty.
Peter Jeremy wrote:
> Having installed a new kernel and userland from sources about a day
> old, my vidcontrol command now causes a panic:
>
> Fatal trap 12: page fault while in vm86 mode
> fault virtual address = 0xc359b
> fault code = user read, page not present
> instruction pointer = 0xc000:0x359b
> stack pointer = 0x0:0xf82
> frame pointer = 0x0:0xfdc
> code segment = base 0x20000, limit 0x5004f, type 0x0
> = DPL 0, pres 0, def32 0, gran 0
> processor eflags = interrupt enabled, resume, vm86, IOPL = 0
> current process = 57775 (vidcontrol)
>
> The backtrace shows nothing useful - gdb doesn't seem to handle
> tracing through vm86 :-(.
>
> The command I used was "vidcontrol 132x60" after confirming that
> this was listed in "vidcontrol -i mode". I have previously been
> using VESA_132x60, but that also panics now.
>
> Any suggestions where to look?
>
> Peter
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
>
jim
--
ET has one helluva sense of humor!
He's always anal-probing right-wing schizos!
-----------------------------------------------------
POWER TO THE PEOPLE!
-----------------------------------------------------
"Religious fundamentalism is the biggest threat to
international security that exists today."
United Nations Secretary General B.B.Ghali, 1995
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
