Re: [Bugme-new] [Bug 10486] New: kernel 2.6.25 4G FC arrays don't work properly with qla2xxx driver

Re: [Bugme-new] [Bug 10486] New: kernel 2.6.25 4G FC arrays don't work properly with qla2xxx driver

[Andrew Morton]

> On Sat, 19 Apr 2008 14:46:04 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=10486
> 
>            Summary: kernel 2.6.25  4G FC arrays don't work properly with
>                     qla2xxx driver
>            Product: SCSI Drivers
>            Version: 2.5
>      KernelVersion: 2.6.25
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: blocking
>           Priority: P1
>          Component: QLOGIC QLA2XXX
>         AssignedTo: scsi_drivers-qla2xxx@kernel-bugs.osdl.org
>         ReportedBy: andrej.filipcic@ijs.si
> 
> 
> Latest working kernel version: 2.6.23
> Earliest failing kernel version: 2.6.24
> Distribution: gentoo
> Hardware Environment: opteron
> Software Environment: x86_64
> Problem Description:
> 
> With 2.6.24 and 25 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
> 
> 
> 2.6.23 (gentoo-sources) 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.
> 
> To be honest, I have not checked 2.6.25 release but rather rc8, however there
> are no qla2xxx related patches since then.
> 
> 
> Steps to reproduce: boot 2.6.24 or 25, run vgscan
> 
> 
> -- 
> Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.