topic Re: Proliant ML530 G3 Linux RedHat ES 2.1 System panics in Operating System - Linux

Proliant ML530 G3 Linux RedHat ES 2.1 System panics

meekrob — Mon, 05 Apr 2004 09:53:04 GMT

Dear All,

I have a problem on Proliant ML 350 G3,1.768 Go de RAM (1 x 1Go + 3 x 256Ko), bi-processeur Intel(R) Xeon(TM) CPU 2.40GHz.

O.S is RedHat Enterprise ES 2.1, with Linux 2.4.9-e.38smp.

We had a Linux Kernel crash

Apr 2 09:21:12 snapapp kernel: Unable to handle kernel paging request at
virtual address 62db361a
Apr 2 09:21:12 snapapp kernel: printing eip:
Apr 2 09:21:12 snapapp kernel: c03aa2dc
Apr 2 09:21:12 snapapp kernel: *pde = 00000000

Can you please advise how to sort out this issue??

Regards

Suzanne

Re: Proliant ML530 G3 Linux RedHat ES 2.1 System panics

Andy Beal — Tue, 06 Apr 2004 15:03:11 GMT

First make sure your swap is activated, and you have enough, you should at least match the amount of swap with the amount of ram. If that looks intact, I'd start reading the changelog for the kernel on the redhat network.

Maybe try a slightly older Kernel, I'm running 2.4.9-e.27smp with 4Gb of RAM, on the exact same hardware. But that is an AS system, I'm not sure if when they rebranded to 2.1 ES from 2.1 AS if they changed the base kernel load.

Also the HP management agents can tell you a lot about the hardware and how it's behaving, I had a bad slot in a memory carrier that would show up about once a week, the IML told me at least the chip/slot was defective.

Andy

Re: Proliant ML530 G3 Linux RedHat ES 2.1 System panics

meekrob — Wed, 07 Apr 2004 01:07:00 GMT

Thanks a lot for your reply.
In reference to your reply, i understand that the slot or the memory module might cause the problem of Kernel crash!!!
By the way, I've assigned you a point for this reply!!!!!!