Re: 2.6.28-rc2 hates my e1000e

From: Yinghai Lu
Date: Sat Nov 01 2008 - 15:50:38 EST


On Sat, Nov 1, 2008 at 10:16 AM, Linus Torvalds
<torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
>
>
>> e0000000-fe7fffff : reserved
>> fe800000-fe8fffff : PCI Bus 0000:01
>> fe800000-fe8fffff : reserved
>> fe900000-fe9d9aff : reserved
>> fe9d9b00-fe9d9bff : 0000:00:1f.3
>> fe9d9b00-fe9d9bff : reserved
>> fe9d9c00-fe9d9fff : 0000:00:1a.7
>> fe9d9c00-fe9d9fff : reserved
>> fe9da000-fe9dafff : 0000:00:03.3
>> fe9da000-fe9dafff : reserved
>> fe9db000-fe9dbfff : 0000:00:19.0
>> fe9db000-fe9dbfff : reserved
>> fe9dc000-fe9dffff : 0000:00:1b.0
>> fe9dc000-fe9dffff : reserved
>> fe9e0000-fe9fffff : 0000:00:19.0
>> fe9e0000-fe9fffff : reserved
>> fea00000-fea7ffff : 0000:00:02.0
>> fea00000-fea7ffff : reserved
>> fea80000-feafffff : 0000:00:02.1
>> fea80000-feafffff : reserved
>> feb00000-febfffff : 0000:00:02.0
>> feb00000-febfffff : reserved
>> fec00000-fed003ff : reserved
>> fec00000-fec00fff : IOAPIC 0
>> fed00000-fed003ff : HPET 0
>
> .. which is just really messy, but is the same e0000000-fed003ff
> "reserved" e820 entry just split and moved into each resource.
>
> I hate firmware.

Jonathan, can you try patch i sent?

http://lkml.org/lkml/2008/10/31/274
[PATCH] x86: remove PCI bar range from e820 reserved entries

Impact: clean up buggy e820 tables

so make those ranges can be claimed by drivers
acctually BIOS is not supposed to put resource in pci BAR in reserved
entries of e820.
e820 entries should only include reserved range include mmconfig,
lapic, ... and others
that are not in BARs



the magic regions like gart, mmconfig, ioapic, lapic and others who
knows, should be really reserved.

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/