HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Proliant ML530 G3 Linux RedHat ES 2.1 System pani...
Operating System - Linux
1833780
Members
2401
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2004 02:53 AM
04-05-2004 02:53 AM
Proliant ML530 G3 Linux RedHat ES 2.1 System panics
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
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
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2004 08:03 AM
04-06-2004 08:03 AM
Re: Proliant ML530 G3 Linux RedHat ES 2.1 System panics
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2004 06:07 PM
04-06-2004 06:07 PM
Re: Proliant ML530 G3 Linux RedHat ES 2.1 System panics
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!!!!!!
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!!!!!!
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP