From owner-freebsd-current@FreeBSD.ORG Mon Feb 17 16:41:39 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EAF36FE5 for ; Mon, 17 Feb 2014 16:41:38 +0000 (UTC) Received: from mail-lb0-f180.google.com (mail-lb0-f180.google.com [209.85.217.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6CCCD15F1 for ; Mon, 17 Feb 2014 16:41:38 +0000 (UTC) Received: by mail-lb0-f180.google.com with SMTP id n15so11290280lbi.39 for ; Mon, 17 Feb 2014 08:41:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type:subject:from:date:to:cc :message-id; bh=nlNlwVltYMWtBYaX4JCo0SZ98Q6R3bDoAQHDA5vZgy0=; b=GO8Pzf5IDQpXtE7jvL3Pvt+uTUtnwKCzievoeMKdBt2i4zwQR/CMLRECtVSnNZIpKO 6yKNIWHisWuTbgSIhIMG5+UElNxHohEsc9qnsjQGSw0XkrqI34uTThmvOWXAltA1ovc7 jqh+FHeTBIB8NOqQ3srIxgCUceR+Ccl7aXml63WNNAScRhqYwvby3jmr3hzPynvYQjKO m/qMlr5vbJnlwd9ug48gJHvzFyCNlL+8UnXKE0OaGKeUs76JBcXoFmlb9miPohZE+6CM BbPqn61i1UZlGFjk8FoEdjcgp8Ks8K6AwvSHe92SGTtV4fepgGGgfmCUM3pBW7AFeMqB QENA== X-Gm-Message-State: ALoCoQmoAYOGuxvNxRZHte8SobATNYSTANsQXEnc+klO7Hfaz6IZkJQ1gCyOpChrUHIO77qzasHF X-Received: by 10.112.164.5 with SMTP id ym5mr2220178lbb.48.1392655290106; Mon, 17 Feb 2014 08:41:30 -0800 (PST) Received: from [88.154.170.47] ([88.154.170.47]) by mx.google.com with ESMTPSA id g8sm26610987lae.1.2014.02.17.08.41.25 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 17 Feb 2014 08:41:28 -0800 (PST) User-Agent: K-9 Mail for Android In-Reply-To: <5301DF89.5030707@FreeBSD.org> References: <5301DF89.5030707@FreeBSD.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: vt(9): couple of small issues From: Aleksandr Rybalko Date: Mon, 17 Feb 2014 18:41:13 +0200 To: Andriy Gapon , FreeBSD Current , Aleksandr Rybalko Message-ID: <78196899-7922-4fd0-937c-7b4a69714dbc@email.android.com> Cc: freebsd-x11@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Feb 2014 16:41:39 -0000 On 17 лютого 2014 р. 12:08:09 GMT+02:00, Andriy Gapon wrote: > >I used to have mousechar_start="3" in my r.conf. To be honest I can >not even >recall why. But this worked fine with syscons without any glitches. >With vt I get the following during boot up: >vidcontrol: setting mouse character: Inappropriate ioctl for device >And mouse cursor is never drawn, apparently vidcontrol -m on -M >just fails. > >Looks like with syscons MOUSE_MOUSECHAR ioctl is handled by a terminal >device >and consolectl device while with vt it is handled only by sysmouse >device. > > >Another issue is that I see the following messages appearing during >boot and >from time to time afterwards in the system log: >kernel: sysmouse: unknown ioctl: t:40007413 >kernel: sysmouse: unknown ioctl: t:80007410 > >The ioctls seem to be TIOCFLUSH and TIOCGETA, so I am not sure why >sysmouse gets >involved. Maybe the same issue exists with syscons's sysmouse as well, >but it >is just silent about it. > >Seems like ioctls are called by X server. For example: >sysmouse_ioctl:entry > kernel`devfs_ioctl_f+0x11c > kernel`kern_ioctl+0x1db > kernel`sys_ioctl+0x142 > kernel`amd64_syscall+0x3c9 > kernel`0xffffffff8080e6db > > libc.so.7`ioctl+0xa > Xorg`xf86OpenSerial+0x221 > mouse_drv.so`MouseProc+0x2f3 > Xorg`EnableDevice+0x214 > Xorg`xf86Wakeup+0x57b > Xorg`WakeupHandler+0x42 > Xorg`WaitForSomething+0x317 > Xorg`Dispatch+0x92 > Xorg`main+0x475 > Xorg`_start+0x14f > >sysmouse_ioctl:entry > kernel`devfs_ioctl_f+0x11c > kernel`kern_ioctl+0x1db > kernel`sys_ioctl+0x142 > kernel`amd64_syscall+0x3c9 > kernel`0xffffffff8080e6db > > libc.so.7`ioctl+0xa > Xorg`xf86FlushInput+0x21 > mouse_drv.so`MouseProc+0x376 > Xorg`EnableDevice+0x214 > Xorg`xf86Wakeup+0x57b > Xorg`WakeupHandler+0x42 > Xorg`WaitForSomething+0x317 > Xorg`Dispatch+0x92 > Xorg`main+0x475 > Xorg`_start+0x14f > ld-elf.so.1`0x8007d5000 Hello Andriy! I remember we were discussed that problem before, can you please check if moused enabled (in rc.conf or by devd for USB mouse) and do you use Kern.vt.textmode (IIRC its name)? Mousecharstart is a first char of 4 to replace its bitmap with parts of mouse pointer. You can see its job by defining it to some of frequently used chars, then mouse pointer will be moved over many chars on the screen :-) About second question - there is no problem to just remove that warning, but think better to left it to make an idea for developers about what term ioctls doing with sysmuse devfs node. Thanks for testing! WBW ------ Aleksandr Rybalko