From owner-freebsd-scsi Sun Jan 10 05:40:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21676 for freebsd-scsi-outgoing; Sun, 10 Jan 1999 05:40:32 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA21654; Sun, 10 Jan 1999 05:40:28 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id NAA00662; Sun, 10 Jan 1999 13:11:47 GMT Date: Sun, 10 Jan 1999 13:11:47 +0000 (GMT) From: Doug Rabson To: Stephen Palmer cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, son@teaser.fr, Jos M Alcaide , gp@oitunix.oit.umass.edu Subject: Re: Request fo help with Zip Drive on vpo0 in -current In-Reply-To: <19990110075223.12171.qmail@www0d.netaddress.usa.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 10 Jan 1999, Stephen Palmer wrote: > Sorry if this is redundant, but I haven't seen any new posts on this > since 1/1/99. I am still showing this problem (vpo0 detected, da0 and scbus > not detected) with sources current as of 1/9/99 5PM CST. > > Any help would be appreciated. (I'm almost to the point of bowing down to > whomever can solve this! I wish I could code as well as report :-( ) I made a fix for this yesterday and Nick comitted it. Try a new version of vpo.c. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jan 10 10:37:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25232 for freebsd-scsi-outgoing; Sun, 10 Jan 1999 10:37:24 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25227 for ; Sun, 10 Jan 1999 10:37:22 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA19977; Sat, 9 Jan 1999 11:45:18 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdA19975; Sat Jan 9 19:45:13 1999 Date: Sat, 9 Jan 1999 11:45:10 -0800 (PST) From: Julian Elischer To: Gabor Zahemszky cc: scsi@FreeBSD.ORG Subject: Re: SCSI problem In-Reply-To: <199901090011.BAA31756@neumann.cs.elte.hu> 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 Hi! On Sat, 9 Jan 1999, Gabor Zahemszky wrote: > Hi, Julian! > > If I remember well, you wrote some of the FreeBSD's SCSI-driver. So here is > an interesting (for me, of course) problem: The scsi stuff I wrote is the old stuff now being replaced :-) > > I've got an ASUS SC200 PCI-bus SCSI-controller. It has NCR810 on it. On > it, there is a Plextor PX-4XCE CD-ROM, with id of 2. Worked well. Now, > I've bought a 2MB _wide_ SCSI disc, an IBM DCAS-32160W. I've got an 50->68 > adapter, so I can put it on the normal cable (as id 6). But if I boot with > these hardwares, the SCSI BIOS cannot identify them, and the FreeBSD boot will > generate so many errors, that it'll be about an hour to boot, and non of them > identified by it. Maybe it's a wrong card, or something. So i got for a > while an Adaptec 2840 - another _non-wide_ PCI-adapter. Only the CD -> OK. > Only the disk -> OK. Both of them: the same problem: neither the card's > BIOS, nor the BSD driver cannot identify the CD and the disc, and the boot > generates a ton of errors, and it's about an hour to boot. > is the disk SCAM compatible (check docs) id the CD SCAM compatible? SCAM is a scheme where the IDs are dynamically assigned. But all devices must be compatible with it. Most modern PCs try use SCAM these days in the BIOS. > So my questions: > can I put wide and normal peripherals on a normal controller? > If it's yes, can I put it onto my SC200, or I need to change the adapter (or > the disc)? > What on Earth can generates this problem? Unfortunatly I got out of the SCSI business before WIDE devices became popular, so I know very little about it.. My suggestion (In fact I will forward it) is to ask scsi@freebsd.org > > And another one: I've got an old SyQuest removable disc. On it there are > some defects. I tried to verify it with the Adaptec's BIOS utility, and it > remapped some tracks. After it I tried to format. The format failed. After > the failed format, I cannot make anything with it. Some hints? (I'm an > analphabet for SCSI, so pardon my silly questions!) I think you mean illiterate.. :-) > I really cannot help you much with this.. If the SCSI BIOS cannot handle this device it may be a bad sign.. have you tried a different cartridge? Maybe others have more information on this device.. BTW, 3.0 or 2.2.x? > Bye, Gabor > > PS: the most trivial answers are: > yes, terminators are OK > yes, both of them has parity enabled > yes, the IDs are different > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jan 10 13:31:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15915 for freebsd-scsi-outgoing; Sun, 10 Jan 1999 13:31:43 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.ruhrgebiet.individual.net (in-ruhr.ruhr.de [141.39.224.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15907 for ; Sun, 10 Jan 1999 13:31:40 -0800 (PST) (envelope-from robsch@robkaos.ruhr.de) Received: from robkaos.ruhr.de (admin@localhost) by mail.ruhrgebiet.individual.net (8.8.5-r-beta/8.8.5) with UUCP id WAA23109 for freebsd.org!freebsd-scsi; Sun, 10 Jan 1999 22:23:36 +0100 (MET) Received: by robkaos.ruhr.de (Smail-3.2 1996-Jul-4 #1) id ; Sun, 10 Jan 1999 22:18:15 +0100 (CET) Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Can't get UMAX scanner working in 3.0-current To: freebsd-scsi@FreeBSD.ORG Date: Sun, 10 Jan 1999 22:18:15 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL28 (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'm trying to get my UMAX Astra 1200S scanner working under FreeBSD-3-0-current. I rebuilt the sane-1.00 package from the ports directory of ftp.cdrom.com. Compiling and installing worked fine (well the GTK stuff did not compile correctly, because of the version chaos of GTK). So I tried to use scanimage. I edited dll.conf and umax.conf, symlinked /dev/scanner -> /dev/pass6. (The scanner is recognized as the pass trough device number 6 during device probing). Unfortunately, all I get when running scanimage is 'Invalid argument' :-( The exact command is: scanimage -d umax:/dev/scanner . The scanner worked with earlier (pre-CAM) versions of 3-0-current. And, yes, it works under NT. So I hope the hardware isn't broken :-) Did I forget to configure something? BTW, the CD-burner Yamaha 4216S works fine with its pass-trough-device. Has someone a scanner running with a CAM-kernel? TIA for any help Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jan 10 15:28:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28420 for freebsd-scsi-outgoing; Sun, 10 Jan 1999 15:28:22 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28414 for ; Sun, 10 Jan 1999 15:28:20 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id IAA07478; Mon, 11 Jan 1999 08:27:47 +0900 (JST) Message-ID: <36992436.47CBA1B@newsguy.com> Date: Mon, 11 Jan 1999 07:05:42 +0900 From: "Daniel C. Sobral" Reply-To: dcs@newsguy.com X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Mylex Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Which Mylex SCSI controllers are supported by FreeBSD? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jan 10 18:51:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19895 for freebsd-scsi-outgoing; Sun, 10 Jan 1999 18:51:50 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19887 for ; Sun, 10 Jan 1999 18:51:47 -0800 (PST) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id VAA18827; Sun, 10 Jan 1999 21:51:14 -0500 (EST) To: robsch@robkaos.ruhr.de (Robert Schien), freebsd-scsi@FreeBSD.ORG Subject: Re: Can't get UMAX scanner working in 3.0-current References: From: Cory Kempf Date: 10 Jan 1999 21:51:13 -0500 In-Reply-To: robsch@robkaos.ruhr.de's message of "Sun, 10 Jan 1999 22:18:15 +0100 (CET)" Message-ID: Lines: 27 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org robsch@robkaos.ruhr.de (Robert Schien) writes: > I'm trying to get my UMAX Astra 1200S scanner working under > FreeBSD-3-0-current. I rebuilt the sane-1.00 package from the > ports directory of ftp.cdrom.com. > Unfortunately, all I get when running scanimage is 'Invalid argument' :-( > The exact command is: scanimage -d umax:/dev/scanner . CAM is broken, you need to use /dev/pass6. Something may be broken in the 1.0 SANE... it doesn't seem to work on my system, although 0.74 + my CAM mods does. I haven't had time to figure out what broke though. Let me know if you need the 0.74 mods. +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 11 10:53:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11192 for freebsd-scsi-outgoing; Mon, 11 Jan 1999 10:53:09 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11187 for ; Mon, 11 Jan 1999 10:53:08 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0zzmS2-000I0NC; Mon, 11 Jan 1999 13:52:34 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: CAM SA Problem (fwd) To: scsi@FreeBSD.ORG Date: Mon, 11 Jan 1999 13:52:34 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM916080753-12369-1_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ELM916080753-12369-1_ Content-Type: message/rfc822 Content-Disposition: inline Content-Description: Forwarded message from Tom Torrance Content-Transfer-Encoding: 7bit Return-Path: Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0zzkYb-000I0NC; Mon, 11 Jan 1999 11:51:13 -0500 (EST) Message-Id: From: freebsd (Tom Torrance) Subject: Re: CAM SA Problem In-Reply-To: from Tom Torrance at home at "Jan 11, 1999 11: 0:37 am" To: tom@tomqnx.com (Tom Torrance at home) Date: Mon, 11 Jan 1999 11:51:13 -0500 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 370 I forgot to mention - the device does NOT get reset during the boot (no tape positioning takes place). 'camcontrol reset 0:6:0' results in: camcontrol: CAMIOCOMMAND ioctl failed: Invalid argument The messages I used to get at open/close time under CAM were related to the inability of the drive to support locking/unlocking of the tape cartridge in the drive. Tom --ELM916080753-12369-1_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 11 11:22:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15132 for freebsd-scsi-outgoing; Mon, 11 Jan 1999 11:22:46 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15115 for ; Mon, 11 Jan 1999 11:22:43 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id LAA19159; Mon, 11 Jan 1999 11:22:03 -0800 Date: Mon, 11 Jan 1999 11:22:03 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Tom Torrance at home cc: scsi@FreeBSD.ORG Subject: Re: CAM SA Problem (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It turns out, btw, that there's an open PR on this model (which I have no access to hardware for) o [1996/10/04] kern/1724 mjacob HP colorado T4000S tape drive hangs syste Which may or may not continue to be broken for you. Let me know what your experiences with setting blocksize to 512 do for you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 11 12:24:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24514 for freebsd-scsi-outgoing; Mon, 11 Jan 1999 12:24:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24509 for ; Mon, 11 Jan 1999 12:24:40 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0zznQP-000I0NC; Mon, 11 Jan 1999 14:54:57 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: CAM SA Problem (fwd) In-Reply-To: from Matthew Jacob at "Jan 11, 1999 11:22: 3 am" To: mjacob@feral.com Date: Mon, 11 Jan 1999 14:54:57 -0500 (EST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM916084497-12603-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ELM916084497-12603-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > It turns out, btw, that there's an open PR on this model (which I have no > access to hardware for) > > o [1996/10/04] kern/1724 mjacob HP colorado T4000S tape drive hangs syste > It works for me under 2.2-stable using an AHA-2740, and until very recently under CAM using the ASUS-875. Under CAM, there were "ignored" messages: ILLEGAL REQUEST asc:24,0 on open, and ILLEGAL REQUEST asc:26,0 on close (or equivalent - they might have been slightly different). > > Which may or may not continue to be broken for you. > > Let me know what your experiences with setting blocksize to 512 do for > you. The 'mt -f /dev/nrst0 blocksize 512' fails. Curiously, the debug output (attached) finishes by complaining that it was unable to set variable blocksize. Regards, Tom P.S. I did not mean to insult you! I know d****d well that you tested the code to exaustion on the drives available to you. It just doesn't work at all for me on my drive... What stings, is that it DID :-} --ELM916084497-12603-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=dmesg Content-Description: Results of mt blocksize command Content-Transfer-Encoding: 7bit [ Extraneous stuff deleted ] Linux-ELF exec handler installed Waiting 15 seconds for SCSI devices to settle ncr0: restart (scsi reset). (probe5:ncr0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe5:ncr0:0:5:0): ILLEGAL REQUEST asc:24,0 (probe5:ncr0:0:5:0): Invalid field in CDB sks:c0,1 (probe6:ncr0:0:6:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe6:ncr0:0:6:0): ILLEGAL REQUEST asc:24,0 (probe6:ncr0:0:6:0): Invalid field in CDB sa0 at ncr0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number JKA5580002KB3M pass0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled pass1 at ncr0 bus 0 target 5 lun 0 pass1: Removable CD-ROM SCSI-2 device pass1: 3.300MB/s transfers pass2 at ncr0 bus 0 target 6 lun 0 pass2: Removable Sequential Access SCSI-2 device pass2: 3.300MB/s transfers da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number JKA5580002KB3M da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [176780 x 2048 byte records] [ Stuff Deleted ] [ Results of attempting 'mt -f /dev/nrsa0 blocksize 512 follow ] (xpt0:ncr0:0:6:0): debugging flags now 8 (sa0:ncr0:0:6:0): RESERVE(06). CDB: 16 0 0 0 0 0 (sa0:ncr0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (sa0:ncr0:0:6:0): READ BLOCK LIMITS. CDB: 5 0 0 0 0 0 (sa0:ncr0:0:6:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 (sa0:ncr0:0:6:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:24,0 (sa0:ncr0:0:6:0): Invalid field in CDB (sa0:ncr0:0:6:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 (sa0:ncr0:0:6:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 (sa0:ncr0:0:6:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ncr0:0:6:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:26,0 (sa0:ncr0:0:6:0): Invalid field in parameter list (sa0:ncr0:0:6:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ncr0:0:6:0): unable to set variable blocksize --ELM916084497-12603-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 11 12:46:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27392 for freebsd-scsi-outgoing; Mon, 11 Jan 1999 12:46:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27382 for ; Mon, 11 Jan 1999 12:46:07 -0800 (PST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id VAA05214; Mon, 11 Jan 1999 21:44:26 +0100 (MET) Received: (from ticso@localhost) by cicely7.cicely.de (8.9.0/8.9.0) id VAA02559; Mon, 11 Jan 1999 21:44:10 +0100 (CET) Message-ID: <19990111214410.60469@cicely.de> Date: Mon, 11 Jan 1999 21:44:10 +0100 From: Bernd Walter To: Cory Kempf , Robert Schien , freebsd-scsi@FreeBSD.ORG Subject: Re: Can't get UMAX scanner working in 3.0-current References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Cory Kempf on Sun, Jan 10, 1999 at 09:51:13PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Jan 10, 1999 at 09:51:13PM -0500, Cory Kempf wrote: > robsch@robkaos.ruhr.de (Robert Schien) writes: > > > I'm trying to get my UMAX Astra 1200S scanner working under > > FreeBSD-3-0-current. I rebuilt the sane-1.00 package from the > > ports directory of ftp.cdrom.com. > > > Unfortunately, all I get when running scanimage is 'Invalid argument' :-( > > The exact command is: scanimage -d umax:/dev/scanner . > > CAM is broken, you need to use /dev/pass6. > > Something may be broken in the 1.0 SANE... it doesn't seem to work on > my system, although 0.74 + my CAM mods does. I haven't had time to > figure out what broke though. > > Let me know if you need the 0.74 mods. I'm using a HP Scanner with CAM and sane 1.0 build from ports scanimage -d hp:/dev/pt0 You need to include pt0 device to your kernel config. It's working realy fine -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 11 15:09:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15972 for freebsd-scsi-outgoing; Mon, 11 Jan 1999 15:09:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15953; Mon, 11 Jan 1999 15:09:29 -0800 (PST) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.8.8/8.8.5) id RAA12571; Mon, 11 Jan 1999 17:08:51 -0600 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 11 Jan 1999 17:08:51 -0600 (CST) Reply-To: greg@uswest.net Organization: US WEST !NTERACT From: Greg Rowe To: freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Fatal Trap Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a Tyan mb dual 400mhz system I'm building that's getting repeatable crashes under disk load. This didn't occur until I compiled an SMP kernel. I'm running -current as of last Friday and the system has 512mb of memory and 4 drives on Adaptec controllers (1 - 4gig on one controller and 3 - 9gig on the other). Untarring a file will interestingly enough crash the system at around the same appoximate place in the tar image every time, although it's crashed while building ports also. The system drops to the debugger with the following: Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid=1; lapic.id = 01000000(I've also seen it for cpuid0) fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xf0216357 stack pointer = 0x10:0xff618ce8 frame pointer = 0x10:0xff618d0c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 243 (tar) interrupt mask = net tty bio cam <-SMP:XXX kernel: type 12 trap, code 0 Stopped at generic_bzero+0xf: repe stosl %es:(%edi) Any ideas as to what to look for ? Thanks. Greg Greg Rowe US WEST - Internet Service Operations "The telephone, for those of you who have forgotten, was a commonly used communications technology in the days before electronic mail. They're still easy to find in most large cities." -- Nathaniel Borenstein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 11 22:21:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02828 for freebsd-scsi-outgoing; Mon, 11 Jan 1999 22:21:48 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02822 for ; Mon, 11 Jan 1999 22:21:44 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id PAA04646; Tue, 12 Jan 1999 15:21:09 +0900 (JST) Message-ID: <369AE9C6.F17426AF@newsguy.com> Date: Tue, 12 Jan 1999 15:20:54 +0900 From: "Daniel C. Sobral" Reply-To: dcs@newsguy.com X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: low-end Fast Wide SCSI? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Anyone has any tips about low-end Fast Wide SCSI controllers for FreeBSD? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 11 23:25:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09916 for freebsd-scsi-outgoing; Mon, 11 Jan 1999 23:25:13 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from quark.ChrisBowman.com (crbowman.erols.com [209.122.47.155]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09910 for ; Mon, 11 Jan 1999 23:25:08 -0800 (PST) (envelope-from crb@ChrisBowman.com) Received: from fermion (fermion.ChrisBowman.com [10.0.1.2]) by quark.ChrisBowman.com (8.8.8/8.8.8) with SMTP id CAA06235; Tue, 12 Jan 1999 02:32:33 -0500 (EST) (envelope-from crb@ChrisBowman.com) Message-Id: <199901120732.CAA06235@quark.ChrisBowman.com> X-Sender: crb@quark X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 12 Jan 1999 02:22:10 -0500 To: dcs@newsguy.com From: "Christopher R. Bowman" Subject: Re: low-end Fast Wide SCSI? Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: <369AE9C6.F17426AF@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 03:20 PM 1/12/99 +0900, Daniel C. Sobral wrote: >Anyone has any tips about low-end Fast Wide SCSI controllers for >FreeBSD? Symbios based 53c875 controllers should be pretty cheap, my Tekram DC-390F has been rock solid for me on everything from 2.1.5 up until 2.2.8 (I haven't tried with 3.0) Check www.pricewatch.com and www.shopper.com for prices which should be somewhere in the neighborhood of $75. -------- Christopher R. Bowman crb@ChrisBowman.com http://www.ChrisBowman.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 12 00:20:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14754 for freebsd-scsi-outgoing; Tue, 12 Jan 1999 00:20:47 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14748 for ; Tue, 12 Jan 1999 00:20:45 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0zzz3T-000I0SC; Tue, 12 Jan 1999 03:20:03 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: CAM SA Problem (fwd) In-Reply-To: from Matthew Jacob at "Jan 11, 1999 3:14:41 pm" To: mjacob@feral.com Date: Tue, 12 Jan 1999 03:20:02 -0500 (EST) Cc: tom@tomqnx.com, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM916129202-14971-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ELM916129202-14971-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Initial results with quirks commented out. It appears that 1) it kinda basicly functions (verbosely) 2) some commands get issued twice when debugging on 3) I can't prove it, but I believe they are repeated also while debugging is off. 4) camcontrol debug off doesn't log change 5) mt status gives inaccurate results. Please let me know what I should test next... Regards, Tom --ELM916129202-14971-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=dmesg Content-Description: Quirks commented out Content-Transfer-Encoding: 7bit Linux-ELF exec handler installed Waiting 15 seconds for SCSI devices to settle ncr0: restart (scsi reset). (probe5:ncr0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe5:ncr0:0:5:0): ILLEGAL REQUEST asc:24,0 (probe5:ncr0:0:5:0): Invalid field in CDB sks:c0,1 (probe6:ncr0:0:6:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe6:ncr0:0:6:0): ILLEGAL REQUEST asc:24,0 (probe6:ncr0:0:6:0): Invalid field in CDB sa0 at ncr0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number JKA5580002KB3M pass0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled pass1 at ncr0 bus 0 target 5 lun 0 pass1: Removable CD-ROM SCSI-2 device pass1: 3.300MB/s transfers pass2 at ncr0 bus 0 target 6 lun 0 pass2: Removable Sequential Access SCSI-2 device pass2: 3.300MB/s transfers da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number JKA5580002KB3M da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [176780 x 2048 byte records] Considering MFS root f/s. No MFS image available as root f/s. Considering FFS root f/s. changing root device to da0s2a da0s1: type 0x6, start 63, end = 1025891, size 1025829 : OK da0s2: type 0xa5, start 1025892, end = 8885267, size 7859376 : OK wd0s1: type 0xb, start 63, end = 6152894, size 6152832 : OK wd0s2: type 0x82, start 6152895, end = 8353799, size 2200905 : OK ffs_mountfs: superblock updated for soft updates OSS/FreeBSD loading, address = f08ded58 (xpt0:ncr0:0:6:0): debugging flags now 8 [ mt status ] (sa0:ncr0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code [ mt rewind ] (sa0:ncr0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code (sa0:ncr0:0:6:0): REWIND. CDB: 1 0 0 0 0 0 [ mt fsf 1 ] (sa0:ncr0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code (sa0:ncr0:0:6:0): SPACE. CDB: 11 1 0 0 1 0 (sa0:ncr0:0:6:0): SPACE. CDB: 11 1 0 0 1 0 [ mt rewind ] (sa0:ncr0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code (sa0:ncr0:0:6:0): REWIND. CDB: 1 0 0 0 0 0 [ mt fsf 1 ] (sa0:ncr0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code (sa0:ncr0:0:6:0): SPACE. CDB: 11 1 0 0 1 0 (sa0:ncr0:0:6:0): SPACE. CDB: 11 1 0 0 1 0 [ mt rewind ] (sa0:ncr0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code (sa0:ncr0:0:6:0): REWIND. CDB: 1 0 0 0 0 0 [ debugging turned off - no message logged ] [ mt status ] (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code [ mt fsf 1 ] (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code --ELM916129202-14971-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=status Content-Description: mt status results Content-Transfer-Encoding: 7bit Mode Density Blocksize bpi Compression Current: 0x45 512 bytes 0 unsupported ---------available modes--------- 0: 0x45 512 bytes 0 unsupported 1: 0x45 512 bytes 0 unsupported 2: 0x45 512 bytes 0 unsupported 3: 0x45 512 bytes 0 unsupported --ELM916129202-14971-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 12 00:54:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18742 for freebsd-scsi-outgoing; Tue, 12 Jan 1999 00:54:10 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18737 for ; Tue, 12 Jan 1999 00:54:09 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id AAA22389; Tue, 12 Jan 1999 00:53:29 -0800 Date: Tue, 12 Jan 1999 00:53:29 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Tom Torrance at home cc: scsi@FreeBSD.ORG Subject: Re: CAM SA Problem (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is all pretty wierd. I can't figure out why the prevent/allow is happening twice, nor can I figure out what's happening with the space operation. I *will* say that the current sa driver has retries set for many operations that it shouldn't, in fact, retry (saspace is one of them)- but not for saprevent. In either case, a retry is masking some other error. Try it with camcontol -Ic device which should have saerror dump unconditionally the sense key, asc, etc... Sigh. I was going to try and get this all cleaned up before the code fork this week, but doubt I'll make it. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 12 01:36:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23301 for freebsd-scsi-outgoing; Tue, 12 Jan 1999 01:36:45 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23284; Tue, 12 Jan 1999 01:36:35 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id JAA26451; Tue, 12 Jan 1999 09:35:37 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Tue, 12 Jan 1999 09:32:18 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 12 Jan 1999 09:32:15 +0000 To: greg@uswest.net From: Bob Bishop Subject: Re: Fatal Trap Cc: freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, At 5:08 pm -0600 11/1/99, Greg Rowe wrote: > I have a Tyan mb dual 400mhz system I'm building that's getting repeatable >crashes under disk load. This didn't occur until I compiled an SMP kernel. I'm >running -current as of last Friday and the system has 512mb of memory and 4 >drives on Adaptec controllers (1 - 4gig on one controller and 3 - 9gig on the >other). [etc] What Adaptec controllers, precisely? -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 12 02:46:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00421 for freebsd-scsi-outgoing; Tue, 12 Jan 1999 02:46:45 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00416 for ; Tue, 12 Jan 1999 02:46:43 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m1001Kn-000I0SC; Tue, 12 Jan 1999 05:46:05 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: CAM SA Problem (fwd) In-Reply-To: from Matthew Jacob at "Jan 12, 1999 0:53:29 am" To: mjacob@feral.com Date: Tue, 12 Jan 1999 05:46:05 -0500 (EST) Cc: tom@tomqnx.com, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM916137965-15223-1_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ELM916137965-15223-1_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit I am confused too. I did the following test sequence. camcontrol debug -Ic 0:6:0 mt fsf 1 manually change tape camcontrol debug -Ic 0:6:0 mt fsf 1 manually change tape camcontrol debug -Ic 0:6:0 mt fsf 1 The first tape used was the one from the aborted dump test. It gave very unusual results. The next 2 tests worked fine. Query: Could there be an assumption built in anywhere that a file ends with 2 EOFs? My understanding is that a proper multifile volume looks like: file 1 EOF file 2 EOF last file EOF EOF although headers and trailers (if any) could change that. In any case, mt fsf 1 should search for the one next EOF. Regards, Tom --ELM916137965-15223-1_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=dmesg Content-Description: mt fsf 1 test results Content-Transfer-Encoding: 7bit Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #41: Tue Jan 12 02:24:29 EST 1999 tom@darkstar.tomqnx.com:/usr/src/sys/compile/DARKSTAR Calibrating clock(s) ... TSC clock: 200453060 Hz, i8254 clock: 1193174 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 200453060 Hz CPU: Pentium/P55C (200.45-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x544 Stepping=4 Features=0x8001bf real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002b1000 - 0x03ff5fff, 64245760 bytes (15685 pages) config> pnp 1 0 enable os port0 0x220 port1 0x300 port2 0x388 irq0 10 drq0 3 drq1 5 config> pnp 1 1 enable os port0 0x200 config> pnp 1 2 enable os port0 0x620 port1 0xa20 port2 0xe20 config> config> quit avail memory = 62472192 (61008K bytes) Found BIOS32 Service Directory header at 0xf00f9a20 Entry = 0xf04e0 (0xf00f04e0) Rev = 0 Len = 1 PCI BIOS entry at 0x510 DMI header at 0xf00f52a0 Version 2.0 Table at 0xf52ba, 33 entries, 1044 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000fcf10 Preloaded elf kernel "kernel" at 0xf02a0000. Preloaded userconfig_script "/boot/pnp.config" at 0xf02a009c. pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71008086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x7100, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip0: rev 0x01 on pci0.0.0 found-> vendor=0x8086, dev=0x7110, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x01 on pci0.1.0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000e000, size 4 ide_pci0: rev 0x01 on pci0.1.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 24 from port: 0000e002 ide_pci: ide0:0 has been configured for DMA by BIOS intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000e00a found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=3 map[0]: type 4, range 32, base 0000d800, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x01 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip2: rev 0x01 on pci0.1.3 found-> vendor=0x1000, dev=0x000f, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base 0000d400, size 8 map[1]: type 1, range 32, base e7000000, size 8 map[2]: type 1, range 32, base e6800000, size 12 ncr0: rev 0x03 int a irq 9 on pci0.10.0 ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM found-> vendor=0x5333, dev=0x8a01, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base e0000000, size 26 vga0: rev 0x01 int a irq 11 on pci0.11.0 Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 CSN 1 Vendor ID: CTL00c1 [0xc1008c0e] Serial 0x1641e094 Comp ID: PNPb02f [0x2fb0d041] PnP: override config for CSN 1 LDN 0 vend_id 0xc1008c0e port 0x0220 0x0300 0x0388 0x0000 irq 10:0 drq 3:5 en 1 PnP: override config for CSN 1 LDN 1 vend_id 0xc1008c0e port 0x0200 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 1 PnP: override config for CSN 1 LDN 2 vend_id 0xc1008c0e port 0x0620 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 1 Called nullpnp_probe with tag 0x00000001, type 0xc1008c0e Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 Probing for devices on the ISA bus: sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x10000, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status b1 03 c8 psm: status b1 03 c8 psm: status b1 03 c8 psm: status 00 00 3c psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface bpf: lp0 attached fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, iordy acd0: drive speed 689KB/sec, 256KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked 1 3C5x9 board(s) on ISA found at 0x210 ep0 at 0x210-0x21f irq 5 on isa ep0: aui/bnc[*BNC*] address 00:60:8c:62:a5:65 bpf: ep0 attached vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xf00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 175592625 bytes/sec bzero() bandwidth = 88409512 bytes/sec joy0 at 0x201 on isa joy0: joystick imasks: bio c008c040, tty c00710b2, net c00710b2 BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. Intel Pentium detected, installing workaround for F00F bug bpf: tun0 attached bpf: sl0 attached bpf: ppp0 attached new masks: bio c008c040, tty c00710b2, net c00710b2 bpf: lo0 attached Linux-ELF exec handler installed Waiting 15 seconds for SCSI devices to settle ncr0: restart (scsi reset). (probe5:ncr0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe5:ncr0:0:5:0): ILLEGAL REQUEST asc:24,0 (probe5:ncr0:0:5:0): Invalid field in CDB sks:c0,1 (probe6:ncr0:0:6:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe6:ncr0:0:6:0): ILLEGAL REQUEST asc:24,0 (probe6:ncr0:0:6:0): Invalid field in CDB sa0 at ncr0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number JKA5580002KB3M pass0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled pass1 at ncr0 bus 0 target 5 lun 0 pass1: Removable CD-ROM SCSI-2 device pass1: 3.300MB/s transfers pass2 at ncr0 bus 0 target 6 lun 0 pass2: Removable Sequential Access SCSI-2 device pass2: 3.300MB/s transfers da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number JKA5580002KB3M da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [176780 x 2048 byte records] Considering MFS root f/s. No MFS image available as root f/s. Considering FFS root f/s. changing root device to da0s2a da0s1: type 0x6, start 63, end = 1025891, size 1025829 : OK da0s2: type 0xa5, start 1025892, end = 8885267, size 7859376 : OK wd0s1: type 0xb, start 63, end = 6152894, size 6152832 : OK wd0s2: type 0x82, start 6152895, end = 8353799, size 2200905 : OK ffs_mountfs: superblock updated for soft updates OSS/FreeBSD loading, address = f08dad58 (xpt0:ncr0:0:6:0): debugging flags now 9 (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): RESERVE(06). CDB: 16 0 0 0 0 0 (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (sa0:ncr0:0:6:0): READ BLOCK LIMITS. CDB: 5 0 0 0 0 0 (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 (sa0:ncr0:0:6:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:24,0 (sa0:ncr0:0:6:0): Invalid field in CDB (sa0:ncr0:0:6:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 (sa0:ncr0:0:6:0): Mode Sense Data= 0x0b 0xb6 0x10 0x08 0x45 0x00 0x00 0x00 0x00 0x00 0x02 0x00 (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 (sa0:ncr0:0:6:0): Mode Sense Data= 0x0b 0xb6 0x10 0x08 0x45 0x00 0x00 0x00 0x00 0x00 0x02 0x00 (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ncr0:0:6:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:26,0 (sa0:ncr0:0:6:0): Invalid field in parameter list (sa0:ncr0:0:6:0): Err22, Mode Select Data= 0x00 0x00 0x10 0x08 0x7f 0x00 0x00 0x00 0x00 0x00 0x00 0x00 (sa0:ncr0:0:6:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 (sa0:ncr0:0:6:0): Mode Sense Data= 0x0b 0xb6 0x10 0x08 0x45 0x00 0x00 0x00 0x00 0x00 0x02 0x00 (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ncr0:0:6:0): Err0, Mode Select Data= 0x00 0x00 0x10 0x08 0x7f 0x00 0x00 0x00 0x00 0x00 0x02 0x00 (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): SPACE. CDB: 11 1 0 0 1 0 (xpt0:ncr0:0:6:0): debugging flags now 9 (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (sa0:ncr0:0:6:0): READ BLOCK LIMITS. CDB: 5 0 0 0 0 0 (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 (sa0:ncr0:0:6:0): Mode Sense Data= 0x0b 0xb6 0x90 0x08 0x45 0x00 0x00 0x00 0x00 0x00 0x02 0x00 (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): SPACE. CDB: 11 1 0 0 1 0 (xpt0:ncr0:0:6:0): debugging flags now 9 (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (sa0:ncr0:0:6:0): READ BLOCK LIMITS. CDB: 5 0 0 0 0 0 (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 (sa0:ncr0:0:6:0): Mode Sense Data= 0x0b 0xb6 0x90 0x08 0x45 0x00 0x00 0x00 0x00 0x00 0x02 0x00 (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code (sa0:ncr0:0:6:0): sastart(sa0:ncr0:0:6:0): SPACE. CDB: 11 1 0 0 1 0 --ELM916137965-15223-1_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 12 06:29:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25763 for freebsd-scsi-outgoing; Tue, 12 Jan 1999 06:29:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA25744; Tue, 12 Jan 1999 06:29:16 -0800 (PST) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.8.8/8.8.5) id IAA13923; Tue, 12 Jan 1999 08:28:01 -0600 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 12 Jan 1999 08:28:01 -0600 (CST) Reply-To: greg@uswest.net Organization: US WEST !NTERACT From: Greg Rowe To: Bob Bishop Subject: Re: Fatal Trap Cc: freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org They are 2940UW's Revision C. I had 2940UW revision E's in, but I replaced them thinking that was the issue. I can build the system with a Generic kernel, single CPU, and do the tar load with no problems, so it appears to be an SMP issue ??? A dmesg output follows: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #1: Mon Jan 11 09:02:31 CST 1999 root@spare2.oss.uswest.net:/usr/src/sys/compile/TAHITI Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II (quarter-micron) (686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff> real memory = 536870912 (524288K bytes) config> quit avail memory = 518963200 (506800K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xf0309000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x02 on pci0.7.3 Freeing (NOT implemented) redirected ISA irq 11. ahc0: rev 0x00 int a irq 16 on pci0.16.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Freeing (NOT implemented) redirected ISA irq 9. ahc1: rev 0x00 int a irq 17 on pci0.17.0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Freeing (NOT implemented) redirected ISA irq 10. vga0: rev 0x01 int a irq 18 on pci0.18. 0 Freeing (NOT implemented) redirected ISA irq 5. fxp0: rev 0x05 int a irq 19 on pci0 .19.0 fxp0: Ethernet address 00:90:27:1d:8e:08 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> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 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 wdc0 not found at 0x1f0 wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 adv0 not found at 0x330 bt0 not found at 0x134 aha0 not found at 0x134 npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da1 at ahc1 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da3 at ahc1 bus 0 target 2 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da2 at ahc1 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) WARNING: / was not properly dismounted (da3:ahc1:0:2:0): tagged openings now 64 (da0:ahc0:0:0:0): tagged openings now 61 (da0:ahc0:0:0:0): tagged openings now 60 (da0:ahc0:0:0:0): tagged openings now 59 (da0:ahc0:0:0:0): tagged openings now 58 (da0:ahc0:0:0:0): tagged openings now 57 (da0:ahc0:0:0:0): tagged openings now 56 (da0:ahc0:0:0:0): tagged openings now 55 (da0:ahc0:0:0:0): tagged openings now 54 (da0:ahc0:0:0:0): tagged openings now 53 (da0:ahc0:0:0:0): tagged openings now 52 (da0:ahc0:0:0:0): tagged openings now 51 (da0:ahc0:0:0:0): tagged openings now 50 (da0:ahc0:0:0:0): tagged openings now 49 (da1:ahc1:0:0:0): tagged openings now 64 (da1:ahc1:0:0:0): tagged openings now 63 (da1:ahc1:0:0:0): tagged openings now 62 (da1:ahc1:0:0:0): tagged openings now 61 (da1:ahc1:0:0:0): tagged openings now 60 (da1:ahc1:0:0:0): tagged openings now 59 (da1:ahc1:0:0:0): tagged openings now 58 (da1:ahc1:0:0:0): tagged openings now 57 (da1:ahc1:0:0:0): tagged openings now 56 (da1:ahc1:0:0:0): tagged openings now 55 (da1:ahc1:0:0:0): tagged openings now 54 (da1:ahc1:0:0:0): tagged openings now 53 (da1:ahc1:0:0:0): tagged openings now 52 (da1:ahc1:0:0:0): tagged openings now 51 (da1:ahc1:0:0:0): tagged openings now 50 (da1:ahc1:0:0:0): tagged openings now 49 On 12-Jan-99 Bob Bishop wrote: > Hi, > > At 5:08 pm -0600 11/1/99, Greg Rowe wrote: >> I have a Tyan mb dual 400mhz system I'm building that's getting repeatable >>crashes under disk load. This didn't occur until I compiled an SMP kernel. >>I'm >>running -current as of last Friday and the system has 512mb of memory and 4 >>drives on Adaptec controllers (1 - 4gig on one controller and 3 - 9gig on the >>other). [etc] > > What Adaptec controllers, precisely? > > > -- > Bob Bishop (0118) 977 4017 international code +44 118 > rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message Greg Rowe US WEST - Internet Service Operations "The telephone, for those of you who have forgotten, was a commonly used communications technology in the days before electronic mail. They're still easy to find in most large cities." -- Nathaniel Borenstein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 12 11:51:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02038 for freebsd-scsi-outgoing; Tue, 12 Jan 1999 11:51:40 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02027; Tue, 12 Jan 1999 11:51:28 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id TAA07388; Tue, 12 Jan 1999 19:50:30 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Tue, 12 Jan 1999 19:42:37 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 12 Jan 1999 19:42:35 +0000 To: greg@uswest.net From: Bob Bishop Subject: Re: Fatal Trap Cc: freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 8:28 am -0600 12/1/99, Greg Rowe wrote: >They are 2940UW's Revision C. I had 2940UW revision E's in, but I replaced >them >thinking that was the issue. I can build the system with a Generic kernel, >single CPU, and do the tar load with no problems, so it appears to be an SMP >issue ??? A dmesg output follows: Some 2940s (but not the UW, IIRC) misbehave with some MP motherboards. http://www.adaptec.com/support might be worth a quick look. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 12 13:54:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16108 for freebsd-scsi-outgoing; Tue, 12 Jan 1999 13:54:53 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gta.gta.com (gta.gta.com [199.120.225.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA16102 for ; Tue, 12 Jan 1999 13:54:51 -0800 (PST) (envelope-from lab@gta.com) Message-Id: <199901122201.RAA07265@gta.gta.com> Received: forwarded by SMTP 1.6.0. Received: (from lab@localhost) by uno.gta.com (8.8.8/8.8.7) id QAA14253 for freebsd-scsi@freebsd.org; Tue, 12 Jan 1999 16:50:25 -0500 (EST) From: "Larry Baird" Date: Tue, 12 Jan 1999 16:50:24 -0500 X-Mailer: Z-Mail (3.0.1 04apr94) To: freebsd-scsi@FreeBSD.ORG Subject: AHA2940U2W and 2.2.8 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well it looks like I made an ordering mistake. I have several systems that I had planned to run 2.2.8 along with Adaptec AHA2940U2W controllers and the corresponding ultra2 hard disks. I now realize that only 3.0 supports this controller using CAM. There used to be a backport of CAM to 2.2 in ftp://ftp.freebsd.org/pub/FreeBSD/cam. This seems to have been moved to ftp://ftp.freebsd.org/pub/FreeBSD/development/cam. But the 2.2 cam boot.flp still expects to find the installation files in the old place. Does anybody have a work around? Thanks in advance, Larry -- ----------------------------------------------------------------------------- Larry Baird Global Technology Associates, Inc. | Orlando, FL Email: lab@gta.com | Tel 407-380-0220 FAX 407-380-6080 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 12 14:31:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20756 for freebsd-scsi-outgoing; Tue, 12 Jan 1999 14:31:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20741 for ; Tue, 12 Jan 1999 14:31:07 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id PAA47630; Tue, 12 Jan 1999 15:30:29 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901122230.PAA47630@panzer.plutotech.com> Subject: Re: AHA2940U2W and 2.2.8 In-Reply-To: <199901122201.RAA07265@gta.gta.com> from Larry Baird at "Jan 12, 99 04:50:24 pm" To: lab@gta.com (Larry Baird) Date: Tue, 12 Jan 1999 15:30:28 -0700 (MST) 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 Larry Baird wrote... > Well it looks like I made an ordering mistake. I have several systems that > I had planned to run 2.2.8 along with Adaptec AHA2940U2W controllers and > the corresponding ultra2 hard disks. I now realize that only 3.0 supports this > controller using CAM. > > There used to be a backport of CAM to 2.2 in > ftp://ftp.freebsd.org/pub/FreeBSD/cam. This seems to have been moved > to ftp://ftp.freebsd.org/pub/FreeBSD/development/cam. But the 2.2 cam > boot.flp still expects to find the installation files in the old place. > > Does anybody have a work around? You should be able to specify the full URL for the location of the distribution. (nope, I don't know the exact sysinstall screen where you'd type that in, it's been a while since I've done an install like that) 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 Jan 12 21:13:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02616 for freebsd-scsi-outgoing; Tue, 12 Jan 1999 21:13:26 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from beast.freibergnet.de (beast.freibergnet.de [194.123.255.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02593 for ; Tue, 12 Jan 1999 21:13:23 -0800 (PST) (envelope-from mw@freibergnet.de) Received: from io.freibergnet.de (io.freibergnet.de [194.123.255.11]) by beast.freibergnet.de (8.8.8/8.8.8) with ESMTP id GAA26721; Wed, 13 Jan 1999 06:12:40 +0100 (CET) (envelope-from mw@freibergnet.de) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901122201.RAA07265@gta.gta.com> Date: Wed, 13 Jan 1999 06:12:32 +0100 (CET) Reply-To: mw@freibergnet.de Organization: FreibergNet Liebscher & Partner Werbeagentur und XLink-PoP Freiberg From: Martin Welk To: Larry Baird Subject: RE: AHA2940U2W and 2.2.8 Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 12-Jan-99 Larry Baird wrote: () Well it looks like I made an ordering mistake. I have several systems () that () I had planned to run 2.2.8 along with Adaptec AHA2940U2W controllers () and () the corresponding ultra2 hard disks. I now realize that only 3.0 () supports this () controller using CAM. () (...) () () Does anybody have a work around? Wait until a 3.0-STABLE tree exists and use FreeBSD 3.0 native. It brings some more advantages and of course CAM. We have it running on three machines with an Asus P2B-S (UW-SCSI onboard) and they work fine. They act as a server machine (1) and desktop machines (2). They donīt have a significant high load yet, but are running steadily and doing this and that, also things like "make buildworld" and compiling ghostscript or postgresql fine... We didnīt experience heavy problems, so simply try if it good enough for your purpose and maybe a 3.0-STABLE will be available meanwhile. Unfortunately, upgrading from 2.2-somewhat or 3.0-RELEASE will definitely make some work, as there are some things you have to look carefully for, especially if you want to use ELF kernels. Perhaps you should read the current mailing list for problems you may run into. You can also run CAM with 2.2, but we havenīt tried that but made good experiences with 3.0-CURRENT in the last months. Perhaps you can put a 3.0-RELEASE on one of your machines, install a base installation, upgrade it and copy that to all of the other machines you are going to buy? Regards, Martin -- FreibergNet Systemhaus GbR Martin Welk * Sales, Support Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781387 Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 13 11:16:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05291 for freebsd-scsi-outgoing; Wed, 13 Jan 1999 11:16:30 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05188 for ; Wed, 13 Jan 1999 11:16:11 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id EAA29406; Thu, 14 Jan 1999 04:15:01 +0900 (JST) Message-ID: <369CF063.3A1F24F3@newsguy.com> Date: Thu, 14 Jan 1999 04:13:39 +0900 From: "Daniel C. Sobral" Reply-To: dcs@newsguy.com X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Mylex Flashpoint LW Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mmmm.... There is some interesting points about this card. "Plug and Play with SCAM Level I compliance". Does this have anything to do with our "CAM"? Also: > All major desktop > operating systems are supported including: Windows 95, > Windows NT, OS/2 Warp, OS/2 2.XX, Windows for Workgroups, > DOS/Windows 3.x, UnixWare, NetWare 3.1X, > 4.X, SCO UNIX, Solaris, Linux Linux? Anyone knows if this is binary-only driver or it actually comes with source code? A friend of mine wants to buy this card. He says that if it is not supported, he will write the driver for it. I'm concerned about the availability of proper documentation if he takes this way. Anyone wanting to share useful insights? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 13 11:24:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07903 for freebsd-scsi-outgoing; Wed, 13 Jan 1999 11:24:46 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from saffron.CS.Berkeley.EDU (saffron.CS.Berkeley.EDU [128.32.33.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07808 for ; Wed, 13 Jan 1999 11:24:24 -0800 (PST) (envelope-from nisha@saffron.CS.Berkeley.EDU) Received: from saffron.CS.Berkeley.EDU (localhost [127.0.0.1]) by saffron.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id KAA15286 for ; Wed, 13 Jan 1999 10:25:24 -0800 (PST) From: Nisha Talagala Message-Id: <199901131825.KAA15286@saffron.CS.Berkeley.EDU> X-Mailer: exmh version 1.6.9 8/22/96 To: scsi@FreeBSD.ORG Subject: Explanations of Disk Error Messages Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Jan 1999 10:25:24 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org There are a set of error message definitions in /usr/src/sys/cam/scsi/scsi_all.c, in the data structure static struct asc_table_entry asc_text[]. (The list is too long to include here) Most of them are mentioned in the SCSI-2 spec. The spec does not explain what disk behavior triggers each message though. Also, a few of the messages in the scsi_all.c code are not defined in the SCSI spec documents that I was able to download. The"Failure Prediction Threshold Exceeded" message is one of the undefined ones. Can anyone let me know what disk behaviour triggers each message? I'm interested in the following 3 messages in particular: - Pheripheral device write fault field replaceable unit - Diagnostic failure: ASCQ=Component ID field replaceable unit - Failure Prediction Threshold Exceeded field replaceable unit thanks, -nisha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 13 12:08:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18608 for freebsd-scsi-outgoing; Wed, 13 Jan 1999 12:08:08 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18599 for ; Wed, 13 Jan 1999 12:08:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00799; Wed, 13 Jan 1999 12:03:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901132003.MAA00799@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nisha Talagala cc: scsi@FreeBSD.ORG Subject: Re: Explanations of Disk Error Messages In-reply-to: Your message of "Wed, 13 Jan 1999 10:25:24 PST." <199901131825.KAA15286@saffron.CS.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Jan 1999 12:03:25 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > There are a set of error message definitions in > > /usr/src/sys/cam/scsi/scsi_all.c, in the data structure > static struct asc_table_entry asc_text[]. (The list is too long to > include here) > > Most of them are mentioned in the SCSI-2 spec. The spec does not > explain what disk behavior triggers each message though. Also, a few of > the messages in the scsi_all.c code are not defined in the SCSI spec > documents that I was able to download. The"Failure Prediction Threshold > Exceeded" message is one of the undefined ones. > > Can anyone let me know what disk behaviour triggers each message? I'm > interested in the following 3 messages in particular: > - Pheripheral device write fault field replaceable unit A hardware failure occured while writing (the FRU indicates the vendor-specific code for the failed component or subsystem). > - Diagnostic failure: ASCQ=Component ID field replaceable unit Diagnostic checks of (component ID) indicated a failure of (FRU). Both values are vendor-specific. > - Failure Prediction Threshold Exceeded field replaceable unit Drive-maintained statistics and tests indicate that (FRU) has an unacceptably high chance of failure. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 13 12:40:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26172 for freebsd-scsi-outgoing; Wed, 13 Jan 1999 12:40:25 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26139 for ; Wed, 13 Jan 1999 12:40:07 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA52513; Wed, 13 Jan 1999 13:38:56 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901132038.NAA52513@panzer.plutotech.com> Subject: Re: Mylex Flashpoint LW In-Reply-To: <369CF063.3A1F24F3@newsguy.com> from "Daniel C. Sobral" at "Jan 14, 99 04:13:39 am" To: dcs@newsguy.com Date: Wed, 13 Jan 1999 13:38:56 -0700 (MST) 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 Daniel C. Sobral wrote... > Mmmm.... There is some interesting points about this card. "Plug and > Play with SCAM Level I compliance". Does this have anything to do > with our "CAM"? No, nothing to do with CAM. SCAM is a protocol that (I think) allows devices to have their SCSI ID's assigned automatically. > Also: > > All major desktop > > operating systems are supported including: Windows 95, > > Windows NT, OS/2 Warp, OS/2 2.XX, Windows for Workgroups, > > DOS/Windows 3.x, UnixWare, NetWare 3.1X, > > 4.X, SCO UNIX, Solaris, Linux > > Linux? Anyone knows if this is binary-only driver or it actually > comes with source code? It comes with source. > A friend of mine wants to buy this card. He says that if it is not > supported, he will write the driver for it. I'm concerned about the > availability of proper documentation if he takes this way. Anyone > wanting to share useful insights? The Mylex/BusLogic Flashpoint cards are not supported under ANY version of FreeBSD. Their MultiMaster cards are supported under FreeBSD, though. Justin has a Flashpoint card, possibly multiple cards, and I believe he intends to write a driver for it. You should be able to get documentation on the Flashpoint cards from Mylex. Really, unless your friend knows something about writing drivers, he would be better off getting a supported card. Adaptec cards are well supported, and would be a safe bet. If he's concerned about price, he can get an Advansys or NCR-based board. 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 Wed Jan 13 15:59:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22697 for freebsd-scsi-outgoing; Wed, 13 Jan 1999 15:59:25 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22573 for ; Wed, 13 Jan 1999 15:59:21 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA53765; Wed, 13 Jan 1999 16:58:06 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901132358.QAA53765@panzer.plutotech.com> Subject: Re: Explanations of Disk Error Messages In-Reply-To: <199901131825.KAA15286@saffron.CS.Berkeley.EDU> from Nisha Talagala at "Jan 13, 99 10:25:24 am" To: nisha@CS.Berkeley.EDU (Nisha Talagala) Date: Wed, 13 Jan 1999 16:58:06 -0700 (MST) Cc: 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 Nisha Talagala wrote... > > > There are a set of error message definitions in > > /usr/src/sys/cam/scsi/scsi_all.c, in the data structure > static struct asc_table_entry asc_text[]. (The list is too long to > include here) > > Most of them are mentioned in the SCSI-2 spec. The spec does not > explain what disk behavior triggers each message though. Also, a few of > the messages in the scsi_all.c code are not defined in the SCSI spec > documents that I was able to download. The"Failure Prediction Threshold > Exceeded" message is one of the undefined ones. > > Can anyone let me know what disk behaviour triggers each message? I'm > interested in the following 3 messages in particular: > - Pheripheral device write fault field replaceable unit > - Diagnostic failure: ASCQ=Component ID field replaceable unit > - Failure Prediction Threshold Exceeded field replaceable unit Mike already explained what those errors mean, so I won't repeat what he said. The ASC/ASCQ text descriptions were taken from a text file, I think on ftp.symbios.com somewhere, that had the latest SCSI-3 draft ASC/ASCQ values and descriptions. So in order to find out what those things mean, you'll probably want to download the SCSI-3 draft specs from: http://www.symbios.com/x3t10/drafts.htm As far as what disk behavior triggers each message, the above messages probably really depend on the disk in question. A full SCSI interface manual for the disk may or may not be helpful in figuring things out. Quantum and Seagate at least have manuals on their web sites for most of their disks. IBM, on the other hand, does not have manuals on its web site. I sent mail to IBM's disk tech support email address about a month ago asking why they don't provide SCSI interface specs for their drives on the web, but they never responded. 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 Thu Jan 14 07:42:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19249 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 07:37:50 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA19243 for ; Thu, 14 Jan 1999 07:37:45 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 81778 invoked by uid 1000); 14 Jan 1999 16:44:10 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 14 Jan 1999 11:44:10 -0500 (EST) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Martin Welk Subject: RE: FreeBSD and RAID controller Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Martin Welk, On 08-Jan-99 you wrote: > Hi everybody, > > I have to set up a FreeBSD machine for a customer that needs a SCSI RAID > subsystem, and internal CD-ROM and 1/4" tape drive. > > Can anybody give a hint for which host adapters I should look? The DPT > adapters seem to look fine, but I donīt know how they work exactly and > if all DPT adapters are supported. The same with the Adaptec RAID > adapters. All SmartRaid and SmartCache generations III and IV work (PCI/EISA, no ISA). The i2o SmartCache V are in development now. Simon > > Thank you in advance. > > Regards, > > Martin > -- > FreibergNet Systemhaus GbR Martin Welk * Sales, > Support > Systemhaus für Daten- und Netzwerktechnik phone +49 3731 > 781387 > Unternehmensgruppe Liebscher & Partner fax +49 3731 > 781377 > D-09599 Freiberg * Am St. Niclas Schacht 13 > http://www.freibergnet.de/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 14 08:20:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24476 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 08:20:16 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dfw-ix1.ix.netcom.com (dfw-ix1.ix.netcom.com [206.214.98.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24471 for ; Thu, 14 Jan 1999 08:20:14 -0800 (PST) (envelope-from phate1@ix.netcom.com) Received: (from smap@localhost) by dfw-ix1.ix.netcom.com (8.8.4/8.8.4) id KAA25880 for ; Thu, 14 Jan 1999 10:19:04 -0600 (CST) Received: from nyc-ny83-53.ix.netcom.com(205.184.128.53) by dfw-ix1.ix.netcom.com via smap (V1.3) id rma025846; Thu Jan 14 10:18:55 1999 Message-ID: <369E19B9.56235557@ix.netcom.com> Date: Thu, 14 Jan 1999 11:22:17 -0500 From: Mike Organization: Integration Soft. X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Freebsd can't find my scsi bus. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org FreeBSD 2.2.7-RELEASE P2-333 Mylex 960SXI SCSI<->SCSI Raid controller. Adaptec 2940U/UW SCSI Controller. Hi, I'm trying to setup a scsi<->scsi raid controller hooked up a 2940uw host scsi controller. I setup the raid controller fine (create an array, initialize the array), boot up the system, then adaptec 2940 detects the array of disks as SCSI ID 0, LUN 0.. But when I boot up freebsd, freebsd doesnt detect ANY disks whatsoever. What can be the problem? Any help on this matter would be greately appreciated, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 14 08:57:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28945 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 08:57:23 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28940 for ; Thu, 14 Jan 1999 08:57:21 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id JAA57190; Thu, 14 Jan 1999 09:55:33 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901141655.JAA57190@panzer.plutotech.com> Subject: Re: Freebsd can't find my scsi bus. In-Reply-To: <369E19B9.56235557@ix.netcom.com> from Mike at "Jan 14, 99 11:22:17 am" To: phate1@ix.netcom.com (Mike) Date: Thu, 14 Jan 1999 09:55:33 -0700 (MST) 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 Mike wrote... > FreeBSD 2.2.7-RELEASE > P2-333 > Mylex 960SXI SCSI<->SCSI Raid controller. > Adaptec 2940U/UW SCSI Controller. > > Hi, > > I'm trying to setup a scsi<->scsi raid controller hooked up a 2940uw > host scsi controller. > > I setup the raid controller fine (create an array, initialize the > array), boot up the system, then adaptec 2940 detects the array of disks > as SCSI ID 0, LUN 0.. > > But when I boot up freebsd, freebsd doesnt detect ANY disks whatsoever. > > What can be the problem? That is a bit odd. The first question is, does FreeBSD detect your 2940? Are you sure the 2940 isn't a 2940 U2W (i.e., an Ultra-2 controller)? Will FreeBSD boot if you put a "normal" disk on the system? How did you install FreeBSD in the first place if it doesn't detect any disks? 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 Thu Jan 14 09:31:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04168 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 09:31:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dfw-ix1.ix.netcom.com (dfw-ix1.ix.netcom.com [206.214.98.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04161 for ; Thu, 14 Jan 1999 09:31:06 -0800 (PST) (envelope-from phate1@ix.netcom.com) Received: (from smap@localhost) by dfw-ix1.ix.netcom.com (8.8.4/8.8.4) id LAA06457; Thu, 14 Jan 1999 11:29:16 -0600 (CST) Received: from nyc-ny71-13.ix.netcom.com(209.109.226.205) by dfw-ix1.ix.netcom.com via smap (V1.3) id rma006422; Thu Jan 14 11:28:46 1999 Message-ID: <369E2A19.7A957A35@ix.netcom.com> Date: Thu, 14 Jan 1999 12:32:09 -0500 From: Mike Organization: Integration Soft. X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: "Kenneth D. Merry" CC: freebsd-scsi@FreeBSD.ORG Subject: Re: Freebsd can't find my scsi bus. References: <199901141655.JAA57190@panzer.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 Keith, thanks for replying. yes, I have a 2940U/UW controller.. Not U2W.. OK, first of all i found interesting, that unlike in other computers (using regular scsi disks) in this one the 2940 occupies 2 IRQ's - #9, #10 shown by the BIOS after startup. Now, when freebsd boots up, all the way at the top, it shows found - Adaptec-- IRQ 9 - no driver assigned Adaptec-- IRQ 10 - no driver assigned Further way down in the probe, it shows aha0 not found at 0x330.. Thanks for your help Mike Kenneth D. Merry wrote: > > Mike wrote... > > FreeBSD 2.2.7-RELEASE > > P2-333 > > Mylex 960SXI SCSI<->SCSI Raid controller. > > Adaptec 2940U/UW SCSI Controller. > > > > Hi, > > > > I'm trying to setup a scsi<->scsi raid controller hooked up a 2940uw > > host scsi controller. > > > > I setup the raid controller fine (create an array, initialize the > > array), boot up the system, then adaptec 2940 detects the array of disks > > as SCSI ID 0, LUN 0.. > > > > But when I boot up freebsd, freebsd doesnt detect ANY disks whatsoever. > > > > What can be the problem? > > That is a bit odd. The first question is, does FreeBSD detect your 2940? > Are you sure the 2940 isn't a 2940 U2W (i.e., an Ultra-2 controller)? > > Will FreeBSD boot if you put a "normal" disk on the system? How did you > install FreeBSD in the first place if it doesn't detect any disks? > > 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 Thu Jan 14 09:45:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06358 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 09:45:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06346 for ; Thu, 14 Jan 1999 09:45:53 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id KAA57483; Thu, 14 Jan 1999 10:42:36 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901141742.KAA57483@panzer.plutotech.com> Subject: Re: Freebsd can't find my scsi bus. In-Reply-To: <369E2A19.7A957A35@ix.netcom.com> from Mike at "Jan 14, 99 12:32:09 pm" To: phate1@ix.netcom.com (Mike) Date: Thu, 14 Jan 1999 10:42:36 -0700 (MST) 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 Mike wrote... > Kenneth D. Merry wrote: > > > > Mike wrote... > > > FreeBSD 2.2.7-RELEASE > > > P2-333 > > > Mylex 960SXI SCSI<->SCSI Raid controller. > > > Adaptec 2940U/UW SCSI Controller. > > > > > > Hi, > > > > > > I'm trying to setup a scsi<->scsi raid controller hooked up a 2940uw > > > host scsi controller. > > > > > > I setup the raid controller fine (create an array, initialize the > > > array), boot up the system, then adaptec 2940 detects the array of disks > > > as SCSI ID 0, LUN 0.. > > > > > > But when I boot up freebsd, freebsd doesnt detect ANY disks whatsoever. > > > > > > What can be the problem? > > > > That is a bit odd. The first question is, does FreeBSD detect your 2940? > > Are you sure the 2940 isn't a 2940 U2W (i.e., an Ultra-2 controller)? > > > > Will FreeBSD boot if you put a "normal" disk on the system? How did you > > install FreeBSD in the first place if it doesn't detect any disks? > thanks for replying. > > yes, I have a 2940U/UW controller.. Not U2W.. > > OK, first of all i found interesting, that unlike in other computers > (using regular scsi disks) in this one the 2940 occupies 2 IRQ's - #9, > #10 shown by the BIOS after startup. > > Now, when freebsd boots up, all the way at the top, it shows found - > Adaptec-- IRQ 9 - no driver assigned > Adaptec-- IRQ 10 - no driver assigned It really sounds like you've got a 3940AUW, or a 2940 "Dual". Both of them have 7895 chips onboard. That would explain why you're seeing two interrupts assigned for the board. Can you look on the board itself and find out: - how many large Adaptec chips are on it - What the markings/model numbers are on those chips. > Further way down in the probe, it shows > aha0 not found at 0x330.. That driver is for the Adaptec 154x series of ISA controllers. 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 Thu Jan 14 09:54:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07601 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 09:54:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07596 for ; Thu, 14 Jan 1999 09:54:16 -0800 (PST) (envelope-from hinman@us.networkcs.com) Received: from us.networkcs.com (us.networkcs.com [137.66.11.15]) by marcos.networkcs.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id LAA10559 for ; Thu, 14 Jan 1999 11:53:07 -0600 (CST) Received: (from hinman@localhost) by us.networkcs.com (8.8.7/8.8.7) id LAA02406 for freebsd-scsi@freebsd.org; Thu, 14 Jan 1999 11:53:06 -0600 (CST) From: "Lee E. Hinman" Message-Id: <199901141753.LAA02406@us.networkcs.com> Subject: Help with Onboard Adaptec 7890 and LVD drive To: freebsd-scsi@FreeBSD.ORG Date: Thu, 14 Jan 1999 11:53:06 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL32 (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 Hi, I'm trying to install 3.0Release on a Gateway ALR 7200, and I'm having a daemon of a time getting it to boot off the Hard drive. Here are the specs: 2 Adaptec 7890 onboard Controlers, Bios 2.01 Seagate ST34573LW Hard Drive Phoenix Bios 4.0 6.00.4 What happens: Boots off floppy fine detects 7890 Controller Do Novice Install, with Minimal distribution set reboot get a "Read Error" from Bios when it should start booting FreeBSD Things I've Tried: Different LVD terminators Different SCSI cables Jumpering the TP jumper on HD Forcing HD Single Ended Slowing Down Transfer Rate to 40M/sec in Adaptec Bios True Partion Entries Explicitly setting bootable flag during format I have Disabled the Second Adaptec Controler Does Anybody have any ideas? Thanks Lee -- ___________________________________________________________________________ | Lee E. Hinman PhD. | Email: hinman@networkcs.com | | Network Computing Services Inc. | | | Minneapolis, MN 55415 | Web: www.networkcs.com | --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 14 12:52:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05967 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 12:52:58 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05962 for ; Thu, 14 Jan 1999 12:52:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00754; Thu, 14 Jan 1999 12:48:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901142048.MAA00754@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Lee E. Hinman" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Help with Onboard Adaptec 7890 and LVD drive In-reply-to: Your message of "Thu, 14 Jan 1999 11:53:06 CST." <199901141753.LAA02406@us.networkcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Jan 1999 12:48:13 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > > I'm trying to install 3.0Release on a Gateway ALR 7200, and I'm having > a daemon of a time getting it to boot off the Hard drive. Here are the > specs: > > 2 Adaptec 7890 onboard Controlers, Bios 2.01 > Seagate ST34573LW Hard Drive > Phoenix Bios 4.0 6.00.4 > > What happens: > Boots off floppy fine > detects 7890 Controller > Do Novice Install, with Minimal distribution set > reboot > get a "Read Error" from Bios when it should start booting FreeBSD > > Things I've Tried: > Different LVD terminators > Different SCSI cables > Jumpering the TP jumper on HD > Forcing HD Single Ended > Slowing Down Transfer Rate to 40M/sec in Adaptec Bios > True Partion Entries > Explicitly setting bootable flag during format > I have Disabled the Second Adaptec Controler > > Does Anybody have any ideas? Things you haven't tried: - Change the "extended translation for disks > 1GB" option in the Adaptec's setup screen. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 14 13:39:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12691 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 13:39:03 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12680; Thu, 14 Jan 1999 13:38:59 -0800 (PST) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.8.8/8.8.5) id PAA10389; Thu, 14 Jan 1999 15:37:50 -0600 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 14 Jan 1999 15:37:50 -0600 (CST) Reply-To: greg@uswest.net Organization: US WEST !NTERACT From: Greg Rowe To: freebsd-smp@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Fatal Trap - Update Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've done some more testing on this problem and have at least narrowed it down somewhat. The failure happens repeatedly by just un-tarring a tar file. No matter what the tar file contains, it seems to always drop into the debbugger at approximately the same point in the file ??? I've done this around 30 times with different tar files and it always crashes within a file or two of the previous crash. It seems to only be able to handle X amount of IO from tar, but multiple copies of bonnie run fine. The problem doesn't seem to be hardware related (at least failing hardware) as it happens on another system with the same mainboard and CPU's. The problem does not happen in non-SMP mode. The problem also does not exist in SMP mode on 3.0-RELEASE (straight CD install with SMP-GENERIC kernel), so the problem was introduced in -CURRENT. (I'm running yesterdays -CURRENT now) Adaptec SCSI controller revision, number of drives, type of drives, and number of controllers do not effect the problem, I've tried it all ways. Also, the page fault will sometimes report cpuid=0 and sometimes cpuid=1. The problem doesn't exist on a quad Xeon system running the same -CURRENT. So, I guess the question of the day is "what does a Tyan Tiger 100 mainboard, 3.0 CURRENT, SMP, and tar have in common" ? Any ideas what I should try next ? Thanks, Greg -----FW: Fatal Trap----- Date: Mon, 11 Jan 1999 16:48:53 -0600 (CST) From: Greg Rowe To: freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Fatal Trap I have a Tyan mb dual 400mhz system I'm building that's getting repeatable crashes under disk load. This didn't occur until I compiled an SMP kernel. I'm running -current as of last Friday and the system has 512mb of memory and 4 drives on Adaptec controllers (1 - 4gig on one controller and 3 - 9gig on the other). Untarring a file will interestingly enough crash the system at around the same appoximate place in the tar image every time, although it's crashed while building ports also. The system drops to the debugger with the following: Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid=1; lapic.id = 01000000(I've also seen it for cpuid0) fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xf0216357 stack pointer = 0x10:0xff618ce8 frame pointer = 0x10:0xff618d0c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 243 (tar) interrupt mask = net tty bio cam <-SMP:XXX kernel: type 12 trap, code 0 Stopped at generic_bzero+0xf: repe stosl %es:(%edi) Any ideas as to what to look for ? Thanks. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 14 13:56:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15326 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 13:56:23 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gta.gta.com (gta.gta.com [199.120.225.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA15320 for ; Thu, 14 Jan 1999 13:56:20 -0800 (PST) (envelope-from lab@gta.com) Message-Id: <199901142202.RAA14307@gta.gta.com> Received: forwarded by SMTP 1.6.0. Received: (from lab@localhost) by uno.gta.com (8.8.8/8.8.7) id QAA28843 for freebsd-scsi@freebsd.org; Thu, 14 Jan 1999 16:51:19 -0500 (EST) From: "Larry Baird" Date: Thu, 14 Jan 1999 16:51:19 -0500 X-Mailer: Z-Mail (3.0.1 04apr94) To: freebsd-scsi@FreeBSD.ORG Subject: Re: AHA2940U2W and 2.2.8 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry (ken@plutotech.com) wrote: : Larry Baird wrote... : > Well it looks like I made an ordering mistake. I have several systems that : > I had planned to run 2.2.8 along with Adaptec AHA2940U2W controllers and : > the corresponding ultra2 hard disks. I now realize that only 3.0 supports this : > controller using CAM. : > : > There used to be a backport of CAM to 2.2 in : > ftp://ftp.freebsd.org/pub/FreeBSD/cam. This seems to have been moved : > to ftp://ftp.freebsd.org/pub/FreeBSD/development/cam. But the 2.2 cam : > boot.flp still expects to find the installation files in the old place. : > : > Does anybody have a work around? : You should be able to specify the full URL for the location of the : distribution. (nope, I don't know the exact sysinstall screen where you'd : type that in, it's been a while since I've done an install like that) Thanks for the clue. Here are the steps I did to get everything to work. 1) Get ftp://ftp.freebsd.org/pub/FreeBSD/development/cam/2.2CAM-19980716-SNAP/floppies/boot.flp 2) Make a bootable floppy from above image and boot it. 3) Select kernel developer for distribution to install. 4) When specifing the media, select FTP and the URL. Specify a URL of ftp://ftp.freebsd.org/pub/FreeBSD/development/cam 5) After install, cd /usr/src/sys and build a new kernel and install it 6) Save old cam tree mv /usr/src/sys /usr/src/sys.cam.save 7) Use 2.2.8 CD to install all sources 8) Use cvsup to bring everything up todate. 9) Follow directions from ftp://ftp.freebsd.org/pub/FreeBSD/development/cam/README on how to apply the 2.2 cam patches. -- ----------------------------------------------------------------------------- Larry Baird Global Technology Associates, Inc. | Orlando, FL Email: lab@gta.com | Tel 407-380-0220 FAX 407-380-6080 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 14 18:03:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24320 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 18:03:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mx0-smtp.goodnet.com (envy.goodnet.com [207.98.129.151]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24307 for ; Thu, 14 Jan 1999 18:03:01 -0800 (PST) (envelope-from mc4pc@goodnet.com) Received: from p200mmxntwks (dsld29.phnx.uswest.net [209.180.145.28]) by mx0-smtp.goodnet.com with SMTP id TAA17964 for ; Thu, 14 Jan 1999 19:01:47 -0700 (MST) Reply-To: From: "Max" To: Subject: DAC 960 Date: Thu, 14 Jan 1999 19:02:01 -0700 Message-ID: <000b01be402b$0aa772b0$1c91b4d1@p200mmxntwks.phnx.uswest.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <199901141742.KAA57483@panzer.plutotech.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does FreeBSD supports the DAC960 Raid? warchive lists having one running in their server. thanks Max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 14 18:05:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24564 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 18:05:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA24557 for ; Thu, 14 Jan 1999 18:05:07 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with esmtp (Exim 1.82 #3) id 100xdM-0004PM-00; Thu, 14 Jan 1999 17:01:08 -0800 Date: Thu, 14 Jan 1999 17:01:05 -0800 (PST) From: Tom To: Simon Shapiro cc: Martin Welk , freebsd-scsi@FreeBSD.ORG Subject: FreeBSD dptmgr... any takers? (was: FreeBSD and RAID controller) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id SAA24560 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 14 Jan 1999, Simon Shapiro wrote: > > Martin Welk, On 08-Jan-99 you wrote: > > Hi everybody, > > > > I have to set up a FreeBSD machine for a customer that needs a SCSI RAID > > subsystem, and internal CD-ROM and 1/4" tape drive. > > > > Can anybody give a hint for which host adapters I should look? The DPT > > adapters seem to look fine, but I donīt know how they work exactly and > > if all DPT adapters are supported. The same with the Adaptec RAID > > adapters. > > All SmartRaid and SmartCache generations III and IV work (PCI/EISA, no ISA). > The i2o SmartCache V are in development now. > > Simon Anybody got a working dptmgr binary for FreeBSD? Would sponsership assist somebody who has received the code from DPT? Would anyone be interesting in joint sponsering someone to finish dptmgr for FreeBSD? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 14 18:08:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24988 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 18:08:09 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uhura.concentric.net (uhura.concentric.net [206.173.119.93]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24976 for ; Thu, 14 Jan 1999 18:08:06 -0800 (PST) (envelope-from bstockr@concentric.net) From: bstockr@concentric.net Received: from cliff.concentric.net ([206.173.119.90]) by uhura.concentric.net (8.9.1a/(98/12/15 5.12)) id VAA01266; Thu, 14 Jan 1999 21:06:56 -0500 (EST) [1-800-745-2747 The Concentric Network] Received: from concentric.net (ts004d29.buf-ny.concentric.net [206.173.43.185]) by cliff.concentric.net (8.9.1a) id VAA00985; Thu, 14 Jan 1999 21:06:53 -0500 (EST) Message-ID: <369EA2D7.D153B2B7@concentric.net> Date: Thu, 14 Jan 1999 21:07:19 -0500 X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: freebsd scsi problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello SCSI@FreeBSD.org Per Instructions from Walnut Creek CdROM I am forwarding this to you as I am having problems with FreeBSD versions after 2.1.5 that is I did not have these problems with 2.1.5, but did with 2.2.5 and 2.2.8. I also had problems with 3.0 which I returned to Walnut Creek. the system does not lock up but any time the system is sitting idle for 10-20 minutes I get the message that follows at the end of this message. Also per Walnut Creek the drivers changed between 2.1.5 and 2.2.5. Anyways here is a copy of dmesg which I printed and have copied verbatim in this text. 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.8-RELEASE #0: Mon Nov 30 06:34:08 GMT 1998 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC CPU: Pentium/P54C (75.00-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 50331648 (49152K bytes) avail memory = 46661632 (45568K bytes) Probing for devices on PCI bus 0: chip0 rev 57 on pci0:0:0 chip1 rev 0 on pci0:1:0 vga0 rev 0 int a irq 15 on pci0:11:0 ahc0 rev 0 int a irq 10 on pci0:13:0 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "SEAGATE ST3620N 8070" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 520MB (1066255 512 byte sectors) (ahc0:4:0): "TOSHIBA CD-ROM XM-3601TA 1885" type 5 removable SCSI 2 cd0(ahc0:4:0): CD-ROM can't get the size Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 Lpt0 at 0x378-0x2ff irq 3 on isa Lpt0: Interrupt-driven port Lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in npx0 flags 0x1 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround changing root device to sd0s1a sd0(ahc0:0:0): ILLEGAL REQUEST info?:0x6f asc:20,0 Invalid command operation cod e field replaceable unit: 1 sks:c0,0 sd0(ahc0:0:0): ILLEGAL REQUEST info?:0x44e0f asc:20,0 Invalid command operation code field replaceable unit: 1 sks:c0,0 sd0(ahc0:0:0): ILLEGAL REQUEST info?:0x44e0f asc:20,0 Invalid command operation code field replaceable unit: 1 sks:c0,0 sd0(ahc0:0:0): ILLEGAL REQUEST info?:0x44e0f asc:20,0 Invalid command operation code field replaceable unit: 1 sks:c0,0 sd0(ahc0:0:0): ILLEGAL REQUEST info?:0x44e0f asc:20,0 Invalid command operation code field replaceable unit: 1 sks:c0,0 Once again this happen if I sign in as a user or as root, in command line mode or using X windows. While using X windows any window which is open ie xterm or login will fill up with these error messages. Any help would be greatly appreciated Brett Stockdale To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 14 18:35:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28183 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 18:35:45 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dfw-ix1.ix.netcom.com (dfw-ix1.ix.netcom.com [206.214.98.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28178 for ; Thu, 14 Jan 1999 18:35:43 -0800 (PST) (envelope-from phate1@ix.netcom.com) Received: (from smap@localhost) by dfw-ix1.ix.netcom.com (8.8.4/8.8.4) id UAA19460; Thu, 14 Jan 1999 20:33:57 -0600 (CST) Received: from unknown(205.184.128.228) by dfw-ix1.ix.netcom.com via smap (V1.3) id rma019350; Thu Jan 14 20:33:26 1999 Message-ID: <369EA9C1.3E4B28E0@ix.netcom.com> Date: Thu, 14 Jan 1999 21:36:49 -0500 From: Mike Organization: Integration Soft. X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: mc4pc@goodnet.com CC: freebsd-scsi@FreeBSD.ORG Subject: Re: DAC 960 References: <000b01be402b$0aa772b0$1c91b4d1@p200mmxntwks.phnx.uswest.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The DAC960SX/SXI is an external SCSI-SCSI controller, it's os/platform independent.. (it appears as one big disk to the host) I just set one up today. M Max wrote: > > Does FreeBSD supports the DAC960 Raid? warchive lists having one running in > their server. > > thanks > > Max > > 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 Jan 14 21:19:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18309 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 21:19:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from beast.freibergnet.de (beast.freibergnet.de [194.123.255.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18165 for ; Thu, 14 Jan 1999 21:19:36 -0800 (PST) (envelope-from mw@freibergnet.de) Received: from io.freibergnet.de (io.freibergnet.de [194.123.255.11]) by beast.freibergnet.de (8.8.8/8.8.8) with ESMTP id GAA12377; Fri, 15 Jan 1999 06:17:50 +0100 (CET) (envelope-from mw@freibergnet.de) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901142048.MAA00754@dingo.cdrom.com> Date: Fri, 15 Jan 1999 06:17:39 +0100 (CET) Reply-To: mw@freibergnet.de Organization: FreibergNet Liebscher & Partner Werbeagentur und XLink-PoP Freiberg From: Martin Welk To: Mike Smith Subject: Re: Help with Onboard Adaptec 7890 and LVD drive Cc: freebsd-scsi@FreeBSD.ORG, "Lee E. Hinman" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 14-Jan-99 Mike Smith wrote: () > Does Anybody have any ideas? () () Things you haven't tried: () () - Change the "extended translation for disks > 1GB" option in the () Adaptec's setup screen. Iīm not sure if this is necessary: as long as the kernel is under 1 GB, there shouldnīt appear a problem. For me, that problem appeared on my good old 486DX-80 at home with a Adaptec 2842 (VLB-SCSI-adapter, donīt blame, that machine just works and Iīm not going to change it :-) ) when I decided to reinstall my system on the exchange disk I received from Quantum the one that went to hell some days ago at work. The 2940UW I used had extended translation enabled (the different is, that the mapping to this C/H/S scheme uses a maximum of 255 heads, where the older scheme used just 64 heads due to BIOS limitations, as I remember) and so I needed to enable it at home, too. Before I never cared about, as the drive was and is dedicated to FreeBSD and nothing else. Regards, Martin -- FreibergNet Systemhaus GbR Martin Welk * Sales, Support Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781387 Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 14 22:44:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29587 for freebsd-scsi-outgoing; Thu, 14 Jan 1999 22:44:13 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA29582 for ; Thu, 14 Jan 1999 22:44:09 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 81803 invoked by uid 1000); 15 Jan 1999 07:50:42 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 15 Jan 1999 02:50:42 -0500 (EST) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Tom Subject: RE: FreeBSD dptmgr... any takers? (was: FreeBSD and RAID control Cc: freebsd-scsi@FreeBSD.ORG, Martin Welk Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tom, On 15-Jan-99 you wrote: > > On Thu, 14 Jan 1999, Simon Shapiro wrote: > > > > > Martin Welk, On 08-Jan-99 you wrote: > > > Hi everybody, > > > > > > I have to set up a FreeBSD machine for a customer that needs a SCSI > > > RAID > > > subsystem, and internal CD-ROM and 1/4" tape drive. > > > > > > Can anybody give a hint for which host adapters I should look? The > > > DPT > > > adapters seem to look fine, but I donīt know how they work exactly > > > and > > > if all DPT adapters are supported. The same with the Adaptec RAID > > > adapters. > > > > All SmartRaid and SmartCache generations III and IV work (PCI/EISA, no > > ISA). > > The i2o SmartCache V are in development now. > > > > Simon > > Anybody got a working dptmgr binary for FreeBSD? Would sponsership > assist somebody who has received the code from DPT? Would anyone be > interesting in joint sponsering someone to finish dptmgr for FreeBSD? I have all the necessary NDA paperwork from DPT, but currently the new generation cards are higher priority. Sponsorship will definitely help :-) Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jan 15 04:52:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07738 for freebsd-scsi-outgoing; Fri, 15 Jan 1999 04:52:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07729 for ; Fri, 15 Jan 1999 04:52:01 -0800 (PST) (envelope-from ip@nessie.mcc.ac.uk) Received: from nessie.mcc.ac.uk ([130.88.200.20] ident=ip) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #2) for scsi@freebsd.org id 1018i3-000030-00; Fri, 15 Jan 1999 12:50:43 +0000 Received: (from ip@localhost) by nessie.mcc.ac.uk (8.8.8/8.8.8) id MAA21397 for scsi@freebsd.org; Fri, 15 Jan 1999 12:50:43 GMT (envelope-from ip) From: Ian Pallfreeman Message-Id: <199901151250.MAA21397@nessie.mcc.ac.uk> Subject: CAM doesn't like my DAT any more To: scsi@FreeBSD.ORG Date: Fri, 15 Jan 1999 12:50:43 +0000 (GMT) Reply-To: ip@mcc.ac.uk X-Mailer: ELM [version 2.4ME+ PL32 (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 >From the 13th onwards, I can't boot my -current trash box -- it's choking probing the SCSI bus. Here's what I'm expecting: >> FreeBSD 3.0-CURRENT #18: Tue Jan 12 14:44:39 GMT 1999 >> ip@lurch:/usr/src/sys/compile/LURCH >> [...] >> Waiting 15 seconds for SCSI devices to settle >> sa0 at ahc0 bus 0 target 4 lun 0 >> sa0: Removable Sequential Access SCSI-2 device >> sa0: 5.0MB/s transfers (5.0MHz, offset 8) >> da1 at ahc0 bus 0 target 2 lun 0 >> da1: Fixed Direct Access SCSI-2 device >> da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled >> da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) >> da0 at ahc0 bus 0 target 0 lun 0 >> da0: Fixed Direct Access SCSI-2 device >> da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled >> da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) >> changing root device to wd0s1a Here's what I'm getting: >> FreeBSD 3.0-CURRENT #19: Thu Jan 14 12:28:36 GMT 1999 >> ip@lurch:/usr/src/sys/compile/LURCH >> [...] >> Waiting 15 seconds for SCSI devices to settle >> ahc0:A:4: Message reject for 80 -- ignored >> (probe4:ahc0:0:4:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x9 >> (probe4:ahc0:0:4:0): Queuing a BDR SCB >> (probe4:ahc0:0:4:0): Bus Device Reset Message Sent >> (probe4:ahc0:0:4:0): SCB 0x4 - timed out in message out phase, SEQADDR == 0x153 >> (probe4:ahc0:0:4:0): no longer in timeout, status = 34b >> ahc0: Issued Channel A Bus Reset. 1 SCBs aborted >> ahc0:A:4: Message reject for 80 -- ignored The "message reject" repeats, and we go nowhere. >From a "boot -v", we see: >> (probe4:ahc0:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 >> (probe4:ahc0:0:4:0): ILLEGAL REQUEST asc:24,0 >> (probe4:ahc0:0:4:0): Invalid field in CDB sks:c8,1 >> ahc0:A:4: Message reject for 80 -- ignored Complete boot output (today's kernel) appended. All the best, Ian. <----------> BIOS basemem (639K) != RTC basemem (640K), setting to BIOS value Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #21: Fri Jan 15 12:03:26 GMT 1999 ip@lurch:/usr/src/sys/compile/LURCH Calibrating clock(s) ... TSC clock: 199439027 Hz, i8254 clock: 1193226 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 199432938 Hz CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x617 Stepping=7 Features=0xf9ff real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00286000 - 0x03ffdfff, 64454656 bytes (15736 pages) avail memory = 62705664 (61236K bytes) Found BIOS32 Service Directory header at 0xf00fd770 Entry = 0xfd780 (0xf00fd780) Rev = 0 Len = 1 PCI BIOS entry at 0xd7a1 DMI header at 0xf00fa160 Version 2.0 Table at 0xfa17c, 34 entries, 1155 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000fa760 Preloaded elf kernel "kernel" at 0xf0279000. pci_open(1): mode 1 addr port (0x0cf8) is 0x80000090 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12378086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x1237, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip0: rev 0x02 on pci0.0.0 found-> vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x01 on pci0.7.0 I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks Extended BIOS: enabled Lower BIOS: enabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: disabled, B: IRQ9, C: disabled, D: IRQ5 MB0: IRQ15, MB1: found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000ff60, size 4 ide_pci0: rev 0x00 on pci0.7.1 intel_piix_status: primary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: primary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 04 from port: 0000ff62 intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: secondary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: secondary slave fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled ide_pci: busmaster 1 status: 04 from port: 0000ff6a found-> vendor=0x10b7, dev=0x5900, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=5 map[0]: type 4, range 32, base 0000ff80, size 5 vx0: <3COM 3C590 Etherlink III PCI> rev 0x00 int a irq 5 on pci0.15.0 utp/aui/bnc[*utp*] address 00:a0:24:6a:3e:42 found-> vendor=0x1142, dev=0x6424, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 1, range 32, base fe000000, size 24 map[1]: type 4, range 32, base 0000ffa0, size 4 vga0: rev 0x00 on pci0.17.0 found-> vendor=0x9004, dev=0x8178, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base 0000fc00, size 8 map[1]: type 1, range 32, base ffbee000, size 12 ahc0: rev 0x00 int a irq 9 on pci0.19.0 ahc0: Reading SEEPROM...done. ahc0: internal 50 cable is present, internal 68 cable not present ahc0: external cable not present ahc0: BIOS eeprom not present ahc0: Low byte termination Enabled ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 411 instructions downloaded Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x10000, flags:0x3d0000 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-8 wd0: 81MB (166600 sectors), 980 cyls, 10 heads, 17 S/T, 512 B/S wd0: ATA INQUIRE valid = 0000, dmamword = 0000, apio = 0000, udma = 0000 wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa intel_piix_dmainit: setting multiword DMA mode 2 wd2: wdsetmode() setting transfer mode to 22 intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: secondary slave fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-16 wd2: 3681MB (7539840 sectors), 7480 cyls, 16 heads, 63 S/T, 512 B/S wd2: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 intel_piix_dmainit: setting multiword DMA mode 2 wd3: wdsetmode() setting transfer mode to 22 intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: secondary slave fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled wdc1: unit 1 (wd3): , DMA, 32-bit, multi-block-16 wd3: 3681MB (7539840 sectors), 7480 cyls, 16 heads, 63 S/T, 512 B/S wd3: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xf00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 02 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 00 00 03 00 02 67 5f 4f 50 02 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff npx0 on motherboard npx0: INT 16 interface imasks: bio c008c040, tty c003001a, net c0060020 BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. ccd0: Concatenated disk driver Waiting 15 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc0: Selection Timeout on A:1. 1 SCBs aborted ahc0: Selection Timeout on A:3. 1 SCBs aborted ahc0: Selection Timeout on A:5. 1 SCBs aborted ahc0: Selection Timeout on A:6. 1 SCBs aborted (probe4:ahc0:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe4:ahc0:0:4:0): ILLEGAL REQUEST asc:24,0 (probe4:ahc0:0:4:0): Invalid field in CDB sks:c8,1 ahc0:A:4: Message reject for 80 -- ignored (probe4:ahc0:0:4:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xc (probe4:ahc0:0:4:0): Queuing a BDR SCB (probe4:ahc0:0:4:0): Bus Device Reset Message Sent (probe4:ahc0:0:4:0): SCB 0x0 - timed out in message out phase, SEQADDR == 0x153 (probe4:ahc0:0:4:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted ahc0:A:4: Message reject for 80 -- ignored (probe0:ahc0:0:4:1): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xc (probe0:ahc0:0:4:1): Queuing a BDR SCB (probe0:ahc0:0:4:1): Bus Device Reset Message Sent (probe0:ahc0:0:4:1): SCB 0x0 - timed out in message out phase, SEQADDR == 0x153 (probe0:ahc0:0:4:1): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted ahc0:A:4: Message reject for 80 -- ignored To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jan 15 07:44:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01079 for freebsd-scsi-outgoing; Fri, 15 Jan 1999 07:44:37 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01071 for ; Fri, 15 Jan 1999 07:44:32 -0800 (PST) (envelope-from hinman@us.networkcs.com) Received: from us.networkcs.com (us.networkcs.com [137.66.11.15]) by marcos.networkcs.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id JAA18971; Fri, 15 Jan 1999 09:43:12 -0600 (CST) Received: (from hinman@localhost) by us.networkcs.com (8.8.7/8.8.7) id JAA00121; Fri, 15 Jan 1999 09:43:11 -0600 (CST) From: "Lee E. Hinman" Message-Id: <199901151543.JAA00121@us.networkcs.com> Subject: Re: Help with Onboard Adaptec 7890 and LVD drive In-Reply-To: <199901142048.MAA00754@dingo.cdrom.com> from Mike Smith at "Jan 14, 99 12:48:13 pm" To: mike@smith.net.au (Mike Smith) Date: Fri, 15 Jan 1999 09:43:11 -0600 (CST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (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 > > Hi, > > > > I'm trying to install 3.0Release on a Gateway ALR 7200, and I'm having > > a daemon of a time getting it to boot off the Hard drive. Here are the > > specs: > > > > 2 Adaptec 7890 onboard Controlers, Bios 2.01 > > Seagate ST34573LW Hard Drive > > Phoenix Bios 4.0 6.00.4 > > > > What happens: > > Boots off floppy fine > > detects 7890 Controller > > Do Novice Install, with Minimal distribution set > > reboot > > get a "Read Error" from Bios when it should start booting FreeBSD > > > > Things I've Tried: > > Different LVD terminators > > Different SCSI cables > > Jumpering the TP jumper on HD > > Forcing HD Single Ended > > Slowing Down Transfer Rate to 40M/sec in Adaptec Bios > > True Partion Entries > > Explicitly setting bootable flag during format > > I have Disabled the Second Adaptec Controler > > > > Does Anybody have any ideas? > > Things you haven't tried: > > - Change the "extended translation for disks > 1GB" option in the > Adaptec's setup screen. > -- Changing the extended translation didn't have any effect, but I was able to fix this. As usual FreeBSD was working perfectly. I reformatted the disk using the Adaptec Bios and after that it booted just fine, Gateway must have shipped the disk with some weird format. Thanks for the suggestions. Lee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jan 15 08:04:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03791 for freebsd-scsi-outgoing; Fri, 15 Jan 1999 08:04:33 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03786 for ; Fri, 15 Jan 1999 08:04:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id HAA00650; Fri, 15 Jan 1999 07:59:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901151559.HAA00650@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mw@freibergnet.de cc: Mike Smith , freebsd-scsi@FreeBSD.ORG, "Lee E. Hinman" Subject: Re: Help with Onboard Adaptec 7890 and LVD drive In-reply-to: Your message of "Fri, 15 Jan 1999 06:17:39 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 15 Jan 1999 07:59:34 -0800 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id IAA03787 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On 14-Jan-99 Mike Smith wrote: > > () > Does Anybody have any ideas? > () > () Things you haven't tried: > () > () - Change the "extended translation for disks > 1GB" option in the > () Adaptec's setup screen. > > Iīm not sure if this is necessary: as long as the kernel is under 1 GB, I'm absolutely certain that it *is* necessary - the option changes the BIOS geometry for any disk > 1GB, and sysinstall/libdisk/CAM make assumptions about this which determine the layout of the disk during the installation. If this option is set incorrectly, you WILL NOT be able to boot following installation. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jan 15 09:59:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15961 for freebsd-scsi-outgoing; Fri, 15 Jan 1999 09:59:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA15933 for ; Fri, 15 Jan 1999 09:59:05 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA27947 (5.67b/IDA-1.5); Fri, 15 Jan 1999 18:36:06 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id HAA07652; Fri, 15 Jan 1999 07:51:29 +0100 (CET) From: Wilko Bulte Message-Id: <199901150651.HAA07652@yedi.iaf.nl> Subject: Re: DAC 960 In-Reply-To: <000b01be402b$0aa772b0$1c91b4d1@p200mmxntwks.phnx.uswest.net> from Max at "Jan 14, 99 07:02:01 pm" To: mc4pc@goodnet.com Date: Fri, 15 Jan 1999 07:51:29 +0100 (CET) Cc: freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (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 As Max wrote... > > Does FreeBSD supports the DAC960 Raid? warchive lists having one running in > their server. You need to qualify what DAC960 you mean. The DAC960 SCSI-SCSI variants work (like in wcarchive). The DAC960Px backplane raid controllers don't work for lack of a driver. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jan 15 12:26:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06194 for freebsd-scsi-outgoing; Fri, 15 Jan 1999 12:26:57 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06189; Fri, 15 Jan 1999 12:26:55 -0800 (PST) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.8.8/8.8.5) id OAA13011; Fri, 15 Jan 1999 14:26:47 -0600 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 15 Jan 1999 14:26:46 -0600 (CST) Reply-To: greg@uswest.net Organization: US WEST !NTERACT From: Greg Rowe To: freebsd-smp@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: More - Fatal Trap - Update Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I found today that cpio will also cause the crash in the exact same way. It's interesting that bonnie won't though since that's what we usually use to test for IO problems. Greg -----FW: Fatal Trap - Update----- Date: Thu, 14 Jan 1999 15:05:17 -0600 (CST) From: Greg Rowe To: freebsd-smp@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Fatal Trap - Update I've done some more testing on this problem and have at least narrowed it down somewhat. The failure happens repeatedly by just un-tarring a tar file. No matter what the tar file contains, it seems to always drop into the debbugger at approximately the same point in the file ??? I've done this around 30 times with different tar files and it always crashes within a file or two of the previous crash. It seems to only be able to handle X amount of IO from tar, but multiple copies of bonnie run fine. The problem doesn't seem to be hardware related (at least failing hardware) as it happens on another system with the same mainboard and CPU's. The problem does not happen in non-SMP mode. The problem also does not exist in SMP mode on 3.0-RELEASE (straight CD install with SMP-GENERIC kernel), so the problem was introduced in -CURRENT. (I'm running yesterdays -CURRENT now) Adaptec SCSI controller revision, number of drives, type of drives, and number of controllers do not effect the problem, I've tried it all ways. Also, the page fault will sometimes report cpuid=0 and sometimes cpuid=1. The problem doesn't exist on a quad Xeon system running the same -CURRENT. So, I guess the question of the day is "what does a Tyan Tiger 100 mainboard, 3.0 CURRENT, SMP, and tar have in common" ? Any ideas what I should try next ? Thanks, Greg -----FW: Fatal Trap----- Date: Mon, 11 Jan 1999 16:48:53 -0600 (CST) From: Greg Rowe To: freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Fatal Trap I have a Tyan mb dual 400mhz system I'm building that's getting repeatable crashes under disk load. This didn't occur until I compiled an SMP kernel. I'm running -current as of last Friday and the system has 512mb of memory and 4 drives on Adaptec controllers (1 - 4gig on one controller and 3 - 9gig on the other). Untarring a file will interestingly enough crash the system at around the same appoximate place in the tar image every time, although it's crashed while building ports also. The system drops to the debugger with the following: Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid=1; lapic.id = 01000000(I've also seen it for cpuid0) fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xf0216357 stack pointer = 0x10:0xff618ce8 frame pointer = 0x10:0xff618d0c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 243 (tar) interrupt mask = net tty bio cam <-SMP:XXX kernel: type 12 trap, code 0 Stopped at generic_bzero+0xf: repe stosl %es:(%edi) Any ideas as to what to look for ? Thanks. Greg --------------End of forwarded message------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jan 15 19:13:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23571 for freebsd-scsi-outgoing; Fri, 15 Jan 1999 19:13:02 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23566 for ; Fri, 15 Jan 1999 19:13:01 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id TAA05270; Fri, 15 Jan 1999 19:11:50 -0800 Date: Fri, 15 Jan 1999 19:11:50 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: ip@mcc.ac.uk cc: scsi@FreeBSD.ORG Subject: Re: CAM doesn't like my DAT any more In-Reply-To: <199901151250.MAA21397@nessie.mcc.ac.uk> 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 Hmm. That was probably me that broke it for you-although I don't see how as the changes I made didn't affect the probe time stuff. If you could revert to the previous version of scsi_sa.c and let me know if that works better for you, I'd appreciate it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 16 11:05:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11025 for freebsd-scsi-outgoing; Sat, 16 Jan 1999 11:05:46 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mx0-smtp.goodnet.com (envy.goodnet.com [207.98.129.151]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11016 for ; Sat, 16 Jan 1999 11:05:44 -0800 (PST) (envelope-from mc4pc@goodnet.com) Received: from p200mmxntwks (dsld29.phnx.uswest.net [209.180.145.28]) by mx0-smtp.goodnet.com with SMTP id MAA12571; Sat, 16 Jan 1999 12:05:33 -0700 (MST) Reply-To: From: "Max" To: "Wilko Bulte" Cc: Subject: RE: DAC 960 Date: Sat, 16 Jan 1999 12:05:39 -0700 Message-ID: <000d01be4183$34f2a130$1c91b4d1@p200mmxntwks.phnx.uswest.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-reply-to: <199901150651.HAA07652@yedi.iaf.nl> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I got the DAC960F. Does anyone know of any drivers that I could use. thanks Max -----Original Message----- From: Wilko Bulte [mailto:wilko@yedi.iaf.nl] Sent: Thursday, January 14, 1999 11:51 PM To: mc4pc@goodnet.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: DAC 960 As Max wrote... > > Does FreeBSD supports the DAC960 Raid? warchive lists having one running in > their server. You need to qualify what DAC960 you mean. The DAC960 SCSI-SCSI variants work (like in wcarchive). The DAC960Px backplane raid controllers don't work for lack of a driver. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 16 13:25:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24380 for freebsd-scsi-outgoing; Sat, 16 Jan 1999 13:25:59 -0800 (PST) (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 NAA24371 for ; Sat, 16 Jan 1999 13:25:57 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt2-238.HiWAAY.net [208.147.148.238]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id PAA26785 for ; Sat, 16 Jan 1999 15:25:54 -0600 (CST) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.1/8.9.1) with ESMTP id PAA00326 for ; Sat, 16 Jan 1999 15:25:51 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199901162125.PAA00326@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@FreeBSD.ORG Subject: Symbios 875 activity LED? From: David Kelly Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Jan 1999 15:25:51 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just had my system apart as I found some new-in-box Kingston 32MB FP parity 60ns 72-pin SIMMs at a "computer show" for $30 each and had to put them in. Hurray! 128MB! Should have bought all he had. Before you ask, system is 3.0-Current as of 2-jan. While I was in there, connected my Asus SC875's LED connector to the otherwise unused "Turbo LED" wires. Observed the internal LED works at boot time. And lights the external too. But still not under FreeBSD. There was some talk of this long time ago. Did it not make it into the distribution? Just now cvsup'ed again to see how Matthew Jacob's scsi_sa.c fixes behave on my problem tape drives (which are on an Adaptec 2940, which does light its LED during access). -- 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 Sat Jan 16 15:42:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07498 for freebsd-scsi-outgoing; Sat, 16 Jan 1999 15:42:49 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from www.giovannelli.it (www.giovannelli.it [194.184.65.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07490; Sat, 16 Jan 1999 15:42:42 -0800 (PST) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem30.masternet.it [194.184.65.40]) by www.giovannelli.it (8.8.8/8.8.5) with SMTP id AAA07001; Sun, 17 Jan 1999 00:42:29 +0100 (MET) Message-Id: <4.1.19990117003737.009d4a80@194.184.65.4> X-Sender: gmarco@194.184.65.4 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 17 Jan 1999 00:49:57 +0100 To: current@FreeBSD.ORG From: Gianmarco Giovannelli Subject: Problem booting from aic7890/91 Ultra2 SCSI Cc: scsi@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok, first the conclusion... I am not able to boot anymore from a 3.0-current system while I can boot quite nicely from the 3.0-RELEASE generic kernel. The system hangs on checking the scsi chain and remains stopped here. The last thing I can see on the screen is the : Waiting 3 seconds for SCSI devices to settle And nothing else happens anymore. So I have to hard reset the box. here is a dmesg from the 3.0-RELEASE generic kernel. ### dmesg of 3.0-RELEASE generic kernel ### Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #0: Sat Oct 17 17:45:06 GMT 1998 jkh@kickme.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz cost 3038 ns CPU: Pentium II (quarter-micron) (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183f9ff> real memory = 134217728 (131072K bytes) avail memory = 127537152 (124548K bytes) Preloaded a.out kernel "kernel.GENERIC" at 0x0xf02ed000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 ide_pci0: rev 0x01 on pci0.4.1 chip3: rev 0x01 int d irq 255 on pci0.4.2 chip4: rev 0x02 on pci0.4.3 ahc0: rev 0x00 int a irq 14 on pci0.6.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs de0: rev 0x11 int a irq 14 on pci0.9.0 de0: 21041 [10Mb/s] pass 1.1 de0: address 00:40:05:36:7a:72 Probing for devices on PCI bus 1: vga0: rev 0x01 int a irq 11 on pci1.0.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 fe0 not found at 0x300 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 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 wdc0 not found at 0x1f0 wdc1 not found at 0x170 wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 ex0 not found le0 not found at 0x300 lnc0 not found at 0x280 ze0 not found at 0x300 zp0 not found at 0x300 cs0 not found at 0x300 adv0 not found at 0x330 bt0 not found at 0x134 aha0 not found at 0x134 npx0 on motherboard npx0: INT 16 interface de0: enabling 10baseT port Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 3.300MB/s transfers da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 40.0MB/s transfers (20.0MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8682MB (17781520 512 byte sectors: 255H 63S/T 1106C) changing root device to da0s1a da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: 20.0MB/s transfers (10.0MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 2069MB (4238640 512 byte sectors: 255H 63S/T 263C) da2 at ahc0 bus 0 target 2 lun 0 da2: Removable Direct Access SCSI2 device da2: 3.300MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present ### End dmesg ### My kernel is : ### Begin kernel ### machine "i386" cpu "I686_CPU" ident GMARCO maxusers 32 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options PROCFS #Process filesystem options FFS_ROOT options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=3000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SYSVSHM options SYSVSEM options SYSVMSG config kernel root on da0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller ahc0 controller scbus0 device da0 device sa0 device cd0 controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts device sc0 at isa? tty pseudo-device splash device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device de0 device apm0 at isa? flags 0x31 # Advanced Power Management controller pnp0 #Luigi's drivers device pcm0 at isa? port 0x220 tty irq ? drq ? flags 0x15 vector pcmintr controller smbus0 controller iicbus0 controller iicbb0 device bktr0 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip ### End kernel ### I have also a cdrom installed on id #5 , but it is not listed in the GENERIC kernel's dmesg, because with -CURRENT it logs some error about timeout, so I decided to put out of the chain. But the hans problem is still here also without cdrom. The mainboard is an asus P2B-S with scsi onboard (bios 2.01). I use the bios default fro the controller... Please answer... Best Regards, Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) "Unix expert since yesterday" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 16 18:14:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20573 for freebsd-scsi-outgoing; Sat, 16 Jan 1999 18:14:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from rebma.ghostwheel.com (rebma.ghostwheel.com [207.201.56.159]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20561; Sat, 16 Jan 1999 18:14:12 -0800 (PST) (envelope-from merlin@ghostwheel.com) Received: from avalon (avalon.ghostwheel.com [207.201.56.88]) by rebma.ghostwheel.com (8.9.1/8.8.8) with SMTP id SAA09552; Sat, 16 Jan 1999 18:14:04 -0800 (PST) (envelope-from merlin@ghostwheel.com) Message-Id: <4.1.19990116180852.00a9aea0@pop.ghostwheel.com> X-Sender: merlin@rebma.ghostwheel.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 16 Jan 1999 18:10:28 -0800 To: Gianmarco Giovannelli From: Christopher Knight Subject: Re: Problem booting from aic7890/91 Ultra2 SCSI Cc: current@FreeBSD.ORG, scsi@FreeBSD.ORG In-Reply-To: <4.1.19990117003737.009d4a80@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 12:49 AM 1/17/99 +0100, Gianmarco Giovannelli wrote: > >Ok, first the conclusion... > >I am not able to boot anymore from a 3.0-current system while I can boot >quite nicely from the 3.0-RELEASE generic kernel. > >The system hangs on checking the scsi chain and remains stopped here. The >last thing I can see on the screen is the : >Waiting 3 seconds for SCSI devices to settle > >And nothing else happens anymore. So I have to hard reset the box. I have been seeing this for the two weeks or so. A shutdown -r will always hang. A complete powerdown has been the only way I can reboot my box of late. -ck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 16 18:54:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23292 for freebsd-scsi-outgoing; Sat, 16 Jan 1999 18:54:31 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from zeus.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23286; Sat, 16 Jan 1999 18:54:27 -0800 (PST) (envelope-from akm@zeus.theinternet.com.au) Received: (from akm@localhost) by zeus.theinternet.com.au (8.8.7/8.8.7) id MAA01382; Sun, 17 Jan 1999 12:56:51 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <199901170256.MAA01382@zeus.theinternet.com.au> Subject: Re: Problem booting from aic7890/91 Ultra2 SCSI In-Reply-To: <4.1.19990116180852.00a9aea0@pop.ghostwheel.com> from Christopher Knight at "Jan 16, 99 06:10:28 pm" To: merlin@ghostwheel.com (Christopher Knight) Date: Sun, 17 Jan 1999 12:56:51 +1000 (EST) Cc: gmarco@giovannelli.it, current@FreeBSD.ORG, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (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 +----[ Christopher Knight ]--------------------------------------------- | At 12:49 AM 1/17/99 +0100, Gianmarco Giovannelli wrote: | > | >Ok, first the conclusion... | > | >I am not able to boot anymore from a 3.0-current system while I can boot | >quite nicely from the 3.0-RELEASE generic kernel. | > | >The system hangs on checking the scsi chain and remains stopped here. The | >last thing I can see on the screen is the : | >Waiting 3 seconds for SCSI devices to settle | > | >And nothing else happens anymore. So I have to hard reset the box. | | | I have been seeing this for the two weeks or so. A shutdown -r will always | hang. A complete powerdown has been the only way I can reboot my box of late. I recently (last night) added USB support to my kernel (just to see :-) and it hung at the same place. Removing the USB entries fixed it. This was also at the same time as the syscons/atkbd changeover for me as well so I wasn't expecting it really to be the USB driver (since I have no USB devices). If you have USB support compiled in try removing it. -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|Specialist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 16 19:14:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24940 for freebsd-scsi-outgoing; Sat, 16 Jan 1999 19:11:20 -0800 (PST) (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 TAA24910 for ; Sat, 16 Jan 1999 19:11:14 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id EAA01589 for freebsd-scsi@FreeBSD.ORG; Sun, 17 Jan 1999 04:11:11 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id E5ED51573; Sun, 17 Jan 1999 01:25:50 +0100 (CET) Date: Sun, 17 Jan 1999 01:25:50 +0100 From: Ollivier Robert To: freebsd-scsi@FreeBSD.ORG Subject: Re: Symbios 875 activity LED? Message-ID: <19990117012550.A71523@keltia.freenix.fr> Mail-Followup-To: freebsd-scsi@FreeBSD.ORG References: <199901162125.PAA00326@nospam.hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901162125.PAA00326@nospam.hiwaay.net>; from David Kelly on Sat, Jan 16, 1999 at 03:25:51PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4931 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to David Kelly: > otherwise unused "Turbo LED" wires. Observed the internal LED works at > boot time. And lights the external too. But still not under FreeBSD. > There was some talk of this long time ago. Did it not make it into the > distribution? Add the following to your config. file. Why it is not the default just escape me... options SCSI_NCR_SYMBIOS_COMPAT # for LEDs -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #67: Tue Dec 29 20:24:02 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 16 20:54:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02810 for freebsd-scsi-outgoing; Sat, 16 Jan 1999 20:54:55 -0800 (PST) (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 UAA02802 for ; Sat, 16 Jan 1999 20:54:53 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt2-141.HiWAAY.net [208.147.148.141]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id WAA19924 for ; Sat, 16 Jan 1999 22:54:49 -0600 (CST) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.1/8.9.1) with ESMTP id WAA00625 for ; Sat, 16 Jan 1999 22:01:49 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199901170401.WAA00625@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: Symbios 875 activity LED? In-reply-to: Message from Ollivier Robert of "Sun, 17 Jan 1999 01:25:50 +0100." <19990117012550.A71523@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Jan 1999 22:01:49 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ollivier Robert writes: > According to David Kelly: > > otherwise unused "Turbo LED" wires. Observed the internal LED works at > > boot time. And lights the external too. But still not under FreeBSD. > > There was some talk of this long time ago. Did it not make it into the > > distribution? > > Add the following to your config. file. Why it is not the default just > escape me... > > options SCSI_NCR_SYMBIOS_COMPAT # for LEDs Done! Have rebooted 18 times today. Looks like another is on the way. I've had the darndest problems with a pure elf kernel (first time I've tried that). It seems that when I'd do a "shutdown -r" as myself (a member of group "operator") that /etc/nologin was not being deleted. Proceeded to update /etc/rc* for proper /modules loading. That didn't help. Think when I changed out /etc/login.conf things got fixed. Am thinking as soon as "make buildworld" is fixed again it is time for a clean disk reinstall. BTW: not only is the above option not in GENERIC, its not in LINT either. Looked there (actually for other things) before posting. Grep just found it for me in /usr/src/sys/pci/ncr.c. You mean this is all there was to it and I've been without a blinking light all this time? You mean all they had to do was smack one tiny tiny little bit? Doesn't seem worth and ifdef. :-) Can only assume somebody knows more than I do and this is really important to keep from breaking something. #ifdef SCSI_NCR_SYMBIOS_COMPAT if (!(np->rv_gpcntl & 0x01)) np->features |= FE_LED0; #if 0 /* Not safe enough without NVRAM support or user settable option */ if (!(INB(nc_gpreg) & 0x08)) np->features |= FE_DIFF; #endif #endif /* SCSI_NCR_SYMBIOS_COMPAT */ -- 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