From owner-freebsd-usb@FreeBSD.ORG Fri Nov 12 23:38:41 2004 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8F8E16A4CE for ; Fri, 12 Nov 2004 23:38:41 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D44243D39 for ; Fri, 12 Nov 2004 23:38:41 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 2C7967A440; Fri, 12 Nov 2004 15:38:41 -0800 (PST) Message-ID: <41954980.6050201@elischer.org> Date: Fri, 12 Nov 2004 15:38:40 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Adam Kropelin References: <41953285.8070405@elischer.org> <4195340C.6030201@elischer.org> <049301c4c90a$d8109d80$03c8a8c0@kroptech.com> In-Reply-To: <049301c4c90a$d8109d80$03c8a8c0@kroptech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: usb@freebsd.org Subject: Re: anyone seen this problem.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Nov 2004 23:38:41 -0000 Adam Kropelin wrote: > Julian Elischer wrote: > >> Julian Elischer wrote: >> >>> >>> I'm working in 4.10++ plus a few MFC patches.. >>> >>> One of our applications regularly crashes when using a uhid device. >> >> >> >> ^^^^^ ugen > > > I've been able to panic the kernel fairly easily using ugen (this is > on 5.2.1 and 5.3). The trigger seems to be a length mismatch where the > device returns a different amount of data than was expected for a > particular transfer. I'm suspecting memory corruption since it will > often fail the ioctl a few times before actually panicing. > > I am not sufficiently clued to obtain a kernel backtrace like you did. > I presume I need to configure something to dump me into a kernel > debugger upon panic instead of the automatic reboot I'm currently > getting. I'll read up on such things and see if I can determine how > closely my situation matches yours. you need to set dumpdev="/dev/ad0s1b" in /etc/rc.conf and after the next boot. cd /(kernelcompile directory) kgdb kernel.debug /var/crash/vmcore.0 (probably best to make /var/crash a symlink somewhere with more space) 'bt' to get a stacktrace. > > > --Adam