From: "Hans-Jürgen Lange" <Hans-Juergen.Lange@gmx.de>
To: jinhong.hu@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel 2.6.15 scsi problem
Date: Fri, 13 Jan 2006 12:07:38 +0100 [thread overview]
Message-ID: <43C789FA.3060404@gmx.de> (raw)
In-Reply-To: <5uuvR-Wc-31@gated-at.bofh.it>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=windows-1252; format=flowed, Size: 4744 bytes --]
jinhong hu wrote:
> 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.git6B 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Hello,
I run 2.6.15 and a qla2100 with the same driver qla2xxx. I have no
problem on startup.
Is <Prevent Firmware from being built> off/N ???
And I have no choice for the firmware. Mmm. Is there such a big
difference between versions? Or is my configuration file wrong/old??
BR
Hans-Juergen Lange
next parent reply other threads:[~2006-01-13 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5uuvR-Wc-31@gated-at.bofh.it>
2006-01-13 11:07 ` Hans-Jürgen Lange [this message]
2006-01-13 10:30 kernel 2.6.15 scsi problem jinhong hu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43C789FA.3060404@gmx.de \
--to=hans-juergen.lange@gmx.de \
--cc=jinhong.hu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox