From owner-freebsd-scsi Sun May 26 01:51:41 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA14889 for freebsd-scsi-outgoing; Sun, 26 May 1996 01:51:41 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA14869 for ; Sun, 26 May 1996 01:51:37 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA23556 for ; Sun, 26 May 1996 10:51:34 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA14636 for freebsd-scsi@freebsd.org; Sun, 26 May 1996 10:51:34 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id KAA01219 for freebsd-scsi@freebsd.org; Sun, 26 May 1996 10:43:11 +0200 (MET DST) From: J Wunsch Message-Id: <199605260843.KAA01219@uriah.heep.sax.de> Subject: Re: How to send "start unit" to disk during boot? (solved) To: freebsd-scsi@freebsd.org Date: Sun, 26 May 1996 10:43:11 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199605251845.UAA03638@yedi.iaf.nl> from Wilko Bulte at "May 25, 96 08:45:35 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Wilko Bulte wrote: (mode page 0x25) > Hmm, I think DEC did this from Day-1 when CD-R was a unheard of device. Nevermind, i'm wrong: mode page 0x25 _is_ inside the vendor-specific range. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sun May 26 05:16:42 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA22087 for freebsd-scsi-outgoing; Sun, 26 May 1996 05:16:42 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA22081 for ; Sun, 26 May 1996 05:16:34 -0700 (PDT) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id OAA02321; Sun, 26 May 1996 14:17:26 +0200 Received: by uni4nn.iaf.nl with UUCP id AA27321 (5.67b/IDA-1.5); Sun, 26 May 1996 14:16:23 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA08759 (5.67b/IDA-1.5); Sun, 26 May 1996 13:41:31 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id NAA09075; Sun, 26 May 1996 13:14:19 +0200 From: Wilko Bulte Message-Id: <199605261114.NAA09075@yedi.iaf.nl> X-Organisation: Private FreeBSD site - Arnhem - The Netherlands Subject: Re: kern/1245: scsi tape driver write-protect and eject handling is broken To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 26 May 1996 13:14:19 +0200 (MET DST) Cc: freebsd-scsi@FreeBSD.ORG, fredriks@mcs.com In-Reply-To: <199605252106.XAA27362@uriah.heep.sax.de> from "J Wunsch" at May 25, 96 11:06:37 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As J Wunsch wrote... > > (Moved to freebsd-scsi) > > As Lars Fredriksen wrote: > > that I hadn't submitted context diffs. If someone is willing to review > > these changes (Peter?), then I can submit them if that eases the load > > on people. > > > *************** > > *** 547,552 **** > > --- 547,556 ---- > > #define QIC_1320 0x12 > > #define DDS 0x13 > > #define DAT_1 0x13 > > + #define EXB_8200 0x14 > > + #define EXB_8500 0x15 > > + #define EXB_8200C 0x8c > > + #define EXB_8500C 0x90 > > #define QIC_3080 0x29 > > > ! #define SCSI_2_MAX_DENSITY_CODE 0x17 /* maximum density code specified > > > ! #ifdef EXB_8500C > > ! # define SCSI_2_MAX_DENSITY_CODE EXB_8500C > > ! #else > > ! # define SCSI_2_MAX_DENSITY_CODE 0x17 /* maximum density code specified > > There are two things here that are questionable. I don't particularly > like the #ifdef EXB_8500C -- either we do support it, so it should be > available all the time, or we don't. It is, I'm sorry to say, a bad idea to have this #ifdef. I for myself own a DLT2000 drive that needs density codes $80/$81 to toggle compression mode on/off. We really don't need drive specific values all over the st.c > But the other thing (and that's why the freebsd-scsi) is that it > wasn't clear that the entire conception of ``MAX_DENSITY_CODE'' seems > to make sense. What are the pros and cons? Why is it there? Is it > only ``legacy code''? I killed the check in st.c in my tapedriver and let the drive decide whether it likes the code it received or not. If not, it will return an error. Sounds simple and adequate to me. When it comes to density codes, we should also take a look at mt Something like the following: - mt should have a way to find out if a tape is SCSI or not (ioctl that works on SCSI dev but not on other tapes ?) - mt should have a way to get inquiry string from the tape - mt should have a 'tapecap' file to know what is valid for a particular drive, compression and all. It can now also display the density settings that are non-SCSI-2 standard in an ASCII strings iso in hex. But: this is probably gross overkill. As long as the driver does not make any artificial checks. > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------------- From owner-freebsd-scsi Sun May 26 05:17:04 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA22118 for freebsd-scsi-outgoing; Sun, 26 May 1996 05:17:04 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA22109; Sun, 26 May 1996 05:16:58 -0700 (PDT) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id OAA02324; Sun, 26 May 1996 14:17:48 +0200 Received: by uni4nn.iaf.nl with UUCP id AA27331 (5.67b/IDA-1.5); Sun, 26 May 1996 14:16:27 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA08761 (5.67b/IDA-1.5); Sun, 26 May 1996 13:41:33 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id NAA09113; Sun, 26 May 1996 13:15:58 +0200 From: Wilko Bulte Message-Id: <199605261115.NAA09113@yedi.iaf.nl> X-Organisation: Private FreeBSD site - Arnhem - The Netherlands Subject: Re: dump and 32blocks limit To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 26 May 1996 13:15:58 +0200 (MET DST) Cc: andreas@knobel.gun.de, freebsd-scsi@freebsd.org, davidg@freebsd.org, dyson@freebsd.org In-Reply-To: <199605252037.WAA27101@uriah.heep.sax.de> from "J Wunsch" at May 25, 96 10:37:47 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As J Wunsch wrote... > As Andreas Klemm wrote: > > > Well, sometimes I had a SUN 4mm DAT (Archive Python) at home. > > When doing backups with dump everything seemed to be fine. I could > > choose blocksizes of about 96 blocks (as it's usual on Sun's). > > Ah! This raises a flag... you've been using 96 KB blocking. Sigh. > Now look at the 64 KB physio limitation: your 96 KB has been accepted > by dump(8), but physio(9) split it into one 64 KB block (due to its > limit), and one 32 KB block. This gives you a tape with alternate > 64/32/64/32 KB blocking, nothing you would really like to have... Ah (again ;-) This is of course in line with my observation of multiple drive types never being bothered by 64 Kbyte. > So we should bump the limit to 64 KB, and explain the limitation of > physio in the man page (until it's been fixed -- which should remain a > goal, think of importing tapes with > 64 KB blocking). Yep. Makes my DLT quicker also :) Wilko _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------------- From owner-freebsd-scsi Sun May 26 10:24:33 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA05328 for freebsd-scsi-outgoing; Sun, 26 May 1996 10:24:33 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA05305 for ; Sun, 26 May 1996 10:24:18 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA01666; Sun, 26 May 1996 19:24:00 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA19142; Sun, 26 May 1996 19:23:53 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id SAA02378; Sun, 26 May 1996 18:57:15 +0200 (MET DST) From: J Wunsch Message-Id: <199605261657.SAA02378@uriah.heep.sax.de> Subject: Re: kern/1245: scsi tape driver write-protect and eject handling is broken To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Sun, 26 May 1996 18:57:15 +0200 (MET DST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-scsi@FreeBSD.ORG, fredriks@mcs.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199605261114.NAA09075@yedi.iaf.nl> from Wilko Bulte at "May 26, 96 01:14:19 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Wilko Bulte wrote: > Something like the following: > > - mt should have a way to find out if a tape is SCSI or not > (ioctl that works on SCSI dev but not on other tapes ?) > - mt should have a way to get inquiry string from the tape > - mt should have a 'tapecap' file to know what is valid for a particular > drive, compression and all. It can now also display the density settings > that are non-SCSI-2 standard in an ASCII strings iso in hex. I don't mind you implementing it. 8-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sun May 26 18:31:20 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA03754 for freebsd-scsi-outgoing; Sun, 26 May 1996 18:31:20 -0700 (PDT) Received: from eldorado.net-tel.co.uk (eldorado.net-tel.co.uk [193.122.171.253]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA03700; Sun, 26 May 1996 18:31:10 -0700 (PDT) From: Andrew.Gordon@net-tel.co.uk Received: (from root@localhost) by eldorado.net-tel.co.uk (8.6.12/8.6.10) id CAA20933; Mon, 27 May 1996 02:30:27 +0100 Received: from "/PRMD=NET-TEL/ADMD=GOLD 400/C=GB/" by net-tel.co.uk (Route400-RFCGate); Mon, 27 May 96 2:30:14 +0100 X400-Received: by mta "eldorado" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; Relayed; Mon, 27 May 96 2:30:14 +0100 X400-Received: by mta "net-tel cambridge" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; Relayed; Mon, 27 May 96 1:30:12 +0000 X400-Received: by "/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"; Relayed; Mon, 27 May 96 1:30:12 +0000 X400-MTS-Identifier: ["/PRMD=NET-TEL/ADMD=Gold 400/C=GB/";hst:27674-960527013012-4F6E] X400-Content-Type: P2-1984 (2) X400-Originator: Andrew.Gordon@net-tel.co.uk Original-Encoded-Information-Types: IA5-Text X400-Recipients: non-disclosure:; Date: Mon, 27 May 96 1:30:12 +0000 Content-Identifier: Re(2): SCSI host Message-Id: <"1443-960526225554-A900*/G=Andrew/S=Gordon/O=NET-TEL Computer Systems Ltd/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"@MHS> To: freebsd-scsi@freebsd.org, j@uriah.heep.sax.de Cc: "(FreeBSD hackers)" In-Reply-To: <199605240641.IAA21885@uriah.heep.sax.de> Subject: Re(2): SCSI hostadapter Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Reminds me: does anybody have any information about the 53C400? > > I've got a couple of these boards sitting on a shelf, they used to > accompany HP ScanJets. I don't think they will be anything that can > be called performant, but just out of curiosity... Perhaps they are > good enough to recommend them to someone who needs an adapter for an > Archive Viper 150 or so (which i'd recommend rather than those floppy > tape crap). As it happens, I was trying to put a system together yesterday, using mostly old junk I had lying around. Since I didn't care about disc performance, and I had an old SCSI drive plus a 53C400 adapter handy, I thought I would use those (booting off floppy with some suitably hacked bootblocks). The adapter originally came with a scanner, (but not an HP one) and contains just the 53C400 plus an LS245 buffering the databus and some SCSI termination resnets. Curiously, the nca driver probes the card as a NCR-5380 despite the fact that the chip on the card is clearly labelled as a 53C400A. However, hacking the driver to probe only for 53C400 (it normally probes 5380 first) caused the card not to be probed at all. This particular card does not support interrupts (it doesn't even have any fingers on the connector for any of the IRQ lines). For the hard drive, it seems to work reliably, but is _very_ slow - here are some bonnie results (and results for the same motherboard/drive but with a 2940 instead, for comparison): -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ncr 16 105 89.0 110 10.8 55 1.3 109 8.4 111 5.5 9.6 8.7 2940 16 560 28.4 553 7.7 266 6.5 612 28.7 605 8.3 24.8 3.8 (the drive is an old SCSI-1 device, async transfers only. CPU is AMD 486/100). Results with a tape drive added were mixed. A couple of times, it got into a state where the SCSI bus was jammed, giving "st0: timed out", and total disaster if the hard drive was on the same controller. With just the tape drive, it worked OK, but I was not able to get it to stream with a DC6525 tape (normal data rate around 200K/sec). With a DC6150 (data rate about 90K/sec) it performed normally. From owner-freebsd-scsi Sun May 26 18:31:25 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA03790 for freebsd-scsi-outgoing; Sun, 26 May 1996 18:31:25 -0700 (PDT) Received: from eldorado.net-tel.co.uk (eldorado.net-tel.co.uk [193.122.171.253]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA03705; Sun, 26 May 1996 18:31:11 -0700 (PDT) From: Andrew.Gordon@net-tel.co.uk Received: (from root@localhost) by eldorado.net-tel.co.uk (8.6.12/8.6.10) id CAA20936; Mon, 27 May 1996 02:30:30 +0100 Received: from "/PRMD=NET-TEL/ADMD=GOLD 400/C=GB/" by net-tel.co.uk (Route400-RFCGate); Mon, 27 May 96 2:30:20 +0100 X400-Received: by mta "eldorado" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; Relayed; Mon, 27 May 96 2:30:20 +0100 X400-Received: by mta "net-tel cambridge" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; Relayed; Mon, 27 May 96 1:30:17 +0000 X400-Received: by "/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"; Relayed; Mon, 27 May 96 1:30:16 +0000 X400-MTS-Identifier: ["/PRMD=NET-TEL/ADMD=Gold 400/C=GB/";hst:27674-960527013016-5E86] X400-Content-Type: P2-1984 (2) X400-Originator: Andrew.Gordon@net-tel.co.uk Original-Encoded-Information-Types: IA5-Text X400-Recipients: non-disclosure:; Date: Mon, 27 May 96 1:30:16 +0000 Content-Identifier: Re(2): SCSI host Message-Id: <"1443-960527013356-2539*/G=Andrew/S=Gordon/O=NET-TEL Computer Systems Ltd/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"@MHS> To: freebsd-scsi@freebsd.org, j@uriah.heep.sax.de Cc: "(FreeBSD hackers)" In-Reply-To: <199605240641.IAA21885@uriah.heep.sax.de> Subject: Re(2): SCSI hostadapter Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Reminds me: does anybody have any information about the 53C400? > > I've got a couple of these boards sitting on a shelf, they used to > accompany HP ScanJets. I don't think they will be anything that can > be called performant, but just out of curiosity... Perhaps they are > good enough to recommend them to someone who needs an adapter for an > Archive Viper 150 or so (which i'd recommend rather than those floppy > tape crap). As it happens, I was trying to put a system together yesterday, using mostly old junk I had lying around. Since I didn't care about disc performance, and I had an old SCSI drive plus a 53C400 adapter handy, I thought I would use those (booting off floppy with some suitably hacked bootblocks). The adapter originally came with a scanner, (but not an HP one) and contains just the 53C400 plus an LS245 buffering the databus and some SCSI termination resnets. Curiously, the nca driver probes the card as a NCR-5380 despite the fact that the chip on the card is clearly labelled as a 53C400A. However, hacking the driver to probe only for 53C400 (it normally probes 5380 first) caused the card not to be detected at all. This particular card does not support interrupts (it doesn't even have any fingers on the connector for any of the IRQ lines). For the hard drive, it seems to work reliably, but is _very_ slow - here are some bonnie results (and results for the same motherboard/drive but with a 2940 instead, for comparison): -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ncr 16 105 89.0 110 10.8 55 1.3 109 8.4 111 5.5 9.6 8.7 2940 16 560 28.4 553 7.7 266 6.5 612 28.7 605 8.3 24.8 3.8 (the drive is an old SCSI-1 device, async transfers only. CPU is AMD 486/100). Results with a tape drive added were mixed. A couple of times, it got into a state where the SCSI bus was jammed, giving "st0: timed out", and total disaster if the hard drive was on the same controller. With just the tape drive, it worked OK, but I was not able to get it to stream with a DC6525 tape (normal data rate around 200K/sec). With a DC6150 (data rate about 90K/sec) it performed normally. From owner-freebsd-scsi Sun May 26 23:51:50 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA09671 for freebsd-scsi-outgoing; Sun, 26 May 1996 23:51:50 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA09636 for ; Sun, 26 May 1996 23:51:41 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA13087; Mon, 27 May 1996 08:51:34 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA25903; Mon, 27 May 1996 08:51:33 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id IAA05674; Mon, 27 May 1996 08:28:23 +0200 (MET DST) From: J Wunsch Message-Id: <199605270628.IAA05674@uriah.heep.sax.de> Subject: Re: Archive Viper not correctly identified. To: freebsd-scsi@freebsd.org Date: Mon, 27 May 1996 08:28:23 +0200 (MET DST) Cc: jfieber@indiana.edu (John Fieber) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from John Fieber at "May 26, 96 10:30:57 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As John Fieber wrote: > [I posted this to scsi a while ago, no responese. Does anybody > read it?] ...and i'm moving it back there, where it belongs. You can always ask majordomo to see who's subscribed. If you do for freebsd-scsi, you'll find all the scsi-related people here. So if you don't get an answer, it's most likely not that nobody read your message, but that nobody *has* an answer ready. Me for example, i gave my Viper away more than a year ago, and i know that the ``known rogue'' selection works for my TDC-4222 drive. (Btw., the ``...is a known rogue'' has gone some time ago, since it was confusing too many people -- so don't wait for it.) If it doesn't work for you, it's most likely that you have only two options: give the tape to somebody else who's willing to debug it, or debug it yourself. Looking into the code (sys/scsi/scsiconf.c), you'll notice that you can temporarily turn on SC_SHOWME in the flags of a quirk record, to make the quirk selection code more noisy about its decisions. Perhaps this will get you something further. Sorry that i can't be more helpful. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Mon May 27 07:26:51 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA16600 for freebsd-scsi-outgoing; Mon, 27 May 1996 07:26:51 -0700 (PDT) Received: from mail.ruhrgebiet.individual.net (in-ruhr.ruhr.de [193.100.176.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA16580 for ; Mon, 27 May 1996 07:26:43 -0700 (PDT) Received: from robkaos.UUCP (admin@localhost) by mail.ruhrgebiet.individual.net (8.7.1/8.7.1) with UUCP id PAA10165 for freebsd.org!freebsd-scsi; Mon, 27 May 1996 15:46:36 +0200 (MET DST) Received: by robkaos.ruhr.de (/\oo/\ Smail3.1.29.1 #29.1) id ; Mon, 27 May 96 15:45 MET DST Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Driver for HP Vectra (AMD SCSI) available? To: freebsd-scsi@freebsd.org Date: Mon, 27 May 1996 15:45:27 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there a SCSI driver for the HP Vectra machines? These beasts have an AMD PCI SCSI chip integrated on the motherboard. It would be nice to run FreeBSD on these machines. TIA Robert From owner-freebsd-scsi Mon May 27 07:55:48 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA18288 for freebsd-scsi-outgoing; Mon, 27 May 1996 07:55:48 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA18282 for ; Mon, 27 May 1996 07:55:45 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id JAA03319; Mon, 27 May 1996 09:55:40 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Mon, 27 May 1996 09:55:40 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: Michael Smith cc: scsi@FreeBSD.ORG Subject: Re: Archive Viper not correctly identified. In-Reply-To: <199605270553.PAA25819@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [back to scsi after dropping some bait in current to hook a reply...] On Mon, 27 May 1996, Michael Smith wrote: > > I recently jumped from 2.1R to 2.2-960501-SNAP. Now, my Archive > > Viper is apparently not being identified properly as a > > "known rogue". At boot I get this: > > > > (aha0:2:0): "ARCHIVE VIPER 150 21247 -005" type 1 removable SCSI 1 > > st0(aha0:2:0): Sequential-Access density code 0x0, drive empty > > I have one of these on a machine running this SNAP. Does it have *exactly* the same version string? > Weird; I haven't had any problems with mine, it's running A-OK reading > 120's and writing 150 and 250's. I don't get the 'known rogue' message > though, so it's possible I'm just not tickling the problem. The "known rogue" message is actually gone; the rogue code has been replaced by New Improved (tm) scsiconf code that apparently needs a tweak somewhere. I'll look more carefully into the code and see if I can figure something out. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-scsi Mon May 27 08:08:44 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA19019 for freebsd-scsi-outgoing; Mon, 27 May 1996 08:08:44 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA19009 for ; Mon, 27 May 1996 08:08:41 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id AAA27803; Tue, 28 May 1996 00:56:11 +0930 From: Michael Smith Message-Id: <199605271526.AAA27803@genesis.atrad.adelaide.edu.au> Subject: Re: Archive Viper not correctly identified. To: jfieber@indiana.edu (John Fieber) Date: Tue, 28 May 1996 00:56:11 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, scsi@FreeBSD.ORG In-Reply-To: from "John Fieber" at May 27, 96 09:55:40 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John Fieber stands accused of saying: > > > > > > (aha0:2:0): "ARCHIVE VIPER 150 21247 -005" type 1 removable SCSI 1 > > > st0(aha0:2:0): Sequential-Access density code 0x0, drive empty > > > > I have one of these on a machine running this SNAP. > > Does it have *exactly* the same version string? (bt0:6:0): "ARCHIVE VIPER 150 21247 -005" type 1 removable SCSI 1 > The "known rogue" message is actually gone; the rogue code has > been replaced by New Improved (tm) scsiconf code that apparently > needs a tweak somewhere. I'll look more carefully into the code > and see if I can figure something out. Sure; if you think a reference system will help, let me know. > -john -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-scsi Mon May 27 08:35:53 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA20202 for freebsd-scsi-outgoing; Mon, 27 May 1996 08:35:53 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA20193 for ; Mon, 27 May 1996 08:35:47 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id KAA03461; Mon, 27 May 1996 10:35:42 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Mon, 27 May 1996 10:35:42 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: Michael Smith cc: scsi@FreeBSD.ORG Subject: Re: Archive Viper not correctly identified. In-Reply-To: <199605271526.AAA27803@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 28 May 1996, Michael Smith wrote: > > Does it have *exactly* the same version string? > > (bt0:6:0): "ARCHIVE VIPER 150 21247 -005" type 1 removable SCSI 1 Hrmph. > Sure; if you think a reference system will help, let me know. Is your /sys/scsi/scsiconf.c: $Id: scsiconf.c,v 1.58 1996/04/07 17:32:42 bde Exp $ ? -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-scsi Mon May 27 09:13:22 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA22518 for freebsd-scsi-outgoing; Mon, 27 May 1996 09:13:22 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA22510 for ; Mon, 27 May 1996 09:13:17 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id CAA28011; Tue, 28 May 1996 02:00:38 +0930 From: Michael Smith Message-Id: <199605271630.CAA28011@genesis.atrad.adelaide.edu.au> Subject: Re: Archive Viper not correctly identified. To: jfieber@indiana.edu (John Fieber) Date: Tue, 28 May 1996 02:00:35 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, scsi@FreeBSD.ORG In-Reply-To: from "John Fieber" at May 27, 96 10:35:42 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John Fieber stands accused of saying: > > On Tue, 28 May 1996, Michael Smith wrote: > > > > Does it have *exactly* the same version string? > > > > (bt0:6:0): "ARCHIVE VIPER 150 21247 -005" type 1 removable SCSI 1 > > Hrmph. > > > Sure; if you think a reference system will help, let me know. > > Is your /sys/scsi/scsiconf.c: > > $Id: scsiconf.c,v 1.58 1996/04/07 17:32:42 bde Exp $ * $Id: scsiconf.c,v 1.58 1996/04/07 17:32:42 bde Exp $ > -john About all that's left is that this is a 386 and a BT542, as opposed to your Adaptec. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-scsi Mon May 27 09:18:28 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA22856 for freebsd-scsi-outgoing; Mon, 27 May 1996 09:18:28 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA22850 for ; Mon, 27 May 1996 09:18:26 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id LAA03546; Mon, 27 May 1996 11:18:20 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Mon, 27 May 1996 11:18:20 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: Michael Smith cc: scsi@FreeBSD.ORG Subject: Re: Archive Viper not correctly identified. In-Reply-To: <199605271630.CAA28011@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 28 May 1996, Michael Smith wrote: > * $Id: scsiconf.c,v 1.58 1996/04/07 17:32:42 bde Exp $ Hrmph. > About all that's left is that this is a 386 and a BT542, as opposed to your > Adaptec. I'll stick some debugging into scsiconf.c and if you would be willing to build a test kernel, we can compare the results. It may be some days, as I've got many more pressing things to do. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-scsi Mon May 27 14:14:57 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA13474 for freebsd-scsi-outgoing; Mon, 27 May 1996 14:14:57 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA13464 for ; Mon, 27 May 1996 14:14:51 -0700 (PDT) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id XAA06263; Mon, 27 May 1996 23:14:36 +0200 Received: by uni4nn.iaf.nl with UUCP id AA26957 (5.67b/IDA-1.5); Mon, 27 May 1996 23:14:10 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA32513 (5.67b/IDA-1.5); Mon, 27 May 1996 22:36:30 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id TAA22170; Mon, 27 May 1996 19:14:55 +0200 From: Wilko Bulte Message-Id: <199605271714.TAA22170@yedi.iaf.nl> X-Organisation: Private FreeBSD site - Arnhem - The Netherlands Subject: Re: kern/1245: scsi tape driver write-protect and eject handling is broken To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 27 May 1996 19:14:55 +0200 (MET DST) Cc: freebsd-scsi@freebsd.org, fredriks@mcs.com In-Reply-To: <199605261657.SAA02378@uriah.heep.sax.de> from "J Wunsch" at May 26, 96 06:57:15 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As J Wunsch wrote... > As Wilko Bulte wrote: > > > Something like the following: > > > > - mt should have a way to find out if a tape is SCSI or not > > (ioctl that works on SCSI dev but not on other tapes ?) > > - mt should have a way to get inquiry string from the tape > > - mt should have a 'tapecap' file to know what is valid for a particular > > drive, compression and all. It can now also display the density settings > > that are non-SCSI-2 standard in an ASCII strings iso in hex. > > I don't mind you implementing it. 8-) I guessed that one :) But you left off my last remark about 'gross overkill'. I only run the R FreeBSDs, not current. This makes hacks on -current stuff even more unlikely. But kidding aside: isn't the most simple and elegant(?) way to solve the issue getting rid of the density checks in st.c? Wilko _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------------- From owner-freebsd-scsi Mon May 27 14:29:07 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA15088 for freebsd-scsi-outgoing; Mon, 27 May 1996 14:29:07 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA15061; Mon, 27 May 1996 14:29:01 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA09109; Mon, 27 May 1996 14:26:59 -0700 From: Terry Lambert Message-Id: <199605272126.OAA09109@phaeton.artisoft.com> Subject: Re: Re(2): SCSI hostadapter To: Andrew.Gordon@net-tel.co.uk Date: Mon, 27 May 1996 14:26:59 -0700 (MST) Cc: freebsd-scsi@FreeBSD.org, j@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org In-Reply-To: <"1443-960526225554-A900*/G=Andrew/S=Gordon/O=NET-TEL Computer from "Andrew.Gordon@net-tel.co.uk" at May 27, 96 01:30:12 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Reminds me: does anybody have any information about the 53C400? > > > > I've got a couple of these boards sitting on a shelf, they used to > > accompany HP ScanJets. I don't think they will be anything that can > > be called performant, but just out of curiosity... Perhaps they are > > good enough to recommend them to someone who needs an adapter for an > > Archive Viper 150 or so (which i'd recommend rather than those floppy > > tape crap). > > As it happens, I was trying to put a system together yesterday, using mostly old junk I had lying around. Since I didn't care about disc performance, and I had an old SCSI drive plus a 53C400 adapter handy, I thought I would use those (booting off floppy with some suitably hacked bootblocks). > > The adapter originally came with a scanner, (but not an HP one) and contains just the 53C400 plus an LS245 buffering the databus and some SCSI termination resnets. Curiously, the nca driver probes the card as a NCR-5380 despite the fact that the chip on the card is clearly labelled as a 53C400A. However, hacking the driver to probe only for 53C400 (it normally probes 5380 first) caused the card not to be probed at all. > > This particular card does not support interrupts (it doesn't even have any fingers on the connector for any of the IRQ lines). > > For the hard drive, it seems to work reliably, but is _very_ slow - here are some bonnie results (and results for the same motherboard/drive but with a 2940 instead, for comparison): > > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > ncr 16 105 89.0 110 10.8 55 1.3 109 8.4 111 5.5 9.6 8.7 > 2940 16 560 28.4 553 7.7 266 6.5 612 28.7 605 8.3 24.8 3.8 > > (the drive is an old SCSI-1 device, async transfers only. CPU is AMD 486/100). This is typically an artifact of having the interrupt set incorrectly. I'd caution you that it's also possible that it's just a dog-slow interface, so there may be nothing to be done about it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-scsi Mon May 27 17:32:49 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA13537 for freebsd-scsi-outgoing; Mon, 27 May 1996 17:32:49 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA13511; Mon, 27 May 1996 17:32:36 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id KAA29356; Tue, 28 May 1996 10:18:47 +0930 From: Michael Smith Message-Id: <199605280048.KAA29356@genesis.atrad.adelaide.edu.au> Subject: Re: Re(2): SCSI hostadapter To: terry@lambert.org (Terry Lambert) Date: Tue, 28 May 1996 10:18:46 +0930 (CST) Cc: Andrew.Gordon@net-tel.co.uk, freebsd-scsi@FreeBSD.ORG, j@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199605272126.OAA09109@phaeton.artisoft.com> from "Terry Lambert" at May 27, 96 02:26:59 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert stands accused of saying: > > > > This particular card does not support interrupts (it doesn't even have any fingers on the connector for any of the IRQ lines). ... > This is typically an artifact of having the interrupt set incorrectly. This message is an artifact of Terry spending too long awake 8) > I'd caution you that it's also possible that it's just a dog-slow > interface, so there may be nothing to be done about it. A good 5380 clone in a good DMA environment can manage around the 2M/sec mark sustained (eg. the LOGIC 53C80 in the Atari TT). Without this, and with no interrupts, you're kinda restricted in your total data rate 8( > Terry Lambert -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-scsi Mon May 27 17:58:12 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA14983 for freebsd-scsi-outgoing; Mon, 27 May 1996 17:58:12 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA14962; Mon, 27 May 1996 17:58:08 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA09890; Mon, 27 May 1996 17:55:23 -0700 From: Terry Lambert Message-Id: <199605280055.RAA09890@phaeton.artisoft.com> Subject: Re: Re(2): SCSI hostadapter To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 27 May 1996 17:55:23 -0700 (MST) Cc: terry@lambert.org, Andrew.Gordon@net-tel.co.uk, freebsd-scsi@FreeBSD.ORG, j@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199605280048.KAA29356@genesis.atrad.adelaide.edu.au> from "Michael Smith" at May 28, 96 10:18:46 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > This particular card does not support interrupts (it doesn't even have any fingers on the connector for any of the IRQ lines). > ... > > This is typically an artifact of having the interrupt set incorrectly. > > This message is an artifact of Terry spending too long awake 8) Oh, duh. Then "it's just a slow card". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-scsi Tue May 28 00:26:37 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA08307 for freebsd-scsi-outgoing; Tue, 28 May 1996 00:26:37 -0700 (PDT) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA08302 for ; Tue, 28 May 1996 00:26:35 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id AAA08500; Tue, 28 May 1996 00:25:17 -0700 (PDT) Message-Id: <199605280725.AAA08500@ref.tfs.com> Subject: Re: kern/1245: scsi tape driver write-protect and eject handling is broken To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Tue, 28 May 1996 00:25:16 -0700 (PDT) From: "JULIAN Elischer" Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-scsi@freebsd.org, fredriks@mcs.com In-Reply-To: <199605271714.TAA22170@yedi.iaf.nl> from "Wilko Bulte" at May 27, 96 07:14:55 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > But kidding aside: isn't the most simple and elegant(?) way to solve > the issue getting rid of the density checks in st.c? > I agree I didn't like that line in the patch that it came from but didn't have the time to change it when I committed it.. kill it. it's up to the drive to reject bad numbers.. julian From owner-freebsd-scsi Tue May 28 01:48:56 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA11507 for freebsd-scsi-outgoing; Tue, 28 May 1996 01:48:56 -0700 (PDT) Received: from uu.elvisti.kiev.ua ([193.125.28.132]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA11444 for ; Tue, 28 May 1996 01:47:03 -0700 (PDT) Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.129]) by uu.elvisti.kiev.ua (8.7.5/8.7.3) with ESMTP id LAA02634 for ; Tue, 28 May 1996 11:48:42 +0300 (EET DST) Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id LAA12874 for scsi@freebsd.org; Tue, 28 May 1996 11:48:42 +0300 From: "Andrew V. Stesin" Message-Id: <199605280848.LAA12874@office.elvisti.kiev.ua> Subject: AdvanSys SCSI question To: scsi@freebsd.org Date: Tue, 28 May 1996 11:48:41 +0300 (EET DST) X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello SCSI gurus, just a question -- I know that the driver is in work already. Is Advansys PCI SCSI HDA any good from the technical point of view? >From my (rather limited) experience with Advansys SCSI HBA I got an impression that it is designed to fill a nishe between NCR 53c810 and Adaptec 2940; it's price is between those ones, but performance is worse than of above two. We also had a headache while equipping the box for a customer because of Advansys SCSI -- it wasn't supported by FreeBSD, UnixWare drivers were dead, we weren't able to get some working driver set, and SCO UNIX 3.2.4 was settled there at last; and the drivers were really bad, NCR outperformed Advansys easily. I think that device itself is probably not that bad, but the drivers for UW and SCO were buggy? -- With best regards -- Andrew Stesin. +380 (44) 2760188 +380 (44) 2713457 +380 (44) 2713560 "You may delegate authority, but not responsibility." Frank's Management Rule #1. From owner-freebsd-scsi Tue May 28 14:10:48 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA29598 for freebsd-scsi-outgoing; Tue, 28 May 1996 14:10:48 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA29555 for ; Tue, 28 May 1996 14:10:40 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id NAA07996 for ; Tue, 28 May 1996 13:20:45 -0700 Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id WAA09687; Tue, 28 May 1996 22:20:57 +0200 Received: by uni4nn.iaf.nl with UUCP id AA17008 (5.67b/IDA-1.5); Tue, 28 May 1996 22:20:29 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA09616 (5.67b/IDA-1.5); Tue, 28 May 1996 21:32:58 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id VAA01232; Tue, 28 May 1996 21:30:47 +0200 From: Wilko Bulte Message-Id: <199605281930.VAA01232@yedi.iaf.nl> X-Organisation: Private FreeBSD site - Arnhem - The Netherlands Subject: Re: kern/1245: scsi tape driver To: julian@ref.tfs.com (JULIAN Elischer) Date: Tue, 28 May 1996 21:30:47 +0200 (MET DST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-scsi@freebsd.org, fredriks@mcs.com In-Reply-To: <199605280725.AAA08500@ref.tfs.com> from "JULIAN Elischer" at May 28, 96 00:25:16 am X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As JULIAN Elischer wrote... > > > But kidding aside: isn't the most simple and elegant(?) way to solve > > the issue getting rid of the density checks in st.c? > > > I agree > I didn't like that line in the patch that it came from > but didn't have the time to change it when I committed it.. > > > > kill it. it's up to the drive to reject bad numbers.. OK. I can grab the -current st.c and create a patch. Someone with patch ^H^H^H^H^H^H commit privs has to put it in the tree. OK? Wilko _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------------- From owner-freebsd-scsi Tue May 28 15:14:58 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA07407 for freebsd-scsi-outgoing; Tue, 28 May 1996 15:14:58 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA07303; Tue, 28 May 1996 15:14:34 -0700 (PDT) Received: from uu.elvisti.kiev.ua ([193.125.28.132]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id JAA06345 ; Tue, 28 May 1996 09:48:54 -0700 Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.129]) by uu.elvisti.kiev.ua (8.7.5/8.7.3) with ESMTP id TAA15426; Tue, 28 May 1996 19:49:18 +0300 (EET DST) Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id TAA07502; Tue, 28 May 1996 19:49:11 +0300 From: "Andrew V. Stesin" Message-Id: <199605281649.TAA07502@office.elvisti.kiev.ua> Subject: Mysterious crashes of FreeBSD gateway -- caugh it(?) To: questions@freebsd.org, scsi@freebsd.org Date: Tue, 28 May 1996 19:49:10 +0300 (EET DST) X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi people, I got some problems, and maybe someone can comment? A machine, our recently built firewall gateway to Internet, is: ATC-1425B mainboard, PCI, SiS 496/7 chipset; 16Mb RAM; AMD 5x133 CPU; NCR 53c810 SCSI; 1Gb Conner CFP1060S drive (recent, good one); two modems on the onboard COMs (SLIP lines to the world); 1 Ethernet card. OS: FreeBSD-stable as of late March. Add-ons: IPfilter 3.0.3+ (by Darren Reed) as in-kernel IP filtering facility, Squid 1.0beta7 WWW proxy cache daemon. The machine was experiencing spontaneous reboots from time to time. Either silent reboots, or prefaced with messages from NCR driver (like "NCR dead?"). When a Compex ReadyLink (DEC 21041-based) PCI ethernet was replaced by a random NE2000, the trouble almost gone -- the box was up for some days, just Ok. Today we were able to inspire a repeatable reboot with a misconfigured test machine on the same network. It has a gateway machine as a default router, and no route to another subnet, connected via FreeBSD-1.1.5-based host, was in the tables. So each packed from the test machine, destined to those subnet, was going to gateway first, then forwarded to 1.1.5 box, and ICMP redirect was sent to the test box about this from the gateway. When doing a massive TCP transfers to the 1.1.5-connected subnet, or even ping -f, a high network load was inspired on a gateway machine (receive a packet -- forvard it -- send redirect). NE2000 worked fine, but NCR driver started to through messages about I/O errors, "NCR dead", etc. Then gateway rebooted itself. What I want to ask. What might be the source of that trouble? Poor motherboard quality, when an overloaded (?! is it an overload?) either ISA or PCI bus forces NCR to go asleep? Or is it a bug in TCP/IP stack or IPfilter, or their interraction with NCR driver, tickled with the nessesity to process IP/ICMP packets at a very high rate? I strongly suspect a hardware problem, but maybe there are other opinions? -- With best regards -- Andrew Stesin. +380 (44) 2760188 +380 (44) 2713457 +380 (44) 2713560 "You may delegate authority, but not responsibility." Frank's Management Rule #1. From owner-freebsd-scsi Tue May 28 22:46:04 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA07972 for freebsd-scsi-outgoing; Tue, 28 May 1996 22:46:04 -0700 (PDT) Received: from mail.think.com (Mail1.Think.COM [131.239.33.245]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA07967 for ; Tue, 28 May 1996 22:46:02 -0700 (PDT) Received: from Early-Bird-1.Think.COM by mail.think.com; Wed, 29 May 96 01:45:49 -0400 Received: from compound.Think.COM (fergus-28.dialup.prtel.com) by Early-Bird.Think.COM; Wed, 29 May 96 01:45:47 EDT Received: (from alk@localhost) by compound.Think.COM (8.7.5/8.7.3) id AAA01176; Wed, 29 May 1996 00:45:30 -0500 (CDT) Date: Wed, 29 May 1996 00:45:30 -0500 (CDT) Message-Id: <199605290545.AAA01176@compound.Think.COM> From: Tony Kimball To: scsi@freebsd.org Subject: ncr scsi Qs Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Since switching from an Adaptec 1542CF ISA to a CSC NCR PCI scsi controller, my ancient Micropolis drive has been filling my logs with this stuff: May 28 23:25:36 compound /kernel: sd1(ncr0:2:0): RECOVERED ERROR info:1857e6 asc:3,0 Peripheral device write fault May 28 23:25:36 compound /kernel: , retries:4 May 28 23:25:36 compound /kernel: sd1(ncr0:2:0): extraneous data discarded. May 28 23:25:36 compound /kernel: sd1(ncr0:2:0): COMMAND FAILED (9 0) @f10d3400. May 28 23:30:09 compound /kernel: sd1(ncr0:2:0): RECOVERED ERROR info:1b6aa5 asc:3,0 Peripheral device write fault May 28 23:30:09 compound /kernel: , retries:4 Is this a familiar problem for anyone? I had the adaptec turned down to 8MB/sec in order to accomodate this drive. Is there any way to throttle back the scsi bus xfers on the ncr controller? From owner-freebsd-scsi Wed May 29 14:17:57 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA08014 for freebsd-scsi-outgoing; Wed, 29 May 1996 14:17:57 -0700 (PDT) Received: from riley-net170-164.uoregon.edu (riley-net170-164.uoregon.edu [128.223.170.164]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA07975; Wed, 29 May 1996 14:17:37 -0700 (PDT) Received: (from dwhite@localhost) by riley-net170-164.uoregon.edu (8.6.12/8.6.12) id OAA00340; Wed, 29 May 1996 14:17:28 -0700 Date: Wed, 29 May 1996 14:17:28 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: "Andrew V. Stesin" cc: questions@freebsd.org, scsi@freebsd.org Subject: Re: Mysterious crashes of FreeBSD gateway -- caugh it(?) In-Reply-To: <199605281649.TAA07502@office.elvisti.kiev.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 28 May 1996, Andrew V. Stesin wrote: > When a Compex ReadyLink (DEC 21041-based) PCI ethernet was replaced > by a random NE2000, the trouble almost gone -- the box was up for > some days, just Ok. Someone has noted that recent Compex's don't work well with FreeBSD. That may clear up some of your random crashes. > When doing a massive TCP transfers to the 1.1.5-connected subnet, > or even ping -f, a high network load was inspired on a gateway > machine (receive a packet -- forvard it -- send redirect). > NE2000 worked fine, but NCR driver started to through messages > about I/O errors, "NCR dead", etc. Then gateway rebooted itself. I wonder if you have a resource conflict between the NCR and your ethernet card. My NCR may be broke but I had to manually set the IRQ in the PC BIOS. Make sure that the ethernet card and the NCR aren't sharing resources. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-scsi Wed May 29 14:40:14 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09794 for freebsd-scsi-outgoing; Wed, 29 May 1996 14:40:14 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA09676; Wed, 29 May 1996 14:39:54 -0700 (PDT) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id XAA13337; Wed, 29 May 1996 23:37:35 +0200 Received: by uni4nn.iaf.nl with UUCP id AA18315 (5.67b/IDA-1.5); Wed, 29 May 1996 23:34:13 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA23147 (5.67b/IDA-1.5); Wed, 29 May 1996 23:11:59 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id WAA11549; Wed, 29 May 1996 22:55:46 +0200 From: Wilko Bulte Message-Id: <199605292055.WAA11549@yedi.iaf.nl> X-Organisation: Private FreeBSD site - Arnhem - The Netherlands Subject: Re: Mysterious crashes of FreeBSD gateway -- caugh it(?) To: stesin@elvisti.kiev.ua (Andrew V. Stesin) Date: Wed, 29 May 1996 22:55:46 +0200 (MET DST) Cc: questions@freebsd.org, scsi@freebsd.org In-Reply-To: <199605281649.TAA07502@office.elvisti.kiev.ua> from "Andrew V. Stesin" at May 28, 96 07:49:10 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Andrew V. Stesin wrote... > When doing a massive TCP transfers to the 1.1.5-connected subnet, > or even ping -f, a high network load was inspired on a gateway > machine (receive a packet -- forvard it -- send redirect). > NE2000 worked fine, but NCR driver started to through messages > about I/O errors, "NCR dead", etc. Then gateway rebooted itself. > > What I want to ask. > > What might be the source of that trouble? Poor motherboard quality, when > an overloaded (?! is it an overload?) either ISA or PCI bus forces NCR > to go asleep? Or is it a bug in TCP/IP stack or IPfilter, or > their interraction with NCR driver, tickled > with the nessesity to process IP/ICMP packets at a very high rate? > I strongly suspect a hardware problem, but maybe there are other > opinions? I have also seen this happen with a SCSI device that was not 'liked' by the ncr driver. After changing the firmware of the _device_ (a tape) the problem went away. A 'dead' ncr is a perfectly acceptable reason for the system to reboot itself (at least it was on mine). I admit this does not correlate well with your ethernet board swapping, but it is another datapoint on 'dead' ncrs Wilko _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------------- From owner-freebsd-scsi Wed May 29 14:46:32 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA10135 for freebsd-scsi-outgoing; Wed, 29 May 1996 14:46:32 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA10128 for ; Wed, 29 May 1996 14:46:23 -0700 (PDT) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id XAA13394 for ; Wed, 29 May 1996 23:46:53 +0200 Received: by uni4nn.iaf.nl with UUCP id AA18392 (5.67b/IDA-1.5 for freebsd-scsi@freebsd.org); Wed, 29 May 1996 23:36:48 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA23149 (5.67b/IDA-1.5 for freebsd-scsi@freebsd.org); Wed, 29 May 1996 23:12:00 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id XAA11686 for freebsd-scsi@freebsd.org; Wed, 29 May 1996 23:08:55 +0200 From: Wilko Bulte Message-Id: <199605292108.XAA11686@yedi.iaf.nl> X-Organisation: Private FreeBSD site - Arnhem - The Netherlands Subject: removing 32 kbyte limit from dump To: freebsd-scsi@freebsd.org (FreeBSD SCSI hackers) Date: Wed, 29 May 1996 23:08:55 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi there We seem to have agreed that the 32 kbyte limit should be removed from 'dump' and be replaced with the 64 kbyte limit as imposed by physio. There is a patch below that does just that. But I'm not really satisfied by this. I'd rather see that the st.c driver returns EINVAL or something like that when an attempt is made to write an impossible block size (and of course dump should act accordingly when it receives the error value). Am I missing something here? Did not study dump too carefully, but we are now limiting people to <= 64 kbytes even if the output file is not a tape device. That is not too dramatic, but not clean either.. Anyway, here is the patch to be commited.. Wilko --------- *** main.c.orig Wed May 29 22:57:52 1996 --- main.c Wed May 29 23:01:15 1996 *************** *** 167,177 **** case 'b': /* blocks per tape write */ ntrec = numarg('b', "number of blocks per write", 1L, 1000L, &argc, &argv); ! /* XXX restore is unable to restore dumps that ! were created with a blocksize larger than 32K. ! Possibly a bug in the scsi tape driver. */ ! if ( ntrec > 32 ) { ! msg("please choose a blocksize <= 32\n"); exit(X_ABORT); } break; --- 167,177 ---- case 'b': /* blocks per tape write */ ntrec = numarg('b', "number of blocks per write", 1L, 1000L, &argc, &argv); ! /* XXX physio() is currently unable > 64 kByte I/Os */ ! /* so lets tell the user now and not wait for him/her ! /* to see the console message */ ! if ( ntrec > 64 ) { ! msg("Please choose a blocksize <= 64 \n"); exit(X_ABORT); } break; _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------------- From owner-freebsd-scsi Thu May 30 03:20:24 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA21281 for freebsd-scsi-outgoing; Thu, 30 May 1996 03:20:24 -0700 (PDT) Received: from uu.elvisti.kiev.ua ([193.125.28.132]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA20590; Thu, 30 May 1996 03:16:02 -0700 (PDT) Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.129]) by uu.elvisti.kiev.ua (8.7.5/8.7.3) with ESMTP id NAA06287; Thu, 30 May 1996 13:17:16 +0300 (EET DST) Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id NAA16958; Thu, 30 May 1996 13:17:11 +0300 From: "Andrew V. Stesin" Message-Id: <199605301017.NAA16958@office.elvisti.kiev.ua> Subject: Re: Mysterious crashes of FreeBSD gateway -- caugh it(?) To: dwhite@resnet.uoregon.edu Date: Thu, 30 May 1996 13:17:11 +0300 (EET DST) Cc: stesin@elvisti.kiev.ua, questions@freebsd.org, scsi@freebsd.org In-Reply-To: from "Doug White" at May 29, 96 02:17:28 pm X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk # On Tue, 28 May 1996, Andrew V. Stesin wrote: # # > When a Compex ReadyLink (DEC 21041-based) PCI ethernet was replaced # > by a random NE2000, the trouble almost gone -- the box was up for # > some days, just Ok. # # Someone has noted that recent Compex's don't work well with FreeBSD. # That may clear up some of your random crashes. Yes, indeed. Compex ReadyLink Rev. D1 worked (and still works) perfectly; Rev.D2 -- problems... # > When doing a massive TCP transfers to the 1.1.5-connected subnet, # > or even ping -f, a high network load was inspired on a gateway # > machine (receive a packet -- forvard it -- send redirect). # > NE2000 worked fine, but NCR driver started to through messages # > about I/O errors, "NCR dead", etc. Then gateway rebooted itself. # # I wonder if you have a resource conflict between the NCR and your # ethernet card. I doubt. Ether (NE2000) is on ISA port 0x280 irq 5 -- nothing even close to NCR. # My NCR may be broke but I had to manually set the IRQ in # the PC BIOS. Yes, I do it always by hand (NCR uses a jumper-settable PCI INT, by default -- INT A. I don't know details, but from my experience it's wise to set NCR's PCI slot to use INT A manually; problems otherwise). # Make sure that the ethernet card and the NCR aren't sharing # resources. Is it possible at all? # # Doug White | University of Oregon # Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant # http://gladstone.uoregon.edu/~dwhite | Computer Science Major # -- With best regards -- Andrew Stesin. +380 (44) 2760188 +380 (44) 2713457 +380 (44) 2713560 "You may delegate authority, but not responsibility." Frank's Management Rule #1. From owner-freebsd-scsi Thu May 30 04:09:57 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA29110 for freebsd-scsi-outgoing; Thu, 30 May 1996 04:09:57 -0700 (PDT) Received: from uu.elvisti.kiev.ua ([193.125.28.132]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA28742; Thu, 30 May 1996 04:08:35 -0700 (PDT) Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.129]) by uu.elvisti.kiev.ua (8.7.5/8.7.3) with ESMTP id OAA07338; Thu, 30 May 1996 14:05:04 +0300 (EET DST) Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id OAA17791; Thu, 30 May 1996 14:05:03 +0300 From: "Andrew V. Stesin" Message-Id: <199605301105.OAA17791@office.elvisti.kiev.ua> Subject: Re: Mysterious crashes of FreeBSD gateway -- caugh it(?) To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Thu, 30 May 1996 14:05:02 +0300 (EET DST) Cc: stesin@elvisti.kiev.ua, questions@freebsd.org, scsi@freebsd.org In-Reply-To: <199605292055.WAA11549@yedi.iaf.nl> from "Wilko Bulte" at May 29, 96 10:55:46 pm X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi again, # # As Andrew V. Stesin wrote... # # > When doing a massive TCP transfers to the 1.1.5-connected subnet, # > or even ping -f, a high network load was inspired on a gateway # > machine (receive a packet -- forvard it -- send redirect). # > NE2000 worked fine, but NCR driver started to through messages # > about I/O errors, "NCR dead", etc. Then gateway rebooted itself. # > # > What I want to ask. # > # > What might be the source of that trouble? Poor motherboard quality, when # > an overloaded (?! is it an overload?) either ISA or PCI bus forces NCR # > to go asleep? Or is it a bug in TCP/IP stack or IPfilter, or # > their interraction with NCR driver, tickled # > with the nessesity to process IP/ICMP packets at a very high rate? # # > I strongly suspect a hardware problem, but maybe there are other # > opinions? # # I have also seen this happen with a SCSI device that was not 'liked' # by the ncr driver. After changing the firmware of the _device_ (a tape) # the problem went away. I doubt here. Another (similar SCSI hardware) box is rock solid with the same configuration of NCR and Conner drive. The two differences between boxes are: 1) motherboards, 2) gateway has IPfilter inside. Is it possible, for example, that a complex set of filtering rules are processed at a high priority in the kernel while packets are "accepted"-"filtered on input"-"forvarded"-"filtered on output"-"output" ? and for the time of processing packets NCR interrupts are missed? (I don't know much about the things like splnet() etc. :( for a pity. Where can I read about them, BTW?) # A 'dead' ncr is a perfectly acceptable reason for the system to reboot # itself (at least it was on mine). Definitely. # I admit this does not correlate well with your ethernet board swapping, # but it is another datapoint on 'dead' ncrs # # Wilko # _ __________________________________________________________________________ # | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl # |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands # -------------------------------------------------------------------------------- # -- With best regards -- Andrew Stesin. +380 (44) 2760188 +380 (44) 2713457 +380 (44) 2713560 "You may delegate authority, but not responsibility." Frank's Management Rule #1. From owner-freebsd-scsi Thu May 30 05:34:33 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA11705 for freebsd-scsi-outgoing; Thu, 30 May 1996 05:34:33 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA11686 for ; Thu, 30 May 1996 05:34:25 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id WAA19690; Thu, 30 May 1996 22:19:02 +1000 Date: Thu, 30 May 1996 22:19:02 +1000 From: Bruce Evans Message-Id: <199605301219.WAA19690@godzilla.zeta.org.au> To: freebsd-scsi@freebsd.org, wilko@yedi.iaf.nl Subject: Re: removing 32 kbyte limit from dump Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >But I'm not really satisfied by this. I'd rather see that the st.c >driver returns EINVAL or something like that when an attempt is made >to write an impossible block size (and of course dump should act >accordingly when it receives the error value). 96K is not impossible. It just gets mutilated to 64K+32K by physio(), and the error isn't detected because both 64K and 32K are possible. physio() needs to have a do-not-split flag. Similar problems probably affect cd and worm devices. An i/o of 100 * 2352 byte blocks would be mutilated at 64K boundaries. This can be fixed using the current physio() interface: don't use rawread()/ rawwrite(), and provided a minphys() function that returns (MAXPHYS / 2352) * 2352 (it must be <= MAXPHYS because physio() uses min(MAXPHYS, minphys()). >--- 167,177 ---- > case 'b': /* blocks per tape write */ > ntrec = numarg('b', "number of blocks per write", > 1L, 1000L, &argc, &argv); >! /* XXX physio() is currently unable > 64 kByte I/Os */ >! /* so lets tell the user now and not wait for him/her >! /* to see the console message */ >! if ( ntrec > 64 ) { >! msg("Please choose a blocksize <= 64 \n"); > exit(X_ABORT); 64 should be MAXPHYS/1024. Bruce From owner-freebsd-scsi Thu May 30 13:19:00 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA19291 for freebsd-scsi-outgoing; Thu, 30 May 1996 13:19:00 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA19280 for ; Thu, 30 May 1996 13:18:53 -0700 (PDT) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id WAA17193; Thu, 30 May 1996 22:19:51 +0200 Received: by uni4nn.iaf.nl with UUCP id AA16184 (5.67b/IDA-1.5); Thu, 30 May 1996 22:19:27 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA30889 (5.67b/IDA-1.5); Thu, 30 May 1996 21:39:37 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id VAA08360; Thu, 30 May 1996 21:27:05 +0200 From: Wilko Bulte Message-Id: <199605301927.VAA08360@yedi.iaf.nl> X-Organisation: Private FreeBSD site - Arnhem - The Netherlands Subject: Re: removing 32 kbyte limit from dump To: bde@zeta.org.au (Bruce Evans) Date: Thu, 30 May 1996 21:27:05 +0200 (MET DST) Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: <199605301219.WAA19690@godzilla.zeta.org.au> from "Bruce Evans" at May 30, 96 10:19:02 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote... > > >But I'm not really satisfied by this. I'd rather see that the st.c > >driver returns EINVAL or something like that when an attempt is made > >to write an impossible block size (and of course dump should act > >accordingly when it receives the error value). > > 96K is not impossible. It just gets mutilated to 64K+32K by physio(), Read impossible as: as the physio() code now handles it. > and the error isn't detected because both 64K and 32K are possible. > physio() needs to have a do-not-split flag. Hm. > Similar problems probably affect cd and worm devices. An i/o of > 100 * 2352 byte blocks would be mutilated at 64K boundaries. This > can be fixed using the current physio() interface: don't use rawread()/ > rawwrite(), and provided a minphys() function that returns > (MAXPHYS / 2352) * 2352 (it must be <= MAXPHYS because physio() > uses min(MAXPHYS, minphys()). For cd this is possible not a big problem. I'm not sure about worm. > >! /* so lets tell the user now and not wait for him/her > >! /* to see the console message */ > >! if ( ntrec > 64 ) { > >! msg("Please choose a blocksize <= 64 \n"); > > exit(X_ABORT); > > 64 should be MAXPHYS/1024. True! Wilko _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------------- From owner-freebsd-scsi Thu May 30 14:02:55 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA24711 for freebsd-scsi-outgoing; Thu, 30 May 1996 14:02:55 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA24611 for ; Thu, 30 May 1996 14:02:34 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA15821; Thu, 30 May 1996 23:01:33 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA17268; Thu, 30 May 1996 23:01:33 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id WAA23103; Thu, 30 May 1996 22:25:36 +0200 (MET DST) From: J Wunsch Message-Id: <199605302025.WAA23103@uriah.heep.sax.de> Subject: Re: removing 32 kbyte limit from dump To: freebsd-scsi@freebsd.org Date: Thu, 30 May 1996 22:25:36 +0200 (MET DST) Cc: wilko@yedi.iaf.nl Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199605301219.WAA19690@godzilla.zeta.org.au> from Bruce Evans at "May 30, 96 10:19:02 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > Similar problems probably affect cd and worm devices. An i/o of > 100 * 2352 byte blocks would be mutilated at 64K boundaries. This > can be fixed using the current physio() interface: don't use rawread()/ > rawwrite(), and provided a minphys() function that returns > (MAXPHYS / 2352) * 2352 (it must be <= MAXPHYS because physio() > uses min(MAXPHYS, minphys()). This still leaves the problem of not being able to read an SGI-written tape with 256 KB blocking. :( -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Thu May 30 16:56:13 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA17630 for freebsd-scsi-outgoing; Thu, 30 May 1996 16:56:13 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA17625 for ; Thu, 30 May 1996 16:56:08 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id SAA12520 for ; Thu, 30 May 1996 18:56:05 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Thu, 30 May 1996 18:56:05 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: scsi@FreeBSD.ORG Subject: Re: Archive Viper not correctly identified. In-Reply-To: <199605271630.CAA28011@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Okay, I had to rebuild my kernel for another purpose so I looked at the scsi code more carefully. When the probe looks up to see if the given device is in its "quirk" list, it compares three things returned by the device: manufacturer, model, and revision. For the Archive Viper, the quirk entry is: Manufacturer = ARCHIVE mOdel = VIPER 150 Revision = * I assumed the match would happen like this: (bt0:6:0): "ARCHIVE VIPER 150 21247 -005" type 1 removable SCSI 1 MMMMMMM OOOOOOOOO RRRRRRRRRR but it does NOT because the drive returns the information like: (bt0:6:0): "ARCHIVE VIPER 150 21247 -005" type 1 removable SCSI 1 MMMMMMM OOOOOOOOOOOOOOOO RRRR which means the model field either has to have a wildcard or, be more completely specified. The big clue was the fact that the three fields are fixed in length, and the revision field is only four bytes. The light went on in my head that the 21247 was in the model field. Without being more completely specified, or wildcarded the quirk list entry will never match the drive. The patch below fixes the problem. If there are no objections, I'll commit the change. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ *** scsiconf.c.orig Tue May 28 14:46:08 1996 --- scsiconf.c Tue May 28 19:08:45 1996 *************** *** 276,282 **** "st", SC_ONE_LU, 0, mode_archive2525 }, { ! T_SEQUENTIAL, T_SEQUENTIAL, T_REMOV, "ARCHIVE", "VIPER 150", "*", "st", SC_ONE_LU, ST_Q_NEEDS_PAGE_0, mode_archive150 }, { --- 276,282 ---- "st", SC_ONE_LU, 0, mode_archive2525 }, { ! T_SEQUENTIAL, T_SEQUENTIAL, T_REMOV, "ARCHIVE", "VIPER 150 *", "*", "st", SC_ONE_LU, ST_Q_NEEDS_PAGE_0, mode_archive150 }, { From owner-freebsd-scsi Fri May 31 04:58:55 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA08442 for freebsd-scsi-outgoing; Fri, 31 May 1996 04:58:55 -0700 (PDT) Received: from hda (ip57-max1-fitch.zipnet.net [199.232.245.57]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA08437 for ; Fri, 31 May 1996 04:58:53 -0700 (PDT) Received: (from dufault@localhost) by hda (8.6.11/8.6.9) id IAA06323; Fri, 31 May 1996 08:00:28 -0400 From: Peter Dufault Message-Id: <199605311200.IAA06323@hda> Subject: Re: Archive Viper not correctly identified. To: jfieber@indiana.edu (John Fieber) Date: Fri, 31 May 1996 08:00:27 -0400 (EDT) Cc: scsi@FreeBSD.org In-Reply-To: from "John Fieber" at May 30, 96 06:56:05 pm Reply-to: hdalog@zipnet.net X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > The patch below fixes the problem. If there are no objections, > I'll commit the change. (add a "*" to the archive list) Right now a short name has implied spaces at the end - does an implied "*" at the end of a short name makes more sense? -- Peter Dufault Real-Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-scsi Fri May 31 06:25:32 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA11622 for freebsd-scsi-outgoing; Fri, 31 May 1996 06:25:32 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA11617 for ; Fri, 31 May 1996 06:25:30 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id IAA14329; Fri, 31 May 1996 08:25:22 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Fri, 31 May 1996 08:25:21 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: hdalog@zipnet.net cc: scsi@FreeBSD.org Subject: Re: Archive Viper not correctly identified. In-Reply-To: <199605311200.IAA06323@hda> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 31 May 1996, Peter Dufault wrote: > (add a "*" to the archive list) > > Right now a short name has implied spaces at the end - does an implied > "*" at the end of a short name makes more sense? Having an explicit wildcard there makes it reasonably clear to someone browsing the code how the matching is intended to work without having to read the actual matching code. Also, unless an explicit space is added after a name, you could get a false match. Imagine archive makes a viper 1500. The string "VIPER 150" would match "VIPER 1500" which may not be desired. I think requiring a * to ensure a match will be more intuitive and less prone to programmer error than requiring a trailing space to prevent a false match. (not that it would occur often, but it might...) Regardless, a more informative comment at the head of the quirk list describing the policy, and mentioning the fact that the manufacturer, model and revision fields are 8, 16 and 4 bytes respectively would be helpful to future quriklist maintainers. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-scsi Fri May 31 21:10:35 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA07553 for freebsd-scsi-outgoing; Fri, 31 May 1996 21:10:35 -0700 (PDT) Received: from sunfire.j51.com (sunfire.j51.com [199.224.7.165]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA07548 for ; Fri, 31 May 1996 21:10:33 -0700 (PDT) Received: (from afurman@localhost) by sunfire.j51.com (8.6.12/8.6.12) id AAA22689; Sat, 1 Jun 1996 00:13:25 -0400 Date: Sat, 1 Jun 1996 00:13:24 -0400 (EDT) From: Adam Furman To: freebsd-scsi@freebsd.org Subject: Parallel to Scsi Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a FreeBSD server that has IDE drives in it. I would like to get the Belkin one because I would like to move around my external dat drive and would find this conivernt and chaper. Please let mw know if the Belkin adapter would work and what I have to do. This would be greatly appreciated. Thanks Adam Adam Furman System Administrator of Sunfire.j51.com afurman@amf.net Irc Operator of irc.j51.com Mud Admin of sufire.j51.com:4000