Date: Fri, 09 Mar 2007 19:13:16 +0100 From: Ivan Voras <ivoras@fer.hr> To: freebsd-current@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Re: MFC request: QLogic 24xx FibreChannel controller Message-ID: <ess83u$j2c$1@sea.gmane.org> In-Reply-To: <45F182F2.10604@fer.hr> References: <esruhl$8s9$1@sea.gmane.org> <45F18183.7050405@FreeBSD.org> <45F182F2.10604@fer.hr>
next in thread | previous in thread | raw e-mail | index | archive | help
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: <Qlogic ISP 2422 PCI FC-AL Adapter> 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: <Qlogic ISP 2422 PCI FC-AL Adapter> 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: <IBM 1724-100 FAStT 0542> 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: <IBM 1724-100 FAStT 0542> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ess83u$j2c$1>