[asterisk-users] PRI worked fine for months, nowit stopps working after 2-3 hours

[Loic Didelot]

Hello,
I wanted to relaunch my problem with a quite precise and small question.

Could the command "lsusb" affect interrupts when executing it regularly
(cron) and if the zaptel pci card is sharing an interrupt with a usb
bus?

I have a Digium PRI card and a few Xorcom USB Devices. The Digium card
seems to share the IRQ with some USB bus.

cat /proc/interrupts 
           CPU0       CPU1       
  0:        153          0   IO-APIC-edge      timer
  1:          2          0   IO-APIC-edge      i8042
  8:          3          0   IO-APIC-edge      rtc
  9:          1          0   IO-APIC-fasteoi   acpi
 16:   54917872          0   IO-APIC-fasteoi   uhci_hcd:usb1, wcte12xp0
 18:          0          0   IO-APIC-fasteoi   uhci_hcd:usb2
 19:  231245335          0   IO-APIC-fasteoi   uhci_hcd:usb3,
ehci_hcd:usb7
 20:      20892          0   IO-APIC-fasteoi   uhci_hcd:usb4, libata,
libata
 21:          0          0   IO-APIC-fasteoi   ehci_hcd:usb5,
uhci_hcd:usb6
218:          6          0      none-edge    
219:    2014578          0   PCI-MSI-edge      eth3
NMI:          0          0   Non-maskable interrupts
LOC:    2180853    1019374   Local timer interrupts
RES:       1655        872   Rescheduling interrupts
CAL:         49         74   function call interrupts
TLB:       5322       5969   TLB shootdowns
TRM:          0          0   Thermal event interrupts
SPU:          0          0   Spurious interrupts
ERR:          0
MIS:          0



lsusb 
Bus 007 Device 003: ID e4e4:1152  
Bus 007 Device 002: ID e4e4:1142  
Bus 007 Device 001: ID 0000:0000  
Bus 005 Device 001: ID 0000:0000  
Bus 006 Device 001: ID 0000:0000  
Bus 004 Device 001: ID 0000:0000  
Bus 003 Device 001: ID 0000:0000  
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 001: ID 0000:0000  




Best regards,
Loïc Didelot.


On Wed, 2009-08-26 at 22:57 +0200, F6HQZ wrote:
> Mmh.. 
> Moving the card into another slot, disabling all unused interfaces (parallel, USB, COM, second ATA controler, etc...) and hope that the BIOS will reattribute hte IRQ with more chance, sometimes the BIOS authorize to move the IRQ assignement manualy or to reserve some (trick and see), sometimes it's possible through some dip switches on the mother board, sometimes nothing todo except to change the MoBo...
> 
> Good luck !
> Francois
> 
> -----Message d'origine-----
> De : Loic Didelot [mailto:ldidelot at mixvoip.com]
> Envoyé : mercredi 26 août 2009 12:49
> À : f6hqz-m at hamwlan.net; Asterisk Users Mailing List - Non-Commercial
> Discussion
> Objet : Re: [asterisk-users] PRI worked fine for months, nowit stopps
> working after 2-3 hours
> 
> 
> Hello,
> seems that the IRQ is shared. How can I change this? What would be the
> best way to move it to a dedicated IRQ?
> 
> Loïc.
> Analyse effectuée par AVG - www.avg.fr 
> Version: 8.5.375 / Base de données virale: 270.13.67/2326 - Date: 08/25/09 18:07:00
> 
> 
-- 
Loïc DIDELOT
MIXvoip S.a.
Tel: +352 20 3333 20
Fax: +352 20 3333 90
ldidelot at mixvoip.com
http://www.mixvoip.com