2004-06-01 09:22:45

by Marco Marabelli

[permalink] [raw]
Subject: probls upgrading ram on a 2.4 linuxbox


Hi all!
As subject I upgraded my box from 1GB ram to 2GB ram; bios sees all
new memory but kernel doesn'load (error in memory stack).
I have the kernel set with CONFIG_HIGHMEM4G.
I googled everywhere but didn't find any similar problem.
Anyone has a suggestion?
linux 2.4.18 (slackware) on 2x1.6 athlon processor, ram266Mhz no ECC.

Regards,
Marco Marabelli


2004-06-01 09:52:36

by Marco Marabelli

[permalink] [raw]
Subject: Re: probls upgrading ram on a 2.4 linuxbox





On Tuesday 01 June 2004 12:19, Marco Marabelli wrote:
> > Hi all!
> > As subject I upgraded my box from 1GB ram to 2GB ram; bios sees all
> >new memory but kernel doesn'load (error in memory stack).

>Details??

> > I have the kernel set with CONFIG_HIGHMEM4G.
> > I googled everywhere but didn't find any similar problem.
> > Anyone has a suggestion?
> > linux 2.4.18 (slackware) on 2x1.6 athlon processor, ram266Mhz no ECC.
> --
> vda

Unfortunately I didn't note exactly the error output, I will try tonight
again (it's a server on production), but:
- with 2GB, after lilo black screen ...
- with 1.5GB, the kernel stops after detecting SCSI drive, with a long
output that explaned a memory error in stack ...
- obviously, rebooting with 1GB everything works ...
in a few hours I can report in ML the details ... (waiting for offices to
close)

thanks in advice,
Marco Marabelli

2004-06-01 13:29:32

by Kalin KOZHUHAROV

[permalink] [raw]
Subject: Re: probls upgrading ram on a 2.4 linuxbox

Marco Marabelli wrote:
>
>
>
>
> On Tuesday 01 June 2004 12:19, Marco Marabelli wrote:
>
>> > Hi all!
>> > As subject I upgraded my box from 1GB ram to 2GB ram; bios sees all
>> >new memory but kernel doesn'load (error in memory stack).
>
>
>> Details??
>
>
>> > I have the kernel set with CONFIG_HIGHMEM4G.
>> > I googled everywhere but didn't find any similar problem.
>> > Anyone has a suggestion?
>> > linux 2.4.18 (slackware) on 2x1.6 athlon processor, ram266Mhz no ECC.
Probably CONFIG_HIGHMEM4G is notrelated...

> Unfortunately I didn't note exactly the error output, I will try tonight
> again (it's a server on production), but:
> - with 2GB, after lilo black screen ...
> - with 1.5GB, the kernel stops after detecting SCSI drive, with a long
> output that explaned a memory error in stack ...
> - obviously, rebooting with 1GB everything works ...
I bet it is faulty RAM (hardware bug). To be sure run memtest http://memtest.org/ for a few hours if possible
Try running with 1GB, but with the new DIMM (t.e. just exchange the DIMMs).
If this works, put now the old DIMM back, but on different DIMM slot and try memtest.

Report back.

> in a few hours I can report in ML the details ... (waiting for offices
> to close)
> thanks in advice,
> Marco Marabelli

Kalin.

--
||///_ o *****************************
||//'_/> WWW: http://ThinRope.net/
|||\/<"
|||\\ '
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

2004-06-01 13:33:50

by Kalin KOZHUHAROV

[permalink] [raw]
Subject: Re: probls upgrading ram on a 2.4 linuxbox

Marco Marabelli wrote:
>
>
>
>
> On Tuesday 01 June 2004 12:19, Marco Marabelli wrote:
>
>> > Hi all!
>> > As subject I upgraded my box from 1GB ram to 2GB ram; bios sees all
>> >new memory but kernel doesn'load (error in memory stack).
>
>
>> Details??
>
>
>> > I have the kernel set with CONFIG_HIGHMEM4G.
>> > I googled everywhere but didn't find any similar problem.
>> > Anyone has a suggestion?
>> > linux 2.4.18 (slackware) on 2x1.6 athlon processor, ram266Mhz no ECC.
Probably CONFIG_HIGHMEM4G is notrelated...

> Unfortunately I didn't note exactly the error output, I will try tonight
> again (it's a server on production), but:
> - with 2GB, after lilo black screen ...
> - with 1.5GB, the kernel stops after detecting SCSI drive, with a long
> output that explaned a memory error in stack ...
> - obviously, rebooting with 1GB everything works ...
I bet it is faulty RAM (hardware bug). To be sure run memtest http://memtest.org/ for a few hours if possible
Try running with 1GB, but with the new DIMM (t.e. just exchange the DIMMs).
If this works, put now the old DIMM back, but on different DIMM slot and try memtest.

Report back.

> in a few hours I can report in ML the details ... (waiting for offices
> to close)
> thanks in advice,
> Marco Marabelli

Kalin.

--
||///_ o *****************************
||//'_/> WWW: http://ThinRope.net/
|||\/<"
|||\\ '
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^