Re: kern: device pcm problems

2002-07-02 Thread Martin Faxer

On 2002.07.02 16:28:10 +, Michael Hostbaek wrote:
 I have problems getting my sound card functioning under -CURRENT. (While
 it was working perfect under -STABLE).
 
 I simply added 'device pcm' to the kernel config, when booting on new
 kernel I get lots of errors like this:
 
 ESS Technology Maestro-2E port 0x1400-0x14ff irq 5 at device 8.0 on pci0
 ../../../vm/uma_core.c:1333: could sleep with pcm0 locked from ../../../dev/so
 und/pcm/sound.c:134

This is a well known problem; it's basically a diagnostic message
telling you that there's a deficiency in the pcm driver.

If you want to fix it permanently I suggest that you go and have a look
at dev/sound/pcm/sound.c:134 and look for a way of invoking UMA without
holding the lock.

If you just want to work around it, you can probably disable INVARIANTS
and WITNESS in your kernel configuration and hope that it won't turn
into a real problem (ie. panic.)

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: kern: device pcm problems

2002-07-02 Thread Juan Francisco Rodriguez Hervella

Martin Faxer escribió:

 On 2002.07.02 16:28:10 +, Michael Hostbaek wrote:
  I have problems getting my sound card functioning under -CURRENT. (While
  it was working perfect under -STABLE).
 
  I simply added 'device pcm' to the kernel config, when booting on new
  kernel I get lots of errors like this:
 
  ESS Technology Maestro-2E port 0x1400-0x14ff irq 5 at device 8.0 on pci0
  ../../../vm/uma_core.c:1333: could sleep with pcm0 locked from ../../../dev/so
  und/pcm/sound.c:134

 This is a well known problem; it's basically a diagnostic message
 telling you that there's a deficiency in the pcm driver.

 If you want to fix it permanently I suggest that you go and have a look
 at dev/sound/pcm/sound.c:134 and look for a way of invoking UMA without
 holding the lock.


Hello:

Im a bit corious about what's the meaning of UMA.

Thanks and sorry fot this simple question :)

JFRH.




 If you just want to work around it, you can probably disable INVARIANTS
 and WITNESS in your kernel configuration and hope that it won't turn
 into a real problem (ie. panic.)

 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: kern: device pcm problems

2002-07-02 Thread Martin Faxer

On 2002.07.02 17:56:28 +, Juan Francisco Rodriguez Hervella wrote:
 Im a bit corious about what's the meaning of UMA.
 
 Thanks and sorry fot this simple question :)

UMA is the Universal Memory Allocator, written by Jeff Roberson.

It's the memory manager and things like malloc(9) make use of it.

It was quite recently committed to -CURRENT so if you search the
archives it shouldn't be too hard to find mails describing it in more
detail.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message