Martin wrote:

Run it once, you'll get an error. The second run
will cause a panic.

Additional info:
5.1-CURRENT FreeBSD 5.1-CURRENT #1: Tue Nov 18 00:30:15 CET 2003 i386
usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
ugen0: WINBOND W9967CF, rev 1.10/1.10, addr 3

This sounds similar to a bug which (I thought) I fixed earlier in the year [multiple calls of USB_SET_CONFIG conflicted with devfs, fixed in sys/dev/ugen.c rev 1.71].


I have a modem attached to the USB connector at the moment, so it's a bit tricky to test. Can you (or someone) provide a backtrace to help trace the cause?

(and is the panic "don't do that", perchance?)

--
Cheers,
Jay

http://www.evilrealms.net/ - Systems Administrator & Developer
http://www.imperial.ac.uk/ - 3rd year CS student

_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to