linux-kernel - Re: PCIE

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46561287.8020103@gmail.com>
Date:	Fri, 25 May 2007 02:32:39 +0400
From:	Manu Abraham <abraham.manu@...il.com>
To:	Roland Dreier <rdreier@...co.com>
CC:	Greg KH <greg@...ah.com>, linux-pci@...ey.karlin.mff.cuni.cz,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: PCIE

Roland Dreier wrote:

> Why does the device come up in a state where it generates a stream of
> interrupts as soon as you enable the PCI device?  That's somewhat
> unusual behavior, although certainly not unheard of.
> 

In fact the device wasn't generating a stream of interrupts when loaded
(i guess). It was just that the shared handler was showing all the
interrupts that occurred, since i was not looking at the interrupt
mask/status.

But accessing any registers caused me a flood of interrupts, which froze
the system. excessive printing to the console caused a lockup.

I am now wondering whether the usage of MSI would help in this case and
that i should be using enable_msi before request_irq ?

-
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/