From owner-freebsd-scsi Mon Aug 21 7: 3:51 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from elend.fremde.com (elend.fremde.com [12.2.86.60]) by hub.freebsd.org (Postfix) with ESMTP id 2917D37B423 for ; Mon, 21 Aug 2000 07:03:50 -0700 (PDT) Received: by elend.fremde.com (Postfix, from userid 1000) id 451281A083; Mon, 21 Aug 2000 10:03:49 -0400 (EDT) Date: Mon, 21 Aug 2000 10:03:49 -0400 From: oneiros To: freebsd-scsi@freebsd.org Subject: ultra 160 and performance Message-ID: <20000821100349.C29427@elend.fremde.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (this was posted to -stable earlier, and someone pointed out to me that this might be the appropriate place to ask such a question) greetings- can anyone tell me if support for the full 160mb/sec has been merged into -stable yet? after reading through the archives i found justin's patch, but i was hoping to avoid that. in short, my disk is still running at ultra-2 speeds :< many thanks, -justin da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) ahc1: port 0xb000-0xb0ff mem 0xde800000-0xde800fff irq 11 at device 10.0 on pci0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 21 7:12:14 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.161.193]) by hub.freebsd.org (Postfix) with ESMTP id 01BA337B424 for ; Mon, 21 Aug 2000 07:12:12 -0700 (PDT) Received: from mail.vt.edu (gkar.cc.vt.edu [198.82.161.190]) by lennier.cc.vt.edu (8.11.0/8.11.0) with ESMTP id e7LECBB08793 for ; Mon, 21 Aug 2000 10:12:11 -0400 (EDT) Received: from vt.edu ([128.173.92.190]) by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with ESMTP id <0FZN00JDZBGAJZ@gkar.cc.vt.edu> for freebsd-scsi@freebsd.org; Mon, 21 Aug 2000 10:12:10 -0400 (EDT) Date: Mon, 21 Aug 2000 10:12:10 -0400 From: George Morgan Subject: Problems booting IBM 18LZX on Adaptec 39160 To: freebsd-scsi@freebsd.org Message-id: <39A138BA.1FA0BDB5@vt.edu> MIME-version: 1.0 X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.16 i686) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone have experience with IBM Ultra 160 drives with the Adaptec 39160? I know that FreeBSD 4.0 doesn't currently support the 160 MB/s speed, but I can't get *any* os to boot on the IBM 18 GB Ultra160 10k rpm drive. It is attached to Channel A of an Adaptec 39160 using the cable and terminator which comes with the kit. The board is installed in a 32bit 33mhz PCI slot. (which it supposedly supports) I can boot CD-ROMs (the method I used for the install) using this controller, but have not successfully booted a disk. Any help/suggestions are appreciated. I am subscribed to the freebsd-scsi list so you don't need to copy the response to my address also. If your response is not freebsd related (you have booted NT or 98 on one of these drives) please direct the response directly to me. Thank you for your time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 21 13:30:34 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from sun.rhrk.uni-kl.de (sun.rhrk.uni-kl.de [131.246.137.50]) by hub.freebsd.org (Postfix) with SMTP id 2624637B43C for ; Mon, 21 Aug 2000 13:30:28 -0700 (PDT) Received: from aixs1.rhrk.uni-kl.de ( exim@aixs1.rhrk.uni-kl.de [131.246.137.3] ) by sun.rhrk.uni-kl.de id aa14431 ; 21 Aug 2000 22:29 MESZ Received: from aixd1.rhrk.uni-kl.de ([131.246.137.210] ident=exim) by aixs1.rhrk.uni-kl.de with esmtp (Exim 3.03 #2) id 13QyCY-000LYi-00; Mon, 21 Aug 2000 22:29:46 +0200 Received: from mheller (helo=localhost) by aixd1.rhrk.uni-kl.de with local-esmtp (Exim 3.03 #2) id 13QyCY-000W3K-00; Mon, 21 Aug 2000 22:29:46 +0200 Date: Mon, 21 Aug 2000 22:29:45 +0200 (MES) From: Martin Heller X-Sender: mheller@aixd1.rhrk.uni-kl.de To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: bellefso@execpc.com, freebsd-scsi@freebsd.org Subject: RE: Tekram DC390U3W In-Reply-To: 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 Sorry for my late response but I was several days without internet connection ... My results at power-up are: u160 disks: needed to update firmware as they were not correctly recognized UW disks: somehow strange - some where correctly recognized, some not U2W disks: everything was ok DAT: correct CD-ROM: correct booting FreeBSD4.1 I get: u160 disks: correct (after FW update) U2W: correct DAT: correct CD-ROM: correct UW: some disks, which where reported correctly on power-up where not during booting and vice versa I suspect, that the FW of some UW disks is not quite up to the task. MARTIN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 21 19:44:45 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.chuckr.org (picnic.chuckr.org [216.254.96.118]) by hub.freebsd.org (Postfix) with ESMTP id 014BD37B424 for ; Mon, 21 Aug 2000 19:44:43 -0700 (PDT) Received: from localhost (chuckr@localhost) by picnic.chuckr.org (8.9.3/8.9.3) with ESMTP id WAA00890; Mon, 21 Aug 2000 22:45:03 -0400 (EDT) (envelope-from chuckr@picnic.chuckr.org) Date: Mon, 21 Aug 2000 22:45:03 -0400 (EDT) From: Chuck Robey To: oneiros Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ultra 160 and performance In-Reply-To: <20000821100349.C29427@elend.fremde.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 Mon, 21 Aug 2000, oneiros wrote: > (this was posted to -stable earlier, and someone pointed out to me that this might be the appropriate place to ask such a question) > > greetings- > > can anyone tell me if support for the full 160mb/sec has been merged into > -stable yet? > > after reading through the archives i found justin's patch, but i was > hoping to avoid that. > > in short, my disk is still running at ultra-2 speeds :< > > many thanks, > -justin > > da1: Fixed Direct Access SCSI-3 device > da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing > Enabled > da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > > ahc1: port 0xb000-0xb0ff mem > 0xde800000-0xde800fff irq 11 at device 10.0 on pci0 I don't think it's Justin's problem: ahc2: port 0xf000-0xf0ff mem 0xfecfd000-0xfecfdfff irq 16 at device 16.0 on pci0 ahc2: aic7892 Wide Channel A, SCSI Id=7, 32/255 SCBs da3 at ahc2 bus 0 target 0 lun 0 da3: Fixed Direct Access SCSI-3 device da3: 160.000MB/s transfers (80.000MHz, offset 63, 16bit) da3: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) OTOH, I can't get this baby to boot. Not a FreeBSD problem, that seems pretty certain, but it's a major PITA. The drive mounts fine after it boots from the DK440LX's 7895 Ch A ID 0, but if I tell the BIOS to boot from the 29160, I get a blank screen, never goes to boot. I posted to the Intel forum, but if anyone knows any secret mantras, I'm suddenly feeling somewhat religious .... ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.chuckr.org| electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 21 19:47:18 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 529DF37B422 for ; Mon, 21 Aug 2000 19:47:17 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id TAA05298; Mon, 21 Aug 2000 19:46:55 -0700 Date: Mon, 21 Aug 2000 19:43:33 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Chuck Robey Cc: oneiros , freebsd-scsi@FreeBSD.ORG Subject: Re: ultra 160 and performance In-Reply-To: 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 Let me point out again that there are two other Ultra3 cards supported in FreeBSD- Symbios (NCR1010) and QLogic (12160). -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 21 22:43:57 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ns1.networkiowa.com (ns1.networkiowa.com [209.234.64.192]) by hub.freebsd.org (Postfix) with ESMTP id D3C2D37B422 for ; Mon, 21 Aug 2000 22:43:54 -0700 (PDT) Received: from raccoon.com (dsl.72.145.networkiowa.com [209.234.72.145]) by ns1.networkiowa.com (8.9.3/8.9.3) with ESMTP id AAA02881 for ; Tue, 22 Aug 2000 00:49:03 -0500 Message-ID: <39A21314.1107B6AD@raccoon.com> Date: Tue, 22 Aug 2000 00:43:48 -0500 From: John Lengeling X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Different init speeds of raid5 plex subdisks under vinum Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I created a raid5 plex under vinum using 3 drives. These are supposed to be identical drives. They are slightly different in size. da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 17366MB (35566501 512 byte sectors: 255H 63S/T 2213C) da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-3 device da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da3: 17366MB (35566501 512 byte sectors: 255H 63S/T 2213C) When I ran the vinum init command to initialize the plex, one of the drives da2 completed the initialization 3-4 times faster than da1 and da3. Something like 20 minutes for da2 versus 60 minutes for da1/da3. Both da1 and da3 initialized at the same rate. Is this weird? Did da3/da1 get transfers negotiated down to slower speeds? Bad cabling? Or is this normal? johnl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 21 22:50:19 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 2709637B422 for ; Mon, 21 Aug 2000 22:50:17 -0700 (PDT) Received: (qmail 37077 invoked by uid 1001); 22 Aug 2000 05:50:11 +0000 (GMT) To: johnl@raccoon.com Cc: freebsd-scsi@freebsd.org Subject: Re: Different init speeds of raid5 plex subdisks under vinum From: sthaug@nethelp.no In-Reply-To: Your message of "Tue, 22 Aug 2000 00:43:48 -0500" References: <39A21314.1107B6AD@raccoon.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 22 Aug 2000 07:50:11 +0200 Message-ID: <37075.966923411@verdi.nethelp.no> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > When I ran the vinum init command to initialize the plex, one of the > drives da2 completed the initialization 3-4 times faster than da1 > and da3. Something like 20 minutes for da2 versus 60 minutes for > da1/da3. Both da1 and da3 initialized at the same rate. Is this > weird? Did da3/da1 get transfers negotiated down to slower speeds? > Bad cabling? I noticed a similar problem when initializing a 4-disk RAID5 array some weeks ago. In my case I had two disks on ATA-66 controllers and two disks on ATA-33 - and the ATA-66 connected disks initialized at roughly double the rate of the ATA-33 connected disks. I simply assumed it was due to difference between the ATA-66 and ATA-33 speeds. 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 Aug 21 23: 0:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 7554937B424 for ; Mon, 21 Aug 2000 23:00:10 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id PAA23683; Tue, 22 Aug 2000 15:29:59 +0930 (CST) (envelope-from grog) Date: Tue, 22 Aug 2000 15:29:59 +0930 From: Greg Lehey To: John Lengeling Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Different init speeds of raid5 plex subdisks under vinum Message-ID: <20000822152959.D46852@wantadilla.lemis.com> References: <39A21314.1107B6AD@raccoon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <39A21314.1107B6AD@raccoon.com>; from johnl@raccoon.com on Tue, Aug 22, 2000 at 12:43:48AM -0500 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Format recovered--see http://www.lemis.com/email/email-format.html] Please limit your text lines to 80 characters or less. Don't limit log output or similar texts. On Tuesday, 22 August 2000 at 0:43:48 -0500, John Lengeling wrote: > I created a raid5 plex under vinum using 3 drives. These are > supposed to be identical drives. They are slightly different in > size. > da2 at ahc0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI-3 device > da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled > da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled > da1: 17366MB (35566501 512 byte sectors: 255H 63S/T 2213C) > da3 at ahc0 bus 0 target 3 lun 0 > da3: Fixed Direct Access SCSI-3 device > da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled > da3: 17366MB (35566501 512 byte sectors: 255H 63S/T 2213C) > > When I ran the vinum init command to initialize the plex, one of the > drives da2 completed the initialization 3-4 times faster than da1 and > da3. Something like 20 minutes for da2 versus 60 minutes for > da1/da3. Both da1 and da3 initialized at the same rate. Is this > weird? Yes. > Did da3/da1 get transfers negotiated down to slower speeds? Probably not. > Bad cabling? No. > Or is this normal? For a certain definition of "normal", yes. I've seen this too. It seems to have something to do with the scheduler. Since we've seen it both on IDE and SCSI drives, and normally the request queue is short on such operations, it doesn't appear to be the disk driver. Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 21 23:13:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ns1.networkiowa.com (ns1.networkiowa.com [209.234.64.192]) by hub.freebsd.org (Postfix) with ESMTP id D5CAE37B43F for ; Mon, 21 Aug 2000 23:13:29 -0700 (PDT) Received: from raccoon.com (dsl.72.145.networkiowa.com [209.234.72.145]) by ns1.networkiowa.com (8.9.3/8.9.3) with ESMTP id BAA03390; Tue, 22 Aug 2000 01:18:40 -0500 Message-ID: <39A21A08.E6688013@raccoon.com> Date: Tue, 22 Aug 2000 01:13:28 -0500 From: John Lengeling X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: sthaug@nethelp.no Cc: freebsd-scsi@freebsd.org Subject: Re: Different init speeds of raid5 plex subdisks under vinum References: <39A21314.1107B6AD@raccoon.com> <37075.966923411@verdi.nethelp.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org sthaug@nethelp.no wrote: > > > When I ran the vinum init command to initialize the plex, one of the > > drives da2 completed the initialization 3-4 times faster than da1 > > and da3. Something like 20 minutes for da2 versus 60 minutes for > > da1/da3. Both da1 and da3 initialized at the same rate. Is this > > weird? Did da3/da1 get transfers negotiated down to slower speeds? > > Bad cabling? > > I noticed a similar problem when initializing a 4-disk RAID5 array some > weeks ago. In my case I had two disks on ATA-66 controllers and two disks > on ATA-33 - and the ATA-66 connected disks initialized at roughly double > the rate of the ATA-33 connected disks. I simply assumed it was due to > difference between the ATA-66 and ATA-33 speeds. > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no All 3 drives are on the same SCSI bus in my case. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 21 23:13:48 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6CEF337B422 for ; Mon, 21 Aug 2000 23:13:46 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA57115; Tue, 22 Aug 2000 00:13:41 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA01743; Tue, 22 Aug 2000 00:13:31 -0600 (MDT) Message-Id: <200008220613.AAA01743@harmony.village.org> To: Chuck Robey Subject: Re: ultra 160 and performance Cc: oneiros , freebsd-scsi@FreeBSD.ORG In-reply-to: Your message of "Mon, 21 Aug 2000 22:45:03 EDT." References: Date: Tue, 22 Aug 2000 00:13:31 -0600 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Chuck Robey writes: : Intel forum, but if anyone knows any secret mantras, I'm suddenly feeling : somewhat religious .... fdisk -s the disk on a machine that can read it and make sure that the partitions end on hard head boundaries. There is a bug in FreeBSD, introduced recently (just before 4.1R) that causes it to write somewhat bogus partition tables that some bioses just hate to boot. Others boot them just fine. Yes, patches are being reviewed right now, and should hit the tree soonish. Just a thought. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 22 5:59:47 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.chuckr.org (picnic.chuckr.org [216.254.96.118]) by hub.freebsd.org (Postfix) with ESMTP id 2C3D737B422 for ; Tue, 22 Aug 2000 05:59:44 -0700 (PDT) Received: from localhost (chuckr@localhost) by picnic.chuckr.org (8.9.3/8.9.3) with ESMTP id JAA02144; Tue, 22 Aug 2000 09:00:02 -0400 (EDT) (envelope-from chuckr@picnic.chuckr.org) Date: Tue, 22 Aug 2000 09:00:02 -0400 (EDT) From: Chuck Robey To: Warner Losh Cc: oneiros , freebsd-scsi@FreeBSD.ORG Subject: Re: ultra 160 and performance In-Reply-To: <200008220613.AAA01743@harmony.village.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 On Tue, 22 Aug 2000, Warner Losh wrote: > fdisk -s the disk on a machine that can read it and make sure that the > partitions end on hard head boundaries. There is a bug in FreeBSD, > introduced recently (just before 4.1R) that causes it to write > somewhat bogus partition tables that some bioses just hate to boot. > Others boot them just fine. > > Yes, patches are being reviewed right now, and should hit the tree > soonish. > > Just a thought. Surprised heck out of me, I figured anything that happened before FreeBSD could even boot couldn't possibly be FreeBSD's fault. da0 is the old 4G, da3 is the new one: ROOT:/usr/src:106 >fdisk -s /dev/da0 /dev/da0: 525 cyl 256 hd 63 sec Part Start Size Type Flags 1: 63 8467137 0xa5 0x80 ROOT:/usr/src:103 >fdisk -s /dev/da3 /dev/da3: 2231 cyl 255 hd 63 sec Part Start Size Type Flags 1: 63 35840952 0xa5 0x80 It doesn't look like that's the problem, but it was probably worth posting just in case someone else was scratching their head over it. Besides, if I move da3 to be on the DK440LX's 7895 (ch A, like da0) and have it replace da0, it boots on the 7895 just fine, it just won't boot on the 29160. I've been wondering if there's some sort of upper limit of the number of disks that the system can see (I have 2 on 7895 ch A and 3 on 7895 ch B) so the 29160 starts off as the 6th disk. The BIOS is very intelligent, it recognizes the 29160 and allows me to set the drive 0 on the 29160 as the boot drive, but when I do that, it just hangs, no boot. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.chuckr.org| electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 22 8:42:16 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front1.grolier.fr (front1.grolier.fr [194.158.96.51]) by hub.freebsd.org (Postfix) with ESMTP id 5445637B449 for ; Tue, 22 Aug 2000 08:42:13 -0700 (PDT) Received: from nas25-137.vlt.club-internet.fr (nas25-137.vlt.club-internet.fr [195.36.173.137]) by front1.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id RAA27129; Tue, 22 Aug 2000 17:41:56 +0200 (MET DST) Date: Tue, 22 Aug 2000 17:23:34 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Martin Heller Cc: bellefso@execpc.com, freebsd-scsi@freebsd.org Subject: RE: Tekram DC390U3W In-Reply-To: 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 Mon, 21 Aug 2000, Martin Heller wrote: > Sorry for my late response but I was several days without internet > connection ... > My results at power-up are: > u160 disks: needed to update firmware as they were not correctly > recognized > UW disks: somehow strange - some where correctly recognized, some not > U2W disks: everything was ok > DAT: correct > CD-ROM: correct > > booting FreeBSD4.1 I get: > u160 disks: correct (after FW update) > U2W: correct > DAT: correct > CD-ROM: correct > UW: some disks, which where reported correctly on power-up where not > during booting and vice versa > I suspect, that the FW of some UW disks is not quite up to the task. Could you explain more accurately what goes wrong with your UW disks. Do you mean that the negotiated data transfer speed at boot-up is slower than the settings configured in NVRAM ? Gerard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 22 10:17:41 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B470137B423 for ; Tue, 22 Aug 2000 10:17:38 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA60546; Tue, 22 Aug 2000 11:17:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA05514; Tue, 22 Aug 2000 11:17:20 -0600 (MDT) Message-Id: <200008221717.LAA05514@harmony.village.org> To: Chuck Robey Subject: Re: ultra 160 and performance Cc: oneiros , freebsd-scsi@FreeBSD.ORG In-reply-to: Your message of "Tue, 22 Aug 2000 09:00:02 EDT." References: Date: Tue, 22 Aug 2000 11:17:20 -0600 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Chuck Robey writes: : The BIOS is very intelligent, it recognizes the 29160 and allows me to set : the drive 0 on the 29160 as the boot drive, but when I do that, it just : hangs, no boot. Normally you get either the F1 FreeBSD prompt or the / of the spinner for boot1. I take it you get neither of these? Are you using boot0? Also, I was mistaken abut fdisk -s. It doesn't break down things properly. fdisk da3 will tell you for sure. However, since the geometry looks reasonable, I don't think the fdisk issue is the problem. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 22 15:29: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.chuckr.org (picnic.chuckr.org [216.254.96.118]) by hub.freebsd.org (Postfix) with ESMTP id 6CB9F37B423 for ; Tue, 22 Aug 2000 15:28:57 -0700 (PDT) Received: from localhost (chuckr@localhost) by picnic.chuckr.org (8.9.3/8.9.3) with ESMTP id SAA03568; Tue, 22 Aug 2000 18:29:19 -0400 (EDT) (envelope-from chuckr@picnic.chuckr.org) Date: Tue, 22 Aug 2000 18:29:19 -0400 (EDT) From: Chuck Robey To: Warner Losh Cc: oneiros , freebsd-scsi@FreeBSD.ORG Subject: Re: ultra 160 and performance In-Reply-To: <200008221717.LAA05514@harmony.village.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 On Tue, 22 Aug 2000, Warner Losh wrote: > In message Chuck Robey writes: > : The BIOS is very intelligent, it recognizes the 29160 and allows me to set > : the drive 0 on the 29160 as the boot drive, but when I do that, it just > : hangs, no boot. > > Normally you get either the F1 FreeBSD prompt or the / of the spinner > for boot1. I take it you get neither of these? Are you using boot0? Seeing as I don't know how to directly check it, after it failed with boot0cfg, I took the disk and initialized it from another machine, a clean 4.1 release install. I'm pretty sure the disk is right now, but it still fails, dark screen after the last bios boot screen (the screen when I would normally see the F1 prompt is totally dark). > Also, I was mistaken abut fdisk -s. It doesn't break down things > properly. fdisk da3 will tell you for sure. However, since the > geometry looks reasonable, I don't think the fdisk issue is the > problem. Tonight, I'm going to take it down again, and stick the old 4G disk onto the 29160, see if that boots from the new controller. Sure would like to find out it's a software problem. This one's a bit odd. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.chuckr.org| electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 22 19:41:13 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from dnai.com (dnai.com [207.181.194.98]) by hub.freebsd.org (Postfix) with ESMTP id 1FB2737B424; Tue, 22 Aug 2000 19:41:08 -0700 (PDT) Received: from azoth.dnai.com (azoth.dnai.com [207.181.194.94]) by dnai.com (8.9.3/8.9.3) with ESMTP id TAA01447; Tue, 22 Aug 2000 19:41:07 -0700 (PDT) Received: from terra (dnai-216-15-121-72.cust.dnai.com [216.15.121.72]) by azoth.dnai.com (8.9.3/8.9.3) with SMTP id TAA34197; Tue, 22 Aug 2000 19:41:06 -0700 (PDT) From: "Sam" To: , Subject: Tape problems. Date: Tue, 22 Aug 2000 19:43:47 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Right now we are using a Tekram DC-315U SCSI Adapter with an HP SureStore 24I tape drive. We are currently trying to figure out where our problems are emanating from (be it the driver, our misconfiguration, or the hardware). The problem is that whenever we attempt to use 'dump -0au -h 0 -d 61000 -f /dev/nrsa0 /home' and it reaches the end of the tape, it does not prompt for a new tape, instead it freezes the tape and gives us the following error: DUMP: write error 3725120 blocks into volume 1 and this in /var/log/messages (nothing relevant has been omitted): Aug 14 20:08:55 sol /kernel: (sa0:tekram_trm0:0:3:0): failed to write terminating f ilemark(s) Aug 14 20:08:56 sol /kernel: (sa0:tekram_trm0:0:3:0): tape is now frozen- use an OF FLINE, REWIND or MTEOM command to clear this state. In addition to this problem we cannot use restore on archives that we have dumped without specifying the tape density to dump (-d 61000). It may be noted that the drivers for our Tekram DC-315U SCSI Adapter are not part of the FreeBSD kernel, but Tekram provides a patch to the kernel source on their website. We can backup fine under Windows with the same hardware, and we have tried both FreeBSD 3.5-STABLE and 4.1-STABLE. We are really enjoying using FreeBSD, and would hate for a problem like this to force us to use that other open-source operating system. Any input would be greatly appreciated. Free Print Shop 3145 23rd St San Francisco, 94110 Phone: 415.648.3222 Fax: 415.648.4466 Website: http://freeprintshop.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 22 21:29:26 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 A88AD37B42C; Tue, 22 Aug 2000 21:29:13 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id VAA01917; Tue, 22 Aug 2000 21:29:11 -0700 Date: Tue, 22 Aug 2000 21:29:15 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Sam Cc: freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Tape problems. In-Reply-To: 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 I said to you in private mail, which you seem to not read, I don't believe that early warning is occurring. I asked you whether or not the workaround of specifying a tape length (that I told you) is working for you. -matt On Tue, 22 Aug 2000, Sam wrote: > Right now we are using a Tekram DC-315U SCSI Adapter with an HP SureStore > 24I tape drive. We are currently trying to figure out where our problems are > emanating from (be it the driver, our misconfiguration, or the hardware). > The problem is that whenever we attempt to use 'dump -0au -h 0 -d 61000 -f > /dev/nrsa0 /home' and it reaches the end of the tape, it does not prompt for > a new tape, instead it freezes the tape and gives us the following error: > > DUMP: write error 3725120 blocks into volume 1 > > and this in /var/log/messages (nothing relevant has been omitted): > > Aug 14 20:08:55 sol /kernel: (sa0:tekram_trm0:0:3:0): failed to write > terminating f > ilemark(s) > Aug 14 20:08:56 sol /kernel: (sa0:tekram_trm0:0:3:0): tape is now frozen- > use an OF > FLINE, REWIND or MTEOM command to clear this state. > > In addition to this problem we cannot use restore on archives that we have > dumped without specifying the tape density to dump (-d 61000). It may be > noted that the drivers for our Tekram DC-315U SCSI Adapter are not part of > the FreeBSD kernel, but Tekram provides a patch to the kernel source on > their website. > > We can backup fine under Windows with the same hardware, and we have tried > both FreeBSD 3.5-STABLE and 4.1-STABLE. We are really enjoying using > FreeBSD, and would hate for a problem like this to force us to use that > other open-source operating system. > > Any input would be greatly appreciated. > > Free Print Shop > 3145 23rd St > San Francisco, 94110 > Phone: 415.648.3222 > Fax: 415.648.4466 > Website: http://freeprintshop.org > > > > > 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 Wed Aug 23 1:57:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail-service.wias-berlin.de (descartes.wias-berlin.de [192.124.249.194]) by hub.freebsd.org (Postfix) with ESMTP id D636037B42C for ; Wed, 23 Aug 2000 01:57:27 -0700 (PDT) Received: from wias-berlin.de by mail-service.wias-berlin.de (8.8.8/1.1.22.3/16Mar99-0205PM) id KAA0000028698; Wed, 23 Aug 2000 10:57:26 +0200 (MET DST) Received: from localhost by wias-berlin.de (8.8.8/1.1.10.5/07Oct97-0932AM) id KAA0000002957; Wed, 23 Aug 2000 10:57:25 +0200 (MET DST) To: freebsd-scsi@freebsd.org Subject: NCR SCSI controller problems with FreeBSD-4.1R From: Jens Andre Griepentrog Reply-To: griepent@wias-berlin.de X-Mailer: Mew version 1.94.1 on Emacs 19.33 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000823105725P.griepent@hilbert.wias-berlin.de> Date: Wed, 23 Aug 2000 10:57:25 +0200 X-Dispatcher: imput version 990905(IM130) Lines: 35 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear FreeBSD and SCSI experts! I have tried to install FreeBSD 4.1 Release from CD-ROM (4.1-install.iso). Using the boot floppies kern.flp and mfsroot.flp the system hangs up during the detection and settlement of SCSI devices. None of my five SCSI devices connected to the ASUS SC-200 NCR SCSI controller appears in the boot display messages. Here is the short list of relevant hardware components: ASUS P6NP5 Intel Pentium Pro 200 mother board, three IBM and Quantum SCSI hard drives, Tandberg SCSI QIC streamer, Plextor SCSI CD-ROM. Using the same hardware this problem appears for the first time in my four-year experience with successful installed releases 2.1, 2.2, 3.1 or 3.4. From time to time I tried to install several Linux distributions to get the impression of a comparable OS but every time running into the same trouble concerning the detection of SCSI devices. The deeper reason could be a problem with the NCR SCSI controller because of reported code modifications after release 3.4. It would be nice if you could give me hint. Let me know if you need more details about my hardware or BIOS settings. For instance I can send a dmesg log file from my current FreeBSD-3.4 installation. So long, Jens Griepentrog To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 23 5:44: 6 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front7.grolier.fr (front7.grolier.fr [194.158.96.57]) by hub.freebsd.org (Postfix) with ESMTP id BB49337B423 for ; Wed, 23 Aug 2000 05:44:00 -0700 (PDT) Received: from nas22-154.vlt.club-internet.fr (nas22-154.vlt.club-internet.fr [195.36.170.154]) by front7.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id OAA02881; Wed, 23 Aug 2000 14:43:25 +0200 (MET DST) Date: Wed, 23 Aug 2000 14:25:06 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Jens Andre Griepentrog Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: NCR SCSI controller problems with FreeBSD-4.1R In-Reply-To: <20000823105725P.griepent@hilbert.wias-berlin.de> 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 I would suggest the following: 1) Check that your SC-200 is configured for PCI INT A. If it is not, change jumpers accordingly. 2) Move you board to another PCI slot. 3) Check/set SCSI termination properly. If either (1) and/or (2) and/or (3) does not cure, then send me any dmesg you have. You also could try to catch manually driver messages that look like complaint about something going wrong under FreeBSD and/or Linux as well. The fact that your system experiences the problem also under Linux and given that the ncr(4) driver (used in 3.4) also polls interrupts using a timer, it might well be that hardware interrupts are not functionning properly for your SC-200 (just a guessing). Gerard. On Wed, 23 Aug 2000, Jens Andre Griepentrog wrote: > Dear FreeBSD and SCSI experts! > > I have tried to install FreeBSD 4.1 Release from CD-ROM (4.1-install.iso). > Using the boot floppies kern.flp and mfsroot.flp the system hangs up during > the detection and settlement of SCSI devices. None of my five SCSI devices > connected to the ASUS SC-200 NCR SCSI controller appears in the boot display > messages. Here is the short list of relevant hardware components: > > ASUS P6NP5 Intel Pentium Pro 200 mother board, > three IBM and Quantum SCSI hard drives, > Tandberg SCSI QIC streamer, > Plextor SCSI CD-ROM. > > Using the same hardware this problem appears for the first time in my > four-year experience with successful installed releases 2.1, 2.2, 3.1 or 3.4. > > >From time to time I tried to install several Linux distributions to get > the impression of a comparable OS but every time running into the same > trouble concerning the detection of SCSI devices. > > The deeper reason could be a problem with the NCR SCSI controller because > of reported code modifications after release 3.4. > > It would be nice if you could give me hint. Let me know if you need more > details about my hardware or BIOS settings. For instance I can send a dmesg > log file from my current FreeBSD-3.4 installation. > > So long, > > Jens Griepentrog To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 23 19:41: 1 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id E3DB537B422 for ; Wed, 23 Aug 2000 19:40:54 -0700 (PDT) Received: from nospam.hiwaay.net (tnt8-216-180-71-236.dialup.hiwaay.net [216.180.71.236]) by mail.hiwaay.net (8.11.0/8.11.0) with ESMTP id e7O2ep716545; Wed, 23 Aug 2000 21:40:52 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id UAA36595; Wed, 23 Aug 2000 20:02:43 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <200008240102.UAA36595@nospam.hiwaay.net> X-Mailer: exmh version 2.1.1 10/15/1999 To: griepent@wias-berlin.de Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: NCR SCSI controller problems with FreeBSD-4.1R In-Reply-To: Message from Jens Andre Griepentrog of "Wed, 23 Aug 2000 10:57:25 +0200." <20000823105725P.griepent@hilbert.wias-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Aug 2000 20:02:43 -0500 From: David Kelly Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jens Andre Griepentrog writes: > >From time to time I tried to install several Linux distributions to get > the impression of a comparable OS but every time running into the same > trouble concerning the detection of SCSI devices. You didn't say, but this configuration works under something? Even Windows? Is there a BIOS SCSI probe utility? One where you can list devices? The P6NP5 manual acts like it contains the SC-200 manual too. Says there is an "auto NCR BIOS" setting, offering the ability to use a BIOS on the card (which the less expensive cards lack) or the same built into the MB BIOS. You might check this. Also consider flashing your BIOS to whatever current version is available. I too have a P6NP5 PPro system. New out of the box it did the darndest things. Floppy drive was flakey under FreeBSD but worked under DOS. Fought it for weeks. Then on a lark in the BIOS setup I hit "restore to factory defaults" then punched selected things back to where I wanted them. System has purred like a kitten ever since. Forgot when this was. Seems like the P-II 266 was just out. I'm running a PPro-166/512k, (now) overclocked to 210. The conclusion is there are hardware parameters that can be set in the BIOS BBRAM that do not have an interface for changing in the BIOS setup program. Parameters that apparently Microsoft knows about and is able to put into sane state after boot. And while we are at it, this BIOS allows you control over IRQ assignments. I don't remember why but I have my SC-875 on IRQ 11 all by itself with all the rest of my PCI stuff (including an old 2940) mux'ed on IRQ 15. Then again it works and no reason to change it. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 23 22:39:44 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from theshell.com (arsenic.theshell.com [63.236.138.5]) by hub.freebsd.org (Postfix) with SMTP id 8AE6837B43E for ; Wed, 23 Aug 2000 22:39:41 -0700 (PDT) Received: (qmail 5961 invoked by uid 500); 24 Aug 2000 05:39:58 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 24 Aug 2000 05:39:58 -0000 Date: Wed, 23 Aug 2000 22:39:58 -0700 (PDT) From: "Barrett G. Lyon" To: freebsd-scsi@freebsd.org Subject: Adaptec 3960D Ultra160 issues 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 I would like to pre-apologize if I am posting this to the wrong list. I am running FreeBSD 4.1-STABLE on x86 with this Adaptec 3960D Ultra160 SCSI controller using an IBM DDYS-T09170N Ultra160 disk. The machine locks up weekly on any heavy load. It was crashing when the vm system would get stressed so we added more memory and now it is only crashing with the filesystem is stressed (I think). One of the problems is that the Ultra160 disk (the IBM one) is not coming up at 80 MHz only at 40 MHz: da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled I'm not sure why that is happening because the SCSI adapter in the bios detects it and shows it listed as operating at u160. I figured it could be a driver issue so I updated from 4.0 to 4.1 and that seemed to not help too much. Here is the debugger output from today's crash: (da0:ahc1:0:6:0): Invalidating pack (da0:ahc1:0:6:0): Invalidating pack (da0:ahc1:0:6:0): Invalidating pack (da0:ahc1:0:6:0): Invalidating pack (da0:ahc1:0:6:0): Invalidating pack dev = #da/0x20005, ino = 902, fs = /usr panic: ffs_vfree: freeing free inode Debugger("panic") Stopped at Debugger+0x34: movb $0,in_Debugger.390 db> next Stopped at Debugger+0x3c: ret db> next syncing disks... (da0:ahc1:0:6:0): Invalidating pack (da0:ahc1:0:6:0): Invalidating pack (da0:ahc1:0:6:0): Invalidating pack (da0:ahc1:0:6:0): Invalidating pack (da0:ahc1:0:6:0): Invalidating pack (da0:ahc1:0:6:0): Invalidating pack (on and on) I'm not much of a BSD genius, any help would be very appreciated. -Barrett Barrett G. Lyon Have fun: www.AlphaLinux.org [Q]: Hey, do they test this stuff before it's released? [A]: Sure they do... "It compiles, it's ready!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 23 22:49:27 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id BE60B37B43C for ; Wed, 23 Aug 2000 22:49:24 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id 789EC2B2BC; Thu, 24 Aug 2000 00:49:24 -0500 (CDT) Date: Wed, 23 Aug 2000 22:49:24 -0700 From: Paul Saab To: "Barrett G. Lyon" Cc: freebsd-scsi@freebsd.org Subject: Re: Adaptec 3960D Ultra160 issues Message-ID: <20000823224924.A90931@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from blyon@theshell.com on Wed, Aug 23, 2000 at 10:39:58PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Turn off write caching. On recent 4.1 stable echo "WCE: 0" | camcontrol modepage da0 -m 8 -P 3 On older 4.1 stable EDITOR="/usr/bin/perl -i -pe 's/1/0/g if /^WCE/'" camcontrol \ modepage da0 -m 8 -P 3 Its a bug with U160 drives these days.. The otherway to fix it is to get an updated firmware from your drive manufacturer. paul Barrett G. Lyon (blyon@theshell.com) wrote: > > I would like to pre-apologize if I am posting this to the wrong list. I > am running FreeBSD 4.1-STABLE on x86 with this Adaptec 3960D Ultra160 SCSI > controller using an IBM DDYS-T09170N Ultra160 disk. The machine locks up > weekly on any heavy load. It was crashing when the vm system would get > stressed so we added more memory and now it is only crashing with the > filesystem is stressed (I think). > > One of the problems is that the Ultra160 disk (the IBM one) is not coming > up at 80 MHz only at 40 MHz: > > da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled > > I'm not sure why that is happening because the SCSI adapter in the bios > detects it and shows it listed as operating at u160. I figured it could > be a driver issue so I updated from 4.0 to 4.1 and that seemed to not help > too much. > > Here is the debugger output from today's crash: > > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > dev = #da/0x20005, ino = 902, fs = /usr > panic: ffs_vfree: freeing free inode > Debugger("panic") > Stopped at Debugger+0x34: movb $0,in_Debugger.390 > db> next > Stopped at Debugger+0x3c: ret > db> next > > syncing disks... (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (da0:ahc1:0:6:0): Invalidating pack > (on and on) > > > I'm not much of a BSD genius, any help would be very appreciated. > > -Barrett > > > > Barrett G. Lyon > Have fun: www.AlphaLinux.org > > [Q]: Hey, do they test this stuff before it's released? > [A]: Sure they do... "It compiles, it's ready!" > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 23 23:28:49 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from theshell.com (arsenic.theshell.com [63.236.138.5]) by hub.freebsd.org (Postfix) with SMTP id C713937B42C for ; Wed, 23 Aug 2000 23:28:47 -0700 (PDT) Received: (qmail 10857 invoked by uid 500); 24 Aug 2000 06:29:04 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 24 Aug 2000 06:29:04 -0000 Date: Wed, 23 Aug 2000 23:29:04 -0700 (PDT) From: "Barrett G. Lyon" To: Paul Saab Cc: freebsd-scsi@freebsd.org Subject: Re: Adaptec 3960D Ultra160 issues In-Reply-To: <20000823224924.A90931@elvis.mu.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 /- Wed, 23 Aug 2000, owner-freebsd-scsi@FreeBSD.ORG (paul@mu.org) | Turn off write caching. | On recent 4.1 stable | echo "WCE: 0" | camcontrol modepage da0 -m 8 -P 3 | On older 4.1 stable | EDITOR="/usr/bin/perl -i -pe 's/1/0/g if /^WCE/'" camcontrol \ | modepage da0 -m 8 -P 3 | | Its a bug with U160 drives these days.. The otherway to fix it is to | get an updated firmware from your drive manufacturer. \- Paul: Thank you, I hope that will do the trick. I found a write cache option in the adaptec bios as well and set that all to no. As an unrelated problem I am still having the disk come up as 40 MHz, I am not sure why it will not run at 80 MHz. -Barrett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 23 23:31:37 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 839F537B422 for ; Wed, 23 Aug 2000 23:31:35 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA93021; Thu, 24 Aug 2000 00:31:14 -0600 (MDT) (envelope-from ken) Date: Thu, 24 Aug 2000 00:31:14 -0600 From: "Kenneth D. Merry" To: "Barrett G. Lyon" Cc: Paul Saab , freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 3960D Ultra160 issues Message-ID: <20000824003114.A92995@panzer.kdm.org> References: <20000823224924.A90931@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from blyon@theshell.com on Wed, Aug 23, 2000 at 11:29:04PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Aug 23, 2000 at 23:29:04 -0700, Barrett G. Lyon wrote: > /- Wed, 23 Aug 2000, owner-freebsd-scsi@FreeBSD.ORG (paul@mu.org) > | Turn off write caching. > | On recent 4.1 stable > | echo "WCE: 0" | camcontrol modepage da0 -m 8 -P 3 > | On older 4.1 stable > | EDITOR="/usr/bin/perl -i -pe 's/1/0/g if /^WCE/'" camcontrol \ > | modepage da0 -m 8 -P 3 > | > | Its a bug with U160 drives these days.. The otherway to fix it is to > | get an updated firmware from your drive manufacturer. > \- > > Paul: > > Thank you, I hope that will do the trick. I found a write cache option in > the adaptec bios as well and set that all to no. As an unrelated > problem I am still having the disk come up as 40 MHz, I am not sure why it > will not run at 80 MHz. The Ultra160 code for Adaptec cards hasn't been merged yet. When Justin merges it (I don't know when, you'll have to send mail to gibbs@FreeBSD.org to find out what his plans are) in from -current, your disks should negotiate at Ultra160 speeds. 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 Thu Aug 24 5:41:19 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.chuckr.org (picnic.chuckr.org [216.254.96.118]) by hub.freebsd.org (Postfix) with ESMTP id 3EE3B37B42C for ; Thu, 24 Aug 2000 05:41:17 -0700 (PDT) Received: from localhost (chuckr@localhost) by picnic.chuckr.org (8.9.3/8.9.3) with ESMTP id IAA99444; Thu, 24 Aug 2000 08:41:24 -0400 (EDT) (envelope-from chuckr@picnic.chuckr.org) Date: Thu, 24 Aug 2000 08:41:24 -0400 (EDT) From: Chuck Robey To: Paul Saab Cc: "Barrett G. Lyon" , freebsd-scsi@FreeBSD.ORG, George Morgan Subject: Re: Adaptec 3960D Ultra160 issues In-Reply-To: <20000823224924.A90931@elvis.mu.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 On Wed, 23 Aug 2000, Paul Saab wrote: > Turn off write caching. > On recent 4.1 stable > echo "WCE: 0" | camcontrol modepage da0 -m 8 -P 3 > On older 4.1 stable > EDITOR="/usr/bin/perl -i -pe 's/1/0/g if /^WCE/'" camcontrol \ > modepage da0 -m 8 -P 3 > > Its a bug with U160 drives these days.. The otherway to fix it is to > get an updated firmware from your drive manufacturer. Paul, George Morgan and I (see I added him to the CC:, he's not subscribed) are both seeing problems with inability to boot IBM Ultra 160 drives (he on a Adaptec 39160, me on a 29160). Can you tell me where you saw the stuff on this problem, so I can read up on it and see if there's some sort of fix for us? Thanks. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.chuckr.org| electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 24 8: 2:57 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 61E4E37B43E; Thu, 24 Aug 2000 08:02:04 -0700 (PDT) Received: from office.tor.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id ACAF8137F32; Thu, 24 Aug 2000 11:02:02 -0400 (EDT) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.9.3/8.9.3) id LAA64688; Thu, 24 Aug 2000 11:02:02 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="BzGFJYjy6O" Content-Transfer-Encoding: 7bit Message-ID: <14757.14569.732766.367692@trooper.velocet.net> Date: Thu, 24 Aug 2000 11:02:01 -0400 (EDT) To: freebsd-stable@freebsd.org, freebsd-scsi@freebsd.org Subject: Vinum 29160 detaches drives, invalidates RAID. X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --BzGFJYjy6O Content-Type: text/plain; charset=us-ascii Content-Description: message body text Content-Transfer-Encoding: 7bit I have a vinum test box with 8x driven by 2x running 4.1-RELEASE. The machine also has a 9G root SCSI drive that is on a non-LVD connector of the 29160 card. I'll include all the probe messages 'n such at the end, but I want to get to the description first. The 18G drives are all VINUM. It results in Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/vinum/raid 121691956 14986173 96970427 13% /raid I have loaded the drive with a copy of the FreeBSD cvs tree (that I cvsup) and a checked-out copy of the tree. I believe there is also a copy of the results of a make-release and other misc garbage. The drives are cabled 4 per controller with a certified LVD cable that ends with a certified LVD terminator. The root drive has a regular SCSI-2 cable and also an SE/LVD terminator. The 8 drives are in a separate case with redundant (and definately adequate) power. The root drive is on the main case's power. The whole thing is running on a PIII/450 with either 128M or 256M of RAM (depending on what I'm testing). ... so we know what the hardware is. I've been careful to cable and do this all properly. First of all, I'm very pleased with the speed. The system easily beats the AMI MegaRAID 1500 (same drives) with a whopping 35Mbyte/s in RAID-5 (vs. the 1500's 14Mbyte/s) for read. (They both score a dead heat of 4Mbyte/s write.) I have had no troubles with cvsup'ing and no troubles with multiple concurrent cvs checkouts. I have a script that tells me that the 8 drives are dispatching from 500 to 1000 transactions a second (summing up all the iostat figures) and "cvs update" on the FreeBSD src directory can get a combined r/w performance of about 5Mbyte/s on the array. However, the nightly find scripts almost always disable the array. Many, many messages of the form Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x4a - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout resulting in Aug 24 02:04:44 news /kernel: raid.p0.s4: fatal write I/O error Aug 24 02:04:44 news /kernel: vinum: raid.p0.s4 is stale by force Aug 24 02:04:44 news /kernel: vinum: raid.p0 is degraded and then (as other disks do the same) Aug 24 02:04:44 news /kernel: raid.p0.s5: fatal read I/O error Aug 24 02:04:44 news /kernel: vinum: raid.p0.s5 is crashed by force Aug 24 02:04:44 news /kernel: vinum: raid.p0 is corrupt Now... if I reboot, and "vinum setstate up" all these drives, fsck completes without any complaint. I then generally have to "vinum rebuild parity" ... but I suppose that I'd expect that. The problem I'm having here (and I've had it before) is that the FreeBSD SCSI system seems to "give up" under conditions that others would keep retrying or resetting/retrying. It seems really, really, really important to me that we try harder to get a drive back online. This seems as if it could affect the long-term viability of a vinum-based raid server... not because vinum is bad, but because the SCSI subsystem is too fragile. --BzGFJYjy6O Content-Type: text/plain Content-Disposition: inline; filename="foo" Content-Transfer-Encoding: 7bit Aug 8 13:00:00 news newsyslog[408]: logfile turned over Aug 8 13:19:11 news ntpd[236]: time reset -0.210431 s Aug 8 16:00:04 news ntpd[236]: time reset -0.192604 s Aug 10 22:01:17 news shutdown: reboot by root: Aug 10 22:01:19 news syslogd: exiting on signal 15 Aug 10 22:16:07 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 10 22:16:07 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 10 22:16:07 news /kernel: The Regents of the University of California. All rights reserved. Aug 10 22:16:07 news /kernel: FreeBSD 4.1-RELEASE #100: Wed Aug 2 11:22:31 EDT 2000 Aug 10 22:16:07 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 10 22:16:07 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 10 22:16:07 news /kernel: Timecounter "TSC" frequency 451024838 Hz Aug 10 22:16:07 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.02-MHz 686-class CPU) Aug 10 22:16:07 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 10 22:16:07 news /kernel: Features=0x383f9ff Aug 10 22:16:07 news /kernel: real memory = 134201344 (131056K bytes) Aug 10 22:16:07 news /kernel: avail memory = 127328256 (124344K bytes) Aug 10 22:16:07 news /kernel: Preloaded elf kernel "kernel" at 0xc030a000. Aug 10 22:16:07 news /kernel: Pentium Pro MTRR support enabled Aug 10 22:16:07 news /kernel: md0: Malloc disk Aug 10 22:16:07 news /kernel: npx0: on motherboard Aug 10 22:16:07 news /kernel: npx0: INT 16 interface Aug 10 22:16:07 news /kernel: pcib0: on motherboard Aug 10 22:16:07 news /kernel: pci0: on pcib0 Aug 10 22:16:07 news /kernel: pcib1: at device 1.0 on pci0 Aug 10 22:16:07 news /kernel: pci1: on pcib1 Aug 10 22:16:07 news /kernel: pci1: at 0.0 irq 11 Aug 10 22:16:07 news /kernel: isab0: at device 4.0 on pci0 Aug 10 22:16:07 news /kernel: isa0: on isab0 Aug 10 22:16:07 news /kernel: pci0: at 4.1 Aug 10 22:16:07 news /kernel: pci0: at 4.2 irq 12 Aug 10 22:16:07 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 10 22:16:07 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 10 22:16:07 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 10 22:16:07 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 10 22:16:07 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 10 22:16:07 news /kernel: miibus0: on rl0 Aug 10 22:16:07 news /kernel: rlphy0: on miibus0 Aug 10 22:16:07 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 10 22:16:07 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 10 22:16:07 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 10 22:16:07 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 10 22:16:07 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 10 22:16:07 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 10 22:16:07 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 10 22:16:07 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 10 22:16:07 news /kernel: sc0: on isa0 Aug 10 22:16:07 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 10 22:16:07 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 10 22:16:07 news /kernel: sio0: type 16550A Aug 10 22:16:07 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 10 22:16:07 news /kernel: sio1: type 16550A Aug 10 22:16:07 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 10 22:16:07 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 10 22:16:07 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 10 22:16:07 news /kernel: ppi0: on ppbus0 Aug 10 22:16:07 news /kernel: lpt0: on ppbus0 Aug 10 22:16:07 news /kernel: lpt0: Interrupt-driven port Aug 10 22:16:07 news /kernel: plip0: on ppbus0 Aug 10 22:16:07 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 10 22:16:07 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 10 22:16:07 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 10 22:16:07 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 10 22:16:07 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 10 22:16:07 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 10 22:16:07 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 10 22:16:07 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 10 22:16:07 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 10 22:16:07 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 10 22:16:07 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 10 22:16:07 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 10 22:16:07 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 10 22:16:07 news /kernel: vinum: loaded Aug 10 22:16:07 news /kernel: vinum: reading configuration from /dev/da8s1g Aug 10 22:16:07 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 10 22:16:07 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 10 22:16:07 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 10 22:16:07 news /kernel: vinum: updating configuration from /dev/da7s1g Aug 10 22:16:07 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 10 22:16:07 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 10 22:16:07 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 10 22:16:08 news savecore: no core dump Aug 10 22:16:04 news ntpd[169]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 10 22:16:04 news ntpd[169]: using kernel phase-lock loop 2040 Aug 11 01:14:45 news ntpd[169]: time reset -0.133956 s Aug 11 12:45:25 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 11 12:45:25 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 11 12:45:25 news /kernel: The Regents of the University of California. All rights reserved. Aug 11 12:45:25 news /kernel: FreeBSD 4.1-RELEASE #100: Wed Aug 2 11:22:31 EDT 2000 Aug 11 12:45:25 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 11 12:45:25 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 11 12:45:25 news /kernel: Timecounter "TSC" frequency 451024955 Hz Aug 11 12:45:25 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.02-MHz 686-class CPU) Aug 11 12:45:25 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 11 12:45:25 news /kernel: Features=0x383f9ff Aug 11 12:45:25 news /kernel: real memory = 134201344 (131056K bytes) Aug 11 12:45:25 news /kernel: avail memory = 127328256 (124344K bytes) Aug 11 12:45:25 news /kernel: Preloaded elf kernel "kernel" at 0xc030a000. Aug 11 12:45:25 news /kernel: Pentium Pro MTRR support enabled Aug 11 12:45:25 news /kernel: md0: Malloc disk Aug 11 12:45:26 news /kernel: npx0: on motherboard Aug 11 12:45:26 news /kernel: npx0: INT 16 interface Aug 11 12:45:26 news /kernel: pcib0: on motherboard Aug 11 12:45:26 news /kernel: pci0: on pcib0 Aug 11 12:45:26 news /kernel: pcib1: at device 1.0 on pci0 Aug 11 12:45:26 news /kernel: pci1: on pcib1 Aug 11 12:45:26 news /kernel: pci1: at 0.0 irq 11 Aug 11 12:45:26 news /kernel: isab0: at device 4.0 on pci0 Aug 11 12:45:26 news /kernel: isa0: on isab0 Aug 11 12:45:26 news /kernel: pci0: at 4.1 Aug 11 12:45:26 news /kernel: pci0: at 4.2 irq 12 Aug 11 12:45:26 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 11 12:45:26 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 11 12:45:26 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 11 12:45:26 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 11 12:45:26 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 11 12:45:26 news /kernel: miibus0: on rl0 Aug 11 12:45:26 news /kernel: rlphy0: on miibus0 Aug 11 12:45:26 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 11 12:45:26 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 11 12:45:26 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 11 12:45:26 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 11 12:45:26 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 11 12:45:26 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 11 12:45:26 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 11 12:45:26 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 11 12:45:26 news /kernel: sc0: on isa0 Aug 11 12:45:26 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 11 12:45:26 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 11 12:45:26 news /kernel: sio0: type 16550A Aug 11 12:45:26 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 11 12:45:26 news /kernel: sio1: type 16550A Aug 11 12:45:26 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 11 12:45:26 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 11 12:45:26 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 11 12:45:26 news /kernel: ppi0: on ppbus0 Aug 11 12:45:26 news /kernel: lpt0: on ppbus0 Aug 11 12:45:26 news /kernel: lpt0: Interrupt-driven port Aug 11 12:45:26 news /kernel: plip0: on ppbus0 Aug 11 12:45:26 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 11 12:45:26 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 11 12:45:26 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 11 12:45:26 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 11 12:45:26 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 11 12:45:26 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 11 12:45:26 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 11 12:45:26 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 11 12:45:26 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 11 12:45:26 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 11 12:45:26 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 11 12:45:26 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 11 12:45:26 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 11 12:45:26 news /kernel: WARNING: / was not properly dismounted Aug 11 12:45:26 news /kernel: vinum: loaded Aug 11 12:45:26 news /kernel: vinum: reading configuration from /dev/da8s1g Aug 11 12:45:26 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 11 12:45:26 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 11 12:45:26 news /kernel: vinum: updating configuration from /dev/da7s1g Aug 11 12:45:26 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 11 12:45:26 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 11 12:45:26 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 11 12:45:26 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 11 12:45:26 news savecore: no core dump Aug 11 12:45:27 news ntpd[169]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 11 12:45:27 news ntpd[169]: using kernel phase-lock loop 2040 Aug 11 12:50:00 news ntpd[169]: time reset -0.317034 s Aug 11 12:50:00 news ntpd[169]: kernel pll status change 2041 Aug 11 13:09:29 news ntpd[169]: time reset 0.353537 s Aug 11 13:35:09 news ntpd[169]: time reset -0.289343 s Aug 11 15:06:05 news ntpd[169]: time reset -0.208662 s Aug 15 17:01:33 news ntpd[169]: time reset -0.213926 s Aug 15 17:20:53 news ntpd[169]: time reset 0.328963 s Aug 15 23:22:26 news ntpd[169]: time reset -0.152637 s Aug 18 02:09:05 news /kernel: Data modified on freelist: word 0 of object 0xc269a000 size 4096 previous type devbuf (0x0 != 0xdeadc0de) Aug 18 13:03:13 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 18 13:03:13 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 18 13:03:13 news /kernel: The Regents of the University of California. All rights reserved. Aug 18 13:03:13 news /kernel: FreeBSD 4.1-RELEASE #100: Wed Aug 2 11:22:31 EDT 2000 Aug 18 13:03:13 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 18 13:03:13 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 18 13:03:13 news /kernel: Timecounter "TSC" frequency 451025238 Hz Aug 18 13:03:13 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.03-MHz 686-class CPU) Aug 18 13:03:13 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 18 13:03:13 news /kernel: Features=0x383f9ff Aug 18 13:03:13 news /kernel: real memory = 134201344 (131056K bytes) Aug 18 13:03:13 news /kernel: avail memory = 127328256 (124344K bytes) Aug 18 13:03:13 news /kernel: Preloaded elf kernel "kernel" at 0xc030a000. Aug 18 13:03:13 news /kernel: Pentium Pro MTRR support enabled Aug 18 13:03:13 news /kernel: md0: Malloc disk Aug 18 13:03:13 news /kernel: npx0: on motherboard Aug 18 13:03:13 news /kernel: npx0: INT 16 interface Aug 18 13:03:13 news /kernel: pcib0: on motherboard Aug 18 13:03:13 news /kernel: pci0: on pcib0 Aug 18 13:03:13 news /kernel: pcib1: at device 1.0 on pci0 Aug 18 13:03:13 news /kernel: pci1: on pcib1 Aug 18 13:03:13 news /kernel: pci1: at 0.0 irq 11 Aug 18 13:03:13 news /kernel: isab0: at device 4.0 on pci0 Aug 18 13:03:13 news /kernel: isa0: on isab0 Aug 18 13:03:13 news /kernel: pci0: at 4.1 Aug 18 13:03:13 news /kernel: pci0: at 4.2 irq 12 Aug 18 13:03:13 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 18 13:03:13 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 18 13:03:13 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 13:03:13 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 18 13:03:13 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 18 13:03:13 news /kernel: miibus0: on rl0 Aug 18 13:03:13 news /kernel: rlphy0: on miibus0 Aug 18 13:03:13 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 18 13:03:13 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 18 13:03:13 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 13:03:14 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 18 13:03:14 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 18 13:03:14 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 18 13:03:14 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 18 13:03:14 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 18 13:03:14 news /kernel: sc0: on isa0 Aug 18 13:03:14 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 18 13:03:14 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 18 13:03:14 news /kernel: sio0: type 16550A Aug 18 13:03:14 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 18 13:03:14 news /kernel: sio1: type 16550A Aug 18 13:03:14 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 18 13:03:14 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 18 13:03:14 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 18 13:03:14 news /kernel: ppi0: on ppbus0 Aug 18 13:03:14 news /kernel: lpt0: on ppbus0 Aug 18 13:03:14 news /kernel: lpt0: Interrupt-driven port Aug 18 13:03:14 news /kernel: plip0: on ppbus0 Aug 18 13:03:14 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 18 13:03:14 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 18 13:03:14 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 18 13:03:14 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 18 13:03:14 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 18 13:03:14 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 18 13:03:14 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 18 13:03:14 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 18 13:03:14 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 18 13:03:14 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 18 13:03:14 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 18 13:03:14 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 18 13:03:14 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 18 13:03:14 news /kernel: WARNING: / was not properly dismounted Aug 18 13:03:14 news /kernel: vinum: loaded Aug 18 13:03:14 news /kernel: vinum: reading configuration from /dev/da8s1g Aug 18 13:03:14 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 18 13:03:14 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 18 13:03:14 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 18 13:03:14 news /kernel: vinum: updating configuration from /dev/da7s1g Aug 18 13:03:14 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 18 13:03:14 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 18 13:03:14 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 18 13:03:14 news savecore: no core dump Aug 18 13:03:11 news ntpd[169]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 18 13:03:11 news ntpd[169]: using kernel phase-lock loop 2040 Aug 18 12:41:34 news halt: halted by root Aug 18 16:41:34 news syslogd: exiting on signal 15 Aug 18 16:48:20 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 18 16:48:20 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 18 16:48:20 news /kernel: The Regents of the University of California. All rights reserved. Aug 18 16:48:20 news /kernel: FreeBSD 4.1-RELEASE #100: Wed Aug 2 11:22:31 EDT 2000 Aug 18 16:48:20 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 18 16:48:20 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 18 16:48:20 news /kernel: Timecounter "TSC" frequency 451025041 Hz Aug 18 16:48:20 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.03-MHz 686-class CPU) Aug 18 16:48:20 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 18 16:48:20 news /kernel: Features=0x383f9ff Aug 18 16:48:20 news /kernel: real memory = 134201344 (131056K bytes) Aug 18 16:48:20 news /kernel: avail memory = 127328256 (124344K bytes) Aug 18 16:48:20 news /kernel: Preloaded elf kernel "kernel" at 0xc030a000. Aug 18 16:48:20 news /kernel: Pentium Pro MTRR support enabled Aug 18 16:48:20 news /kernel: md0: Malloc disk Aug 18 16:48:20 news /kernel: npx0: on motherboard Aug 18 16:48:20 news /kernel: npx0: INT 16 interface Aug 18 16:48:20 news /kernel: pcib0: on motherboard Aug 18 16:48:20 news /kernel: pci0: on pcib0 Aug 18 16:48:20 news /kernel: pcib1: at device 1.0 on pci0 Aug 18 16:48:20 news /kernel: pci1: on pcib1 Aug 18 16:48:20 news /kernel: pci1: at 0.0 irq 11 Aug 18 16:48:20 news /kernel: isab0: at device 4.0 on pci0 Aug 18 16:48:20 news /kernel: isa0: on isab0 Aug 18 16:48:20 news /kernel: pci0: at 4.1 Aug 18 16:48:20 news /kernel: pci0: at 4.2 irq 12 Aug 18 16:48:20 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 18 16:48:20 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 18 16:48:20 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 16:48:20 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 18 16:48:20 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 18 16:48:20 news /kernel: miibus0: on rl0 Aug 18 16:48:20 news /kernel: rlphy0: on miibus0 Aug 18 16:48:20 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 18 16:48:20 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 18 16:48:20 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 16:48:20 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 18 16:48:20 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 18 16:48:20 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 18 16:48:20 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 18 16:48:20 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 18 16:48:20 news /kernel: sc0: on isa0 Aug 18 16:48:20 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 18 16:48:20 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 18 16:48:20 news /kernel: sio0: type 16550A Aug 18 16:48:20 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 18 16:48:20 news /kernel: sio1: type 16550A Aug 18 16:48:20 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 18 16:48:20 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 18 16:48:20 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 18 16:48:20 news /kernel: ppi0: on ppbus0 Aug 18 16:48:20 news /kernel: lpt0: on ppbus0 Aug 18 16:48:20 news /kernel: lpt0: Interrupt-driven port Aug 18 16:48:20 news /kernel: plip0: on ppbus0 Aug 18 16:48:20 news /kernel: unknown0: at port 0x3e0-0x3e1 on isa0 Aug 18 16:48:20 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 18 16:48:20 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 18 16:48:20 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 18 16:48:20 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 18 16:48:20 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 18 16:48:20 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 18 16:48:20 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 18 16:48:20 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 18 16:48:20 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 18 16:48:20 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 18 16:48:20 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 18 16:48:20 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 18 16:48:20 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 18 16:48:20 news /kernel: vinum: loaded Aug 18 16:48:20 news /kernel: vinum: reading configuration from /dev/da7s1g Aug 18 16:48:20 news /kernel: vinum: updating configuration from /dev/da8s1g Aug 18 16:48:20 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 18 16:48:20 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 18 16:48:20 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 18 16:48:20 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 18 16:48:20 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 18 16:48:21 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 18 16:48:21 news savecore: no core dump Aug 18 16:48:21 news ntpd[169]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 18 16:48:21 news ntpd[169]: using kernel phase-lock loop 2040 Aug 18 16:48:29 news login: ROOT LOGIN (root) ON ttyv0 Aug 18 16:50:34 news login: ROOT LOGIN (root) ON ttyv1 Aug 18 16:52:56 news ntpd[169]: time reset 0.215715 s Aug 18 16:52:56 news ntpd[169]: kernel pll status change 2041 Aug 18 16:55:24 news syslogd: exiting on signal 15 Aug 18 16:59:19 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 18 16:59:19 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 18 16:59:19 news /kernel: The Regents of the University of California. All rights reserved. Aug 18 16:59:19 news /kernel: FreeBSD 4.1-RELEASE #102: Fri Aug 18 12:53:36 EDT 2000 Aug 18 16:59:19 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 18 16:59:19 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 18 16:59:19 news /kernel: Timecounter "TSC" frequency 451025505 Hz Aug 18 16:59:19 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.03-MHz 686-class CPU) Aug 18 16:59:19 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 18 16:59:19 news /kernel: Features=0x383f9ff Aug 18 16:59:19 news /kernel: real memory = 134201344 (131056K bytes) Aug 18 16:59:19 news /kernel: avail memory = 127229952 (124248K bytes) Aug 18 16:59:19 news /kernel: Preloaded elf kernel "kernel" at 0xc0321000. Aug 18 16:59:19 news /kernel: Pentium Pro MTRR support enabled Aug 18 16:59:19 news /kernel: md0: Malloc disk Aug 18 16:59:19 news /kernel: npx0: on motherboard Aug 18 16:59:19 news /kernel: npx0: INT 16 interface Aug 18 16:59:19 news /kernel: pcib0: on motherboard Aug 18 16:59:19 news /kernel: pci0: on pcib0 Aug 18 16:59:19 news /kernel: pcib1: at device 1.0 on pci0 Aug 18 16:59:19 news /kernel: pci1: on pcib1 Aug 18 16:59:19 news /kernel: pci1: at 0.0 irq 11 Aug 18 16:59:19 news /kernel: isab0: at device 4.0 on pci0 Aug 18 16:59:19 news /kernel: isa0: on isab0 Aug 18 16:59:19 news /kernel: atapci0: port 0xd800-0xd80f at device 4.1 on pci0 Aug 18 16:59:19 news /kernel: pci0: at 4.2 irq 12 Aug 18 16:59:19 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 18 16:59:19 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 18 16:59:19 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 16:59:19 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 18 16:59:19 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 18 16:59:19 news /kernel: miibus0: on rl0 Aug 18 16:59:19 news /kernel: rlphy0: on miibus0 Aug 18 16:59:19 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 18 16:59:19 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 18 16:59:19 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 16:59:19 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 18 16:59:19 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 18 16:59:19 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 18 16:59:19 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 18 16:59:19 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 18 16:59:19 news /kernel: sc0: on isa0 Aug 18 16:59:19 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 18 16:59:19 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 18 16:59:19 news /kernel: sio0: type 16550A Aug 18 16:59:19 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 18 16:59:19 news /kernel: sio1: type 16550A Aug 18 16:59:19 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 18 16:59:19 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 18 16:59:19 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 18 16:59:19 news /kernel: ppi0: on ppbus0 Aug 18 16:59:19 news /kernel: lpt0: on ppbus0 Aug 18 16:59:19 news /kernel: lpt0: Interrupt-driven port Aug 18 16:59:19 news /kernel: plip0: on ppbus0 Aug 18 16:59:19 news /kernel: pcic2: at port 0x3e0-0x3e1 on isa0 Aug 18 16:59:19 news /kernel: pcic2: Polling mode Aug 18 16:59:19 news /kernel: pccard0: on pcic2 Aug 18 16:59:19 news /kernel: pccard1: on pcic2 Aug 18 16:59:19 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 18 16:59:19 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 18 16:59:19 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:19 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 18 16:59:19 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:19 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 18 16:59:19 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:19 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 18 16:59:19 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:19 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 18 16:59:19 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:19 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 18 16:59:19 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:19 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 18 16:59:19 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:19 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 18 16:59:19 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:20 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 18 16:59:20 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 18 16:59:20 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 18 16:59:20 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 18 16:59:20 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 18 16:59:20 news /kernel: vinum: loaded Aug 18 16:59:20 news /kernel: vinum: reading configuration from /dev/da8s1g Aug 18 16:59:20 news /kernel: vinum: updating configuration from /dev/da7s1g Aug 18 16:59:20 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 18 16:59:20 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 18 16:59:20 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 18 16:59:20 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 18 16:59:20 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 18 16:59:20 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 18 16:59:20 news savecore: no core dump Aug 18 16:59:20 news ntpd[169]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 18 16:59:20 news ntpd[169]: using kernel phase-lock loop 2040 Aug 18 16:59:29 news login: ROOT LOGIN (root) ON ttyv0 Aug 18 17:01:21 news /kernel: pccard: card inserted, slot 1 Aug 18 13:02:15 news pccardd[282]: No card in database for "(null)"("(null)") Aug 18 13:02:15 news pccardd[282]: pccardd started Aug 18 17:02:30 news /kernel: pccard: card removed, slot 1 Aug 18 17:02:40 news /kernel: pccard: card inserted, slot 1 Aug 18 13:02:46 news pccardd[282]: No card in database for "(null)"("(null)") Aug 18 17:03:36 news /kernel: pccard: card removed, slot 1 Aug 18 17:03:52 news /kernel: pccard: card inserted, slot 0 Aug 18 13:03:57 news pccardd[282]: No card in database for "(null)"("(null)") Aug 18 17:44:33 news sshd[458]: log: ROOT LOGIN as 'root' from trooper.velocet.net Aug 18 17:59:21 news /kernel: pccard: card removed, slot 0 Aug 18 18:03:17 news /kernel: pccard: card inserted, slot 1 Aug 18 14:03:22 news pccardd[282]: No card in database for "(null)"("(null)") Aug 18 18:03:31 news /kernel: pccard: card removed, slot 1 Aug 18 18:06:34 news /kernel: pccard: card inserted, slot 1 Aug 18 14:06:39 news pccardd[282]: No card in database for "(null)"("(null)") Aug 18 18:06:43 news /kernel: pccard: card removed, slot 1 Aug 18 18:18:38 news /kernel: pccard: card inserted, slot 0 Aug 18 14:18:44 news pccardd[282]: No card in database for "(null)"("(null)") Aug 18 14:40:12 news halt: halted by root Aug 18 18:40:12 news syslogd: exiting on signal 15 Aug 18 20:22:37 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 18 20:22:37 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 18 20:22:37 news /kernel: The Regents of the University of California. All rights reserved. Aug 18 20:22:37 news /kernel: FreeBSD 4.1-RELEASE #102: Fri Aug 18 12:53:36 EDT 2000 Aug 18 20:22:37 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 18 20:22:37 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 18 20:22:37 news /kernel: Timecounter "TSC" frequency 451024973 Hz Aug 18 20:22:37 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.02-MHz 686-class CPU) Aug 18 20:22:37 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 18 20:22:37 news /kernel: Features=0x383f9ff Aug 18 20:22:37 news /kernel: real memory = 134201344 (131056K bytes) Aug 18 20:22:37 news /kernel: avail memory = 127229952 (124248K bytes) Aug 18 20:22:37 news /kernel: Preloaded elf kernel "kernel" at 0xc0321000. Aug 18 20:22:37 news /kernel: Pentium Pro MTRR support enabled Aug 18 20:22:37 news /kernel: md0: Malloc disk Aug 18 20:22:37 news /kernel: npx0: on motherboard Aug 18 20:22:37 news /kernel: npx0: INT 16 interface Aug 18 20:22:37 news /kernel: pcib0: on motherboard Aug 18 20:22:37 news /kernel: pci0: on pcib0 Aug 18 20:22:37 news /kernel: pcib1: at device 1.0 on pci0 Aug 18 20:22:37 news /kernel: pci1: on pcib1 Aug 18 20:22:37 news /kernel: pci1: at 0.0 irq 11 Aug 18 20:22:37 news /kernel: isab0: at device 4.0 on pci0 Aug 18 20:22:37 news /kernel: isa0: on isab0 Aug 18 20:22:37 news /kernel: atapci0: port 0xd800-0xd80f at device 4.1 on pci0 Aug 18 20:22:37 news /kernel: pci0: at 4.2 irq 12 Aug 18 20:22:37 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 18 20:22:37 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 18 20:22:37 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 20:22:37 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 18 20:22:37 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 18 20:22:37 news /kernel: miibus0: on rl0 Aug 18 20:22:37 news /kernel: rlphy0: on miibus0 Aug 18 20:22:37 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 18 20:22:37 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 18 20:22:37 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 20:22:37 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 18 20:22:37 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 18 20:22:37 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 18 20:22:37 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 18 20:22:37 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 18 20:22:37 news /kernel: sc0: on isa0 Aug 18 20:22:37 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 18 20:22:37 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 18 20:22:37 news /kernel: sio0: type 16550A Aug 18 20:22:37 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 18 20:22:37 news /kernel: sio1: type 16550A Aug 18 20:22:37 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 18 20:22:37 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 18 20:22:37 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 18 20:22:37 news /kernel: ppi0: on ppbus0 Aug 18 20:22:38 news /kernel: lpt0: on ppbus0 Aug 18 20:22:38 news /kernel: lpt0: Interrupt-driven port Aug 18 20:22:38 news /kernel: plip0: on ppbus0 Aug 18 20:22:38 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 18 20:22:38 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 18 20:22:38 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 18 20:22:38 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 18 20:22:38 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 18 20:22:38 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 18 20:22:38 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 18 20:22:38 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 18 20:22:38 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 18 20:22:38 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 18 20:22:38 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 18 20:22:38 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 18 20:22:38 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 18 20:22:38 news /kernel: vinum: loaded Aug 18 20:22:38 news /kernel: vinum: reading configuration from /dev/da8s1g Aug 18 20:22:38 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 18 20:22:38 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 18 20:22:38 news /kernel: vinum: updating configuration from /dev/da7s1g Aug 18 20:22:38 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 18 20:22:38 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 18 20:22:38 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 18 20:22:38 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 18 20:22:39 news savecore: no core dump Aug 18 20:22:39 news ntpd[236]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 18 20:22:39 news ntpd[236]: using kernel phase-lock loop 2040 Aug 18 22:38:38 news ntpd[236]: time reset -0.142135 s Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0x29 - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0x1d - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0xb0 - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0x92 - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0x57 - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0xbe - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0xc4 - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0x2f - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0xcc - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0xfd - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:39 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:39 news /kernel: (da7:ahc1:0:8:0): SCB 0x23 - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:39 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:39 news /kernel: (da6:ahc1:0:6:0): SCB 0xbf - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:39 news /kernel: (da6:ahc1:0:6:0): BDR message in message buffer Aug 20 02:04:40 news /kernel: (da6:ahc1:0:6:0): SCB 0xd4 - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:40 news /kernel: (da6:ahc1:0:6:0): no longer in timeout, status = 34b Aug 20 02:04:40 news /kernel: ahc1: Issued Channel A Bus Reset. 51 SCBs aborted Aug 20 02:04:45 news /kernel: raid.p0.s5: fatal write I/O error Aug 20 02:04:45 news /kernel: vinum: raid.p0.s5 is stale by force Aug 20 02:04:45 news /kernel: vinum: raid.p0 is degraded Aug 20 02:04:45 news /kernel: raid.p0.s5: fatal write I/O error Aug 20 02:04:45 news last message repeated 9 times Aug 20 02:04:45 news /kernel: raid.p0.s6: fatal write I/O error Aug 20 02:04:46 news /kernel: vinum: raid.p0.s6 is stale by force Aug 20 02:04:46 news /kernel: vinum: raid.p0 is corrupt Aug 20 02:04:46 news /kernel: raid.p0.s5: fatal write I/O error Aug 20 02:04:46 news last message repeated 3 times Aug 22 06:38:02 news dhclient: New IP Address(rl0): 204.138.45.35 Aug 22 06:38:02 news dhclient: New Subnet Mask (rl0): 255.255.255.192 Aug 22 06:38:02 news dhclient: New Broadcast Address(rl0): 204.138.45.0 Aug 22 06:38:02 news dhclient: New Routers: 204.138.45.2 Aug 22 15:05:40 news login: ROOT LOGIN (root) ON ttyv0 Aug 22 15:05:50 news /kernel: pid 17260 (bash), uid 0: exited on signal 3 (core dumped) Aug 22 15:05:59 news syslogd: exiting on signal 15 Aug 22 15:10:15 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 22 15:10:15 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 22 15:10:15 news /kernel: The Regents of the University of California. All rights reserved. Aug 22 15:10:15 news /kernel: FreeBSD 4.1-RELEASE #102: Fri Aug 18 12:53:36 EDT 2000 Aug 22 15:10:15 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 22 15:10:15 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 22 15:10:16 news /kernel: Timecounter "TSC" frequency 451025076 Hz Aug 22 15:10:16 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.03-MHz 686-class CPU) Aug 22 15:10:16 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 22 15:10:16 news /kernel: Features=0x383f9ff Aug 22 15:10:16 news /kernel: real memory = 134201344 (131056K bytes) Aug 22 15:10:16 news /kernel: avail memory = 127229952 (124248K bytes) Aug 22 15:10:16 news /kernel: Preloaded elf kernel "kernel" at 0xc0321000. Aug 22 15:10:16 news /kernel: Pentium Pro MTRR support enabled Aug 22 15:10:16 news /kernel: md0: Malloc disk Aug 22 15:10:16 news /kernel: npx0: on motherboard Aug 22 15:10:16 news /kernel: npx0: INT 16 interface Aug 22 15:10:16 news /kernel: pcib0: on motherboard Aug 22 15:10:16 news /kernel: pci0: on pcib0 Aug 22 15:10:16 news /kernel: pcib1: at device 1.0 on pci0 Aug 22 15:10:16 news /kernel: pci1: on pcib1 Aug 22 15:10:16 news /kernel: pci1: at 0.0 irq 11 Aug 22 15:10:16 news /kernel: isab0: at device 4.0 on pci0 Aug 22 15:10:16 news /kernel: isa0: on isab0 Aug 22 15:10:16 news /kernel: atapci0: port 0xd800-0xd80f at device 4.1 on pci0 Aug 22 15:10:16 news /kernel: pci0: at 4.2 irq 12 Aug 22 15:10:16 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 22 15:10:16 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 22 15:10:16 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 22 15:10:16 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 22 15:10:16 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 22 15:10:16 news /kernel: miibus0: on rl0 Aug 22 15:10:16 news /kernel: rlphy0: on miibus0 Aug 22 15:10:16 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 22 15:10:16 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 22 15:10:16 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 22 15:10:16 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 22 15:10:16 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 22 15:10:16 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 22 15:10:16 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 22 15:10:16 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 22 15:10:16 news /kernel: sc0: on isa0 Aug 22 15:10:16 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 22 15:10:16 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 22 15:10:16 news /kernel: sio0: type 16550A Aug 22 15:10:16 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 22 15:10:16 news /kernel: sio1: type 16550A Aug 22 15:10:16 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 22 15:10:16 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 22 15:10:16 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 22 15:10:16 news /kernel: ppi0: on ppbus0 Aug 22 15:10:16 news /kernel: lpt0: on ppbus0 Aug 22 15:10:16 news /kernel: lpt0: Interrupt-driven port Aug 22 15:10:16 news /kernel: plip0: on ppbus0 Aug 22 15:10:16 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 22 15:10:16 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 22 15:10:16 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 22 15:10:16 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:16 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:16 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 22 15:10:16 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 22 15:10:16 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:16 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:16 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 22 15:10:16 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 22 15:10:16 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:16 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:16 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 22 15:10:16 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 22 15:10:16 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:17 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:17 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 22 15:10:17 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 22 15:10:17 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:17 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:17 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 22 15:10:17 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 22 15:10:17 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:17 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:17 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 22 15:10:17 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 22 15:10:17 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:17 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:17 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 22 15:10:17 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 22 15:10:17 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:17 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:17 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 22 15:10:17 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 22 15:10:17 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 22 15:10:17 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 22 15:10:17 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 22 15:10:17 news /kernel: vinum: loaded Aug 22 15:10:17 news /kernel: vinum: reading configuration from /dev/da7s1g Aug 22 15:10:17 news /kernel: vinum: updating configuration from /dev/da8s1g Aug 22 15:10:17 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 22 15:10:17 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 22 15:10:17 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 22 15:10:17 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 22 15:10:17 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 22 15:10:17 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 22 15:10:17 news savecore: no core dump Aug 22 15:10:11 news ntpd[169]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 22 15:10:11 news ntpd[169]: using kernel phase-lock loop 2040 Aug 22 15:16:41 news login: ROOT LOGIN (root) ON ttyv0 Aug 22 15:17:34 news login: ROOT LOGIN (root) ON ttyv1 Aug 22 17:51:43 news ntpd[169]: time reset -0.131985 s Aug 24 02:03:37 news /kernel: Data modified on freelist: word 0 of object 0xc269d000 size 4096 previous type devbuf (0x0 != 0xdeadc0de) Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x4a - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x2a - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x17 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x16 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x37 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0xe - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0xf - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x33 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x58 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x64 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x85 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x7f - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x3b - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x8b - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0xde - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0xd3 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0xd2 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0xb - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x24 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x44 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0xec - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x7a - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0xe3 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x9d - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x5f - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x97 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da8:ahc1:0:9:0): SCB 0xe0 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da8:ahc1:0:9:0): BDR message in message buffer Aug 24 02:04:39 news /kernel: (da8:ahc1:0:9:0): SCB 0xea - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:39 news /kernel: (da8:ahc1:0:9:0): no longer in timeout, status = 34b Aug 24 02:04:39 news /kernel: ahc1: Issued Channel A Bus Reset. 174 SCBs aborted Aug 24 02:04:44 news /kernel: raid.p0.s4: fatal write I/O error Aug 24 02:04:44 news /kernel: vinum: raid.p0.s4 is stale by force Aug 24 02:04:44 news /kernel: vinum: raid.p0 is degraded Aug 24 02:04:44 news /kernel: raid.p0.s5: fatal read I/O error Aug 24 02:04:44 news /kernel: vinum: raid.p0.s5 is crashed by force Aug 24 02:04:44 news /kernel: vinum: raid.p0 is corrupt Aug 24 02:04:44 news /kernel: raid.p0.s4: fatal write I/O error Aug 24 02:04:44 news /kernel: raid.p0.s5: fatal read I/O error Aug 24 02:04:44 news /kernel: raid.p0.s4: fatal write I/O error Aug 24 02:04:44 news /kernel: raid.p0.s6: fatal write I/O error Aug 24 02:04:44 news /kernel: vinum: raid.p0.s6 is stale by force Aug 24 02:04:44 news /kernel: raid.p0.s4: fatal write I/O error Aug 24 02:04:44 news last message repeated 2 times Aug 24 02:04:44 news /kernel: raid.p0.s5: fatal read I/O error Aug 24 02:04:44 news /kernel: raid.p0.s5: fatal read I/O error Aug 24 02:05:13 news /kernel: vinum: raid.p0.s5 is stale by force Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x8f - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x41 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x48 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0xc2 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x3d - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x13 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x25 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x9b - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x46 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0xbc - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x40 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x51 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x42 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x3c - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x27 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0xab - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x80 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x9d - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0xe3 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0xd2 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0xde - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x8b - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0x79 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0x49 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0x28 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0xc - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0x19 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0xd6 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0x45 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0xc3 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xbe - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xd5 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x6a - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x68 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x2d - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x82 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x9e - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x1c - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xb5 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xee - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x2b - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xdc - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x39 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x32 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xea - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x4 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x15 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xe1 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x94 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x56 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xdb - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x1a - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xc0 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xc5 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x9 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xbd - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x2f - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xe9 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xb7 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x86 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x9f - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x77 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x71 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xa1 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x96 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:46 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:46 news /kernel: (da8:ahc1:0:9:0): SCB 0x2 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:46 news /kernel: (da8:ahc1:0:9:0): BDR message in message buffer Aug 24 02:05:46 news /kernel: (da8:ahc1:0:9:0): SCB 0xe4 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:46 news /kernel: (da8:ahc1:0:9:0): no longer in timeout, status = 34b Aug 24 02:05:46 news /kernel: ahc1: Issued Channel A Bus Reset. 113 SCBs aborted Aug 24 02:05:51 news /kernel: raid.p0.s5: fatal write I/O error Aug 24 02:05:51 news last message repeated 14 times Aug 24 02:05:51 news /kernel: raid.p0.s6: fatal read I/O error Aug 24 02:05:51 news /kernel: vinum: raid.p0.s6 is crashed by force Aug 24 02:05:51 news /kernel: raid.p0.s5: fatal write I/O error Aug 24 02:05:51 news /kernel: raid.p0.s6: fatal write I/O error Aug 24 02:05:51 news /kernel: vinum: raid.p0.s6 is stale by force Aug 24 02:05:51 news /kernel: raid.p0.s7: fatal write I/O error Aug 24 02:05:51 news /kernel: vinum: raid.p0.s7 is stale by force Aug 24 02:05:51 news /kernel: raid.p0.s5: fatal write I/O error Aug 24 02:05:51 news last message repeated 2 times Aug 24 02:05:51 news /kernel: raid.p0.s6: fatal read I/O error Aug 24 02:05:51 news /kernel: vinum: raid.p0.s6 is crashed by force Aug 24 02:05:51 news /kernel: raid.p0.s6: fatal write I/O error Aug 24 02:05:51 news /kernel: vinum: raid.p0.s6 is stale by force Aug 24 02:05:51 news /kernel: raid.p0.s6: fatal write I/O error Aug 24 09:04:31 news reboot: rebooted by root Aug 24 13:04:31 news syslogd: exiting on signal 15 Aug 24 13:08:48 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 24 13:08:48 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 24 13:08:48 news /kernel: The Regents of the University of California. All rights reserved. Aug 24 13:08:48 news /kernel: FreeBSD 4.1-RELEASE #102: Fri Aug 18 12:53:36 EDT 2000 Aug 24 13:08:48 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 24 13:08:48 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 24 13:08:48 news /kernel: Timecounter "TSC" frequency 451024938 Hz Aug 24 13:08:48 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.02-MHz 686-class CPU) Aug 24 13:08:48 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 24 13:08:48 news /kernel: Features=0x383f9ff Aug 24 13:08:48 news /kernel: real memory = 134201344 (131056K bytes) Aug 24 13:08:48 news /kernel: avail memory = 127229952 (124248K bytes) Aug 24 13:08:48 news /kernel: Preloaded elf kernel "kernel" at 0xc0321000. Aug 24 13:08:48 news /kernel: Pentium Pro MTRR support enabled Aug 24 13:08:48 news /kernel: md0: Malloc disk Aug 24 13:08:48 news /kernel: npx0: on motherboard Aug 24 13:08:48 news /kernel: npx0: INT 16 interface Aug 24 13:08:48 news /kernel: pcib0: on motherboard Aug 24 13:08:48 news /kernel: pci0: on pcib0 Aug 24 13:08:48 news /kernel: pcib1: at device 1.0 on pci0 Aug 24 13:08:48 news /kernel: pci1: on pcib1 Aug 24 13:08:48 news /kernel: pci1: at 0.0 irq 11 Aug 24 13:08:48 news /kernel: isab0: at device 4.0 on pci0 Aug 24 13:08:48 news /kernel: isa0: on isab0 Aug 24 13:08:48 news /kernel: atapci0: port 0xd800-0xd80f at device 4.1 on pci0 Aug 24 13:08:48 news /kernel: pci0: at 4.2 irq 12 Aug 24 13:08:48 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 24 13:08:48 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 24 13:08:48 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 24 13:08:48 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 24 13:08:48 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 24 13:08:48 news /kernel: miibus0: on rl0 Aug 24 13:08:48 news /kernel: rlphy0: on miibus0 Aug 24 13:08:48 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 24 13:08:48 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 24 13:08:48 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 24 13:08:48 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 24 13:08:48 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 24 13:08:48 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 24 13:08:48 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 24 13:08:48 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 24 13:08:48 news /kernel: sc0: on isa0 Aug 24 13:08:48 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 24 13:08:48 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 24 13:08:48 news /kernel: sio0: type 16550A Aug 24 13:08:48 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 24 13:08:48 news /kernel: sio1: type 16550A Aug 24 13:08:48 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 24 13:08:48 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 24 13:08:48 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 24 13:08:48 news /kernel: ppi0: on ppbus0 Aug 24 13:08:48 news /kernel: lpt0: on ppbus0 Aug 24 13:08:48 news /kernel: lpt0: Interrupt-driven port Aug 24 13:08:48 news /kernel: plip0: on ppbus0 Aug 24 13:08:48 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 24 13:08:48 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 24 13:08:48 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 24 13:08:48 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 24 13:08:48 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 24 13:08:48 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 24 13:08:48 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 24 13:08:48 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 24 13:08:48 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 24 13:08:48 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 24 13:08:48 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 24 13:08:48 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 24 13:08:48 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 24 13:08:48 news /kernel: vinum: loaded Aug 24 13:08:48 news /kernel: vinum: reading configuration from /dev/da8s1g Aug 24 13:08:48 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 24 13:08:48 news /kernel: vinum: updating configuration from /dev/da7s1g Aug 24 13:08:48 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 24 13:08:48 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 24 13:08:48 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 24 13:08:48 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 24 13:08:48 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 24 13:08:49 news savecore: no core dump Aug 24 13:08:47 news ntpd[169]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 24 13:08:47 news ntpd[169]: using kernel phase-lock loop 2040 --BzGFJYjy6O Content-Type: text/plain; charset=us-ascii Content-Description: message body and .signature Content-Transfer-Encoding: 7bit Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ --BzGFJYjy6O-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 24 10:52:46 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id C28D937B424 for ; Thu, 24 Aug 2000 10:52:43 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id 6E8202B23A; Thu, 24 Aug 2000 12:52:38 -0500 (CDT) Date: Thu, 24 Aug 2000 10:52:38 -0700 From: Paul Saab To: Chuck Robey Cc: "Barrett G. Lyon" , freebsd-scsi@FreeBSD.ORG, George Morgan Subject: Re: Adaptec 3960D Ultra160 issues Message-ID: <20000824105238.A422@elvis.mu.org> References: <20000823224924.A90931@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from chuckr@picnic.chuckr.org on Thu, Aug 24, 2000 at 08:41:24AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chuck Robey (chuckr@picnic.chuckr.org) wrote: > Paul, George Morgan and I (see I added him to the CC:, he's not > subscribed) are both seeing problems with inability to boot IBM Ultra 160 > drives (he on a Adaptec 39160, me on a 29160). Can you tell me where you > saw the stuff on this problem, so I can read up on it and see if there's > some sort of fix for us? I dont know anything about not being able to boot U160 IBM drives. We use seagate drives at work and they boot just fine. We had stability issues with the drives and I asked around and found that disabling WCE on the drive is a work around for the problem. -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 24 11:12:27 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from theshell.com (arsenic.theshell.com [63.236.138.5]) by hub.freebsd.org (Postfix) with SMTP id 644E037B423 for ; Thu, 24 Aug 2000 11:12:25 -0700 (PDT) Received: (qmail 1967 invoked by uid 500); 24 Aug 2000 18:12:42 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 24 Aug 2000 18:12:42 -0000 Date: Thu, 24 Aug 2000 11:12:42 -0700 (PDT) From: "Barrett G. Lyon" To: Paul Saab Cc: Chuck Robey , freebsd-scsi@FreeBSD.ORG, George Morgan Subject: Re: Adaptec 3960D Ultra160 issues In-Reply-To: <20000824105238.A422@elvis.mu.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 Chuck Robey (chuckr@picnic.chuckr.org) wrote: > Paul, George Morgan and I (see I added him to the CC:, he's not > subscribed) are both seeing problems with inability to boot IBM Ultra 160 > drives (he on a Adaptec 39160, me on a 29160). Can you tell me where you > saw the stuff on this problem, so I can read up on it and see if there's > some sort of fix for us? As an added note, I can boot just fine with IBM U160 disks on the Adaptec 39160. I just had crashing problems and it only runs at 40 MHz. -Barrett Barrett G. Lyon http://www.theshell.com http://www.alphalinux.org A corporation is like a tree of monkeys, all the monkeys on top looking down see smiling faces, while all the monkeys looking up see assholes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 24 12: 6:47 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from theshell.com (arsenic.theshell.com [63.236.138.5]) by hub.freebsd.org (Postfix) with SMTP id 11D6937B42C for ; Thu, 24 Aug 2000 12:06:44 -0700 (PDT) Received: (qmail 9798 invoked by uid 500); 24 Aug 2000 19:07:01 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 24 Aug 2000 19:07:01 -0000 Date: Thu, 24 Aug 2000 12:07:01 -0700 (PDT) From: "Barrett G. Lyon" To: freebsd-scsi@freebsd.org Cc: gibbs@FreeBSD.org Subject: Re: Adaptec 3960D Ultra160 In-Reply-To: <200008241529.JAA80172@pluto.plutotech.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 Well now the system is crashing with a different error: Aug 24 12:01:03 63.236.138.8 /kernel: (da0:ahc1:0:6:0): SCB 0x3f - timed out while idle, SEQADDR == 0xb I'm not sure what would cause that, however this is really getting bad. This machine is a production machine and it can't stay up longer than a day. I need some advice. (FreeBSD 4.1-Stable, Ultra160 IBM, Adaptec 39160) -Barrett Barrett G. Lyon http://www.theshell.com http://www.alphalinux.org A corporation is like a tree of monkeys, all the monkeys on top looking down see smiling faces, while all the monkeys looking up see assholes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 24 19: 7: 6 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 6796337B422 for ; Thu, 24 Aug 2000 19:07:01 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id LAA47231; Fri, 25 Aug 2000 11:36:38 +0930 (CST) (envelope-from grog) Date: Fri, 25 Aug 2000 11:36:38 +0930 From: Greg Lehey To: David Gilbert Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Vinum 29160 detaches drives, invalidates RAID. Message-ID: <20000825113638.D39208@wantadilla.lemis.com> References: <14757.14569.732766.367692@trooper.velocet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <14757.14569.732766.367692@trooper.velocet.net>; from dgilbert@velocet.ca on Thu, Aug 24, 2000 at 11:02:01AM -0400 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [dropping -stable] On Thursday, 24 August 2000 at 11:02:01 -0400, David Gilbert wrote: Content-Description: message body text > I have a vinum test box with 8x driven > by 2x running 4.1-RELEASE. The > machine also has a 9G root SCSI drive that is on a non-LVD connector > of the 29160 card. I'll include all the probe messages 'n such at the > end, but I want to get to the description first. > > The 18G drives are all VINUM. It results in > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/vinum/raid 121691956 14986173 96970427 13% /raid > > I have loaded the drive with a copy of the FreeBSD cvs tree (that I > cvsup) and a checked-out copy of the tree. I believe there is also a > copy of the results of a make-release and other misc garbage. > > The drives are cabled 4 per controller with a certified LVD cable that > ends with a certified LVD terminator. The root drive has a regular > SCSI-2 cable and also an SE/LVD terminator. The 8 drives are in a > separate case with redundant (and definately adequate) power. The > root drive is on the main case's power. > > The whole thing is running on a PIII/450 with either 128M or 256M of > RAM (depending on what I'm testing). > > ... so we know what the hardware is. I've been careful to cable and > do this all properly. > > First of all, I'm very pleased with the speed. The system easily > beats the AMI MegaRAID 1500 (same drives) with a whopping 35Mbyte/s in > RAID-5 (vs. the 1500's 14Mbyte/s) for read. (They both score a dead > heat of 4Mbyte/s write.) Nice to hear :-) > I have had no troubles with cvsup'ing and no troubles with multiple > concurrent cvs checkouts. I have a script that tells me that the 8 > drives are dispatching from 500 to 1000 transactions a second (summing > up all the iostat figures) and "cvs update" on the FreeBSD src > directory can get a combined r/w performance of about 5Mbyte/s on the > array. > > However, the nightly find scripts almost always disable the array. > Many, many messages of the form > > Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x4a - timed out in Data-out phase, SEQADDR == 0x5c > Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout This is almost certainly a SCSI problem. I'll leave the SCSI experts to decipher it, though I'd suspect a bus problem, despite your attempts to avoid them. > resulting in > > Aug 24 02:04:44 news /kernel: raid.p0.s4: fatal write I/O error > Aug 24 02:04:44 news /kernel: vinum: raid.p0.s4 is stale by force > Aug 24 02:04:44 news /kernel: vinum: raid.p0 is degraded > > and then (as other disks do the same) Yes, there's little else I can do there. > Now... if I reboot, and "vinum setstate up" all these drives, They all go down, do they? > fsck completes without any complaint. I then generally have to > "vinum rebuild parity" ... but I suppose that I'd expect that. Hmm. rebuildparity is a dangerous command. Basically, a parity error means that *one* (or more) of the drives has incorrect data. rebuildparity simply assumes that the error is in the data block and "corrects" it. It's a serious problem, one that is very difficult to solve. > The problem I'm having here (and I've had it before) is that the > FreeBSD SCSI system seems to "give up" under conditions that others > would keep retrying or resetting/retrying. > > It seems really, really, really important to me that we try harder to > get a drive back online. This seems as if it could affect the > long-term viability of a vinum-based raid server... not because vinum > is bad, but because the SCSI subsystem is too fragile. Hmm. I can't really comment on that, but it would be nice if the SCSI system could recover from these problems. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 24 21: 5:23 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from theshell.com (arsenic.theshell.com [63.236.138.5]) by hub.freebsd.org (Postfix) with SMTP id E858137B423 for ; Thu, 24 Aug 2000 21:05:20 -0700 (PDT) Received: (qmail 6339 invoked from network); 25 Aug 2000 04:05:34 -0000 Received: from arsenic.theshell.com (HELO tequila) (root@63.236.138.5) by arsenic.theshell.com with SMTP; 25 Aug 2000 04:05:34 -0000 From: "Peter Avalos" To: Subject: Re: Adaptec 3960D Ultra160 Date: Thu, 24 Aug 2000 23:06:43 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Barrett Lyon wrote: Well now the system is crashing with a different error: Aug 24 12:01:03 63.236.138.8 /kernel: (da0:ahc1:0:6:0): SCB 0x3f - timed out while idle, SEQADDR == 0xb I'm not sure what would cause that, however this is really getting bad. This machine is a production machine and it can't stay up longer than a day. I need some advice. (FreeBSD 4.1-Stable, Ultra160 IBM, Adaptec 39160) ------------------ I figured that I'd paste the latest syslog messages of the most recent crash: (sorry for the length, but I want to be thorough) Aug 24 20:07:08 63.236.138.8 /kernel: (da0:ahc1:0:6:0): Invalidating pack Aug 24 20:07:30 63.236.138.8 last message repeated 7 times Aug 24 20:07:33 63.236.138.8 /kernel: spec_getpages:(#da/0x20005) I/O read failure: (error=6) bp 0xcef1bbb0 vp 0xdc77a780 Aug 24 20:07:33 63.236.138.8 /kernel: size: 4096, resid: 4096, a_count: 4096, valid: 0x0 Aug 24 20:07:33 63.236.138.8 /kernel: nread: 0, reqpage: 0, pindex: 15, pcount: 1 Aug 24 20:07:33 63.236.138.8 /kernel: vm_fault: pager read error, pid 1363 (eggdrop) Aug 24 20:07:33 63.236.138.8 /kernel: pid 1363 (eggdrop), uid 538: exited on signal 11 Aug 24 20:07:34 63.236.138.8 /kernel: (da0:ahc1:0:6:0): Invalidating pack Aug 24 20:07:47 63.236.138.8 last message repeated 4 times Aug 24 20:07:47 63.236.138.8 /kernel: spec_getpages:(#da/0x20005) I/O read failure: (error=6) bp 0xcef1bbb0 vp 0xdc77a780 Aug 24 20:07:47 63.236.138.8 /kernel: size: 4096, resid: 4096, a_count: 4096, valid: 0x0 Aug 24 20:07:47 63.236.138.8 /kernel: nread: 0, reqpage: 0, pindex: 15, pcount: 1 Aug 24 20:07:47 63.236.138.8 /kernel: vm_fault: pager read error, pid 1365 (eggdrop) Aug 24 20:07:47 63.236.138.8 /kernel: pid 1365 (eggdrop), uid 538: exited on signal 11 Aug 24 20:07:50 63.236.138.8 /kernel: (da0:ahc1:0:6:0): Invalidating pack Aug 24 20:07:54 63.236.138.8 last message repeated 1 times Aug 24 20:07:54 63.236.138.8 /kernel: spec_getpages:(#da/0x20005) I/O read failure: (error=6) bp 0xcef1bbb0 vp 0xdc77a780 Aug 24 20:07:54 63.236.138.8 /kernel: size: 4096, resid: 4096, a_count: 4096, valid: 0x0 Aug 24 20:07:54 63.236.138.8 /kernel: nread: 0, reqpage: 0, pindex: 15, pcount: 1 Aug 24 20:07:54 63.236.138.8 /kernel: vm_fault: pager read error, pid 1364 (eggdrop) Aug 24 20:07:54 63.236.138.8 /kernel: pid 1364 (eggdrop), uid 538: exited on signal 11 Aug 24 20:07:56 63.236.138.8 /kernel: (da0:ahc1:0:6:0): Invalidating pack Aug 24 20:08:00 63.236.138.8 /kernel: (da0:ahc1:0:6:0): Invalidating pack Aug 24 20:08:00 63.236.138.8 CRON[86449]: (root) CMD (/usr/local/scripts/bnckiller >/dev/null 2>&1) Aug 24 20:08:00 63.236.138.8 CRON[86450]: (soniq) CMD (/usr/home/tsh/soniq/europa/botchk >/dev/null 2>&1) Aug 24 20:08:00 63.236.138.8 CRON[86451]: (popper) CMD (/usr/home/tsh/popper/eggdrop/popchk > /dev/null 2>1&^M) Aug 24 20:08:00 63.236.138.8 CRON[86452]: (popper) CMD (/usr/home/tsh/popper/.786/botchk > /dev/null 2>1&^M) Aug 24 20:08:03 63.236.138.8 /kernel: (da0:ahc1:0:6:0): Invalidating pack Aug 24 20:08:19 63.236.138.8 last message repeated 5 times Aug 24 20:08:30 63.236.138.8 /kernel: spec_getpages:(#da/0x20005) I/O read failure: (error=6) bp 0xcef1bbb0 vp 0xdc77a780 Aug 24 20:08:30 63.236.138.8 /kernel: size: 4096, resid: 4096, a_count: 4096, valid: 0x0 Aug 24 20:08:30 63.236.138.8 /kernel: nread: 0, reqpage: 0, pindex: 15, pcount: 1 Aug 24 20:08:30 63.236.138.8 /kernel: vm_fault: pager read error, pid 1360 (eggdrop) Aug 24 20:08:30 63.236.138.8 /kernel: pid 1360 (eggdrop), uid 538: exited on signal 11 Peter Avalos www.theshell.com -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS/ED/B d-(+) s:+> a-- C++$ UBLO++++$ P+ L++++ E- W+ N+ o? K? w(++) !O M- V- PS+ PE++ Y+ PGP++ t+@ 5 X- R- tv+ b++ DI- D-- G e>+++ h-- r++ y++ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 24 22:47:12 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from cs4.cs.ait.ac.th (cs4.cs.ait.ac.th [192.41.170.15]) by hub.freebsd.org (Postfix) with ESMTP id 0C28D37B422 for ; Thu, 24 Aug 2000 22:47:09 -0700 (PDT) Received: from banyan.cs.ait.ac.th (on@banyan.cs.ait.ac.th [192.41.170.5]) by cs4.cs.ait.ac.th (8.9.3/8.9.3) with ESMTP id MAA24450 for ; Fri, 25 Aug 2000 12:47:02 +0700 (GMT+0700) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.8.5/8.8.5) id MAA06984; Fri, 25 Aug 2000 12:47:00 +0700 (ICT) Date: Fri, 25 Aug 2000 12:47:00 +0700 (ICT) Message-Id: <200008250547.MAA06984@banyan.cs.ait.ac.th> X-Authentication-Warning: banyan.cs.ait.ac.th: on set sender to on@banyan.cs.ait.ac.th using -f From: Olivier Nicole To: freebsd-scsi@freebsd.org Subject: Tandberg SLR 100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I plan to build a back-up server build around a Tandberg SLR 100 (and maybe an autoloader) with Amanda. I would like to know if SLR 100 is supported in FreeBSD, and if so, in what version of FreeBSD. Any help or pointer would be warmly welcome, Thakns olivier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 24 22:53: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 4E15A37B423 for ; Thu, 24 Aug 2000 22:53:41 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA11207; Thu, 24 Aug 2000 22:53:32 -0700 Date: Thu, 24 Aug 2000 22:50:07 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Olivier Nicole Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Tandberg SLR 100 In-Reply-To: <200008250547.MAA06984@banyan.cs.ait.ac.th> 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 Is this SLR a QIC device? Typically, QIC type tapes are problematic. I bought an SLR-5 to test with FreeBSD last year- that seems to work. The current quirk table entry should match correctly for it. The QIC issues usually are: need 1 filemark only (quirks can handle this, also doing a 'mt seteotmodel'- see mt(1)- can make this explicit), usually need to be in fixed block mode (at 1024 byte blocks). So- the answer is "I haven't tried it. Should work." Hopefully one of the folks who use QICs more than I do can chime in. I'd recommend at least 4.0. > Hello, > > I plan to build a back-up server build around a Tandberg SLR 100 (and > maybe an autoloader) with Amanda. > > I would like to know if SLR 100 is supported in FreeBSD, and if so, in > what version of FreeBSD. > > Any help or pointer would be warmly welcome, > > Thakns > > olivier > > > 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 Thu Aug 24 22:59:58 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from cs4.cs.ait.ac.th (cs4.cs.ait.ac.th [192.41.170.15]) by hub.freebsd.org (Postfix) with ESMTP id 4823A37B423 for ; Thu, 24 Aug 2000 22:59:54 -0700 (PDT) Received: from banyan.cs.ait.ac.th (on@banyan.cs.ait.ac.th [192.41.170.5]) by cs4.cs.ait.ac.th (8.9.3/8.9.3) with ESMTP id MAA24528 for ; Fri, 25 Aug 2000 12:59:51 +0700 (GMT+0700) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.8.5/8.8.5) id MAA07000; Fri, 25 Aug 2000 12:59:50 +0700 (ICT) Date: Fri, 25 Aug 2000 12:59:50 +0700 (ICT) Message-Id: <200008250559.MAA07000@banyan.cs.ait.ac.th> X-Authentication-Warning: banyan.cs.ait.ac.th: on set sender to on@banyan.cs.ait.ac.th using -f From: Olivier Nicole To: freebsd-scsi@FreeBSD.ORG In-reply-to: (message from Matthew Jacob on Thu, 24 Aug 2000 22:50:07 -0700 (PDT)) Subject: Re: Tandberg SLR 100 References: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Is this SLR a QIC device? Yes it is, well, it is a quater inch cartridge, but it is not a QIC standard yet (?) >Typically, QIC type tapes are problematic. I bought an SLR-5 to test with >FreeBSD last year- that seems to work. The current quirk table entry should >match correctly for it. Any idea where/what is this table for FreeBSD 3.5? >The QIC issues usually are: need 1 filemark only (quirks can handle this, also >doing a 'mt seteotmodel'- see mt(1)- can make this explicit), usually need to >be in fixed block mode (at 1024 byte blocks). I have seen that discussion. >So- the answer is "I haven't tried it. Should work." Hopefully one of the >folks who use QICs more than I do can chime in. I'd recommend at least 4.0. Any one that can tell me it works (given this and that configuration) or it definitely does not work? I could go for DLT, but I like QIC like technology better :) Olivier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 25 0:45:49 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 0331837B423 for ; Fri, 25 Aug 2000 00:45:47 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA11405; Fri, 25 Aug 2000 00:45:39 -0700 Date: Fri, 25 Aug 2000 00:45:40 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Olivier Nicole Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Tandberg SLR 100 In-Reply-To: <200008250559.MAA07000@banyan.cs.ait.ac.th> 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 Fri, 25 Aug 2000, Olivier Nicole wrote: > >Is this SLR a QIC device? > > Yes it is, well, it is a quater inch cartridge, but it is not a QIC > standard yet (?) > > >Typically, QIC type tapes are problematic. I bought an SLR-5 to test with > >FreeBSD last year- that seems to work. The current quirk table entry should > >match correctly for it. > > Any idea where/what is this table for FreeBSD 3.5? Same table. EOT model stuff is not there- that was a 4.0 introduction. > > >The QIC issues usually are: need 1 filemark only (quirks can handle this, also > >doing a 'mt seteotmodel'- see mt(1)- can make this explicit), usually need to > >be in fixed block mode (at 1024 byte blocks). > > I have seen that discussion. > > >So- the answer is "I haven't tried it. Should work." Hopefully one of the > >folks who use QICs more than I do can chime in. I'd recommend at least 4.0. > > Any one that can tell me it works (given this and that configuration) > or it definitely does not work? > > I could go for DLT, but I like QIC like technology better :) I'll have to admit I'm getting further and further behind the curve on what's current. I don't work for a company that buys tape toys for me. There are a lot of issues for tapes that are forever, but what's actually working well this year is something I can only find out about if spend my own money. This year, I bought a SCSI analyzer instead (Ancot Ultra3. 5k$USD! Rah! Rah!). -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 25 0:51:51 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mailgate.siemens.ch (mailgate.siemens.ch [195.48.203.142]) by hub.freebsd.org (Postfix) with ESMTP id 067D837B42C for ; Fri, 25 Aug 2000 00:51:49 -0700 (PDT) Received: from eugateext.siemens.ch (eugate.siemens.ch [195.48.203.130]) by mailgate.siemens.ch (8.8.8/8.8.8) with SMTP id JAA08979 for ; Fri, 25 Aug 2000 09:51:47 +0200 (MET DST) Received: from mail2.siemens.ch by eugateext.siemens.ch via smtpd (for mailgate.siemens.ch [195.48.203.142]) with SMTP; 25 Aug 2000 07:51:46 UT Received: from ray.ren.es1.siemens.ch (ray.ren.es1.siemens.ch [139.16.185.140]) by zrha221a (Build 101 8.9.3/NT-8.9.3) with ESMTP id JAA00151 for ; Fri, 25 Aug 2000 09:51:06 +0200 Received: from ren.es1.siemens.ch (bee.ren.es1.siemens.ch) by ray.ren.es1.siemens.ch (Sun Internet Mail Server sims.3.5.1999.07.30.00.05.p8) with ESMTP id <0FZU004028I5MK@ray.ren.es1.siemens.ch> for freebsd-scsi@FreeBSD.ORG; Fri, 25 Aug 2000 09:51:41 +0200 (MET DST) Date: Fri, 25 Aug 2000 09:51:33 +0200 From: Fabbri Pascal Subject: Faltal trap 12: page fault while in kernel mode To: freebsd-scsi@FreeBSD.ORG Message-id: <39A62585.6A4B8723@ren.es1.siemens.ch> MIME-version: 1.0 X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.7 sun4u) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When I boot FreeBSD 4.1, the kernel trap with this message: sym0: <895a> port 0x2800-0x28ff mem 0xf4900000-0xf4901fff, ..... irq 9 at device 11.0 on pci2 sym0: failed to allocate RAM resources Faltal trap 12: page fault while in kernel mode This with a SCSI Host adapter SYMBIOS 53c895a. Can You please help me ? Thanks in advance, fabbri... pascal.fabbri@ren.es1.siemens.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 25 3:50: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front6.grolier.fr (front6.grolier.fr [194.158.96.56]) by hub.freebsd.org (Postfix) with ESMTP id 6286637B42C for ; Fri, 25 Aug 2000 03:49:55 -0700 (PDT) Received: from nas26-79.vlt.club-internet.fr (nas26-79.vlt.club-internet.fr [195.36.223.79]) by front6.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id MAA24549; Fri, 25 Aug 2000 12:49:48 +0200 (MET DST) Date: Fri, 25 Aug 2000 12:31:35 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Fabbri Pascal Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Faltal trap 12: page fault while in kernel mode In-Reply-To: <39A62585.6A4B8723@ren.es1.siemens.ch> 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 Fri, 25 Aug 2000, Fabbri Pascal wrote: > When I boot FreeBSD 4.1, the kernel trap with this message: >=20 > sym0: <895a> port 0x2800-0x28ff mem 0xf4900000-0xf4901fff, ..... Could you report the entire line, please ? Given the message above, the driver is seeing a bogus PCI BARs=20 configuration: - The MMIO region is reported as a 0x2000=3D8Kb window that should in=20 fact be 256 bytes. - The on-chip RAM region that should be 8Kb large is not reported. This let me think that the region reported as MMIO might well be=20 the on-chip RAM region, btw. > irq 9 at device 11.0 on pci2 > sym0: failed to allocate RAM resources The driver probably allocated the 8K region as MMIO and failed when trying to allocated the on-chip RAM resource (next PCI BAR). > Faltal trap 12: page fault while in kernel mode >=20 > This with a SCSI Host adapter SYMBIOS 53c895a. >=20 > Can You please help me ? It would be interesting to have the actual values of the first 64 bytes of the PCI configuration space for this 53c895 chip. 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 Fri Aug 25 6:14:41 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from starfire.mn.org (starfire.skypoint.net [199.199.159.71]) by hub.freebsd.org (Postfix) with ESMTP id 9677E37B423 for ; Fri, 25 Aug 2000 06:14:38 -0700 (PDT) Received: (from john@localhost) by starfire.mn.org (8.8.5/1.1) id IAA28262; Fri, 25 Aug 2000 08:14:42 -0500 (CDT) Message-ID: Date: Fri, 25 Aug 2000 08:14:42 -0500 From: john@dexter.starfire.mn.org (John) To: freebsd-scsi@FreeBSD.ORG Subject: EMC Symmetrix / Fibre Channel X-Mailer: Mutt 0.53 Mime-Version: 1.0 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am an Advisory Systems Engineer at EMC who is trying to get the company to pay more attention to FreeBSD. The attitude at EMC Corporate seems to be that Linux implies or contains all (significant) Open Source Unix(-like) operating systems! Therefore, I would love to hear from any of you who are operating FreeBSD attached to EMC Symmetrix Integrated Cache Disk Arrays or EMC DG CLARiiON products, what the challenges have been, if you've tried to use Linux compatibility to run the management and support software, and so forth. Related but not quite the same, I would love to hear from those who are working with Fibre Channel Arbitrated Loop Point to Point, FC-AL with hubs, or Fibre Channel Switched Fabric (SAN) for FreeBSD. Thank you! -- John Lind john@starfire.MN.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 25 6:43:40 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 4E9FF37B43E for ; Fri, 25 Aug 2000 06:43:37 -0700 (PDT) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer goliath.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e7PDhJc12721; Fri, 25 Aug 2000 15:43:27 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail2.siemens.de (8.10.1/8.10.1) with ESMTP id e7PDhI118017; Fri, 25 Aug 2000 15:43:18 +0200 (MET DST) Received: (from localhost) by curry.mchp.siemens.de (8.10.2/8.10.2) id e7PDhIM28295; Date: Fri, 25 Aug 2000 15:43:09 +0200 From: Andre Albsmeier To: "Barrett G. Lyon" Cc: Paul Saab , Chuck Robey , freebsd-scsi@FreeBSD.ORG, George Morgan Subject: Re: Adaptec 3960D Ultra160 issues Message-ID: <20000825154309.A24793@curry.mchp.siemens.de> References: <20000824105238.A422@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from blyon@theshell.com on Thu, Aug 24, 2000 at 11:12:42AM -0700 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 24-Aug-2000 at 11:12:42 -0700, Barrett G. Lyon wrote: > Chuck Robey (chuckr@picnic.chuckr.org) wrote: > > Paul, George Morgan and I (see I added him to the CC:, he's not > > subscribed) are both seeing problems with inability to boot IBM Ultra 160 > > drives (he on a Adaptec 39160, me on a 29160). Can you tell me where you > > saw the stuff on this problem, so I can read up on it and see if there's > > some sort of fix for us? > > As an added note, I can boot just fine with IBM U160 disks on the Adaptec > 39160. I just had crashing problems and it only runs at 40 MHz. I can only speak for the 2940U2W and I think the 29160 has the same problem. Don't know about yours... The SCSI driver in -STABLE has a problem when using manual termination settings on the 2940U2W. I have some device on the 68pin SE connector and some on th 50pin SE connector. And two IBM DDYS-T18350N on the LVD connector. So the manual temination settings would be enabled for LVD and ON/OFF for SE. This didn't work, one machine even wasn't able to go multiuser. This was fixed by enabling automatic termination. The other possibility is to use sys/cam/scsi/scsi_message.h sys/cam/cam_ccb.h sys/cam/cam_xpt.c sys/dev/aic7xxx (the whole dir) from -current on 4.1-STABLE. That is what I am doing now. Justin told me yesterday that the -current code will be MFC'ed to -STABLE very soon. Hope it helps, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 25 7:42:52 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 9223B37B424 for ; Fri, 25 Aug 2000 07:42:50 -0700 (PDT) Received: from office.tor.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id B682C137F56; Fri, 25 Aug 2000 10:42:44 -0400 (EDT) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.9.3/8.9.3) id KAA93753; Fri, 25 Aug 2000 10:42:44 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14758.34276.167320.197675@trooper.velocet.net> Date: Fri, 25 Aug 2000 10:42:44 -0400 (EDT) To: Greg Lehey Cc: David Gilbert , freebsd-scsi@FreeBSD.ORG Subject: Re: Vinum 29160 detaches drives, invalidates RAID. In-Reply-To: <20000825113638.D39208@wantadilla.lemis.com> References: <14757.14569.732766.367692@trooper.velocet.net> <20000825113638.D39208@wantadilla.lemis.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Greg" == Greg Lehey writes: >> First of all, I'm very pleased with the speed. The system easily >> beats the AMI MegaRAID 1500 (same drives) with a whopping 35Mbyte/s >> in RAID-5 (vs. the 1500's 14Mbyte/s) for read. (They both score a >> dead heat of 4Mbyte/s write.) Greg> Nice to hear :-) In general, I'm an advocate of the vinum system. I've been hammering it for months now on the test RAID-5 system. Besides this disconnecting problem, the system is performing very well. >> Now... if I reboot, and "vinum setstate up" all these drives, Greg> They all go down, do they? Not all... Sometimes 2 sometimes 4. I suppose I should have said that I setstate up all the drives that are down. >> fsck completes without any complaint. I then generally have to >> "vinum rebuild parity" ... but I suppose that I'd expect that. Greg> Hmm. rebuildparity is a dangerous command. Basically, a parity Greg> error means that *one* (or more) of the drives has incorrect Greg> data. rebuildparity simply assumes that the error is in the Greg> data block and "corrects" it. It's a serious problem, one that Greg> is very difficult to solve. Well... at the point of failure, we're doing the nightly finds on the disk. I do the fsck (usually) before I do the rebuildparity. I suspect that the only information being written to the disk at this point is the access time updates. I would expect, then, that corrupt data is likely limited to an update of this nature. >> The problem I'm having here (and I've had it before) is that the >> FreeBSD SCSI system seems to "give up" under conditions that others >> would keep retrying or resetting/retrying. >> It seems really, really, really important to me that we try harder >> to get a drive back online. This seems as if it could affect the >> long-term viability of a vinum-based raid server... not because >> vinum is bad, but because the SCSI subsystem is too fragile. Greg> Hmm. I can't really comment on that, but it would be nice if Greg> the SCSI system could recover from these problems. I think this is a critical thing. I can accept that it may be hard to discern if the device has been yanked from the bus or had gone into some other bad state --- but this is definately not the case. The FreeBSD SCSI subsystem as-it-stands is very fragile. I realize that cabling must be 100% for many different reasons; ... But by the same token, we need things to keep retrying and resetting far longer before loosing all hope. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 25 10:18: 7 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 A0EDC37B42C for ; Fri, 25 Aug 2000 10:18:05 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA13390; Fri, 25 Aug 2000 10:17:54 -0700 Date: Fri, 25 Aug 2000 10:14:28 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: EMC Symmetrix / Fibre Channel In-Reply-To: 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 > I am an Advisory Systems Engineer at EMC who is trying to get the company > to pay more attention to FreeBSD. The attitude at EMC Corporate seems to > be that Linux implies or contains all (significant) Open Source > Unix(-like) operating systems! Don't I know it! I had a client that had to turn down a working target mode implementation on FreeBSD because it wasn't Linux. Go figure. > > Therefore, I would love to hear from any of you who are operating FreeBSD > attached to EMC Symmetrix Integrated Cache Disk Arrays or EMC DG CLARiiON > products, what the challenges have been, if you've tried to use Linux > compatibility to run the management and support software, and so forth. > > Related but not quite the same, I would love to hear from those > who are working with Fibre Channel Arbitrated Loop Point to Point, > FC-AL with hubs, or Fibre Channel Switched Fabric (SAN) for FreeBSD. I'm the driver writer for the QLogic FC cards in FreeBSD. It works, with varying success, with Vixel, Gadzoox and other hubs in private loop mode (for Qlogic 2100s and 2200s). It works in public loop and point-to-point topologies with Brocade and Ancor SA-8 fabric switches. Both the Brocade && Ancor doing aliasing, so the 2100 should work on fabrics as does the 2200. However, your mileage may vary on that one. FC-IP should be integrated in the next month os so. The same driver also supports Ultra, Ultra2 and Ultra3 cards. Target mode is supported, but not well shaken out in SPI. I have not had the opportunity to try the EMC hardware to validate how well this works or not. Typically, the problems often revolve around firmware issues in the QLogic card that can't often be gotten around. I have a sample LSI-Logic Fibre Channel card that I hope to have a driver in FreeBSD for in a couple of months. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 25 10:25:23 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mproxy.zedo.fuedo.de (mproxy.zedo.fuedo.de [193.99.167.226]) by hub.freebsd.org (Postfix) with ESMTP id 9971D37B422; Fri, 25 Aug 2000 10:25:17 -0700 (PDT) Received: from master.zkom.de (master.zkom.de [193.99.166.6]) by mproxy.zedo.fuedo.de (8.9.3/8.9.3) with ESMTP id TAA23364; Fri, 25 Aug 2000 19:25:16 +0200 (CEST) Received: from zkom.de (jack.zkom.de [193.99.166.10]) by master.zkom.de (8.9.1a/8.8.8) with ESMTP id TAA05122; Fri, 25 Aug 2000 19:25:15 +0200 (CEST) (envelope-from hartung@zkom.de) Message-ID: <39A6AC0C.2F8A6D3B@zkom.de> Date: Fri, 25 Aug 2000 19:25:33 +0200 From: Michael Hartung Organization: ZKOM GmbH, Fax: +49 (0)231 9700 474, Germany X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-isp@freebsd.org Subject: HW-RAID1 FreeBSD 4.1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi girls and boys, We need to setup a server with HW-raid (RAID1 mirroring / 30-60Gbyte). LINT says: # RAID controllers device ida # Compaq Smart RAID device amr # AMI MegaRAID device mlx # Mylex DAC960 family Of course the OS schould be FreeBSD (4.1). Which controller is supported/a good choice? What about the configuration-SW? Is there a substitute for the Mylex DAC960 which is not longer available? Which Compaq, AMI models are supported? A nice weekend and thanks in advance. Michael Hartung -- Michael Hartung |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | ZKOM GmbH | | State Diagnostics Systems | | and Computer Networks | | | | WWW: www.zkom.de (WebCam) | | | | Joseph-von-Fraunhofer Str. 20 | | D-44227 Dortmund | | Germany | | E-mail: hartung@zkom.de | | Phone: +49 (0)231 / 9700 336 | | Fax: +49 (0)231 / 9700 474 | | Mobile: +49 (0)172 / 67 70 522 | | | | AG Dortmund HRB 12918 | | Managing Director: Dipl.-Ing. Michael Hartung | |_______________________________________________| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 25 11:55:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id C811237B43C for ; Fri, 25 Aug 2000 11:55:12 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13SOd8-0001Gt-00; Fri, 25 Aug 2000 18:55:06 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id UAA01456; Fri, 25 Aug 2000 20:55:21 +0200 (CEST) (envelope-from wkb) Date: Fri, 25 Aug 2000 20:55:20 +0200 From: Wilko Bulte To: Olivier Nicole Cc: freebsd-scsi@freebsd.org Subject: Re: Tandberg SLR 100 Message-ID: <20000825205520.C605@freebie.demon.nl> References: <200008250559.MAA07000@banyan.cs.ait.ac.th> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200008250559.MAA07000@banyan.cs.ait.ac.th>; from on@cs.ait.ac.th on Fri, Aug 25, 2000 at 12:59:50PM +0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Aug 25, 2000 at 12:59:50PM +0700, Olivier Nicole wrote: > >So- the answer is "I haven't tried it. Should work." Hopefully one of the > >folks who use QICs more than I do can chime in. I'd recommend at least 4.0. > > Any one that can tell me it works (given this and that configuration) > or it definitely does not work? > > I could go for DLT, but I like QIC like technology better :) QIC is not bad, from the robustness of drive & tape angle. But DLT is better. And much more expensive. Wilko [very happy with his DLTs] -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 25 11:56:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id B2A6E37B42C for ; Fri, 25 Aug 2000 11:56:29 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13SOeS-0001Hn-00; Fri, 25 Aug 2000 18:56:28 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id UAA01470; Fri, 25 Aug 2000 20:56:44 +0200 (CEST) (envelope-from wkb) Date: Fri, 25 Aug 2000 20:56:44 +0200 From: Wilko Bulte To: Matthew Jacob Cc: Olivier Nicole , freebsd-scsi@freebsd.org Subject: Re: Tandberg SLR 100 Message-ID: <20000825205644.D605@freebie.demon.nl> References: <200008250559.MAA07000@banyan.cs.ait.ac.th> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Fri, Aug 25, 2000 at 12:45:40AM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Aug 25, 2000 at 12:45:40AM -0700, Matthew Jacob wrote: > > Any one that can tell me it works (given this and that configuration) > > or it definitely does not work? > > > > I could go for DLT, but I like QIC like technology better :) > > I'll have to admit I'm getting further and further behind the curve on what's > current. I don't work for a company that buys tape toys for me. There are a > lot of issues for tapes that are forever, but what's actually working well > this year is something I can only find out about if spend my own money. This > year, I bought a SCSI analyzer instead (Ancot Ultra3. 5k$USD! Rah! Rah!). AIT drives are also pretty neat. And fast. But not cheap AFAIK. SCSI analysers are there to be borrowed from one's employer, I agree ;-) Some holds, even more strongly, for FC analysers. -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 25 14: 0: 6 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 6BE8537B43C for ; Fri, 25 Aug 2000 14:00:04 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA14210; Fri, 25 Aug 2000 13:59:49 -0700 Date: Fri, 25 Aug 2000 13:56:22 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: Olivier Nicole , freebsd-scsi@FreeBSD.ORG Subject: Re: Tandberg SLR 100 In-Reply-To: <20000825205644.D605@freebie.demon.nl> 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 > > I'll have to admit I'm getting further and further behind the curve on what's > > current. I don't work for a company that buys tape toys for me. There are a > > lot of issues for tapes that are forever, but what's actually working well > > this year is something I can only find out about if spend my own money. This > > year, I bought a SCSI analyzer instead (Ancot Ultra3. 5k$USD! Rah! Rah!). > > AIT drives are also pretty neat. And fast. But not cheap AFAIK. SCSI > analysers are there to be borrowed from one's employer, I agree ;-) Some > holds, even more strongly, for FC analysers. Well, I'm my own employer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 25 14:51:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 67A5737B424 for ; Fri, 25 Aug 2000 14:51:57 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13SROF-00059N-00; Fri, 25 Aug 2000 21:51:55 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id XAA02226; Fri, 25 Aug 2000 23:52:12 +0200 (CEST) (envelope-from wkb) Date: Fri, 25 Aug 2000 23:52:12 +0200 From: Wilko Bulte To: Matthew Jacob Cc: Olivier Nicole , freebsd-scsi@FreeBSD.ORG Subject: Re: Tandberg SLR 100 Message-ID: <20000825235212.A2206@freebie.demon.nl> References: <20000825205644.D605@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Fri, Aug 25, 2000 at 01:56:22PM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Aug 25, 2000 at 01:56:22PM -0700, Matthew Jacob wrote: > > > I'll have to admit I'm getting further and further behind the curve on what's > > > current. I don't work for a company that buys tape toys for me. There are a > > > lot of issues for tapes that are forever, but what's actually working well > > > this year is something I can only find out about if spend my own money. This > > > year, I bought a SCSI analyzer instead (Ancot Ultra3. 5k$USD! Rah! Rah!). > > > > AIT drives are also pretty neat. And fast. But not cheap AFAIK. SCSI > > analysers are there to be borrowed from one's employer, I agree ;-) Some > > holds, even more strongly, for FC analysers. > > Well, I'm my own employer. I know. Means you have to provide your own investment capital. Such is life.. -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message