From: Kenneth Parrish <Kenneth.Parrish@family-bbs.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM] mtrr's not set, 2.6.13
Date: 14 Sep 2005 09:22:34 GMT [thread overview]
Message-ID: <603fb7.2e22d1@family-bbs.org> (raw)
-=> In 13 Sep 05 15:30:16 article, Dave Jones wrote to All and Jim <=-
[...]
JM> /proc/mtrr:
JM>
JM> reg00: base=0x00000000 ( 0MB), size=983552MB: write-back, count=1
DJ> That's an incredibly huge amount of system ram :)
DJ> Have you done a BIOS update between the kernel upgrades by any
chance ?
DJ> Or altered any options in the BIOS ?
DJ> Does booting the older kernel definitly still work ?
DJ> AFAIR, we don't touch the first MTRR, that's typically set up by
DJ> the BIOS before we even boot.
not sure when this changed, but this computer, a 99 e-machines cyrix m
ii and via mvp3 unit, is showing more than the 512 megas pc 100 ram it
actually has, apparently, in the first line of /proc/mtrr quoted below
3 Wed Sep 14 03:44:18 0 ~/build/kernel/linux-2.6.14-rc1 $ cat /proc/mtrr
reg00: base=0xfd000000 (4048MB), size= 4MB: write-combining, count=1
reg01: base=0x000c0000 ( 0MB), size= 256KB: uncachable, count=1
reg07: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1
X shows the video with four MB, lspci shows 16MB -- been that
way for awhile..
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC AGP (rev
7a) (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Rage IIC AGP
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste
SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbor
<MAbort- >SERR- <PERR-
Latency: 64 (2000ns min), cache line size 08
Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Region 1: I/O ports at d800 [size=256]
Region 2: Memory at feaff000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at feac0000 [disabled] [size=128K]
Capabilities: [5c] Power Management version 1
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3ho
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Linux fret 2.6.14-rc1 #6 Wed Sep 14 01:05:11 CDT 2005 i686 unknown unknown
GNU/Linux
p.s. this 2.6.14-rc1 kernel shows four lines plus one or two
pixels of the next line, at the bottom of each text console, filled with
what looks like earlier buffer. and it scrolls, with new output. ??
--- MultiMail/Linux v0.46
next reply other threads:[~2005-09-14 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 9:22 Kenneth Parrish [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-04 21:14 [PROBLEM] mtrr's not set, 2.6.13 Jouni Karvo
2005-09-12 9:10 Jim McCloskey
2005-09-12 9:51 ` Andrew Morton
2005-09-12 17:24 ` Jim McCloskey
2005-09-12 23:27 ` Dave Jones
2005-09-13 3:01 ` Shaohua Li
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=603fb7.2e22d1@family-bbs.org \
--to=kenneth.parrish@family-bbs.org \
--cc=linux-kernel@vger.kernel.org \
/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