[Asterisk-Users] [Asterisk-Dev] Re: FXO PCI Master abort

[Mark Burton]

Dear Zaptel and wcfxo devellopers,

Hi, so far I have had no success moving this issue forward. Carl 
Andersson has been kind enough to help build various kernels to try, 
but with no success.

So, I have tried to debug the problem directly. So far I have applied 
the patch below to wcfxo.c. (on the latest CVS head) This makes my 
system stable again (in that I dont have to keep pressing the big red 
button).
In principle I can not see how this patch would harm a working system, 
and seems to me to be the right thing to do anyway. I would love to 
know why not.

However, of course, this does not fix the problem.

Firstly the watchdog never re-starts the DMA engine (even with the 
watchdog enabled in zaptel). This means that the driver sits there 
"impotent" and in order to recover you have to unload and reload the 
module.
	Hardly ideal.

Second, of course, I am no nearer finding out why I am getting the 
erroneous IRQ in the first place!

Any help much appreciated...

Cheers

Mark.



--- wcfxo.c     2005-08-13 14:16:44.690969912 +0100
+++ wcfxo.c.old 2005-08-13 08:51:00.000000000 +0100
@@ -726,18 +726,11 @@
         /* Reset Master and TDM */
         outb(0x01, wc->ioaddr + WC_CNTL);
         outb(0x01, wc->ioaddr + WC_OPER);
-
-        printk("UnMasking IRQ\n");
-       outb(0x3f, wc->ioaddr + WC_MASK0);
  }


  static void wcfxo_stop_dma(struct wcfxo *wc)
  {
-       /* Enable interrupts (we care about all of them, except the one 
that gave us the abort) */
-        printk("Masking IRQ's, waiting for watchdog to restart\n");
-       outb(0x2f, wc->ioaddr + WC_MASK0);
-
         outb(0x00, wc->ioaddr + WC_OPER);
  }

On 2 Aug 2005, at 13:56, Mark Burton wrote:

> [posted here as well as -users as the situation is stranger than I had 
> first thought... and I'm running standard parts... ]
>
> Hi, I have the following configuration, which doesn't seem to work, 
> any help much appreciated
>
> I am trying to get a  X101P FXO card working AT ALL!
> (It has the Ambient chip on it)
>
> All I get is:
>
> FXO PCI Master abort errors.
>
> Depending on the way it feels, either these are repeated till 
> /var/log/ is full, or I get one and then the thing hangs.
> This may, or may not, have something to do with a message
>
> Uhhuh. NMI received. Dazed and confused, but trying to continue
> You probably have a hardware problem with your RAM chips
>
> I have tried all combinations of
> Debian builds of Linux 2.4.27, 2.6.8 and 2.6.11
> Debian builds of Zaptel
> CVS builds of Zaptel
>
> I have tried it on an old P2 and a newer P4
>
> I have switch off asterisk to make sure it's not in the asterisk 
> configuration...
>
> In all cases with the same result.
>
> I've mucked with the IRQ's till they dont conflict.. no change...
>
> I've tried 2 different cards....
>
> So, I'm clearly deluded as everybody else seems to have no problem.
>
> Can anybody help - what silly thing have I done?
>
> Cheers
>
> Mark.
>
>
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>

_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev