From owner-freebsd-current@freebsd.org Mon Feb 22 07:08:03 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2A78AAFD26 for ; Mon, 22 Feb 2016 07:08:03 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 706EA1E82 for ; Mon, 22 Feb 2016 07:08:03 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id C2DEE1FE022; Mon, 22 Feb 2016 08:08:01 +0100 (CET) Subject: Re: new computer, strange usb messages at boot To: Larry Rosenman , freebsd-current@freebsd.org References: <20160220051951.GA47875@lrosenman-dell.lerctr.org> <20160220120401.GA91220@kib.kiev.ua> <20160220122416.GA1026@lrosenman-dell.lerctr.org> <2575cfd714188f7ffbc873cb5d87cc97@thebighonker.lerctr.org> From: Hans Petter Selasky Message-ID: <56CAB468.4070201@selasky.org> Date: Mon, 22 Feb 2016 08:10:32 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <2575cfd714188f7ffbc873cb5d87cc97@thebighonker.lerctr.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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, 22 Feb 2016 07:08:03 -0000 On 02/21/16 17:28, Larry Rosenman wrote: > Does this mean that the touch screen is hitting a limit in FreeBSD's > driver? Yes, the hid driver is limiting the range of some report. This should be harmless. You would need to dump the HID descriptor to see the limits. Maybe we could raise the limit from 256 to 4096 or something in that range, to make the warning to away. It's sys/dev/usb/usb_hid.c: > /* range check usage count */ > if (c->loc.count > 255) { > DPRINTFN(0, "Number of " > "items truncated to 255\n"); > s->ncount = 255; > } else > s->ncount = c->loc.count; > Try adding c->loc.count to the printout, to see the limit it is exceeding. --HPS