From owner-freebsd-current Mon Jan 24 4:39:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 201B014D52 for ; Mon, 24 Jan 2000 04:39:37 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup5-1.iptelecom.net.ua [212.9.227.1]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id OAA01992 for ; Mon, 24 Jan 2000 14:44:52 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id OAA20300 for ; Mon, 24 Jan 2000 14:38:45 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <388C47D4.50FD2100@altavista.net> Date: Mon, 24 Jan 2000 14:38:44 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: VESA modes broken in syscons driver Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, It seems that recent kernels have problems initialising syscons in VESA pixel modes. Particularly "vidcontrol VESA_800x600" (actually "vidcontrol VESA_800x600 < /dev/ttyv1" to see what's going on ttyv0) command make my kernel panicing with the following output: Fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xc01baee9 stack pointer = 0x10:0xc455fc78 frame pointer = 0x10:0xc455fc84 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 176 (vidcontrol) interrupt mask = tty trap number = 18 panic: integer divide fault Looking into nm /kernel output I figured that 0xc01baee9 pointer is within sc_mouse_move procedure, however I doesn't use moused. Moreover, disabling mouse support in syscons (SC_NO_SYSMOUSE) seems like a temporary workaround to this bug. -Maxim kernel config: device vga0 at isa? port ? conflicts device sc0 at isa? options VESA options SC_PIXEL_MODE options SC_TWOBUTTON_MOUSE options SC_HISTORY_SIZE=1024 dmesg: Preloaded elf kernel "kernel" at 0xc0302000. Preloaded elf module "splash_bmp.ko" at 0xc03020a8. Preloaded splash_image_data "/boot/chuck.bmp" at 0xc030214c. Intel Pentium detected, installing workaround for F00F bug VESA: information block 56 45 53 41 00 02 00 01 00 01 00 00 00 00 40 00 00 01 20 00 00 01 16 01 00 01 31 01 00 01 4a 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 20 mode(s) found VESA: v2.0, 2048k memory, flags:0x0, mode table:0xc0242f40 (1000040) VESA: CHIPS 6x554 Super VGA VESA: Chips & Technologies, Inc. 6x554 Display Controller 2 splash: image@0xc028b068, size:481078 bmp_start(): splash_mode:259 splash: image decoder found: splash_bmp vga-pci0: mem 0xfe000000-0xfeffffff at device 4.0 on pci0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 06 e0 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message