page fault panic tracked down (selwakeuppri())
shoesoft at gmx.net
Sun Jan 4 14:46:21 PST 2004
On Sun, 2004-01-04 at 23:24, Don Lewis wrote:
> On 4 Jan, Stefan Ehmann wrote:
> > I took out the debug options because it was just too slow. Put back
> > INVARIANTS (but no WITNESS) now and speed is nice again.
> This problem is more likely to be caught by INVARIANTS than WITNESS.
> > Applied your suggested changes which resulted in a panic. No
> > assertations were triggered though.
Updated to plain (= no patches/hacks) again, also put in the
For the first time I got a backtrace that ended in the soundcard module
- So maybe this is the right direction (on the other hand this might be
some newly introduced error)
panic: bad bufsize
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1 0xc04e5198 in boot (howto=256) at
#2 0xc04e5527 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3 0xc07ec648 in feed_vchan_s16 () from /boot/kernel/snd_pcm.ko
#4 0xc07e2c6d in sndbuf_feed () from /boot/kernel/snd_pcm.ko
#5 0xc07e3225 in chn_wrfeed () from /boot/kernel/snd_pcm.ko
#6 0xc07e327c in chn_wrintr () from /boot/kernel/snd_pcm.ko
#7 0xc07e3990 in chn_intr () from /boot/kernel/snd_pcm.ko
#8 0xc07fca2f in csa_intr () from /boot/kernel/snd_csa.ko
#9 0xc07fb724 in csa_intr () from /boot/kernel/snd_csa.ko
#10 0xc04d1692 in ithread_loop (arg=0xc1737b00)
#11 0xc04d0684 in fork_exit (callout=0xc04d1500 <ithread_loop>, arg=0x0,
frame=0x0) at /usr/src/sys/kern/kern_fork.c:796
Nearly all other panics (I put a collection of ~20 backtraces on
http://stud4.tuwien.ac.at/~e0125637/fbsd/ if it's of any interest) ended
up in file system code.
More information about the freebsd-current