Date: Thu, 03 Oct 2002 16:55:14 +0000 (GMT) From: attila! <attila@hun.org> To: "Long, Scott" <Scott_Long@adaptec.com> Cc: Justin T.Gibbs <gibbs@scsiguy.com>, Poul-Henning Kamp <phk@critter.freebsd.dk>, FreeBSD 5.0-CURRENT <current@freebsd.org> Subject: RE: aic7890/91 controller Message-ID: <20021003165514.9dv685621@hun.org> In-Reply-To: <AD1F046251DCD311BA6F00204840376704A21124@aimexc02.corp.adaptec.com> References: <20021003023404.uesI9921@hun.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Sent: Thu, 3 Oct 2002 05:20:08 +0200 by marius@alchemy.franken.de
+ Sent: Wed, 2 Oct 2002 19:53:27 -0700 by Scott Long
+
+ * >
+ * > The aic 7890/91 is a dual 160 MB controller.
+ *
+ * No, the 7890/91 is 80MB/s max.
+
+ The Tyan S2462UNG has an aic-7899w.
yes, my error, too many #$* numbers after 16 hours...
+ * > Adaptec's
+ * > documentation expliciely states that the bus speed is the
+ * > rate of the _slowest_ device on the channel.
+ *
+ * No it does not.
+
+ Well, the whole bus will switch to SE-speed if a SE-device
+ is connected, guess that's what he meant.
Well, I won't argue with the man from Adaptec, but if I
use a 68 to 50 pin adaptor, the channel will not operate
at 160 MB/sec (80 x 16 bits wide) since the differential
lines are hosed. It may not have been Adaptec
documentation specific to the aic7899, but I have seen
more than one reference to the ills of mixing
high-speed differential and 50 pin SE devices. The
reasons are blatantly obvious.
+ * > Did you try
+ * > placing the cd on the B channel or vice-versa? Tyan, in
+ * > their 2642 SMP manual, recommends that the faster (and
+ * > boot) drives be placed on the B bus.
+ *
+ * I can't imagine why it would say this. Can you provide a
+ * reference?
+
+ Me neither but my 2642 additionally only boots from channel B.
Mine will boot from the A channel as long as the B
channel is unused. Also, in one test, using hints on the
B channel blew it out of the water, even with A
vacant. It will boot from A with hints, however ... more
detail later.
+ The manual is available at:
+ ftp://ftp.tyan.com/manuals/thunder/m_s2462_100.pdf
+
+ He was refering to:
+
+ "You can connect Ultra160 and Ultra2 SCSI devices to the
+ 68-pin Low Voltage Differential/Single-Ended (LVD/SE)
+ connectors on both SCSI channels. Or you can operate the
+ newer Ultra160 and Ultra2 devices at their maximum speed on
+ Channel B while at the same time using legacy SCSI devices
+ on Channel A." (page 47)
+
+ * > This worked fine for me through builds of 31 Dec; I
+ * > discovered with the 20 Feb slice that you could no
+ * > longer use both channels with CURRENT. the da drives
+ * > would boot from A or B, but when on B, the kernel would
+ * > not recognize the DVDRAM on A. The SCSI firmware
+ * > utility always reported all drives correctly on both
+ * > channels.
+ *
+ * This is the first I've heard of this problem. Can you provide
+ * more details? Did you file a PR back then? Did you post
+ * any mail to the freebsd-scsi list?
I don't track freebsd-scsi.
How much detail do you want? I tried every combination
of A/B, with/without hints, etc, ahc0 bus 0/1 and ahc0/1
bus 0, ad nauseum.
In the last several weeks I have done a check the boxes
routine ... do you want the "8x10 glossy pictures with
the circles and the arrows for the blind judge"? I'm
going to rerun the basics again either today or
tomorrow. If you want to chat, the coordinates and
phone number are in the header.
I posted a comment in March on the problem but did not
follow up, using an older version on another machine to
backup. Most everything slid after that as my stealth
carrier line was dismantled and USworst/Qworst's lines
out to the boonies are on really nasty SLCs which
reduced my access to 19200 (or less). Two months ago I
managed to put up a powerful enough uplink to hit the
local wireless two big hills --14 miles-- down the
road. Now I have 6mbs straight on to a dual 9mbs ATM
link to SLC.
+ * > I tried every combination of hints; and finally went to
+ * > a separate controller (Tekram DC395U) for the slow
+ * > peripherals. Hints worked on assigning cd0 and cd1 until
+ * > 27 Sep build and now only block them moving the devices
+ * > to cd2 and cd3 in the order found.
+ *
+ * Hints were fixed on RELENG_4 on September 22. Can you provide
+ * more information?
I don't track RELENG_4... I have been tracking CURRENT
since version 1 became 2.
FWIW, I have 27 years in UNIX, --23 in BSD starting with
version 2.something on a PDP 11/45 (maintenance hawg),
an 11/44 (sweet machine), and VAXen when the pre 4.0
code became available. At one point I had two VAXen in
my garage --raised floor and all. These were my personal
machines, replaced by SUNs and DEC/VAXstations. Among
others, I was an operating systems contractor/consultant
to Bell Labs' government division --System III, System
IV (yes, it existed and I ported it to VAX from its
native 3b20), and System V.
Ritchie and I were classmates at Harvard, and I have a
doctorate in IT... (yes, all that dates me). Yeah, and I
may mave have collected as many or more enemies than
friends.
There are only two languages: assembly and its
shorthand: C. C++ is reusable containers for
disposable programmers.
+ * > I'm going to add GEOM in a few minutes --if it stays
+ * > stable for a while, I'll go through the cable swapping
+ * > and hints routine again to try and control all devices
+ * > with the dual controller. I don't have any non-SCSI
+ * > devices.
I added the statement
#option GEOM
to the config file as requested by PHK. It went as far
as identifying the two 'da' drives and the two 'cd'
drives, then hung asking for
mountroute>
and '?' did not list 'da' or 'cd' in any form. I have
da1a mirroring da0a so it can be booted from either, but
no combination of disk1a, da0a, da0s1a, da0s4a, etc,
including the disk2a, variants sparked a response other
than a new prompt. hard boot time.
The rest of the gory details will be in the missile
[sic] to PHK.
---- addendum:
Sent: Thu, 03 Oct 2002 07:20:38 +0200 by PHK
Message-ID: <3761.1033622438@critter.freebsd.dk>
< yes, there is a problem with scsi-cd devices.
<
< can you please try this patch:
< http://phk.freebsd.dk/patch/scsi_cd.c.patch
I will also try this patch, which may affect the gory
details.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021003165514.9dv685621>