mtrr: 0xe4000000,0x4000000 overlaps existing 0xe4000000,0x800000
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?
Lee
Quoted 2 lines · On Sun, 01 Jan 2006 22:37:54 -0500 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?
Is that a typo (2.6.14-rc7 or 2.6.15-rc7) ?
---
~Randy
Quoted 7 lines · Randy.Dunlap
Quoted 2 lines · On Sun, 01 Jan 2006 22:37:54 -0500 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?
Is that a typo (2.6.14-rc7 or 2.6.15-rc7) ?
Yep I meant 2.6.15-rc7.
Quoted 3 lines · Lee Revell
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
Signature · 1 line
Ondrej Zary
Quoted 7 lines · Ondrej Zary
Quoted 3 lines · Lee Revell
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
Same here
mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x2000000
It appeared around kernel 2.6.14
--
Quoted 6 lines · [email protected] wrote:
Quoted 4 lines · Ondrej Zary
Quoted 3 lines · Lee Revell
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?
Quoted 8 lines
Quoted 3 lines
I see that always when starting X:
mtrr: 0xe1000000,0x800000 overlaps existing 0xe1000000,0x400000Same here
mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x2000000It appeared around kernel 2.6.14
I've just tried 2.6.8.1 and it's there too. Nothing in 2.6.0.
Signature · 1 line
Ondrej Zary
Quoted 6 lines · On Monday 02 January 2006 08:40, [email protected] wrote:
Quoted 5 lines · Ondrej Zary
Quoted 3 lines · Lee Revell
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?
Quoted 8 lines
Quoted 2 lines
I see that always when starting X:
mtrr: 0xe1000000,0x800000 overlaps existing 0xe1000000,0x400000Same here
mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x2000000It appeared around kernel 2.6.14
And I've built and ran virtually every kernel from 2.6.14 to 2.6.15-rc7 without encountering that message. Ati 9200SE card, 128 megs of ram. Athlon 32 bitter running at a real clock speed of 2100mhz.
Quoted 9 lines
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signature · 7 lines
Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.