From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040514 Description of problem: The black list included in the various distributions includes the following entry for the Chaparral FR1422 disk sub-system : {"CNSi", "JSS224", "*", BLIST_SPARSELUN}, // Chaparral FR1422 This entry is not correct and should be : {"CNSi", "JFS224", "*", BLIST_SPARSELUN}, // Chaparral FR1422 Could it be fixed in the AS 2.1 Update 6 and AS 3 Update 4 G.A. versions ? Version-Release number of selected component (if applicable): kernel-source-2.4.21-21.EL How reproducible: Always Steps to Reproduce: 1. To install RHEL3-U4 or RHEL2.1-U6 releases. 2. To check the /usr/src/linux/drivers/scsi/scsi_scan.c file, searching for Chaparral FR1422 Actual Results: {"CNSi", "JSS224", "*", BLIST_SPARSELUN}, // Chaparral FR1422 Expected Results: {"CNSi", "JFS224", "*", BLIST_SPARSELUN}, // Chaparral FR1422 Additional info: This is a typo which prevents to get right information. This is a no risk fix that could be easily fixed for the G.A. delivery.
RHEL3 U4 is already closed.
Pierre: I'm sorry, but I've checked with kernel engineering and have confirmed that this would require a kernel respin, which isn't planned for RHEL 3 U4. We will add this to the U5 list. Please open an Issue Tracker for this and Frank will have it fixed. Thanks.
A fix for this problem has just been committed to the RHEL3 U4 patch pool this evening (in kernel version 2.4.21-24.EL).
An errata 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-2004-505.html
An errata 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-2004-504.html
This bug was inappropriately listed in the above 2.1 Errata (listed above), and thus should not have yet been closed. I'm reverting it to MODIFIED state until the RHEL3 Erratum is released (which should be in a week).
Ernie, it was correctly filed, as this bug was hitting both 2.1 and 3.
Hi, Bastien. A bug can only be filed against a single version (2.1, 3, 4) of a RHEL kernel because there are different CVS trees, different kernel maintainers, different blocker lists, and different advisories in the Errata System. When you enter a single bug with the hope of 2 versions being fixed, you risk that it will get fixed in one version and then forgotten about. So, in the future, please file a separate bugzilla for each kernel (major) kernel version that exhibits the problem. Thanks. Cheers. -ernie
An errata 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/RHBA-2004-550.html