search for: intx

...linux disables MSI > > which then causes an "irq %d: nobody cared" message, with irq being > > subsequently disabled. > > My understanding is: > > Linux disables MSI/MSI-X during device shutdown. If the device > signals an interrupt after that, it may use INTx. > > This INTx interrupt is not necessarily spurious. Using INTx to signal an > interrupt that occurs when MSI is disabled seems like reasonable behavior > for any PCI device. > And it doesn't seem related to switching between MSI and non-MSI mode. > Yes, the INTx happens *a...

...linux disables MSI > > which then causes an "irq %d: nobody cared" message, with irq being > > subsequently disabled. > > My understanding is: > > Linux disables MSI/MSI-X during device shutdown. If the device > signals an interrupt after that, it may use INTx. > > This INTx interrupt is not necessarily spurious. Using INTx to signal an > interrupt that occurs when MSI is disabled seems like reasonable behavior > for any PCI device. > And it doesn't seem related to switching between MSI and non-MSI mode. > Yes, the INTx happens *a...

...%d: nobody cared" message, with irq being > > > > subsequently disabled. > > > > > > My understanding is: > > > > > > Linux disables MSI/MSI-X during device shutdown. If the device > > > signals an interrupt after that, it may use INTx. > > > > > > This INTx interrupt is not necessarily spurious. Using INTx to signal an > > > interrupt that occurs when MSI is disabled seems like reasonable behavior > > > for any PCI device. > > > And it doesn't seem related to switching between M...

...%d: nobody cared" message, with irq being > > > > subsequently disabled. > > > > > > My understanding is: > > > > > > Linux disables MSI/MSI-X during device shutdown. If the device > > > signals an interrupt after that, it may use INTx. > > > > > > This INTx interrupt is not necessarily spurious. Using INTx to signal an > > > interrupt that occurs when MSI is disabled seems like reasonable behavior > > > for any PCI device. > > > And it doesn't seem related to switching between M...

Hello! I have something like this: test1 <- data.frame(intx=c(4,3,1,1,2,2,3), status=c(1,1,1,0,1,1,0), x1=c(0,2,1,1,1,0,0), x2=c(1,1,0,0,2,2,0), sex=c(0,0,0,0,1,1,1)) and I can easily fit a cox model: library(survival) coxph(Surv(intx,status) ~ x1 + x2 + st...

..., with irq being > > > > > subsequently disabled. > > > > > > > > My understanding is: > > > > > > > > Linux disables MSI/MSI-X during device shutdown. If the device > > > > signals an interrupt after that, it may use INTx. > > > > > > > > This INTx interrupt is not necessarily spurious. Using INTx to signal an > > > > interrupt that occurs when MSI is disabled seems like reasonable behavior > > > > for any PCI device. > > > > And it doesn't seem relat...

...cards 2. Boot! 3. Actual results: Expected results: Additional info: lspci -vvv: 00:00.0 Host bridge: Intel Corporation 82975X Memory Controller Hub Subsystem: Hewlett-Packard Company Device 280c Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort+ <MAbort+ >SERR- <PERR- INTx- Latency: 0 Capabilities: <access denied> Kernel driver in use: i82975x_edac Kernel modules: i82975x_edac 00:01.0 PCI bridge: Intel Corporation 82975X PCI Express Root Por...

...hich then causes an "irq %d: nobody cared" message, with irq being > > > subsequently disabled. > > > > My understanding is: > > > > Linux disables MSI/MSI-X during device shutdown. If the device > > signals an interrupt after that, it may use INTx. > > > > This INTx interrupt is not necessarily spurious. Using INTx to signal an > > interrupt that occurs when MSI is disabled seems like reasonable behavior > > for any PCI device. > > And it doesn't seem related to switching between MSI and non-MSI mode. >...

...; > > > subsequently disabled. > > > > > > > > > > My understanding is: > > > > > > > > > > Linux disables MSI/MSI-X during device shutdown. If the device > > > > > signals an interrupt after that, it may use INTx. > > > > > > > > > > This INTx interrupt is not necessarily spurious. Using INTx to signal an > > > > > interrupt that occurs when MSI is disabled seems like reasonable behavior > > > > > for any PCI device. > > > > > And...

...; > > > subsequently disabled. > > > > > > > > > > My understanding is: > > > > > > > > > > Linux disables MSI/MSI-X during device shutdown. If the device > > > > > signals an interrupt after that, it may use INTx. > > > > > > > > > > This INTx interrupt is not necessarily spurious. Using INTx to signal an > > > > > interrupt that occurs when MSI is disabled seems like reasonable behavior > > > > > for any PCI device. > > > > > And...

...rmation ('lspci -vvv' as root) > TEST-MAIL1 ~ # lspci -vvv > 00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 22) > Subsystem: IBM Device 7270 > Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- > ParErr+ Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast > >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Interrupt: pin A routed to IRQ 11 > Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit- > Address: 00000020 Data: 000...

This fixes a few things that I missed in previous patches: * Use the hw INTX rather than INTA in pt_reset_interrupt_and_io_mapping() This is consistent with other uses of pci_intx() * Remove now inaccurate "/* fix virtual interrupt pin to INTA# */" comments * Use PCI_SLOT() Signed-off-by: Simon Horman <horms@verge.net.au> Index: ioemu-remote/hw/pass-thro...

Hi, I saw that Xen support a translation between device/intx to GSI for a single PCI bus, I thought about adding multiple PCI bus support but disregard the bus information so the same device/intx on different buses will be OR wired to the same GSI, sounds reasonable? What other things do I need to support in Xen in order to add multiple PCI buses, assuming t...

...o do with delaying the start of libvirtd in systemd until the PCI card (or vfio?) is ready, but I don’t know how to do that. Can anyone else offer assistance? My output: 2016-03-29T18:29:26.191010Z qemu-kvm: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x7: vfio: Error: Failed to setup INTx fd: Device or resource busy 2016-03-29T18:29:26.289154Z qemu-kvm: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x7: Device initialization failed. 2016-03-29T18:29:26.289195Z qemu-kvm: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x7: Device 'vfio-pci' could not be in...

Is there anything I can do in this regard? /smo On 2016-03-31 23:12, Pierre Moreau wrote: > Oh, hum, GM108 is NV118 and not NV108 which is Gk208… My bad! > > SMF from the bug report seemed to have some working setup, and since he didn't > pinged back, I guess it's working nicely. But some more checking might still be > needed? > > On 04:59 PM - Mar 31 2016, Ilia

...ssed through to the VM, the error seems to relate to that. The error that always appears at boot in `/var/log/libvirt/qemu/test-vm.log` is: > 2016-01-11T05:29:28.487935Z qemu-system-x86_64: -device > vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x4: vfio: Error: > Failed to setup INTx fd: Device or resource busy > 2016-01-11T05:29:28.488148Z qemu-system-x86_64: -device > vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x4: Device > initialization failed > 2016-01-11T05:29:28.488169Z qemu-system-x86_64: -device > vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr...

...just installed CentOS 4.4 x86_64 on our new 2 x Dual Core Opteron Server. First the system was unstable, but I after turning of Power-now it runs stable (anyone else experienced this?). However the following line in dmesg puzzles me: tg3: eth0: No interrupt was generated using MSI, switching to INTx mode. Please report this failure to the PCI maintainer and include system chipset information. Has someone else experienced this? What does it mean and who am I supposed to contact? Sorry if this is a stupid question, but a simple pointer would be appreciated. Apart from this message the syst...

...====================== teo-en-ming@intel-core-i5-4430-desktop:~$ lspci -vvv 00:00.0 Host bridge: Intel Corporation Haswell DRAM Controller (rev 06) Subsystem: ASRock Incorporation Device 0c00 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx- Latency: 0 Capabilities: <access denied> 00:01.0 PCI bridge: Intel Corporation Haswell PCI Express x16 Controller (rev 06) (prog-if 00 [Normal decode]) C...

...all is well, but during shutdown, linux disables MSI > which then causes an "irq %d: nobody cared" message, with irq being > subsequently disabled. My understanding is: Linux disables MSI/MSI-X during device shutdown. If the device signals an interrupt after that, it may use INTx. This INTx interrupt is not necessarily spurious. Using INTx to signal an interrupt that occurs when MSI is disabled seems like reasonable behavior for any PCI device. And it doesn't seem related to switching between MSI and non-MSI mode. Yes, the INTx happens *after* disabling MSI, but it i...

...inline 3.5-rc6 kernel and yesterday''s xen-unstable, I''m having trouble passing in some PCI devices. Everything else works smoothly. Attached are some of the relevant logs and configurations. I did notice from the qemu logs that all the problematic devices have "IRQ type = INTx" whereas those that are working have "IRQ type = MSI-INTx". On the domU side, Windows reports that the devices cannot start and Ubuntu complained something along the lines of "Invalid USB capability 0xFF" (for the USB controller I was passing through). Kernel versi...