Bug 162065
Created attachment 116133 [details]
This patch to remove the aac_handle_aif() code did not help.
Created attachment 116134 [details]
Patch to turn on dprintk and add more debug printks, attaching console messages.
Created attachment 116135 [details]
Console messages showing the driver stuck in aac_queue_get()
Please test the kernel located at: http://people.redhat.com/coughlan/.2.4.21-37.7.ELdrvrtest2/ to verify that it solves the problem. This contains version 1.1.5-2412 of the aacraid driver. This is the latest from Adaptec, and is a candidate for U7. A fix for this problem has just been committed to the RHEL3 U7 patch pool this evening (in kernel version 2.4.21-37.10.EL). An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2006-0144.html |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2 Description of problem: Using an Adaptec 2230SLP RAID controller with 2 73GB disks in a RAID-1 setup. If the array is not "optimal" then RHEL will quit responding to keyboard, mouse and network (system hung). System is in a state were fib_adapter_complete() calls acc_queue_get() which in turns calls aac_get_entry(), acc_get_entry() is always returning 0 causing the driver to be stuck in the following loop in aac_queue_get(): else if (qid == AdapHighRespQueue || qid == AdapNormRespQueue) { while(!aac_get_entry(dev, qid, &entry, index, nonotify)) { /* if no entries wait for some if caller wants to */ DPRINTK("RespQueue: No entries, wait...\n"); } } Version-Release number of selected component (if applicable): kernel-2.4.21-32.0.1.EL How reproducible: Always Steps to Reproduce: 1. Boot with RAID array not optimal. 2. 3. Actual Results: System will hang, no response from keyboard, mouse, or networking. Expected Results: System should boot up and function as normal. Additional info: Based upon Alan Cox's comments for 2.6 http://lkml.org/lkml/2005/1/14/252, tried to remove the aac_handle_aif() code from the 2.4 driver, the system still hung when booting with raid not optimal. Also turned on dprintk and added some more debug statements, console messages attached.