From owner-freebsd-current@FreeBSD.ORG Tue Dec 2 11:04:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EA5716A4CE for ; Tue, 2 Dec 2003 11:04:00 -0800 (PST) Received: from python.evilrealms.net (evilrealms.demon.co.uk [62.49.12.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8E3243FCB for ; Tue, 2 Dec 2003 11:03:57 -0800 (PST) (envelope-from jay@evilrealms.net) Received: from evilrealms.net (viper.evilrealms.net [192.168.1.2]) by python.evilrealms.net (Postfix) with ESMTP id 230965C30; Tue, 2 Dec 2003 19:03:54 +0000 (GMT) Message-ID: <3FCCE217.2090302@evilrealms.net> Date: Tue, 02 Dec 2003 19:03:51 +0000 From: Jay Cornwall User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin References: <1069874342.704.18.camel@klotz.local> <3FC60935.3050604@evilrealms.net><3FC7510A.8070906@evilrealms.net> <1070218984.675.4.camel@klotz.local> In-Reply-To: <1070218984.675.4.camel@klotz.local> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Panic with ugen X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 02 Dec 2003 19:04:00 -0000 Martin wrote: >>Could you try the attached patch (rm -f sys/dev/usb/ugen.c, cvs up >>sys/dev/usb/ugen.c, patch ...) to see if it alleviates the panic? It >>should at least give a more specific panic, if it doesn't fix the problem. > Sorry for the delay, I got a busy weekend. And sorry for the delay here too. Had a busy start-of-week. :\ > I still got a panic after starting the small piece of code, but it looks > like this now: > > fatal trap 12 > fault virtual address = 0x5 > supervisor read, page not present > [...] > > trace shows me "ugen_set_config()" at top of the stack. Hmm. I'm afraid I'm not really sure why my patch doesn't fix the problem. Unfortunately, to fix this I think I'd need to be able to reproduce the panic locally and do some debugging. Otherwise, I'd just be guessing at what's causing the problem. If you could provide a full backtrace with a debug-enabled kernel ('makeoptions DEBUG=-g' in your kernel configuration file, with GDB using kernel.debug to obtain symbols - I think onlamp.com had a tutorial on doing this) I may be able to locate where things are going wrong. But if it's too much hassle for you, I think it'd be best to pass this on to a developer with a machine to test the panic on. Thanks for trying the patches, though. :) -- Cheers, Jay http://www.evilrealms.net/ - Systems Administrator & Developer http://www.imperial.ac.uk/ - 3rd year CS student