From: Doug Ledford <dledford@redhat.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Graham Knap <graham.knap@rogers.com>, Horms <horms@debian.org>,
338089@bugs.debian.org, linux-scsi@vger.kernel.org
Subject: Re: Bug#338089: New aic7xxx driver fails spectacularly on 2940UW
Date: Sun, 13 Nov 2005 14:42:01 -0500 [thread overview]
Message-ID: <43779709.5070404@redhat.com> (raw)
In-Reply-To: <1131906086.3291.10.camel@mulgrave>
James Bottomley wrote:
> On Sun, 2005-11-13 at 13:03 -0500, Graham Knap wrote:
>
>>Doug Ledford <dledford@redhat.com> wrote:
>>
>>>You already said it didn't help with the problem,
>>
>>I meant that I don't think I successfully disabled DV, because the boot
>>messages were *identical*, except for the line where the kernel shows
>>the "Kernel command line".
>>
>>I had added this argument at the end of the line: aic7xxx=dv:{0}
>>
>>I've re-read "aic7xxx.txt" and I'm not sure what I'm doing wrong. If
>>you can tell me how to disable DV, I'd be happy to give it a try.
>
>
> aic7xxx.txt is out of date. The aic7xxx (and 79xx) drivers use the
> generic domain validation code now rather than the old aic specific ones
> (which is what the dv:{0} option is referring to). If you try the code
> in the prior email, I think that will disable the piece of DV that's
> causing the problem.
>
> If the test code succeeds, the problem is pretty nasty: Apparently the
> device claims DT support but in fact rejects DT in the negotiation. We
> use DT support to begin the check for an echo buffer, which starts with
> READ_BUFFERS for the descriptor. Apparently this device returns a valid
> descriptor with a reasonable echo buffer size and then promptly throws a
> wobbly when we try to use it.
>
> James
>
The device is on a non-LVD bus. Certain devices were created back when
the spec still stated that using PPR negotiation messages on a non-LVD
bus was a no-no. As the echo buffer was an addition to support DV, and
originally DV wasn't intended to be used on non-LVD busses, it might
stand to reason that this device simply is going tits up because we are
attempting to use the echo buffer while in SE mode. Checking that
PPR/DT is valid (not just between controller and device, but also given
bus mode) and only using echo buffer DV when all LVD conditions are met
would likely solve the problem (assuming that the problem is what you
are referring to).
--
Doug Ledford <dledford@redhat.com>
http://people.redhat.com/dledford
next prev parent reply other threads:[~2005-11-13 19:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051108024523.35622.qmail@web88006.mail.re2.yahoo.com>
2005-11-08 3:31 ` Bug#338089: New aic7xxx driver fails spectacularly on 2940UW Horms
2005-11-08 14:10 ` James Bottomley
2005-11-09 1:47 ` Graham Knap
2005-11-13 4:16 ` James Bottomley
2005-11-13 16:47 ` Graham Knap
2005-11-13 17:41 ` Doug Ledford
2005-11-13 17:46 ` James Bottomley
2005-11-15 0:45 ` Graham Knap
2005-11-16 2:37 ` Horms
2005-11-13 18:03 ` Graham Knap
2005-11-13 18:21 ` James Bottomley
2005-11-13 19:42 ` Doug Ledford [this message]
2005-11-13 21:51 ` James Bottomley
2005-11-14 10:15 emmanuel.fuste
-- strict thread matches above, loose matches on Subject: below --
2005-11-21 2:21 Graham Knap
2005-11-28 21:41 ` James Bottomley
2005-11-28 22:26 ` Doug Ledford
2005-12-05 1:49 ` Graham Knap
2005-12-12 17:53 ` Florian Ernst
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=43779709.5070404@redhat.com \
--to=dledford@redhat.com \
--cc=338089@bugs.debian.org \
--cc=James.Bottomley@SteelEye.com \
--cc=graham.knap@rogers.com \
--cc=horms@debian.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 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.