linux-kernel - Re: PCI Resource Allocation Error

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]

Message-ID: <20060807175511.GB7868@kroah.com>
Date:	Mon, 7 Aug 2006 10:55:11 -0700
From:	Greg KH <greg@...ah.com>
To:	"D. Hazelton" <dhazelton@...er.net>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: PCI Resource Allocation Error

On Mon, Aug 07, 2006 at 10:34:27AM -0400, D. Hazelton wrote:
> After using 2.6.8 and 2.6.11 for a *long* time I decided to upgrade. When I 
> first tried using 2.6.15 I tested a vanilla kernel and ran into the following 
> message in the dmesg:
> 
> PCI: Failed to allocate mem resource #6:20000@...00000 for 0000:01:00.0
> 
> Since I'm running FC4 I figured that a fix might have made it into the distro 
> supplied kernel, so I again upgraded, this time to 2.6.17-1.2142_FC4. I see 
> the same message in the dmesg output, so I'm certain that it hasn't been 
> fixed.
> 
> This is definately caused by my graphics card, an  NVidia GeForce 5200, just 
> because that's the PCI ID of the AGP port.
> 
> I know a lot of you will tell me to file a report with RedHat, but after 
> checking the LKML archives I see this problem was introduced around 2.6.13 
> and though I saw some patches to fix this, I'm pretty certain they were 
> either for x86-64 or were not ever merged.

Even with this message, does the hardware still work properly?

thanks,

greg k-h
-
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/