linux-kernel - Re: IRQ handler type mismatch for IRQ 7

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] [day] [month] [year] [list]

Message-ID: <19f34abd0706110619i7cf011d5x340b65dcf94f3365@mail.gmail.com>
Date:	Mon, 11 Jun 2007 15:19:32 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org,
	"Thomas Gleixner" <tglx@...utronix.de>
Subject: Re: IRQ handler type mismatch for IRQ 7

On 6/11/07, Ingo Molnar <mingo@...e.hu> wrote:
> so both parport and serial is on the same IRQ: #7, but the parport one
> does not support shared interrupt lines (IRQF_SHARED). You can probably
> change the mapping in the BIOS (change the serial one to say IRQ#3 or
> IRQ#4). I suspect you dont have any real parallel port hardware
> attached? (and probably no serial port hardware either?) So you can
> safely ignore this.

Correct, there is neither serial nor parport hardware here. Thanks for
your help!

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