From owner-freebsd-scsi Sun Sep 19 14: 9:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by hub.freebsd.org (Postfix) with ESMTP id 8C65B156CF for ; Sun, 19 Sep 1999 14:09:57 -0700 (PDT) (envelope-from papalia@UDel.Edu) Received: from morgaine.avalon.com (host75-157.student.udel.edu [128.175.75.157]) by copland.udel.edu (8.9.3/8.9.3) with SMTP id RAA22358 for ; Sun, 19 Sep 1999 17:10:03 -0400 (EDT) Message-Id: <4.1.19990919170554.009486c0@unix01.voicenet.com> X-Sender: jpapalia@unix01.voicenet.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 19 Sep 1999 17:08:13 -0400 To: freebsd-scsi@freebsd.org From: John Subject: Raid Drivers Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey all... I posted this question to freebsd-questions, and the answer left me hope, but I was hoping to get more details. If I understand the mail archives correctly, someone was planning on working for a driver for the Dell Perc2/SC raid controller. Any update on that? The reason I'm asking is that my boss is looking at installing 5 servers, and I'll be picking the OS. I'd like to go with FreeBSD, but if the driver won't be out in the next couple of months, I'll need to scramble to pick something different (which I'd rather not do :) ) Thanks in advance!!! --John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 19 21:36: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dingo.cdrom.com (castles524.castles.com [208.214.165.88]) by hub.freebsd.org (Postfix) with ESMTP id 1BB0215132 for ; Sun, 19 Sep 1999 21:36:00 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA28580; Sun, 19 Sep 1999 21:28:50 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909200428.VAA28580@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Cc: freebsd-scsi@freebsd.org Subject: Re: Raid Drivers In-reply-to: Your message of "Sun, 19 Sep 1999 17:08:13 EDT." <4.1.19990919170554.009486c0@unix01.voicenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Sep 1999 21:28:50 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Don't expect a driver for the Perc (really an AMI MegaRAID) anytime before the 4.0 release. There are a number of issues to deal with before we can even start looking at a driver. > I posted this question to freebsd-questions, and the answer left me hope, > but I was hoping to get more details. If I understand the mail archives > correctly, someone was planning on working for a driver for the Dell > Perc2/SC raid controller. Any update on that? The reason I'm asking is > that my boss is looking at installing 5 servers, and I'll be picking the > OS. I'd like to go with FreeBSD, but if the driver won't be out in the > next couple of months, I'll need to scramble to pick something different > (which I'd rather not do :) ) I'd suggest that if you *must* have hardware raid, get an external unit like an Infortrend. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Sun Sep 19 22: 0:51 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from localhost.primenet.com (207-218-5-157.nas-1.SCF.primenet.com [207.218.5.157]) by hub.freebsd.org (Postfix) with ESMTP id DCEE114CB7 for ; Sun, 19 Sep 1999 22:00:44 -0700 (PDT) (envelope-from jreynold@primenet.com) Received: (from jreynold@localhost) by localhost.primenet.com (8.9.3/8.9.3) id WAA00623; Sun, 19 Sep 1999 22:02:45 -0700 (MST) (envelope-from jreynold@primenet.com) From: John and Jennifer Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14309.49140.814045.451806@localhost.primenet.com> Date: Sun, 19 Sep 1999 22:02:44 -0700 (MST) To: freebsd-scsi@freebsd.org Subject: How to tell if a quirk "worked"? X-Mailer: VM 6.73 under Emacs 20.3.1 Cc: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, In -questions, I've been running a thread about my difficulties getting a TapeStor 8000 (TR4) to dump(8) properly. Here is a quick synopsys of my difficulties: o I cannot get multiple files onto a tape by issuing sequential dump(8) commands (using /dev/nrsa0 of course) using the -a "auto-size" option to dump(8). Yes, I've rewound, erased, retentioned my life away. o If I use "dump 0uBbf 4000000 10 /dev/nrsa0 filesystem" I can get multiple dumps to run in a row but cannot "restore -i" any file except for the first one. A "restore -b 10 -s 2 -i" to get to the second dump on the tape will fail with a "tape read error: Undefined error: 0" and rewind. I can do restore -i on the first dump file on the tape. In my /var/log/messages file, I received the following messages: (sa0:ahc0:0:2:0): unable to backspace over one of double filemarks at end of tape (sa0:ahc0:0:2:0): it is possible that this device needs a SA_QUIRK_1FM quirk set for it I did a "recursive" grep of every .h and .c in /usr/src looking for those error messages but couldn't find them. Notwithstanding that, I went and edited cam/scsi/scsi_sa.c and put the following quirk entry: { { T_SEQUENTIAL, SIP_MEDIA_REMOVABLE, "SEAGATE", "Seagate STT8000*", "*"}, SA_QUIRK_FIXED|SA_QUIRK_1FM, 512 }, I'm just guessing that was correct from reading the header files, etc. I copied this from the HP T4000 tape entry so I don't know if the FIXED quirk needs to be there or if a good block size is 512. However, how does one know if a "quirk" is applied correctly? I'm assuming that the '*' in the product and revision fields are for wild carding. I'm asking this because after recompiling my kernel with this change in scsi_sa.c, I see no differences in tape drive behavior. How can I tell if CAM is "applying" the quirk (don't know the right terminology here) to my drive? My boot message for the drive is: sa0 at ahc0 bus 0 target 2 lun 0 sa0: Removable Sequential Access SCSI-2 device The truly strange part about this that I've gotten mail from Bryce Newall stating that his Seagate ST8000N works like a charm. The only difference is that he's got an older ROM onboard. His boot message shows sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device Does anybody out there on this list have an STT8000N with my ROM version -AND- have it working under 3.3-STABLE? If nothing at all, I'd like to know about the quirk thing above. Thanks in advance for any help. -Jr ps: the drive functions flawlessly under Ebola98 and their software, so I don't think I can blame hardware--except for possibily inducing stupidity into the equation between ROM 3.16 and 4.11 .... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jreynold@primenet.com FreeBSD 3.3-STABLE. FreeBSD: The Power to Serve. http://www.primenet.com/~jreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 19 22:18:51 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3373715248 for ; Sun, 19 Sep 1999 22:18:49 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id WAA01420; Sun, 19 Sep 1999 22:17:13 -0700 Date: Sun, 19 Sep 1999 22:18:48 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John and Jennifer Reynolds Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: How to tell if a quirk "worked"? In-Reply-To: <14309.49140.814045.451806@localhost.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Hello all, > > In -questions, I've been running a thread about my difficulties getting a > TapeStor 8000 (TR4) to dump(8) properly. Here is a quick synopsys of my > difficulties: Some of us don't read -questions, so that's why I haven't seen this... > > o I cannot get multiple files onto a tape by issuing sequential dump(8) > commands (using /dev/nrsa0 of course) using the -a "auto-size" option to > dump(8). Yes, I've rewound, erased, retentioned my life away. > > o If I use "dump 0uBbf 4000000 10 /dev/nrsa0 filesystem" I can get multiple > dumps to run in a row but cannot "restore -i" any file except for the first > one. A "restore -b 10 -s 2 -i" to get to the second dump on the tape will fail > with a "tape read error: Undefined error: 0" and rewind. I can do restore -i > on the first dump file on the tape. That one I don't know about. > > In my /var/log/messages file, I received the following messages: > > (sa0:ahc0:0:2:0): unable to backspace over one of double filemarks at end of tape > (sa0:ahc0:0:2:0): it is possible that this device needs a SA_QUIRK_1FM quirk set for it You can also, when the tape is loaded to BOT, do: mt -f /dev/nrsa0 seteotmodel 1 See the mt(1) man page for this. > > I did a "recursive" grep of every .h and .c in /usr/src looking for those error > messages but couldn't find them. Notwithstanding that, I went and edited in scsi_sa.c:sa_close: case SA_MODE_NOREWIND: /* * If we're not rewinding/unloading the tape, find out * whether we need to back up over one of two filemarks * we wrote (if we wrote two filemarks) so that appends * from this point on will be sane. */ if (error == 0 && writing && (softc->quirks & SA_QUIRK_2FM)) { tmp = saspace(periph, -1, SS_FILEMARKS); if (tmp) { xpt_print_path(periph->path); printf("unable to backspace over one of double" " filemarks at end of tape\n"); xpt_print_path(periph->path); printf("it is possible that this device " " needs a SA_QUIRK_1FM quirk set for it\n"); softc->flags |= SA_FLAG_TAPE_FROZEN; } } I now see, much to my embarrassment, that I forgot to document a "FROZEN" state- if the the driver thinks it has lost where things are on the tape, it won't let you do anything but rewind, seek to end of tape, or unload the tape. When any of these actions occur, normal tape operations consistent with that state may resume. > cam/scsi/scsi_sa.c and put the following quirk entry: > > { > { T_SEQUENTIAL, SIP_MEDIA_REMOVABLE, "SEAGATE", > "Seagate STT8000*", "*"}, SA_QUIRK_FIXED|SA_QUIRK_1FM, 512 > }, > > I'm just guessing that was correct from reading the header files, etc. I copied > this from the HP T4000 tape entry so I don't know if the FIXED quirk needs to > be there or if a good block size is 512. However, how does one know if a > "quirk" is applied correctly? I'm assuming that the '*' in the product and > revision fields are for wild carding. I'm asking this because after recompiling > my kernel with this change in scsi_sa.c, I see no differences in tape drive > behavior. How can I tell if CAM is "applying" the quirk (don't know the right > terminology here) to my drive? My boot message for the drive is: > > sa0 at ahc0 bus 0 target 2 lun 0 > sa0: Removable Sequential Access SCSI-2 device If you set CAMDEBUG, a quirk match will trigger this code in saregister: #ifdef CAMDEBUG xpt_print_path(periph->path); printf("found quirk entry %d\n", ((struct sa_quirk_entry *) match) - sa_quirk_table); #endif > > The truly strange part about this that I've gotten mail from Bryce Newall > stating that his Seagate ST8000N works like a charm. The > only difference is that he's got an older ROM onboard. His boot message shows > > sa0 at ahc0 bus 0 target 5 lun 0 > sa0: Removable Sequential Access SCSI-2 device The above quirk likely should be: { { T_SEQUENTIAL, SIP_MEDIA_REMOVABLE, "SEAGATE ", "STT8000*", "*"}, SA_QUIRK_FIXED|SA_QUIRK_1FM, 512 }, > > ps: the drive functions flawlessly under Ebola98 and their software, so I don't > think I can blame hardware--except for possibily inducing stupidity into the > equation between ROM 3.16 and 4.11 .... > !$&!)%(&!)@(%!()@%_(!)@%)_(!@%!!!!!!!###!! :-} -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 19 22:45: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from localhost.primenet.com (207-218-5-157.nas-1.SCF.primenet.com [207.218.5.157]) by hub.freebsd.org (Postfix) with ESMTP id 4F54514BDE for ; Sun, 19 Sep 1999 22:45:02 -0700 (PDT) (envelope-from jreynold@primenet.com) Received: (from jreynold@localhost) by localhost.primenet.com (8.9.3/8.9.3) id WAA00856; Sun, 19 Sep 1999 22:46:58 -0700 (MST) (envelope-from jreynold@primenet.com) From: John and Jennifer Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14309.51794.537121.179915@localhost.primenet.com> Date: Sun, 19 Sep 1999 22:46:58 -0700 (MST) To: mjacob@feral.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: How to tell if a quirk "worked"? In-Reply-To: References: <14309.49140.814045.451806@localhost.primenet.com> X-Mailer: VM 6.73 under Emacs 20.3.1 Cc: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ On Sunday, September 19, Matthew Jacob wrote: ] > > Some of us don't read -questions, so that's why I haven't seen this... Good thing I put some history of my problem in ;-) > That one I don't know about. it was very strange indeed ... I guess it was a "restore" message, but why I got it, who knows. > You can also, when the tape is loaded to BOT, do: > > mt -f /dev/nrsa0 seteotmodel 1 Cool. I will try that. > printf("unable to backspace over one of double" > " filemarks at end of tape\n"); DOH ... my grepping was flawed ... I was looking for the whole string on a single line .... > I now see, much to my embarrassment, that I forgot to document a "FROZEN" > state- if the the driver thinks it has lost where things are on the tape, > it won't let you do anything but rewind, seek to end of tape, or unload > the tape. When any of these actions occur, normal tape operations consistent > with that state may resume. I should have also said I got a few of these in my syslog: (sa0:ahc0:0:2:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. Tonight, I did "mt rewind" on a tape I was fooling with yesterday and got the following in messages: (sa0:ahc0:0:2:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x8 (sa0:ahc0:0:2:0): Queuing a BDR SCB (sa0:ahc0:0:2:0): Bus Device Reset Message Sent (sa0:ahc0:0:2:0): no longer in timeout, status = anything of consequence? > > If you set CAMDEBUG, a quirk match will trigger this code in saregister: > > #ifdef CAMDEBUG > xpt_print_path(periph->path); > printf("found quirk entry %d\n", > ((struct sa_quirk_entry *) match) - sa_quirk_table); > #endif > > The above quirk likely should be: > > { > { T_SEQUENTIAL, SIP_MEDIA_REMOVABLE, "SEAGATE ", > "STT8000*", "*"}, SA_QUIRK_FIXED|SA_QUIRK_1FM, 512 > }, OK. I will redo the quirk like above and include CAMDEBUG (I was actually just reading cam(4) coincidentally :) and see if things improve. I will also do the setoetmodel that you suggested. > > [ works with Ebola98 ] > !$&!)%(&!)@(%!()@%_(!)@%)_(!@%!!!!!!!###!! :-} *definitely* Thanks for the response! It is quite late tonight so I'll get back to debugging this problem tomorrow. If it is a matter of the quirk being re-written slightly as you did above and things work, I'll send-pr with the trivial patch. I am curious to know if anybody else reading -scsi owns or knows of somebody who owns one of these TapeStor 8000 drives with ROM 4.11 in it? If so, are they experiencing the same wierdness? Thanks, -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jreynold@primenet.com FreeBSD 3.3-STABLE. FreeBSD: The Power to Serve. http://www.primenet.com/~jreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 19 22:54:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 311121560F for ; Sun, 19 Sep 1999 22:54:54 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id WAA01536; Sun, 19 Sep 1999 22:52:52 -0700 Date: Sun, 19 Sep 1999 22:54:26 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John and Jennifer Reynolds Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: How to tell if a quirk "worked"? In-Reply-To: <14309.51794.537121.179915@localhost.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I now see, much to my embarrassment, that I forgot to document a "FROZEN" > > state- if the the driver thinks it has lost where things are on the tape, > > it won't let you do anything but rewind, seek to end of tape, or unload > > the tape. When any of these actions occur, normal tape operations consistent > > with that state may resume. > > I should have also said I got a few of these in my syslog: > > (sa0:ahc0:0:2:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. > > Tonight, I did "mt rewind" on a tape I was fooling with yesterday and got the > following in messages: > > (sa0:ahc0:0:2:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x8 > (sa0:ahc0:0:2:0): Queuing a BDR SCB > (sa0:ahc0:0:2:0): Bus Device Reset Message Sent > (sa0:ahc0:0:2:0): no longer in timeout, status = > > anything of consequence? Take that one up with Justin Gibbs- his HBA driver.... > > > > > If you set CAMDEBUG, a quirk match will trigger this code in saregister: > > > > #ifdef CAMDEBUG > > xpt_print_path(periph->path); > > printf("found quirk entry %d\n", > > ((struct sa_quirk_entry *) match) - sa_quirk_table); > > #endif > > > > The above quirk likely should be: > > > > { > > { T_SEQUENTIAL, SIP_MEDIA_REMOVABLE, "SEAGATE ", > > "STT8000*", "*"}, SA_QUIRK_FIXED|SA_QUIRK_1FM, 512 > > }, > > OK. I will redo the quirk like above and include CAMDEBUG (I was actually just > reading cam(4) coincidentally :) and see if things improve. I will also do the > setoetmodel that you suggested. Yes- until this can be put into a boot time quirk table, the seteotmodel is a pain to remember. > > > > [ works with Ebola98 ] > > !$&!)%(&!)@(%!()@%_(!)@%)_(!@%!!!!!!!###!! :-} > > *definitely* > > Thanks for the response! It is quite late tonight so I'll get back to debugging > this problem tomorrow. If it is a matter of the quirk being re-written slightly > as you did above and things work, I'll send-pr with the trivial patch. Sure thing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 19 23:27: 1 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 6A44014CAC for ; Sun, 19 Sep 1999 23:26:59 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA78694; Mon, 20 Sep 1999 00:26:52 -0600 (MDT) (envelope-from ken) Message-Id: <199909200626.AAA78694@panzer.kdm.org> Subject: Re: How to tell if a quirk "worked"? In-Reply-To: from Matthew Jacob at "Sep 19, 1999 10:54:26 pm" To: mjacob@feral.com Date: Mon, 20 Sep 1999 00:26:52 -0600 (MDT) Cc: jreynold@primenet.com (John and Jennifer Reynolds), freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (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 Matthew Jacob wrote... > > > I now see, much to my embarrassment, that I forgot to document a "FROZEN" > > > state- if the the driver thinks it has lost where things are on the tape, > > > it won't let you do anything but rewind, seek to end of tape, or unload > > > the tape. When any of these actions occur, normal tape operations consistent > > > with that state may resume. > > > > I should have also said I got a few of these in my syslog: > > > > (sa0:ahc0:0:2:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. > > > > Tonight, I did "mt rewind" on a tape I was fooling with yesterday and got the > > following in messages: > > > > (sa0:ahc0:0:2:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x8 > > (sa0:ahc0:0:2:0): Queuing a BDR SCB > > (sa0:ahc0:0:2:0): Bus Device Reset Message Sent > > (sa0:ahc0:0:2:0): no longer in timeout, status = > > > > anything of consequence? > > Take that one up with Justin Gibbs- his HBA driver.... Timed out while idle generally indicates that the command in question timed out. i.e. the timeout for the rewind may be too short for that drive. (Or it could be another command, if something else is done before the rewind.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 20 14:12:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7E32814C21 for ; Mon, 20 Sep 1999 14:12:45 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id RAA21248; Mon, 20 Sep 1999 17:12:18 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA35442; Mon, 20 Sep 1999 17:11:48 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 20 Sep 1999 17:11:48 -0400 (EDT) To: scsi@FreeBSD.ORG Subject: Re: data corruption when using aic7890 -- FIXED In-Reply-To: References: <199909150836.BAA17105@salsa.gv.tsc.tdk.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14310.41323.508001.549560@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For the benefit of everybody following this thread: Justin has committed a fix to aic7xxx.seq to -current and -stable which fixes the aic7890 data corruption problem. I've been been testing this patch with my exhaustive corruption test for well over 72 hours with no errors. Thank you, Justin!! Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 PS: The log: gibbs 1999/09/20 11:57:05 PDT Modified files: sys/dev/aic7xxx aic7xxx.seq Log: Work around a defect in the FIFOEMP status bit of Ultra2 class aic7xxx parts. This problem could result in data corruption during periods of my PCI bus load by busmasters other than the aic7xxx. Many thanks to Andrew Gallatin for characterizing the symptoms of this problem and testing this fix. Revision Changes Path 1.91 +33 -3 src/sys/dev/aic7xxx/aic7xxx.seq (MFC'ed as rev 1.84.2.7). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 20 22: 5:56 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id 734C8153F8 for ; Mon, 20 Sep 1999 22:05:43 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 3218 invoked from network); 21 Sep 1999 05:05:42 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 21 Sep 1999 05:05:42 -0000 Date: Mon, 20 Sep 1999 22:05:37 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Andrew Gallatin Cc: scsi@FreeBSD.ORG Subject: Re: data corruption when using aic7890 -- FIXED In-Reply-To: <14310.41323.508001.549560@grasshopper.cs.duke.edu> 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 Yet another reason FreeBSD is such a great OS. A commercial vendor wouldn't have admitted it had a problem, and then fixed it after 2 years. Thanks for the detective work and the repair job Andrew and Justin. On Mon, 20 Sep 1999, Andrew Gallatin wrote: > > For the benefit of everybody following this thread: > > Justin has committed a fix to aic7xxx.seq to -current and -stable > which fixes the aic7890 data corruption problem. I've been been > testing this patch with my exhaustive corruption test for well over 72 > hours with no errors. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 21 11:57: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from internal.mail.demon.net (internal.mail.demon.net [193.195.224.3]) by hub.freebsd.org (Postfix) with ESMTP id 31017151B0 for ; Tue, 21 Sep 1999 11:57:00 -0700 (PDT) (envelope-from fanf@demon.net) Received: from fanf.eng.demon.net (fanf.eng.demon.net [195.11.55.89]) by internal.mail.demon.net with ESMTP id TAA24044; Tue, 21 Sep 1999 19:56:53 +0100 (BST) Received: from fanf by fanf.eng.demon.net with local (Exim 3.03 #2) id 11TV5X-0006fH-00; Tue, 21 Sep 1999 19:56:27 +0100 From: Tony Finch To: scsi@freebsd.org Cc: Tony Finch Subject: status of DPT SmartRAID iv Message-Id: Date: Tue, 21 Sep 1999 19:56:27 +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone got the DPT userland utilities in /usr/src/usr.sbin/dpt to compile? Do they work? If not, how hard is it to make them work? All we really need is something that can tell us the status of the disks in the RAID -- with hot-swappable drives we can replace the broken one and the DPT will rebuild the RAID without interrupting service. The only problem is that (a) we need to know that a drive is funted, and (b) which one it is. (I'm not on this list so CC:s of replies are appreciated.) Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net e pluribus unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 21 15: 3:41 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from baklava.alt.net (baklava.alt.net [207.14.113.9]) by hub.freebsd.org (Postfix) with ESMTP id D9B181520F for ; Tue, 21 Sep 1999 15:03:36 -0700 (PDT) (envelope-from ccaputo@alt.net) Received: from baklava.alt.net (ccaputo@baklava.alt.net [207.14.113.9]) by baklava.alt.net (8.9.3/8.7.3) with SMTP id PAA10331; Tue, 21 Sep 1999 15:03:34 -0700 (PDT) Date: Tue, 21 Sep 1999 15:03:32 -0700 (PDT) From: Chris Caputo To: scsi@FreeBSD.ORG Subject: timed out in dataout phase In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am seeing the following crash every day or two: (da1:ahc0:0:1:0): SCB 0xe - timed out in dataout phase, SEQADDR == 0x5c (da1:ahc0:0:1:0): BDR message in message buffer (da1:ahc0:0:1:0): SCB 0xe - timed out in dataout phase, SEQADDR == 0x5d (da1:ahc0:0:1:0): no longer in timeout, status = 34b ahc0: Issued channel A Bus Reset, 3 SCBs aborted This is a on a ASUS P2B-LS. Any ideas on how to work around? Thanks! Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 21 15:15: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id DBEC01543E for ; Tue, 21 Sep 1999 15:15:01 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA91715; Tue, 21 Sep 1999 16:14:43 -0600 (MDT) (envelope-from ken) Message-Id: <199909212214.QAA91715@panzer.kdm.org> Subject: Re: timed out in dataout phase In-Reply-To: from Chris Caputo at "Sep 21, 1999 03:03:32 pm" To: ccaputo@alt.net (Chris Caputo) Date: Tue, 21 Sep 1999 16:14:43 -0600 (MDT) Cc: scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (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 Chris Caputo wrote... > I am seeing the following crash every day or two: > > (da1:ahc0:0:1:0): SCB 0xe - timed out in dataout phase, SEQADDR == 0x5c > (da1:ahc0:0:1:0): BDR message in message buffer > (da1:ahc0:0:1:0): SCB 0xe - timed out in dataout phase, SEQADDR == 0x5d > (da1:ahc0:0:1:0): no longer in timeout, status = 34b > ahc0: Issued channel A Bus Reset, 3 SCBs aborted > > This is a on a ASUS P2B-LS. > > Any ideas on how to work around? You probably have a cabling or termination problem. You can also see these types of problems if your SCSI cables are too close to the power supply. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 21 16:56: 2 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from armadillo.yoyo.org (armadillo.yoyo.org [195.40.6.65]) by hub.freebsd.org (Postfix) with SMTP id 93A1B14DF7 for ; Tue, 21 Sep 1999 16:55:54 -0700 (PDT) (envelope-from matts@yoyo.org) Received: (qmail 20131 invoked by uid 1975); 21 Sep 1999 23:55:50 -0000 Date: Wed, 22 Sep 1999 00:55:49 +0100 From: Matt Saunders To: freebsd-scsi@freebsd.org Subject: DPT tools Message-ID: <19990922005549.A16334@yoyo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: Yoyo Internet Services Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a DPT SmartRAID IV controller which has happily been running a mail service for the past year or so on a FreeBSD 3.2-REL box. Reading through LINT today I've discovered the utilities hiding away in /usr/src/usr.sbin/dpt/ but I can't get them built... root@omega[/usr/src/usr.sbin/dpt]# make ===> dpt_ctlinfo Warning: Object directory not changed from original /usr/src/usr.sbin/dpt/dpt_ctlinfo cc -O -pipe -Wall -I/usr/src/usr.sbin/dpt/dpt_ctlinfo/../../../sys -c dpt_ctlinfo.c dpt_ctlinfo.c:43: scsi/scsi_all.h: No such file or directory dpt_ctlinfo.c:44: scsi/scsi_message.h: No such file or directory dpt_ctlinfo.c:45: scsi/scsiconf.h: No such file or directory dpt_ctlinfo.c:49: sys/dpt.h: No such file or directory There are further errors but these are caused by the problem I've pasted here. I've found the missing include files (except scsiconf.h) in /usr/include/cam/ but that doesn't help me get this stuff compiled. :-( Am I missing something? Is there a way to get these tools compiled without resorting to hacking the Makefiles? Thanks in advance for any suggestions. Regards, Matt. -- matts@yoyo.org "Circular logic will only make http://www.yoyo.org/ you dizzy." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 21 16:59:37 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E1185150D2 for ; Tue, 21 Sep 1999 16:59:35 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id QAA09154; Tue, 21 Sep 1999 16:57:44 -0700 Date: Tue, 21 Sep 1999 16:57:44 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Matt Saunders Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: DPT tools In-Reply-To: <19990922005549.A16334@yoyo.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This looks like this is depending on 2.2.X includes. On Wed, 22 Sep 1999, Matt Saunders wrote: > Hi, > > I have a DPT SmartRAID IV controller which has happily been running a > mail service for the past year or so on a FreeBSD 3.2-REL box. > > Reading through LINT today I've discovered the utilities hiding > away in /usr/src/usr.sbin/dpt/ but I can't get them built... > > root@omega[/usr/src/usr.sbin/dpt]# make > ===> dpt_ctlinfo > Warning: Object directory not changed from original > /usr/src/usr.sbin/dpt/dpt_ctlinfo > cc -O -pipe -Wall -I/usr/src/usr.sbin/dpt/dpt_ctlinfo/../../../sys > -c dpt_ctlinfo.c > dpt_ctlinfo.c:43: scsi/scsi_all.h: No such file or directory > dpt_ctlinfo.c:44: scsi/scsi_message.h: No such file or directory > dpt_ctlinfo.c:45: scsi/scsiconf.h: No such file or directory > dpt_ctlinfo.c:49: sys/dpt.h: No such file or directory > > There are further errors but these are caused by the problem I've > pasted here. I've found the missing include files (except scsiconf.h) > in /usr/include/cam/ but that doesn't help me get this stuff > compiled. :-( > > Am I missing something? Is there a way to get these tools compiled > without resorting to hacking the Makefiles? > > Thanks in advance for any suggestions. > > > Regards, > Matt. > -- > matts@yoyo.org "Circular logic will only make > http://www.yoyo.org/ you dizzy." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 22 8: 1:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from localhost.primenet.com (206-132-48-129.nas-1.SCF.primenet.com [206.132.48.129]) by hub.freebsd.org (Postfix) with ESMTP id 25BBE1585C for ; Wed, 22 Sep 1999 08:01:51 -0700 (PDT) (envelope-from jreynold@primenet.com) Received: (from jreynold@localhost) by localhost.primenet.com (8.9.3/8.9.3) id IAA07253; Wed, 22 Sep 1999 08:03:48 -0700 (MST) (envelope-from jreynold@primenet.com) From: John and Jennifer Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14312.61395.807193.436425@localhost.primenet.com> Date: Wed, 22 Sep 1999 08:03:47 -0700 (MST) To: freebsd-scsi@freebsd.org Subject: new quirk entry for my seagate tape (please commit) X-Mailer: VM 6.73 under Emacs 20.3.1 Cc: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Could one of you fine commiters commit the attached patch to /usr/src/sys/cam/scsi/scsi_sa.c ? I finally got my new Seagate TapeStor 8000 drive working with the advice of several on this list. The trick turned out to be using "mt seteotmodel 1" to make the SA driver deal with just 1 filemark at EOT. Everything seems to be peachy now. The following quirk entry makes things work peachy as well without having to remember the 'mt' command before backing up. I'm using 3.3-STABLE (CVSup'ed very recently ... I believe last sunday) and I would imagine that the patch would apply to -current as well. (I didn't know if I should send-pr for such a small patch ...) Thanks, and thanks for everybody's help!!!!! -Jr --- scsi_sa.c Tue Sep 21 01:18:26 1999 +++ scsi_sa.c.new Wed Sep 22 07:17:36 1999 @@ -213,6 +213,10 @@ static struct sa_quirk_entry sa_quirk_table[] = { + { + { T_SEQUENTIAL, SIP_MEDIA_REMOVABLE, "Seagate", + "STT8000N*", "*"}, SA_QUIRK_1FM, 0 + }, { { T_SEQUENTIAL, SIP_MEDIA_REMOVABLE, "ARCHIVE", "Python 25601*", "*"}, SA_QUIRK_NOCOMP, 0 @@ -544,7 +548,7 @@ printf("unable to backspace over one of double" " filemarks at end of tape\n"); xpt_print_path(periph->path); - printf("it is possible that this device " + printf("it is possible that this device" " needs a SA_QUIRK_1FM quirk set for it\n"); softc->flags |= SA_FLAG_TAPE_FROZEN; -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jreynold@primenet.com FreeBSD 3.3-STABLE. FreeBSD: The Power to Serve. http://www.primenet.com/~jreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 22 9:30:16 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 908A9154CE for ; Wed, 22 Sep 1999 09:30:11 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA01492; Wed, 22 Sep 1999 09:28:07 -0700 Date: Wed, 22 Sep 1999 09:28:07 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John and Jennifer Reynolds Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: new quirk entry for my seagate tape (please commit) In-Reply-To: <14312.61395.807193.436425@localhost.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I'm using 3.3-STABLE (CVSup'ed very recently ... I believe last sunday) and I > would imagine that the patch would apply to -current as well. > > (I didn't know if I should send-pr for such a small patch ...) Nope, got it, thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 23 15:15:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front5.grolier.fr (front5.grolier.fr [194.158.96.55]) by hub.freebsd.org (Postfix) with ESMTP id 56ADA14D7A for ; Thu, 23 Sep 1999 15:15:45 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-162-123.villette.club-internet.fr [195.36.162.123]) by front5.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id AAA07542 for ; Fri, 24 Sep 1999 00:14:56 +0200 (MET DST) Date: Fri, 24 Sep 1999 00:35:33 +0200 (MET DST) From: Gerard Roudier X-Sender: groudier@localhost Reply-To: Gerard Roudier To: scsi@FreeBSD.ORG Subject: Some SYM53C896 benchmarks Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-1785991469-938125182=:349" Content-ID: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --8323328-1785991469-938125182=:349 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Content-ID: PII-233 / SYM53C896 / SnapShot 07/05/99 1) Using disklate.c (only works with disks that do not remove from =20 their cache data previously read) DDRS 34560W at 40 MB/s data transfers ncr: Command overhead 230 us - Transfer speed 23 MB/s sym_hipd: Command overhead 149 us - Transfer speed 34 MB/s XP32275W at 40 MB/s data transfers ncr: Command overhead 409 us - Transfer speed 23 MB/s sym_hipd: Command overhead 310 us - Transfer speed 34 MB/s 2) For the Cheatah2 LVD and the DRVS LVD, disklate is not usable since=20 these drives seem to remove data previouly read from their cache. I just tried to perform small sequential IOs read (1Kb) using dd, from= =20 the both drives at the same time (connected to the same SCSI BUS). ncr: 6000 Tps sym_hipd: 11500 Tps For test (1), the difference in latency seems to me explainable, but the=20 difference in transfers speed is strange to me. Will try to understand=20 more. I am also asking me questions about results of test 2. Under Linux I can get up to 8000 Tps in the same conditions using the generic ncr53c8xx driver and about 11500 (same as the sym_hipd driver as expected) using the sym53c8xx that takes advantage of the features of the SYM53C896.=20 I recently read a post at this list that reported a SYM53C895 in LVD mode 80 MB/s being slower that an adaptec board in SE mode (40 MB/s) using same hard disks and stock drivers. The numbers above may explain the results and let me think that the 895 was not the cause of the bad results. It would be fair, to give a try to the sym_hipd driver in the same situation and report results, even if I have only announced the sym_hipd driver as being optimized for the 896 and friends (may-be it can also help for the 895 as it does under Linux). Thanks. (The sym_hipd driver is still experimental)=20 G=E9rard. PS: I have attached disklate.c which is not from me, but that had been=20 posted to a FreeBSD list years ago. --8323328-1785991469-938125182=:349 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="disklate.c" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: I2luY2x1ZGUgPHN5cy90eXBlcy5oPg0KI2luY2x1ZGUgPHN5cy90aW1lLmg+ DQojaW5jbHVkZSA8ZmNudGwuaD4NCiNpbmNsdWRlIDxzdGRpby5oPg0KI2lu Y2x1ZGUgPHVuaXN0ZC5oPg0KDQojZGVmaW5lIElURVJBVElPTlMJMjAwMA0K DQpzdGF0aWMgaW50IHN5c2Vycm9yKGNvbnN0IGNoYXIgKndoZXJlKTsNCnN0 YXRpYyBsb25nIHRpbWVpdChpbnQgZmQsIGNoYXIgKmJ1ZiwgdW5zaWduZWQg YmxvY2tzaXplKTsNCg0KaW50IG1haW4oaW50IGFyZ2MsIGNoYXIgKiphcmd2 KQ0Kew0KICAgIGNoYXIgYnVmWzIgKiA0MDk2XTsNCiAgICBpbnQgZmQ7DQog ICAgbG9uZyB0aW1lXzQwOTY7DQogICAgbG9uZyB0aW1lXzgxOTI7DQoNCiAg ICBpZiAoYXJnYyAhPSAyKQ0KICAgIHsNCglmcHJpbnRmKHN0ZGVyciwgInVz YWdlOiAlcyBkZXZpY2VcbiIsIGFyZ3ZbMF0pOw0KCWV4aXQoMSk7DQogICAg fQ0KICAgIGZkID0gb3Blbihhcmd2WzFdLCBPX1JET05MWSk7DQogICAgaWYg KGZkID09IC0xKQ0KCXN5c2Vycm9yKCJvcGVuIik7DQogICAgdGltZV80MDk2 ID0gdGltZWl0KGZkLCBidWYsIDQwOTYpOw0KICAgIHRpbWVfODE5MiA9IHRp bWVpdChmZCwgYnVmLCA4MTkyKTsNCiAgICBwcmludGYoIkNvbW1hbmQgb3Zl cmhlYWQgaXMgJWxkIHVzZWMgKHRpbWVfNDA5NiA9ICVsZCwgdGltZV84MTky ID0gJWxkKVxuIiwNCgkgICAodGltZV80MDk2IC0gKHRpbWVfODE5MiAtIHRp bWVfNDA5NikpIC8gSVRFUkFUSU9OUywNCgkgICB0aW1lXzQwOTYgLyBJVEVS QVRJT05TLCB0aW1lXzgxOTIgLyBJVEVSQVRJT05TKTsNCiAgICBwcmludGYo InRyYW5zZmVyIHNwZWVkIGlzICVnIGJ5dGVzL3NlY1xuIiwNCgkgICA0MDk2 ICogSVRFUkFUSU9OUyAqIDEwMDAwMDAuMCAvICh0aW1lXzgxOTIgLSB0aW1l XzQwOTYpKTsNCiAgICBleGl0KDApOw0KfQ0KDQpzdGF0aWMgaW50IHN5c2Vy cm9yKGNvbnN0IGNoYXIgKndoZXJlKQ0Kew0KICAgIHBlcnJvcih3aGVyZSk7 DQogICAgZXhpdCgxKTsNCn0NCg0Kc3RhdGljIGxvbmcgdGltZWl0KGludCBm ZCwgY2hhciAqYnVmLCB1bnNpZ25lZCBibG9ja3NpemUpDQp7DQogICAgc3Ry dWN0IHRpbWV2YWwgZmluaXNoOw0KICAgIGludCBpOw0KICAgIHN0cnVjdCB0 aW1ldmFsIHN0YXJ0Ow0KDQogICAgaWYgKHJlYWQoZmQsIGJ1ZiwgYmxvY2tz aXplKSAhPSBibG9ja3NpemUpDQoJc3lzZXJyb3IoInJlYWQiKTsNCiAgICBp ZiAoZ2V0dGltZW9mZGF5KCZzdGFydCwgKHN0cnVjdCB0aW1lem9uZSAqKU5V TEwpICE9IDApDQoJc3lzZXJyb3IoImdldHRpbWVvZmRheShzdGFydCkiKTsN CiAgICBmb3IgKGkgPSAwOyBpIDwgSVRFUkFUSU9OUzsgKytpKQ0KICAgIHsN CglpZiAobHNlZWsoZmQsIChvZmZfdCkwLCBTRUVLX1NFVCkgPT0gLTEpDQoJ ICAgIHN5c2Vycm9yKCJsc2VlayIpOw0KCWlmIChyZWFkKGZkLCBidWYsIGJs b2Nrc2l6ZSkgIT0gYmxvY2tzaXplKQ0KCSAgICBzeXNlcnJvcigicmVhZCIp Ow0KICAgIH0NCiAgICBpZiAoZ2V0dGltZW9mZGF5KCZmaW5pc2gsIChzdHJ1 Y3QgdGltZXpvbmUgKilOVUxMKSAhPSAwKQ0KCXN5c2Vycm9yKCJnZXR0aW1l b2ZkYXkoZmluaXNoKSIpOw0KICAgIHJldHVybiAoZmluaXNoLnR2X3NlYyAt IHN0YXJ0LnR2X3NlYykgKiAxMDAwMDAwDQoJICAgICsgZmluaXNoLnR2X3Vz ZWMgLSBzdGFydC50dl91c2VjOw0KfQ0K --8323328-1785991469-938125182=:349-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 24 7:17:27 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from thelab.hub.org (nat194.229.mpoweredpc.net [142.177.194.229]) by hub.freebsd.org (Postfix) with ESMTP id 5328C151D4; Fri, 24 Sep 1999 07:17:19 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id LAA09349; Fri, 24 Sep 1999 11:15:38 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 24 Sep 1999 11:15:38 -0300 (ADT) From: The Hermit Hacker To: freebsd-scsi@freebsd.org Cc: freebsd-stable@freebsd.org Subject: swap_pager: indefinite wait buffer Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm assuming a bad drive here, but any way of determining whch based on the 'device' entry? Sep 24 04:22:07 hub /kernel: swap_pager: indefinite wait buffer: device: 0x20439 , blkno: 2704, size: 4096 Thanks... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 25 5: 8:50 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rknebel.uplink.net (rknebel.uplink.net [209.173.88.243]) by hub.freebsd.org (Postfix) with ESMTP id 9131114C99 for ; Sat, 25 Sep 1999 05:08:44 -0700 (PDT) (envelope-from rknebel@rknebel.uplink.net) Received: (from rknebel@localhost) by rknebel.uplink.net (8.9.3/8.9.3) id IAA05588 for scsi@freebsd.org; Sat, 25 Sep 1999 08:08:04 -0400 (EDT) (envelope-from rknebel) Date: Sat, 25 Sep 1999 08:08:04 -0400 From: Rick Knebel To: scsi@freebsd.org Subject: scanner and scsi Message-ID: <19990925080804.C5411@rknebel.uplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I seem to be having trouble with my scsi scanner. I have two scsi cards. A ultra2scsi symbious card and a adaptec card. The symbious card is on scbus 0 and the adaptec card is on scbus 1. I have both scbus0 and scbus4 in my kernel. Here is an exert from my dmesg ncr0: rev 0x01 int a irq 9 on pci0.10.0 ahc0: rev 0x03 int a irq 10 on pci0.11.0 ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs Probing for devices on PCI bus 1: vga0: rev 0x11 int a irq 11 on pci1.0.0 Probing for PnP devices: CSN 1 Vendor ID: CTL00e4 [0xe4008c0e] Serial 0x1b940231 Comp ID: PNPb02f [0x2fb0 d041] Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 4 on isa sio2: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis wdc1: ATAPI streaming tapes not configured wdc1: unit 1 (atapi): , removable, accel, dma, io rdis acd0: drive speed 5512KB/sec, 256KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked wt0 not found at 0x300 mcd0 not found at 0x300 ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 15 seconds for SCSI devices to settle pass4 at ahc0 bus 0 target 0 lun 0 pass4: Fixed Scanner SCSI-2 device pass4: 3.300MB/s transfers changing root device to da1s1a cd0 at ncr0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 8.333MB/s transfers (8.333MHz, offset 31) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c losed da2 at ncr0 bus 0 target 2 lun 0 da2: Removable Direct Access SCSI-2 device da2: 3.300MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) p Here is the camcontrol devlist -v scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) scbus0 on ncr0 bus 0: at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) at scbus0 target 2 lun 0 (pass2,da2) at scbus0 target 6 lun 0 (pass3,cd0) < > at scbus0 target -1 lun -1 () scbus1 on ahc0 bus 0: at scbus1 target 0 lun 0 (pass4) < > at scbus1 target -1 lun -1 () My problem is the scanner on bootup is listed as pass 4 but there is no pass4 in the /dev directory. I have tried to make it but if I do ./MAKEDEV pass4 only pass 0-3 are made. I am not a real advanced user so if somone could help I would appreciate it. Thanks Rick -- Rick Knebel rknebel@uplink.net http://rknebel.uplink.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 25 5:11:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 89006150F5 for ; Sat, 25 Sep 1999 05:11:17 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1003) id CF600F80F; Sat, 25 Sep 1999 08:11:16 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id BFD889B09; Sat, 25 Sep 1999 08:11:16 -0400 (EDT) Date: Sat, 25 Sep 1999 08:11:16 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: Rick Knebel Cc: scsi@freebsd.org Subject: Re: scanner and scsi In-Reply-To: <19990925080804.C5411@rknebel.uplink.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 Sat, 25 Sep 1999, Rick Knebel wrote: > Hi, > I seem to be having trouble with my scsi scanner. > *snip* > > My problem is the scanner on bootup is listed as pass 4 but there is no > pass4 in the /dev directory. I have tried to make it but if I do ./MAKEDEV > pass4 only pass 0-3 are made. > ./MAKEDEV pass4 means that 4 pass devs are created (0-3). Try ./MAKEDEV pass5 to create 0-4. ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 25 5:38:38 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rknebel.uplink.net (rknebel.uplink.net [209.173.88.243]) by hub.freebsd.org (Postfix) with ESMTP id 1445314FA6 for ; Sat, 25 Sep 1999 05:38:33 -0700 (PDT) (envelope-from rknebel@rknebel.uplink.net) Received: (from rknebel@localhost) by rknebel.uplink.net (8.9.3/8.9.3) id IAA00325; Sat, 25 Sep 1999 08:37:46 -0400 (EDT) (envelope-from rknebel) Date: Sat, 25 Sep 1999 08:37:46 -0400 From: Rick Knebel To: "Chris D. Faulhaber" Cc: scsi@freebsd.org Subject: Re: scanner and scsi Message-ID: <19990925083746.A310@rknebel.uplink.net> References: <19990925080804.C5411@rknebel.uplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Chris D. Faulhaber on Sat, Sep 25, 1999 at 08:11:16AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Sep 25, 1999 at 08:11:16AM -0400, Chris D. Faulhaber wrote: > On Sat, 25 Sep 1999, Rick Knebel wrote: > > > Hi, > > I seem to be having trouble with my scsi scanner. > > > *snip* > > > > My problem is the scanner on bootup is listed as pass 4 but there is no > > pass4 in the /dev directory. I have tried to make it but if I do ./MAKEDEV > > pass4 only pass 0-3 are made. > > > > ./MAKEDEV pass4 means that 4 pass devs are created (0-3). Try ./MAKEDEV > pass5 to create 0-4. Hey thanks that worked. I do not know how much you know about scanners but now whenever I go to start up my scanner with xscanimage I get this message in my dmesg xptioctl: pass driver is not in the kernel xptioctl: put "device pass0" in your kernel config file This is strange because i have device pass0 in my kernal config. Any ideas Thanks Rick > ----- > Chris D. Faulhaber | All the true gurus I've met never > System/Network Administrator, | claimed they were one, and always > Reality Check Information, Inc. | pointed to someone better. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > -- Rick Knebel rknebel@uplink.net http://rknebel.uplink.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 25 13:26:56 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front1m.grolier.fr (front1m.grolier.fr [195.36.216.51]) by hub.freebsd.org (Postfix) with ESMTP id 5217A15655 for ; Sat, 25 Sep 1999 13:24:50 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-102-76.villette.club-internet.fr [194.158.102.76]) by front1m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id WAA15440 for ; Sat, 25 Sep 1999 22:24:34 +0200 (MET DST) Date: Sat, 25 Sep 1999 22:45:15 +0200 (MET DST) From: Gerard Roudier X-Sender: groudier@localhost To: scsi@FreeBSD.ORG Subject: sym driver 0.3.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I have made available revision 0.3.0 of the sym_hipd driver for FreeBSD-CAM. This driver version behaves correctly on QUEUE FULL condition and has been rock solid for me.=20 This driver is still under development. Patches are hosted at the ftp site= =20 with the ncr53c8xx/sym53c8xx drivers updates: ftp://ftp.tux.org/pub/roudier/drivers/freebsd/experimental/ Here's an excerpt of the README file: ------------------------------------------------------------------------- Status: EXPERIMENTAL This driver is currently developped under the following O/S: FreeBSD 4.0 SNAPSHOT July 5th 1999 Latest revision: sym-0.3.0-1990925 Supported SCSI features: - Initiator mode - Wide 16 SCSI BUS - FAST10 up to FAST80-DT synchronous data transfers (1) (depends on controller capabilities) - 64 luns per target - 256 tags per lun (3) - MDP (2) - BUS DEVICE RESET message (2) - ABORT, ABORT TAG message (2) Supported chip features: - On chip RAM - PCI optimized transactions. Supported features of 896/895A/1010: - Full SCRIPTS in on-board RAM (8K) - Phase mismatch handling from SCRIPTS. Others: - SYMBIOS NVRAM layout using 24c16 EEPROM - TEKRAM NVRAM layout using 24c16 EEPROM (2) - TEKRAM NVRAM layout using 93c46 EEPROM - Transfer residuals - 0(1) for both SCRIPTS and C code, allowing=20 100% scalability. Notes: (1) Only supported by the LSI53C1010 and not yet=20 tested due to lack of C1010 based controller. (2) Not yet checked. May not work as expected. (3) Tags/Lun set to 64 for the moment. =20 Files: README.sym=09=09this file sym_conf.h=09=09driver configuration sym_defs.h=09=09driver definitions sym_hipd.c=09=09driver code sym_sys.patch=09=09kernel patch Installation: 1) Untar SYM-0.0.0-990915.tar.gz 2) Copy README.sym, sym_conf.h, sym_defs.h and sym_hipd.c to=20 /usr/src/sys/pci/ 3) Change to /usr/src/sys/ directory 4) Apply the unified patch sym_sys.patch (only if ncr also configured) This patch applies a change to the ncr.c driver that forces it to=20 ignore SYM53C8XX chips that support LOAD/STORE. These devices will=20 be attached by the sym_hipd.c driver. 5) Change to /usr/src/sys/pci/ directory Apply the following patches in that order: PATCH-SYM-0.1.0-19990919 PATCH-SYM-0.2.0-19990922 PATCH-SYM-0.3.0-19990925 Configuring and building the kernel: Since only people that know what they do are allowed to use=20 this driver, such an operation should be just trivial for them. :-) Warnings: - The error recovery pathes of this driver haven't yet been fully tested. For this reason, you should not install this driver on a system that=20 is known to experience SCSI errors other than QUEUE FULL status. (The QUEUE FULL handling has been tested and fixed in revision 0.3.0) - This driver uses LOAD/STORE instructions from SCRIPTS and thus does=20 not support earliest NCR chips (NCR53C810, NCR53C815, NCR53C825). Versionning: - The version number consists in 3 numbers X.Y.Z, starting with 0.0.0. - Z will not be used for incremental patches, but may be used for=20 quick fixes. - Incremental diff files are of the following pattern: PATCH-SYM-X.Y.Z-YYYYMMDD They must be applied from directory: /usr/src/sys/pci/ - Version 1.0.0 will add support for the C1010 (Ultra-3 DT data transfers) - Version 2.0.0 is not planned for now, but will add support for host targe= t=20 mode if it will ever exist. Change log: * SYM-0.0.0-19990915 Initial release. * SYM-0.1.0-19990919 (diff file PATCH-SYM-0.1.0-19990919 Add NVRAM support for latest Tekram boards using 24c16 EEPROM. * SYM-0.2.0-19990922 (diff file PATCH-SYM-0.2.0-19990922 Add PPR negotiation and Ultra3 DT transfers for the LSI53C1010. This corresponding code is untested since I haven't yet the=20 hardware. But the driver is not broken for current chips. * SYM-0.5.0-19990925 (diff file PATCH-SYM-0.2.0-19990925 Source review. Testing of the QUEUE FULL handling (some fixes applied). -------------------------------------------------------------------------- The driver is very fast for me. My 2 fastest HDs (DRVS LVD and Cheatah2 LVD) are not enough to really overload a single SCSI channel of the 896.=20 Latency seems very low. For exemple, reading the both drives using 'dd' at the same time, I get the following results: IO chunk Tps 1K 11600 2K 10600 3K 9450 4K 8900 Ex. for 4K chunk: dd if=3D/dev/rda0 of=3D/dev/null ibs=3D4096 obs=3D16384 count=3D200000 & dd if=3D/dev/rda1 of=3D/dev/null ibs=3D4096 obs=3D16384 count=3D200000 & The result for 4K IO chunk is very interesting, since the hard disks are=20 mostly streaming data at their full sustaint data rate with this test. - Total latency per IO =3D 112 micro-seconds (8900 Tps) - 4K transfer time, assuming 80 MB/s transfer, =3D 50 micro-seconds=20 - So, the total command overhead without data transfer is less=20 than 62 micro-seconds. For sure, faster things exist, but I would be interested in knowing about how similar controllers from other vendors actually perform in the same situation.=20 By the way, a SYM53C895 will give about same result. G=E9rard.=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 25 13:35: 8 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C233E14F1D for ; Sat, 25 Sep 1999 13:35:06 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA26804; Sat, 25 Sep 1999 13:33:21 -0700 Date: Sat, 25 Sep 1999 13:35:02 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Gerard Roudier Cc: scsi@FreeBSD.ORG Subject: Re: sym driver 0.3.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'd like to thank Gerard for doing this- I believe it will be important for us to test this thoroughly, and if I hadn't been 257 tags overflowed myself, I'd be doing it now.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 25 16: 3:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 25E5A14C1F for ; Sat, 25 Sep 1999 16:03:46 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA24089; Sat, 25 Sep 1999 17:03:17 -0600 (MDT) (envelope-from ken) Message-Id: <199909252303.RAA24089@panzer.kdm.org> Subject: Re: scanner and scsi In-Reply-To: <19990925083746.A310@rknebel.uplink.net> from Rick Knebel at "Sep 25, 1999 08:37:46 am" To: rknebel@uplink.net (Rick Knebel) Date: Sat, 25 Sep 1999 17:03:17 -0600 (MDT) Cc: jedgar@fxp.org (Chris D. Faulhaber), scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (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 Rick Knebel wrote... > On Sat, Sep 25, 1999 at 08:11:16AM -0400, Chris D. Faulhaber wrote: > > On Sat, 25 Sep 1999, Rick Knebel wrote: > > > > > Hi, > > > I seem to be having trouble with my scsi scanner. > > > > > *snip* > > > > > > My problem is the scanner on bootup is listed as pass 4 but there is no > > > pass4 in the /dev directory. I have tried to make it but if I do ./MAKEDEV > > > pass4 only pass 0-3 are made. > > > > > > > ./MAKEDEV pass4 means that 4 pass devs are created (0-3). Try ./MAKEDEV > > pass5 to create 0-4. > > Hey thanks that worked. > > I do not know how much you know about scanners but now whenever I go to > start up my scanner with xscanimage I get this message in my dmesg > > xptioctl: pass driver is not in the kernel > xptioctl: put "device pass0" in your kernel config file > > > This is strange because i have device pass0 in my kernal config. Hmm, that is odd, since it does show up in your dmesg as pass4. I'll have to look at the diagnostic code and see if there's a bug somewhere. Does camcontrol work properly? I know you can do a devlist, but that doesn't use the pass device. Try this: camcontrol tur da0 -v Are you sure that xscanimage is looking for a pass device? Is xscanimage in the ports tree at all? A quick grep through the INDEX file doesn't reveal anything obvious. Some scanner utilities want a processor target (pt) device. You might try putting 'device pt0' in your kernel config file (and make sure you have /dev/pt0 as well). Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message