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: Fri, 15 Sep 2006 23:47:04 -0400 [thread overview]
Message-ID: <1158378424.2661.150.camel@fc6.xsintricity.com> (raw)
In-Reply-To: <1157637874.3462.8.camel@mulgrave.il.steeleye.com>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
On Thu, 2006-09-07 at 09:04 -0500, James Bottomley wrote:
> On Thu, 2006-09-07 at 11:15 +0200, Olaf Hering wrote:
> > This does not work: ahc_linux_get_signalling: f 56f6
> >
> > echo $(( 0x56f6 & 0x00002 )) gives 2, and the ahc_inb is called.
>
> Erm, there's something else going on then: An ultra 2 card has to have
> this register. It's used to signal mode changes in
> ahc_handle_scsiint(). The piece of code in there will trigger and read
> this register for any ultra 2 + controller every time there's an error
> (just to see if the bus mode changed).
Sorry for my belated response, but this usually happens when you access
an aic chipset too soon after a chip reset. Try putting a delay before
whatever access is causing this to see if it make s difference. Common
problems include after a chip reset, touching any register will cause
the card to reset, etc.
--
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 --]
next prev parent reply other threads:[~2006-09-16 3:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 2:42 Linus Torvalds
2006-09-04 11:05 ` Gene Heskett
2006-09-04 22:31 ` Steffen Klassert
2006-09-05 0:17 ` Gene Heskett
2006-09-05 16:04 ` Alistair John Strachan
2006-09-05 20:02 ` Gene Heskett
2006-09-22 9:10 ` Konstantin Kletschke
2006-09-05 12:26 ` Olaf Hering
2006-09-05 12:45 ` maximilian attems
2006-09-05 18:56 ` Greg KH
2006-09-05 19:01 ` maximilian attems
2006-09-05 21:50 ` Greg KH
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 [this message]
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
2006-09-17 18:20 ` Doug Ledford
2006-09-12 15:04 Jody Belka
2006-09-12 22:33 ` Greg KH
2006-09-12 23:11 ` Jody Belka
2006-09-13 0:42 ` Jody Belka
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=1158378424.2661.150.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
all inboxes | Powered by JetHome®