similar to: Changing IRQ

I am running Asterisk 1.16.2.13, dahdi 2.4.0 and libpri 1.4.11.4 on an HP ML110 G6 using Ubuntu Linux 10.04 LTS. I have two Digium TE121 single T1 port cards and a Digium AEX800 8-port FXS card. All PCI Express cards. Co-workers are hearing hissing sounds on some calls, and I am getting IRQ errors when running "dahdi show status". I see that sharing IRQs for Digium cards isn't

Hello, We have built a couple of CentOS 5.5 systems on the Intel DH67BL (Sandy Bridge) motherboard and overall they work pretty well. I'm having one problem which keeps cropping up and that is an error message that says: IRQ 177 nobody cared (try booting with the irqpoll option) report bad irq, references CPU idle then it references usb_hcd_irq and e1000_intr then it disables the add-on

Hello, I had noticed strange crackling sound on my phone calls going through my zaptel device (TDM400P), so i decided to check on possible timer issue, and found lots of issues on forums concerning the sensibility of zaptel with IRQs, and tried about everything: moving PCI slots, noapic and acpi=off boot options, play with different kernel options: iosched/preemption/timer/..., play with

Hi folks.. just a few weeks ago I wrote this to someone else: ------------------------ We have several 2900s in production as VoIP servers.. no lockups. On every server I go into the BIOS and: * Disable USB * Disabled uneeded things like Parallel, Serial * Put ETH0 on a seperate IRQ from the Digium card And everything's fine. Dell's do NOT have to share IRQs... go into your BIOS and

define api for allocating/setting up msi-x irqs, and for updating them with msi-x vector information, supply implementation in ioapic. Please comment on this API: I intend to port my msi-x patch to work on top of it. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- hw/apic.c | 1 - hw/ioapic.c | 65 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/irq.c

define api for allocating/setting up msi-x irqs, and for updating them with msi-x vector information, supply implementation in ioapic. Please comment on this API: I intend to port my msi-x patch to work on top of it. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- hw/apic.c | 1 - hw/ioapic.c | 65 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/irq.c

I have installed two 4-port serial cards (http://www.startech.com/ Product/ItemDetail.aspx?productid=PCI4S550&c=US) on a CentOS 4.4 system. The hardware appears to be recognized correctly, as kudzu added 2 entries to /etc/sysconfig/hwconf and lscpi shows both cards (output of lspci -vv for both cards included at the end of this email): # lspci 00:00.0 Host bridge: Intel Corporation

For a while we've been having issues with seemingly random interrupts coming from nvidia cards when resuming them. Originally the fix for this was thought to be just re-arming the MSI interrupt registers right after re-allocating our IRQs, however it seems a lot of what we do is both wrong and not even nessecary. This was made apparent by what appeared to be a regression in the mainline

Hi, is it possible to set a wcte11xp card to use a certain IRQ? I've tried a few things but it always shares the IRQ with eth0 even though the system has 4 spare ones. I can't set it via the BIOS. Regards Lee -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050902/9ce217db/attachment.htm

As the current virtio-mmio only support single irq, so some advanced features such as vhost-net with irqfd are not supported. And the net performance is not the best without vhost-net and irqfd supporting. This patch support virtio-mmio to request multiple irqs like virtio-pci. With this patch and qemu assigning multiple irqs for virtio-mmio device, it's ok to use vhost-net with irqfd on

As the current virtio-mmio only support single irq, so some advanced features such as vhost-net with irqfd are not supported. And the net performance is not the best without vhost-net and irqfd supporting. This patch support virtio-mmio to request multiple irqs like virtio-pci. With this patch and qemu assigning multiple irqs for virtio-mmio device, it's ok to use vhost-net with irqfd on

Hi all! After upgrading to Squeeze, I am watching a Xen VMHost that after a while it hangs. This did not happen when I was using Xen with Debian Lenny (in this case as with Squeeze, the Xen components are from Debian repositories). In each case I connected a keyboard and monitor to the computer and the screen remained black without answering any key. This problem seems to also affect domUs,

Dne 17.9.2019 v 14:02 Mauricio Tavares napsal(a): > On Tue, Sep 17, 2019 at 7:06 AM Miroslav Geisselreiter <mg at intar.cz> wrote: >> I have brand new PC with this components: >> CPU Intel? Pentium G5400, LGA1151 >> motherboard ASUS PRIME B360M-C >> 16 GB RAM >> HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) >> NIC Intel X550-T1

Hi, On a (bogus) system equiped with a Digium HA8 and 8 BRI ports, I'm reading this: # asterisk -rx "dahdi show status" Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO HA8-0000 RED 109 0 0 CCS AMI YEL 0 db (CSU)/0-133 feet (DSX-1) HA8-0000 UNCONFI 109 0

Hi, Thanks to everyone involved in the Xen project. I think it is great and can''t wait to get my hands dirty with it. In the meantime, I cannot boot Dom0 on an ibm x335 and I am not sure what the problem is. Any insights are welcome. Here is what my grub.conf file looks like: title Fedora Core (2.6.8-1.521) root (hd0,0) kernel /vmlinuz-2.6.8-1.521 ro root=/dev/sda9

On 2014/7/29 22:08, Arnd Bergmann wrote: > On Saturday 26 July 2014 11:08:37 Yijing Wang wrote: >> The series is a draft of generic MSI driver that supports PCI >> and Non-PCI device which have MSI capability. If you're not interested >> it, sorry for the noise. > > I've finally managed to take some time to look at the series. Overall, > the concept

On 2014/7/29 22:08, Arnd Bergmann wrote: > On Saturday 26 July 2014 11:08:37 Yijing Wang wrote: >> The series is a draft of generic MSI driver that supports PCI >> and Non-PCI device which have MSI capability. If you're not interested >> it, sorry for the noise. > > I've finally managed to take some time to look at the series. Overall, > the concept

Dear Sirs. It seems to me a never ending story. We run a box with a TYAN Thunder 2500 Dual SMP mainboard, 2GB ECC Tyan certified memory, AMI Enterprise 1600 RAID adapter and additional Intel 1000/Pro server type (64 bit) GBit LAN NIC. With FreeBSD 4.8 this was stable, but to achive this state was really hard! It is a story similar to that what happend when we changed towards FreeBSD

On 2014/11/11 23:11, Pawel Moll wrote: > On Tue, 2014-11-04 at 09:35 +0000, Shannon Zhao wrote: >> As the current virtio-mmio only support single irq, >> so some advanced features such as vhost-net with irqfd >> are not supported. And the net performance is not >> the best without vhost-net and irqfd supporting. > > Could you, please, help understanding me where

On 2014/11/11 23:11, Pawel Moll wrote: > On Tue, 2014-11-04 at 09:35 +0000, Shannon Zhao wrote: >> As the current virtio-mmio only support single irq, >> so some advanced features such as vhost-net with irqfd >> are not supported. And the net performance is not >> the best without vhost-net and irqfd supporting. > > Could you, please, help understanding me where