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

as i386-undermydesk-freebsd... (no debugging symbols found)... panic: bremfree: removing a buffer not on a queue panic messages: --- panic: don't do that syncing disks, buffers remaining... 1806 panic: bremfree: removing a buffer not on a queue Uptime: 6m34s Dumping 191 MB ata0: resetting devices

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

-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

Re: [Fwd: panic: don't do that ?]

On Wed, Feb 12, 2003 at 12:23:53AM +0100, David Vidal Rodr?guez wrote: Hi, 1) If they aren't loaded (I forgot them on the 1st try by mistake), the kernel panics if I try to change hw.snd.maxautovchans (that odd bwrite: buffer is not busy??? message again!). That shouldn't happen: if I don't

Re: [Fwd: panic: don't do that ?]

Olivier Houchard wrote: I'm afraid I don't know anything about that. The oid doesn't exist for me if I don't load the kernel module. That's my fault for being imprecise. I forgot to mention that I had snd_pcm.ko loaded, but nothing else. I believe it has been fixed on -CURRENT. You may try

Re: [Fwd: panic: don't do that ?]

Olivier Houchard wrote: Ooops sorry. They have to be applied in /sys/dev/sound/pcm. My bad, next time I'll make them against /usr/src :) Thanks! That did the trick. Where I have to keep an eye is to the device busy problem, since it doesn't appear immediately. CU, David. To Unsubscribe:

[Fwd: panic: don't do that ?]

Hi! I've sent this post to comp.unix.bsd.freebsd, and I've been told that I should report the problem to this list, so... Original Message Hi folks! I was trying to modularize the sound in my 5.0R machine, which has two sound cards: $ dmesg | grep pcm.: pcm0: VIA VT82C686A

panic: don't do that

: repeat make_dev(ad0s1) panic: don't do that Debugger(panic) Is this really a Driver mistake ? Or am I mistaken ? I guess we should do a # chflags nodump /dev during the install on CURRENT. Why has been /dev dumped anyway ? Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED

Re: panic: don't do that

On Tue, 8 Jan 2002, Martin Blapp wrote: ... during the install on CURRENT. Why has been /dev dumped anyway ? I bet you have old /dev entries as a fallback left which got backed up. What do you see on a unmounted /dev? Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To

Re: panic: don't do that

Hi, during the install on CURRENT. Why has been /dev dumped anyway ? I bet you have old /dev entries as a fallback left which got backed up. I guess no. This was a fresh CURRENT installation from November 2001. What do you see on a unmounted /dev? devfs cannot be unmounted as I know.