Bug 50636 - pe7150 unresponsive while running cerberus
Summary: pe7150 unresponsive while running cerberus
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel   
(Show other bugs)
Version: 7.3
Hardware: ia64
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-08-01 20:01 UTC by Clay Cooper
Modified: 2007-04-18 16:35 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-10-10 14:54:41 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Clay Cooper 2001-08-01 20:01:42 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-2 i686; en-US; m18)
Gecko/20010131 Netscape6/6.01

Description of problem:
While running cerberus 9-20 on a pe7150 w/ beta3 installed, 24GB ram, 2GB
swap, perc3qc raid 0 container, bios x15.

Cerberus stops timer within 15 minutes, change of virtual console takes 30
seconds, top takes over 30 minutes to update.  All swap space in use.  All
but 8MB ram in use.  Alt-sysreq is available.  No disk IO occuring.

How reproducible:

Steps to Reproduce:
1.Install fairfax beta3 on pe7150
2.Run cerberus 9-20 and note performance, responsiveness, and timer stopping

Actual Results:  System all but hangs

Expected Results:  Top should update frequently, virtual console available
immediately, disk IO should be evident, cerberus timer should continue.

Additional info:

Comment 1 Clay Cooper 2001-08-03 20:02:56 UTC
Behaviour did not occur on a pe7150 w/ beta 3 installed, bios X15, 2GB ram, 2GB

Comment 2 Bill Nottingham 2001-08-09 15:34:19 UTC
Does this behavior happen with the 2.4.7 kernel, or with more swap added?

Comment 3 Clay Cooper 2001-08-10 12:51:32 UTC
Yes and Yes.  Kernel 2.4.7-0.12.0smp, with 24GB ram, 12GB swap.  Heartbeat
stopped after 3 hours.  Machine was still up but same unresponsiveness.  Still
had sysreq access.  Could not ctrl-c cerberus to kill it.

Comment 4 Glen Foster 2001-08-23 21:51:33 UTC
This defect is considered MUST-FIX for Fairfax.

Comment 5 Clay Cooper 2001-10-10 14:54:36 UTC
Newburn ran for over 3 days with kernel 2.4.9-0.18smp and 32GB ram and 2GB swap.
Machine retained responsiveness and newburn could be stopped and started again
without problem.

Note You need to log in before you can comment on or make changes to this bug.