Re: I think I found cause of severe data corruption on 2.3.24-ikd -- memory detection

Pavel Machek (pavel@suse.cz)
Fri, 5 Nov 1999 18:56:58 +0100


Hi!

> Okay. My wetware has been a bit overloaded of late. You observe from the
> listing that you have a reserved space from 3ff0000 to 4000000, which is the
> 64k just below the 64M boundary (the ACPI memory is available for reclaim.)
> mem=0x3ff0000 should give you the most possible memory.
>
>
> What I don't understand--what I STILL don't understand, is why you need a
> command line option at all. The routines to initialize this memory should
> work just fine
> without any help.

Ok, I found out. Mingo's patch gives error at e8000. That's somewhere
below 1MB. It seems toshiba messed up their tables, grr.

Pavel

> <4>Linux version 2.3.24 (pavel@bug) (gcc version 2.7.2.3) #389 Fri Oct 29
> 00:29:44 CEST 1999
> <4>e820: 0009fc00 @ 00000000 (usable)
> <4>e820: 00000400 @ 0009fc00 (reserved)
> <4>e820: 00004000 @ 000e8000 (usable)
> <4>e820: 00010000 @ 000f0000 (reserved)
> <4>e820: 03ee0000 @ 00100000 (usable)
> <4>e820: 00010000 @ 03fe0000 (ACPI data)
> <4>e820: 00010000 @ 03ff0000 (reserved)
> <4>e820: 00016e00 @ 100a0000 (reserved)
> <4>e820: 00000200 @ 100b6e00 type 4
> <4>e820: 00049000 @ 100b7000 (reserved)
> <4>e820: 00080000 @ fff80000 (reserved)
> <4>Initializing CPU#0
> <4>Detected 299943970 Hz processor.
> <4>Console: colour dummy device 80x25
> <4>Calibrating delay loop... 299.01 BogoMIPS
> <4>Memory: 60748k/64512k available (0k kernel code, 0k reserved, 0k data, 0k
> init, 0k highmem)

-- 
I'm really pavel@ucw.cz. Look at http://195.113.31.123/~pavel.  Pavel
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!

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