From owner-freebsd-scsi Sun Apr 23 1:31:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front2.grolier.fr (front2.grolier.fr [194.158.96.52]) by hub.freebsd.org (Postfix) with ESMTP id 88AD137B962; Sun, 23 Apr 2000 01:31:54 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from ppp-168-138.villette.club-internet.fr (ppp-168-138.villette.club-internet.fr [195.36.168.138]) by front2.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id KAA14640; Sun, 23 Apr 2000 10:31:51 +0200 (MET DST) Date: Sun, 23 Apr 2000 10:06:03 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Jean-Marc Zucconi Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sym driver: new experimental version (multi-firmware support) In-Reply-To: <200004222041.NAA38107@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 22 Apr 2000, Jean-Marc Zucconi wrote: > >>>>> G=E9rard Roudier writes: >=20 > > Add support for early NCR53C8XX PCI-SCSI chips: >=20 > > - NCR53C810 revision <=3D 15 >=20 > It does not work for me. The card is not probed. As I wrote, I haven't currently a 810 rev < 15 installed on my home machine and I did the testing by hacking the driver device tables for=20 a 810a and a 895 to be driven by the NCR generic firmware instead. I have a machine at work under FreeBSD with a 810 rev. 2 and it is planned = =20 to test the driver on this machine on next tuesday. Looking into the detection code, I see no obvious reason for the driver not to accept your controller. If you have time for, you may add some `printf' in sym_find_pci_chip() and sym_find_firmware() in order to track the problem. sym_find_pci_chip() detection loop: ----------------------------------- Printing device ids and revisions ids before the `if's can help. =2E.. =09for (i =3D 0; i < sym_pci_num_devs; i++) { =09=09chip =3D &sym_pci_dev_table[i]; =09=09if (device_id !=3D chip->device_id) =09=09=09continue; =09=09if (revision > chip->revision_id) =09=09=09continue; =09=09return chip; =09} =2E.. sym_find_firmware is a pretty trivial function. ----------------------------------------------- /* * Find the most appropriate firmware for a chip. */ static struct sym_fw *=20 sym_find_firmware(struct sym_pci_chip *chip) { =09if (chip->features & FE_LDSTR) =09=09return &sym_fw2; #ifdef=09SYM_CONF_GENERIC_SUPPORT =09else if (!(chip->features & (FE_PFEN|FE_NOPM|FE_64BIT))) =09=09return &sym_fw1; #endif =09else =09=09return 0; } G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 23 1:47:57 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144]) by hub.freebsd.org (Postfix) with ESMTP id 52F9237B8A0; Sun, 23 Apr 2000 01:47:54 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay01.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000423084801.KDWC485.relay01@chello.nl>; Sun, 23 Apr 2000 10:48:01 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id KAA13077; Sun, 23 Apr 2000 10:47:52 +0200 (CEST) (envelope-from wkb) Date: Sun, 23 Apr 2000 10:47:51 +0200 From: Wilko Bulte To: Jean-Marc Zucconi Cc: groudier@club-internet.fr, freebsd-scsi@FreeBSD.ORG Subject: Re: sym driver: new experimental version (multi-firmware support) Message-ID: <20000423104751.B12885@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: <200004222041.NAA38107@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 1.0.1i In-Reply-To: <200004222041.NAA38107@freefall.freebsd.org>; from jmz@FreeBSD.ORG on Sat, Apr 22, 2000 at 01:41:35PM -0700 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by chello.nl id KAA13077 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Apr 22, 2000 at 01:41:35PM -0700, Jean-Marc Zucconi wrote: I think I have missed the original message. Can someone please repost the pointer to the new driver? I have an Alpha machine with an early NCR810 that I'd like to test on. Wilko > >>>>> G=E9rard Roudier writes: >=20 > > Add support for early NCR53C8XX PCI-SCSI chips: >=20 > > - NCR53C810 revision <=3D 15 >=20 > It does not work for me. The card is not probed. >=20 > Jean-Marc >=20 > --=20 > Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.org >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message ---end quoted text--- --=20 Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 23 7:12:49 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id 01BF737B586 for ; Sun, 23 Apr 2000 07:12:46 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000423140435.QXJH22628.relay02@chello.nl>; Sun, 23 Apr 2000 16:04:35 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id QAA14510; Sun, 23 Apr 2000 16:04:38 +0200 (CEST) (envelope-from wkb) Date: Sun, 23 Apr 2000 16:04:38 +0200 From: Wilko Bulte To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: FreeBSD SCSI hackers Subject: Re: sym driver: new experimental version (multi-firmware support) Message-ID: <20000423160438.A14494@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: <200004222041.NAA38107@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from groudier@club-internet.fr on Sun, Apr 23, 2000 at 10:06:03AM +0200 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The Aspen Alpine alphabox appears to by happy with the new sym driver. At least the chips gets recognised and appears to work well (it is the boot/root SCSI bus). I'm doing a buildworld to stress it a bit more. Gerard, if you want me to try something particular please let me know. Thanks, Wilko -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 23 8:33: 2 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front2m.grolier.fr (front2m.grolier.fr [195.36.216.52]) by hub.freebsd.org (Postfix) with ESMTP id BD37137B58C for ; Sun, 23 Apr 2000 08:32:56 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from ppp-172-170.villette.club-internet.fr (ppp-172-170.villette.club-internet.fr [195.36.172.170]) by front2m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id RAA15708; Sun, 23 Apr 2000 17:24:06 +0200 (MET DST) Date: Sun, 23 Apr 2000 17:07:06 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: wc.bulte@chello.nl Cc: FreeBSD SCSI hackers Subject: Re: sym driver: new experimental version (multi-firmware support) In-Reply-To: <20000423160438.A14494@yedi.wbnet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 23 Apr 2000, Wilko Bulte wrote: > The Aspen Alpine alphabox appears to by happy with the new sym driver. At > least the chips gets recognised and appears to work well (it is the > boot/root SCSI bus). Thanks a lot for having tried this new driver version. I am very glad of your success report. On recent O/Ses, the boot does so many IOs that a driver that succeeds the boot has every chance to be just rock solid. :-) =20 > I'm doing a buildworld to stress it a bit more. Gerard, if you want me to > try something particular please let me know. A build world is a great test. My preliminary testings have been more IO intensive, but were probably not as relevant for driver testing. By the way, the only SCSI feature I am unable to test is support for multi-lun device since I haven't any device of this kind. If you have this sort of device, you may want to give it a try. Regards, G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 23 8:56:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144]) by hub.freebsd.org (Postfix) with ESMTP id ABE4337B690 for ; Sun, 23 Apr 2000 08:56:11 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay01.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000423155615.DDG5152.relay01@chello.nl>; Sun, 23 Apr 2000 17:56:15 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id RAA30426; Sun, 23 Apr 2000 17:56:06 +0200 (CEST) (envelope-from wkb) Date: Sun, 23 Apr 2000 17:56:06 +0200 From: Wilko Bulte To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: wc.bulte@chello.nl, FreeBSD SCSI hackers Subject: Re: sym driver: new experimental version (multi-firmware support) Message-ID: <20000423175606.B30392@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: <20000423160438.A14494@yedi.wbnet> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 1.0.1i In-Reply-To: ; from groudier@club-internet.fr on Sun, Apr 23, 2000 at 05:07:06PM +0200 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by chello.nl id RAA30426 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Apr 23, 2000 at 05:07:06PM +0200, G=E9rard Roudier wrote: > On Sun, 23 Apr 2000, Wilko Bulte wrote: >=20 > > The Aspen Alpine alphabox appears to by happy with the new sym driver= . At > > least the chips gets recognised and appears to work well (it is the > > boot/root SCSI bus). >=20 > Thanks a lot for having tried this new driver version. I am very glad o= f > your success report. :-) > > I'm doing a buildworld to stress it a bit more. Gerard, if you want m= e to > > try something particular please let me know. >=20 > A build world is a great test. My preliminary testings have been more I= O > intensive, but were probably not as relevant for driver testing. By the > way, the only SCSI feature I am unable to test is support for multi-lun > device since I haven't any device of this kind. If you have this sort o= f > device, you may want to give it a try. Actually I do. I have a Pioneer DRM604X 6 CD changer. And that one gave t= he 'old' ncr driver fits when I tried to use it on an old ncr810 card/chip. I'll give it a try as soon as the buildworld finishes. W/ --=20 Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 23 8:57:18 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id BE2E137B690 for ; Sun, 23 Apr 2000 08:57:14 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000423155704.RMTA22628.relay02@chello.nl>; Sun, 23 Apr 2000 17:57:04 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id RAA30451; Sun, 23 Apr 2000 17:57:07 +0200 (CEST) (envelope-from wkb) Date: Sun, 23 Apr 2000 17:57:07 +0200 From: Wilko Bulte To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: wc.bulte@chello.nl, FreeBSD SCSI hackers Subject: Re: sym driver: new experimental version (multi-firmware support) Message-ID: <20000423175707.A30437@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: <20000423160438.A14494@yedi.wbnet> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 1.0.1i In-Reply-To: ; from groudier@club-internet.fr on Sun, Apr 23, 2000 at 05:07:06PM +0200 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by chello.nl id RAA30451 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Apr 23, 2000 at 05:07:06PM +0200, G=E9rard Roudier wrote: > > boot/root SCSI bus). >=20 > Thanks a lot for having tried this new driver version. I am very glad o= f > your success report. Additional question: how can I determine what 810 chip revision I'm now running on? Might be interesting to know. Wilko --=20 Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 23 10:32:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144]) by hub.freebsd.org (Postfix) with ESMTP id 2BEE737B74F for ; Sun, 23 Apr 2000 10:32:30 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay01.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000423173237.NML5152.relay01@chello.nl>; Sun, 23 Apr 2000 19:32:37 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id TAA30936; Sun, 23 Apr 2000 19:32:28 +0200 (CEST) (envelope-from wkb) Date: Sun, 23 Apr 2000 19:32:28 +0200 From: Wilko Bulte To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: wc.bulte@chello.nl, FreeBSD SCSI hackers Subject: Re: sym driver: new experimental version (multi-firmware support) Message-ID: <20000423193228.A30887@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: <20000423160438.A14494@yedi.wbnet> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 1.0.1i In-Reply-To: ; from groudier@club-internet.fr on Sun, Apr 23, 2000 at 05:07:06PM +0200 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by chello.nl id TAA30936 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Apr 23, 2000 at 05:07:06PM +0200, G=E9rard Roudier wrote: > On Sun, 23 Apr 2000, Wilko Bulte wrote: > > I'm doing a buildworld to stress it a bit more. Gerard, if you want m= e to > > try something particular please let me know. >=20 > A build world is a great test. My preliminary testings have been more I= O > intensive, but were probably not as relevant for driver testing. By the > way, the only SCSI feature I am unable to test is support for multi-lun > device since I haven't any device of this kind. If you have this sort o= f > device, you may want to give it a try. Hello Gerard, The buildworld completed just fine (ok, the /usr/obj filled up too early=20 but I cannot blame sym for that ;-). I subsequently tested my 6 CD Pionee= r changer and that also works like a charm. Great job! Wilko --=20 Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 23 11:31:43 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id BE13737B9B4 for ; Sun, 23 Apr 2000 11:31:40 -0700 (PDT) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id UAA04767 for freebsd-scsi@freebsd.org; Sun, 23 Apr 2000 20:31:39 +0200 (CEST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id TAA45564 for freebsd-scsi@freebsd.org; Sun, 23 Apr 2000 19:26:34 +0200 (CEST) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: sym driver: new experimental version (multi-firmware support) Date: 23 Apr 2000 19:26:34 +0200 Message-ID: <8dvboa$1cfe$1@bigeye.rhein-neckar.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit To: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just rebuilt the kernel to include the experimental sym driver on an AXPpci33 (with on-board 53C810) running 4.0-STABLE. The box has come up again successfully: sym0: <810> port 0x10000-0x100ff mem 0x81014000-0x810140ff irq 11 at device 6.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: interrupting at ISA irq 11 ... cd0 at sym0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) To create a bit of disk load I did a cvsup update of /usr/ports. No problems. Kudos to Gérard! -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 23 11:54:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 4849937B52A; Sun, 23 Apr 2000 11:54:13 -0700 (PDT) (envelope-from jmz@FreeBSD.org) Received: (from jmz@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id LAA32131; Sun, 23 Apr 2000 11:54:13 -0700 (PDT) (envelope-from jmz@FreeBSD.org) Date: Sun, 23 Apr 2000 11:54:13 -0700 (PDT) Message-Id: <200004231854.LAA32131@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: jmz set sender to jmz@FreeBSD.org using -f From: Jean-Marc Zucconi To: groudier@club-internet.fr Cc: freebsd-scsi@FreeBSD.ORG In-reply-to: (message from G=?ISO-8859-1?Q?=E9rard_Roudier_on_Sun=2C_23_Apr_2000_10=3A06=3A03_+0200_=28CEST=29=29?= Subject: Re: sym driver: new experimental version (multi-firmware support) X-Mailer: Emacs References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> G=E9rard Roudier writes: > On Sat, 22 Apr 2000, Jean-Marc Zucconi wrote: >> >>>>> G=E9rard Roudier writes: >> >> > Add support for early NCR53C8XX PCI-SCSI chips: >> >> > - NCR53C810 revision <=3D 15 >> >> It does not work for me. The card is not probed. > As I wrote, I haven't currently a 810 rev < 15 installed on my home > machine and I did the testing by hacking the driver device tables for > a 810a and a 895 to be driven by the NCR generic firmware instead. > I have a machine at work under FreeBSD with a 810 rev. 2 and it is pla= nned > to test the driver on this machine on next tuesday. > Looking into the detection code, I see no obvious reason for the drive= r > not to accept your controller. If you have time for, you may add some > `printf' in sym_find_pci_chip() and sym_find_firmware() in order to tr= ack > the problem. I have discovered that moving files from /sys/dev/sym-1.5.0-20000421/ to /sys/dev/sym/ gives better results :-) sym0: <810> port 0xe400-0xe4ff mem 0xe3800000-0xe38000ff irq 10 at device= 11.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking Merci ! Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 23 12: 7:10 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from c014.sfo.cp.net (c014-h023.c014.sfo.cp.net [209.228.12.87]) by hub.freebsd.org (Postfix) with SMTP id 481C637BA81 for ; Sun, 23 Apr 2000 12:07:07 -0700 (PDT) (envelope-from shiratsoi@flashcom.net) Received: (cpmta 3962 invoked from network); 23 Apr 2000 12:07:06 -0700 Received: from 216-59-11-226.usa.flashcom.net (HELO flashcom.net) (216.59.11.226) by smtp.flashcom.net with SMTP; 23 Apr 2000 12:07:06 -0700 X-Sent: 23 Apr 2000 19:07:06 GMT Message-ID: <39034A67.22044E2D@flashcom.net> Date: Sun, 23 Apr 2000 12:09:27 -0700 From: Alkis Evlogimenos Organization: UC Berkeley X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Mylex Flashpoint BT-950 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Are there any drivers in development for this model? Thanks. Alkis Evlogimenos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 23 12:36:46 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 8221F37B75D for ; Sun, 23 Apr 2000 12:36:41 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA05301; Sun, 23 Apr 2000 13:36:33 -0600 (MDT) (envelope-from ken) Date: Sun, 23 Apr 2000 13:36:33 -0600 From: "Kenneth D. Merry" To: Alkis Evlogimenos Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Mylex Flashpoint BT-950 Message-ID: <20000423133633.A5249@panzer.kdm.org> References: <39034A67.22044E2D@flashcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <39034A67.22044E2D@flashcom.net>; from shiratsoi@flashcom.net on Sun, Apr 23, 2000 at 12:09:27PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Apr 23, 2000 at 12:09:27 -0700, Alkis Evlogimenos wrote: > Are there any drivers in development for this model? > Justin Gibbs was planning on doing a driver, but I don't think he's gotten around to it. If you want to find out the status of it, just send him mail. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 23 17:25:57 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from yam.ex.itc.keio.ac.jp (yam.ex.itc.keio.ac.jp [131.113.212.100]) by hub.freebsd.org (Postfix) with SMTP id 8DCC437B886 for ; Sun, 23 Apr 2000 17:25:47 -0700 (PDT) (envelope-from hiroyu-y@ex.itc.keio.ac.jp) Received: (qmail 98240 invoked by uid 1001); 24 Apr 2000 00:30:38 -0000 Date: 24 Apr 2000 00:30:38 -0000 Message-ID: <20000424003038.98239.qmail@yam.ex.itc.keio.ac.jp> To: mkes@ra.rockwell.com Cc: freebsd-scsi@freebsd.org Subject: Re: 4.0 RELEASE on HP Kayak XU800 and HP NetServer LH 3000 In-Reply-To: Your message of "Fri, 21 Apr 2000 22:36:24 JST". From: hiroyu-y@ex.itc.keio.ac.jp (Hiroyuki Yamagai) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To my knowledge that AIC-7892 is a dual channel SCSI Controler, with BUS A & B. On FreeBSD, if the B Bus BIOS is set to [Reset SCSI bus at IC Initialization -- enable] the system will panic as you posted. If, disabled it'll boot with out problem. #Linux 2.2X and Solaris 7&8 is not effected by this. By the way, when did you purchace your HP NetServer LH 3000? I belevie that the new models has integrated RAID Controler instead of AMI MegaRAID 1400 as on older LH3000. I'm interested in what Serise of MegaRaid is on th New LH3000. Can you post or mail me dmesg of your LH3000? #Has any body had luck booting from new AMI 1500/1600? Regards on message mkes@ra.rockwell.com wrote, >> Hi >> >> I have HP Kayak XU 800 with Adaptec AIC 7892 SCSI controller. >> Any attempt to install 4.0 Release ends up with a crash. The installation >> works fine until it starts copying distributions on the disk. It usually >> copies some files of the /bin part of the distrubution and than the >> machine hangs. >> >> Here is what I suceeded to put down before the screen scrolled away. >> >> ahc:A:0: no active SCB for reconnecting target - issuing BUS DEVICE RESET >> SAVED_ICL == 0x0, ARG_1 == 0x1d, SEQ_FLAGS == 0x40 >> >> ... some more error messages (I wasn't so fast) ... and finaly >> >> panic page fault >> >> syncing disc ... 709 709 709 ... >> >> ahc0: Interrupted for status of 0??? >> ahc0: WARNING no command for scb 29 (cmdcpplt) >> OUTPOS = 0 >> >> After that a hard reset was necessary. >> >> ---------------- >> >> On the other hand I suceeded to install 4.0 R on HP NetServer LH 3000, >> which is quite new model with AIC 7880 and AMI MegaRAID. >> I have 2 arrays defined - one RAID 0 (1x 9GB disk) and one RAID 5 (3x 18 >> GB disk) >> The only problem I experienced is that if I tried to partition these 2 >> logical disks as fully dedicated for FreeBSD the installation completed OK >> but the machine didn't boot saying "Read error" >> If I chose the partitionig as "remain cooperative with other OS" (even if >> there is no other OS) the problem disappeared. >> I think this observation can help to others. >> >> So now our new main fileserver runs FreeBSD (as well as any other server in >> our office) :-) >> >> Regards >> >> Mira >> >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-scsi" in the body of the message >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 23 19:11:38 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (law2-f192.hotmail.com [216.32.181.192]) by hub.freebsd.org (Postfix) with SMTP id 3157837B735 for ; Sun, 23 Apr 2000 19:11:37 -0700 (PDT) (envelope-from mut3x@hotmail.com) Received: (qmail 31741 invoked by uid 0); 24 Apr 2000 02:11:36 -0000 Message-ID: <20000424021136.31740.qmail@hotmail.com> Received: from 206.165.200.116 by www.hotmail.com with HTTP; Sun, 23 Apr 2000 19:11:36 PDT X-Originating-IP: [206.165.200.116] From: "Mutex Records USA" To: freebsd-scsi@freebsd.org Subject: Mylex Extremeraid 1100 booting? Date: Sun, 23 Apr 2000 19:11:36 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am tinkering with a Mylex Extremeraid 1100 card, on one of those Supermicro motherboards (no scsi on board, just on the card...) The Mylex card reports it's self as DAC1164P, FW Ver. 5.07-79 The BIOS seemed to format the RAID as RAID5 (3 Seagate Barracuda drives, one per interface) and the FTP install seemed to go just fine. However... When I come back up for 'first boot', the system seems to hang at the Freebsd Bootloader prompt. F1 FreeBSD... and it hangs. Any ideas? Thanks, Adam ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 23 19:55:54 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (adsl-63-202-179-64.dsl.snfc21.pacbell.net [63.202.179.64]) by hub.freebsd.org (Postfix) with ESMTP id 0A3DD37B718 for ; Sun, 23 Apr 2000 19:55:52 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA56743; Sun, 23 Apr 2000 20:03:05 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004240303.UAA56743@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Mutex Records USA" Cc: freebsd-scsi@freebsd.org Subject: Re: Mylex Extremeraid 1100 booting? In-reply-to: Your message of "Sun, 23 Apr 2000 19:11:36 PDT." <20000424021136.31740.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Apr 2000 20:03:05 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am tinkering with a Mylex Extremeraid 1100 card, on one of those > Supermicro motherboards (no scsi on board, just on the card...) > The Mylex card reports it's self as DAC1164P, FW Ver. 5.07-79 > > The BIOS seemed to format the RAID as RAID5 (3 Seagate Barracuda drives, one > per interface) and the FTP install seemed to go just fine. > > However... > > When I come back up for 'first boot', the system seems to hang at the > Freebsd Bootloader prompt. F1 FreeBSD... and it hangs. > > Any ideas? Try flipping the geometry mode in the controller's BIOS setup; it needs to match what was detected when you install (except when you've had another OS on there and sysinstall gets it wrong). There may be issues with this though - to be safe, use the 2GB mode all around. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 24 8:15: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id D788B37BBBC for ; Mon, 24 Apr 2000 08:15:01 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 70078 invoked by uid 1001); 24 Apr 2000 15:15:00 +0000 (GMT) To: freebsd-scsi@freebsd.org Subject: Safe mounting of one file system on multiple hosts? From: sthaug@nethelp.no X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 24 Apr 2000 17:15:00 +0200 Message-ID: <70070.956589300@verdi.nethelp.no> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a RAID system from Nexsan (www.nexsan.com), which is basically two CMD CDR-5644 controllers in a hot-standby configuration. The system has two host channels, and two disk channels. I have two different hosts connected to the two hosts channels. Normally, I would configure two (or more) RAID sets, and have each RAID set dedicated to one host (visible on only one of the host channels). Each RAID set appears to the host as one disk - and can be partitioned, newfs'ed etc. with normal FreeBSD tools. This works fine. However, I also have the *option* of making all RAID sets visible on *both* host channels. I don't want to try read/write mounting one RAID set on two hosts - but can I safely read/write mount the RAID set (its corresponding file system(s)) on one host, and mount it readonly on the other host? I guess the basic question is: Will a readonly mount of a file system lead to *zero* writes to this file system? Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 24 9:20:39 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 0DC0237B635 for ; Mon, 24 Apr 2000 09:20:26 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA10619; Mon, 24 Apr 2000 10:20:05 -0600 (MDT) (envelope-from ken) Date: Mon, 24 Apr 2000 10:20:05 -0600 From: "Kenneth D. Merry" To: sthaug@nethelp.no Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Safe mounting of one file system on multiple hosts? Message-ID: <20000424102005.A10563@panzer.kdm.org> References: <70070.956589300@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <70070.956589300@verdi.nethelp.no>; from sthaug@nethelp.no on Mon, Apr 24, 2000 at 05:15:00PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Apr 24, 2000 at 17:15:00 +0200, sthaug@nethelp.no wrote: > I have a RAID system from Nexsan (www.nexsan.com), which is basically > two CMD CDR-5644 controllers in a hot-standby configuration. The system > has two host channels, and two disk channels. I have two different hosts > connected to the two hosts channels. > > Normally, I would configure two (or more) RAID sets, and have each RAID > set dedicated to one host (visible on only one of the host channels). > Each RAID set appears to the host as one disk - and can be partitioned, > newfs'ed etc. with normal FreeBSD tools. This works fine. > > However, I also have the *option* of making all RAID sets visible on > *both* host channels. I don't want to try read/write mounting one RAID > set on two hosts - but can I safely read/write mount the RAID set (its > corresponding file system(s)) on one host, and mount it readonly on the > other host? I guess the basic question is: Will a readonly mount of a > file system lead to *zero* writes to this file system? I would recommend that you test out the controller carefully under high load conditions if you have more than one array configured on it. There have been a number of reports (see the list archives) about problems with CMD RAID arrays with more than one LUN (i.e. more than one array) configured. As for the mount question, it should work, but I haven't actually done it, so I can't say for sure. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 24 9:33:44 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CD18D37B731 for ; Mon, 24 Apr 2000 09:33:42 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA04152; Mon, 24 Apr 2000 09:32:24 -0700 Date: Mon, 24 Apr 2000 09:33:06 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: sthaug@nethelp.no, freebsd-scsi@FreeBSD.ORG Subject: Re: Safe mounting of one file system on multiple hosts? In-Reply-To: <20000424102005.A10563@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > As for the mount question, it should work, but I haven't actually done it, > so I can't say for sure. Better pick a filesystem that doens't cache info. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 24 9:59:24 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id A610837B616 for ; Mon, 24 Apr 2000 09:59:18 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000424165911.YYDT22628.relay02@chello.nl>; Mon, 24 Apr 2000 18:59:11 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id SAA36665; Mon, 24 Apr 2000 18:59:15 +0200 (CEST) (envelope-from wkb) Date: Mon, 24 Apr 2000 18:59:15 +0200 From: Wilko Bulte To: Matthew Jacob Cc: "Kenneth D. Merry" , sthaug@nethelp.no, freebsd-scsi@FreeBSD.ORG Subject: Re: Safe mounting of one file system on multiple hosts? Message-ID: <20000424185915.B36639@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: <20000424102005.A10563@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from mjacob@feral.com on Mon, Apr 24, 2000 at 09:33:06AM -0700 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Apr 24, 2000 at 09:33:06AM -0700, Matthew Jacob wrote: > > > As for the mount question, it should work, but I haven't actually done it, > > so I can't say for sure. > > Better pick a filesystem that doens't cache info. Even better: write a cluster filesystem ;-) Or arrange for one of the machines to do block serving via a high speed network link for the other one. In case of a server death the survivor takes over for both. FreeBSD clusters would be COOL(tm). -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 24 10: 2: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id EF23837BB6F for ; Mon, 24 Apr 2000 10:02:03 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id JAA08902; Mon, 24 Apr 2000 09:59:20 -0700 (PDT) Message-Id: <200004241659.JAA08902@implode.root.com> To: sthaug@nethelp.no Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Safe mounting of one file system on multiple hosts? In-reply-to: Your message of "Mon, 24 Apr 2000 17:15:00 +0200." <70070.956589300@verdi.nethelp.no> From: David Greenman Reply-To: dg@root.com Date: Mon, 24 Apr 2000 09:59:20 -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I have a RAID system from Nexsan (www.nexsan.com), which is basically >two CMD CDR-5644 controllers in a hot-standby configuration. The system >has two host channels, and two disk channels. I have two different hosts >connected to the two hosts channels. > >Normally, I would configure two (or more) RAID sets, and have each RAID >set dedicated to one host (visible on only one of the host channels). >Each RAID set appears to the host as one disk - and can be partitioned, >newfs'ed etc. with normal FreeBSD tools. This works fine. > >However, I also have the *option* of making all RAID sets visible on >*both* host channels. I don't want to try read/write mounting one RAID >set on two hosts - but can I safely read/write mount the RAID set (its >corresponding file system(s)) on one host, and mount it readonly on the >other host? I guess the basic question is: Will a readonly mount of a >file system lead to *zero* writes to this file system? It might work if you use softupdates, but it won't work if you don't since the state of the on-disk filesystem metadata isn't always going to be consistent due to defered writes. The read-only machine will also have stuff in it's own cache which won't be kept updated and will certainly interfere with the correct view of things (which probably means that it won't work with softupdates, either). Of course, if both servers mount it read-only, then you'll be fine. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 24 11:32:51 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 0B6F737B731 for ; Mon, 24 Apr 2000 11:32:49 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 72993 invoked by uid 1001); 24 Apr 2000 18:32:47 +0000 (GMT) To: ken@kdm.org Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Safe mounting of one file system on multiple hosts? From: sthaug@nethelp.no In-Reply-To: Your message of "Mon, 24 Apr 2000 10:20:05 -0600" References: <20000424102005.A10563@panzer.kdm.org> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 24 Apr 2000 20:32:46 +0200 Message-ID: <72991.956601166@verdi.nethelp.no> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I would recommend that you test out the controller carefully under high > load conditions if you have more than one array configured on it. > > There have been a number of reports (see the list archives) about problems > with CMD RAID arrays with more than one LUN (i.e. more than one array) > configured. I have two LUNs on one of the host channels, and I can easily provoke problems here (running a few copies of bonnie, for instance) with tagged queueing enabled. If I turn off tagged queueing on the host channel with multiple LUNs (as suggested by Oliver Blasnik ), there are no problems. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 24 13:48:47 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id EB32B37B8E8 for ; Mon, 24 Apr 2000 13:48:29 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA05169; Mon, 24 Apr 2000 13:47:39 -0700 Date: Mon, 24 Apr 2000 13:48:22 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: sthaug@nethelp.no Cc: ken@kdm.org, freebsd-scsi@FreeBSD.ORG Subject: Re: Safe mounting of one file system on multiple hosts? In-Reply-To: <72991.956601166@verdi.nethelp.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Define 'problems'. On Mon, 24 Apr 2000 sthaug@nethelp.no wrote: > > I would recommend that you test out the controller carefully under high > > load conditions if you have more than one array configured on it. > > > > There have been a number of reports (see the list archives) about problems > > with CMD RAID arrays with more than one LUN (i.e. more than one array) > > configured. > > I have two LUNs on one of the host channels, and I can easily provoke > problems here (running a few copies of bonnie, for instance) with > tagged queueing enabled. If I turn off tagged queueing on the host > channel with multiple LUNs (as suggested by Oliver Blasnik > ), there are no problems. > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 24 13:56:40 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 7430837BBE5 for ; Mon, 24 Apr 2000 13:56:32 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 75154 invoked by uid 1001); 24 Apr 2000 20:56:29 +0000 (GMT) To: mjacob@feral.com Cc: ken@kdm.org, freebsd-scsi@FreeBSD.ORG Subject: Re: Safe mounting of one file system on multiple hosts? From: sthaug@nethelp.no In-Reply-To: Your message of "Mon, 24 Apr 2000 13:48:22 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 24 Apr 2000 22:56:29 +0200 Message-ID: <75152.956609789@verdi.nethelp.no> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Define 'problems'. Like this: (da4:ahc2:0:0:2): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xa (da4:ahc2:0:0:2): Queuing a BDR SCB (da4:ahc2:0:0:2): Bus Device Reset Message Sent (da4:ahc2:0:0:2): no longer in timeout, status = 34b ahc2: Bus Device Reset on A:0. 10 SCBs aborted (da4:ahc2:0:0:2): SCB 0x2b - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x8 (da4:ahc2:0:0:2): Queuing a BDR SCB (da4:ahc2:0:0:2): Bus Device Reset Message Sent (da4:ahc2:0:0:2): no longer in timeout, status = 34b ahc2: Bus Device Reset on A:0. 26 SCBs aborted (da4:ahc2:0:0:2): SCB 0x19 - timed out in datain phase, SEQADDR == 0x5e (da4:ahc2:0:0:2): Other SCB Timeout (da4:ahc2:0:0:2): SCB 0x17 - timed out in datain phase, SEQADDR == 0x5e (da4:ahc2:0:0:2): Other SCB Timeout Unexpected busfree. LASTPHASE == 0x40 SEQADDR == 0x5e ahc2:A:0: no active SCB for reconnecting target - issuing BUS DEVICE RESET SAVED_TCL == 0x1, ARG_1 == 0x15, SEQ_FLAGS == 0x0 ahc2: Bus Device Reset on A:0. 14 SCBs aborted As I mentioned, if I turn off tagged queuing on the host channel with the two LUNs, everything seems to work just fine - but somewhat slower for certain operations, of course. Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > On Mon, 24 Apr 2000 sthaug@nethelp.no wrote: > > > > I would recommend that you test out the controller carefully under high > > > load conditions if you have more than one array configured on it. > > > > > > There have been a number of reports (see the list archives) about problems > > > with CMD RAID arrays with more than one LUN (i.e. more than one array) > > > configured. > > > > I have two LUNs on one of the host channels, and I can easily provoke > > problems here (running a few copies of bonnie, for instance) with > > tagged queueing enabled. If I turn off tagged queueing on the host > > channel with multiple LUNs (as suggested by Oliver Blasnik > > ), there are no problems. > > > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 24 13:58:42 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CC9BC37BB88 for ; Mon, 24 Apr 2000 13:58:38 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA05250; Mon, 24 Apr 2000 13:57:49 -0700 Date: Mon, 24 Apr 2000 13:58:33 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: sthaug@nethelp.no Cc: ken@kdm.org, freebsd-scsi@FreeBSD.ORG Subject: Re: Safe mounting of one file system on multiple hosts? In-Reply-To: <75152.956609789@verdi.nethelp.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Huh, well, this looks more like a problem with the target than anything else, but it's hard to say. On Mon, 24 Apr 2000 sthaug@nethelp.no wrote: > > Define 'problems'. > > Like this: > > (da4:ahc2:0:0:2): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xa > (da4:ahc2:0:0:2): Queuing a BDR SCB > (da4:ahc2:0:0:2): Bus Device Reset Message Sent > (da4:ahc2:0:0:2): no longer in timeout, status = 34b > ahc2: Bus Device Reset on A:0. 10 SCBs aborted > (da4:ahc2:0:0:2): SCB 0x2b - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x8 > (da4:ahc2:0:0:2): Queuing a BDR SCB > (da4:ahc2:0:0:2): Bus Device Reset Message Sent > (da4:ahc2:0:0:2): no longer in timeout, status = 34b > ahc2: Bus Device Reset on A:0. 26 SCBs aborted > (da4:ahc2:0:0:2): SCB 0x19 - timed out in datain phase, SEQADDR == 0x5e > (da4:ahc2:0:0:2): Other SCB Timeout > (da4:ahc2:0:0:2): SCB 0x17 - timed out in datain phase, SEQADDR == 0x5e > (da4:ahc2:0:0:2): Other SCB Timeout > Unexpected busfree. LASTPHASE == 0x40 > SEQADDR == 0x5e > ahc2:A:0: no active SCB for reconnecting target - issuing BUS DEVICE RESET > SAVED_TCL == 0x1, ARG_1 == 0x15, SEQ_FLAGS == 0x0 > ahc2: Bus Device Reset on A:0. 14 SCBs aborted > > As I mentioned, if I turn off tagged queuing on the host channel with > the two LUNs, everything seems to work just fine - but somewhat slower > for certain operations, of course. > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > > > > > > On Mon, 24 Apr 2000 sthaug@nethelp.no wrote: > > > > > > I would recommend that you test out the controller carefully under high > > > > load conditions if you have more than one array configured on it. > > > > > > > > There have been a number of reports (see the list archives) about problems > > > > with CMD RAID arrays with more than one LUN (i.e. more than one array) > > > > configured. > > > > > > I have two LUNs on one of the host channels, and I can easily provoke > > > problems here (running a few copies of bonnie, for instance) with > > > tagged queueing enabled. If I turn off tagged queueing on the host > > > channel with multiple LUNs (as suggested by Oliver Blasnik > > > ), there are no problems. > > > > > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-scsi" in the body of the message > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 24 14: 9:56 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 1D0AB37BBCB for ; Mon, 24 Apr 2000 14:09:49 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 76386 invoked by uid 1001); 24 Apr 2000 21:09:47 +0000 (GMT) To: mjacob@feral.com Cc: ken@kdm.org, freebsd-scsi@FreeBSD.ORG Subject: Re: Safe mounting of one file system on multiple hosts? From: sthaug@nethelp.no In-Reply-To: Your message of "Mon, 24 Apr 2000 13:58:33 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 24 Apr 2000 23:09:47 +0200 Message-ID: <76384.956610587@verdi.nethelp.no> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Huh, well, this looks more like a problem with the target than anything else, > but it's hard to say. Possibly so - but: - Several people have suggested that CMD RAID controllers do indeed have problems with multiple LUN support, - I experience this problem only on the host channel with multiple LUNs, - The fix suggested by Oliver Blasnik (see below) seems to work. All of this makes me conclude that the problem probably *is* due to bugs in the multiple LUN support in the CMD firmware. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- From: "Oliver Blasnik" To: "Kenneth D. Merry" , "LukeUnix" Cc: References: <200001251721.JAA32558@infosite.com> <20000125131901.A96487@panzer.kdm.org> Subject: Re: CMD problems Date: Thu, 27 Jan 2000 12:14:02 +0100 Organization: Omnilink ISC Hi there, Luke had some (well known) Problems: > > I am having problems with a CMD CRD-5440 with multiple luns. The config is 2 > > /kernel: (da2:ahc1:0:1:0): SCB 0x18 - timed out while idle, LASTPHASE == > > 0x1, SEQADDR == 0xa > > /kernel: (da2:ahc1:0:1:0): Queuing a BDR SCB > > /kernel: (da2:ahc1:0:1:0): Bus Device Reset Message Sent > > /kernel: (da2:ahc1:0:1:0): no longer in timeout, status = 34b > > /kernel: ahc1: Bus Device Reset on A:1. 2 SCBs aborted > > /kernel: (da2:ahc1:0:1:0): SCB 0x28 - timed out while idle, LASTPHASE == > > 0x1, SEQADDR == 0x9 Go into CMD-Setup via serial, disable "Tagged Queuing" on the/all Host-Channels. Kenneth stated: > The short answer is "don't do that". > Other folks have discovered that the CMD RAID arrays don't quite work right > with more than one LUN enabled. > Sorry I can't provide any solutions here, but this is almost certainly a > problem with CMD's firmware, and the workaround is to only use one LUN on > the controller. True, the problem is that crappy firmware, which does not currectly share the commandqueue between multiple LUNs. If you _need_ multiple LUNs per Hostchannel, disable tagged queuing. This slows down disk-i/o a little bit, but the CMD works out very well due to the fast cache-access. Cu, Oliver -- __ OMNILINK Internet Service Center GmbH / \ Hahnstrasse 70, 60528 Frankfurt __\ /_________ Tel.: (0 69)66 44 10 Fax: (0 69)66 44 11 99 O M N I L I N K http://www.omnilink.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 24 14:10:48 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 8BDA337BBCB for ; Mon, 24 Apr 2000 14:10:34 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA13291; Mon, 24 Apr 2000 15:10:22 -0600 (MDT) (envelope-from ken) Date: Mon, 24 Apr 2000 15:10:22 -0600 From: "Kenneth D. Merry" To: Matthew Jacob Cc: sthaug@nethelp.no, freebsd-scsi@FreeBSD.ORG Subject: Re: Safe mounting of one file system on multiple hosts? Message-ID: <20000424151022.A13260@panzer.kdm.org> References: <75152.956609789@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mjacob@feral.com on Mon, Apr 24, 2000 at 01:58:33PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Apr 24, 2000 at 13:58:33 -0700, Matthew Jacob wrote: > > Huh, well, this looks more like a problem with the target than anything else, > but it's hard to say. It's a CMD problem, essentially their firmware goes out to lunch when you have multiple luns with tagged queueing enabled and then put load on them. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 24 17:20:22 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 2BF1737B7B2 for ; Mon, 24 Apr 2000 17:20:16 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id RAA30645; Mon, 24 Apr 2000 17:39:55 -0600 (MDT) Date: Mon, 24 Apr 2000 17:39:55 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <200004242339.RAA30645@narnia.plutotech.com> To: wkt@cs.adfa.edu.au Cc: scsi@FreeBSD.org Subject: Re: Adaptec 2906, any users? X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <200004070203.MAA19720@henry.cs.adfa.edu.au> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <200004070203.MAA19720@henry.cs.adfa.edu.au> you wrote: > Back in December 1999, Justin Gibbs wrote: > >> The driver does not have an entry for [the Adaptec 2906] card, >> but it should be caught by one of the generic entries. If it doesn't >> work for you, I should be able to get you a patch for it as soon as >> you can supply the PCI vendor/device/subvendor/subdevice ids >> from a boot -v. >> >> -- >> Justin > > I'm just about to buy this card. Has anybody get this working in 3.4-RELEASE > or 4.0-RELEASE since then? Justin, did the person supply you with the > PCI device ids? Nope, they just confirmed that it worked. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Apr 25 2: 8:10 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from clefw.ra.rockwell.com (clefw.ra.rockwell.com [192.159.76.15]) by hub.freebsd.org (Postfix) with ESMTP id 6BC1E37BCA6 for ; Tue, 25 Apr 2000 02:08:04 -0700 (PDT) (envelope-from mkes@ra.rockwell.com) Received: from raclesmtp01.cle.ra.rockwell.com (raclesmtp01.cle.ra.rockwell.com [130.151.192.220]) by clefw.ra.rockwell.com (8.9.3/8.9.3) with ESMTP id FAA12502 for ; Tue, 25 Apr 2000 05:08:02 -0400 (EDT) From: mkes@ra.rockwell.com Subject: Re: 4.0 RELEASE on HP Kayak XU800 and HP NetServer LH 3000 To: hiroyu-y@ex.itc.keio.ac.jp (Hiroyuki Yamagai) Cc: freebsd-scsi@freebsd.org Date: Tue, 25 Apr 2000 10:51:22 +0200 Message-ID: X-MIMETrack: Serialize by Router on RACleSMTP01/Cleveland/RA/Rockwell(Release 5.0.2b (Intl)|16 December 1999) at 04/25/2000 04:57:14 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > To my knowledge that AIC-7892 is a dual channel SCSI Controler, with BUS A & B. > On FreeBSD, if the B Bus BIOS is set to > > [Reset SCSI bus at IC Initialization -- enable] > > the system will panic as you posted. > If, disabled it'll boot with out problem. I tried to change it in the SCSI setup but it looks like there is no separate option for BUS B (only one set of settings). I checked at the Adaptec web site and they treat 7892 as on-board equivalent of 2940UW card (which has single channel). Are you sure about the B Bus ? > By the way, when did you purchace your HP NetServer LH 3000? Two weeks ago > I belevie that the new models has integrated RAID Controler > instead of AMI MegaRAID 1400 as on older LH3000. Yes, the RAID Controler is integrated. Regards Mira P.S. > I'm interested in what Serise of MegaRaid is on th New LH3000. > Can you post or mail me dmesg of your LH3000? Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-RELEASE #1: Thu Apr 20 12:29:27 CEST 2000 root@bivoj.cze.ra.rockwell.com:/usr/src/sys/compile/LOCAL Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 723337131 Hz CPU: Pentium III/Pentium III Xeon (723.34-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x387fbff real memory = 268369920 (262080K bytes) config> di pcic0 No such device: pcic0 Invalid command or syntax. Type `?' for help. config> di sn0 No such device: sn0 Invalid command or syntax. Type `?' for help. config> di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config> di le0 No such device: le0 Invalid command or syntax. Type `?' for help. config> di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config> di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config> di ed0 No such device: ed0 Invalid command or syntax. Type `?' for help. config> di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config> di bt0 No such device: bt0 Invalid command or syntax. Type `?' for help. config> di ata1 No such device: ata1 Invalid command or syntax. Type `?' for help. config> di aic0 No such device: aic0 Invalid command or syntax. Type `?' for help. config> di aha0 No such device: aha0 Invalid command or syntax. Type `?' for help. config> di adv0 No such device: adv0 Invalid command or syntax. Type `?' for help. config> q avail memory = 257220608 (251192K bytes) Preloaded elf kernel "kernel" at 0xc0302000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc030209c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 fxp0: port 0x1800-0x183f mem 0xd1000000-0xd10fffff,0xcff80000-0xcff80fff irq 9 at device 6.0 on pci0 fxp0: Ethernet address 00:10:83:f9:1d:84 fxp0: supplying EUI64: 00:10:83:ff:fe:f9:1d:84 pci0: at 7.0 irq 9 isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x1840-0x184f at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pcib3: on motherboard pci3: on pcib3 pci3: (vendor=0x103c, dev=0x1219) at 2.0 irq 10 pci3: (vendor=0x103c, dev=0x121a) at 2.1 irq 11 pcib4: at device 3.0 on pci3 pci4: on pcib4 ahc0: port 0x5000-0x50ff mem 0xd4108000-0xd4108fff irq 5 at device 7.0 on pci4 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Host Adapter Bios disabled. Using default SCSI device parameters pci4: (vendor=0x103c, dev=0x10c1) at 8.0 amr0: mem 0xe0000000-0xefffffff irq 5 at device 3.1 on pci3 amr0: firmware bios \^A\^BB 32MB memory amrd0: on amr0 amrd0: 8677MB (17770496 sectors) RAID 0 (optimal) amrd1: on amr0 amrd1: 34730MB (71127040 sectors) RAID 5 (optimal) fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging limited to 100 packets/entry by default ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed acd0: CDROM at ata0-master using PIO4 Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) no devsw (majdev=0 bootdev=0xa0200000) Mounting root from ufs:/dev/amrd0s1a fxp0: starting DAD for fe80:0001::0210:83ff:fef9:1d84 fxp0: DAD complete for fe80:0001::0210:83ff:fef9:1d84 - no duplicates found To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 26 16:41:40 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from yam.ex.itc.keio.ac.jp (yam.ex.itc.keio.ac.jp [131.113.212.100]) by hub.freebsd.org (Postfix) with SMTP id DCF5337BD28 for ; Wed, 26 Apr 2000 16:41:36 -0700 (PDT) (envelope-from hiroyu-y@ex.itc.keio.ac.jp) Received: (qmail 28060 invoked by uid 1001); 26 Apr 2000 23:46:59 -0000 Date: 26 Apr 2000 23:46:59 -0000 Message-ID: <20000426234659.28059.qmail@yam.ex.itc.keio.ac.jp> To: mkes@ra.rockwell.com Cc: freebsd-scsi@freebsd.org, hiroyu-y@ex.itc.keio.ac.jp Subject: Re: 4.0 RELEASE on HP Kayak XU800 and HP NetServer LH 3000 In-Reply-To: Your message of "Tue, 25 Apr 2000 17:51:22 JST". From: hiroyu-y@ex.itc.keio.ac.jp (Hiroyuki Yamagai) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On messages mkes@ra.rockwell.com worte: >> > To my knowledge that AIC-7892 is a dual channel SCSI Controler, with BUS >> A & B. >> > On FreeBSD, if the B Bus BIOS is set to >> > >> > [Reset SCSI bus at IC Initialization -- enable] >> > >> > the system will panic as you posted. >> > If, disabled it'll boot with out problem. >> >> I tried to change it in the SCSI setup but it looks like there is no >> separate option for BUS B (only one set of settings). >> I checked at the Adaptec web site and they treat 7892 as on-board >> equivalent of 2940UW card (which has single channel). >> Are you sure about the B Bus ? My mistake. Mine was AIC-7895. (Gave me the same symptoms,thought.) If it dosen't have a second channel, then could be that one of the DEVICE on your scsi bus doing a reset. Thanks for the dmesg. Regards To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 27 1:37:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id A666F37B5D1 for ; Thu, 27 Apr 2000 01:37:29 -0700 (PDT) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id JAA19459 for freebsd-scsi@FreeBSD.ORG; Thu, 27 Apr 2000 09:37:27 +0100 (BST) (envelope-from geoffb) Date: Thu, 27 Apr 2000 09:37:27 +0100 From: Geoff Buckingham To: freebsd-scsi@FreeBSD.ORG Subject: SAN ro filesystem sharing under FreeBSD Message-ID: <20000427093727.A19441@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Having mad a few searches and found nothing recent I was wondering what the state of affairs was with reguard to sharing filesystems with an FCAL SAN. Both ADIC and AVID have announced their filesystems for linux does FreeBSD have the hardware support to make a port possible? If not is it likely to migrate from BSDI? -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 27 1:46:39 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-132.dsl.snfc21.pacbell.net [63.202.176.132]) by hub.freebsd.org (Postfix) with ESMTP id 9EDB437B515 for ; Thu, 27 Apr 2000 01:46:36 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA06185; Thu, 27 Apr 2000 01:54:07 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004270854.BAA06185@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Geoff Buckingham Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SAN ro filesystem sharing under FreeBSD In-reply-to: Your message of "Thu, 27 Apr 2000 09:37:27 BST." <20000427093727.A19441@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Apr 2000 01:54:07 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Having mad a few searches and found nothing recent I was wondering what the > state of affairs was with reguard to sharing filesystems with an FCAL SAN. > > > Both ADIC and AVID have announced their filesystems for linux does FreeBSD > have the hardware support to make a port possible? If not is it likely to > migrate from BSDI? We have most of the support already, yes. I have no idea what the likelihood is of seeing a shareable filesystem in the short term. I don't see any applicable support in the BSD/OS codebase, so I'm not sure what's expected to "migrate" here. As a general rule, our hardware footprint is comparable or better there. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 27 1:49:55 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A9AC637B603 for ; Thu, 27 Apr 2000 01:49:51 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id BAA14829; Thu, 27 Apr 2000 01:48:48 -0700 Date: Thu, 27 Apr 2000 01:49:48 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Geoff Buckingham Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SAN ro filesystem sharing under FreeBSD In-Reply-To: <20000427093727.A19441@chuggalug.clues.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Having mad a few searches and found nothing recent I was wondering what the > state of affairs was with reguard to sharing filesystems with an FCAL SAN. The h/w is in place for Fibre Channel, yes, although it's better if you can affort a fabric switch. > Both ADIC and AVID have announced their filesystems for linux does FreeBSD > have the hardware support to make a port possible? If not is it likely to > migrate from BSDI? If people find the Fibre Channel hardware support lacking, perhaps they should tell me about it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 27 10:45:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (Postfix) with ESMTP id 9891037BAD2 for ; Thu, 27 Apr 2000 10:45:21 -0700 (PDT) (envelope-from nrahlstr@mail.winternet.com) Received: from tundra.winternet.com (nrahlstr@tundra.winternet.com [198.174.169.11]) by icicle.winternet.com (8.9.3/8.9.3mc) with ESMTP id MAA09442; Thu, 27 Apr 2000 12:45:19 -0500 (CDT) SMTP "HELO" (ESMTP) greeting from tundra.winternet.com But _really_ from :: nrahlstr@tundra.winternet.com [198.174.169.11] SMTP "MAIL From" = nrahlstr@mail.winternet.com (Nathan Ahlstrom) SMTP "RCPT To" = Received: (from nrahlstr@localhost) by tundra.winternet.com (8.8.7/8.8.4) id MAA13686; Thu, 27 Apr 2000 12:45:18 -0500 (CDT) Date: Thu, 27 Apr 2000 12:45:18 -0500 From: Nathan Ahlstrom To: Matthew Jacob Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SAN ro filesystem sharing under FreeBSD Message-ID: <20000427124518.H11625@winternet.com> Mail-Followup-To: Matthew Jacob , freebsd-scsi@FreeBSD.ORG References: <20000427093727.A19441@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from mjacob@feral.com on Thu, Apr 27, 2000 at 01:49:48AM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > If people find the Fibre Channel hardware support lacking, perhaps they > should tell me about it. Has anyone thought about support for the JNI or Emulex HBA's? Which begs the question, are programming docs available for those cards? Thanks, Nathan -- Nathan Ahlstrom FreeBSD: http://www.FreeBSD.org/ nrahlstr@winternet.com PGP Key ID: 0x67BC9D19 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 27 10:54:58 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 65E1337B751 for ; Thu, 27 Apr 2000 10:54:56 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA16491; Thu, 27 Apr 2000 10:53:49 -0700 Date: Thu, 27 Apr 2000 10:54:53 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Nathan Ahlstrom Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SAN ro filesystem sharing under FreeBSD In-Reply-To: <20000427124518.H11625@winternet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 27 Apr 2000, Nathan Ahlstrom wrote: > > > If people find the Fibre Channel hardware support lacking, perhaps they > > should tell me about it. > > Has anyone thought about support for the JNI or Emulex HBA's? > > Which begs the question, are programming docs available for those > cards? No, and I've asked. At least for JNI. I could probably reverse engineer the emulex linux driver , plus other knowledge I have, but w/o mfg support, it'll be the frickin' intel eepro1000 all over again. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 27 11: 9: 1 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 7E5B737BF15; Thu, 27 Apr 2000 11:08:56 -0700 (PDT) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id UAA09732; Mon, 1 May 2000 20:34:25 -0500 (CDT) From: Joe Greco Message-Id: <200005020134.UAA09732@aurora.sol.net> Subject: 29160/39160 under 3.*-stable To: scsi@freebsd.org, stable@freebsd.org Date: Mon, 1 May 2000 20:34:24 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Will the 29160 and 39160 be supported under 3.*-stable? With the old cards no longer being available, and the relative newness of 4.*-stable, I do not really want to run 4.0R on production servers. Thanks for any info, -- ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 27 12:57:24 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id 958B037B969 for ; Thu, 27 Apr 2000 12:57:21 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 199f3c0039bf924253955fca0afeedcc) with ESMTP id <20000427195715.DWCR1988.relay02@chello.nl>; Thu, 27 Apr 2000 21:57:15 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id VAA01635; Thu, 27 Apr 2000 21:57:17 +0200 (CEST) (envelope-from wkb) Date: Thu, 27 Apr 2000 21:57:17 +0200 From: Wilko Bulte To: Matthew Jacob Cc: Nathan Ahlstrom , freebsd-scsi@FreeBSD.ORG Subject: Re: SAN ro filesystem sharing under FreeBSD Message-ID: <20000427215717.D384@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: <20000427124518.H11625@winternet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from mjacob@feral.com on Thu, Apr 27, 2000 at 10:54:53AM -0700 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Apr 27, 2000 at 10:54:53AM -0700, Matthew Jacob wrote: > On Thu, 27 Apr 2000, Nathan Ahlstrom wrote: > > > > > > If people find the Fibre Channel hardware support lacking, perhaps they > > > should tell me about it. > > > > Has anyone thought about support for the JNI or Emulex HBA's? > > > > Which begs the question, are programming docs available for those > > cards? > No, and I've asked. At least for JNI. 'No' too for Emulex. NDA.. > I could probably reverse engineer the emulex linux driver , plus other The various LPx000 have more or less different interfaces. And not easy ones too. I once saw the spec. > knowledge I have, but w/o mfg support, it'll be the frickin' intel eepro1000 > all over again. No fun.. -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 28 21:44:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id 0228737B5BA for ; Fri, 28 Apr 2000 21:44:23 -0700 (PDT) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id VAA48639 for ; Fri, 28 Apr 2000 21:44:21 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id VAA02314; Fri, 28 Apr 2000 21:44:21 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14602.26788.441429.641364@whale.home-net> Date: Fri, 28 Apr 2000 21:44:20 -0700 (MST) To: scsi@freebsd.org Subject: hardware meltdown or cosmic ray? X-Mailer: VM 6.73 under Emacs 20.6.1 Cc: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok. I've got a question I know that one of you SCSI gurus can help with. I was copying some CDs (data) tonight. Rather than chance buffer underrun, I was copying the entire disc onto an empty chunk o' disk, then burning those ISOs. The command I submitted to copy the cd was: dd if=/dev/cd0c of=disc.iso It chugged along with about 200Mb or so snarfed off the disc, then I got these messages appearing on my console and the whole SCSI subsystem went "dead" (during the timeouts) Apr 28 18:44:17 whale /kernel: dscheck: b_bcount 512 is not on a sector boundary (ssize 2048) Apr 28 18:47:04 whale /kernel: (cd0:ahc0:0:3:0): SCB 0x2 - timed out in dataout phase, SEQADDR == 0x5d Apr 28 18:47:40 whale /kernel: (cd0:ahc0:0:3:0): Other SCB Timeout Apr 28 18:47:40 whale /kernel: (da1:ahc0:0:6:0): SCB 0x3b - timed out in dataout phase, SEQADDR == 0x5d Apr 28 18:47:40 whale /kernel: (da1:ahc0:0:6:0): BDR message in message buffer Apr 28 18:47:40 whale /kernel: (da1:ahc0:0:6:0): SCB 0x2d - timed out in dataout phase, SEQADDR == 0x5d Apr 28 18:47:40 whale /kernel: (da1:ahc0:0:6:0): no longer in timeout, status = 34b Apr 28 18:47:40 whale /kernel: ahc0: Issued Channel A Bus Reset. 7 SCBs aborted Apr 28 20:54:05 whale /kernel: swap_pager: indefinite wait buffer: device: 0x30401, blkno: 50456, size: 36864 Apr 28 20:54:48 whale /kernel: (cd0:ahc0:0:3:0): SCB 0x5 - timed out in dataout phase, SEQADDR == 0x5d Apr 28 20:54:48 whale /kernel: (cd0:ahc0:0:3:0): Other SCB Timeout Apr 28 20:54:48 whale /kernel: swap_pager: indefinite wait buffer: device: 0x30401, blkno: 11536, size: 4096 Apr 28 20:54:48 whale /kernel: swap_pager: indefinite wait buffer: device: 0x30401, blkno: 50456, size: 36864 Apr 28 20:54:48 whale /kernel: (da1:ahc0:0:6:0): SCB 0x11 - timed out in dataout phase, SEQADDR == 0x5d Apr 28 20:54:48 whale /kernel: (da1:ahc0:0:6:0): BDR message in message buffer Apr 28 20:54:48 whale /kernel: (da1:ahc0:0:6:0): SCB 0x11 - timed out in dataout phase, SEQADDR == 0x5e Apr 28 20:54:48 whale /kernel: (da1:ahc0:0:6:0): no longer in timeout, status = 34b Apr 28 20:54:48 whale /kernel: ahc0: Issued Channel A Bus Reset. 10 SCBs aborted Apr 28 20:54:48 whale /kernel: swap_pager: indefinite wait buffer: device: 0x30401, blkno: 11536, size: 4096 Apr 28 20:54:48 whale /kernel: swap_pager: indefinite wait buffer: device: 0x30401, blkno: 50456, size: 36864 At that point the machine was just hung solid and required the reset button. I then powered it down complete and brought it back up. A subsequent dd command produced no wierd behavior: root@whale [/data/isos]<21># dd if=/dev/cd0c of=disc.iso 985332+0 records in 985332+0 records out 504489984 bytes transferred in 224.169648 secs (2250483 bytes/sec) (not a full disc). Any idea by the looks of these error messages if I'm having some some sort of H/W meltdown or is your best guess that this was a random occurance (cosmic rays I like to blame)??? Everything seems "fine" at this point .... Thanks -Jr ps: using adaptec 7890 onboard scsi on a P2B-DS mo-board. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 29 0: 5:49 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from server1.huntsvilleal.com (server1.huntsvilleal.com [63.147.8.7]) by hub.freebsd.org (Postfix) with ESMTP id DED3A37B81F for ; Sat, 29 Apr 2000 00:05:46 -0700 (PDT) (envelope-from kris@hiwaay.net) Received: from barricuda.bsd.nws.net (kris.huntsvilleal.com [63.147.8.46]) by server1.huntsvilleal.com (8.9.3/8.9.3) with ESMTP id BAA15634; Sat, 29 Apr 2000 01:43:52 -0400 Received: from localhost (localhost [127.0.0.1]) by barricuda.bsd.nws.net (8.9.3/8.9.3) with ESMTP id BAA19691; Sat, 29 Apr 2000 01:08:18 -0500 (CDT) (envelope-from kris@hiwaay.net) Date: Sat, 29 Apr 2000 01:08:15 -0500 (CDT) From: Kris Kirby To: John Reynolds Cc: scsi@FreeBSD.ORG Subject: Re: hardware meltdown or cosmic ray? In-Reply-To: <14602.26788.441429.641364@whale.home-net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Ok. I've got a question I know that one of you SCSI gurus can help with. I was > copying some CDs (data) tonight. Rather than chance buffer underrun, I was > copying the entire disc onto an empty chunk o' disk, then burning those ISOs. > The command I submitted to copy the cd was: > > dd if=/dev/cd0c of=disc.iso > > It chugged along with about 200Mb or so snarfed off the disc, then I got these > messages appearing on my console and the whole SCSI subsystem went "dead" > (during the timeouts) This probably has no relavence what so ever, but I'll offer it anyway. Since CD's have 2048 byte sectors, I'd recommend using that for dd's blocksize. Maybe it will work better? ----- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "Fate, it seems, is not without a sense of irony." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 29 0:12:55 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 008D537B6C1 for ; Sat, 29 Apr 2000 00:12:52 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id BAA51121; Sat, 29 Apr 2000 01:12:41 -0600 (MDT) (envelope-from ken) Date: Sat, 29 Apr 2000 01:12:40 -0600 From: "Kenneth D. Merry" To: John Reynolds Cc: scsi@FreeBSD.ORG Subject: Re: hardware meltdown or cosmic ray? Message-ID: <20000429011240.A50701@panzer.kdm.org> References: <14602.26788.441429.641364@whale.home-net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14602.26788.441429.641364@whale.home-net>; from jjreynold@home.com on Fri, Apr 28, 2000 at 09:44:20PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Apr 28, 2000 at 21:44:20 -0700, John Reynolds wrote: > > Ok. I've got a question I know that one of you SCSI gurus can help with. I was > copying some CDs (data) tonight. Rather than chance buffer underrun, I was > copying the entire disc onto an empty chunk o' disk, then burning those ISOs. > The command I submitted to copy the cd was: > > dd if=/dev/cd0c of=disc.iso > > It chugged along with about 200Mb or so snarfed off the disc, then I got these > messages appearing on my console and the whole SCSI subsystem went "dead" > (during the timeouts) One thing you didn't mention was what version of FreeBSD you are using. I suspect you're using a version that has block devices. The above command won't work at all with the raw device, since dd's default sector size (512 bytes) isn't a multiple of the CD sector size (2048 bytes). > Apr 28 18:44:17 whale /kernel: dscheck: b_bcount 512 is not on a sector boundary (ssize 2048) For some reason, the block device code issued a read that wasn't a multiple of the sector size, thus the above error. > Apr 28 18:47:04 whale /kernel: (cd0:ahc0:0:3:0): SCB 0x2 - timed out in dataout phase, SEQADDR == 0x5d > Apr 28 18:47:40 whale /kernel: (cd0:ahc0:0:3:0): Other SCB Timeout > Apr 28 18:47:40 whale /kernel: (da1:ahc0:0:6:0): SCB 0x3b - timed out in dataout phase, SEQADDR == 0x5d > Apr 28 18:47:40 whale /kernel: (da1:ahc0:0:6:0): BDR message in message buffer > Apr 28 18:47:40 whale /kernel: (da1:ahc0:0:6:0): SCB 0x2d - timed out in dataout phase, SEQADDR == 0x5d > Apr 28 18:47:40 whale /kernel: (da1:ahc0:0:6:0): no longer in timeout, status = 34b > Apr 28 18:47:40 whale /kernel: ahc0: Issued Channel A Bus Reset. 7 SCBs aborted It looks like the bus is wedged there. Note that it happened 4 minutes after the error message you got, so they may not be related. In fact, they probably aren't, because the dscheck error above means that the read on the non-sector boundary wasn't issued. [ same thing a couple of hours later ] > At that point the machine was just hung solid and required the reset button. I > then powered it down complete and brought it back up. A subsequent dd command > produced no wierd behavior: > > root@whale [/data/isos]<21># dd if=/dev/cd0c of=disc.iso > 985332+0 records in > 985332+0 records out > 504489984 bytes transferred in 224.169648 secs (2250483 bytes/sec) > > (not a full disc). > > Any idea by the looks of these error messages if I'm having some some sort of > H/W meltdown or is your best guess that this was a random occurance (cosmic > rays I like to blame)??? In general, timed out in dataout/datain phase messages mean that you have some sort of cabling or termination problem. That may or may not be the case here, I dunno. It may be a cabling or connector problem that is triggered by using the cdrom drive. In any case, you should probably use the raw device, and a multiple of the sector size to get an image of the disc, like this: dd if=/dev/rcd0c of=disc.iso bs=64k I doubt that will fix the problem, but it would be interesting to see if you can use the above command to try to reproduce the problem. If you can reproduce the problem, I would start looking for cabling or termination problems. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 29 0:35:37 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id E361E37B76B for ; Sat, 29 Apr 2000 00:35:33 -0700 (PDT) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id AAA49450; Sat, 29 Apr 2000 00:35:32 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id AAA00498; Sat, 29 Apr 2000 00:35:32 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14602.37059.886168.353842@whale.home-net> Date: Sat, 29 Apr 2000 00:35:31 -0700 (MST) To: "Kenneth D. Merry" Cc: scsi@FreeBSD.ORG Subject: Re: hardware meltdown or cosmic ray? In-Reply-To: <20000429011240.A50701@panzer.kdm.org> References: <14602.26788.441429.641364@whale.home-net> <20000429011240.A50701@panzer.kdm.org> X-Mailer: VM 6.73 under Emacs 20.6.1 Cc: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ On Saturday, April 29, Kenneth D. Merry wrote: ] > > One thing you didn't mention was what version of FreeBSD you are using. > > I suspect you're using a version that has block devices. The above command dad-nabit ... I *KNEW* there was something gnawing at me to put in there before I hit "send" .... yes, I'm using 3.4-STABLE which still has the block devices. > some sort of cabling or termination problem. That may or may not be the > case here, I dunno. > > It may be a cabling or connector problem that is triggered by using the > cdrom drive. Hmmmm. I sure hope not .... this has never happened before .. > In any case, you should probably use the raw device, and a multiple of the > sector size to get an image of the disc, like this: > > dd if=/dev/rcd0c of=disc.iso bs=64k So this 'dd' command will work with 4.0 (and -current)? > I doubt that will fix the problem, but it would be interesting to see if > you can use the above command to try to reproduce the problem. If you can > reproduce the problem, I would start looking for cabling or termination > problems. OK. I'll try and read in the image again with the raw device and see what happens. It's been acting like a champ since it freaked (and I've since copied 6 discs using the exact same method ... wierd). Thanks for the answers! -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 29 0:39:39 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 7BB1537B677 for ; Sat, 29 Apr 2000 00:39:36 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id BAA51381; Sat, 29 Apr 2000 01:39:29 -0600 (MDT) (envelope-from ken) Date: Sat, 29 Apr 2000 01:39:29 -0600 From: "Kenneth D. Merry" To: John Reynolds Cc: scsi@FreeBSD.ORG Subject: Re: hardware meltdown or cosmic ray? Message-ID: <20000429013929.A51355@panzer.kdm.org> References: <14602.26788.441429.641364@whale.home-net> <20000429011240.A50701@panzer.kdm.org> <14602.37059.886168.353842@whale.home-net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14602.37059.886168.353842@whale.home-net>; from jjreynold@home.com on Sat, Apr 29, 2000 at 12:35:31AM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Apr 29, 2000 at 00:35:31 -0700, John Reynolds wrote: > > [ On Saturday, April 29, Kenneth D. Merry wrote: ] > > > > One thing you didn't mention was what version of FreeBSD you are using. > > > > I suspect you're using a version that has block devices. The above command > > dad-nabit ... I *KNEW* there was something gnawing at me to put in there before > I hit "send" .... yes, I'm using 3.4-STABLE which still has the block devices. Makes sense. > > some sort of cabling or termination problem. That may or may not be the > > case here, I dunno. > > > > It may be a cabling or connector problem that is triggered by using the > > cdrom drive. > > Hmmmm. I sure hope not .... this has never happened before .. Well, if it is, the fix is usually as easy as a new cable, or re-seating the connectors, or moving it away from the power supply. > > In any case, you should probably use the raw device, and a multiple of the > > sector size to get an image of the disc, like this: > > > > dd if=/dev/rcd0c of=disc.iso bs=64k > > So this 'dd' command will work with 4.0 (and -current)? It'll work with 3.4, which has the block devices. rfoo is the character/raw device. In -current, just plain 'foo' is the raw device. > > I doubt that will fix the problem, but it would be interesting to see if > > you can use the above command to try to reproduce the problem. If you can > > reproduce the problem, I would start looking for cabling or termination > > problems. > > OK. I'll try and read in the image again with the raw device and see what > happens. It's been acting like a champ since it freaked (and I've since copied > 6 discs using the exact same method ... wierd). It may be an intermittent problem, who knows. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message