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
| ||
|
Date: Thu, 7 Dec 2006 17:31:33 -0500 (EST) From: Daniel Barkalow <barkalow@...ervon.org> To: gregkh@...e.de cc: Jeff Garzik <jeff@...zik.org>, Linus Torvalds <torvalds@...l.org>, linux-kernel@...r.kernel.org Subject: Disable INTx when enabling MSI Some device manufacturers seem to think it's the OS's responsibility to disable legacy interrupt delivery when using MSI. If the driver doesn't handle it (which they generally don't), and the device isn't PCI-Express, a steady stream of legacy interrupts will be delivered in addition to the MSI ones, eventually leading to the legacy IRQ getting disabled, which kills any device that shares it. Jeff proposed a patch in http://lkml.org/lkml/2006/11/21/332 when Linus wanted to do it in the PCI layer, but nobody seems to have told the actual PCI maintainer. I'm trying to get a patch into -stable to do pci_intx in exactly the same situations, but only for forcedeth (which is the device that's causing problems for me), but that requires that the real solution be merged in the mainline. -Daniel *This .sig left intentionally blank* - 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