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 her
On Fri, 2003-11-28 at 14:43, Jay Cornwall 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
Martin wrote:
Could you try the attached patch, to see if it fixes the panic on the second
run of your program?
No success. Still same panic.
Oops, my bad. I misread your backtrace, and fixed a similar bug in
ugen_set_interface rather than ugen_set_config.
Could you try the attached patch (rm
On Thu, 2003-11-27 at 15:24, Jay Cornwall wrote:
> Could you try the attached patch, to see if it fixes the panic on the second
> run of your program?
No success. Still same panic.
Martin
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/m
On Thursday 27 November 2003 15:33, Jay Cornwall wrote:
> Daan Vreeken [PA4DAN] wrote:
> > If you have time left, could you perhaps also have a look at kern/51186?
> > I have filed it back in March and it's still open. (Fixes a memory
> > corruption bug in ugen).
>
> I'm not a committer, I'm afraid
Daan Vreeken [PA4DAN] wrote:
If you have time left, could you perhaps also have a look at kern/51186?
I have filed it back in March and it's still open. (Fixes a memory corruption
bug in ugen).
I'm not a committer, I'm afraid, so it's probably best to get in touch with
the code maintainer. ([EMA
Martin wrote:
panic()
destroy_dev()
ugen_destroy_devnodes()
ugen_set_config()
Could you try the attached patch, to see if it fixes the panic on the second
run of your program?
--
Cheers,
Jay
http://www.evilrealms.net/ - Systems Administrator & Developer
http://www.imperial.ac.uk/ - 3rd year CS s
On Thursday 27 November 2003 01:08, Jay Cornwall wrote:
> > It looks like this:
> >
> > panic()
> > destroy_dev()
> > ugen_destroy_devnodes()
> > ugen_set_config()
>
> Yes, that's the one, and I think I can see why. The existing code fixed
> devfs problems for normal ugen_set_config calls, but does
Martin wrote:
It looks like this:
panic()
destroy_dev()
ugen_destroy_devnodes()
ugen_set_config()
Yes, that's the one, and I think I can see why. The existing code fixed devfs
problems for normal ugen_set_config calls, but doesn't account for what
happens when an error occurs (which is presumab
On Wed, 2003-11-26 at 20:44, Jay Cornwall wrote:
> Can you (or someone) provide a backtrace to help trace the cause?
OK. Here is what I found out, I didn't write down any register contents
and stuff, sorry.
It looks like this:
WARNING: Driver mistake: destroy_dev on 114/1
panic: don't do that
d
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: 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
Hi,
I'm still trying to write a webcam application for my
"Creative Videoblaster Webcam Go". I have not much luck, but
I accidently discovered how to cause panic with few lines
of code while using ugen.
Here is the code:
>--<
#include
#include
#include
12 matches
Mail list logo
