host A and host B are connected to the same FC switch with qla2300 HBA card.
And I can see device such as "/dev/sda" through command "fdisk -l" on A.
but if I reboot host B, then the device is removed for some reason.
The messages are:
kernel: rport-0:0-0: blocked FC remote port time out: removing target and
saving binding
kernel: rport-1:0-0: blocked FC remote port time out: removing target and
saving binding
My problem is, the device can not come back automaticly unless I reload
the driver module "qla2300". But after I reload module "qla2300" on host A,
the device on host B disappeared.
Now I've updated my kernel to 2.6.15.git6?B I select the driver as:
<*> QLogic QLA2XXX Fibre Channel Support
[ ] Use firmware-loader modules (DEPRECATED)
but After I reboot my host to the new kernel, I can not find the device.
The logs are:
Jan 11 16:53:07 nd10 kernel: QLogic Fibre Channel HBA Driver
Jan 11 16:53:07 nd10 kernel: ACPI: PCI Interrupt 0000:07:01.0[A] -> GSI 96
(level, low) -> IRQ 169
Jan 11 16:53:07 nd10 kernel: qla2xxx 0000:07:01.0: Found an ISP2312, irq 169,
iobase 0xf8816000
Jan 11 16:53:07 nd10 kernel: qla2xxx 0000:07:01.0: Configuring PCI space...
Jan 11 16:53:07 nd10 kernel: qla2xxx 0000:07:01.0: Configure NVRAM
parameters...
Jan 11 16:53:07 nd10 kernel: qla2xxx 0000:07:01.0: Verifying loaded RISC
code...
Jan 11 16:53:07 nd10 kernel: qla2xxx 0000:07:01.0: Firmware image unavailable.
Jan 11 16:53:07 nd10 kernel: qla2xxx 0000:07:01.0: Failed to initialize adapter
Jan 11 16:53:07 nd10 kernel: Trying to free free IRQ169
Jan 11 16:53:07 nd10 kernel: ACPI: PCI interrupt for device 0000:07:01.0
disabled
Jan 11 16:53:07 nd10 kernel: ACPI: PCI interrupt for device 0000:07:01.0
disabled
Jan 11 16:53:07 nd10 kernel: ACPI: PCI Interrupt 0000:07:01.1[B] -> GSI 97
(level, low) -> IRQ 177
Jan 11 16:53:08 nd10 kernel: qla2xxx 0000:07:01.1: Found an ISP2312, irq 177,
iobase 0xf8816000
Jan 11 16:53:08 nd10 kernel: qla2xxx 0000:07:01.1: Configuring PCI space...
Jan 11 16:53:08 nd10 kernel: qla2xxx 0000:07:01.1: Configure NVRAM
parameters...
Jan 11 16:53:08 nd10 kernel: qla2xxx 0000:07:01.1: Verifying loaded RISC
code...
Jan 11 16:53:08 nd10 kernel: qla2xxx 0000:07:01.1: Firmware image unavailable.
Jan 11 16:53:08 nd10 kernel: qla2xxx 0000:07:01.1: Failed to initialize adapter
Jan 11 16:53:08 nd10 kernel: Trying to free free IRQ177
if I select the driver as:
<M> QLogic QLA2XXX Fibre Channel Support
[*] Use firmware-loader modules (DEPRECATED)
<M> Build QLogic ISP2100 firmware-module
<M> Build QLogic ISP2200 firmware-module
<M> Build QLogic ISP2300 firmware-module
<M> Build QLogic ISP2322 firmware-module
<M> Build QLogic ISP63xx firmware-module
<M> Build QLogic ISP24xx firmware-module
The problem of the comment 5 already exists.
Howerver, if I use the kernel 2.6.11.3, I've not encountered this problem.
What can I do for my system?
------- Additional Comment #8 From Luckey 2006-01-11 01:52 -------
after I type the command "fdisk -l", the logs are:
Jan 11 17:57:47 nd10 kernel: rport-10:0-0: blocked FC remote port time out:
removing target and saving binding
Jan 11 17:57:48 nd10 kernel: 10:0:0:0: SCSI error: return code = 0x10000
Jan 11 17:57:48 nd10 kernel: end_request: I/O error, dev sda, sector 0
Jan 11 17:57:48 nd10 kernel: Buffer I/O error on device sda, logical block 0
Jan 11 17:57:48 nd10 kernel: 10:0:0:0: rejecting I/O to dead device
Jan 11 17:57:48 nd10 kernel: Buffer I/O error on device sda, logical block 0
Jan 11 17:58:23 nd10 kernel: rport-11:0-0: blocked FC remote port time out:
removing target and saving binding
Jan 11 17:58:23 nd10 kernel: 11:0:0:0: SCSI error: return code = 0x10000
Jan 11 17:58:23 nd10 kernel: end_request: I/O error, dev sdb, sector 0
Jan 11 17:58:23 nd10 kernel: Buffer I/O error on device sdb, logical block 0
Jan 11 17:58:23 nd10 kernel: 11:0:0:0: rejecting I/O to dead device
Jan 11 17:58:23 nd10 kernel: Buffer I/O error on device sdb, logical block 0
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/