On Tue, Dec 02, 2008 at 09:52:09PM +0100, Jiri Slaby wrote: > Hi, > > is this dmesg snippet correct? Which kernel? Which architecture? Some architectures also dump ACPI (or other) Interrupt routing table information early in the boot. > PCI: setting IRQ 2 as level-triggered Assuming x86, the above line is printed by eisa_set_level_irq(). (See arch/x86/pci/irq.c) A function called "eisa_foo" printing a "PCI:" prefix? > serial 0000:00:09.0: found PCI INT A -> IRQ 2 I can't find the code which outputs this line in current linux-2.6 source tree. I looked for "%s: found" and also looked for dev_printk() with "PCI" or "found". I suspect "2" is the APIC input line and not the linux global interrupt value (10). Again, code is probably correct but not the labeling of the output. > 0000:00:09.0: ttyS4 at I/O 0x1898 (irq = 10) is a 16550A > 0000:00:09.0: ttyS5 at I/O 0x1890 (irq = 10) is a 16550A > > This is acpi=noirq and it works fine (dev->irq is 10). Shouldn't it show and > enable IRQ 10 instead of the one found by pirq, i.e. 2 (VIA router)? Since you say it's working, it's probably enabling global interrupt 10. I agree it should be showing the same value if it's after all the architecture fix up's have been applied to the dev->irq. hth, grant > > Thanks. > -- > To unsubscribe from this list: send the line "unsubscribe linux-pci" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
