RE: PCI bridges & interrupts

From: John Baldwin (jhb_at_FreeBSD.org)
Date: 09/25/03

  • Next message: John Baldwin: "Re: PCI bridges & interrupts"
    Date: Wed, 24 Sep 2003 18:17:13 -0400 (EDT)
    To: (Steve Watt) <steve@Watt.COM>
    
    

    On 24-Sep-2003 Steve Watt wrote:
    > On Sep 24, 16:38, John Baldwin wrote:
    > } Subject: RE: PCI bridges & interrupts
    >
    > And if I were clever, I would've mentioned that it's in the
    > same slot. And the IRQ that gets assigned (by reading the
    > dmesg, as well as reading out the register from config space)
    > is the same.

    Across bridges the interrupts get swizzled sort of. Which means
    that device 0,4,8,etc. INT A gets mapped to INT A on the front
    side of the bridge, device 1,5,7,etc. INT A gets mapped to INT B.
    etc. IIRC your device is at device 5.0, so it's INT A should be
    mapped to INT B of that slot, which should get a different interrupt.

    > } > What follows is the verbose dmesg from the boot up without the
    > } > riser (bridge), followed by diffs when booted with the riser.
    > } >
    > } > I'm looking for clues. It's about >< that far from working right,
    > } > and this almost looks like a FreeBSD issue.
    > } >
    > } > Buddy, can you spare a clue? Why isn't the ISR running?
    > }
    > } Have you tried 5.x? Basically, 4.x doesn't really have all the
    > } infrastructure to route interrupts, and if your BIOS screws it up,
    > } then you aren't going to get the right IRQ number hooked up.
    >
    > If the BIOS is screwing it up, it's somehow in the configuration
    > of the interrupt controller, which I thought was completely
    > owned by the OS.

    No, the BIOS sets it up and we may try to tweak it. In 5.x we
    fully tweak it now, but 4.x still relies on the BIOS to set this
    up.

    -- 
    John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
    "Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
    

  • Next message: John Baldwin: "Re: PCI bridges & interrupts"

    Relevant Pages

    • [patch 13/33] xen: xen event channels
      ... Xen implements interrupts in terms of event channels. ... it is mapped to an irq and sent ... +static inline unsigned int evtchn_from_irq ...
      (Linux-Kernel)
    • [PATCH 01/10] powerpc: Remove use of CONFIG_PPC_MERGE
      ... This option will show the mapping relationship between hardware irq ... extern int tau_interrupts; ... IRQ controller and virtual interrupts ... *, DMA controller, and JTAG controller. ...
      (Linux-Kernel)
    • RE: [PATCH] Early USB handoff
      ... and USB IRQ is routed to PCI IRQ line and generates ... system is flooded with interrupts. ... >The BIOS should not be leaving the device generating ...
      (Linux-Kernel)
    • Re: [Linux-usb-users] irq XX: nobody cared! and uhci_hcd
      ... > the IRQ for those devices is disabled because nobody cared: ... Some other device is generated interrupts on the same IRQ line, ... sure that Legacy USB Support is disabled in the BIOS. ...
      (Linux-Kernel)
    • [patch 07/32] xen: xen event channels
      ... Xen implements interrupts in terms of event channels. ... it is mapped to an irq and sent ... +static inline unsigned int evtchn_from_irq ...
      (Linux-Kernel)