On Thu, 10 Mar 2005 20:23:19 +0100, jerome lacoste
<[EMAIL PROTECTED]> wrote:
> I've sent this mail to the user list, but it seems that the traffic is
> happening more on the -devel list. No clean separation of concern :)
>
> So I post here, especially as Rich reported the same problem today or
> yesterday but Rich I cannot put you in copy as I don't have your email
> I just registered and don't have access to archives.
>
> So my DMA problem is killing me. I sometimes have hard locks, (see here
> http://forums.viaarena.com/messageview.aspx?catid=28&threadid=60131&STARTPAGE=1#391672
> )
>
> but am not sure if they are exactly the same problem.
>
> I now have a 6 hours uptime on the mythtv frontend/backend which is
> the best I could get in the past days, but I don't use the frontend,
> so I have less risk to trigger the problem.
>
> So I don't know if I have 1 or 2 issues, but both are apparently related to
> DMA.
>
> I am willing to spend time on it. Just need directions.
>
> Rich if you read that mail, feel free to contact me so that I have your email.
>
> J
>
> ---------- Forwarded message ----------
> From: jerome lacoste <[EMAIL PROTECTED]>
> Date: Wed, 9 Mar 2005 17:35:08 +0100
> Subject: IVTV_IRQ_DEC_DMA_ERR kills temporarly video stream in mythtv
> To: ivtv-users@lists.sourceforge.net
>
> Getting these logs in syslog. (see below) Happened 4-5 times since
> yesterday (box is new from Sunday). Using mythtv 0.17 with ivtv
> 0.2.0rcg.
>
> By curiosity I've tried to look at the patterns.
> It is always: 2 blocks of errors (one with intr 1 one with intr 2),
> then the message "Checking FW at xxx jiffies". Then the contents are
> always similar in the two blocks except for the state which always
> goes from 0x00000011 to 0x00000001. Not sure if that helps.
>
> Google found one reference [1] but not applicable to my case
> (downgrade). I have not yet reached a stable state :)
>
> Note that this change log seems to implicate the spin locking change
> with ivtv 0.3 series. Not sure if that could help. See
> http://205.209.168.201/~ckennedy/ivtv/ivtv-0.3/OLD/ivtv-0.3.1k_3.1l.diff
>
> I've also browsed the 0.3 diffs and it appears that the important
> fixes are backported to 0.2.0. So I guess I don't need to upgrade to
> that branch.
>
> So the problem happened yesterday night and now. I restarted the box.
> It rehappened within 5 min but this time without messages in syslog. I
> rerestarted mythfrontend and the box has been happy for 20 min.
>
> I will not try to investigate that issue as restarting the front end
> solved it, except if you want me to.
>
> Mar 9 15:50:22 medios kernel: ivtv: DMA Registers State: xfer:
> 0x00000002, state: 0x00000011 dec_addr: 0x00000000 enc_a
> ddr: 0x1cb10028 control: 0x00000003
> Mar 9 15:50:22 medios kernel: ivtv: DMA DEC Buffers:
> Mar 9 15:50:22 medios kernel: 0x00000000:0x00000000:0x00000000
> Mar 9 15:50:22 medios kernel: ivtv: DMA ENC Buffers:
> Mar 9 15:50:22 medios kernel: 0x001302dc:0x071cc000:0x00004000
> Mar 9 15:50:22 medios kernel: 0x001342dc:0x07218000:0x80004000
> Mar 9 15:50:22 medios kernel: 0x0012b2dc:0x0718c000:0x00004000
> Mar 9 15:50:22 medios kernel: 0x0012f2dc:0x071c8000:0x80004000
> Mar 9 15:50:22 medios kernel: 0x001022dc:0x142e8000:0x80004000
> Mar 9 15:50:22 medios kernel: 0x0011fadc:0x11bc4000:0x80004000
> Mar 9 15:50:22 medios kernel: 0x00174adc:0x11504000:0x00004000
> Mar 9 15:50:22 medios kernel: 0x00178adc:0x11508000:0x80004000
> Mar 9 15:50:22 medios kernel: ivtv: IRQ: IVTV_IRQ_DEC_DMA_ERR intr 2
> Mar 9 15:50:22 medios kernel: ivtv: DMA Registers State: xfer:
> 0x00000002, state: 0x00000001 dec_addr: 0x00000000 enc_a
> ddr: 0x1cb10028 control: 0x00000003
> Mar 9 15:50:22 medios kernel: ivtv: DMA DEC Buffers:
> Mar 9 15:50:22 medios kernel: 0x00000000:0x00000000:0x00000000
> Mar 9 15:50:22 medios kernel: ivtv: DMA ENC Buffers:
> Mar 9 15:50:22 medios kernel: 0x001302dc:0x071cc000:0x00004000
> Mar 9 15:50:22 medios kernel: 0x001342dc:0x07218000:0x80004000
> Mar 9 15:50:22 medios kernel: 0x0012b2dc:0x0718c000:0x00004000
> Mar 9 15:50:22 medios kernel: 0x0012f2dc:0x071c8000:0x80004000
> Mar 9 15:50:22 medios kernel: 0x001022dc:0x142e8000:0x80004000
> Mar 9 15:50:22 medios kernel: 0x0011fadc:0x11bc4000:0x80004000
> Mar 9 15:50:22 medios kernel: 0x00174adc:0x11504000:0x00004000
> Mar 9 15:50:22 medios kernel: 0x00178adc:0x11508000:0x80004000
> Mar 9 15:50:22 medios kernel: ivtv: Checking FW at 5900597 jiffies
>
> [1] http://www.mail-archive.com/ivtv-users@lists.sourceforge.net/msg00129.html
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Ivtv-users mailing list
> Ivtv-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ivtv-users
>
You don't by chance have a VIA chipset mobo? There is some thing to
this effect in the IVTV FAQs about via and DMA problems
--
_\ | /_
(@ @)
-----oOOo-(_)-oOOo-----
~Mark
~Gardner
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Ivtv-users mailing list
Ivtv-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ivtv-users
