aacraid driver fails with Dell PowerEdge Expandable RAID Controller 3/Di
A message that is not in the archive (sent off-list or not yet received): [email protected]/
http://bugzilla.kernel.org/show_bug.cgi?id=9133
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
------- Comment #7 from [email protected] 2008-04-20 05:40 ------- If specific firmware versions (e.g. less than X) for a given card are known to be problematic, the driver init routine should detect these and warn loudly, if not fail to load all together. We did this with the megaraid_legacy driver a long time ago to avoid firmware-induced data corruption.
Signature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.kernel.org/show_bug.cgi?id=9133
------- Comment #8 from [email protected] 2008-06-26 07:29 ------- I also encountered this issue (with kernel 2.6.24, previous kernel was 2.6.15 but I suppose the problem was triggered by upgrading memory from 4GB to 6GB) on PowerEdge 2650 (with Dell PowerEdge Expandable RAID Controller 3/Di).
I can confirm that firmware/BIOS update (from version 2.8.0.6092 to 2.8.1.7692) solved it.
Signature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.kernel.org/show_bug.cgi?id=9133
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |martin.wilck@fujitsu-
| |siemens.com------- Comment #9 from [email protected] 2008-10-10 03:11 ------- (I am copying this from https://bugzilla.redhat.com/show_bug.cgi?id=457552)
Thie discussion here resulted in the following patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=94cf6ba11b
Unless overridden by module dac_mode=0, aac_scsi_32_64 is used for aac_adapter_scsi() on 64bit-DMA-capable systems for all contollers with AAC_QUIRK_SCSI_32 and AAC_OPT_SGMAP_HOST64 set.
aac_scsi_32_64() always returns FAILED on 64bit DMA-capable systems if the adapter has the AAC_OPT_SGMAP_HOST64 flag set , and if the physical memory is
Quoted 1 line
4GB.
Thus, on every system with 64bit DMA and >4GB memory, aac_adapter_scsi() will always fail (!) for each controller with AC_QUIRK_SCSI_32 and AAC_OPT_SGMAP_HOST64. In practice, that means to me that AC_QUIRK_SCSI_32 implies that you can't use >4GB memory (that agrees with the findings in comment #17).
Perhaps the Perc 3/Di has this limitation, but the 2120S and 2200S certainly don't. In the above-mentioned Red Hat bugzilla, the patch was modified by removing 2120S and 2200S from the list of controllers with AC_QUIRK_SCSI_32. Most probably, that isn't even sufficient. I would suggest to remove AC_QUIRK_SCSI_32 for all controllers except the Perc 3/Di.
Mark, how did you generate the list of controllers that you assigned AC_QUIRK_SCSI_32 to? Why did you include 2120S and 2200s?
Signature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.kernel.org/show_bug.cgi?id=9133
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution| |CODE_FIXSignature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.