mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Alexander Huemer" <alexander.huemer@sbg.ac.at>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Helge Hafting" <helge.hafting@aitel.hist.no>
Subject: Re: 2.6.27 mtrr fixes do not work
Date: Fri, 29 Aug 2008 14:39:57 -0700	[thread overview]
Message-ID: <86802c440808291439o156f4f28v4b93e0105b4fe3b3@mail.gmail.com> (raw)
In-Reply-To: <48B849BD.4000405@sbg.ac.at>

On Fri, Aug 29, 2008 at 12:10 PM, Alexander Huemer
<alexander.huemer@sbg.ac.at> wrote:
> http://xx.vu/~ahuemer/dmesg_5.txt
> http://xx.vu/~ahuemer/lspci_vvxxx.txt
> http://xx.vu/~ahuemer/lspci_tv.txt
>

pci 0000:00:1e.0:   IO window: 0x3000-0x3fff
pci 0000:00:1e.0:   MEM window: 0xdc300000-0xdc3fffff
pci 0000:00:1e.0:   PREFETCH window: 0x000000d8000000-0x000000dbffffff

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
(prog-if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Bus: primary=00, secondary=20, subordinate=20, sec-latency=32
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: dc300000-dc3fffff
	Prefetchable memory behind bridge: 00000000d8000000-00000000dbffffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [50] Subsystem: Tyan Computer Device 5397
00: 86 80 4e 24 07 00 10 00 d9 01 04 06 00 00 01 00
10: 00 00 00 00 00 00 00 00 00 20 20 20 30 30 80 22
20: 30 dc 30 dc 01 d8 f1 db 00 00 00 00 00 00 00 00
30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 0c 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 0d 00 00 00 f1 10 97 53 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 80 0f 01 00 00 00 00 00

20:05.0 VGA compatible controller: XGI Technology Inc. (eXtreme
Graphics Innovation) Volari Z7 (prog-if 00 [VGA controller])
	Subsystem: XGI Technology Inc. (eXtreme Graphics Innovation) Volari Z7
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	BIST result: 00
	Region 0: Memory at d8000000 (32-bit, prefetchable) [size=64M]
	Region 1: Memory at dc300000 (32-bit, non-prefetchable) [size=256K]
	Region 2: I/O ports at 3000 [size=128]
	Capabilities: [40] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: ca 18 20 00 03 00 30 02 00 00 00 03 00 00 00 80
10: 08 00 00 d8 00 00 30 dc 01 30 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 ca 18 20 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00
40: 01 00 02 06 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

mtrr: 0xd8000000,0x2000000 overlaps existing 0xd8000000,0x800000

so it seems your card HW said it need 64M,

someone (BIOS or vgabios?) set 8M for it at first. and with write-back...

   # cat /proc/mtrr
   reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
   reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
   reg02: base=0x100000000 (4096MB), size=1024MB: write-back, count=1
   reg03: base=0xd8000000 (3456MB), size=   8MB: write-back, count=1

before loading X drivers, need to remove that entry at first.

echo "disable=3" > /proc/mtrr

YH

  reply	other threads:[~2008-08-29 21:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06 14:05 2.6.27-rc1 " Alexander Huemer
2008-08-07 20:14 ` Rafael J. Wysocki
2008-08-07 20:15   ` Pallipadi, Venkatesh
2008-08-07 20:23     ` Yinghai Lu
2008-08-07 20:26       ` Yinghai Lu
2008-08-07 22:14         ` Alexander Huemer
2008-08-07 23:16           ` Yinghai Lu
2008-08-07 23:17             ` Yinghai Lu
2008-08-07 23:30               ` Alexander Huemer
2008-08-07 23:58                 ` Yinghai Lu
2008-08-08  0:28                   ` Alexander Huemer
2008-08-14 14:09                   ` Alexander Huemer
2008-08-14 17:31                     ` Yinghai Lu
2008-08-21 14:52                       ` 2.6.27 " Alexander Huemer
2008-08-21 15:27                         ` Yinghai Lu
2008-08-21 18:44                           ` Alexander Huemer
2008-08-22 10:11                           ` 2.6.27 mtrr fixes do not work when X starts Helge Hafting
2008-08-22 17:24                             ` Yinghai Lu
2008-08-25 11:10                               ` Helge Hafting
2008-08-25 20:08                                 ` Yinghai Lu
2008-08-25 20:19                                   ` Alexander Huemer
2008-08-25 20:22                                     ` Yinghai Lu
     [not found]                                       ` <48B31508.6020305@sbg.ac.at>
     [not found]                                         ` <86802c440808251344h697a27d0i91486a836d258cb@mail.gmail.com>
     [not found]                                           ` <86802c440808251624u181a98eesd8a19ea6fd3d8d8c@mail.gmail.com>
     [not found]                                             ` <48B34056.5080100@sbg.ac.at>
     [not found]                                               ` <86802c440808251633s7bf8ecb2ua6ef187b5be563db@mail.gmail.com>
2008-08-29 15:09                                                 ` 2.6.27 mtrr fixes do not work Alexander Huemer
2008-08-29 17:43                                                   ` Yinghai Lu
2008-08-29 19:10                                                     ` Alexander Huemer
2008-08-29 21:39                                                       ` Yinghai Lu [this message]
2008-08-30 11:11                                                     ` Helge Hafting
2008-08-26  9:32                                   ` 2.6.27 mtrr fixes do not work when X starts Helge Hafting
2008-08-26 16:43                                     ` Yinghai Lu
2008-08-27 12:53                                       ` Helge Hafting
2008-08-27 13:03                                         ` Andi Kleen

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=86802c440808291439o156f4f28v4b93e0105b4fe3b3@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=alexander.huemer@sbg.ac.at \
    --cc=helge.hafting@aitel.hist.no \
    --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

all inboxes | Powered by JetHome®