From: Ondrej Zary <linux@rainbow-software.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: mtrr: 0xe4000000,0x4000000 overlaps existing 0xe4000000,0x800000
Date: Mon, 02 Jan 2006 14:25:25 +0100 [thread overview]
Message-ID: <43B929C5.6050602@rainbow-software.org> (raw)
In-Reply-To: <1136173074.6553.2.camel@mindpipe>
Lee Revell wrote:
> I got this in dmesg with 2.6.14-rc7 when I restarted X with
> ctrl-alt-backspace due to a lockup. Is it a kernel bug or an X problem?
>
I see that always when starting X:
mtrr: 0xe1000000,0x800000 overlaps existing 0xe1000000,0x400000
and this in Xorg.0.log:
(--) MGA(0): Chipset: "mga1064sg"
(**) MGA(0): Depth 24, (--) framebuffer bpp 32
(==) MGA(0): RGB weight 888
(==) MGA(0): Using AGP 1x mode
(--) MGA(0): Linear framebuffer at 0xE1000000
(--) MGA(0): MMIO registers at 0xE0000000
(--) MGA(0): Pseudo-DMA transfer window at 0xE2000000
(==) MGA(0): BIOS at 0xC0000
(--) MGA(0): Video BIOS info block at offset 0x077E0
(--) MGA(0): Found and verified enhanced Video BIOS info block
(II) MGA(0): MGABios.RamdacType = 0x0
(WW) MGA(0): Failed to set up write-combining range (0xe1000000,0x800000)
(--) MGA(0): VideoRAM: 4096 kByte
--
Ondrej Zary
next prev parent reply other threads:[~2006-01-02 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 3:37 mtrr: 0xe4000000,0x4000000 overlaps existing 0xe4000000,0x800000 Lee Revell
2006-01-02 4:20 ` Randy.Dunlap
2006-01-02 4:20 ` Lee Revell
2006-01-02 13:25 ` Ondrej Zary [this message]
2006-01-02 13:40 ` caszonyi
2006-01-02 14:05 ` Ondrej Zary
2006-01-03 2:47 ` Gene Heskett
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=43B929C5.6050602@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.