From owner-freebsd-current@FreeBSD.ORG Mon May 26 05:59:12 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 9CDB837B401 for ; Mon, 26 May 2003 05:59:12 -0700 (PDT) Received: from viper.evilrealms.net (evilrealms.demon.co.uk [62.49.12.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2113243FBF for ; Mon, 26 May 2003 05:59:11 -0700 (PDT) (envelope-from jay@viper.evilrealms.net) Received: from viper.evilrealms.net (jay@localhost [127.0.0.1]) by viper.evilrealms.net (8.12.9/8.12.8) with ESMTP id h4QCwrsj001437; Mon, 26 May 2003 13:58:53 +0100 Received: from localhost (localhost [[UNIX: localhost]]) by viper.evilrealms.net (8.12.9/8.12.8/Submit) id h4QCwqwF001436; Mon, 26 May 2003 13:58:52 +0100 From: Jay Cornwall To: Mark Blackman Date: Mon, 26 May 2003 13:58:37 +0100 User-Agent: KMail/1.5.1 References: <200305070308.42781.jay@evilrealms.net> <20030511000432.GP94201@cicely9.cicely.de> <20030525191232.GA76628@maddog.blackmans.org> In-Reply-To: <20030525191232.GA76628@maddog.blackmans.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200305261358.52954.jay@evilrealms.net> cc: freebsd-current@freebsd.org cc: ticso@cicely.de cc: speedtouch@ml.free.fr Subject: Re: USB ugen_set_interface issue (+ possible patch) 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: Mon, 26 May 2003 12:59:12 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 25 May 2003 20:12 pm, Mark Blackman wrote: > Thanks for the effort here, but using a -current from May 24, > (patch committed on May 18), I'm still getting device > panics of the same type when using modem_run (from pppoa). However, > the modem_run gets a bit further and most of the upload/download > operations succeed. The panic now occurs at BLOCK4 instead > of immediately. Hmm. I've had a thorough look into /sys/dev/usb/ugen.c, and I can't see how= =20 this panic could be occurring since the patch. =46irstly, could you try a more recent version of the Speedtouch software? = The=20 =2D -current port is only for 1.1b2, and some of the USB code has changed s= ince.=20 You can download the most recent version from http://speedtouch.sf.net/. In order to help me trace the panic, could you also try to obtain a core du= mp=20 from the kernel, and a backtrace to the panic from the dump? A short guide = on=20 doing this is given here: http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html http://www.onlamp.com/pub/a/bsd/2002/04/04/Big_Scary_Daemons.html If you can send me the backtrace (the 'where' output of kgdb), it will grea= tly=20 help in finding the cause of the problem. If you need help in getting a=20 backtrace, feel free to mail me privately and I'll explain it step by step.= =20 (I can't reproduce the panic on my system, unfortunately) Cheers, Jay =2D --=20 http://www.evilrealms.net/ - Systems Administrator & Developer http://www.ic.ac.uk/ - Imperial College, 2nd year CS student =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+0g+CfJLn3O/2GbERAi+6AKCgB8CK7WSj6OrsEqLS8xKv7MsnTACfRomo 4RcNfRgd+RZvhqqKyI9MmGE=3D =3D4vtp =2D----END PGP SIGNATURE-----