From owner-freebsd-scsi Sun Jul 19 02:27:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA22371 for freebsd-scsi-outgoing; Sun, 19 Jul 1998 02:27:54 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from galjas.cs.vu.nl (root@galjas.cs.vu.nl [130.37.24.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA22360 for ; Sun, 19 Jul 1998 02:27:43 -0700 (PDT) (envelope-from gkoller@cs.vu.nl) Received: from localhost by galjas.cs.vu.nl with smtp (Smail3.1.28.1 #56) id m0yxpk1-0006MMC; Sun, 19 Jul 98 11:26 +0200 Date: Sun, 19 Jul 1998 11:26:49 +0200 (MET DST) From: Guido Kollerie To: freebsd-scsi@FreeBSD.ORG cc: gibbs@plutotech.com Subject: CAM-19980712 kernel with bt driver 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 a 2.2-stable system (ctm delta 797) compiling a CAM-19980712 kernel which includes the bt (Buslogic Multimaster series) driver results in the follwing error message: cc -c -O2 -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs - Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I../.. - I../../../include -DFFS -DINET -DCOMPAT_43 -DKERNEL ../../i386/isa/bt_isa.c ../../i386/isa/bt_isa.c:47: warning: static declaration for `bt_isa_intr' follows non-static ../../i386/isa/bt_isa.c:47: warning: redundant redeclaration of `bt_isa_intr' in same scope ioconf.h:12: warning: previous declaration of `bt_isa_intr' [...] loading kernel ioconf.o: Undefined symbol `_bt_isa_intr' referenced from data segment *** Error code 1 Removing 'static' from the declaration and definition of bt_isa_intr in /usr/src/sys/i386/isa/bt_isa.c results in a successful build/working kernel. The following warning is retained however: cc -c -O2 -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs - Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I../.. - I../../../include -DFFS -DINET -DCOMPAT_43 -DKERNEL ../../i386/isa/bt_isa.c ../../i386/isa/bt_isa.c:47: warning: redundant redeclaration of `bt_isa_intr' in same scope ioconf.h:12: warning: previous declaration of `bt_isa_intr' -- Guido Kollerie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 19 03:46:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA01796 for freebsd-scsi-outgoing; Sun, 19 Jul 1998 03:46:08 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from obsidian.noc.dfn.de (obsidian.noc.dfn.de [193.174.247.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01678 for ; Sun, 19 Jul 1998 03:45:49 -0700 (PDT) (envelope-from schweikh@obsidian.noc.dfn.de) Received: (from schweikh@localhost) by obsidian.noc.dfn.de (8.8.7/8.8.7) id MAA25652 for freebsd-scsi@freebsd.org; Sun, 19 Jul 1998 12:15:18 +0200 (MET DST) From: Jens Schweikhardt Message-Id: <199807191015.MAA25652@obsidian.noc.dfn.de> Subject: 2940 Questions (no, not *that* many :-) To: freebsd-scsi@FreeBSD.ORG Date: Sun, 19 Jul 1998 12:15:18 +0200 (MET DST) Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hello, world\n I have to chose between two ASUS boards (P2L97S with an adaptec 2940UW host adapter on board). One is about 6 months old (revision unknown), one is relatively new, rev 2.01. So far I have no ultra or wide devices, just fast scsi 2, a seagte ST31200, IBM DCAS 4,3 and a pioneer 10X Cdrom, nothing fancy, and it looks like I won't buy any U or UW devices in the near future. The old board is way cheaper. Are there any gotchas with P2L97S boards I should be aware of? PS: Let me know if I should post such questions to another list. Thanks a lot. Regards, -- Jens Schweikhardt http://www.shuttle.de/schweikh/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 19 05:20:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09749 for freebsd-scsi-outgoing; Sun, 19 Jul 1998 05:20:10 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09737 for ; Sun, 19 Jul 1998 05:20:05 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id OAA13492 for freebsd-scsi@FreeBSD.ORG; Sun, 19 Jul 1998 14:19:47 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id OAA05508 for freebsd-scsi@FreeBSD.ORG; Sun, 19 Jul 1998 14:11:28 +0200 (CEST) (envelope-from roberto) Message-ID: <19980719141127.A5503@keltia.freenix.fr> Date: Sun, 19 Jul 1998 14:11:27 +0200 From: Ollivier Robert To: freebsd-scsi@FreeBSD.ORG Subject: Re: 2940 Questions (no, not *that* many :-) Mail-Followup-To: freebsd-scsi@FreeBSD.ORG References: <199807191015.MAA25652@obsidian.noc.dfn.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807191015.MAA25652@obsidian.noc.dfn.de>; from Jens Schweikhardt on Sun, Jul 19, 1998 at 12:15:18PM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4462 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Jens Schweikhardt: > one is relatively new, rev 2.01. So far I have no ultra or wide devices, > just fast scsi 2, a seagte ST31200, IBM DCAS 4,3 and a pioneer 10X Cdrom, The IBM DCAS drive is Ultra-capable (like the older DORS). ncr0: rev 0x03 int a irq 9 on pci0.11.0 scbus0 at ncr0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access sd0: WIDE SCSI (16 bit) enabled sd0: 40.0 MB/s (50 ns, offset 15) 4134MB (8467200 512 byte sectors) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #61: Sun Jul 12 14:38:23 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 19 08:08:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21277 for freebsd-scsi-outgoing; Sun, 19 Jul 1998 08:08:36 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21272 for ; Sun, 19 Jul 1998 08:08:34 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id JAA02476; Sun, 19 Jul 1998 09:08:11 -0600 (MDT) Message-Id: <199807191508.JAA02476@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Guido Kollerie cc: freebsd-scsi@FreeBSD.ORG, gibbs@plutotech.com Subject: Re: CAM-19980712 kernel with bt driver In-reply-to: Your message of "Sun, 19 Jul 1998 11:26:49 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Jul 1998 09:02:58 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On a 2.2-stable system (ctm delta 797) compiling a CAM-19980712 kernel >which includes the bt (Buslogic Multimaster series) driver results in the >follwing error message: The fix for this is to not declare the interrupt vector in your kernel config file. Your config line should follow what is presented in the CAM GENERIC config file: controller bt0 at isa? port ? cam irq ? Notice the use of cam and not bio. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 19 08:17:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21766 for freebsd-scsi-outgoing; Sun, 19 Jul 1998 08:17:11 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tor-dev1.nbc.netcom.ca (tor-dev1.nbc.netcom.ca [207.181.89.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21760 for ; Sun, 19 Jul 1998 08:17:09 -0700 (PDT) (envelope-from dacole@netcom.ca) Received: from localhost (dacole@localhost) by tor-dev1.nbc.netcom.ca (8.8.8/8.8.8) with SMTP id LAA26730 for ; Sun, 19 Jul 1998 11:16:34 -0400 (EDT) X-Authentication-Warning: tor-dev1.nbc.netcom.ca: dacole owned process doing -bs Date: Sun, 19 Jul 1998 11:16:33 -0400 (EDT) From: Dave Cole X-Sender: dacole@tor-dev1.nbc.netcom.ca To: freebsd-scsi@FreeBSD.ORG Subject: symbios 53c875 and activity led? 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 know I posted once before, asking for help getting my LED on my asus sc875 (based on the ncr/symbios 53c875 scsi interface) and I'm back again, asking the same question. Many moons ago, the solution was supposedly adding 'option NCR_SYMBIOS_COMPAT' or somesuch to the kernel definition file. Well, that option went away about 2 months after that. I haven't tried a -cam world with this interface yet, and hope to soon, but in the meantime, whom else has this issue? I rather like being able to see my scsi bus accesses, just to prove to myself that the system is actually doing something at times, and miss my LED greatly. Is there another easy patch? Was the LED turned off deliberately? etc. etc. etc. ---------------------------------------------------------------- Dave Cole (DC1110) | dacole@netcom.ca Systems Administrator |* dacole@rik.net * | office/~dacole/ Netcom Canada |* www.rik.net/~dacole/ * 905 King Street West, Toronto, M6K 3G9 | phone - 416.341.5801 Toronto, Ontario, Canada, Earth, Sol | fax - 416.341.5725 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 19 14:38:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25673 for freebsd-scsi-outgoing; Sun, 19 Jul 1998 14:38:52 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25643 for ; Sun, 19 Jul 1998 14:38:48 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA09283 for freebsd-scsi@FreeBSD.ORG; Sun, 19 Jul 1998 23:38:30 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id XAA07612 for freebsd-scsi@FreeBSD.ORG; Sun, 19 Jul 1998 23:07:20 +0200 (CEST) (envelope-from roberto) Message-ID: <19980719230720.A7609@keltia.freenix.fr> Date: Sun, 19 Jul 1998 23:07:20 +0200 From: Ollivier Robert To: freebsd-scsi@FreeBSD.ORG Subject: Re: symbios 53c875 and activity led? Mail-Followup-To: freebsd-scsi@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: ; from Dave Cole on Sun, Jul 19, 1998 at 11:16:33AM -0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4462 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Dave Cole: > Many moons ago, the solution was supposedly adding 'option > NCR_SYMBIOS_COMPAT' or somesuch to the kernel definition file. Well, > that option went away about 2 months after that. Well, it is still here even if config(8) doesn't like it. The driver still uses this #define to play with the lights. I use it myself. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #61: Sun Jul 12 14:38:23 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 19 15:16:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01504 for freebsd-scsi-outgoing; Sun, 19 Jul 1998 15:16:12 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01429 for ; Sun, 19 Jul 1998 15:16:01 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt1-226.HiWAAY.net [208.147.147.226]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id RAA27525 for ; Sun, 19 Jul 1998 17:15:46 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id NAA22095 for ; Sun, 19 Jul 1998 13:37:40 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199807191837.NAA22095@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: symbios 53c875 and activity led? In-reply-to: Message from Dave Cole of "Sun, 19 Jul 1998 11:16:33 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Jul 1998 13:37:40 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dave Cole writes: > I know I posted once before, asking for help getting my LED on my asus > sc875 (based on the ncr/symbios 53c875 scsi interface) and I'm back > again, asking the same question. > > Many moons ago, the solution was supposedly adding 'option > NCR_SYMBIOS_COMPAT' or somesuch to the kernel definition file. Well, > that option went away about 2 months after that. > > I haven't tried a -cam world with this interface yet, and hope to > soon, but in the meantime, whom else has this issue? I rather like > being able to see my scsi bus accesses, just to prove to myself that > the system is actually doing something at times, and miss my LED > greatly. Is there another easy patch? Was the LED turned off > deliberately? etc. etc. etc. You mean to tell me this is a FreeBSD problem? All along I just assumed the LED circuit was broken on my Asus SC875. Then again, I've never run the card under DOS or Windows or anything other than FreeBSD. -- David Kelly N4HHE, dkelly@nospam.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 Sun Jul 19 16:28:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10628 for freebsd-scsi-outgoing; Sun, 19 Jul 1998 16:28:00 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (root@duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10609 for ; Sun, 19 Jul 1998 16:27:57 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id SAA18766; Sun, 19 Jul 1998 18:27:40 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Sun, 19 Jul 1998 18:27:39 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: David Kelly cc: freebsd-scsi@FreeBSD.ORG Subject: Re: symbios 53c875 and activity led? In-Reply-To: <199807191837.NAA22095@nospam.hiwaay.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 19 Jul 1998, David Kelly wrote: > Dave Cole writes: > > I know I posted once before, asking for help getting my LED on my asus > > sc875 (based on the ncr/symbios 53c875 scsi interface) and I'm back > > again, asking the same question. > > > > Many moons ago, the solution was supposedly adding 'option > > NCR_SYMBIOS_COMPAT' or somesuch to the kernel definition file. Well, > > that option went away about 2 months after that. > > > > I haven't tried a -cam world with this interface yet, and hope to > > soon, but in the meantime, whom else has this issue? I rather like > > being able to see my scsi bus accesses, just to prove to myself that > > the system is actually doing something at times, and miss my LED > > greatly. Is there another easy patch? Was the LED turned off > > deliberately? etc. etc. etc. > > You mean to tell me this is a FreeBSD problem? All along I just assumed > the LED circuit was broken on my Asus SC875. Then again, I've never run > the card under DOS or Windows or anything other than FreeBSD. I heard of this problem with the driver a LONG time ago, and thought it was fixed. If it matters any, the LED on my Tekram DC-390F (53c875) has been working for a long time. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://www.freebsd.org) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 19 19:36:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01579 for freebsd-scsi-outgoing; Sun, 19 Jul 1998 19:36:51 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01557 for ; Sun, 19 Jul 1998 19:36:38 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id EAA05359 for scsi@FreeBSD.ORG; Mon, 20 Jul 1998 04:30:19 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id EAA20874 for scsi@FreeBSD.ORG; Mon, 20 Jul 1998 04:26:26 +0200 (CEST) (envelope-from andreas) Message-ID: <19980720042626.A6091@klemm.gtn.com> Date: Mon, 20 Jul 1998 04:26:26 +0200 From: Andreas Klemm To: scsi@FreeBSD.ORG Subject: scanner problems on -current (MUSTEK MSF-06000CZ, pt0 device) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi ! 1st tried to run the scanner under CAM, but the pt0 device doesn't seem to be supported on CAM. Then I switched back to -current, but although the scanner seems to be connected properly to the SCSI bus (adaptec device probing finds it on boot), the pt0 device doesn't show up. Instead of this the unknown device shows up. I use 2 x 2940 SCSI controller. 1st: AHA 2940 U - auto termination Boot disk, Tape and such internal ... 2nd: AHA 2940 - auto termination internal: 2 x IBM DORS, last drive terminated external: Scanner seems to have auto termination I tried to configure everything. Scanner on SCSI ID 5, 6, with only 5 MB/sec ... Nothing works. Only under CAM the scanner was recognized suring inquiry. Under -current's SCSI driver the scanner isn't recognized ... Another strange thing. If I jumper the scanner to SCSI device ID 5 it shows up on SCSI ID 0 and 5, if on 6 it shows up only on SCSI ID 6 (in the adaptec device list during boot). Jul 19 20:28:36 titan /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jul 19 20:28:36 titan /kernel: The Regents of the University of California. All rights reserved. Jul 19 20:28:36 titan /kernel: FreeBSD 3.0-CURRENT #0: Sun Jul 19 20:19:49 CEST 1998 Jul 19 20:28:36 titan /kernel: root@titan.klemm.gtn.com:/home/src/sys/compile/ISDNSMP Jul 19 20:28:36 titan /kernel: Calibrating clock(s) ... TSC clock: 199429395 Hz, i8254 clock: 1193165 Hz Jul 19 20:28:36 titan /kernel: CLK_USE_I8254_CALIBRATION not specified - using default frequency Jul 19 20:28:36 titan /kernel: Timecounter "i8254" frequency 1193182 Hz cost 3558 ns Jul 19 20:28:36 titan /kernel: CLK_USE_TSC_CALIBRATION not specified - using old calibration method Jul 19 20:28:36 titan /kernel: CPU: Pentium Pro (686-class CPU) Jul 19 20:28:37 titan /kernel: Origin = "GenuineIntel" Id = 0x619 Stepping=9 Jul 19 20:28:37 titan /kernel: Features=0xfbff Jul 19 20:28:37 titan /kernel: real memory = 83886080 (81920K bytes) Jul 19 20:28:37 titan /kernel: Physical memory chunk(s): Jul 19 20:28:37 titan /kernel: 0x00001000 - 0x0009efff, 647168 bytes (158 pages) Jul 19 20:28:37 titan /kernel: 0x0027c000 - 0x04ff5fff, 81240064 bytes (19834 pages) Jul 19 20:28:37 titan /kernel: avail memory = 78512128 (76672K bytes) Jul 19 20:28:37 titan /kernel: SMP: CPU0 apic_initialize(): Jul 19 20:28:37 titan /kernel: lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff Jul 19 20:28:37 titan /kernel: FreeBSD/SMP: Multiproces Jul 19 20:28:37 titan /kernel: sor motherboard Jul 19 20:28:37 titan /kernel: cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 Jul 19 20:28:37 titan /kernel: cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 Jul 19 20:28:37 titan /kernel: io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Jul 19 20:28:37 titan /kernel: Found BIOS32 Service Directory header at 0xf00fad00 Jul 19 20:28:37 titan /kernel: Entry = 0xfb180 (0xf00fb180) Rev = 0 Len = 1 Jul 19 20:28:37 titan /kernel: PCI BIOS entry at 0xb1b0 Jul 19 20:28:37 titan /kernel: Other BIOS signatures found: Jul 19 20:28:37 titan /kernel: ACPI: 00000000 Jul 19 20:28:37 titan /kernel: $PnP: 000fbec0 Jul 19 20:28:37 titan /kernel: SMP: CPU0 bsp_apic_configure(): Jul 19 20:28:37 titan /kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff Jul 19 20:28:37 titan /kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c Jul 19 20:28:37 titan /kernel: pci_open(1a): mode1res=0x80000000 (0x80000000) Jul 19 20:28:37 titan /kernel: pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12378086) Jul 19 20:28:37 titan /kernel: Probing for devices on PCI bus 0: Jul 19 20:28:37 titan /kernel: found-> vendor=0x8086, dev=0x1237, revid=0x02 Jul 19 20:28:37 titan /kernel: class=06-00-00, hdrtype=0x00, mfdev=0 Jul 19 20:28:37 titan /kernel: chip0: rev 0x02 on pci0.0.0 Jul 19 20:28:37 titan /kernel: found-> vendor=0x8086, dev=0x7000, revid=0x01 Jul 19 20:28:37 titan /kernel: class=06-01-00, hdrtype=0x00, mfdev=1 Jul 19 20:28:37 titan /kernel: chip1: rev 0x01 on pci0.7.0 Jul 19 20:28:37 titan /kernel: I/O Recovery Timing: Jul 19 20:28:37 titan /kernel: 8-bit 1 clocks, 16-bit 1 clocks Jul 19 20:28:37 titan /kernel: Extended BIOS: enabled Jul 19 20:28:37 titan /kernel: Lower BIOS: disabled Jul 19 20:28:37 titan /kernel: Coprocessor IRQ13: enabled Jul 19 20:28:37 titan /kernel: Mouse IRQ12: enabled Jul 19 20:28:37 titan /kernel: Interrupt Routing: A: IRQ15, B: IRQ11, C: IRQ9, D: IRQ14 Jul 19 20:28:37 titan /kernel: MB0: , MB1: Jul 19 20:28:37 titan /kernel: found-> vendor=0x8086, dev=0x7010, revid=0x00 Jul 19 20:28:37 titan /kernel: class=01-01-80, hdrtype=0x00, mfdev=0 Jul 19 20:28:37 titan /kernel: Freeing (NOT implemented) redirected PCI irq 14. Jul 19 20:28:37 titan /kernel: found-> vendor=0x102b, dev=0x0519, revid=0x01 Jul 19 20:28:37 titan /kernel: class=03-00-00, hdrtype=0x00, mfdev=0 Jul 19 20:28:37 titan /kernel: intpin=a, irq=19 Jul 19 20:28:37 titan /kernel: map[0]: type 1, range 32, base e0800000, size 14 Jul 19 20:28:37 titan /kernel: map[1]: type 3, range 32, base e0000000, size 23 Jul 19 20:28:37 titan /kernel: vga0: rev 0x01 int a irq 19 on pci0.11.0 Jul 19 20:28:37 titan /kernel: Freeing (NOT implemented) redirected PCI irq 9. Jul 19 20:28:37 titan /kernel: found-> vendor=0x10b7, dev=0x9001, revid=0x00 Jul 19 20:28:37 titan /kernel: class=02-00-00, hdrtype=0x00, mfdev=0 Jul 19 20:28:37 titan /kernel: intpin=a, irq=18 Jul 19 20:28:37 titan /kernel: map[0]: type 4, range 32, base 00008000, size 6 Jul 19 20:28:37 titan /kernel: vx0: <3COM 3C900 Etherlink XL PCI> rev 0x00 int a irq 18 on pci0.12.0 Jul 19 20:28:37 titan /kernel: utp/aui/bnc[*utp*] address 00:60:97:aa:3a:db Jul 19 20:28:37 titan /kernel: bpf: vx0 attached Jul 19 20:28:37 titan /kernel: Freeing (NOT implemented) redirected PCI irq 11. Jul 19 20:28:37 titan /kernel: found-> vendor=0x900 Jul 19 20:28:37 titan /kernel: 4, dev=0x8178, revid=0x00 Jul 19 20:28:37 titan /kernel: class=01-00-00, hdrtype=0x00, mfdev=0 Jul 19 20:28:37 titan /kernel: intpin=a, irq=17 Jul 19 20:28:37 titan /kernel: map[0]: type 4, range 32, base 00008100, size 8 Jul 19 20:28:37 titan /kernel: map[1]: type 1, range 32, base e0804000, size 12 Jul 19 20:28:37 titan /kernel: ahc0: rev 0x00 int a irq 17 on pci0.13.0 Jul 19 20:28:37 titan /kernel: ahc0: Reading SEEPROM...done. Jul 19 20:28:37 titan /kernel: internal50 cable is present Jul 19 20:28:37 titan /kernel: internal68 cable not present Jul 19 20:28:37 titan /kernel: brdctl == 0xac Jul 19 20:28:37 titan /kernel: external cable not present Jul 19 20:28:37 titan /kernel: eprom is present Jul 19 20:28:37 titan /kernel: brdctl == 0xec Jul 19 20:28:37 titan /kernel: low byte termination enabled, high byte termination disabled Jul 19 20:28:37 titan /kernel: ahc0: aic7880 Single Channel, SCSI Id=7, 16/255 SCBs Jul 19 20:28:37 titan /kernel: ahc0: Resetting Channel A Jul 19 20:28:37 titan /kernel: ahc0: Downloading Sequencer Program...ahc0: 417 instructions downloaded Jul 19 20:28:37 titan /kernel: Done Jul 19 20:28:37 titan /kernel: ahc0: Probing channel A Jul 19 20:28:37 titan /kernel: Choosing drivers for scbus configured at 0 Jul 19 20:28:37 titan /kernel: ahc0: waiting for scsi devices to settle Jul 19 20:28:37 titan /kernel: scbus0 at ahc0 bus 0 Jul 19 20:28:37 titan /kernel: ahc0: target 0 synchronous at 20.0MHz, offset = 0xf Jul 19 20:28:37 titan /kernel: ahc0: target 0 Tagged Queuing Device Jul 19 20:28:37 titan /kernel: sd is configured at 0 Jul 19 20:28:37 titan /kernel: sd0 at scbus0 target 0 lun 0 Jul 19 20:28:37 titan /kernel: sd0: type 0 fixed SCSI 2 Jul 19 20:28:37 titan /kernel: sd0: Direct-Access 2063MB (4226725 512 byte sectors) Jul 19 20:28:37 titan /kernel: sd0: with 670 Jul 19 20:28:37 titan /kernel: 3 cyls, 5 heads, and an average 126 sectors/track Jul 19 20:28:37 titan /kernel: ahc0: target 4 synchronous at 4.4MHz, offset = 0x8 Jul 19 20:28:37 titan /kernel: st is configured at 0 Jul 19 20:28:38 titan /kernel: st0 at scbus0 target 4 lun 0 Jul 19 20:28:38 titan /kernel: st0: type 1 removable SCSI 2 Jul 19 20:28:38 titan /kernel: st0: Sequential-Access density code 0x0, 512-byte blocks, write-enabled Jul 19 20:28:38 titan /kernel: ahc0: target 6 synchronous at 10.0MHz, offset = 0x8 Jul 19 20:28:38 titan /kernel: cd is configured at 0 Jul 19 20:28:38 titan /kernel: cd0 at scbus0 target 6 lun 0 Jul 19 20:28:38 titan /kernel: cd0: type 5 removable SCSI 2 Jul 19 20:28:38 titan /kernel: cd0: CD-ROM can't get the size Jul 19 20:28:38 titan /kernel: Freeing (NOT implemented) redirected PCI irq 15. Jul 19 20:28:38 titan /kernel: found-> vendor=0x9004, dev=0x7178, revid=0x03 Jul 19 20:28:38 titan /kernel: class=01-00-00, hdrtype=0x00, mfdev=0 Jul 19 20:28:38 titan /kernel: intpin=a, irq=16 Jul 19 20:28:38 titan /kernel: map[0]: type 4, range 32, base 00008200, size 8 Jul 19 20:28:38 titan /kernel: map[1]: type 1, range 32, base e0805000, size 12 Jul 19 20:28:38 titan /kernel: ahc1: rev 0x03 int a irq 16 on pci0.14.0 Jul 19 20:28:38 titan /kernel: ahc1: Reading SEEPROM...done. Jul 19 20:28:38 titan /kernel: low byte termination disabled, high byte termination enabled Jul 19 20:28:38 titan /kernel: ahc1: aic7870 Single Channel, SCSI Id=7, 16/255 SCBs Jul 19 20:28:38 titan /kernel: ahc1: Downloading Sequencer Program...ahc1: 410 instructions downloaded Jul 19 20:28:38 titan /kernel: Done Jul 19 20:28:38 titan /kernel: ah Jul 19 20:28:38 titan /kernel: c1: Probing channel A Jul 19 20:28:38 titan /kernel: Choosing drivers for scbus configured at 1 Jul 19 20:28:38 titan /kernel: ahc1: waiting for scsi devices to settle Jul 19 20:28:38 titan /kernel: scbus1 at ahc1 bus 0 Jul 19 20:28:38 titan /kernel: ahc1: target 1 synchronous at 10.0MHz, offset = 0xf Jul 19 20:28:38 titan /kernel: ahc1: target 1 Tagged Queuing Device Jul 19 20:28:38 titan /kernel: sd is configured at 1 Jul 19 20:28:38 titan /kernel: sd1 at scbus1 target 1 lun 0 Jul 19 20:28:38 titan /kernel: sd1: type 0 fixed SCSI 2 Jul 19 20:28:38 titan /kernel: sd1: Direct-Access 2063MB (4226725 512 byte sectors) Jul 19 20:28:38 titan /kernel: sd1: with 6703 cyls, 5 heads, and an average 126 sectors/track Jul 19 20:28:38 titan /kernel: ahc1: target 2 synchronous at 10.0MHz, offset = 0xf Jul 19 20:28:38 titan /kernel: ahc1: target 2 Tagged Queuing Device Jul 19 20:28:38 titan /kernel: sd is configured at 2 Jul 19 20:28:38 titan /kernel: sd2 at scbus1 target 2 lun 0 Jul 19 20:28:38 titan /kernel: sd2: type 0 fixed SCSI 2 Jul 19 20:28:38 titan /kernel: sd2: Direct-Access 2063MB (4226725 512 byte sectors) Jul 19 20:28:38 titan /kernel: sd2: with 6703 cyls, 5 heads, and an average 126 sectors/track Jul 19 20:28:38 titan /kernel: uk0 at scbus1 target 5 lun 0 Jul 19 20:28:38 titan /kernel: uk0: type 0 fixed SCSI 0 Jul 19 20:28:38 titan /kernel: uk0: Unknown Jul 19 20:28:38 titan /kernel: uk1 at scbus1 target 5 lun 1 Jul 19 20:28:38 titan /kernel: uk1: type 0 fixed SCSI 0 Jul 19 20:28:38 titan /kernel: uk1: Unknown Jul 19 20:28:38 titan /kernel: uk2 at scbus1 target 5 lun 2 Jul 19 20:28:38 titan /kernel: uk2: type 0 fixed SCSI 0 Jul 19 20:28:38 titan /kernel: uk2: Unknown Jul 19 20:28:38 titan /kernel: uk3 at scbus1 tar Jul 19 20:28:38 titan /kernel: get 5 lun 3 Jul 19 20:28:38 titan /kernel: uk3: type 0 fixed SCSI 0 Jul 19 20:28:38 titan /kernel: uk3: Unknown Jul 19 20:28:38 titan /kernel: uk4 at scbus1 target 5 lun 4 Jul 19 20:28:38 titan /kernel: uk4: type 0 fixed SCSI 0 Jul 19 20:28:38 titan /kernel: uk4: Unknown Jul 19 20:28:38 titan /kernel: uk5 at scbus1 target 5 lun 5 Jul 19 20:28:38 titan /kernel: uk5: type 0 fixed SCSI 0 Jul 19 20:28:38 titan /kernel: uk5: Unknown Jul 19 20:28:38 titan /kernel: uk6 at scbus1 target 5 lun 6 Jul 19 20:28:38 titan /kernel: uk6: type 0 fixed SCSI 0 Jul 19 20:28:38 titan /kernel: uk6: Unknown Jul 19 20:28:38 titan /kernel: uk7 at scbus1 target 5 lun 7 Jul 19 20:28:38 titan /kernel: uk7: type 0 fixed SCSI 0 Jul 19 20:28:38 titan /kernel: uk7: Unknown Jul 19 20:28:38 titan /kernel: Probing for devices on the ISA bus: Jul 19 20:28:38 titan /kernel: sc0: the current keyboard controller command byte 0047 Jul 19 20:28:38 titan /kernel: kbdio: DIAGNOSE status:0055 Jul 19 20:28:38 titan /kernel: kbdio: TEST_KBD_PORT status:0000 Jul 19 20:28:38 titan /kernel: kbdio: RESET_KBD return code:00fa Jul 19 20:28:38 titan /kernel: kbdio: RESET_KBD status:00aa # # ISDN kernel # machine "i386" cpu "I686_CPU" ident ISDNSMP # rse's recommendations for heavily users apache servers maxusers 256 #options SOMAXCONN="256" #options "NMBCLUSTER=4096" #options "CHILD_MAX=512" #options "OPEN_MAX=512" # Options for the VM subsystem #options PQ_NOOPT # No coloring #options PQ_LARGECACHE # color for 512k/16k cache options PQ_HUGECACHE # color for 1024k/16k cache options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O options INCLUDE_CONFIG_FILE # Include this file in kernel #options USERCONFIG #boot -c editor #options VISUAL_USERCONFIG #visual boot -c editor options DDB options KTRACE #kernel tracing options SHOW_BUSYBUFS # busy buffers on shutdown ? options INET #InterNETworking options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about dropped packets options "IPFIREWALL_VERBOSE_LIMIT=500" #limit verbosity options IPDIVERT #divert sockets #options IPFILTER #kernel ipfilter support #options IPFILTER_LOG #ipfilter logging options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" options FFS #Berkeley Fast Filesystem #options NFS #Network File System options MFS #Memory File System #options UNION #Union filesystem options "CD9660" #ISO 9660 filesystem options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options NSWAPDEV=3 #Allow this many swap-devices. #options QUOTA #enable disk quotas options SOFTUPDATES #Kirk McKusick's code # DEVFS and SLICE are experimental but work. # SLICE disables too much old code so enabling it in LINT would be bad #options DEVFS #devices filesystem #options SLICE #devfs based disk handling # misc options options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options SYSVSHM,SYSVSEM,SYSVMSG #shared memory (X11) options COMPAT_LINUX # Linux Binary compatibility #options USER_LDT # for Wine options "MD5" #options "VM86" config kernel root on sd1 # ISA and PCI BUS support controller isa0 controller pci0 # Floppy Disk Controller controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 # SCSI Devices # AHA 2940U controller ahc0 controller scbus0 at ahc0 disk sd0 at scbus0 target 0 unit 0 disk sd3 at scbus0 target 1 unit 0 tape st0 at scbus0 target 4 device worm0 at scbus0 target 5 device cd0 at scbus0 target 6 # AHA 2940 controller ahc1 controller scbus1 at ahc1 disk sd1 at scbus1 target 1 unit 0 disk sd2 at scbus1 target 2 unit 0 device pt0 at scbus1 target 5 unit 0 options SCSI_DELAY=15 # Be pessimistic about Joe SCSI device options "CD9660_ROOTDELAY=8" options AHC_TAGENABLE # tagged command queueing options AHC_ALLOW_MEMIO options AHC_SCBPAGING_ENABLE options SCSI_REPORT_GEOMETRY # SCO compatible system console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=4 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines # The pcvt console driver (vt220 compatible). #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options XSERVER # support for running an X server. #options FAT_CURSOR # start with block cursor # floating point unit device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr # serial devices on mainboard # `flags' for serial drivers that support consoles (only for sio now): # 0x10 enable console support for this unit. The other console flags # are ignored unless this is set. Enabling console support does # not make the unit the preferred console - boot with -h or set # the 0x20 flag for that. Currently, at most one unit can have # console support; the first one (in config file order) with # this flag set is preferred. Setting this flag for sio0 gives # the old behaviour. # 0x20 force this unit to be the console (unless there is another # higher priority console). This replaces the COMCONSOLE option. # 0x40 reserve this unit for low level console operations. Do not # device sio0 at isa? port "IO_COM1" tty irq 4 flags 0x20 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to DDB, #if available. options CONSPEED=38400 #default speed for serial console #(default 9600) # parallel device on mainboard device lpt0 at isa? port? tty irq 7 vector lptintr # PS/2 mouse on mainboard device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr options "PSM_ACCEL=1" # PS/2 mouse acceleration # Joystick #device joy0 at isa? port "IO_GAME" # Network 3COM PCI device vx0 #device ed0 at isa? port 0x280 net irq 10 iomem 0xd0000 vector edintr # Soundblaster 16 # SoundBlaster DSP driver - for SB, SB Pro, SB16, PAS(emulating SB) # SoundBlaster 16 DSP driver - for SB16 - requires sb0 device # SoundBlaster 16 MIDI - for SB16 - requires sb0 device # Yamaha OPL-2/OPL-3 FM - for SB, SB Pro, SB16, PAS # controller snd0 # device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr # device sbxvi0 at isa? port? irq? drq 5 conflicts # device sbmidi0 at isa? port 0x330 irq? conflicts # device opl0 at isa? port 0x388 conflicts # pcm: PCM audio through various sound cards. # New Sound code device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x15 vector pcmintr # Pseudo devices pseudo-device loop #Network loopback device pseudo-device ether #Generic Ethernet pseudo-device vn 1 #Vnode driver (turns a file into a dev.) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device disc #Discard device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device pty 16 #Pseudo ttys - can go as high as 256 pseudo-device gzip # Exec gzipped a.out's pseudo-device ccd 4 #Concatenated disk driver pseudo-device tun 1 #Tunnel driver (user process ppp(8)) #pseudo-device ppp 1 #Point-to-point protocol #options PPP_BSDCOMP #PPP BSD-compress support #options PPP_DEFLATE #PPP zlib/deflate/gzip support #options PPP_FILTER #enable bpf filtering (needs bpfilter) # Size of the kernel message buffer. Should be N * pagesize. options "MSGBUF_SIZE=40960" ## BISDN #options IPI_VJ # Van Jacobsen header compression support ##options "IPI_DIPA=3" # send ip accounting packets every 3 seconds #options TELES_HAS_MEMCPYB # bisdn 0.97 # ## Teles S0/16.3 ################################################### IRQ 9 ## #controller tel0 at isa? port 0xd80 net irq 9 vector telintr #pseudo-device disdn #pseudo-device isdn #pseudo-device ipi 4 #pseudo-device ispy 4 #pseudo-device itel 1 options "I4B_SMP_WORKAROUND" # i4b passive ISDN cards support (isic - I4b Siemens Isdn Chipset driver) # Teles S0/16.3 options "TEL_S0_16_3" device isic0 at isa? port 0xd80 net irq 9 flags 0x04 vector isicintr # i4b passive cards D channel handling # Q.921 pseudo-device "i4bq921" # Q.931 pseudo-device "i4bq931" # common passive and active layer 4 # layer 4 pseudo-device "i4b" # userland driver to do ISDN tracing (for passive cards oly) pseudo-device "i4btrc" 4 # userland driver to control the whole thing pseudo-device "i4bctl" # userland driver for access to raw B channel pseudo-device "i4brbch" 4 # userland driver for telephony pseudo-device "i4btel" 2 # network driver for IP over raw HDLC ISDN pseudo-device "i4bipr" 4 # enable VJ header compression detection for ipr i/f options IPR_VJ # network driver for sync PPP over ISDN pseudo-device "i4bisppp" 4 pseudo-device sppp 4 -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 19 23:25:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02197 for freebsd-scsi-outgoing; Sun, 19 Jul 1998 23:25:55 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from rigel.cs.pdx.edu (root@rigel.cs.pdx.edu [131.252.220.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02192 for ; Sun, 19 Jul 1998 23:25:53 -0700 (PDT) (envelope-from rotan@cs.pdx.edu) Received: from sol.cs.pdx.edu (slip15.cs.pdx.edu [131.252.218.15]) by rigel.cs.pdx.edu (8.8.6/8.8.6) with ESMTP id XAA26761; Sun, 19 Jul 1998 23:25:32 -0700 (PDT) Message-Id: <199807200625.XAA26761@rigel.cs.pdx.edu> From: "robert t tan" To: "scsi" Cc: Subject: AHA-2940UW Date: Sun, 19 Jul 1998 23:25:06 -0700 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Need help with the following, please: This is my configuration: Terminated, 2G Western Digital Wide SCSI hard drive ( 16 bit), Terminated 12/20 Plexter CDROM ( 8 bit ) SCSI. AHA-2940UW SCSI host adapter Micron Millenia board. Besided the controller card there is just the video card. Sync and Disconnect are both disabled for all the devices in the SCSI chain ( hard drive, CDROM, and controller ). Mother Board BIOS: Phoenix v4.04 Host adapter BIOS: v1.32 PNP is disabled. Partitions: Primary active DOS partition: 250M win95 Rest: Unused. I have a problem when booting FreeBSD with the install floppy: /RELEASE2.2.6/updates/boot.flp, see below for boot dmesg output By the way WIN95 runs fine, and had FreeBSD runing when I used a buslogic controler on a regular SCSI drive ( 2G ) Have tried the following: - Disconnecting the CDROM. - Taking out the controller and booting untill "No Operating System", then rebooting again. - Moving the controller to different PCI slots. - Sync, and disconnect enabled. - Searching around for this problem on the net. Below: >> Mouse IRQ12: enabled Interrupt Routing: A: disabled, B: disabled, C: IRQ15, D: IRQ11 MB0: disabled, MB1: disabled chip2 rev 1 int a irq 11 on pci0:17:0 mapreg[10] type = 1 addr = 0000fc00 size = 0100 mapreg[14] type = 0 addr = f0dff000 size = 1000 reg16: ioaddr = 0xfc00 size 0x100 ahc0: reading SEEPROM ... done internal 50 cable is present internal 68 cable is present brdctl == 0x2c external cable not present eprom is present brdctl == 0xcc low byte termination disabled, high byte termination enabled ahc0: aic7880 Wide Channel, SCSI Id = 7, 116 SCBs ahc0: Downloading Sequencer program ... ahc: 373 instructions downloaded Done ahc0: Probing channel A ahc0: Waiting for scsi devices to settle achc0: board is not responding (ahc0:0:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x01 SCSISIGI == 0x0 SEQADDR = 0x166 SCSISEQ = 0x12 SSTAT0 = 0x4 SSTAT1 = 0x8 (ahc0:0:0) Queueing an abort SCB ahc:0 board is not responding cmd fail (ahc0:0:0) SCB 0x1 timed out while recovery in progress (ahc0:0:0) "Unknown unknown ????" type 13 fixed SCSI 0 uk0(ahc0:0:0): Unknown ahc0: board is not responding ..... << Thanks, robert t tan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 20 07:52:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15574 for freebsd-scsi-outgoing; Mon, 20 Jul 1998 07:52:49 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15568 for ; Mon, 20 Jul 1998 07:52:47 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id QAA24386; Mon, 20 Jul 1998 16:52:29 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id QAA01705; Mon, 20 Jul 1998 16:52:28 +0200 (MET DST) Date: Mon, 20 Jul 1998 16:52:28 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199807201452.QAA01705@surf.IAE.nl> To: cdillon@wolves.k12.mo.us Subject: Re: IBM DCAS X-Newsgroups: list.freebsd.current In-Reply-To: References: <19980719222526.A25289@mi.uni-koeln.de> Organization: Internet Access Eindhoven, the Netherlands Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you write: >On Sun, 19 Jul 1998, Stefan Esser wrote: > >> On 1998-07-12 17:30 -0500, Chris Dillon wrote: >> > > Negotiations may be started by both the drive or host adapter >> > > at any time. But except for IBM, most vendors leave it up to >> > > the host system to send the first message (which the driver >> > > does after receiving the result of an INQUIRY command). >> > >> > Ok, makes sense.. I was just wondering. :-) >> > >> > And I guess that last part about IBM drives is a GoodThing? >> >> It doesn't really matter. The IBM driver have >> other annoying firmware features (e.g. can't >> deal with a "start motor" command in certain >> situation where it could be considered a NOP), >> and they sometimes drop the number of tagged >> commands they can deal with for no apparent >> reason. But I'm still thinking that the DDRS >> is a rather good buy, currently ;-) > >I thought that tag problem was only with certain Quantum drives. :-) >Well, these are DCAS drives, and have worked without a single hitch so >far, but I wouldn't exactly say I put them under any major stress. >Knock on wood. I currently run a rack of DCAS on an adaptec 2940UW without much of a problem (until last night, which is most likely a temperature problem) (ahc0:14:0): "IBM DCAS-34330W S61A" I've created several CCD's and I'm trying to pound on them using bonnie, iozone, and likes. Like I said, they ran for 4 days hammering without trouble, until the summer started here in Holland. And my garage/office started to heat up. Now I've asked IBM what the latest firmware release for these drives was. But untill now I've only received dumb, std answers. --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 20 10:15:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03795 for freebsd-scsi-outgoing; Mon, 20 Jul 1998 10:15:54 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (root@duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03790 for ; Mon, 20 Jul 1998 10:15:53 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id MAA21332; Mon, 20 Jul 1998 12:15:32 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 20 Jul 1998 12:15:32 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Willem Jan Withagen cc: scsi@FreeBSD.ORG Subject: Re: IBM DCAS In-Reply-To: <199807201452.QAA01705@surf.IAE.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 On Mon, 20 Jul 1998, Willem Jan Withagen wrote: > In article you write: > >On Sun, 19 Jul 1998, Stefan Esser wrote: > > > >> On 1998-07-12 17:30 -0500, Chris Dillon wrote: > >> > > Negotiations may be started by both the drive or host adapter > >> > > at any time. But except for IBM, most vendors leave it up to > >> > > the host system to send the first message (which the driver > >> > > does after receiving the result of an INQUIRY command). > >> > > >> > Ok, makes sense.. I was just wondering. :-) > >> > > >> > And I guess that last part about IBM drives is a GoodThing? > >> > >> It doesn't really matter. The IBM driver have > >> other annoying firmware features (e.g. can't > >> deal with a "start motor" command in certain > >> situation where it could be considered a NOP), > >> and they sometimes drop the number of tagged > >> commands they can deal with for no apparent > >> reason. But I'm still thinking that the DDRS > >> is a rather good buy, currently ;-) > > > >I thought that tag problem was only with certain Quantum drives. :-) > >Well, these are DCAS drives, and have worked without a single hitch so > >far, but I wouldn't exactly say I put them under any major stress. > >Knock on wood. > > I currently run a rack of DCAS on an adaptec 2940UW without much of > a problem (until last night, which is most likely a temperature problem) > > (ahc0:14:0): "IBM DCAS-34330W S61A" > > I've created several CCD's and I'm trying to pound on them using bonnie, > iozone, and likes. > > Like I said, they ran for 4 days hammering without trouble, until > the summer started here in Holland. And my garage/office started to heat up. > > Now I've asked IBM what the latest firmware release for these drives was. > But untill now I've only received dumb, std answers. > Well, if you find a new firmware release because of some problem, please let me know. My controller every time at boot (and FreeBSD, at install-time), reports geometry problems and that "This will not work in OS other than DOS", and, well, it works just fine. :-) Flipping the "Support for drives >1GB" option and various other options didn't help, and I'm thinking maybe the drives themselves are reporting something odd. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://www.freebsd.org) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 20 14:54:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23120 for freebsd-scsi-outgoing; Mon, 20 Jul 1998 14:54:32 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from digi.digiware.nl (gtw.digiware.nl [194.151.72.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23109 for ; Mon, 20 Jul 1998 14:54:24 -0700 (PDT) (envelope-from wjw@digi.digiware.nl) Received: by digi.digiware.nl (8.8.7/1.63) id VAA16546; Mon, 20 Jul 1998 21:53:17 GMT From: wjw@digi.digiware.nl (Willem Jan Withagen) Message-Id: <199807202153.VAA16546@digi.digiware.nl> Subject: AHC errors under load. To: scsi@FreeBSD.ORG Date: Mon, 20 Jul 1998 23:53:17 +0200 (CEST) Reply-To: wjw@digiware.nl X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I got the message below, some more junk, and then the AHC resets the bus. But the system is still up and running. First time I eve see this. Can anybody explain what happened? Thanx, --WjW ----- Forwarded message from Charlie Root ----- hobby kernel log messages: > sd2(ahc0:9:0): data overrun of 16777215 bytes detected in Data-Out phase. Tag == 0x9. Forcing a retry. > sd2(ahc0:9:0): Have seen Data Phase. Length = 65536. NumSGs = 15. > sg[0] - Addr 0x3326000 : Length 4096 > sg[1] - Addr 0x627000 : Length 8192 > sg[2] - Addr 0x3ea9000 : Length 4096 > sg[3] - Addr 0x3baa000 : Length 4096 > sg[4] - Addr 0x206b000 : Length 4096 > sg[5] - Addr 0x242c000 : Length 4096 > sg[6] - Addr 0x396d000 : Length 4096 > sg[7] - Addr 0x262e000 : Length 4096 > sg[8] - Addr 0x12ef000 : Length 4096 > sg[9] - Addr 0x21b0000 : Length 4096 > sg[10] - Addr 0x2971000 : Length 4096 > sg[11] - Addr 0x16b2000 : Length 4096 > sg[12] - Addr 0x2833000 : Length 4096 > sg[13] - Addr 0x2f34000 : Length 4096 > sg[14] - Addr 0x33b5000 : Length 4096 > sd2(ahc0:9:0): data overrun of 16777215 bytes detected in Data-Out phase. Tag == 0x9. Forcing a retry. > sd2(ahc0:9:0): Haven't seen Data Phase. Length = 65536. NumSGs = 15. > sg[0] - Addr 0x3326000 : Length 4096 > sg[1] - Addr 0x627000 : Length 8192 > sg[2] - Addr 0x3ea9000 : Length 4096 > sg[3] - Addr 0x3baa000 : Length 4096 > sg[4] - Addr 0x206b000 : Length 4096 > sg[5] - Addr 0x242c000 : Length 4096 > sg[6] - Addr 0x396d000 : Length 4096 > sg[7] - Addr 0x262e000 : Length 4096 > sg[8] - Addr 0x12ef000 : Length 4096 > sg[9] - Addr 0x21b0000 : Length 4096 > sg[10] - Addr 0x2971000 : Length 4096 > sg[11] - Addr 0x16b2000 : Length 4096 > sg[12] - Addr 0x2833000 : Length 4096 > sg[13] - Addr 0x2f34000 : Length 4096 > sg[14] - Addr 0x33b5000 : Length 4096 ----- End of forwarded message from Charlie Root ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 20 15:52:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05049 for freebsd-scsi-outgoing; Mon, 20 Jul 1998 15:52:42 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05034 for ; Mon, 20 Jul 1998 15:52:40 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id RAA10908; Mon, 20 Jul 1998 17:52:23 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id RAA07193; Mon, 20 Jul 1998 17:52:23 -0500 (CDT) Message-ID: <19980720175223.53615@mcs.net> Date: Mon, 20 Jul 1998 17:52:23 -0500 From: Karl Denninger To: wjw@digiware.nl Cc: scsi@FreeBSD.ORG Subject: Re: AHC errors under load. References: <199807202153.VAA16546@digi.digiware.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807202153.VAA16546@digi.digiware.nl>; from Willem Jan Withagen on Mon, Jul 20, 1998 at 11:53:17PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is VERY bad. You now have trash in at least one file (if you're lucky), or a wrecked directory structure (if you're unlucky). Find the cause. Like immediately. Termination problems can cause this problem, and it should be treated with EXTREME severity. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Mon, Jul 20, 1998 at 11:53:17PM +0200, Willem Jan Withagen wrote: > > I got the message below, some more junk, and then the AHC resets the bus. > But the system is still up and running. > First time I eve see this. > Can anybody explain what happened? > > Thanx, > --WjW > > ----- Forwarded message from Charlie Root ----- > > hobby kernel log messages: > > sd2(ahc0:9:0): data overrun of 16777215 bytes detected in Data-Out phase. Tag == 0x9. Forcing a retry. > > sd2(ahc0:9:0): Have seen Data Phase. Length = 65536. NumSGs = 15. > > sg[0] - Addr 0x3326000 : Length 4096 > > sg[1] - Addr 0x627000 : Length 8192 > > sg[2] - Addr 0x3ea9000 : Length 4096 > > sg[3] - Addr 0x3baa000 : Length 4096 > > sg[4] - Addr 0x206b000 : Length 4096 > > sg[5] - Addr 0x242c000 : Length 4096 > > sg[6] - Addr 0x396d000 : Length 4096 > > sg[7] - Addr 0x262e000 : Length 4096 > > sg[8] - Addr 0x12ef000 : Length 4096 > > sg[9] - Addr 0x21b0000 : Length 4096 > > sg[10] - Addr 0x2971000 : Length 4096 > > sg[11] - Addr 0x16b2000 : Length 4096 > > sg[12] - Addr 0x2833000 : Length 4096 > > sg[13] - Addr 0x2f34000 : Length 4096 > > sg[14] - Addr 0x33b5000 : Length 4096 > > sd2(ahc0:9:0): data overrun of 16777215 bytes detected in Data-Out phase. Tag == 0x9. Forcing a retry. > > sd2(ahc0:9:0): Haven't seen Data Phase. Length = 65536. NumSGs = 15. > > sg[0] - Addr 0x3326000 : Length 4096 > > sg[1] - Addr 0x627000 : Length 8192 > > sg[2] - Addr 0x3ea9000 : Length 4096 > > sg[3] - Addr 0x3baa000 : Length 4096 > > sg[4] - Addr 0x206b000 : Length 4096 > > sg[5] - Addr 0x242c000 : Length 4096 > > sg[6] - Addr 0x396d000 : Length 4096 > > sg[7] - Addr 0x262e000 : Length 4096 > > sg[8] - Addr 0x12ef000 : Length 4096 > > sg[9] - Addr 0x21b0000 : Length 4096 > > sg[10] - Addr 0x2971000 : Length 4096 > > sg[11] - Addr 0x16b2000 : Length 4096 > > sg[12] - Addr 0x2833000 : Length 4096 > > sg[13] - Addr 0x2f34000 : Length 4096 > > sg[14] - Addr 0x33b5000 : Length 4096 > ----- End of forwarded message from Charlie Root ----- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 20 19:38:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21171 for freebsd-scsi-outgoing; Mon, 20 Jul 1998 19:38:45 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from maui.net (maui.net [207.175.210.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21160 for ; Mon, 20 Jul 1998 19:38:42 -0700 (PDT) (envelope-from langfod@maui.net) Received: from mx2.maui.net (www.maui.net [207.175.210.4]) by maui.net (8.8.7/8.8.5) with ESMTP id QAA18437 for ; Mon, 20 Jul 1998 16:38:24 -1000 (HST) From: David Langford Received: (from langfod@localhost) by mx2.maui.net (8.8.8/8.8.5) id QAA22983 for scsi@freebsd.org; Mon, 20 Jul 1998 16:38:24 -1000 (HST) Message-Id: <199807210238.QAA22983@mx2.maui.net> Subject: what this SCSI error? To: scsi@FreeBSD.ORG Date: Mon, 20 Jul 1998 16:38:22 -1000 (HST) X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can someone shed some light what the following errors point to? Since these two drive are in a CCD array things are not happy. Thank you, -David Langford langfod@maui.net ... sd1(ahc1:8:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 sd1(ahc1:8:0): Queueing an Abort SCB sd1(ahc1:8:0): Abort Message Sent sd1(ahc1:8:0): SCB 0 - Abort Tag Completed. sd1(ahc1:8:0): no longer in timeout sd1(ahc1:8:0): data overrun of 8186 bytes detected in Data-Out phase. Tag == 0x0. Forcing a retry. sd1(ahc1:8:0): Have seen Data Phase. Length = 8192. NumSGs = 2. ... sd2(ahc2:8:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 sd2(ahc2:8:0): Queueing an Abort SCB sd2(ahc2:8:0): Abort Message Sent sd2(ahc2:8:0): SCB 3 - Abort Tag Completed. sd2(ahc2:8:0): no longer in timeout sd2(ahc2:8:0): data overrun of 4 bytes detected in Data-In phase. Tag == 0x3. Forcing a retry. sd2(ahc2:8:0): Have seen Data Phase. Length = 8192. NumSGs = 1. sd2(ahc2:8:0): data overrun of 8197 bytes detected in Data-In phase. Tag == 0x3. Forcing a retry. ... Device info: Probing for devices on PCI bus 1: ahc1 rev 0 int a irq 9 on pci1:4:0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16 SCBs ahc1: target 8 Tagged Queuing Device (ahc1:8:0): "SEAGATE ST34501W 0018" type 0 fixed SCSI 2 sd1(ahc1:8:0): Direct-Access 4339MB (8887200 512 byte sectors) sd1(ahc1:8:0): with 6576 cyls, 8 heads, and an average 168 sectors/track ahc2 rev 0 int a irq 11 on pci1:5:0 ahc2: aic7880 Wide Channel B, SCSI Id=7, 16 SCBs ahc2: target 8 Tagged Queuing Device (ahc2:8:0): "SEAGATE ST34501W 0018" type 0 fixed SCSI 2 sd2(ahc2:8:0): Direct-Access 4339MB (8887200 512 byte sectors) sd2(ahc2:8:0): with 6576 cyls, 8 heads, and an average 168 sectors/track To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 21 00:21:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29139 for freebsd-scsi-outgoing; Tue, 21 Jul 1998 00:21:57 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29131 for ; Tue, 21 Jul 1998 00:21:53 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl1.philips.com with ESMTP id JAA19198 for ; Tue, 21 Jul 1998 09:21:28 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id JAA15599 for ; Tue, 21 Jul 1998 09:21:27 +0200 (MET DST) Received: (qmail 4793 invoked by uid 666); 21 Jul 1998 07:19:15 -0000 Message-ID: <19980721091915.B1891@mpn.cp.philips.com> Date: Tue, 21 Jul 1998 09:19:15 +0200 From: Jos Backus To: freebsd-scsi@FreeBSD.ORG Subject: CAM build trouble on -stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I'm using the latest 2.2CAM-19980716-SNAP.diffs patch. The patch applies almost cleanly to yesterday's -stable: ``camcontrol'' needs to be added to the SUBDIR definition in /usr/src/sbin/Makefile and mt.c needs some manual tweaking. bilbo:/usr/src# ls -l **/*.rej -rw-r--r-- 1 root bin 751 Jul 20 17:07 release/Makefile.rej -rw-r--r-- 1 root bin 911 Jul 20 17:07 sbin/Makefile.rej -rw-r--r-- 1 root bin 3266 Jul 20 17:07 usr.bin/mt/mt.c.rej However, when trying to build a kernel, I am seeing the following: cc -c -O -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I../.. -I../../../include -DAHC_TAGENABLE -DCOMPAT_43 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL ../../cam/scsi/scsi_target.c In file included from ../../cam/scsi/scsi_target.c:45: ../../cam/cam_periph.h:108: warning: `struct devstat' declared inside parameter list ../../cam/cam_periph.h:108: warning: its scope is only this definition or declaration, ../../cam/cam_periph.h:108: warning: which is probably not what you want. ../../cam/scsi/scsi_target.c: In function `ptasync': ../../cam/scsi/scsi_target.c:175: warning: passing arg 1 of `cam_alloc_periph' from incompatible pointer type ../../cam/scsi/scsi_target.c:175: warning: passing arg 2 of `cam_alloc_periph' makes pointer from integer without a cast ../../cam/scsi/scsi_target.c:175: warning: passing arg 3 of `cam_alloc_periph' makes pointer from integer without a cast ../../cam/scsi/scsi_target.c:175: incompatible type for argument 5 of `cam_alloc_periph' ../../cam/scsi/scsi_target.c:175: warning: passing arg 6 of `cam_alloc_periph' from incompatible pointer type ../../cam/scsi/scsi_target.c:175: too many arguments to function `cam_alloc_periph' *** Error code 1 Stop. The first warning I fixed by adding sys/devicestat.h to scsi_target.c, but I'm not sure about the other one. Thanks, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 21 04:48:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05209 for freebsd-scsi-outgoing; Tue, 21 Jul 1998 04:48:42 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA05189 for ; Tue, 21 Jul 1998 04:48:27 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id NAA10859; Tue, 21 Jul 1998 13:48:08 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id NAA05663; Tue, 21 Jul 1998 13:48:08 +0200 (MET DST) Date: Tue, 21 Jul 1998 13:48:08 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199807211148.NAA05663@surf.IAE.nl> To: karl@mcs.net Subject: Re: AHC errors under load. X-Newsgroups: list.freebsd.scsi In-Reply-To: <19980720175223.53615@mcs.net> References: <199807202153.VAA16546@digi.digiware.nl> Organization: Internet Access Eindhoven, the Netherlands Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <19980720175223.53615@mcs.net> you write: >This is VERY bad. You now have trash in at least one file (if you're >lucky), or a wrecked directory structure (if you're unlucky). > >Find the cause. > >Like immediately. > >Termination problems can cause this problem, and it should be treated with >EXTREME severity. Well it's not that serious, since I was only running bonnie and iozone on that volume, as part of a stress-test. I guess it failed. You say termination? Could it be funcky firmware? But I'm still wondering what the messages mean?? Is it because a device did not respond? Did the controller forget about things? ..... --WjW >> I got the message below, some more junk, and then the AHC resets the bus. >> But the system is still up and running. >> First time I eve see this. >> Can anybody explain what happened? >> >> hobby kernel log messages: >> > sd2(ahc0:9:0): data overrun of 16777215 bytes detected in Data-Out phase. Tag == 0x9. Forcing a retry. >> > sd2(ahc0:9:0): Have seen Data Phase. Length = 65536. NumSGs = 15. >> > sg[0] - Addr 0x3326000 : Length 4096 >> > sg[1] - Addr 0x627000 : Length 8192 >> > sg[2] - Addr 0x3ea9000 : Length 4096 >> > sg[3] - Addr 0x3baa000 : Length 4096 >> > sg[4] - Addr 0x206b000 : Length 4096 >> > sg[5] - Addr 0x242c000 : Length 4096 >> > sg[6] - Addr 0x396d000 : Length 4096 -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 21 06:58:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23603 for freebsd-scsi-outgoing; Tue, 21 Jul 1998 06:58:27 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23585 for ; Tue, 21 Jul 1998 06:58:20 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id HAA19519; Tue, 21 Jul 1998 07:57:50 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807211357.HAA19519@panzer.plutotech.com> Subject: Re: CAM build trouble on -stable In-Reply-To: <19980721091915.B1891@mpn.cp.philips.com> from Jos Backus at "Jul 21, 98 09:19:15 am" To: Jos.Backus@nl.origin-it.com (Jos Backus) Date: Tue, 21 Jul 1998 07:57:50 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jos Backus wrote... > However, when trying to build a kernel, I am seeing the following: > > cc -c -O -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -nostdinc -I- -I. -I../.. -I../../../include -DAHC_TAGENABLE -DCOMPAT_43 > -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL ../../cam/scsi/scsi_target.c > In file included from ../../cam/scsi/scsi_target.c:45: > ../../cam/cam_periph.h:108: warning: `struct devstat' declared inside > parameter list > ../../cam/cam_periph.h:108: warning: its scope is only this definition or > declaration, > ../../cam/cam_periph.h:108: warning: which is probably not what you want. > ../../cam/scsi/scsi_target.c: In function `ptasync': > ../../cam/scsi/scsi_target.c:175: warning: passing arg 1 of `cam_alloc_periph' > from incompatible pointer type > ../../cam/scsi/scsi_target.c:175: warning: passing arg 2 of `cam_alloc_periph' > makes pointer from integer without a cast > ../../cam/scsi/scsi_target.c:175: warning: passing arg 3 of `cam_alloc_periph' > makes pointer from integer without a cast > ../../cam/scsi/scsi_target.c:175: incompatible type for argument 5 of > `cam_alloc_periph' > ../../cam/scsi/scsi_target.c:175: warning: passing arg 6 of `cam_alloc_periph' > from incompatible pointer type > ../../cam/scsi/scsi_target.c:175: too many arguments to function > `cam_alloc_periph' > *** Error code 1 > > Stop. > > The first warning I fixed by adding sys/devicestat.h to scsi_target.c, but I'm > not sure about the other one. Don't try to build that peripheral driver, it doesn't work. Take 'device pt0' out of your config file, and you should be okay. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 21 07:06:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25448 for freebsd-scsi-outgoing; Tue, 21 Jul 1998 07:06:43 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25437 for ; Tue, 21 Jul 1998 07:06:36 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id JAA14736; Tue, 21 Jul 1998 09:06:18 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id JAA16374; Tue, 21 Jul 1998 09:06:17 -0500 (CDT) Message-ID: <19980721090617.59118@mcs.net> Date: Tue, 21 Jul 1998 09:06:17 -0500 From: Karl Denninger To: Willem Jan Withagen Cc: scsi@FreeBSD.ORG Subject: Re: AHC errors under load. References: <199807202153.VAA16546@digi.digiware.nl> <19980720175223.53615@mcs.net> <199807211148.NAA05663@surf.IAE.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807211148.NAA05663@surf.IAE.nl>; from Willem Jan Withagen on Tue, Jul 21, 1998 at 01:48:08PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 21, 1998 at 01:48:08PM +0200, Willem Jan Withagen wrote: > In article <19980720175223.53615@mcs.net> you write: > >This is VERY bad. You now have trash in at least one file (if you're > >lucky), or a wrecked directory structure (if you're unlucky). > > > >Find the cause. > > > >Like immediately. > > > >Termination problems can cause this problem, and it should be treated with > >EXTREME severity. > > Well it's not that serious, since I was only running bonnie and iozone > on that volume, as part of a stress-test. > I guess it failed. Uh, yeah. > You say termination? Could it be funcky firmware? It could be. It could also be a bad (out of spec) cable, a bad terminator, or a bad device (ie: the data buffers and/or drivers on the device itself or the adapter are defective). > But I'm still wondering what the messages mean?? > Is it because a device did not respond? Did the controller forget about > things? ..... > > --WjW This usually means that the drive did not strobe the data off the bus within the time window allowed, and as such the adapter "overran". SCSI is a clocked-bus architecture operating on rather strict timing requirements. If you do not acknowledge the data that is placed on the bus (indicating that you latched it, and the adapter is now free to release the data lines) this can happen. Now as it turns out this may happen because either (1) the "data is valid" signal never was recognized by the other device, (2) the "data is ACKd" signal never got back to the adapter, (3) the cable is too long, and as a result the signal didn't propagate to the other end in time, or (4) due to a reflection in the cable caused by either improper impedence, bad termination or an excessive "stub" length one or more reflected signals was interpreted as one of the above signals when it really hadn't been presented. What happens in that case is that the adapter and/or device gets confused, and you get this kind of error. The BITCH is that on a non-CAM system, the number of aborted transactions is sometimes unknown. This means that you could miss one or more writes to the disk. I've seen *major* disk corruption come out of this kind of error during testing. CAM fixes a lot of the retry semantics, but I don't think its possible to be *certain* that all the data got where it is supposed to be, and got there intact. SCSI parity is supposed to catch data errors (if you EVER get a parity error on the SCSI bus you have real trouble; find the reason and fix it immediately!) but parity is by definition a single-bit-error detector, and will fail half the time to detect a double-bit (or more) error. If you're seeing these errors there is a possibility that you are also taking undetected data errors and the data on your disk is trash! There is a also note in one of the recent kernel source files that a perculiarity in Rev B chipsets of certain Adaptec products has some kind of problem which can be tickled by code of specific revisions, and that this kind of problem could manifest as a result (it is claimed to be fixed in the most recent code branch). I've seen this error while qualifying disk subsystems before, and generally it means the cables, terminators, and/or drive electronics are not up to snuff. One potential fix (which you probably won't like) is to cut back the transfer rate in the Adapter (you can do this from the "setup" screen which is enterable during the boot sequence; hit CTRL-A when prompted) That is really a hack, as what you're doing by slowing down the bus is increasing the timing window during which an DAV or DACK signal is considered to be valid. If you're trying to run with a cable which is too long but everything else is ok, however, this will usually work - at the cost of some performance. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost > >> I got the message below, some more junk, and then the AHC resets the bus. > >> But the system is still up and running. > >> First time I eve see this. > >> Can anybody explain what happened? > > >> > >> hobby kernel log messages: > >> > sd2(ahc0:9:0): data overrun of 16777215 bytes detected in Data-Out phase. Tag == 0x9. Forcing a retry. > >> > sd2(ahc0:9:0): Have seen Data Phase. Length = 65536. NumSGs = 15. > >> > sg[0] - Addr 0x3326000 : Length 4096 > >> > sg[1] - Addr 0x627000 : Length 8192 > >> > sg[2] - Addr 0x3ea9000 : Length 4096 > >> > sg[3] - Addr 0x3baa000 : Length 4096 > >> > sg[4] - Addr 0x206b000 : Length 4096 > >> > sg[5] - Addr 0x242c000 : Length 4096 > >> > sg[6] - Addr 0x396d000 : Length 4096 > > > -- > Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 > P.O. 928, 5600 AX Eindhoven, The Netherlands > Full Internet connectivity for only fl 12.95 a month. > Call now, and login as 'new'. > > 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 Tue Jul 21 07:30:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01099 for freebsd-scsi-outgoing; Tue, 21 Jul 1998 07:30:29 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01080 for ; Tue, 21 Jul 1998 07:30:21 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl1.philips.com with ESMTP id QAA17096 for ; Tue, 21 Jul 1998 16:29:56 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id QAA16690 for ; Tue, 21 Jul 1998 16:29:55 +0200 (MET DST) Received: (qmail 12669 invoked by uid 666); 21 Jul 1998 14:27:44 -0000 Message-ID: <19980721162744.A12592@mpn.cp.philips.com> Date: Tue, 21 Jul 1998 16:27:44 +0200 From: Jos Backus To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CAM build trouble on -stable References: <19980721091915.B1891@mpn.cp.philips.com> <199807211357.HAA19519@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199807211357.HAA19519@panzer.plutotech.com>; from Kenneth D. Merry on Tue, Jul 21, 1998 at 07:57:50AM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Ken, On Tue, Jul 21, 1998 at 07:57:50AM -0600, Kenneth D. Merry wrote: > Don't try to build that peripheral driver, it doesn't work. Take > 'device pt0' out of your config file, and you should be okay. Yes! That did it, thanks. Btw, even though the README doesn't mention it, I'm using this option (taken from LINT): options SCSI_CAM #We're using CAM in this kernel Is this necessary? I just built and booted a kernel without it and it seems to work fine. Groetjes, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 21 08:04:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07504 for freebsd-scsi-outgoing; Tue, 21 Jul 1998 08:04:00 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07498 for ; Tue, 21 Jul 1998 08:03:57 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id JAA19813; Tue, 21 Jul 1998 09:03:22 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807211503.JAA19813@panzer.plutotech.com> Subject: Re: CAM build trouble on -stable In-Reply-To: <19980721162744.A12592@mpn.cp.philips.com> from Jos Backus at "Jul 21, 98 04:27:44 pm" To: Jos.Backus@nl.origin-it.com (Jos Backus) Date: Tue, 21 Jul 1998 09:03:22 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jos Backus wrote... > Hi Ken, > > On Tue, Jul 21, 1998 at 07:57:50AM -0600, Kenneth D. Merry wrote: > > Don't try to build that peripheral driver, it doesn't work. Take > > 'device pt0' out of your config file, and you should be okay. > > Yes! That did it, thanks. > > Btw, even though the README doesn't mention it, I'm using this option (taken > from LINT): > > options SCSI_CAM #We're using CAM in this kernel > > Is this necessary? I just built and booted a kernel without it and it seems to > work fine. It shouldn't be necessary unless you're running with the QLogic (isp) driver. I think the isp driver is the only one that currently uses that option. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 21 08:38:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12387 for freebsd-scsi-outgoing; Tue, 21 Jul 1998 08:38:07 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12326 for ; Tue, 21 Jul 1998 08:37:56 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id JAA23677; Tue, 21 Jul 1998 09:32:19 -0600 (MDT) Date: Tue, 21 Jul 1998 09:32:19 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807211532.JAA23677@narnia.plutotech.com> To: Jos Backus cc: scsi@FreeBSD.ORG Subject: Re: CAM build trouble on -stable Newsgroups: pluto.freebsd.scsi In-Reply-To: <19980721091915.B1891@mpn.cp.philips.com> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <19980721091915.B1891@mpn.cp.philips.com> you wrote: > > However, when trying to build a kernel, I am seeing the following: The pt driver is not yet supported by CAM. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 21 08:53:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14236 for freebsd-scsi-outgoing; Tue, 21 Jul 1998 08:53:14 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (mjacob@gw100.feral.com [192.67.166.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14213 for ; Tue, 21 Jul 1998 08:53:04 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id IAA07940; Tue, 21 Jul 1998 08:52:29 -0700 Date: Tue, 21 Jul 1998 08:52:29 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@feral-gw To: Jos Backus cc: "Kenneth D. Merry" , freebsd-scsi@FreeBSD.ORG Subject: Re: CAM build trouble on -stable In-Reply-To: <19980721162744.A12592@mpn.cp.philips.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 SCSI_CAM is used so that when some drivers are built they know that the CAM version code should be built. On Tue, 21 Jul 1998, Jos Backus wrote: > Hi Ken, > > On Tue, Jul 21, 1998 at 07:57:50AM -0600, Kenneth D. Merry wrote: > > Don't try to build that peripheral driver, it doesn't work. Take > > 'device pt0' out of your config file, and you should be okay. > > Yes! That did it, thanks. > > Btw, even though the README doesn't mention it, I'm using this option (taken > from LINT): > > options SCSI_CAM #We're using CAM in this kernel > > Is this necessary? I just built and booted a kernel without it and it seems to > work fine. > > Groetjes, > -- > Jos Backus _/ _/_/_/ "Reliability means never > _/ _/ _/ having to say you're sorry." > _/ _/_/_/ -- D. J. Bernstein > _/ _/ _/ _/ > Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; > > 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 Jul 22 00:47:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01200 for freebsd-scsi-outgoing; Wed, 22 Jul 1998 00:47:48 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01172 for ; Wed, 22 Jul 1998 00:47:32 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl1.philips.com with ESMTP id JAA08880 for ; Wed, 22 Jul 1998 09:47:08 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id JAA03316 for ; Wed, 22 Jul 1998 09:47:07 +0200 (MET DST) Received: (qmail 16467 invoked by uid 666); 22 Jul 1998 07:44:58 -0000 Message-ID: <19980722094458.A16268@mpn.cp.philips.com> Date: Wed, 22 Jul 1998 09:44:58 +0200 From: Jos Backus To: freebsd-scsi@FreeBSD.ORG Subject: Re: CAM build trouble on -stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'd like to thank Ken, Matthew and Justin for their speedy response regarding subject (and their work on CAM, of course). Thanks people! Groetjes, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 22 02:30:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA21140 for freebsd-scsi-outgoing; Wed, 22 Jul 1998 02:30:32 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from internal.mail.demon.net (internal.mail.demon.net [193.195.224.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21018 for ; Wed, 22 Jul 1998 02:29:59 -0700 (PDT) (envelope-from kerryw@demon.net) Received: from office.demon.net (office.demon.net [193.195.224.1]) by internal.mail.demon.net with SMTP id KAA13933; Wed, 22 Jul 1998 10:29:30 +0100 (BST) Subject: AHC SCSI errors To: freebsd-scsi@FreeBSD.ORG Date: Wed, 22 Jul 1998 10:29:29 +0100 (BST) From: Kerry Woods X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-ID: <901099770.0027031.0@office.demon.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Using the FreeBSD 2.2CAM-19980716-SNAP, with ahc1 rev 0 int a irq 11 on pci1:4:0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc2 rev 0 int a irq 11 on pci1:5:0 ahc2: aic7880 Wide Channel B, SCSI Id=7, 16/255 SCBs and da1 at ahc1 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 4095MB (8386733 512 byte sectors: 64H 32S/T 4095C) plus five more of the same disks off ahc1 forming a ccd array Problems seen: Jul 21 17:58:04 test /kernel: SEQADDR == 0x8 Jul 21 17:58:04 test /kernel: SSTAT1 == 0xa Jul 21 17:58:04 test /kernel: (da2:ahc1:0:1:0): Queuing a BDR SCB Jul 21 17:58:04 test /kernel: (da2:ahc1:0:1:0): Bus Device Reset Message Sent Jul 21 17:58:04 test /kernel: (da2:ahc1:0:1:0): no longer in timeout, status = 3 4c Jul 21 17:58:04 test /kernel: ahc1: Bus Device Reset Sent. 1 SCBs aborted Jul 21 17:58:12 test /kernel: (da2:ahc1:0:1:0): SCB 0x7c - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Jul 21 17:58:12 test /kernel: SEQADDR == 0xb Jul 21 17:58:12 test /kernel: SSTAT1 == 0xa Jul 21 17:58:12 test /kernel: (da2:ahc1:0:1:0): Queuing a BDR SCB Jul 21 17:58:12 test /kernel: (da2:ahc1:0:1:0): Bus Device Reset Message Sent Jul 21 17:58:12 test /kernel: (da2:ahc1:0:1:0): no longer in timeout, status = 3 4c Seen over various drives and over both controllers when the drives were split between them; option SCB_PAGING is not enabled; Any suggestions appreciated Cheers -- Kerry Woods kerryw@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 22 05:45:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23412 for freebsd-scsi-outgoing; Wed, 22 Jul 1998 05:45:08 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ferda.research.rockwell.cz (ferda.research.rockwell.cz [193.85.154.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23392 for ; Wed, 22 Jul 1998 05:45:00 -0700 (PDT) (envelope-from mira@rockwell.cz) Received: from rockwell.cz (localhost [127.0.0.1]) by ferda.research.rockwell.cz (8.8.8/8.8.8) with ESMTP id OAA01944 for ; Wed, 22 Jul 1998 14:47:33 GMT (envelope-from mira@rockwell.cz) Message-ID: <35B5FB85.D63E2228@rockwell.cz> Date: Wed, 22 Jul 1998 14:47:33 +0000 From: Miroslav Kes Organization: Rockwell Automation Ltd., Research Center Prague X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE i386) MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: running 2940U2W with Ultra2 disks Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I want to report (ugh, finaly) succesfull use of CAM on a box with AHA 2940U2W and Seagate Barracuda Ultra2 disks. See the dmesg dump for details bellow. I have one question concerning the information shown by the disklabel command. ferda:/root# disklabel -r da2 # /dev/rda2c: type: SCSI disk: da2s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 1106 sectors/unit: 17783240 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 17783240 0 unused 0 0 # (Cyl. 0 - 1106*) e: 17783240 0 4.2BSD 0 0 0 # (Cyl. 0 - 1106*) Some values like rpm shown by disklabel do not match the factory values. For example the rpm here is 3600 and the disk documantation says 7200. Number of cylinders is 1106 vs 7520. I'm not experienced enough to see whether these inconsistencies are something I should be worry about or not. Thanks Mira ----------------------------------------------------------------------- ferda:/root#dmesg Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.6-STABLE #0: Thu Jul 16 10:22:54 GMT 1998 root@ferda.research.rockwell.cz:/usr/src/sys/compile/LOCAL CPU: Pentium II (267.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80f9ff real memory = 67108864 (65536K bytes) avail memory = 63365120 (61880K bytes) Probing for devices on PCI bus 0: chip0 rev 3 on pci0:0:0 chip1 rev 3 on pci0:1:0 chip2 rev 1 on pci0:7:0 chip3 rev 1 on pci0:7:1 chip4 rev 1 int d irq 11 on pci0:7:2 chip5 rev 1 on pci0:7:3 ahc0 rev 0 int a irq 10 on pci0:14:0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 32/255 SCBs vga0 rev 154 on pci0:16:0 Probing for devices on PCI bus 1: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 5 on isa ed0: address 00:40:05:11:fe:12, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 flags 0x1 on motherboard npx0: INT 16 interface cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI2 device da3: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) cd1 at ahc0 bus 0 target 5 lun 1 cd1: Removable CD-ROM SCSI2 device cd1: 10.0MB/s transfers (10.0MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI2 device da2: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 2157MB (4419464 512 byte sectors: 255H 63S/T 275C) cd2 at ahc0 bus 0 target 5 lun 2 cd2: Removable CD-ROM SCSI2 device cd2: 10.0MB/s transfers (10.0MHz, offset 15) cd2: Attempt to query device size failed: NOT READY, Medium not present cd3 at ahc0 bus 0 target 5 lun 3 cd3: Removable CD-ROM SCSI2 device cd3: 10.0MB/s transfers (10.0MHz, offset 15) cd3: Attempt to query device size failed: NOT READY, Medium not present cd4 at ahc0 bus 0 target 5 lun 4 cd4: Removable CD-ROM SCSI2 device cd4: 10.0MB/s transfers (10.0MHz, offset 15) cd4: Attempt to query device size failed: NOT READY, Medium not present To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 22 13:03:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13800 for freebsd-scsi-outgoing; Wed, 22 Jul 1998 13:03:09 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13744 for ; Wed, 22 Jul 1998 13:02:56 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id NAA28497; Wed, 22 Jul 1998 13:57:14 -0600 (MDT) Date: Wed, 22 Jul 1998 13:57:14 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807221957.NAA28497@narnia.plutotech.com> To: Kerry Woods cc: scsi@FreeBSD.ORG Subject: Re: AHC SCSI errors Newsgroups: pluto.freebsd.scsi In-Reply-To: <901099770.0027031.0@office.demon.net> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <901099770.0027031.0@office.demon.net> you wrote: > Hi > > Using the FreeBSD 2.2CAM-19980716-SNAP, with > > ahc1 rev 0 int a irq 11 on pci1:4:0 > ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > ahc2 rev 0 int a irq 11 on pci1:5:0 > ahc2: aic7880 Wide Channel B, SCSI Id=7, 16/255 SCBs > > and > da1 at ahc1 bus 0 target 0 lun 0 > da1: Fixed Direct Access SCSI2 device > da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled > da1: 4095MB (8386733 512 byte sectors: 64H 32S/T 4095C) > > plus five more of the same disks off ahc1 forming a ccd array Did you see any messages showing the tag count being reduced? > Jul 21 17:58:04 test /kernel: SEQADDR == 0x8 > Jul 21 17:58:04 test /kernel: SSTAT1 == 0xa > Jul 21 17:58:04 test /kernel: (da2:ahc1:0:1:0): Queuing a BDR SCB > Jul 21 17:58:04 test /kernel: (da2:ahc1:0:1:0): Bus Device Reset Message Sent > Jul 21 17:58:04 test /kernel: (da2:ahc1:0:1:0): no longer in timeout, status = 3 This usually indicates a drive firmware bug. Essentially the adaptec sent the drive a command that didn't come back after 10 whole seconds. You can verify this with a SCSI bus trace. You should probably contact Seagate and see if there is newer firmware available for these drives. > Seen over various drives and over both controllers when the drives were > split between them; option SCB_PAGING is not enabled; SCB_PAGING is enabled as it is no longer an option under CAM. You should also ensure that you use AHC_ALLOW_MEMIO if your motherboard supports it (most do). -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 22 13:08:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14805 for freebsd-scsi-outgoing; Wed, 22 Jul 1998 13:08:51 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from bryggen.bgnett.no (root@bryggen.bgnett.no [194.54.96.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14752 for ; Wed, 22 Jul 1998 13:08:33 -0700 (PDT) (envelope-from erikhb@bgnett.no) Received: from bgnett.no (ti21a96-0170.dialup.online.no [130.67.198.170]) by bryggen.bgnett.no (8.8.8/8.8.5/brage2.1) with ESMTP id UAA09061; Wed, 22 Jul 1998 20:07:42 GMT Message-ID: <35B646BA.655E2B19@bgnett.no> Date: Wed, 22 Jul 1998 22:08:26 +0200 From: Erik Bakke Organization: Habatech AS X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Kerry Woods CC: freebsd-scsi@FreeBSD.ORG Subject: Re: AHC SCSI errors References: <901099770.0027031.0@office.demon.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kerry Woods wrote: > > Problems seen: > > Jul 21 17:58:04 test /kernel: SEQADDR == 0x8 > Jul 21 17:58:04 test /kernel: SSTAT1 == 0xa > Jul 21 17:58:04 test /kernel: (da2:ahc1:0:1:0): Queuing a BDR SCB > Jul 21 17:58:04 test /kernel: (da2:ahc1:0:1:0): Bus Device Reset Message Sent > Jul 21 17:58:04 test /kernel: (da2:ahc1:0:1:0): no longer in timeout, status = 3 > 4c > Jul 21 17:58:04 test /kernel: ahc1: Bus Device Reset Sent. 1 SCBs aborted > Jul 21 17:58:12 test /kernel: (da2:ahc1:0:1:0): SCB 0x7c - timed out while idle, > LASTPHASE == 0x1, SCSISIGI == 0x0 > Jul 21 17:58:12 test /kernel: SEQADDR == 0xb > Jul 21 17:58:12 test /kernel: SSTAT1 == 0xa > Jul 21 17:58:12 test /kernel: (da2:ahc1:0:1:0): Queuing a BDR SCB > Jul 21 17:58:12 test /kernel: (da2:ahc1:0:1:0): Bus Device Reset Message Sent > Jul 21 17:58:12 test /kernel: (da2:ahc1:0:1:0): no longer in timeout, status = 3 > 4c > > Seen over various drives and over both controllers when the drives were > split between them; option SCB_PAGING is not enabled; > This also shows up on my computer, running 3.0-CURRENT cvsup as of 18. jul. 98 and CAM. Equipment in use: Adaptec 2940U2W and 1 Seagate Cheetah 34502LW U2W drive. --- Erik H. Bakke Habatech AS erikhb@bgnett.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 22 14:01:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23496 for freebsd-scsi-outgoing; Wed, 22 Jul 1998 14:01:39 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23491 for ; Wed, 22 Jul 1998 14:01:38 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.8) with SMTP id OAA23045; Wed, 22 Jul 1998 14:00:35 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Wed, 22 Jul 1998 14:00:35 -0700 (PDT) From: Chris Timmons To: Kerry Woods cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AHC SCSI errors In-Reply-To: <901099770.0027031.0@office.demon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I saw this too (I'm running the may CAM snapshot on -stable.) This disk is a quantum atlas-ii which has slightly old firmware which Justin has already warned us about. I also had a seagate go offline and never come back (until the power was reset) during backups the other night. I am getting ready to build the more recent CAM and will see if that helps... -Chris (da2:ahc1:0:4:0): SCB 0x9 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x8 SSTAT1 == 0xa (da2:ahc1:0:4:0): Queuing a BDR SCB (da2:ahc1:0:4:0): Bus Device Reset Message Sent (da2:ahc1:0:4:0): no longer in timeout, status = 34b ahc1: Bus Device Reset Sent. 23 SCBs aborted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 22 15:53:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13375 for freebsd-scsi-outgoing; Wed, 22 Jul 1998 15:53:13 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13360 for ; Wed, 22 Jul 1998 15:53:09 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id QAA02846; Wed, 22 Jul 1998 16:47:29 -0600 (MDT) Date: Wed, 22 Jul 1998 16:47:29 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807222247.QAA02846@narnia.plutotech.com> To: Erik Bakke cc: scsi@FreeBSD.ORG Subject: Re: AHC SCSI errors Newsgroups: pluto.freebsd.scsi In-Reply-To: <901099770.0027031.0@office.demon.net> <35B646BA.655E2B19@bgnett.no> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Seen over various drives and over both controllers when the drives were >> split between them; option SCB_PAGING is not enabled; >> > > This also shows up on my computer, running 3.0-CURRENT cvsup as of 18. > jul. 98 and CAM. > Equipment in use: > > Adaptec 2940U2W and 1 Seagate Cheetah 34502LW U2W drive. Another possibility that Matthew Jacob brought up is that the drives may be performing thermal recal. The Seageate rep once told us that their newer drives perform recalibration on a per-track basis which only blocks for ~250ms. Perhaps he lied. You can certainly try bumping up the timeout values in the scsi_da driver (try 1 minute) and see if this addresses your problem. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 22 20:01:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22687 for freebsd-scsi-outgoing; Wed, 22 Jul 1998 20:01:08 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from proxy4.ba.best.com (root@proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22678 for ; Wed, 22 Jul 1998 20:01:06 -0700 (PDT) (envelope-from Kurt@Boolean.Net) Received: from Boolean.Net (smx-ca16-57.ix.netcom.com [207.93.148.185]) by proxy4.ba.best.com (8.9.0/8.9.0/best.out) with ESMTP id TAA01198 for ; Wed, 22 Jul 1998 19:59:39 -0700 (PDT) Message-ID: <35B6A49C.D18C43A5@Boolean.Net> Date: Wed, 22 Jul 1998 19:49:00 -0700 From: "Kurt D. Zeilenga" Organization: Net Boolean Incorporated X-Mailer: Mozilla 4.05 [en] (WinNT; U) MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: CAM transfer rates between 0712-SNAP and 0716-diffs (-current) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm getting half transfer rates on recent CAM builds (-current as of 17 July 12:00 GMT + 0716-diffs or today with 0716 diffs) on two of three nearly identical systems using same kernel. The kernel from 0712 SNAP shows full rates on all devices on all systems. All three systems use the SuperMicro P6DBS Motherboard with integrated AIC-7895 dual UW controller and single disk . The system showing the correct transfer rate has a second unused CPU and a CDROM drive and a PnP modem. The only interesting difference between my config and the GENERIC is the addition of SoftUpdates. Now, what's strange and so far unexplainable is why a dual cpu system with a CDROM drive might be able show full tranfer rates regardless of kernel (generic, mono, smp). Maybe its the modem :-). I noticed that on 0716 the "using left over BIOS settings message" has gone away. Wondering if changes to support Ultra2 controllers might have affected the 7895. Kurt PS: for bandwidth reasons, I've only included relevent portions of my dmesgs below. Complete listings, as well as kernel config files, are availabe for the asking. 0712 SNAP Generic: >ahc0: rev 0x04 int a irq 11 on pci0.14.0 >ahc0: Using left over BIOS settings >ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs >ahc1: rev 0x04 int b irq 11 on pci0.14.1 >ahc1: Using left over BIOS settings >ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs ... >da0 at ahc0 bus 0 target 1 lun 0 >da0: Fixed Direct Access SCSI2 device >da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing >Enabled >da0: 4357MB (8925000 512 byte sectors: 64H 32S/T 4357C) -current + 0716 diffs (BOOLEAN) >ahc0: rev 0x04 int a irq 11 on >pci0.14.0 >ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs >ahc1: rev 0x04 int b irq 11 on >pci0.14.1 >ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs ... >da0 at ahc0 bus 0 target 1 lun 0 >da0: Fixed Direct Access SCSI2 device >da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled >da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) >From SMP kernel (BOOLEAN-SMP) Freeing (NOT implemented) redirected ISA irq 11. ahc0: rev 0x04 int a irq 16 on pci0.14.0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs Freeing (NOT implemented) redirected ISA irq 11. ahc1: rev 0x04 int b irq 16 on pci0.14.1 ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 23 00:50:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01782 for freebsd-scsi-outgoing; Thu, 23 Jul 1998 00:50:39 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ether.ether.online.sh.cn ([202.96.211.193]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA01761 for ; Thu, 23 Jul 1998 00:50:30 -0700 (PDT) (envelope-from paulk@ether.online.sh.cn) Received: from jinbo (202.120.100.126) by ether.ether.online.sh.cn (EMWAC SMTPRS 0.81) with SMTP id ; Thu, 23 Jul 1998 10:42:00 +0800 Message-ID: <003101bdb5e3$404f89c0$c201a8c0@jinbo.ecust.edu.cn> Reply-To: "Paul King" From: "Paul King" To: Subject: Mylex DAC 960 Driver Date: Thu, 23 Jul 1998 10:39:49 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3007.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3007.0 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mylex DAC 960 driver for Linux (beta) is avaliable. Is there any plan of DAC960 driver for FreeBSD. Regards. -Paul King To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 23 09:10:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10214 for freebsd-scsi-outgoing; Thu, 23 Jul 1998 09:10:25 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (mjacob@gw100.feral.com [192.67.166.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10080 for ; Thu, 23 Jul 1998 09:10:11 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id JAA13311; Thu, 23 Jul 1998 09:01:37 -0700 Date: Thu, 23 Jul 1998 09:01:37 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@feral-gw To: Paul King cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Mylex DAC 960 Driver In-Reply-To: <003101bdb5e3$404f89c0$c201a8c0@jinbo.ecust.edu.cn> 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 Yes. I'm for sure going to attempt it for NetBSD. I may not get to it until September at the current snail's pace of all my committments. On Thu, 23 Jul 1998, Paul King wrote: > Mylex DAC 960 driver for Linux (beta) is avaliable. > Is there any plan of DAC960 driver for FreeBSD. > > Regards. > > -Paul King > > > 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 Jul 23 12:24:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13631 for freebsd-scsi-outgoing; Thu, 23 Jul 1998 12:24:21 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from bryggen.bgnett.no (root@bryggen.bgnett.no [194.54.96.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13562 for ; Thu, 23 Jul 1998 12:23:50 -0700 (PDT) (envelope-from erikhb@bgnett.no) Received: from bgnett.no (ti21a96-0312.dialup.online.no [130.67.199.56]) by bryggen.bgnett.no (8.8.8/8.8.5/brage2.1) with ESMTP id TAA03874; Thu, 23 Jul 1998 19:23:09 GMT Message-ID: <35B78DCF.F021F9A3@bgnett.no> Date: Thu, 23 Jul 1998 21:23:59 +0200 From: Erik Bakke Organization: Habatech AS X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: "Justin T. Gibbs" CC: scsi@FreeBSD.ORG Subject: Re: AHC SCSI errors References: <199807222247.QAA02846@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs wrote: > > > Another possibility that Matthew Jacob brought up is that the drives > may be performing thermal recal. The Seageate rep once told us that > their newer drives perform recalibration on a per-track basis which > only blocks for ~250ms. Perhaps he lied. You can certainly try > bumping up the timeout values in the scsi_da driver (try 1 minute) and > see if this addresses your problem. > I compiled a new kernel today, with the timeout set to 120 seconds, but the problem persists. For each SCSI ID that is inquired at boot it gives me 5 errors and moves on to the next ID. When it has scanned all the IDs it continues to boot normally. However, both the SCSI BIOS and other OS's are able to use the drive without problems, so it seems to me that the problem lies somewhere within the CAM subsystem. I have too little experience with CAM to tell for sure, though. I'll try one of the boot floppies with CAM-enabled kernels and see what happens. Thanks for the help so far, anyway. --- Erik H. Bakke Habatech AS erikhb@bgnett.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 23 13:07:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23000 for freebsd-scsi-outgoing; Thu, 23 Jul 1998 13:07:34 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22982 for ; Thu, 23 Jul 1998 13:07:27 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id OAA23160; Thu, 23 Jul 1998 14:06:56 -0600 (MDT) Message-Id: <199807232006.OAA23160@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Erik Bakke cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: AHC SCSI errors In-reply-to: Your message of "Thu, 23 Jul 1998 21:23:59 +0200." <35B78DCF.F021F9A3@bgnett.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Jul 1998 14:01:44 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Another possibility that Matthew Jacob brought up is that the drives >> may be performing thermal recal. The Seageate rep once told us that >> their newer drives perform recalibration on a per-track basis which >> only blocks for ~250ms. Perhaps he lied. You can certainly try >> bumping up the timeout values in the scsi_da driver (try 1 minute) and >> see if this addresses your problem. >> >I compiled a new kernel today, with the timeout set to 120 seconds, but >the problem persists. For each SCSI ID that is inquired at boot it >gives me 5 errors and moves on to the next ID. When it has scanned all >the IDs it continues to boot normally. So this only occurs at boot? Can you provide a dmesg output that contains the errors? It almost sounds like the drive doesn't appreciate multi-lun probing. You wouldn't happen to have a Rev B. aic7880 would you? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 23 17:32:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03522 for freebsd-scsi-outgoing; Thu, 23 Jul 1998 17:32:10 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from marvin.albury.net.au (marvin.albury.NET.AU [203.15.244.108]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03484 for ; Thu, 23 Jul 1998 17:32:04 -0700 (PDT) (envelope-from josh2@marvin.albury.net.au) Received: (from josh2@localhost) by marvin.albury.net.au (8.8.7/8.8.8) id KAA06290 for freebsd-scsi@FreeBSD.ORG; Fri, 24 Jul 1998 10:33:12 +1000 (EST) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 24 Jul 1998 10:12:35 +1000 (EST) From: Josh To: freebsd-scsi@FreeBSD.ORG Subject: cam patch- cant buildworld :-( HELP. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there. I am trying to get a mother board with an AIC-7895 on board controller working. As you know I need to use cam to achieve this. However I got the latest cam patch, 2.2CAM-19980716-SNAP.diffs, and cvsuped on the 23 Jul and tryed to buildworld. I didnt work. The last bit of the build is shown below. HELP. PLEASE! I am currently trying 2.2.6-RELEASE and 2.2CAM-19980712-SNAP.diffs I HOPE this works or one of you who knows a lot more than me have a bright idea. Josh -------------------------------------------------------------------------- cc -nostdinc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -o msgs msgs.o -lte rmcap gzip -c /usr/src/usr.bin/msgs/msgs.1 > msgs.1.gz ===> usr.bin/mt cc -nostdinc -O -pipe -I/usr/src/usr.bin/mt/../../sys -I/usr/obj/usr/src/tmp/u sr/include -c /usr/src/usr.bin/mt/mt.c cc -nostdinc -O -pipe -I/usr/src/usr.bin/mt/../../sys -I/usr/obj/usr/src/tmp/u sr/include -o mt mt.o mt.o: Undefined symbol `_stringtocomp' referenced from text segment *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. bash-2.01# ------------------------------------------------------------------ ---------------------------------- E-Mail: Josh Date: 24-Jul-98 Time: 10:12:35 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 24 05:49:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA00784 for freebsd-scsi-outgoing; Fri, 24 Jul 1998 05:49:22 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from garlic.acadiau.ca (root@garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA00778 for ; Fri, 24 Jul 1998 05:49:19 -0700 (PDT) (envelope-from marc@acadiau.ca) Received: from iceberg (iceberg [131.162.2.91]) by garlic.acadiau.ca (8.8.5/8.8.5) with SMTP id JAA07798 for ; Fri, 24 Jul 1998 09:48:50 -0300 (ADT) Date: Fri, 24 Jul 1998 09:48:50 -0300 (ADT) From: Marc Fournier X-Sender: marc@iceberg To: freebsd-scsi@FreeBSD.ORG Subject: newest CAM driver... 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 Ack... Just updated my kernel using the newest CAM drivers, and, upon reboot, got hit with, which just doesn't give a "warm fuzzy feeling". I did a 'cvs checkout' of the source tree as of July 16th, applied the diff and then did a 'cvs update -APd' to bring the source tree up to date (today, July 24th), with the only conflict being in isa_device.h ... (probe1:ahc1:0:0:3): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x18d SSTAT1 == 0xa (probe1:ahc1:0:0:3): Queuing a BDR SCB (probe1:ahc1:0:0:3): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x18d SSTAT1 == 0xa (probe1:ahc1:0:0:3): no longer in timeout, status = 34b ahc1: Issued Channel A Bus Reset. 2 SCBs aborted (probe1:ahc1:0:0:3): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x18d SSTAT1 == 0xa (probe1:ahc1:0:0:3): Queuing a BDR SCB (probe1:ahc1:0:0:3): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x18d SSTAT1 == 0xa (probe1:ahc1:0:0:3): no longer in timeout, status = 34b ahc1: Issued Channel A Bus Reset. 2 SCBs aborted cda0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) hda1 at ahc1 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI2 device da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) da2 at ahc1 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI2 device da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) anging root device to da0s1a (da0:ahc0:0:0:0): SCB 0xe - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x18d SSTAT1 == 0xa (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): SCB 0xe - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x18d SSTAT1 == 0xa (da0:ahc0:0:0:0): no longer in timeout, status = 34b Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 24 09:05:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04028 for freebsd-scsi-outgoing; Fri, 24 Jul 1998 09:05:32 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03982 for ; Fri, 24 Jul 1998 09:05:15 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id KAA07708; Fri, 24 Jul 1998 10:04:22 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807241604.KAA07708@panzer.plutotech.com> Subject: Re: cam patch- cant buildworld :-( HELP. In-Reply-To: from Josh at "Jul 24, 98 10:12:35 am" To: josh2@marvin.albury.net.au (Josh) Date: Fri, 24 Jul 1998 10:04:22 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Josh wrote... > Hi there. > I am trying to get a mother board with an AIC-7895 on board controller > working. As you know I need to use cam to achieve this. However I got the > latest cam patch, 2.2CAM-19980716-SNAP.diffs, and cvsuped on the 23 Jul and > tryed to buildworld. I didnt work. The last bit of the build is shown below. > > HELP. PLEASE! > I am currently trying 2.2.6-RELEASE and 2.2CAM-19980712-SNAP.diffs > I HOPE this works or one of you who knows a lot more than me > have a bright idea. Patching 2.2.6 with the snapshot from July 12th is even less likely to work than patching -stable from July 23rd with the snapshot from the 16th. The best thing to do is read the README. In the readme file, it says: =========================================================================== [ ... ] On a FreeBSD-current/FreeBSD-stable system from ~0200 PDT on 19980716 # Apply the patches. All patches include "src" in them, so # assuming your src tree is in "/usr": # for 2.2-stable systems: cd /usr patch -p0 < zcat 2.2CAM-19980716-SNAP.diffs.gz [ ... ] =========================================================================== If you apply the patches to -stable from approximately that time, the patch should apply okay. If you apply the patches to -stable from an earlier or later time, they probably won't work correctly. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 24 09:43:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11646 for freebsd-scsi-outgoing; Fri, 24 Jul 1998 09:43:28 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from bryggen.bgnett.no (root@bryggen.bgnett.no [194.54.96.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11601 for ; Fri, 24 Jul 1998 09:43:08 -0700 (PDT) (envelope-from erikhb@bgnett.no) Received: from bgnett.no (ti21a96-0502.dialup.online.no [130.67.199.246]) by bryggen.bgnett.no (8.8.8/8.8.5/brage2.1) with ESMTP id QAA03167; Fri, 24 Jul 1998 16:42:33 GMT Message-ID: <35B8B9B3.6017E3F9@bgnett.no> Date: Fri, 24 Jul 1998 18:43:31 +0200 From: Erik Bakke Organization: Habatech AS X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: "Justin T. Gibbs" CC: scsi@FreeBSD.ORG Subject: Re: AHC SCSI errors References: <199807232006.OAA23160@pluto.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >I compiled a new kernel today, with the timeout set to 120 seconds, but > >the problem persists. For each SCSI ID that is inquired at boot it > >gives me 5 errors and moves on to the next ID. When it has scanned all > >the IDs it continues to boot normally. > > So this only occurs at boot? Can you provide a dmesg output that contains > the errors? It almost sounds like the drive doesn't appreciate multi-lun > probing. > > You wouldn't happen to have a Rev B. aic7880 would you? > The controller on these cards is a 7890 chip. It seems like the dmesg output is truncated, so I am including what I have access to: c0:0:11:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 6 SCBs aborted (probe10:ahc0:0:11:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe10:ahc0:0:11:0): SCB 10: Immediate reset. Flags = 0x4040 (probe10:ahc0:0:11:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 6 SCBs aborted (probe10:ahc0:0:11:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe10:ahc0:0:11:0): SCB 5: Immediate reset. Flags = 0x4040 (probe10:ahc0:0:11:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 6 SCBs aborted (probe10:ahc0:0:11:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe10:ahc0:0:11:0): SCB 10: Immediate reset. Flags = 0x4040 (probe10:ahc0:0:11:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 6 SCBs aborted (probe10:ahc0:0:11:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe10:ahc0:0:11:0): SCB 5: Immediate reset. Flags = 0x4040 (probe10:ahc0:0:11:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 6 SCBs aborted (probe11:ahc0:0:12:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe11:ahc0:0:12:0): SCB 10: Immediate reset. Flags = 0x4040 (probe11:ahc0:0:12:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 5 SCBs aborted (probe11:ahc0:0:12:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe11:ahc0:0:12:0): SCB 6: Immediate reset. Flags = 0x4040 (probe11:ahc0:0:12:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 5 SCBs aborted (probe11:ahc0:0:12:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe11:ahc0:0:12:0): SCB 10: Immediate reset. Flags = 0x4040 (probe11:ahc0:0:12:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 5 SCBs aborted (probe11:ahc0:0:12:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe11:ahc0:0:12:0): SCB 6: Immediate reset. Flags = 0x4040 (probe11:ahc0:0:12:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 5 SCBs aborted (probe11:ahc0:0:12:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe11:ahc0:0:12:0): SCB 10: Immediate reset. Flags = 0x4040 (probe11:ahc0:0:12:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 5 SCBs aborted (probe12:ahc0:0:13:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe12:ahc0:0:13:0): SCB 6: Immediate reset. Flags = 0x4040 (probe12:ahc0:0:13:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 4 SCBs aborted (probe12:ahc0:0:13:0): SCB 0x9 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe12:ahc0:0:13:0): SCB 9: Immediate reset. Flags = 0x4040 (probe12:ahc0:0:13:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 4 SCBs aborted (probe12:ahc0:0:13:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe12:ahc0:0:13:0): SCB 6: Immediate reset. Flags = 0x4040 (probe12:ahc0:0:13:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 4 SCBs aborted (probe12:ahc0:0:13:0): SCB 0x9 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe12:ahc0:0:13:0): SCB 9: Immediate reset. Flags = 0x4040 (probe12:ahc0:0:13:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 4 SCBs aborted (probe12:ahc0:0:13:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe12:ahc0:0:13:0): SCB 6: Immediate reset. Flags = 0x4040 (probe12:ahc0:0:13:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 4 SCBs aborted (probe13:ahc0:0:14:0): SCB 0x9 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe13:ahc0:0:14:0): SCB 9: Immediate reset. Flags = 0x4040 (probe13:ahc0:0:14:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 3 SCBs aborted (probe13:ahc0:0:14:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe13:ahc0:0:14:0): SCB 7: Immediate reset. Flags = 0x4040 (probe13:ahc0:0:14:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 3 SCBs aborted (probe13:ahc0:0:14:0): SCB 0x9 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe13:ahc0:0:14:0): SCB 9: Immediate reset. Flags = 0x4040 (probe13:ahc0:0:14:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 3 SCBs aborted (probe13:ahc0:0:14:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe13:ahc0:0:14:0): SCB 7: Immediate reset. Flags = 0x4040 (probe13:ahc0:0:14:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 3 SCBs aborted (probe13:ahc0:0:14:0): SCB 0x9 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe13:ahc0:0:14:0): SCB 9: Immediate reset. Flags = 0x4040 (probe13:ahc0:0:14:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 3 SCBs aborted (probe14:ahc0:0:15:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe14:ahc0:0:15:0): SCB 7: Immediate reset. Flags = 0x4040 (probe14:ahc0:0:15:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe14:ahc0:0:15:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe14:ahc0:0:15:0): SCB 8: Immediate reset. Flags = 0x4040 (probe14:ahc0:0:15:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe14:ahc0:0:15:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe14:ahc0:0:15:0): SCB 7: Immediate reset. Flags = 0x4040 (probe14:ahc0:0:15:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe14:ahc0:0:15:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe14:ahc0:0:15:0): SCB 8: Immediate reset. Flags = 0x4040 (probe14:ahc0:0:15:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe14:ahc0:0:15:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe14:ahc0:0:15:0): SCB 7: Immediate reset. Flags = 0x4040 (probe14:ahc0:0:15:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe0:ahc0:0:0:0): SCB 8: Immediate reset. Flags = 0x4040 (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe0:ahc0:0:0:0): SCB 8: Immediate reset. Flags = 0x4040 (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe0:ahc0:0:0:0): SCB 8: Immediate reset. Flags = 0x4040 (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x2 SSTAT1 == 0x0 (probe0:ahc0:0:0:0): SCB 8: Immediate reset. Flags = 0x4040 (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted changing root device to wd0s1a Hope this is of any help. --- Erik H. Bakke Habatech AS erikhb@bgnett.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message