linux-kernel - Re: a7839e96 (PNP: increase max resources) breaks my ALSA intel8x0 sound card

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: <alpine.LFD.1.00.0801280841440.4544@www.l.google.com>
Date:	Mon, 28 Jan 2008 08:50:24 +1100 (EST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Avuton Olrich <avuton@...il.com>
cc:	Zhao Yakui <yakui.zhao@...el.com>,
	Li Shaohua <shaohua.li@...el.com>,
	Bjorn Helgaas <bjorn.helgaas@...com>,
	Thomas Renninger <trenn@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Linux-Kernel," <linux-kernel@...r.kernel.org>,
	Alsa-Devel <alsa-devel@...a-project.org>
Subject: Re: a7839e96 (PNP: increase max resources) breaks my ALSA intel8x0
 sound card

On Sun, 27 Jan 2008, Avuton Olrich wrote:
>
> With v2.6.24 my second ALSA sound device stopped working.

Hmm. Why is PnP ACPI called before PCI probing? That seems to be the 
problem here - we should *never* have any firmware allocation block known 
hardware BARs, they should only be blocking new dynamic allocations.

Hmm. I wonder if the problem is that ACPIPnP marks the regions busy. That 
would be wrong. They shouldn't be busy, they should just "exist".

A busy region will stop a "request_region()" (incorrect for this case - 
thats' not what the PnP resurce allocation should be all about), but an 
*existing* resource will just stop a new resource being dynamically 
assigned to that address (not not stop a known resource from using it).

So maybe the ACPIPnP allocation is doen at the right moment, just doing 
the wrong thing..

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