All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <heinzm@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: bug report: 3.1.0-rc4 doesn't discover my FC drives
Date: Wed, 23 Nov 2011 16:28:06 +0000	[thread overview]
Message-ID: <1322065686.2143.23.camel@o> (raw)
In-Reply-To: <1315419505.1068.43.camel@o.ww.redhat.com>

On Sun, 2011-11-20 at 17:29 -0500, David Miller wrote:
> From: Heinz Mauelshagen <heinzm@redhat.com>
> Date: Fri, 18 Nov 2011 12:20:02 +0100
> 
> > I'm not able to discover any FC-drives on my E6500
> > (same drives get discovered on an Intel box) with 3.1.0-rc4.
> > 
> > Is this a known issue?
> > Wrong driver?
> > Any hints to analyze further?
> 
> The common problem with hardware as old as these SBUS scsi controllers
> is that the SCSI protocol sequence is done by firmware and this firmware
> is 15 years old and hasn't been updated since.
> 
> So the more recent the devices are which you try to hook up to them,
> the less likely they'll be usable with such an old controller.
> 
> There's a patch below for the qlogicpti driver that will add some
> tracing to the SCSI bus probe, so you can try it out to see what might
> be happening.

Will try.

> 
> But, I wonder, are you sure the drives are attached to the qlogicpti
> card?  You say FC disks, but qlogicpti is SCSI.

If so, my wrong driver point from above applies.

> 
> The SBUS fibre-channel controllers Sun made aren't supported, we had
> to rip the old drivers we had out of the tree nearly 10 years ago
> because 1) the drivers were unmaintained and rapidly rotting and 2) we
> never were able to secure the right to distribute the firmware for
> those cards in any way so people had to extract the firmware from the
> Solaris drivers in a cumbersome way to even to try and use these
> cards.

They were in Aurora 2 still, which got released in 2006, because I could
access the drives with it IIRC. I don't remember to have been forced to
do FW tricks like that with it. Are the drivers floating around
somewhere still?

Thanks,
Heinz

> 
> diff --git a/drivers/scsi/qlogicpti.c b/drivers/scsi/qlogicpti.c
> index e40dc1c..8d01193 100644
> --- a/drivers/scsi/qlogicpti.c
> +++ b/drivers/scsi/qlogicpti.c
> @@ -48,6 +48,7 @@
>  #include <scsi/scsi_eh.h>
>  #include <scsi/scsi_tcq.h>
>  #include <scsi/scsi_host.h>
> +#include <scsi/scsi_dbg.h>
>  
>  #define MAX_TARGETS	16
>  #define MAX_LUNS	8	/* 32 for 1.31 F/W */
> @@ -1011,6 +1012,8 @@ static int qlogicpti_queuecommand_lck(struct scsi_cmnd *Cmnd, void (*done)(struc
>  	u_int out_ptr;
>  	int in_ptr;
>  
> +	pr_info("qlogicpti: Queueing command %p\n", Cmnd);
> +	scsi_print_command(Cmnd);
>  	Cmnd->scsi_done = done;
>  
>  	in_ptr = qpti->req_in_ptr;
> @@ -1169,12 +1172,19 @@ static struct scsi_cmnd *qlogicpti_intr_handler(struct qlogicpti *qpti)
>  			memcpy(Cmnd->sense_buffer, sts->req_sense_data,
>  			       SCSI_SENSE_BUFFERSIZE);
>  
> +		pr_info("qlogicpti: Completing command %p, entry_type[0x%02x]\n",
> +			Cmnd, sts->hdr.entry_type);
> +		pr_info("qlogicpti: sts->completion_status[0x%016x]\n",
> +			sts->completion_status);
> +
>  		if (sts->hdr.entry_type = ENTRY_STATUS)
>  			Cmnd->result >  			    qlogicpti_return_status(sts, qpti->qpti_id);
>  		else
>  			Cmnd->result = DID_ERROR << 16;
>  
> +		scsi_print_result(Cmnd);
> +
>  		if (scsi_bufflen(Cmnd))
>  			dma_unmap_sg(&qpti->op->dev,
>  				     scsi_sglist(Cmnd), scsi_sg_count(Cmnd),
> --
> To unsubscribe from this list: send the line "unsubscribe sparclinux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  parent reply	other threads:[~2011-11-23 16:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07 18:18 bug report: 3.1.0-rc4 doesn't discover my FC drives Heinz Mauelshagen
2011-11-18 11:20 ` Heinz Mauelshagen
2011-11-20 22:29 ` David Miller
2011-11-23 16:28 ` Heinz Mauelshagen [this message]
2011-11-23 21:04 ` Tom Callaway
2011-11-23 21:15 ` David Miller

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=1322065686.2143.23.camel@o \
    --to=heinzm@redhat.com \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.