Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 459247

Summary:	server with Areca 1120 RAID controller hangs
Product:	Red Hat Enterprise Linux 5	Reporter:	Ferry Tap <ferry.tap>
Component:	kernel	Assignee:	Red Hat Kernel Manager <kernel-mgr>
Status:	CLOSED DUPLICATE	QA Contact:	Martin Jenner <mjenner>
Severity:	high	Docs Contact:
Priority:	medium
Version:	5.2	CC:	abc
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-09-02 12:40:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ferry Tap 2008-08-15 12:05:54 UTC

Server with RHEL 5.2 (kernel-2.6.18-92.1.6.el5, x86_64) and an Areca 1120 RAID controller hangs after heavy read/write to the RAID set. The problem persists with kernel-2.6.18-92.1.10.el5. 

It works fine with the older kernel (kernel-2.6.18-53.1.21.el5). 

I am member of the CentOS Community. See the following post: http://www.centos.org/modules/newbb/viewtopic.php?topic_id=15640&forum=39&post_id=54941#forumpost54941

Comment 1 abc 2008-08-16 00:58:40 UTC

Same problem here with ARC1220 controller.

The complete system freezes with recent kernels. No kernel output when the system crashes. With an older kernel it is working (using kernel-2.6.18-53.1.21.el5xen at the moment).

My System: 4 GB RAM, AMD64, kernel-2.6.18-92.1.10.el5xen

Comment 2 Tomas Henzl 2008-09-02 12:40:32 UTC

It looks like a duplicate of 460789, so I'm closing it here.

*** This bug has been marked as a duplicate of bug 460789 ***