HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- ASR detected by system ROM during stress test.
Operating System - Linux
1829598
Members
1714
Online
109992
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
11-06-2007 07:17 PM
11-06-2007 07:17 PM
ASR detected by system ROM during stress test.
Hi,
I have a DL585G1 linux box as a web servers. Currently we conduct a stress test. It always rebooted when the concurrent connection reachs 100. We have 4 CPUs. Before the system reboot, the first CPU reaches about 63% utilization, but the other 3 cpus are about 20% utilization. Major processes are java, tomcat and apache.
The system doesn't capture any useful inforamtion except "ASR detected by system ROM" after system reboot.
Anyone has encountered this before? please advise.
I have a DL585G1 linux box as a web servers. Currently we conduct a stress test. It always rebooted when the concurrent connection reachs 100. We have 4 CPUs. Before the system reboot, the first CPU reaches about 63% utilization, but the other 3 cpus are about 20% utilization. Major processes are java, tomcat and apache.
The system doesn't capture any useful inforamtion except "ASR detected by system ROM" after system reboot.
Anyone has encountered this before? please advise.
wang & wang
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-06-2007 07:31 PM
11-06-2007 07:31 PM
Re: ASR detected by system ROM during stress test.
ASR's are caused when the system can't contact the OS via an NMI.
The 'hpasmd' which is running is what resets the ASR counter.
Using the 'hplog' tool, you can alter the ASR period, or even disable it.
That being said, only 100 concurrent connections? It should be getting ASR timeout's with so little load, unless the tomcat/apache services aren't really well configured.
Make sure you're running the most up to date packages available, and not the old distributed packages (which are usually fairly buggy).
Possibly change which JRE you're using, if you can do that. Most JRE's run in single thread unless you tweak it fairly hard to use multiple threads. From your description, your JRE is only running a single thread (thus why one CPU is getting most of the load, and the others are sleeping).
Now, all this being said, you've only talked about what sort of CPU utilization you're witnessing. A busy system is more than CPU usage. It's also tied to the IO subsystems, what sort of runqueues you're getting, memory and swap usage etc. etc. etc.
Use tools like 'vmstat' and 'sar' to help monitor these things is helpful. Set up 'snmp' and MRTG/Cacti to graph the results to make sense of them.
Keep poking it.. ;)
The 'hpasmd' which is running is what resets the ASR counter.
Using the 'hplog' tool, you can alter the ASR period, or even disable it.
That being said, only 100 concurrent connections? It should be getting ASR timeout's with so little load, unless the tomcat/apache services aren't really well configured.
Make sure you're running the most up to date packages available, and not the old distributed packages (which are usually fairly buggy).
Possibly change which JRE you're using, if you can do that. Most JRE's run in single thread unless you tweak it fairly hard to use multiple threads. From your description, your JRE is only running a single thread (thus why one CPU is getting most of the load, and the others are sleeping).
Now, all this being said, you've only talked about what sort of CPU utilization you're witnessing. A busy system is more than CPU usage. It's also tied to the IO subsystems, what sort of runqueues you're getting, memory and swap usage etc. etc. etc.
Use tools like 'vmstat' and 'sar' to help monitor these things is helpful. Set up 'snmp' and MRTG/Cacti to graph the results to make sense of them.
Keep poking it.. ;)
One long-haired git at your service...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2007 12:40 AM
11-08-2007 12:40 AM
Re: ASR detected by system ROM during stress test.
Hello KenKen,
As a first step to debug, I would disable ASR thru BISO.
This should avoid the system rebooting and give a chance to debug.
-Good Luck
Bharath
As a first step to debug, I would disable ASR thru BISO.
This should avoid the system rebooting and give a chance to debug.
-Good Luck
Bharath
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2007 01:28 AM
11-08-2007 01:28 AM
Re: ASR detected by system ROM during stress test.
I have tried to disable it, but the system just hung there and I still can't get any valueble information.
wang & wang
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