On Thu, Sep 20, 2007 at 09:43:42AM +0200, Wojciech Kromer wrote:
> Uff. Now full memtest takes less than 2 hours.
Being able to cache memory helps a lot.
--
Len Sorensen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
On Wed, Sep 19, 2007 at 11:28:16AM +0200, Wojciech Kromer wrote:
> a)With mem=8GB parameter I had:
>
> #free -m
> total used free shared buffers cached
> Mem: 6473 474 5999 0 29 278
>
>
> b) Without mem=8GM system slows down while booting and sometimes restart...
>
>
> So the story
On Wed, Sep 19, 2007 at 11:28:16AM +0200, Wojciech Kromer wrote:
a)With mem=8GB parameter I had:
#free -m
total used free shared buffers cached
Mem: 6473 474 5999 0 29 278
b) Without mem=8GM system slows down while booting and sometimes restart...
So the story begins
On Thu, Sep 20, 2007 at 09:43:42AM +0200, Wojciech Kromer wrote:
Uff. Now full memtest takes less than 2 hours.
Being able to cache memory helps a lot.
--
Len Sorensen
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
# free -m
total used free shared buffers cached
Mem: 7988 1120 6868 0 88 612
Now i need to rerun memory tests.
Thank you for helping me with this stuff.
Uff. Now full memtest takes less than 2 hours.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
# free -m
total used free shared buffers cached
Mem: 7988 1120 6868 0 88 612
Now i need to rerun memory tests.
Thank you for helping me with this stuff.
Uff. Now full memtest takes less than 2 hours.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
It's Intel-quad, so there are 4 CPUs.
Weird. The message about the MTRR on all the CPUs not maching sound
like a strange bios bug. Are you running the latest bios version?
See the story below.
Looks to match the MTRR setup at least. So how much ram does the kernel
actually
It's Intel-quad, so there are 4 CPUs.
Weird. The message about the MTRR on all the CPUs not maching sound
like a strange bios bug. Are you running the latest bios version?
See the story below.
Looks to match the MTRR setup at least. So how much ram does the kernel
actually
On Tue, Sep 18, 2007 at 04:35:43PM +0200, Wojciech Kromer wrote:
> Yes, it's a bit strange, but there should be a way to configure it in linux.
> I found only memmap option which does selection of regions, but not
> remapping.
No it is entirely the BIOS's job to do that. It would be very hard
[EMAIL PROTECTED] ~]# cat /proc/mtrr
reg00: base=0x1 (4096MB), size=8192MB: write-back, count=1
reg01: base=0x28000 (10240MB), size=2048MB: uncachable, count=1
reg02: base=0x26000 (9728MB), size= 512MB: uncachable, count=1
reg03: base=0x ( 0MB), size=4096MB:
On Tue, Sep 18, 2007 at 09:01:44AM +0200, Wojciech Kromer wrote:
> I have 2.6.22.6 kernel
>
> First MTRR looks good for me.
> Why it was rejected?
> And how to force using it?
>
> here are more details
>
> [EMAIL PROTECTED] ~]# cat /proc/mtrr
> reg00: base=0x1 (4096MB), size=8192MB:
What does your mtrr look like? How about dmesg? Might be the stupid
mtrr setup some bioses have been doing on intel chips where it would do:
4GB range at 4GB
1GB range at 8GB
512MB range at 9GB
256MB range at 9.5GB
etc.
And then it runs out of entries (which pisses of X).
The simple
What does your mtrr look like? How about dmesg? Might be the stupid
mtrr setup some bioses have been doing on intel chips where it would do:
4GB range at 4GB
1GB range at 8GB
512MB range at 9GB
256MB range at 9.5GB
etc.
And then it runs out of entries (which pisses of X).
The simple
On Tue, Sep 18, 2007 at 09:01:44AM +0200, Wojciech Kromer wrote:
I have 2.6.22.6 kernel
First MTRR looks good for me.
Why it was rejected?
And how to force using it?
here are more details
[EMAIL PROTECTED] ~]# cat /proc/mtrr
reg00: base=0x1 (4096MB), size=8192MB: write-back,
[EMAIL PROTECTED] ~]# cat /proc/mtrr
reg00: base=0x1 (4096MB), size=8192MB: write-back, count=1
reg01: base=0x28000 (10240MB), size=2048MB: uncachable, count=1
reg02: base=0x26000 (9728MB), size= 512MB: uncachable, count=1
reg03: base=0x ( 0MB), size=4096MB:
On Tue, Sep 18, 2007 at 04:35:43PM +0200, Wojciech Kromer wrote:
Yes, it's a bit strange, but there should be a way to configure it in linux.
I found only memmap option which does selection of regions, but not
remapping.
No it is entirely the BIOS's job to do that. It would be very hard for
On Fri, Sep 14, 2007 at 10:50:24AM +0200, Wojciech Kromer wrote:
> I can't see whole 8GB of ram.
>
> With F2 BIOS release i can only work with kernel param mem=4G.
> After updating to F4 BIOS release I can work with mem=8G, but I see this:
>
> # free -m
> total used free
I can't see whole 8GB of ram.
With F2 BIOS release i can only work with kernel param mem=4G.
After updating to F4 BIOS release I can work with mem=8G, but I see this:
# free -m
total used free sharedbuffers cached
Mem: 6473474 5999
I can't see whole 8GB of ram.
With F2 BIOS release i can only work with kernel param mem=4G.
After updating to F4 BIOS release I can work with mem=8G, but I see this:
# free -m
total used free sharedbuffers cached
Mem: 6473474 5999
On Fri, Sep 14, 2007 at 10:50:24AM +0200, Wojciech Kromer wrote:
I can't see whole 8GB of ram.
With F2 BIOS release i can only work with kernel param mem=4G.
After updating to F4 BIOS release I can work with mem=8G, but I see this:
# free -m
total used free
20 matches
Mail list logo
