Hey Karl, On Tue, 2003-03-18 at 02:54, Karl and Tanya Pizzolatto wrote: > I didn't find anything. What I wrote down follows below. Keep in mind this > report has gone from screen to eyes to fingers to paper to eyes to fingers to > screen! (well, there's keyboard and computer between fingers and screen, but > you get the idea). If you can tell me how to trap this (or where to look for > it), I will be very grateful. Otherwise, I hope this helps you with the > driver. [..] > Kernel BUG at sched.c:564! ins: 0 del: 0 ae: 0 td1=0.009 td2=0.0040
Oi, an oops. Could you try two things? 1) try with a vanilla 2.4.20 kernel. 2) try loading modules in the same order on startup (so their memory location between two subsequent boots is the same). After that, redo the same thing, and on the next boot, run "ksymoops", paste the output of the previous oops (which you need to write down again, sorry...) into it, press enter a few times and wait for output. That should give a kernel backtrace. Ronald -- Ronald Bultje <[EMAIL PROTECTED]> ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ Mjpeg-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
