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

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


* Vegard Nossum <vegard.nossum@...il.com> wrote:

> I receive this on a fresh install of Fedora 7 (x86_64) running 
> 2.6.21-1.3194.fc7, and wonder if it's something to worry about:
> 
> IRQ handler type mismatch for IRQ 7
> current handler: parport0

> [<ffffffff802adf6d>] request_irq+0xd7/0xfd
> [<ffffffff8039a583>] serial8250_startup+0x423/0x56f

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.

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