From owner-freebsd-current@FreeBSD.ORG Fri Mar 9 18:13:57 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9DB1616A401 for ; Fri, 9 Mar 2007 18:13:57 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 2DDC313C4B8 for ; Fri, 9 Mar 2007 18:13:57 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HPjaz-0002NX-IJ for freebsd-current@freebsd.org; Fri, 09 Mar 2007 19:13:37 +0100 Received: from 83-131-163-54.adsl.net.t-com.hr ([83.131.163.54]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 Mar 2007 19:13:37 +0100 Received: from ivoras by 83-131-163-54.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 Mar 2007 19:13:37 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Fri, 09 Mar 2007 19:13:16 +0100 Lines: 61 Message-ID: References: <45F18183.7050405@FreeBSD.org> <45F182F2.10604@fer.hr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig4A27015134C55AF2912BE93E" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 83-131-163-54.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) In-Reply-To: <45F182F2.10604@fer.hr> X-Enigmail-Version: 0.94.1.2 Sender: news Cc: freebsd-stable@freebsd.org Subject: Re: MFC request: QLogic 24xx FibreChannel controller X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2007 18:13:57 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4A27015134C55AF2912BE93E Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ivan Voras wrote: > I'll try it now and report how it's doing. It works! Here's the relevant output from dmesg: isp0: port 0x4100-0x41ff mem 0xe8014000-0xe8014fff irq 20 at device 5.0 on pci3 isp0: [GIANT-LOCKED] isp0: Board Type 2422, Chip Revision 0x2, loaded F/W Revision 4.0.20 isp1: port 0x4200-0x42ff mem 0xe8015000-0xe8015fff irq 21 at device 5.1 on pci3 isp1: [GIANT-LOCKED] isp1: Board Type 2422, Chip Revision 0x2, loaded F/W Revision 4.0.20 da1 at isp0 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 100.000MB/s transfers, Tagged Queueing Enabled da1: 20480MB (41943040 512 byte sectors: 255H 63S/T 2610C) da2 at isp0 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 100.000MB/s transfers, Tagged Queueing Enabled da2: 20480MB (41943040 512 byte sectors: 255H 63S/T 2610C) I know it says up there it's "2422" but I'm sure I've read from the BIOS messages it's "2462S". Anyway, not a big problem. I'm not familiar with this hardware, but I'm curious why I see the one test drive I assigned to it twice. I seem to recall reading somewhere a discussion for Linux in which it's been mentioned that one of these should be a read-write and another "read-only" device, but is this correct? I can write to both drives. There's something else that bothers me: I'm using GEOM_LABEL and, at least in theory, there might be a problem when the same label is detected on both drives. AFAIK, currently this event is handled so that the second label gets ignored, but who knows for the future? --------------enig4A27015134C55AF2912BE93E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF8aO8ldnAQVacBcgRAv7hAKCIJZdiXvo5LgFUNhZrKFoO+h+O0QCgvTH8 hdiXMIjiMc7bN4R4Exs7tGU= =bZ5l -----END PGP SIGNATURE----- --------------enig4A27015134C55AF2912BE93E--