-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On
Behalf Of Herbert Xu
Sent: Wednesday, May 09, 2007 6:39 PM
To: Qi, Yanling
Cc: [EMAIL PROTECTED]; linux-scsi@vger.kernel.org; open-
[EMAIL PROTECTED]; [EMAIL PROTECTED]; Qi,
Yanling; [EMAIL PROTECTED]; [EMAIL
-Original Message-
From: Mike Christie [mailto:[EMAIL PROTECTED]
Qi, Yanling wrote:
Yeah, this problem should occur in the upstream open-iscsi iscsi code.
open-iscsi works very similar to linux-scsi where it just sends pages
around with sock-ops-sendpage, and it looks like sg uses
Hi All,
We have a 4GB Emulex HBA with 8.1.6 lpfc driver. The distribution is
SLES10 on PowerPc. When we do a number of target-storage-system reboots,
we see the following panic.
Has any one seen this before?
Thanks,
Yanling
Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=128 NUMA
what DID_BUSY_BUSY
would allow) for a retry.
[Qi, Yanling] The following code in the scsi_lib.c will be enough for
RDAC/MPP. BTW, why do we do wait_for = (cmd-allowed + 1) *
cmd-timeout_per_command. With a sd request, the wait_for will be 180
seconds. (SD_MAX_RETRIES=5 and SD_TIMEOUT=30 * HZ
I agree with Eric. RDAC/MPP will survive with the straight SAM BUSY
status.
--yanling
-Original Message-
From: Moore, Eric
Sent: Friday, February 02, 2007 5:59 PM
To: Edward Goggin; James Bottomley; Qi, Yanling
Cc: linux-scsi@vger.kernel.org
Subject: RE: [PATCH 0/2] : definion, code
Hi All,
I didn't follow the thread and progress of the parallel device scan at
FC LLD driver module loading time in the list. I would like to
understand the expected behavior of the parallel scan and
insmod/modprobe.
I have a configuration where I have 4 LSI FC ports. When I insmod the
Hi All,
I saw SLES10 2.6.16.21-0.8-smp kernel supports a new module parameter
remove_on_dev_loss in scsi_transport_fc. The parameter description is
remove_on_dev_loss:Boolean. When the device loss timer fires, this
variable controls whether the scsi infrastructure for the target device
is
7 matches
Mail list logo