From: "Grégoire Favre" <gregoire.favre@gmail.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: dino@in.ibm.com, Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: What breaks aic7xxx in post 2.6.12-rc2 ?
Date: Sun, 22 May 2005 01:22:20 +0200 [thread overview]
Message-ID: <20050521232220.GD28654@gmail.com> (raw)
In-Reply-To: <1116363971.4989.51.camel@mulgrave>
On Tue, May 17, 2005 at 04:06:11PM -0500, James Bottomley wrote:
> Well, the attached is what I'd like you to try, capturing the
> information from the initial inquiry on ... it will be quite a bit.
>
> Hopefully it will give me a clearer idea of what's going on.
I have found a way to fetch the console :-)
Against which kernel revision is your patch made for ?
Thank you very much :-)
> Thanks,
>
> James
>
> --- a/drivers/scsi/scsi_transport_spi.c
> +++ b/drivers/scsi/scsi_transport_spi.c
> @@ -669,14 +669,23 @@ spi_dv_retrain(struct scsi_request *sreq
> {
> struct spi_internal *i = to_spi_internal(sreq->sr_host->transportt);
> struct scsi_device *sdev = sreq->sr_device;
> + struct scsi_target *starget = sdev->sdev_target;
> int period = 0, prevperiod = 0;
> enum spi_compare_returns retval;
>
>
> for (;;) {
> int newperiod;
> +
> retval = compare_fn(sreq, buffer, ptr, DV_LOOPS);
>
> + if(i->f->get_period)
> + i->f->get_period(starget);
> + if (i->f->get_offset)
> + i->f->get_offset(starget);
> +
> + spi_display_xfer_agreement(starget);
> +
> if (retval == SPI_COMPARE_SUCCESS
> || retval == SPI_COMPARE_SKIP_TEST)
> break;
> @@ -765,6 +774,8 @@ spi_dv_device_internal(struct scsi_reque
> /* first set us up for narrow async */
> DV_SET(offset, 0);
> DV_SET(width, 0);
> +
> + printk("BEGINNING ASYNC, inq len = %d\n", sdev->inquiry_len);
>
> if (spi_dv_device_compare_inquiry(sreq, buffer, buffer, DV_LOOPS)
> != SPI_COMPARE_SUCCESS) {
> @@ -773,11 +784,13 @@ spi_dv_device_internal(struct scsi_reque
> return;
> }
>
> + printk("ASYNC INQUIRY SUCCEEDED\n");
> +
> /* test width */
> if (i->f->set_width && spi_max_width(starget) && sdev->wdtr) {
> i->f->set_width(sdev->sdev_target, 1);
>
> - printk("WIDTH IS %d\n", spi_max_width(starget));
> + printk("TRYING WIDE ASYNC INQUIRY\n");
>
> if (spi_dv_device_compare_inquiry(sreq, buffer,
> buffer + len,
> @@ -802,12 +815,17 @@ spi_dv_device_internal(struct scsi_reque
> if (sdev->ppr)
> len = spi_dv_device_get_echo_buffer(sreq, buffer);
>
> + printk("ECHO BUFFER HAS LEN %d\n", len);
> +
> retry:
>
> /* now set up to the maximum */
> DV_SET(offset, spi_max_offset(starget));
> DV_SET(period, spi_min_period(starget));
>
> + printk("DV SETTING TO period %d, offset %d\n", spi_min_period(starget),
> + spi_max_offset(starget));
> +
> if (len == 0) {
> SPI_PRINTK(sdev->sdev_target, KERN_INFO, "Domain Validation skipping write tests\n");
> spi_dv_retrain(sreq, buffer, buffer + len,
>
--
Grégoire Favre
next prev parent reply other threads:[~2005-05-21 23:22 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 8:58 What breaks aic7xxx in post 2.6.12-rc2 ? Grégoire Favre
2005-05-16 15:03 ` Jesper Juhl
2005-05-16 15:12 ` What breaks aic7xxx in post 2.6.12-rc2 ? (on amd64 ?) Grégoire Favre
2005-05-16 15:31 ` Jesper Juhl
2005-05-17 7:13 ` What breaks aic7xxx in post 2.6.12-rc2 ? Dinakar Guniguntala
2005-05-17 7:29 ` Andrew Morton
2005-05-17 8:34 ` Dinakar Guniguntala
2005-05-17 14:34 ` James Bottomley
2005-05-17 15:57 ` Grégoire Favre
2005-05-17 16:38 ` James Bottomley
2005-05-17 16:52 ` Grégoire Favre
2005-05-17 18:16 ` James Bottomley
2005-05-17 17:08 ` Dinakar Guniguntala
2005-05-17 18:34 ` James Bottomley
2005-05-17 19:26 ` Grégoire Favre
2005-05-17 19:50 ` James Bottomley
2005-05-17 19:56 ` Grégoire Favre
2005-05-17 21:06 ` James Bottomley
2005-05-17 22:09 ` Grégoire Favre
2005-05-17 22:14 ` James Bottomley
2005-05-21 23:22 ` Grégoire Favre [this message]
2005-05-22 13:54 ` James Bottomley
2005-05-24 15:39 ` Grégoire Favre
2005-05-26 13:19 ` James Bottomley
2005-05-26 14:35 ` Grégoire Favre
2005-05-26 14:46 ` James Bottomley
2005-05-26 17:35 ` Grégoire Favre
2005-05-30 14:38 ` James Bottomley
2005-05-30 14:51 ` Michael Tokarev
2005-05-30 14:59 ` James Bottomley
2005-05-30 15:09 ` Grégoire Favre
2005-05-30 15:34 ` James Bottomley
2005-05-30 16:01 ` Grégoire Favre
2005-05-30 18:17 ` James Bottomley
2005-05-30 19:07 ` Grégoire Favre
2005-06-06 18:17 ` James Bottomley
2005-06-07 8:57 ` Grégoire Favre
2005-06-12 15:38 ` James Bottomley
2005-06-13 14:50 ` Grégoire Favre
2005-06-13 14:59 ` James Bottomley
2005-06-13 15:05 ` Christoph Hellwig
2005-06-13 15:17 ` Grégoire Favre
2005-06-13 18:37 ` Gr�goire Favre
2005-06-13 20:50 ` James Bottomley
2005-06-13 21:33 ` Gregoire Favre
2005-06-13 21:46 ` James Bottomley
2005-06-13 21:59 ` Gregoire Favre
2005-06-13 22:04 ` James Bottomley
2005-06-13 22:25 ` Gregoire Favre
2005-06-14 2:20 ` James Bottomley
2005-06-14 9:28 ` What breaks aic7xxx in post 2.6.12-rc2 ? (fixed in 2.6.12-rc6 with patches) Gregoire Favre
2005-06-13 21:42 ` What breaks aic7xxx in post 2.6.12-rc2 ? Frank van Maarseveen
2005-06-13 22:59 ` James Bottomley
2005-06-14 21:42 ` Frank van Maarseveen
2005-06-15 12:02 ` Frank van Maarseveen
2005-06-15 14:14 ` James Bottomley
2005-06-15 20:09 ` Frank van Maarseveen
2005-06-15 20:15 ` James Bottomley
2005-06-15 20:15 ` James Bottomley
2005-06-15 20:49 ` Frank van Maarseveen
2005-05-18 9:07 ` Dinakar Guniguntala
2005-05-18 14:12 ` James Bottomley
2005-05-18 14:40 ` Dinakar Guniguntala
2005-05-19 3:07 ` K.R. Foley
2005-05-19 4:23 ` James Bottomley
2005-05-19 9:51 ` Dinakar Guniguntala
2005-05-19 23:56 ` James Bottomley
2005-05-20 1:05 ` K.R. Foley
2005-05-20 1:17 ` James Bottomley
2005-05-20 1:32 ` K.R. Foley
2005-05-20 1:33 ` James Bottomley
2005-05-20 1:40 ` James Bottomley
2005-05-20 1:54 ` K.R. Foley
2005-05-20 2:30 ` James Bottomley
2005-05-20 3:06 ` K.R. Foley
2005-05-20 10:09 ` Dinakar Guniguntala
2005-05-19 11:27 ` K.R. Foley
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=20050521232220.GD28654@gmail.com \
--to=gregoire.favre@gmail.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=dino@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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