Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 214883 - [2.6.24 regression] 4G FC arrays don't work properly w/ qla2xxx driver
Summary: [2.6.24 regression] 4G FC arrays don't work properly w/ qla2xxx driver
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL: http://bugzilla.kernel.org/show_bug.c...
Whiteboard: linux-2.6.24-regression
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-26 14:05 UTC by Andrej Filipcic
Modified: 2008-05-04 09:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrej Filipcic 2008-03-26 14:05:57 UTC
With gentoo-sources-2.6.24-r3, there are troubles with qla2xxx module. 4G FC arrays (Infortrend) are not working properly, while 2G FC are OK. 

Detecting 4G array gives:
 sd 8:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
 sd 8:0:0:0: [sdc] 44918798336 512-byte hardware sectors (22998425 MB)
 sd 8:0:0:0: [sdc] Write Protect is off
 sd 8:0:0:0: [sdc] Mode Sense: 8f 00 00 08
 sd 8:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sd 8:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
 sd 8:0:0:0: [sdc] 44918798336 512-byte hardware sectors (22998425 MB)
 sd 8:0:0:0: [sdc] Write Protect is off
 sd 8:0:0:0: [sdc] Mode Sense: 8f 00 00 08
 sd 8:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdc: sdc1
 sd 8:0:0:0: [sdc] Attached SCSI disk

and later on, generated by vgscan:

 sd 8:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdc, sector 0
 sd 8:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdc, sector 44918798208
 sd 8:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdc, sector 44918798320
 sd 8:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdc, sector 0
 sd 8:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdc, sector 8
 sd 8:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdc, sector 0
 sd 8:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdc, sector 44918798114
 sd 8:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdc, sector 44918798282
 sd 8:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdc, sector 34
 sd 8:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdc, sector 42
 sd 8:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdc, sector 34


gentoo-sources-2.6.23-r6 works fine. I am not sure whether this is a regression in the driver or something else. The controller is
QLogic QLE220 - PCI-Express to 4Gb FC, Single Channel
ISP5432: PCIe (2.5Gb/s x4)
and firmware version is 4.02.02 (from sys-block/qla-fc-firmware-20071207)
On qlogic site there is a newer firmware (4.03.02), although I doubt the firmware would be the cause of the problems.
Comment 1 Mike Pagano gentoo-dev 2008-03-26 16:49:24 UTC
Can you test with the latest development kernel which is vanilla-sources-2.6.25_rc7 as of this writing.
Comment 2 Andrej Filipcic 2008-03-26 16:57:00 UTC
Well, it is a production server, so I will try to find an empty slot in the next couple of days.
Comment 3 Andrej Filipcic 2008-04-06 21:50:12 UTC
I have tested today with vanilla-sources-2.6.25_rc8. Still the same problem.
Comment 4 Daniel Drake (RETIRED) gentoo-dev 2008-04-19 21:27:09 UTC
Thanks for testing. Please report this upstream at http://bugzilla.kernel.org and post the new bug URL here.

How easy is it to produce those errors? Does just running vgscan cause them?
Comment 5 Andrej Filipcic 2008-04-19 21:30:12 UTC
Will do that. Yes, vgscan causes the error. Always reproducible.
Comment 6 Andrej Filipcic 2008-04-19 21:51:25 UTC
The new URL for the bug:
http://bugzilla.kernel.org/show_bug.cgi?id=10486
Comment 7 Daniel Drake (RETIRED) gentoo-dev 2008-04-19 22:02:28 UTC
Thanks.
Easily reproducible regressions like this are good candidates for bisection, if you can afford the downtime.

http://www.reactivated.net/weblog/archives/2006/01/using-git-bisect-to-find-buggy-kernel-patches/

If you do have time to do that, please put results on the upstream bug.
Comment 8 Andrej Filipcic 2008-04-24 21:43:06 UTC
The upstream bug was resolved today.
Comment 9 Daniel Drake (RETIRED) gentoo-dev 2008-05-02 17:28:44 UTC
.
Comment 10 Daniel Drake (RETIRED) gentoo-dev 2008-05-04 09:42:45 UTC
fixed in gentoo-sources-2.6.24-r7 and gentoo-sources-2.6.25-r2, thanks for your help solving this