From owner-freebsd-usb@FreeBSD.ORG Fri Nov 12 22:56:37 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 526C916A4CE for ; Fri, 12 Nov 2004 22:56:37 +0000 (GMT) Received: from ms-smtp-02.nyroc.rr.com (ms-smtp-02.nyroc.rr.com [24.24.2.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8EA443D45 for ; Fri, 12 Nov 2004 22:56:36 +0000 (GMT) (envelope-from akropel1@rochester.rr.com) Received: from mail.kroptech.com (roc-24-93-20-125.rochester.rr.com [24.93.20.125])iACMuSYn007868; Fri, 12 Nov 2004 17:56:30 -0500 (EST) Received: from pia (pia.kroptech.com [192.168.200.3]) by mail.kroptech.com (Postfix) with SMTP id 70C1011376E; Fri, 12 Nov 2004 18:48:22 -0500 (EST) Message-ID: <049301c4c90a$d8109d80$03c8a8c0@kroptech.com> From: "Adam Kropelin" To: "Julian Elischer" References: <41953285.8070405@elischer.org> <4195340C.6030201@elischer.org> Date: Fri, 12 Nov 2004 17:56:28 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine 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 22:56:37 -0000 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. --Adam