> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:ivtv-devel- > [EMAIL PROTECTED] On Behalf Of Mark Bryars > Sent: 09 January 2008 12:15 > To: Hans Verkuil > Cc: Discussion list for development of the IVTV driver > Subject: Re: [ivtv-devel] Crashes with ivtv on 2.6.24-rc3 > > Hans Verkuil wrote: > > Hi Mark, > > > > I'll be looking at this during the weekend. It's a very interesting > result > > and it will be an nice challenge to figure out how this deadlock can > occur > > :-) > > > I think the memory is getting trashed, and its not a deadlock its just > a > duff lock. > > ivtv67108864: dma_reg_lock already locked! Deadlocked... > > ^-- I dont have that many cards. >
I think the best way to investigate this might be to add some code that checks the ivtv_cards array and check that itv->num for each card matches the offset in the array. You could scatter calls to that in various places and find when it goes wrong. It would also be worth adding a print of the address of the itv pointer used in the interrupt handler and also when they are allocated to make sure it is not getting a bad pointer which would have a similar effect on the printout above. John No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.17.13/1214 - Release Date: 08/01/2008 13:38 _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
