[Asterisk-Users] DELL 2800 : PCI Parity error

Syed Akbar syed.akbar at alicosystems.com
Sun Jul 10 18:40:39 MST 2005


I had the same problem with a Dell PowerEdge 800 server and a TDM400 card. I
talked to Digium and they suggested a workaround by adding a NMI flag reset
in the Linux boot file. This only prevents a system lockup. The system
worked fine even with the blinking orange light and the dazed and confused
comment from the modprobe command. I have heard that the new firmware on the
TDM400P card has fixed this problem, but have not experienced that first
hand. 

In the same machine I am using a new TE110P with no problems at all.

Syed Akbar

Alico Systems Inc
www.alicosystems.com
Tel: 562-436-1510 

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Rod Bacon
Sent: Sunday, July 10, 2005 3:20 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] DELL 2800 : PCI Parity error

I too had this problem, on a 2850, as well as the occasional missed IRQ.

I went through all the usual zaptel tuning stuff.... Disabled fb, disabled
ht, disabled acpi (left io-apic enabled), then moved irq affinity of zaptel 
card to second CPU so all interrupts from zaptel are on their own. My
systems now run close to 100% in zttest, never miss an irq and don't seem to

generate PCI parity errors any more.

I don't know if I've fixed it, but you should really go through the whole
process anyway.


==========================================
Rod Bacon
Empowered Communications
Ground Floor, 102 York St. South Melbourne
Victoria, Australia. 3205
Phone: +613 99401600    Fax: +613 99401650
FWD: 512237                   ICQ: 5662270
==========================================


list wrote:
> Still not resolved
> 
> On Wed, 2005-06-08 at 01:16, David John Walsh wrote:
> 
>>Frank
>>
>>Did you ever resolve this?  If so what was the issue?
>>
>>On 03/05/05, list <list at nax.no> wrote:
>>
>>>Hi,
>>>I am struggling to get rid of a conflict on DELL 2800 : PCI Parity error
>>>(EB113 on the display)
>>>I am learning linux and asterisk as I go along, there might be obvious
>>>things I should know, but bear with me.
>>>
>>>>From demsg below my 2 digium cards installed are listed (no config or
>>>connections done to digium cards yet), the conflict is with the TDM400P
>>>card, without that card, in any slot, no alarm.
>>>
>>>        Zapata Telephony Interface Registered on major 196
>>>        Registered Tormenta2 PCI
>>>        Controller version: 24
>>>        FALC version: 00000000
>>>        TE110P: Setting up global serial parameters for E1 FALC V1.2
>>>        TE110P: Successfully initialized serial bus for card
>>>        Found a Wildcard: Digium Wildcard TE110P T1/E1
>>>        Freshmaker version: 71
>>>        Freshmaker passed register test
>>>        Uhhuh. NMI received. Dazed and confused, but trying to continue
>>>        You probably have a hardware problem with your RAM chips
>>>        Module 0: Installed -- AUTO FXS/DPO
>>>        Module 1: Not installed
>>>        Module 2: Not installed
>>>        Module 3: Installed -- AUTO FXO (FCC mode)
>>>        Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules)
>>>        Registered tone zone 8 (Norway)
>>>        TE110P: Span configured for CCS/HDB3/CRC4
>>>        Calling startup (flags is 4099)
>>>        wcte1xxp: Setting yellow alarm
>>>        usb.c: registered new driver wcusb
>>>        Wildcard USB FXS Interface driver registered
>>>        TE110P: Span configured for CCS/HDB3/CRC4
>>>        Calling startup (flags is 4099)
>>>        Registered tone zone 8 (Norway)
>>>        TE110P: Span configured for CCS/HDB3/CRC4
>>>        Calling startup (flags is 4099)
>>>        Registered tone zone 8 (Norway)
>>>
>>>ramchip problem is false, without the card all ok, ramtests on machine
>>>as well.
>>>
>>>lsmod shows wcusb driver on zaptel, I dont need that, can I remove it?
>>>is that a problem or not?
>>>
>>>        # lsmod
>>>        Module                  Size  Used by    Not tainted
>>>        usbserial              23964   0  (autoclean) (unused)
>>>        lp                      9156   0  (autoclean)
>>>        parport                38848   0  (autoclean) [lp]
>>>        autofs4                16984   0  (autoclean) (unused)
>>>        wcusb                  19552   0  (unused)
>>>        wctdm                  41088   0  (unused)
>>>        wcte11xp               22048   0  (unused)
>>>        zaptel                182080   4  [wcusb wctdm wcte11xp]
>>>        e1000                  77884   1  (autoclean)
>>>        floppy                 57552   0  (autoclean)
>>>        sg                     37388   0  (autoclean)
>>>        microcode               6912   0  (autoclean)
>>>        ide-cd                 34016   0  (autoclean)
>>>        cdrom                  32896   0  (autoclean) [ide-cd]
>>>        keybdev                 2976   0  (unused)
>>>        mousedev                5688   1
>>>        hid                    22308   0  (unused)
>>>        input                   6176   0  [keybdev mousedev hid]
>>>        ehci-hcd               20776   0  (unused)
>>>        usb-uhci               26860   0  (unused)
>>>        usbcore                81152   1  [usbserial wcusb hid ehci-hcd
>>>        usb-uhci]
>>>        ext3                   89960   6
>>>        jbd                    55060   6  [ext3]
>>>        megaraid2              38344   7
>>>        diskdumplib             5228   0  [megaraid2]
>>>        sd_mod                 13904  14
>>>        scsi_mod              115112   2  [sg megaraid2 sd_mod]
>>>
>>>finally my interrupts, bit confusing to me, looks like I have dual
>>>processor, can see the NMI but what else can be found here?
>>>
>>>        # cat /proc/interrupts
>>>                   CPU0       CPU1
>>>          0:    3298395    3303167    IO-APIC-edge  timer
>>>          1:       3300       2876    IO-APIC-edge  keyboard
>>>          2:          0          0          XT-PIC  cascade
>>>          8:          0          1    IO-APIC-edge  rtc
>>>         12:     236637     237965    IO-APIC-edge  PS/2 Mouse
>>>         14:     261779     262965    IO-APIC-edge  ide0
>>>         16:          0          0   IO-APIC-level  usb-uhci
>>>         18:          0          0   IO-APIC-level  usb-uhci
>>>         19:          0          0   IO-APIC-level  usb-uhci
>>>         23:          0         24   IO-APIC-level  ehci-hcd
>>>         29:   33133540   32846566   IO-APIC-level  t1xxp
>>>         38:      72500      83317   IO-APIC-level  megaraid
>>>         58:   32838989   33150525   IO-APIC-level  wctdm
>>>         72:     222855         12   IO-APIC-level  eth0
>>>        NMI:          1          0
>>>        LOC:    6601462    6601460
>>>        ERR:          0
>>>        MIS:          0
>>>
>>>any suggestions from someone experienced something similar?
>>>
>>>regards
>>>Frank
>>>_______________________________________________
>>>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-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-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-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




More information about the asterisk-users mailing list