From owner-freebsd-current@FreeBSD.ORG Tue May 27 17:51:43 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 1564D37B401; Tue, 27 May 2003 17:51:43 -0700 (PDT) Received: from viper.evilrealms.net (evilrealms.demon.co.uk [62.49.12.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E3B043F3F; Tue, 27 May 2003 17:51:41 -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 h4S0pinD012544; Wed, 28 May 2003 01:51:44 +0100 Received: from localhost (localhost [[UNIX: localhost]]) by viper.evilrealms.net (8.12.9/8.12.8/Submit) id h4S0piAn012543; Wed, 28 May 2003 01:51:44 +0100 From: Jay Cornwall To: Juli Mallett Date: Wed, 28 May 2003 01:51:42 +0100 User-Agent: KMail/1.5.1 References: <20030527180621.A10430@FreeBSD.org> In-Reply-To: <20030527180621.A10430@FreeBSD.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: <200305280151.44094.jay@evilrealms.net> cc: freebsd-current@freebsd.org Subject: Re: panic: don't do that, in ugen(4) 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: Wed, 28 May 2003 00:51:43 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 28 May 2003 00:06 am, Juli Mallett wrote: > Running `quickcam' twice from: > http://people.freebsd.org/~jmallett/qce-freebsd.tgz > > Yields the following loveliness: [..] This is the same issue another person (Mark Blackman) is seeing with the=20 Speedtouch software. I submitted a patch to the kernel recently which=20 alleviated the problem for me (and others), but Mark is still having proble= ms=20 (albeit slightly different since the patch) with ugen_set_interface panicin= g=20 inside /sys/dev/usb/ugen.c. I'll be looking into this either tomorrow or the next day, to try to work o= ut=20 how it's still occurring and fix it. If anyone else decides to take a look,= =20 it may help to see the patch recently committed to ugen.c: =20 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/ugen.c.diff?r1=3D1.69= &r2=3D1.70&f=3Dh It's related to the way ugen treats device nodes since; since devfs was=20 introduced into the kernel, there have been stricter rules on how the kerne= l=20 can manipulate device nodes, and ugen.c is (apparently) still breaking thes= e=20 rules. 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+1AgffJLn3O/2GbERAjlrAKCxOMROjqZdSKHmYoywNt/85JQW4gCbBAQO OT6Z2VJGht+J1gctuWLZqN4=3D =3DM6D7 =2D----END PGP SIGNATURE-----