Date: Wed, 26 Jun 2002 03:23:26 -0400 From: Anthony Jenkins <abjenkins@attbi.com> To: FreeBSD-current <current@freebsd.org> Subject: Still having problems with snd_emu10k1/ohci irq10 + cpu usage Message-ID: <3D196BEE.6030900@attbi.com>
next in thread | raw e-mail | index | archive | help
With nothing registering the interrupt I am mostly idle. Loading
snd_emu10k1 sound driver evokes the following in dmesg (if I can paste
it correctly this time):
pcm0: <Creative EMU10K1> port 0x2080-0x209f irq 10 at device 6.0 on pci2
pcib2: device pcm0 requested decoded I/O range 0x2080-0x209f
emu: setmap (116ac000, 800), nseg=1, error=0
emu: setmap (1d0cb000, 1000), nseg=1, error=0
pcm0: ac97 codec id 0x54524123 (TriTech TR28602)
pcm0: ac97 codec features 5 bit master volume, no 3D Stereo Enhancement
../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from
/usr/src/sys/dev/sound/pcm/sound.c:134
../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from
/usr/src/sys/dev/sound/pcm/sound.c:134
../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from
/usr/src/sys/dev/sound/pcm/sound.c:134
../../../vm/uma_core.c:1330: could sleep with "pcm0:fake" locked
from /usr/src/sys/dev/sound/pcm/channel.c:677
../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from
/usr/src/sys/dev/sound/pcm/sound.c:134
../../../vm/uma_core.c:1330: could sleep with "pcm0:fake" locked
from /usr/src/sys/dev/sound/pcm/channel.c:677
../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from
/usr/src/sys/dev/sound/pcm/sound.c:134
../../../vm/uma_core.c:1330: could sleep with "pcm0:fake" locked
from /usr/src/sys/dev/sound/pcm/channel.c:677
../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from
/usr/src/sys/dev/sound/pcm/sound.c:134
../../../vm/uma_core.c:1330: could sleep with "pcm0:fake" locked
from /usr/src/sys/dev/sound/pcm/channel.c:677
../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from
/usr/src/sys/dev/sound/pcm/sound.c:134
../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from
/usr/src/sys/dev/sound/pcm/sound.c:134
../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from
/usr/src/sys/dev/sound/pcm/sound.c:134
[snip]
../../../vm/uma_core.c:1330: could sleep with "pcm0:play:0" locked
from /usr/src/sys/dev/sound/pcm/channel.c:677
../../../vm/uma_core.c:1330: could sleep with "pcm0:play:0" locked
from /usr/src/sys/dev/sound/pcm/channel.c:677
../../../vm/uma_core.c:1330: could sleep with "pcm0:play:0" locked
from /usr/src/sys/dev/sound/pcm/channel.c:677
emu: setmap (3364000, 1000), nseg=1, error=0
../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from
/usr/src/sys/dev/sound/pcm/sound.c:134
../../../vm/uma_core.c:1330: could sleep with "pcm0:play:0" locked
from /usr/src/sys/dev/sound/pcm/channel.c:677
../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from
/usr/src/sys/dev/sound/pcm/sound.c:134
../../../vm/uma_core.c:1330: could sleep with "pcm0:play:1" locked
from /usr/src/sys/dev/sound/pcm/channel.c:677
../../../vm/uma_core.c:1330: could sleep with "pcm0:play:1" locked
from /usr/src/sys/dev/sound/pcm/channel.c:677
../../../vm/uma_core.c:1330: could sleep with "pcm0:play:1" locked
from /usr/src/sys/dev/sound/pcm/channel.c:677
emu: setmap (e37a000, 1000), nseg=1, error=0
[snip]
This is with no sound device usage. I kldunload the device 30 seconds
later and get this:
pcm0: warning: memblock list not empty
stray irq 10
pcm0: detached
emujoy0: detached
I get this one pretty reliably when unloading the device. When the
device is loaded, cpu usage looks like this: (`ps aux`):
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
nobody 548 41.9 2.9 15756 3752 con- RN Sun01PM 3372:40.70
/usr/local/sbin/setiathome -email -nice 15
root 24 39.1 0.0 0 3 ?? ML 31Dec69 1:39.04
(irq10: pcm0)
ajenkins 715 2.2 3.4 25792 4423 ?? S Sun01PM 88:16.73
kdeinit: kicker (kdeinit)
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
root 24 58.2 0.0 0 3 ?? ML 31Dec69 2:15.38
(irq10: pcm0)
nobody 548 19.4 2.9 15756 3752 con- RN Sun01PM 3373:17.87
/usr/local/sbin/setiathome -email -nice 15
ajenkins 682 1.0 2.4 20812 3093 ?? S Sun01PM 47:25.40
kdeinit: kded (kdeinit)
kldload'ing the usb module gives about the same result, sans the "could
sleep" messages, except I can't seem to unload the device:
su-205a# dmesg
[snip]
ohci0: <OPTi 82C861 (FireLink) USB controller> mem
0xea001000-0xea001fff irq 11 at device 5.0 on pci2
pcib2: device ohci0 requested decoded memory range 0xea001000-0xea001fff
usb0: OHCI version 1.0, legacy support
usb0: <OPTi 82C861 (FireLink) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: OPTi OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ohci1: <OPTi 82C861 (FireLink) USB controller> mem
0xea002000-0xea002fff irq 10 at device 5.1 on pci2
pcib2: device ohci1 requested decoded memory range 0xea002000-0xea002fff
usb1: OHCI version 1.0, legacy support
usb1: <OPTi 82C861 (FireLink) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: OPTi OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
su-2.05a# kldstat
Id Refs Address Size Name
1 6 0xc0100000 2e448c kernel
4 1 0xc0407000 39a88 acpi.ko
5 1 0xde2d7000 7000 ipfw.ko
6 1 0xde282000 2000 green_saver.ko
10 1 0xe0e1a000 1a000 usb.ko
su-2.05a# kldunload -i 10
kldunload: can't unload file: Device not configured
I'm fairly decent at C programming and Linux kernel development, and
trying to become more adept at FreeBSD kernel work, so any debugging
suggestions or requests for more info would be greatly appreciated.
TIA,
Anthony Jenkins
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D196BEE.6030900>