| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <Pine.LNX.4.61.0709181028270.6702@chaos.analogic.com> Date: Tue, 18 Sep 2007 10:34:55 -0400 From: "linux-os \(Dick Johnson\)" <linux-os@...logic.com> To: <Duncan.Perrett@...kta.com> Cc: "Linux kernel" <linux-kernel@...r.kernel.org> Subject: Re: PCI Interrupt On Tue, 18 Sep 2007 Duncan.Perrett@...kta.com wrote: > The driver already does that ... > > result = > request_irq(irq, can_pci_interrupt, SA_INTERRUPT | SA_SHIRQ, > pDevice->au8IrqName, pDevice); > > > Any other ideas? > > Duncan > > > "linux-os \(Dick > Johnson\)" > <linux-os@...logi To > c.com> <Duncan.Perrett@...kta.com> > cc > 18/09/2007 14:57 "Linux kernel" > <linux-kernel@...r.kernel.org> > Subject > Please respond to Re: PCI Interrupt > "linux-os \(Dick > Johnson\)" > <linux-os@...logi > c.com> > > On Tue, 18 Sep 2007 Duncan.Perrett@...kta.com wrote: > >> >> I have a CAN PCI card installed on my Ubuntu box. >> I understand that PCI interrupts should be level rather than edge >> triggered. >> >> The output of cat /proc/interrupts is :- >> >> CPU0 >> 0: 1614601 IO-APIC-edge timer >> 1: 164 IO-APIC-edge i8042 >> 8: 3 IO-APIC-edge rtc >> 9: 1 IO-APIC-level acpi >> 12: 0 IO-APIC-edge CAN-ACx-PCI_01 >> 14: 65786 IO-APIC-edge ide0 >> 169: 3220 IO-APIC-level eth0, i915@pci:0000:00:02.0 >> 177: 46459 IO-APIC-level eth1 >> 209: 0 IO-APIC-level uhci_hcd:usb3, eth2 >> 217: 2 IO-APIC-level uhci_hcd:usb1, ehci_hcd:usb4 >> 225: 697 IO-APIC-level uhci_hcd:usb2 >> NMI: 0 >> LOC: 1614399 >> ERR: 0 >> MIS: 0 >> >> You see that irq 12 CAN-ACx-PCI_01 is edge triggered. >> Is there any way of forcing the BIOS to see the interrupt as a >> level-triggered one? > > It's done in the driver. IRQ12 can be shared, so the driver > needs to request the IRQ as a shared interrupt. > > > Cheers, > Dick Johnson > Penguin : Linux version 2.6.22.1 on an i686 machine (5588.30 BogoMips). > My book : http://www.AbominableFirebug.com/ > _ Okay, then in the BIOS, make sure that IRQ12 is not assigned to a specific device. In other words, set it to PnP (if available). As you well know, PCI requires sharable interrupts and edges are not sharable so something is broken. As a last resort, move your PCI board to abother slot which should pick up another interrupt, which may not be broken. If that doesn't work, see if a new BIOS is available for download. Cheers, Dick Johnson Penguin : Linux version 2.6.22.1 on an i686 machine (5588.30 BogoMips). My book : http://www.AbominableFirebug.com/ _ **************************************************************** The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@...logic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them. Thank you. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists