Paul Koster wrote: > Philip Rowlands wrote: > >> Attached are serial console logs captured by Grant Kwok (thanks Grant!) >> showing the kernel log during system lockup - he's having some trouble >> mailing the list. >> >> Anyone familiar with interrupt handler oopses? I'm among the least >> qualified to comment on interrupt handlers, but... is it correct that >> ivtv uses SA_INTERRUPT (disable all interrupts during handler), yet >> doesn't use a minimal "top-half"? In ivtv_irq_handler I see spinlocks, >> printks, and other fun stuff which might cause complications. >> >> If not that, then perhaps the kfree() at ivtv-fileops.c:1494 (in >> ivtv_v4l2_close)? > > > These logs are quite similar to my situation since I upgraded to newer > versions than 0.3.2f. > > System description: > - PVR 350 (using TV out) > - PVR 250 > - 384 MB memory (no swapfile enabled)
I justed read your message and it hit me. When I originally reported the problem, I stated that i have 512MB ram, that actually is incorrect - I do infact only have 384MB memory. My box does have a 512mb dimm in it but it just occured to me because i'm using an Asus p4r800-vm mobo (which steals 128mb of your memory for video memory) i'm left with 384. I don't know how relevant that is other than the fact that it's these allocation errors are just more likely to occur on systems with less ram, but I thought i'd mention it in case there could be something specific with the configuration of 384mb. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
