Re: Panic with ugen

2003-12-02 Thread Jay Cornwall
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

Re: Panic with ugen

2003-11-28 Thread Jay Cornwall
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

Re: Panic with ugen

2003-11-27 Thread Jay Cornwall
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

Re: Panic with ugen

2003-11-27 Thread Jay Cornwall
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.

Re: Panic with ugen

2003-11-26 Thread Jay Cornwall
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

Re: Panic with ugen

2003-11-26 Thread Jay Cornwall
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

ps: kvm_getprocs: No such file or directory

2003-09-13 Thread Jay Cornwall
Hi I just updated my FreeBSD 5.1 system to HEAD, to see if the NFS problems had been fixed. I've done {build|install}world, built a new kernel (with my config from 5.1), and mergemaster -i. Running ps with the -a option produces this error: ps: kvm_getprocs: No such file or directory Have I

Re: ps: kvm_getprocs: No such file or directory

2003-09-13 Thread Jay Cornwall
Ruslan Ermilov wrote: If you did it exactly like you describe, then you forgot to install and boot with the new kernel. Oh. *blushes* :) I can't believe I forgot to do 'make install'. Thanks Rus. ;) -- Cheers, Jay http://www.evilrealms.net/ - Systems Administrator Developer

Re: panic: don't do that, in ugen(4)

2003-05-27 Thread Jay Cornwall
-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