Messages in this thread | | | Date | Sat, 28 Jan 2006 09:02:41 +0800 | From | "Antonino A. Daplas" <> | Subject | Re: vesa fb is slow on 2.6.15.1 |
| |
Hai Zaar wrote: > On 1/28/06, Antonino A. Daplas <adaplas@gmail.com> wrote: >> Hai Zaar wrote: >>>> Looks harmless to me. >>>> >>>> Can you check /proc/iomem just to verify if that particular address has >>>> been reserved by the OS. >>> Relevant iomem entries are: >>> f0000000-f7ffffff : PCI Bus #40 >>> f0000000-f7ffffff : 0000:40:00.0 >>> f0000000-f7ffffff : vesafb >>> f8000000-f9ffffff : PCI Bus #40 >>> f8000000-f8ffffff : 0000:40:00.0 >>> f9000000-f9ffffff : 0000:40:00.0 >>> After I load nvidia.ko, it changes to: >>> f0000000-f7ffffff : PCI Bus #40 >>> f0000000-f7ffffff : 0000:40:00.0 >>> f0000000-f7ffffff : vesafb >>> f8000000-f9ffffff : PCI Bus #40 >>> f8000000-f8ffffff : 0000:40:00.0 >> ^^^^^^^^ >> Yes, this address range (16M) is already allocated to resource #0 >> of the nvidia card. So trying to allocate resource #6 on the same >> address looks bogus to me. > > Ok. What now?
Well, it looks to me like a harmless message and I'll just ignore it, I think, as long as the affected pci device works properly.
> I've rebooted without 'vga' and 'video' parameters at all - the error stays. > > BTW: How do you know that its allocated to resource #0 - are resource > numbers written somewhere in /proc/iomem and I've missed it?
This was part of your lspci:
Region 0: Memory at f8000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at f0000000 (64-bit, prefetchable) [size=128M] Region 3: Memory at f9000000 (64-bit, non-prefetchable) [size=16M]
See region 0.
Tony - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |