linux-kernel - Re: 2.6.20 "IRQ handler type mismatch for IRQ 4"

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]

Date:	Mon, 12 Feb 2007 16:51:05 +0000
From:	Alan <alan@...rguk.ukuu.org.uk>
To:	Florian Schmidt <mista.tapas@....net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.20 "IRQ handler type mismatch for IRQ 4"

> > This is all scary and generally not needed spew but handy for debug.
> >
> > Looks like a PCMCIA layer bug. It should be respecting IRQ assignment
> > (not just allocation) by other resource configuration layers.
> 
> Ah thanks for taking a look. I was slowly getting the impression from older 
> lkml posts, that this isn't really what stopped my wifi from functioning. It 
> seems there are other reasons and i just stumbled across this harmless 
> message in dmesg.. Thanks for clearing it up :)

The problem is we don't know what the PNP layer does about the routing
here. It could be breaking the wifi but it's only a possible cause. It
still shouldn't be using IRQ 4 after pnp had it.

I'm also a little suprised to see both pnp and ACPI triggering. I thought
it wasn't permitted to use both at once but that really wants asking of
an ACPI guru like Len.

Does it work if you compile out PNP bios support ?
-
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/