linux-kernel - Re: pnpacpi : exceeded the max number of IO resources

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]

Date:	Fri, 30 Nov 2007 16:14:14 +0800
From:	Zhao Yakui <yakui.zhao@...el.com>
To:	Valdis.Kletnieks@...edu
Cc:	Dave Young <hidave.darkstar@...il.com>, lenb@...nel.org,
	linux-acpi@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: pnpacpi : exceeded the max number of IO resources

On Fri, 2007-11-30 at 01:40 -0500, Valdis.Kletnieks@...edu wrote:
> On Fri, 30 Nov 2007 10:21:28 +0800, Zhao Yakui said:
> > Thanks for the acpidump & dmesg.
> > 	In the acpidump there are so many IO resource definitions in the device
> > of mem2 and the number exceeds the predefined number(24).
> 
> On a semi-related note, I'm seeing 7 of these at each boot on a Dell Latitude D820:
> 
> pnpacpi: exceeded the max number of mem resources: 12
> 
> 2.6.24-rc3-mm2 does it, it didn't do it for 2.6.23-mm1.
> 
> pnp-increase-the-maximum-number-of-resources.patch raised it from 4 to 12, but
> I don't understand why it didn't complain at 4 in 23-mm1, but it does at 12 now.
In the 23-mm1 there is no such debug info. When the number of mem
resource (for one Pnp device) defined by BIOS exceeds the predefined
constant, the mem resource can't be added. But it won't report this
case. 
In the 24-mm2 the PnP constant is raised and the debug info is added.
When the number exceeds the predifined constant, it will give the debug
info. 

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