Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Trying to make a happy kernel for an i7 920 with KVM
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
1clue
Advocate
Advocate


Joined: 05 Feb 2006
Posts: 2569

PostPosted: Sat Oct 16, 2010 5:23 am    Post subject: Reply with quote

I think I get it. I thought you were asking something else.

Right now, I have the log entry and nothing else. I haven't tried KVM yet. I'm trying to have my ducks in a row before diving in. I'm reasonably experienced with VMware on Linux, Mac and Windows, and with Parallels on Mac. So I'm a KVM newbie.

I'm just going through the Gentoo KVM HOWTO right now, and discovered that qemu-kvm is masked by ~amd64. I now suddenly wonder why, and if it's always masked or if something bad just happened.

I was under the impression that KVM was a mature product. I unmasked it for now, but I would like to have some level of confidence that when I have commercial software licenses on KVM I won't be stuck with dead software.

Thanks.
Back to top
View user's profile Send private message
cach0rr0
Bodhisattva
Bodhisattva


Joined: 13 Nov 2008
Posts: 4123
Location: Houston, Republic of Texas

PostPosted: Sat Oct 16, 2010 7:56 am    Post subject: Reply with quote

it's perfectly stable. It's just not officially perfectly stable.

If you have your /dev/kvm you're fine. And really, do a 1GB qcow2 image, boot qemu-kvm from a minimal iso (preferably sysrescuecd!), see if it works. There's no real harm in it, and that's a more than adequate test. If that works, nothing else you could potentially do should be problematic.
Back to top
View user's profile Send private message
aCOSwt
Bodhisattva
Bodhisattva


Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space

PostPosted: Sat Oct 16, 2010 8:39 am    Post subject: Reply with quote

1clue wrote:
reg03: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable
reg04: base=0x0bf700000 ( 3063MB), size= 1MB, count=1: uncachable
reg05: base=0x0bf800000 ( 3064MB), size= 8MB, count=1: uncachable

Well, coming back to your "cherry on the cake" or whatever you called it... :wink:
This is indeed suboptimal.
According to Gentoo Linux nVidia Guide :
<<Every line should contain "write-back" or "write-combining". If you see a line with "uncachable" in it you will need to change a BIOS setting to fix this.

Reboot and enter the BIOS, then find the MTRR settings (probably under "CPU Settings"). Change the setting from "continuous" to "discrete" and boot back into Linux. You will now find out that there is no "uncachable" entry anymore and 2D acceleration now works without any glitches
.>>
Back to top
View user's profile Send private message
1clue
Advocate
Advocate


Joined: 05 Feb 2006
Posts: 2569

PostPosted: Sun Oct 17, 2010 12:18 am    Post subject: Reply with quote

I don't have any MTRR setting in my bios. I don't have anything with a setting of continuous or discrete either.

And I did find a new issue with VT-d settings being turned on: The system will not run the nvidia X driver. I get a frozen screen after X starts, and it does not come back.

I changed the sata mode from PCI to AHCP (sorry if the four letter acronyms are wrong, I'm working from memory here) but still nothing shows up.

Is there some other name by which MTRR might be referenced? Nearly everything is either Enabled or Disabled, and if it's not a legacy feature it seems to be enabled.

I'm not messing with RAM timings or processor speed settings just on a lark.

I'll look through the nvidia guide and see if I can find something interesting.

Thanks.
Back to top
View user's profile Send private message
1clue
Advocate
Advocate


Joined: 05 Feb 2006
Posts: 2569

PostPosted: Sun Oct 17, 2010 12:24 am    Post subject: Reply with quote

However, I see my kernel has a setting for MTRR and it's set to "continuous". I obviously missed some things in here. I looked at it a month or 3 ago and I evidently did it sleeping.

Thanks.
Back to top
View user's profile Send private message
1clue
Advocate
Advocate


Joined: 05 Feb 2006
Posts: 2569

PostPosted: Sun Oct 17, 2010 12:40 am    Post subject: Reply with quote

OK I think what happened is when I started asking for help, I just took a bare seed from Pappy's site, then did what you guys said. There are settings turned off that I am positive I turned on last time.

No harm no foul, I stopped paying attention when I started this thread. I'll save the existing config so I can revert and start going from there.

I'll take it from here for a bit, the only thing I really need is info on this VT-d setting and a potential unofficial BIOS upgrade that may or may not actually be floating around somewhere.

My kernel is definitely MUCH happier than it was when I asked for help.

Thanks.
Back to top
View user's profile Send private message
pappy_mcfae
Watchman
Watchman


Joined: 27 Dec 2007
Posts: 5999
Location: Pomona, California.

PostPosted: Sun Oct 17, 2010 6:21 am    Post subject: Reply with quote

Always glad to help...and to see others out there in the thick of it as well. Happy Gentooing!

Cheers,
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols.
Back to top
View user's profile Send private message
1clue
Advocate
Advocate


Joined: 05 Feb 2006
Posts: 2569

PostPosted: Wed Oct 20, 2010 5:41 am    Post subject: Reply with quote

Trying to figure out what my MTRR kernel values should be.

I have this in my current kernel:
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1

I can't find documentation on what the last 2 should be.

Any advice, or do I just start experimenting? I can't even really tell what the possible options are.

Based on what I found in the kernel source, I'm guessing these values:
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=4

If you never hear from me again, I've torn a hole in the space-time continuum and will probably come back out of the black hole at the other end of the universe.
Back to top
View user's profile Send private message
1clue
Advocate
Advocate


Joined: 05 Feb 2006
Posts: 2569

PostPosted: Wed Oct 20, 2010 6:10 am    Post subject: Reply with quote

I think that did exactly jack. My /proc/mtrr is no different.

glxgears is even slower.

Here's the pertinent part of dmesg, only what I think is "new" mtrr related information which is impenetrable to me.

Code:

[    0.000000] MTRR default type: uncachable
[    0.000000] MTRR fixed ranges enabled:
[    0.000000]   00000-9FFFF write-back
[    0.000000]   A0000-BFFFF uncachable
[    0.000000]   C0000-E3FFF write-protect
[    0.000000]   E4000-EBFFF write-through
[    0.000000]   EC000-FFFFF write-protect
[    0.000000] MTRR variable ranges enabled:
[    0.000000]   0 base 000000000 mask E00000000 write-back
[    0.000000]   1 base 200000000 mask F00000000 write-back
[    0.000000]   2 base 300000000 mask FC0000000 write-back
[    0.000000]   3 base 0C0000000 mask FC0000000 uncachable
[    0.000000]   4 base 0BF700000 mask FFFF00000 uncachable
[    0.000000]   5 base 0BF800000 mask FFF800000 uncachable
[    0.000000]   6 disabled
[    0.000000]   7 disabled
[    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[    0.000000] original variable MTRRs
[    0.000000] reg 0, base: 0GB, range: 8GB, type WB
[    0.000000] reg 1, base: 8GB, range: 4GB, type WB
[    0.000000] reg 2, base: 12GB, range: 1GB, type WB
[    0.000000] reg 3, base: 3GB, range: 1GB, type UC
[    0.000000] reg 4, base: 3063MB, range: 1MB, type UC
[    0.000000] reg 5, base: 3064MB, range: 8MB, type UC
[    0.000000] total RAM covered: 12279M
[    0.000000]  gran_size: 64K    chunk_size: 64K    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 64K    chunk_size: 128K    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 64K    chunk_size: 256K    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 64K    chunk_size: 512K    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 64K    chunk_size: 1M    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 64K    chunk_size: 2M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 64K    chunk_size: 4M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 64K    chunk_size: 8M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 64K    chunk_size: 16M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 64K    chunk_size: 32M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 64K    chunk_size: 64M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 64K    chunk_size: 128M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 64K    chunk_size: 256M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 64K    chunk_size: 512M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 64K    chunk_size: 1G    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 64K    chunk_size: 2G    num_reg: 8     lose cover RAM: 0G
[    0.000000]  gran_size: 128K    chunk_size: 128K    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 128K    chunk_size: 256K    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 128K    chunk_size: 512K    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 128K    chunk_size: 1M    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 128K    chunk_size: 2M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 128K    chunk_size: 4M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 128K    chunk_size: 8M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 128K    chunk_size: 16M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 128K    chunk_size: 32M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 128K    chunk_size: 64M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 128K    chunk_size: 128M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 128K    chunk_size: 256M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 128K    chunk_size: 512M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 128K    chunk_size: 1G    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 128K    chunk_size: 2G    num_reg: 8     lose cover RAM: 0G
[    0.000000]  gran_size: 256K    chunk_size: 256K    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 256K    chunk_size: 512K    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 256K    chunk_size: 1M    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 256K    chunk_size: 2M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 256K    chunk_size: 4M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 256K    chunk_size: 8M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 256K    chunk_size: 16M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 256K    chunk_size: 32M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 256K    chunk_size: 64M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 256K    chunk_size: 128M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 256K    chunk_size: 256M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 256K    chunk_size: 512M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 256K    chunk_size: 1G    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 256K    chunk_size: 2G    num_reg: 8     lose cover RAM: 0G
[    0.000000]  gran_size: 512K    chunk_size: 512K    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 512K    chunk_size: 1M    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 512K    chunk_size: 2M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 512K    chunk_size: 4M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 512K    chunk_size: 8M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 512K    chunk_size: 16M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 512K    chunk_size: 32M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 512K    chunk_size: 64M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 512K    chunk_size: 128M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 512K    chunk_size: 256M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 512K    chunk_size: 512M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 512K    chunk_size: 1G    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 512K    chunk_size: 2G    num_reg: 8     lose cover RAM: 0G
[    0.000000]  gran_size: 1M    chunk_size: 1M    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 1M    chunk_size: 2M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 1M    chunk_size: 4M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 1M    chunk_size: 8M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 1M    chunk_size: 16M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 1M    chunk_size: 32M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 1M    chunk_size: 64M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 1M    chunk_size: 128M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 1M    chunk_size: 256M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 1M    chunk_size: 512M    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 1M    chunk_size: 1G    num_reg: 7     lose cover RAM: 0G
[    0.000000]  gran_size: 1M    chunk_size: 2G    num_reg: 8     lose cover RAM: 0G
[    0.000000]  gran_size: 2M    chunk_size: 2M    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 2M    chunk_size: 4M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 2M    chunk_size: 8M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 2M    chunk_size: 16M    num_reg: 7     lose cover RAM: 1M
[    0.000000]  gran_size: 2M    chunk_size: 32M    num_reg: 7     lose cover RAM: 1M
[    0.000000]  gran_size: 2M    chunk_size: 64M    num_reg: 7     lose cover RAM: 1M
[    0.000000]  gran_size: 2M    chunk_size: 128M    num_reg: 7     lose cover RAM: 1M
[    0.000000]  gran_size: 2M    chunk_size: 256M    num_reg: 7     lose cover RAM: 1M
[    0.000000]  gran_size: 2M    chunk_size: 512M    num_reg: 7     lose cover RAM: 1M
[    0.000000]  gran_size: 2M    chunk_size: 1G    num_reg: 7     lose cover RAM: 1M
[    0.000000]  gran_size: 2M    chunk_size: 2G    num_reg: 8     lose cover RAM: 1M
[    0.000000]  gran_size: 4M    chunk_size: 4M    num_reg: 8     lose cover RAM: 9219M
[    0.000000]  gran_size: 4M    chunk_size: 8M    num_reg: 8     lose cover RAM: 9215M
[    0.000000]  gran_size: 4M    chunk_size: 16M    num_reg: 7     lose cover RAM: 3M
[    0.000000]  gran_size: 4M    chunk_size: 32M    num_reg: 7     lose cover RAM: 3M
[    0.000000]  gran_size: 4M    chunk_size: 64M    num_reg: 7     lose cover RAM: 3M
[    0.000000]  gran_size: 4M    chunk_size: 128M    num_reg: 7     lose cover RAM: 3M
[    0.000000]  gran_size: 4M    chunk_size: 256M    num_reg: 7     lose cover RAM: 3M
[    0.000000]  gran_size: 4M    chunk_size: 512M    num_reg: 7     lose cover RAM: 3M
[    0.000000]  gran_size: 4M    chunk_size: 1G    num_reg: 7     lose cover RAM: 3M
[    0.000000]  gran_size: 4M    chunk_size: 2G    num_reg: 8     lose cover RAM: 3M
[    0.000000]  gran_size: 8M    chunk_size: 8M    num_reg: 8     lose cover RAM: 5127M
[    0.000000]  gran_size: 8M    chunk_size: 16M    num_reg: 8     lose cover RAM: 5127M
[    0.000000]  gran_size: 8M    chunk_size: 32M    num_reg: 6     lose cover RAM: 7M
[    0.000000]  gran_size: 8M    chunk_size: 64M    num_reg: 6     lose cover RAM: 7M
[    0.000000]  gran_size: 8M    chunk_size: 128M    num_reg: 6     lose cover RAM: 7M
[    0.000000]  gran_size: 8M    chunk_size: 256M    num_reg: 6     lose cover RAM: 7M
[    0.000000]  gran_size: 8M    chunk_size: 512M    num_reg: 6     lose cover RAM: 7M
[    0.000000]  gran_size: 8M    chunk_size: 1G    num_reg: 6     lose cover RAM: 7M
[    0.000000]  gran_size: 8M    chunk_size: 2G    num_reg: 7     lose cover RAM: 7M
[    0.000000]  gran_size: 16M    chunk_size: 16M    num_reg: 8     lose cover RAM: 5127M
[    0.000000]  gran_size: 16M    chunk_size: 32M    num_reg: 6     lose cover RAM: 7M
[    0.000000]  gran_size: 16M    chunk_size: 64M    num_reg: 6     lose cover RAM: 7M
[    0.000000]  gran_size: 16M    chunk_size: 128M    num_reg: 6     lose cover RAM: 7M
[    0.000000]  gran_size: 16M    chunk_size: 256M    num_reg: 6     lose cover RAM: 7M
[    0.000000]  gran_size: 16M    chunk_size: 512M    num_reg: 6     lose cover RAM: 7M
[    0.000000]  gran_size: 16M    chunk_size: 1G    num_reg: 6     lose cover RAM: 7M
[    0.000000]  gran_size: 16M    chunk_size: 2G    num_reg: 7     lose cover RAM: 7M
[    0.000000]  gran_size: 32M    chunk_size: 32M    num_reg: 8     lose cover RAM: 1047M
[    0.000000]  gran_size: 32M    chunk_size: 64M    num_reg: 6     lose cover RAM: 23M
[    0.000000]  gran_size: 32M    chunk_size: 128M    num_reg: 6     lose cover RAM: 23M
[    0.000000]  gran_size: 32M    chunk_size: 256M    num_reg: 6     lose cover RAM: 23M
[    0.000000]  gran_size: 32M    chunk_size: 512M    num_reg: 6     lose cover RAM: 23M
[    0.000000]  gran_size: 32M    chunk_size: 1G    num_reg: 6     lose cover RAM: 23M
[    0.000000]  gran_size: 32M    chunk_size: 2G    num_reg: 7     lose cover RAM: 23M
[    0.000000]  gran_size: 64M    chunk_size: 64M    num_reg: 8     lose cover RAM: 55M
[    0.000000]  gran_size: 64M    chunk_size: 128M    num_reg: 6     lose cover RAM: 55M
[    0.000000]  gran_size: 64M    chunk_size: 256M    num_reg: 6     lose cover RAM: 55M
[    0.000000]  gran_size: 64M    chunk_size: 512M    num_reg: 6     lose cover RAM: 55M
[    0.000000]  gran_size: 64M    chunk_size: 1G    num_reg: 6     lose cover RAM: 55M
[    0.000000]  gran_size: 64M    chunk_size: 2G    num_reg: 7     lose cover RAM: 55M
[    0.000000]  gran_size: 128M    chunk_size: 128M    num_reg: 7     lose cover RAM: 119M
[    0.000000]  gran_size: 128M    chunk_size: 256M    num_reg: 6     lose cover RAM: 119M
[    0.000000]  gran_size: 128M    chunk_size: 512M    num_reg: 6     lose cover RAM: 119M
[    0.000000]  gran_size: 128M    chunk_size: 1G    num_reg: 6     lose cover RAM: 119M
[    0.000000]  gran_size: 128M    chunk_size: 2G    num_reg: 7     lose cover RAM: 119M
[    0.000000]  gran_size: 256M    chunk_size: 256M    num_reg: 6     lose cover RAM: 247M
[    0.000000]  gran_size: 256M    chunk_size: 512M    num_reg: 6     lose cover RAM: 247M
[    0.000000]  gran_size: 256M    chunk_size: 1G    num_reg: 6     lose cover RAM: 247M
[    0.000000]  gran_size: 256M    chunk_size: 2G    num_reg: 7     lose cover RAM: 247M
[    0.000000]  gran_size: 512M    chunk_size: 512M    num_reg: 5     lose cover RAM: 503M
[    0.000000]  gran_size: 512M    chunk_size: 1G    num_reg: 6     lose cover RAM: 503M
[    0.000000]  gran_size: 512M    chunk_size: 2G    num_reg: 7     lose cover RAM: 503M
[    0.000000]  gran_size: 1G    chunk_size: 1G    num_reg: 4     lose cover RAM: 1015M
[    0.000000]  gran_size: 1G    chunk_size: 2G    num_reg: 5     lose cover RAM: 1015M
[    0.000000]  gran_size: 2G    chunk_size: 2G    num_reg: 3     lose cover RAM: 2039M
[    0.000000] mtrr_cleanup: can not find optimal value
[    0.000000] please specify mtrr_gran_size/mtrr_chunk_size
[    0.000000] e820 update range: 00000000bf700000 - 0000000100000000 (usable) ==> (reserved)
[    0.000000] last_pfn = 0xbf680 max_arch_pfn = 0x400000000
[    0.000000] Scanning 0 areas for low memory corruption
[    0.000000] modified physical RAM map:
[    0.000000]  modified: 0000000000000000 - 0000000000010000 (reserved)
[    0.000000]  modified: 0000000000010000 - 000000000009ec00 (usable)
[    0.000000]  modified: 000000000009ec00 - 00000000000a0000 (reserved)
[    0.000000]  modified: 00000000000e4c00 - 0000000000100000 (reserved)
[    0.000000]  modified: 0000000000100000 - 00000000bf680000 (usable)
[    0.000000]  modified: 00000000bf680000 - 00000000bf698000 (ACPI data)
[    0.000000]  modified: 00000000bf698000 - 00000000bf6dc000 (ACPI NVS)
[    0.000000]  modified: 00000000bf6dc000 - 00000000c0000000 (reserved)
[    0.000000]  modified: 00000000fee00000 - 00000000fee01000 (reserved)
[    0.000000]  modified: 00000000ffe00000 - 0000000100000000 (reserved)
[    0.000000]  modified: 0000000100000000 - 0000000340000000 (usable)
[    0.000000] initial memory mapped : 0 - 20000000
[    0.000000] init_memory_mapping: 0000000000000000-00000000bf680000
[    0.000000]  0000000000 - 00bf600000 page 2M
[    0.000000]  00bf600000 - 00bf680000 page 4k
[    0.000000] kernel direct mapping tables up to bf680000 @ 12000-17000
[    0.000000] init_memory_mapping: 0000000100000000-0000000340000000
[    0.000000]  0100000000 - 0340000000 page 2M
[    0.000000] kernel direct mapping tables up to 340000000 @ 15000-23000
Back to top
View user's profile Send private message
aCOSwt
Bodhisattva
Bodhisattva


Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space

PostPosted: Wed Oct 20, 2010 7:53 am    Post subject: Reply with quote

1clue wrote:

CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1

Good indeed ! 8)
1clue wrote:
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=4

Me too never found any doc about this one... So... I put 1 but... cannot honestly state that 4 is better or worse.

So I just guess that it can be the reason why things are going worse as, in your case, we have seen that reg04 is uncachable.

1clue wrote:
If you never hear from me again, I've torn a hole in the space-time continuum and will probably come back out of the black hole at the other end of the universe.

Then I can deduce from the fact that I see you back that either I am at the other end too or, the other end is identical to this end...

I will have a look to your other traces later.
Back to top
View user's profile Send private message
1clue
Advocate
Advocate


Joined: 05 Feb 2006
Posts: 2569

PostPosted: Wed Oct 20, 2010 3:47 pm    Post subject: Reply with quote

<satire>
We may have stumbled upon a paradoxical paradigm of Roddenberry-esqe scale!

Indeed, not even Wells himself explored the possibilities of time travel and space travel simultaneously.

It seems as though we're stuck with rank amateurs such as Einstein and Clarke to guide us through this maze of confusion.
</satire>
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page Previous  1, 2, 3
Page 3 of 3

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum