public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Olaf Hering <olaf@aepfle.de>, Linus Torvalds <torvalds@osdl.org>,
	linux-scsi@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.18-rc6
Date: Sun, 17 Sep 2006 14:17:01 -0400	[thread overview]
Message-ID: <1158517021.17671.74.camel@fc6.xsintricity.com> (raw)
In-Reply-To: <1158501909.3485.1.camel@mulgrave.il.steeleye.com>

[-- Attachment #1: Type: text/plain, Size: 1701 bytes --]

On Sun, 2006-09-17 at 09:05 -0500, James Bottomley wrote:
> On Sun, 2006-09-17 at 07:38 +0200, Olaf Hering wrote:
> > As pointed out in private mail, this patch fixes the machine check for
> > me. Thanks Doug.
> > 
> > Maybe the AHC_ULTRA2 feature check is needed as well for other cards.
> 
> It is ... the non ULTRA2 non twin cards might not have this register
> (and if they do, it doesn't reflect the LVD/SE bus setting).
> 
> This is a pretty significant alteration, so it's not a -rc candidate,
> but I'll put it in scsi-misc and see how it works out.

No, it's present on all cards.  Reading it for signaling may not be
needed on non-ultra 2 cards (as far as LVD goes), but it won't hurt.
However, all the other places this particular register is touched in the
driver, the card is already paused.  Olaf's problem may be that this is
one of the registers that require the sequencer be paused before you
touch it.  Depending on the chipset, if you touch a pause only register,
it either pukes up like Olaf is seeing or auto pauses the chip.  I had
thought that all the Ultra2 chipsets did autopause, but maybe the
current driver disables that (and even if it did autopause, you would
still need an unpause or else the card stops until the next time
something happens that includes a pause/unpause pair).  Anyway, I asked
Olaf to try wrapping the read in an ahc_lock/unlock and pause/unpause
pair to see if it makes a difference.  We'll see.

-- 
Doug Ledford <dledford@redhat.com>
              GPG KeyID: CFBFF194
              http://people.redhat.com/dledford

Infiniband specific RPMs available at
              http://people.redhat.com/dledford/Infiniband

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-09-17 18:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0609031939100.27779@g5.osdl.org>
2006-09-05 12:26 ` Linux 2.6.18-rc6 Olaf Hering
2006-09-05 21:01   ` James Bottomley
2006-09-05 22:20     ` Benjamin Herrenschmidt
2006-09-05 23:22       ` James Bottomley
2006-09-06  0:47         ` Benjamin Herrenschmidt
2006-09-06 12:09         ` Olaf Hering
2006-09-06 11:01     ` Olaf Hering
2006-09-06 14:04       ` James Bottomley
2006-09-07  9:15         ` Olaf Hering
2006-09-07 14:04           ` James Bottomley
2006-09-16  3:47             ` Doug Ledford
2006-09-16  8:44               ` Olaf Hering
2006-09-17  5:38               ` Olaf Hering
2006-09-17 14:05                 ` James Bottomley
2006-09-17 18:17                   ` Doug Ledford [this message]
2006-09-17 18:20                 ` Doug Ledford

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=1158517021.17671.74.camel@fc6.xsintricity.com \
    --to=dledford@redhat.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=torvalds@osdl.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