Re: 5 devices sharing one irq



with usb devices I not having problems, I'm having them with my
monitor, and as I didn't find the problem yet, I thought if this could
be interfering.....

Also note that these are almost certainly PCI devices, even if they're
on-board USB ports. The PCI interface isn't limited to PCI slots! If
'lspci | grep -i uhci' shows your USB controller, then you can be sure
that it is a PCI device...meaning IRQ sharing is much less of a concern.

yes, by doing that order shows me this:


0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller (rev 81)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller (rev 81)
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller (rev 81)
0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller (rev 81)

So maybe this is not the cause my monitor is working wrong, then,

Thanks and greetins


On 21 mayo, 21:08, John-Paul Stewart <jpstew...@xxxxxxxxxxxxxxxx>
wrote:
dolc...@xxxxxxxxx wrote:
Hello everyone,

I have read an article, which tells that if you type on a shell this
order: cat /proc/interrupts
and then you see more than one device sharing one irq, and these
devices are not pci or agp, then you may be having a conflict. I did
that and I have 5 devices sharing the same irq, these ones:

17: 0 IO-APIC-level ehci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3,
uhci_hcd:usb4, uhci_hcd:usb5

is there something I can do to these devices have their own irq?

There's probably no need to worry (unless you're having problems with
USB).

It appears that you have a single 5-port USB 2.0 controller on that IRQ,
judging by the usb1-usb5 designations after uhci_hcd (a USB host
controller driver) and the ehci_hcd module (USB 2.0 support module). It
may not even be possible to have the different ports of the USB
controller on different IRQs, if they really are 5 ports on one chip (as
is my guess).

Also note that these are almost certainly PCI devices, even if they're
on-board USB ports. The PCI interface isn't limited to PCI slots! If
'lspci | grep -i uhci' shows your USB controller, then you can be sure
that it is a PCI device...meaning IRQ sharing is much less of a concern.


.



Relevant Pages

  • Re: 2.6.17-mm4 -- BUG: illegal lock usage! -- illegal {hardirq-on-W} 
    ... ACPI: bus type pci registered ... Using ACPI for IRQ routing ... usbcore: registered new driver hub ... USB Universal Host Controller Interface driver v3.0 ...
    (Linux-Kernel)
  • Re: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13
    ... ACPI: bus type pci registered ... PCI Interrupt Link enabled at IRQ 10 ... ehci_hcd 0000:00:1d.7: new USB bus registered, ... registering ipv6 mark target ...
    (Linux-Kernel)
  • Strange ATA problems
    ... PCI Interrupt Link enabled at IRQ 18 ... PCI: Setting latency timer of device 0000:02:00.0 to 64 ... usb 1-1: new high speed USB device using ehci_hcd and address 5 ... registering new adapter ...
    (Linux-Kernel)
  • Strange ATA problems
    ... PCI Interrupt Link enabled at IRQ 18 ... PCI: Setting latency timer of device 0000:02:00.0 to 64 ... usb 1-1: new high speed USB device using ehci_hcd and address 5 ... registering new adapter ...
    (Debian-User)
  • Re: [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U8
    ... and at the end one fatal crash while plugging an USB flash memory stick ... ACPI: IRQ9 SCI: Edge set to Level Trigger. ... PCI: PCI BIOS revision 2.10 entry at 0xfd88b, ... PS/2 Mouse Controller at irq 12 ...
    (Linux-Kernel)