linux-kernel - Re: [bisected][resend] pnp: Huge number of "io resource overlap" messages

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: <200809101534.27688.bjorn.helgaas@hp.com>
Date:	Wed, 10 Sep 2008 15:34:27 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Frans Pop <elendil@...net.nl>
Cc:	linux-kernel@...r.kernel.org, Rene Herman <rene.herman@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Matthew Wilcox <matthew@....cx>
Subject: Re: [bisected][resend] pnp: Huge number of "io resource overlap" messages

On Wednesday 10 September 2008 01:39:15 am Frans Pop wrote:
> On Tuesday 09 September 2008, Bjorn Helgaas wrote:
> > If the PCI device isn't fully initialized, it doesn't seem right to
> > check it for resource conflicts.  But I don't know how to tell that.
> >
> > Can you figure out where the 1f.5 and 1f.6 resources get assigned?
> 
> If the approach suggested by Rene feasible or would you still like me to 
> get this info? In the last case I'll need some pointers where exactly to 
> look.

Checking pci_resource_start() for zero would certainly work
in your particular case.  But I don't know enough about PCI to
know whether that's always safe.

Matthew Wilcox suggested that the BARs may be zero because the BIOS
has "disabled" those two devices.  Are there any BIOS setup options
related to them?  I know you need to use at least the sound device,
so I'm not suggesting that Linux should leave it disabled;  I'm just
trying to learn more about the situation.

If I were trying to figure out where we assign resources, I'd probably
boot with "pci=earlydump" and sprinkle calls to early_dump_pci_device()
in pcibios_resource_survey(), and drill down from there.

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