devfs kernel panic

Mike Schreckengost mrpolitics at
Sun Jan 25 17:24:31 PST 2004

Ya know, I am experiencing *exactly* the same problem. Xine has not worked 
for me since 5.2-RELEASE (locks the system hard w/ a kernel panic such as 
the one you described). Accessing /dev/dsp1 causes the panic, it seems. The 
one commonality that I see is that we are both using the snd_emu10k1.ko and 
snd_pcm.ko drivers... I wonder if there is a problem in these kernel 
modules, or if the problem is more widespread.
    Anyways, if you discover a workaround or otherwise figure out what to do 
about this, I'd love to know.

Thanks in advance,

>From: Richard Cox <conardcox at>
>Reply-To: conardcox at
>To: freebsd-current at
>Subject: devfs kernel panic
>Date: Sun, 25 Jan 2004 15:19:19 -0500
>I was trying to get xine going on 5.2 Current and ran into a kernel panic.
>After a bit of investigating, I discovered I could reproduce the panic
>consistently just by trying to stat /dev/dsp1 (i.e., just an 'ls /dev/dsp1'

>rocket:/usr/src/sys/fs/devfs]# kldstat
>Id Refs Address    Size     Name
>  1   11 0xc0400000 3a3d08   kernel
>  2    1 0xc07a4000 1ceac    linux.ko
>  3    1 0xc07c1000 8744     snd_emu10k1.ko
>  4    2 0xc07ca000 1d5d8    snd_pcm.ko
>  5    1 0xc07e8000 1af00    radeon.ko
>  6    1 0xc0803000 4da2c    acpi.ko

Check out the coupons and bargains on MSN Offers!

More information about the freebsd-current mailing list