exiting Xorg locks up 9.2-STABLE system

[doug at safeport.com]

On Wed, 15 Oct 2014, William Bulley wrote:

> According to Warren Block <wblock at wonkity.com> on Wed, 10/15/14 at 11:08:
>>
>> If you are using a custom kernel, yes.  GENERIC now contains both sc and vt,
>> so vt must be selected by adding kern.vty=vt to /boot/loader.conf.
>
> It got worse...  :-(
>
> After commenting out a couple of the "options" found in vt(4) from
> my custom kernel config file, I was able to successfully run (as
> "root"):
>
>   unix# config MYKERNEL
>
> The next step was "make cleandepend" and that was fine.
>
> But running "make depend" caused this error:
>
> unix# make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES |  MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -O -pipe  -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs -fdiagnostics-show-option   -nostdinc  -I. -I../../.. -I../../../contrib/altq -I../../../contrib/ipfilter -I../../../contrib/pf -I../../../dev/ath -I../../../dev/ath/ath_hal -I../../../contrib/ngatm -I../../../dev/twa -I../../../gnu/fs/xfs/FreeBSD -I../../../gnu/fs/xfs/FreeBSD/support -I../../../gnu/fs/xfs -I../../../dev/cxgb -I../../../dev/cxgbe -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000  -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector
> In file included from ../../../dev/fb/fbd.c:51:
> ../../../dev/vt/vt.h:54:2: error: #error "Build with both syscons and vt is not supported. Please enable only one 'device sc' or 'device vt'"
> In file included from ../../../dev/vt/font/vt_font_default.c:36:
> ../../../dev/vt/vt.h:54:2: error: #error "Build with both syscons and vt is not supported. Please enable only one 'device sc' or 'device vt'"
> In file included from ../../../dev/vt/font/vt_mouse_cursor.c:33:
> ../../../dev/vt/vt.h:54:2: error: #error "Build with both syscons and vt is not supported. Please enable only one 'device sc' or 'device vt'"
> In file included from ../../../dev/vt/hw/fb/vt_fb.c:40:
> ../../../dev/vt/vt.h:54:2: error: #error "Build with both syscons and vt is not supported. Please enable only one 'device sc' or 'device vt'"
> In file included from ../../../dev/vt/vt_buf.c:43:
> ../../../dev/vt/vt.h:54:2: error: #error "Build with both syscons and vt is not supported. Please enable only one 'device sc' or 'device vt'"
> In file included from ../../../dev/vt/vt_consolectl.c:38:
> ../../../dev/vt/vt.h:54:2: error: #error "Build with both syscons and vt is not supported. Please enable only one 'device sc' or 'device vt'"
> In file included from ../../../dev/vt/vt_core.c:55:
> ../../../dev/vt/vt.h:54:2: error: #error "Build with both syscons and vt is not supported. Please enable only one 'device sc' or 'device vt'"
> In file included from ../../../dev/vt/vt_font.c:39:
> ../../../dev/vt/vt.h:54:2: error: #error "Build with both syscons and vt is not supported. Please enable only one 'device sc' or 'device vt'"
> In file included from ../../../dev/vt/vt_sysmouse.c:51:
> ../../../dev/vt/vt.h:54:2: error: #error "Build with both syscons and vt is not supported. Please enable only one 'device sc' or 'device vt'"
> mkdep: compile failed
> *** [.depend] Error code 1
>
> Which causes me to ask: how in the heck can the GENERIC kernel have both
> "devices" as you have stated?
>
> Regards,
>
> web...

In my experience this problem stems no support for switching the video back to 
text mode. I have had this issue on the Dell and HP laptops since 8.x. For me 
(on the HP) it remains on 10.0. From my reading and this list the issue (for 
me).

The last answer I got: "If you using Intel KMS it's a known problem that you 
can't switch to a virtual terminal once xorg is running - it hasn't been 
implemented yet AFAIK".

It seems as you had this working this may not be your issue, but apparently this 
is a complex issue and being not windows not much vendor help is forth coming. I 
chip this in because from my [suspect] memory this issue has come and gone as I 
upgrade FreeBSD/Xorg. YMMV.