Re: [comedi] MITE transfer error with the NI PCIe card
'Éric Piel' via Comedi: Linux Control and Measurement Device Interface <[email protected]> Thu, 14 Jul 2022 05:47:26 -0700 (PDT)
| Newsgroups | gmane.linux.comedi |
|---|---|
| Message-ID | <[email protected]> |
------=_Part_486_917365493.1657802846917 Content-Type: multipart/alternative; boundary="----=_Part_487_934877200.1657802846917" ------=_Part_487_934877200.1657802846917 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, As a follow up, we've struggled, but eventually pinpointed the issue to the= =20 PCIe slots of the motherboard. All our systems use the same motherboard. In= =20 some cases, one slot doesn't work well with the NI DAQ board (we are still= =20 not really sure why), and just changing the slot seems to make the DAQ=20 board reliable again. Thanks Ian for pointing us towards a hardware issue! Cheers, =C3=89ric On Wednesday, 18 May 2022 at 11:41:58 UTC+2 Ian Abbott wrote: > Hi '=C3=89ric, > > On 16/05/2022 15:51, '=C3=89ric Piel' via Comedi: Linux Control and=20 > Measurement Device Interface wrote: > > Hi, > >=20 > > We have several systems which experience the same error from time to=20 > > time. During an acquisition (analog input), the read fails. Then, any= =20 > > following commands to the board fails with "input/output error" (5). Th= e=20 > > only way to restore the functionality is to power off the computer, wai= t=20 > > a few seconds, and power it on again. > >=20 > > On the time of the error, I see such message on the kernel side: > > [ 2843.893823] comedi comedi0: mite: transfer error ffffffff > > [ 2843.893856] comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error= =20 > > detected. > > [ 2843.893861] comedi comedi0: ni_tio_handle_interrupt: Gi_DRQ_Error=20 > > detected. > > [ 2843.893867] comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error= =20 > > detected. > > [ 2843.893870] comedi comedi0: ni_tio_handle_interrupt: Gi_DRQ_Error=20 > > detected. > > [ 2845.107044] comedi comedi0: timeout loading channel/gain list > > [ 2845.109086] comedi comedi0: timed out waiting for=20 > > AO_TMRDACWRs_In_Progress_St to clear > > [ 2845.615575] comedi comedi0: timeout loading channel/gain list > > [ 2845.617689] comedi comedi0: timed out waiting for=20 > > AO_TMRDACWRs_In_Progress_St to clear > > [ 2846.123539] comedi comedi0: timeout loading channel/gain list > > [ 2846.125651] comedi comedi0: timed out waiting for=20 > > AO_TMRDACWRs_In_Progress_St to clear > > [ 2846.631557] comedi comedi0: timeout loading channel/gain list > > [ 2846.633673] comedi comedi0: timed out waiting for=20 > > AO_TMRDACWRs_In_Progress_St to clear > >=20 > > Our systems are x86-64 with Ubuntu 18.04 (Linux 5.4) or Ubuntu 20.04=20 > > (Linux 5.13). The errors are quite hard to reproduce. On some systems,= =20 > > it doesn't seem to ever happen, on some others, it's only once in a=20 > > month, and few systems experience it almost daily. All the boards are N= I=20 > > PCIe-6251. > >=20 > > Any idea of what a "MITE transfer error" is? Is there any way we could= =20 > > recover from it in an easier way? Could it be a sign of a hardware=20 > > issue? Any hint is welcome! > > The "MITE transfer error" is a side effect of reading an unexpected=20 > value from the MITE status register. Reading ffffffff unexpectedly from= =20 > a PCI device register is often caused by an unreliable PCI connection,=20 > but in this case I'm not so sure because it is affecting several of your= =20 > systems. > > --=20 > -=3D( Ian Abbott <[email protected]> || MEV Ltd. is a company )=3D- > -=3D( registered in England & Wales. Regd. number: 02862268. )=3D- > -=3D( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=3D- > -=3D( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk )=3D- > --=20 You received this message because you are subscribed to the Google Groups "= Comedi: Linux Control and Measurement Device Interface" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/= comedi_list/4f684776-0b46-4263-bd8a-2982f15e5d01n%40googlegroups.com. ------=_Part_487_934877200.1657802846917 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div>Hi,</div><div>As a follow up, we've struggled, but eventually pinpoint= ed the issue to the PCIe slots of the motherboard. All our systems use the = same motherboard. In some cases, one slot doesn't work well with the NI DAQ= board (we are still not really sure why), and just changing the slot seems= to make the DAQ board reliable again.</div><div><br></div><div>Thanks Ian = for pointing us towards a hardware issue!</div><div>Cheers,<br></div><div>= =C3=89ric<br></div><br><div class=3D"gmail_quote"><div dir=3D"auto" class= =3D"gmail_attr">On Wednesday, 18 May 2022 at 11:41:58 UTC+2 Ian Abbott wrot= e:<br/></div><blockquote class=3D"gmail_quote" style=3D"margin: 0 0 0 0.8ex= ; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi '= =C3=89ric, <br> <br>On 16/05/2022 15:51, '=C3=89ric Piel' via Comedi: Linux Control= and=20 <br>Measurement Device Interface wrote: <br>> Hi, <br>>=20 <br>> We have several systems which experience the same error from time = to=20 <br>> time. During an acquisition (analog input), the read fails. Then, = any=20 <br>> following commands to the board fails with "input/output erro= r" (5). The=20 <br>> only way to restore the functionality is to power off the computer= , wait=20 <br>> a few seconds, and power it on again. <br>>=20 <br>> On the time of the error, I see such message on the kernel side: <br>> [ 2843.893823] comedi comedi0: mite: transfer error ffffffff <br>> [ 2843.893856] comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Er= ror=20 <br>> detected. <br>> [ 2843.893861] comedi comedi0: ni_tio_handle_interrupt: Gi_DRQ_Err= or=20 <br>> detected. <br>> [ 2843.893867] comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Er= ror=20 <br>> detected. <br>> [ 2843.893870] comedi comedi0: ni_tio_handle_interrupt: Gi_DRQ_Err= or=20 <br>> detected. <br>> [ 2845.107044] comedi comedi0: timeout loading channel/gain list <br>> [ 2845.109086] comedi comedi0: timed out waiting for=20 <br>> AO_TMRDACWRs_In_Progress_St to clear <br>> [ 2845.615575] comedi comedi0: timeout loading channel/gain list <br>> [ 2845.617689] comedi comedi0: timed out waiting for=20 <br>> AO_TMRDACWRs_In_Progress_St to clear <br>> [ 2846.123539] comedi comedi0: timeout loading channel/gain list <br>> [ 2846.125651] comedi comedi0: timed out waiting for=20 <br>> AO_TMRDACWRs_In_Progress_St to clear <br>> [ 2846.631557] comedi comedi0: timeout loading channel/gain list <br>> [ 2846.633673] comedi comedi0: timed out waiting for=20 <br>> AO_TMRDACWRs_In_Progress_St to clear <br>>=20 <br>> Our systems are x86-64 with Ubuntu 18.04 (Linux 5.4) or Ubuntu 20.= 04=20 <br>> (Linux 5.13). The errors are quite hard to reproduce. On some syst= ems,=20 <br>> it doesn't seem to ever happen, on some others, it's only = once in a=20 <br>> month, and few systems experience it almost daily. All the boards = are NI=20 <br>> PCIe-6251. <br>>=20 <br>> Any idea of what a "MITE transfer error" is? Is there an= y way we could=20 <br>> recover from it in an easier way? Could it be a sign of a hardware= =20 <br>> issue? Any hint is welcome! <br> <br>The "MITE transfer error" is a side effect of reading an unex= pected=20 <br>value from the MITE status register. Reading ffffffff unexpectedly from= =20 <br>a PCI device register is often caused by an unreliable PCI connection,= =20 <br>but in this case I'm not so sure because it is affecting several of= your=20 <br>systems. <br> <br>--=20 <br>-=3D( Ian Abbott <<a href data-email-masked rel=3D"nofollow">abb...@= mev.co.uk</a>> || MEV Ltd. is a company )=3D- <br>-=3D( registered in England & Wales. Regd. number: 02862268. )=3D= - <br>-=3D( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=3D= - <br>-=3D( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || <a href=3D"http://www.= mev.co.uk" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D"https= ://www.google.com/url?hl=3Den-GB&q=3Dhttp://www.mev.co.uk&source=3D= gmail&ust=3D1657889006813000&usg=3DAOvVaw1hL2HOvhc_T41LOyoOFoWX">ww= w.mev.co.uk</a> )=3D- <br></blockquote></div> <p></p> -- <br /> You received this message because you are subscribed to the Google Groups &= quot;Comedi: Linux Control and Measurement Device Interface" group.<br= /> To unsubscribe from this group and stop receiving emails from it, send an e= mail to <a href=3D"mailto:[email protected]">comedi_= [email protected]</a>.<br /> To view this discussion on the web visit <a href=3D"https://groups.google.c= om/d/msgid/comedi_list/4f684776-0b46-4263-bd8a-2982f15e5d01n%40googlegroups= .com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/ms= gid/comedi_list/4f684776-0b46-4263-bd8a-2982f15e5d01n%40googlegroups.com</a= >.<br /> ------=_Part_487_934877200.1657802846917-- ------=_Part_486_917365493.1657802846917--