[lkml]   [2001]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Possible PCI subsystem bug in 2.4

On Thu, 3 May 2001, Edward Spidre wrote:
> Note: a diff between booting with mem and without it
> yield the same results (the user-defined phys ram map
> is identical to the bios provided one)

Interesting. Your BIOS-provided memory map is buggy:

> BIOS-provided physical RAM map:
> BIOS-e820: 000000000009fc00 @ 0000000000000000 (usable)
> BIOS-e820: 0000000000000400 @ 000000000009fc00 (reserved)
> BIOS-e820: 000000000000c000 @ 00000000000c0000 (reserved)
> BIOS-e820: 0000000013eec000 @ 0000000000100000 (usable)
> BIOS-e820: 0000000000004000 @ 0000000013fec000 (reserved)
> BIOS-e820: 0000000000200000 @ 00000000ffe00000 (reserved)

Note how it says that you have usable RAM from

0000000000100000 - 0000000013fec000

(the thing is hard to read and the output was changed in later kernels: it
really says that you have 0000000013eec000 bytes of ram starting at
0000000000100000, which obviously doing the math means that it goes up to

Now, it then says that you have reserved memory (ie probably the BIOS has
reserved 1kB at high memory) from

0000000013fec000 - 0000000013ff0000

In particular, notice how it does NOT mention the memory region from

0000000013ff0000 - 0000000014000000

at ALL. Which means that Linux thinks that it is free... And Linux will
place PCI devices there. Even though there certainly is memory there.

I'll have to work around the BIOS bug some way. Will you be willing to
try out patches?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.099 / U:1.544 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site