From: Adam Schrotenboer <ajschrotenboer@lycosmail.com>
To: "Dunlap, Randy" <randy.dunlap@intel.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] 2.4.1 Detects 64 MB RAM, actual 192MB
Date: Wed, 31 Jan 2001 21:57:37 -0500 [thread overview]
Message-ID: <3A78D0A1.9070100@lycosmail.com> (raw)
In-Reply-To: <D5E932F578EBD111AC3F00A0C96B1E6F07DBDFC7@orsmsx31.jf.intel.com>
Dunlap, Randy wrote:
>> From: Adam Schrotenboer [mailto:ajschrotenboer@lycosmail.com]
>>
>>> On Wed, 31 Jan 2001 10:01:08 -0500, Adam Schrotenboer wrote:
>>>
>>>>> On Tue, 30 Jan 2001 23:25:22 -0500, Adam Schrotenboer wrote:
>>>>>
>>>>>> ...
>>>>>> Linux version 2.4.1 (root@tabriel) (gcc version egcs-2.91.66
>>>>>
>>>> 19990314/Linux (egcs-1.1.2 release)) #9 Tue Jan 30
>>>
>> 15:35:21 EST 2001
>>
>>>>>> BIOS-provided physical RAM map:
>>>>>> BIOS-88: 000000000009f000 @ 0000000000000000 (usable)
>>>>>> BIOS-88: 0000000003ff0000 @ 0000000000100000 (usable)
>>>>>> On node 0 totalpages: 16624
>>>>>
>>>> ...
>>>> Linux version 2.4.0 (root@tabriel) (gcc version
>>>
>> pgcc-2.95.2 19991024 (release)) #2 Mon Jan 8 09:02:27 EST 2001
>>
>>>> BIOS-provided physical RAM map:
>>>> BIOS-e820: 000000000009fc00 @ 0000000000000000 (usable)
>>>> BIOS-e820: 0000000000000400 @ 000000000009fc00 (reserved)
>>>> BIOS-e820: 0000000000010000 @ 00000000000f0000 (reserved)
>>>> BIOS-e820: 0000000000010000 @ 00000000ffff0000 (reserved)
>>>> BIOS-e820: 000000000bef0000 @ 0000000000100000 (usable)
>>>> BIOS-e820: 000000000000d000 @ 000000000bff3000 (ACPI data)
>>>> BIOS-e820: 0000000000003000 @ 000000000bff0000 (ACPI NVS)
>>>> On node 0 totalpages: 49136
>>>
>> It did it again. fresh tree, egcs 1.1.2, etc
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Different versions of gcc were used on 2.4.0 vs. 2.4.1.
> Were different versions of as also used? (hint?)
>
> Or somehow in linux/arch/i386/boot/setup.S, your source
> file has
> #define STANDARD_MEMORY_BIOS_CALL
> ?
>
> ~Randy / 503-677-5408
>
granted, it is possible that a different gas was used, but extremely
unlikely. I have been known to build my own compilers (need to try libc
some time), but haven't played around w/ binutils. box is Redhat 6.[01]?
upped to Mandrake 7.1 a month ago.
haven't installed any new compilers lately, I think that 2.4.1 makefile
is different, selects diff compiler (haven't found out the differences
btwn Mandrake and RedHat yet)
grepped sources for that #define; did not find anywhere
Sorry for bad grammar, usually not this bad, very very tired, can't make
fingers type straight half the time.
currently running 2.4.1 rebuilt with mem=192M. Hope this is resolved soon.
Also will consider trying to specify compiler to be same as 2.4.0 build
(not likely a good idea, given that pgcc 2.95.x borks 2.4.1
[fxsr_alignment IIRC])
Also will look for different as executables. BTW, pgcc above is actually
2.95.3, not 2.95.2
I'm rambling and need sleep.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-01 2:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 2:22 [BUG] 2.4.1 Detects 64 MB RAM, actual 192MB Dunlap, Randy
2001-02-01 2:47 ` 2.4.1 FireWire compile problem Dax Kelson
2001-02-01 2:54 ` Dax Kelson
2001-02-01 2:57 ` Adam Schrotenboer [this message]
2001-02-06 0:05 ` [BUG] 2.4.1 Detects 64 MB RAM, actual 192MB Ricky Beam
2001-02-06 1:53 ` Ricky Beam
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 23:19 Mikael Pettersson
2001-02-01 0:23 ` Adam Schrotenboer
2001-01-31 10:57 Mikael Pettersson
2001-01-31 11:18 ` Dr. David Gilbert
2001-01-31 16:05 ` Adam Schrotenboer
2001-01-31 4:25 Adam Schrotenboer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A78D0A1.9070100@lycosmail.com \
--to=ajschrotenboer@lycosmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox