From owner-freebsd-scsi Sun Nov 3 03:44:00 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA16524 for freebsd-scsi-outgoing; Sun, 3 Nov 1996 03:44:00 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA16516 for ; Sun, 3 Nov 1996 03:43:56 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id NAA16876 for scsi@freebsd.org; Sun, 3 Nov 1996 13:30:23 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.2/8.8.2) with SMTP id MAA00432 for ; Sun, 3 Nov 1996 12:13:40 +0100 (MET) Date: Sun, 3 Nov 1996 12:13:39 +0100 (MET) From: Andreas Klemm To: scsi@freebsd.org Subject: Is it possible to add a scsi tape after boot ? Rescan of scsi bus ? Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ! I'm used to power down my external tape, because the fan's are a bit loud. But FreeBSD can't recognize the tape, if it wasn't ,on' while booting. On SunOS 4 the scsi tape driver does an inquiry as soon as you write onto the tape device. SunOS5 with it's dynamically kernel driver allows you to rescan the systems devices with a ,drvconfig' command, which scans the hardware. Is there a utility in FreeBSD-current, which causes a tape to be recognizes after booting ? I hardwired my scsi devices, but that didn't help. controller ahc0 controller scbus0 at ahc0 disk sd0 at scbus0 target 0 disk sd1 at scbus0 target 1 tape st0 at scbus0 target 4 device cd0 at scbus0 target 6 Would be nice, if someone could help me. Thanks Andreas /// -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-scsi Sun Nov 3 05:07:49 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA22343 for freebsd-scsi-outgoing; Sun, 3 Nov 1996 05:07:49 -0800 (PST) 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 FAA22334 for ; Sun, 3 Nov 1996 05:07:44 -0800 (PST) Received: by mail.ruhrgebiet.individual.net (8.7.1/8.6.12) with UUCP id NAA27464; Sun, 3 Nov 1996 13:51:38 +0100 (MET) Received: by robkaos.ruhr.de (/\oo/\ Smail3.1.29.1 #29.1) id ; Sun, 3 Nov 96 13:33 MET Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Re: Is it possible to add a scsi tape after boot ? Rescan of scsi bus ? In-Reply-To: from Andreas Klemm at "Nov 3, 96 12:13:39 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Sun, 3 Nov 1996 13:33:25 +0100 (MET) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi ! > > I'm used to power down my external tape, because the fan's are a bit > loud. But FreeBSD can't recognize the tape, if it wasn't ,on' while > booting. > > On SunOS 4 the scsi tape driver does an inquiry as soon as you write > onto the tape device. > > SunOS5 with it's dynamically kernel driver allows you to rescan the > systems devices with a ,drvconfig' command, which scans the hardware. > > Is there a utility in FreeBSD-current, which causes a tape to be > recognizes after booting ? > > I hardwired my scsi devices, but that didn't help. > > controller ahc0 > controller scbus0 at ahc0 > disk sd0 at scbus0 target 0 > disk sd1 at scbus0 target 1 > tape st0 at scbus0 target 4 > device cd0 at scbus0 target 6 > > Would be nice, if someone could help me. > Yes, it would be nice if one had a kind of generic 'super-scsi' device, with which it would be possible to rescan the SCSI bus. As far as I remember such a beast was planned long time ago... I would need it for my MO drive which is turned off most of the time. Or for my CD-R burner which sometimes gives an ioctl error message and where the only solution up to now is to reboot..... Robert From owner-freebsd-scsi Sun Nov 3 06:21:43 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA25877 for freebsd-scsi-outgoing; Sun, 3 Nov 1996 06:21:43 -0800 (PST) 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 GAA25868 for ; Sun, 3 Nov 1996 06:21:35 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id PAA20067; Sun, 3 Nov 1996 15:21:24 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA00744; Sun, 3 Nov 1996 15:21:24 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id PAA09461; Sun, 3 Nov 1996 15:03:03 +0100 (MET) From: J Wunsch Message-Id: <199611031403.PAA09461@uriah.heep.sax.de> Subject: Re: Is it possible to add a scsi tape after boot ? Rescan of scsi bus ? To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Sun, 3 Nov 1996 15:03:03 +0100 (MET) Cc: andreas@klemm.gtn.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Robert Schien at "Nov 3, 96 01:33:25 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 Robert Schien wrote: > > Is there a utility in FreeBSD-current, which causes a tape to be > > recognizes after booting ? > Yes, it would be nice if one had a kind of generic 'super-scsi' device, > with which it would be possible to rescan the SCSI bus. The super-scsi device is only needed (as an alias for the entire bus) if no other SCSI device has been available at boot time. As soon as at least one device came up at boot time, you can do scsi -f /dev/rsd0.ctl -r ^^^^ use whatever device is actually already available This used to hang the entire machine in older systems, but recent 2.2-current's seem to work (at least with an AHA2940 that never worked with -r before). I think Justin's SCSI branch cleans up allot in this area. -- 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 Nov 3 10:23:30 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA13697 for freebsd-scsi-outgoing; Sun, 3 Nov 1996 10:23:30 -0800 (PST) Received: from In-Net.inba.fr (root@arthur.inba.fr [194.51.120.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA13688 for ; Sun, 3 Nov 1996 10:23:26 -0800 (PST) Received: from uther.inba.fr (uther.inba.fr [194.51.120.62]) by In-Net.inba.fr (8.6.12/8.6.9) with SMTP id TAA13495 for ; Sun, 3 Nov 1996 19:23:22 +0100 Message-Id: <1.5.4.16.19961103182934.2417b6a0@mail.inba.fr> X-Sender: psc@mail.inba.fr X-Mailer: Windows Eudora Light Version 1.5.4 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 03 Nov 1996 19:29:34 +0100 To: freebsd-scsi@FreeBSD.ORG From: Philippe SCHACK Subject: Micronics MotherBoard Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, I have installed FreeBSD with a P75 on a Micronics D5CUB PCI/ISA card and have the following problems: I have installed a Adaptec SCSI AHA-1542B card with a TANDBERG TDC-3800 Streamer . When i boot on the BOOT FLOPPY, the system hangs after displaying a part of the Tandberg TDC 3800 informations. If I disconnect the streamer to install FreeBSD, all is OK. But when i want to use it with a kernel wich use the adaptec card, I have the same problem. I have modified the SCSI_DELAY to 30 => same problem I have used the TUNE_1542 option => same problem Does anyone have any information to help me please ? The same material (Adaptec card floppy) on a 486 DLC card works fine. Thank's P.SCHACK From owner-freebsd-scsi Sun Nov 3 10:57:46 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA15081 for freebsd-scsi-outgoing; Sun, 3 Nov 1996 10:57:46 -0800 (PST) Received: from rosemary.fsl.noaa.gov (rosemary.fsl.noaa.gov [137.75.8.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA15067 for ; Sun, 3 Nov 1996 10:57:26 -0800 (PST) Received: from sage.fsl.noaa.gov (sage.fsl.noaa.gov [137.75.253.42]) by rosemary.fsl.noaa.gov (8.7.5/8.6.12) with SMTP id LAA06074 for ; Sun, 3 Nov 1996 11:57:09 -0700 (MST) Message-ID: <327CEB04.41C67EA6@fsl.noaa.gov> Date: Sun, 03 Nov 1996 11:57:08 -0700 From: Sean Kelly Organization: NOAA Forecast Systems Laboratory X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: scsi@freebsd.org Subject: Write me some blank checks ... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What does this mean? Nov 3 11:51:54 sage /kernel: st1(bt0:3:0): BLANK CHECK req sz: 32768 (decimal) I wish it meant I could receive some blank checks ... I could use the money, but I have a feeling that's not quite what it's supposed to be. -- Sean Kelly NOAA Forecast Systems Laboratory Boulder Colorado USA From owner-freebsd-scsi Sun Nov 3 12:24:54 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA19866 for freebsd-scsi-outgoing; Sun, 3 Nov 1996 12:24:54 -0800 (PST) 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 MAA19768 for ; Sun, 3 Nov 1996 12:23:02 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA02159; Sun, 3 Nov 1996 21:21:46 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA06899; Sun, 3 Nov 1996 21:21:26 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id VAA27322; Sun, 3 Nov 1996 21:00:07 +0100 (MET) From: J Wunsch Message-Id: <199611032000.VAA27322@uriah.heep.sax.de> Subject: Re: Write me some blank checks ... To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Sun, 3 Nov 1996 21:00:06 +0100 (MET) Cc: kelly@fsl.noaa.gov (Sean Kelly) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <327CEB04.41C67EA6@fsl.noaa.gov> from Sean Kelly at "Nov 3, 96 11:57:08 am" 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 Sean Kelly wrote: > What does this mean? > > Nov 3 11:51:54 sage /kernel: st1(bt0:3:0): BLANK CHECK req sz: 32768 > (decimal) > > I wish it meant I could receive some blank checks ... I could use the > money, but I have a feeling that's not quite what it's supposed to be. That's only since you Americans are abusing the English language too much, so you cannot distinguish between a check and a cheque now. :-) ``Blank check'' means that you've tried to read unwritten tape area, i.e. read past end of recorded medium. -- 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 Nov 3 14:52:27 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA06246 for freebsd-scsi-outgoing; Sun, 3 Nov 1996 14:52:27 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA06214 for ; Sun, 3 Nov 1996 14:52:20 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vKBOg-00020z-00; Sun, 3 Nov 1996 15:52:06 -0700 To: scsi@freebsd.org Subject: FYI Date: Sun, 03 Nov 1996 15:52:06 -0700 From: Warner Losh Message-Id: Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Found the following in a computer city here. It is a Siig i540 (no floppy) or i542 (w/ floppy). However, under the black paint are AdvanSys chips and artwork. The obscured artwork says AdvanSys ABP-5140/42. Has a AdvanSys chip labeled: ASC1090-B F01 ASQ01455.1 A01 011635 It was $179 at Computer City. ISA card with kit that included drivers for everything (including Linux and Unixware). However, I'm unable to stick it into a machine to see if Julian's new SCSI drivers will see it. When that driver comes into the real tree, we should add this card to the compatibility list :-). No clue if this is worth the price or not, but I just thought I'd pass this along to people on the list here. Warner From owner-freebsd-scsi Sun Nov 3 20:56:04 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA13678 for freebsd-scsi-outgoing; Sun, 3 Nov 1996 20:56:04 -0800 (PST) Received: from rosemary.fsl.noaa.gov (rosemary.fsl.noaa.gov [137.75.8.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA13631 for ; Sun, 3 Nov 1996 20:55:59 -0800 (PST) Received: from sage.fsl.noaa.gov (sage.fsl.noaa.gov [137.75.253.42]) by rosemary.fsl.noaa.gov (8.7.5/8.6.12) with SMTP id VAA06570; Sun, 3 Nov 1996 21:55:32 -0700 (MST) Message-ID: <327D7743.41C67EA6@fsl.noaa.gov> Date: Sun, 03 Nov 1996 21:55:31 -0700 From: Sean Kelly Organization: NOAA Forecast Systems Laboratory X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: Joerg Wunsch CC: FreeBSD SCSI list Subject: Re: Write me some blank checks ... References: <199611032000.VAA27322@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > ``Blank check'' means that you've tried to read unwritten tape area, > i.e. read past end of recorded medium. Thanks, J"org. Unfortunately, I get these messages on tapes I've just written. So now it means I have to write a "cheque" to get a faulty tape drive repaired. :-) -- Sean Kelly NOAA Forecast Systems Laboratory Boulder Colorado USA From owner-freebsd-scsi Mon Nov 4 01:34:23 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA18114 for freebsd-scsi-outgoing; Mon, 4 Nov 1996 01:34:23 -0800 (PST) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA18086 for ; Mon, 4 Nov 1996 01:34:14 -0800 (PST) Received: from sol1.gud.siemens.co.at (root@[10.1.143.100]) by zwei.siemens.at (8.7.5/8.7.3) with SMTP id KAA26011 for ; Mon, 4 Nov 1996 10:32:51 +0100 (MET) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0vKLPY-00021LC; Mon, 4 Nov 96 10:33 MET Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA277309956; Mon, 4 Nov 1996 10:32:36 +0100 From: "Hr.Ladavac" Message-Id: <199611040932.AA277309956@ws2301.gud.siemens.co.at> Subject: Re: FreeBSD support for Adaptec/Buslogic drivers To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 4 Nov 1996 10:32:35 +0100 (MEZ) Cc: lada@ws2301.gud.siemens.co.at, imp@village.org, scsi@freebsd.org In-Reply-To: <199610311654.IAA04790@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Oct 31, 96 08:54:17 am X-Mailer: ELM [version 2.4 PL24 ME8a] 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 E-mail message from Rodney W. Grimes contained: > > E-mail message from Warner Losh contained: > > > > > > In message <199610311020.AA031447211@ws2301.gud.siemens.co.at> > > > "Hr.Ladavac" writes: > > > : If you want cheap SCSI, how about NCR? > > > > > > Any "brand names" that have a NCR chip on them? Or is this only for > > > those controllers that are built into motherboards? > > > > ASUS SC200 (or something like that) if you require a brand name. > > Otherwise, any run-of-the-mill NCR *810 controller will do, as they are > > nothing more than the chip, a connector, and pcb traces binding them > > together. > > They are not all equal, the ``cheap'' ones use passive termination, > the good ones (ASUS SC-200 and many others) use active termination. Alas, that is true. However, since the resistors are the first thing to go out, and the internal and external active termination goes in, I don't really care--never had a problem. I should have mentioned that in my e-mail, though. Thanks for correcting me. /Marino > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation, Inc. Reliable computers for FreeBSD > From owner-freebsd-scsi Mon Nov 4 03:50:24 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA01319 for freebsd-scsi-outgoing; Mon, 4 Nov 1996 03:50:24 -0800 (PST) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA01313 for ; Mon, 4 Nov 1996 03:50:15 -0800 (PST) Received: (from uucp@localhost) by frmug.org (8.8.2/8.8.2/frmug-1.2) with UUCP id MAA16829 for freebsd-scsi@freebsd.org; Mon, 4 Nov 1996 12:47:46 +0100 (MET) Received: (from elrond@localhost) by imladris.frmug.fr.net (8.7.5/8.7.3) id MAA22416 for freebsd-scsi@freebsd.org; Mon, 4 Nov 1996 12:31:26 +0100 (MET) From: Bertrand Petit Message-Id: <199611041131.MAA22416@imladris.frmug.fr.net> Subject: SCSI phase error To: freebsd-scsi@freebsd.org Date: Mon, 4 Nov 1996 12:31:25 +0100 (MET) X-roberto: ce sont X-remibp: Ah! It is marching. X-Mailer: ELM [version 2.4 PL20] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! I've upgraded from 2.1 to 2.2-960501-SNAP ans now experience SCSI troubles with a NOMAI MCD540I unit. This unit, after a BIOS update worked well with 2.1 but now produce a 'SCSI phase error fixup: CDB already dequed' at boot time. Then NCR errors (I don't have the time to copy them) are genarated including for units remaining to be probed (a Plextor CDrom). Then kernel freeze. What's wrong? Thanks. -- %!ps | Bertrand Petit alias | elrond@imladris.frmug.fr.net | Cette zone est | % | >elrond le demi-Elfe< | elrond@freenix.fr | a louer | 550 0 translate 90 rotate/NewCenturySchlbk-Bold findfont 690 scalefont setfont -5 15 moveto(42)true charpath clip/Helvetica-Bold findfont 8 scalefont setfont 0 9 800{dup 360 mod 360 div 1 1 sethsbcolor/y exch def rand 10 mod neg 11 800 {y moveto(42)show}for}for clippath 4 setlinewidth 0 setgray stroke showpage From owner-freebsd-scsi Mon Nov 4 04:23:54 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA06540 for freebsd-scsi-outgoing; Mon, 4 Nov 1996 04:23:54 -0800 (PST) Received: from viking.ucsalf.ac.uk (viking.ucsalf.ac.uk [192.195.1.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA06519 for ; Mon, 4 Nov 1996 04:23:48 -0800 (PST) Received: by viking.ucsalf.ac.uk (Smail3.1.29.1 #4) id m0vKO42-000375C; Mon, 4 Nov 96 12:23 GMT Message-Id: From: news@HAMMER.msfc.nasa.gov Subject: cmsg cancel <366.654193326831@news.nemonet.com> no reply ignore To: freebsd-scsi@freebsd.org Date: Sun, 3 Nov 1996 01:08:24 GMT Reply-To: bitbucket@HAMMER.msfc.nasa.gov X-Gated-To-News-By: news@ucsalf.ac.uk X-No-Archive: Yes X-Canceled-by: news@news.msfc.nasa.gov Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ignore Make Money Fast post canceled by news@news.msfc.nasa.gov. Make Money Fast has been posted thousands of times, enough to qualify as cancel-on-sight spam. The chain letter scheme it describes is illegal in many countries. For example, see: http://www.usps.gov/websites/depart/inspect/chainlet.htm From owner-freebsd-scsi Wed Nov 6 15:23:21 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA06781 for freebsd-scsi-outgoing; Wed, 6 Nov 1996 15:23:21 -0800 (PST) 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 PAA06774; Wed, 6 Nov 1996 15:23:16 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA23930; Thu, 7 Nov 1996 00:21:57 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA18953; Thu, 7 Nov 1996 00:21:57 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id AAA22415; Thu, 7 Nov 1996 00:07:43 +0100 (MET) From: J Wunsch Message-Id: <199611062307.AAA22415@uriah.heep.sax.de> Subject: Re: INSITE floptical anybody ??? To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Thu, 7 Nov 1996 00:07:42 +0100 (MET) Cc: sos@FreeBSD.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199611062253.XAA02949@ravenock.cybercity.dk> from "sos@FreeBSD.org" at "Nov 6, 96 11:53:39 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 (Redirected to -scsi) As sos@FreeBSD.org wrote: > I just had one of those drop on my table so I hooked it > up to the SCSI system, and well, its found but then it > hangs the SCSI subsystem. I glanced through some other > systems scsi files, and saw that the INSITE floptical > needs some kind of "unlock" sequence in order to > work proberly, anybody allready done the nessesary > magic ?? or will I have to get my fingers dirty in the > SCSI code too... I've once tried, too, and eventually gave up. :-( These parts came along with our SGI Indys, but don't worry, they basically turned out to be the worst crap i've ever seen in this area. Don't spend too much time into that driver, or the drive will be dead before you finished polishing the SCSI code... :-(( Hint: pick the `od' driver to start with, it is already better in supporting unit attention conditions etc. -- 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 Wed Nov 6 17:51:35 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA16038 for freebsd-scsi-outgoing; Wed, 6 Nov 1996 17:51:35 -0800 (PST) Received: from viking.ucsalf.ac.uk (viking.ucsalf.ac.uk [192.195.1.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA16033 for ; Wed, 6 Nov 1996 17:51:29 -0800 (PST) Received: by viking.ucsalf.ac.uk (Smail3.1.29.1 #4) id m0vLJci-000377C; Thu, 7 Nov 96 01:51 GMT Message-Id: From: dsr@lns598.lns.cornell.edu Subject: cmsg cancel <778.051093963906@news.nemonet.com> no reply ignore To: freebsd-scsi@freebsd.org Date: 06 Nov 1996 17:54:36 EST X-Gated-To-News-By: news@ucsalf.ac.uk X-Cancelled-By: dsr@lns598.lns.cornell.edu X-No-Archive: Yes Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk MMF cancelled by dsr@lns598.lns.cornell.edu original subject was Just try this, it will work From owner-freebsd-scsi Thu Nov 7 00:11:53 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA10300 for freebsd-scsi-outgoing; Thu, 7 Nov 1996 00:11:53 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA10177; Thu, 7 Nov 1996 00:09:23 -0800 (PST) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id JAA23177; Thu, 7 Nov 1996 09:07:35 +0100 Message-Id: <199611070807.JAA23177@ra.dkuug.dk> Subject: Re: INSITE floptical anybody ??? To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 7 Nov 1996 09:07:35 +0100 (MET) Cc: freebsd-scsi@FreeBSD.org, sos@FreeBSD.org In-Reply-To: <199611062307.AAA22415@uriah.heep.sax.de> from "J Wunsch" at Nov 7, 96 00:07:42 am From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to J Wunsch who wrote: > > (Redirected to -scsi) > > As sos@FreeBSD.org wrote: > > > I just had one of those drop on my table so I hooked it > > up to the SCSI system, and well, its found but then it > > hangs the SCSI subsystem. I glanced through some other > > systems scsi files, and saw that the INSITE floptical > > needs some kind of "unlock" sequence in order to > > work proberly, anybody allready done the nessesary > > magic ?? or will I have to get my fingers dirty in the > > SCSI code too... > > I've once tried, too, and eventually gave up. :-( These parts > came along with our SGI Indys, but don't worry, they basically > turned out to be the worst crap i've ever seen in this area. > Don't spend too much time into that driver, or the drive will be > dead before you finished polishing the SCSI code... :-(( :), well I kind of got it into a working mode by looking some more at the linux code. It seems it need a special MODE_SENSE command that makes it work like a "normal" scsi device. It should be dealt with via a quirk or something. > Hint: pick the `od' driver to start with, it is already better in > supporting unit attention conditions etc. Good idea, I hacked sd.c, because thats the driver that found the floptical, but thats easily changed... Well, the drives are out of production, so it has no real value I just thougt of it as a SCSI floppy drive :) which would be nice to have at times... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-scsi Thu Nov 7 01:13:25 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA13776 for freebsd-scsi-outgoing; Thu, 7 Nov 1996 01:13:25 -0800 (PST) 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 BAA13770; Thu, 7 Nov 1996 01:13:13 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA10230; Thu, 7 Nov 1996 10:12:37 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA29303; Thu, 7 Nov 1996 10:12:36 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id KAA00703 for freebsd-scsi@FreeBSD.org; Thu, 7 Nov 1996 10:03:26 +0100 (MET) From: J Wunsch Message-Id: <199611070903.KAA00703@uriah.heep.sax.de> Subject: Re: INSITE floptical anybody ??? To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Cc: sos@FreeBSD.org Date: Thu, 7 Nov 1996 10:03:26 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199611070807.JAA23177@ra.dkuug.dk> from "sos@FreeBSD.org" at "Nov 7, 96 09:07:35 am" 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 sos@FreeBSD.org wrote: > Well, the drives are out of production, so it has no real value > I just thougt of it as a SCSI floppy drive :) which would be > nice to have at times... ...but fairly slow. :-( -- 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 Nov 7 01:32:48 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA15192 for freebsd-scsi-outgoing; Thu, 7 Nov 1996 01:32:48 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA15185; Thu, 7 Nov 1996 01:32:28 -0800 (PST) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id KAA23906; Thu, 7 Nov 1996 10:27:29 +0100 Message-Id: <199611070927.KAA23906@ra.dkuug.dk> Subject: Re: INSITE floptical anybody ??? To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 7 Nov 1996 10:27:29 +0100 (MET) Cc: freebsd-scsi@FreeBSD.org, sos@FreeBSD.org In-Reply-To: <199611070903.KAA00703@uriah.heep.sax.de> from "J Wunsch" at Nov 7, 96 10:03:26 am From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to J Wunsch who wrote: > > As sos@FreeBSD.org wrote: > > > Well, the drives are out of production, so it has no real value > > I just thougt of it as a SCSI floppy drive :) which would be > > nice to have at times... > > ...but fairly slow. :-( Well, so far it seems to be as fast as a normal floppy drive :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-scsi Fri Nov 8 14:52:17 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA15604 for freebsd-scsi-outgoing; Fri, 8 Nov 1996 14:52:17 -0800 (PST) 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 OAA15560 for ; Fri, 8 Nov 1996 14:51:49 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA27850; Fri, 8 Nov 1996 23:51:19 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA16949; Fri, 8 Nov 1996 23:51:19 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id XAA08109; Fri, 8 Nov 1996 23:40:27 +0100 (MET) From: J Wunsch Message-Id: <199611082240.XAA08109@uriah.heep.sax.de> Subject: Re: Pinnacle RCD Driver To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Fri, 8 Nov 1996 23:40:27 +0100 (MET) Cc: lslile@lexmark.com (Larry S Lile) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199611081632.AA02293@interlock.lexmark.com> from Larry S Lile at "Nov 8, 96 11:29:16 am" 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 (Moved to -scsi) As Larry S Lile wrote: > > I am currently working on a driver for the Pinnacle RCD 5040i. My > > original plan was to attempt to integrate support for this device under > > Joerg's worm driver but it differs to much from the HP/Phillips drives > > to do this (or at least for me to be able to) Why? I hesitate seeing multiple drivers for the same purpose unless really necessary. The driver framework in worm.c was meant to satisfy different types of burners. If this isn't true for a particular device, we should really consider rewriting worm.c, instead of whacking another driver. > > I am also trying to write the > > driver in such a way that I can interface directly back to Julian's cd > > driver to give the device full functionality as both an RCD and CD. That's also on the TODO list for the worm driver. I never got a good idea how to integrate the `cd' stuff without duplicating it, and without massively violating the layering principles. > > As to minor numbers, I have seen mention of things like "5 bit unit" in > > the cd driver, according to documentation Pinnacle sent to me the RCD > > is an 8 bit device, but supports all cd commands that the cd driver has > > implemented. So do I set up the minor number in the same way Julian > > set up the minor number for a cd or should I use the method that Joerg > > used for the worm driver as the RCD is a worm device? Or have they > > taken two different implementation methods because cd supports both > > block and character but worm only currently supports character. worm should also support block devs, it's simply an omission. Can be fixed within some 10 minutes or so, but there's not much use in fixing it as long as the read functionality is broken. I think the final decision about which minor numbering should be used is a fairly low-priority issue. The worm driver is not actually by me, the original roots have been written by Peter Dufault, and i believe he's been cloning the `sd' driver rather than the `cd' driver. > > Second, I have seen what appear to be 2 disperate cdevsw structure > > definitions, could some one clarify what exactly the definition of this > > should be for me. I have compared the implementation of sd, cd, and > > worm but now I am totally confused Where have you seen two of them? I can only find one, in: j@uriah 179% fgrep cdevsw /sys/sys/* /sys/sys/conf.h: struct cdevsw *d_cdev; /* cross pointer to the cdev */ /sys/sys/conf.h:struct cdevsw { ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Last, I really don't get the partition stuff in the cd driver whatsoever, > > or worse the device filesystem (DEVFS) stuff. Don't worry about this in the first place. Concentrate on the actual driver first. The `cd' driver should also be tweaked someday to support reading multiple data tracks, and to support something that could be used by the `cd9660' filesystem to access what ISO9660 calls `multi-session' CDs. And it should allow reading audio tracks, but that's a far more difficult task (since there's no standard on this). So as you can see, the `cd' driver is subject to changes in its minor numbering, too... I once started with that work, but eventually suspended it by the time when Justin announced his massive SCSI subsystem rewrites. Maybe, after 2.2R is ready, i'll continue where i left off. > > I am fairly sure that I can write the driver functions to operate the drive, > > its just the interface to the kernel and low-level scsi driver that I don't > > understand. I have just never had to deal with them before and I don't > > have much documentation on what is required to do so. Careful: the interface to the low-level driver has changed with the new SCSI code. -- 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 Fri Nov 8 17:35:32 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA26668 for freebsd-scsi-outgoing; Fri, 8 Nov 1996 17:35:32 -0800 (PST) Received: from deacon.cogsci.ed.ac.uk (deacon.cogsci.ed.ac.uk [129.215.144.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA26658 for ; Fri, 8 Nov 1996 17:35:26 -0800 (PST) From: richard@cogsci.ed.ac.uk Received: from pitcairn.cogsci.ed.ac.uk (pitcairn.cogsci.ed.ac.uk [129.215.197.19]) by deacon.cogsci.ed.ac.uk (8.6.10/8.6.12) with ESMTP id BAA09909 for ; Sat, 9 Nov 1996 01:34:36 GMT Date: Sat, 9 Nov 1996 01:34:36 GMT Message-Id: <10059.199611090134@pitcairn.cogsci.ed.ac.uk> To: freebsd-scsi@freebsd.org Subject: AIC 6360 in Dell docking station Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a Dell laptop whose docking station includes an AIC-6360 based SCSI adaptor. This isn't recognised (by 2.1.5 GENERIC). Am I right in thinking that only PCI adaptors based on this chipset are supported? According to the manual, the version in the docking station is on the ISA bus. -- Richard From owner-freebsd-scsi Fri Nov 8 17:59:56 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA28126 for freebsd-scsi-outgoing; Fri, 8 Nov 1996 17:59:56 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA28115; Fri, 8 Nov 1996 17:59:53 -0800 (PST) Message-Id: <199611090159.RAA28115@freefall.freebsd.org> To: richard@cogsci.ed.ac.uk cc: freebsd-scsi@freebsd.org Subject: Re: AIC 6360 in Dell docking station In-reply-to: Your message of "Sat, 09 Nov 1996 01:34:36 GMT." <10059.199611090134@pitcairn.cogsci.ed.ac.uk> Date: Fri, 08 Nov 1996 17:59:53 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I have a Dell laptop whose docking station includes an AIC-6360 based >SCSI adaptor. This isn't recognised (by 2.1.5 GENERIC). Am I right in >thinking that only PCI adaptors based on this chipset are supported? >According to the manual, the version in the docking station is on the >ISA bus. > >-- Richard Don't confuse the aic-6360 with the aic-7xxx series of chips. We have a good driver for the 7xxx guys, but a really shaky one for the 6360. It seems that there are more and more systems shipping with these cheap controller chips in them, so I'll put the 6360 driver just below the buslogic one in my queue. The 6360 looks very similar to a 7xxx chip without an onboard processor, so it should be pretty easy to fix it up based on my 7xxx experience. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Sat Nov 9 17:45:46 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA02997 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 17:45:46 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [193.125.152.6]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA02991; Sat, 9 Nov 1996 17:45:42 -0800 (PST) Received: by sequent.kiae.su id AA04033 (5.65.kiae-2 ); Sun, 10 Nov 1996 05:34:52 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Sun, 10 Nov 96 05:34:51 +0400 Received: (from ache@localhost) by nagual.ru (8.8.2/8.8.2) id EAA00401; Sun, 10 Nov 1996 04:33:25 +0300 (MSK) Message-Id: <199611100133.EAA00401@nagual.ru> Subject: SCSI system becomes broken in -current? To: current@freebsd.org (FreeBSD-current), scsi@freebsd.org Date: Sun, 10 Nov 1996 04:33:24 +0300 (MSK) From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It work for me without any error for very long time, but after todays rebuild I often got: sd0(ahc0:0:0): timed out in dataout phase, SCSISIGI == 0x0 Ordered Tag queued Ordered Tag sent sd0(ahc0:0:0): timed out in dataout phase, SCSISIGI == 0x0 sd0(ahc0:0:0): timed out in dataout phase, SCSISIGI == 0x0 ahc0: Issued Channel A Bus Reset. 4 SCBs aborted sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 sd0(ahc0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 , retries:3 sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 sd1(ahc0:1:0): Power on, reset, or bus device reset occurred , retries:4 Ordered Tag sent sd1(ahc0:1:0): NOT READY asc:4,1 sd1(ahc0:1:0): Logical unit is in process of becoming ready , retries:3 sd1(ahc0:1:0): NOT READY asc:4,1 sd1(ahc0:1:0): Logical unit is in process of becoming ready , retries:2 sd1(ahc0:1:0): NOT READY asc:4,1 sd1(ahc0:1:0): Logical unit is in process of becoming ready , retries:1 sd1(ahc0:1:0): NOT READY asc:4,1 sd1(ahc0:1:0): Logical unit is in process of becoming ready , FAILURE sd0(ahc0:0:0): timed out in dataout phase, SCSISIGI == 0x0 Ordered Tag queued Ordered Tag sent Ordered Tag sent sd0(ahc0:0:0): timed out in dataout phase, SCSISIGI == 0x0 sd0(ahc0:0:0): timed out in dataout phase, SCSISIGI == 0x0 ahc0: Issued Channel A Bus Reset. 4 SCBs aborted sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 sd0(ahc0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 , retries:3 sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 sd1(ahc0:1:0): Power on, reset, or bus device reset occurred , retries:4 etc.............................................................. I have ahc0: at 0x1c00-0x1cff irq 11 on eisa0 slot 1 ahc0: aic7770 >= Rev E, Single Channel, SCSI Id=7, 4 SCBs ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "CONNER CFP1060S 1.05GB 2135" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 1013MB (2074880 512 byte sectors) ahc0: target 1 Tagged Queuing Device (ahc0:1:0): "IBM DORS-32160 S84A" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 2063MB (4226725 512 byte sectors) -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-scsi Sat Nov 9 18:15:49 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA04558 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 18:15:49 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA04532; Sat, 9 Nov 1996 18:15:44 -0800 (PST) Message-Id: <199611100215.SAA04532@freefall.freebsd.org> To: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) cc: current@freebsd.org (FreeBSD-current), scsi@freebsd.org Subject: Re: SCSI system becomes broken in -current? In-reply-to: Your message of "Sun, 10 Nov 1996 04:33:24 +0300." <199611100133.EAA00401@nagual.ru> Date: Sat, 09 Nov 1996 18:15:43 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I have >ahc0: at 0x1c00-0x1cff irq 11 on eisa0 slot 1 >ahc0: aic7770 >= Rev E, Single Channel, SCSI Id=7, 4 SCBs >ahc0: target 0 Tagged Queuing Device >(ahc0:0:0): "CONNER CFP1060S 1.05GB 2135" type 0 fixed SCSI 2 >sd0(ahc0:0:0): Direct-Access 1013MB (2074880 512 byte sectors) Do you have the required firmware upgrade for this drive that makes tagged queuing work correctly with it? The driver is a bit faster then it was before and I don't know exactly what it was about this drive that makes it go out to lunch, but it wouldn't surprise me if getting transactions too quickly caused you problems. I do not know where you can get the firmware upgrade from. I tried www.conner.com, but Seagate has that now... >-- >Andrey A. Chernov > >http://www.nagual.ru/~ache/ -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Sat Nov 9 18:42:31 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA05673 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 18:42:31 -0800 (PST) Received: from sumter.awod.com (awod.com [198.81.225.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA05666; Sat, 9 Nov 1996 18:42:23 -0800 (PST) Received: from tsunami..awod.com ([206.30.179.200]) by sumter.awod.com (8.7.6/8.6.12) with SMTP id VAA29275; Sat, 9 Nov 1996 21:42:09 -0500 (EST) Message-Id: <3.0.32.19961109214202.00d8cef8@awod.com> X-Sender: klam@awod.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 09 Nov 1996 21:42:05 -0500 To: "Justin T. Gibbs" , "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) From: Ken Lam Subject: Re: SCSI system becomes broken in -current? Cc: current@FreeBSD.org (FreeBSD-current), scsi@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk At 06:15 PM 11/9/96 -0800, Justin T. Gibbs wrote: >>I have >>ahc0: at 0x1c00-0x1cff irq 11 on eisa0 slot 1 >>ahc0: aic7770 >= Rev E, Single Channel, SCSI Id=7, 4 SCBs >>ahc0: target 0 Tagged Queuing Device >>(ahc0:0:0): "CONNER CFP1060S 1.05GB 2135" type 0 fixed SCSI 2 >>sd0(ahc0:0:0): Direct-Access 1013MB (2074880 512 byte sectors) > >Do you have the required firmware upgrade for this drive that makes tagged >queuing work correctly with it? The driver is a bit faster then it was >before and I don't know exactly what it was about this drive that makes it >go out to lunch, but it wouldn't surprise me if getting transactions too >quickly caused you problems. I do not know where you can get the firmware >upgrade from. I tried www.conner.com, but Seagate has that now... Actually, Justin, these results look just like the errors which I got when you first integrated the SCSI changes into -current tree and I rebuilt for my neptune motherboard. Perhaps it is the problem with mem mapped io? I'd put OPTIONS AHC_FORCE_PIO into the configuration and rebuild. -Ken --- Ken Lam lam@awod.com Integrated Technical Systems Systems, Networks, and Internet Solutions -- Defining Technology Today "'Plug and Play' was only applicable to the original ATARI(tm)" From owner-freebsd-scsi Sat Nov 9 18:47:37 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA06084 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 18:47:37 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA06061; Sat, 9 Nov 1996 18:47:32 -0800 (PST) Message-Id: <199611100247.SAA06061@freefall.freebsd.org> To: Ken Lam cc: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) , current@FreeBSD.org (FreeBSD-current), scsi@FreeBSD.org Subject: Re: SCSI system becomes broken in -current? In-reply-to: Your message of "Sat, 09 Nov 1996 21:42:05 EST." <3.0.32.19961109214202.00d8cef8@awod.com> Date: Sat, 09 Nov 1996 18:47:32 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Actually, Justin, these results look just like the errors which I got when >you first integrated the SCSI changes into -current tree and I rebuilt for >my neptune motherboard. Perhaps it is the problem with mem mapped io? > >I'd put OPTIONS AHC_FORCE_PIO into the configuration and rebuild. The 284x can only do PIO since it is a VL controller so the AHC_FORCE_PIO option doesn't affect it. >-Ken >--- >Ken Lam lam@awod.com >Integrated Technical Systems >Systems, Networks, and Internet Solutions -- Defining Technology Today > "'Plug and Play' was only applicable to the original ATARI(tm)" -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Sat Nov 9 18:57:08 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA06546 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 18:57:08 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA06540; Sat, 9 Nov 1996 18:57:05 -0800 (PST) Received: by sovcom.kiae.su id AA23829 (5.65.kiae-1 ); Sun, 10 Nov 1996 05:52:36 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sun, 10 Nov 96 05:52:36 +0300 Received: (from ache@localhost) by nagual.ru (8.8.2/8.8.2) id FAA00516; Sun, 10 Nov 1996 05:50:22 +0300 (MSK) Message-Id: <199611100250.FAA00516@nagual.ru> Subject: Re: SCSI system becomes broken in -current? In-Reply-To: <199611100215.SAA04532@freefall.freebsd.org> from "Justin T. Gibbs" at "Nov 9, 96 06:15:43 pm" To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Sun, 10 Nov 1996 05:50:22 +0300 (MSK) Cc: current@freebsd.org, scsi@freebsd.org From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >I have > >ahc0: at 0x1c00-0x1cff irq 11 on eisa0 slot 1 > >ahc0: aic7770 >= Rev E, Single Channel, SCSI Id=7, 4 SCBs > >ahc0: target 0 Tagged Queuing Device > >(ahc0:0:0): "CONNER CFP1060S 1.05GB 2135" type 0 fixed SCSI 2 > >sd0(ahc0:0:0): Direct-Access 1013MB (2074880 512 byte sectors) > > Do you have the required firmware upgrade for this drive that makes tagged > queuing work correctly with it? The driver is a bit faster then it was > before and I don't know exactly what it was about this drive that makes it > go out to lunch, but it wouldn't surprise me if getting transactions too > quickly caused you problems. I do not know where you can get the firmware > upgrade from. I tried www.conner.com, but Seagate has that now... Tagged queuing always work with it before recent days. I don't know about any firmware upgrade needed for this drive. BTW, it is almost impossible to get firmware upgrade in Russia or snail mail will costs so much money as compared to new device price. How do you know that firmware upgrade needed for this drive? Could you please resend me your sources? Needless to say that it works OK under Win95. I mention this fact because we need to put some warning about firmware upgrade needed for this drive, or we'll have many users complaints, this model is very popular at least in Russia. Could you please add device flags to turn tagged queuing on per-drive basis instead on for whole controller? My second drive is new IBM disk which works well with tagged queueing and I not want to turn it off for this drive too. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-scsi Sat Nov 9 19:04:30 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA07085 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 19:04:30 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA07061; Sat, 9 Nov 1996 19:04:22 -0800 (PST) Message-Id: <199611100304.TAA07061@freefall.freebsd.org> To: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) cc: current@freebsd.org, scsi@freebsd.org Subject: Re: SCSI system becomes broken in -current? In-reply-to: Your message of "Sun, 10 Nov 1996 05:50:22 +0300." <199611100250.FAA00516@nagual.ru> Date: Sat, 09 Nov 1996 19:04:22 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Tagged queuing always work with it before recent days. I don't know about >any firmware upgrade needed for this drive. BTW, it is almost impossible >to get firmware upgrade in Russia or snail mail will costs so much money as >compared to new device price. >How do you know that firmware upgrade needed for this drive? >Could you please resend me your sources? Drive firmware upgrades are usually ftp-able and are downloaded to the drive on the user's system. As for my sources, Gary Palmer mentioned some time ago that his 1060 would not work with tagged queueing and there is an entry in one of the Linux hardware FAQs about this drive. >Needless to say that it works OK under Win95. They probably have a quirk entry for it. Either that, or there is a new bug in the driver. The changes I made shouldn't have effected tagged queueing, so the bug should be reproducible with tagged queueing disabled. >I mention this fact because we need to put some warning about >firmware upgrade needed for this drive, or we'll have many users >complaints, this model is very popular at least in Russia. Sure, sure. >Could you please add device flags to turn tagged queuing on per-drive basis >instead on for whole controller? My second drive is new IBM disk which >works well with tagged queueing and I not want to turn it off for this drive >too. Don't you read your commit mail? I added this feature to the new SCSI branch code last weekend. >-- >Andrey A. Chernov > >http://www.nagual.ru/~ache/ -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Sat Nov 9 20:32:06 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA12066 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 20:32:06 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA12059; Sat, 9 Nov 1996 20:32:02 -0800 (PST) Received: by sovcom.kiae.su id AA15873 (5.65.kiae-1 ); Sun, 10 Nov 1996 07:17:49 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sun, 10 Nov 96 07:17:49 +0300 Received: (from ache@localhost) by nagual.ru (8.8.2/8.8.2) id HAA00208; Sun, 10 Nov 1996 07:16:41 +0300 (MSK) Message-Id: <199611100416.HAA00208@nagual.ru> Subject: Re: SCSI system becomes broken in -current? In-Reply-To: <199611100304.TAA07061@freefall.freebsd.org> from "Justin T. Gibbs" at "Nov 9, 96 07:04:22 pm" To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Sun, 10 Nov 1996 07:16:40 +0300 (MSK) Cc: current@freebsd.org, scsi@freebsd.org From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Tagged queuing always work with it before recent days. I don't know about > >any firmware upgrade needed for this drive. BTW, it is almost impossible > >to get firmware upgrade in Russia or snail mail will costs so much money as > >compared to new device price. > >How do you know that firmware upgrade needed for this drive? > >Could you please resend me your sources? > > Drive firmware upgrades are usually ftp-able and are downloaded to the > drive on the user's system. As for my sources, Gary Palmer mentioned some > time ago that his 1060 would not work with tagged queueing and there is an > entry in one of the Linux hardware FAQs about this drive. What I find in Linux FAQ: ---------------------------------------------------------------------------------------------- Some Conner CFP1060S drives may have problems with Linux and ext2fs. The symptoms are inode errors during e2fsck and corrupt file systems. Conner has released a firmware upgrade to fix this problem, contact Conner at 1-800-4CONNER (US) or +44-1294-315333 (Europe). Have the microcode version (found on the drive label, 9WA1.6x) handy when you call. ---------------------------------------------------------------------------------------------- I have 9WA1.68 label, so it seems my drive is affected. BTW, I can't call any of this phones, International calls costs too much here. If you got this upgrade somehow, please don't forget me... > They probably have a quirk entry for it. Either that, or there is a new > bug in the driver. The changes I made shouldn't have effected tagged > queueing, so the bug should be reproducible with tagged queueing disabled. I turn tagged queue off about two hours ago and extensively test my drives under hard load. And still not have this bug, so it seems it _is_ tagged queue related. > >Could you please add device flags to turn tagged queuing on per-drive basis > >instead on for whole controller? My second drive is new IBM disk which > >works well with tagged queueing and I not want to turn it off for this drive > >too. > > Don't you read your commit mail? I added this feature to the new SCSI > branch code last weekend. Sorry, I not pay attention on SCSI branch, I track -current only. My home SCSI drives is valuable enough for me to run experimental code on them. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-scsi Sat Nov 9 21:09:26 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA14160 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 21:09:26 -0800 (PST) Received: from fareast.rosprint.ru (fareast.rosprint.ru [193.232.88.195]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA14126 for ; Sat, 9 Nov 1996 21:09:16 -0800 (PST) Received: from fareast.rosprint.ru (localhost.rosprint.ru [127.0.0.1]) by fareast.rosprint.ru (8.7.5/8.7.3) with SMTP id PAA12789 for ; Sun, 10 Nov 1996 15:07:38 +1000 (VSK) Message-ID: <3285631A.167EB0E7@fareast.rosprint.ru> Date: Sun, 10 Nov 1996 15:07:38 +1000 From: "Vladimir P. Frolov" X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: scsi@freebsd.org Subject: SCSI problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Every night (after several hours of inactivity ) there are some errors on my SCSI subsytem. environment: FreeBSD 2.1.5 IWIll P55TU with Adaptec 7880 (2940 UW) enable disconnection for HDD - no termination: Low-Off/ High-On IBM HDD: DFRSS2W (wide SCSI drive) connected to wide connector autostart - on D TI SY - on TERM PWR EN - on TOSHIBA SCSI-2 CD-ROM connected to 50pin connector terminated via pluged terminators syslog: ------- sd0(ahc0:0:0): timed out in command phase, SCSISIGI == 0x4 sd0(ahc0:0:0): asserted ATN - device reset in message buffer sd0(ahc0:0:0): timed out in dataout phase, SCSISIGI == 0x0 ahc0: Issued Channel A Bus Reset #1. 2 SCBs aborted sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 sd0(ahc0:0:0): Power on, reset, or bus device reset occurred , retries:3 swap_pager: I/O error - pagein failed; blkno 11152, size 8192, error 5 vm_fault: pager input (probably hardware) error, PID 92 failure sd0(ahcsd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:3 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:2 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:2 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:1 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:1 sd0(ahc0:0sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:4 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:3 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:2 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:1 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , FAILURE swap_pager: I/O error - pagein failed; blkno 11152, size 8192, error 5 vm_fault: pager input (probably hardware) error, PID 92 failure :0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , FAILURE sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , FAILURE sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:4 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:4 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:3 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:3 0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:4 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:4 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:30:0): Logical unit is in process of becoming ready , retries:4 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:3 From owner-freebsd-scsi Sat Nov 9 21:21:26 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA15283 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 21:21:26 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA15271; Sat, 9 Nov 1996 21:21:21 -0800 (PST) Message-Id: <199611100521.VAA15271@freefall.freebsd.org> To: "Vladimir P. Frolov" cc: scsi@freebsd.org Subject: Re: SCSI problem In-reply-to: Your message of "Sun, 10 Nov 1996 15:07:38 +1000." <3285631A.167EB0E7@fareast.rosprint.ru> Date: Sat, 09 Nov 1996 21:21:20 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Every night (after several hours of inactivity ) >there are some errors on my SCSI subsytem. > > >environment: > FreeBSD 2.1.5 > IWIll P55TU with Adaptec 7880 (2940 UW) > enable disconnection for HDD - no Why are you turning off disconnection??? That will kill your performance. >sd0(ahc0:0:0): timed out in command phase, SCSISIGI == 0x4 This is probably a termination problem. Search for STPWEN in i386/scsi/aic7xxx.c and remove the two occurances of this. The diff should look like what I include below. I have a solution for setting this dynamically that will be going into current tonight and into stable before the 2.1.6 release, but first let me know if this helps your problem. It may also be some other problem in the driver that has been fixed already, so if this doesn't work, I'll send you the new driver ported back to 2.1.5R. *************** *** 1761,1767 **** AHC_OUTB(ahc, SCSIID, ahc->our_id_b); scsi_conf = AHC_INB(ahc, SCSICONF + 1); AHC_OUTB(ahc, SXFRCTL1, (scsi_conf & (ENSPCHK|STIMESEL)) ! | ENSTIMER|ACTNEGEN|STPWEN); AHC_OUTB(ahc, SIMODE1, ENSELTIMO|ENSCSIRST|ENSCSIPERR); if (ahc->type & AHC_ULTRA) AHC_OUTB(ahc, SXFRCTL0, DFON|SPIOEN|ULTRAEN); --- 1761,1767 ---- AHC_OUTB(ahc, SCSIID, ahc->our_id_b); scsi_conf = AHC_INB(ahc, SCSICONF + 1); AHC_OUTB(ahc, SXFRCTL1, (scsi_conf & (ENSPCHK|STIMESEL)) ! | ENSTIMER|ACTNEGEN); AHC_OUTB(ahc, SIMODE1, ENSELTIMO|ENSCSIRST|ENSCSIPERR); if (ahc->type & AHC_ULTRA) AHC_OUTB(ahc, SXFRCTL0, DFON|SPIOEN|ULTRAEN); *************** *** 1788,1794 **** AHC_OUTB(ahc, SCSIID, ahc->our_id); scsi_conf = AHC_INB(ahc, SCSICONF); AHC_OUTB(ahc, SXFRCTL1, (scsi_conf & (ENSPCHK|STIMESEL)) ! | ENSTIMER|ACTNEGEN|STPWEN); AHC_OUTB(ahc, SIMODE1, ENSELTIMO|ENSCSIRST|ENSCSIPERR); if (ahc->type & AHC_ULTRA) AHC_OUTB(ahc, SXFRCTL0, DFON|SPIOEN|ULTRAEN); --- 1788,1794 ---- AHC_OUTB(ahc, SCSIID, ahc->our_id); scsi_conf = AHC_INB(ahc, SCSICONF); AHC_OUTB(ahc, SXFRCTL1, (scsi_conf & (ENSPCHK|STIMESEL)) ! | ENSTIMER|ACTNEGEN); AHC_OUTB(ahc, SIMODE1, ENSELTIMO|ENSCSIRST|ENSCSIPERR); if (ahc->type & AHC_ULTRA) AHC_OUTB(ahc, SXFRCTL0, DFON|SPIOEN|ULTRAEN); -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Sat Nov 9 22:28:25 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA18188 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 22:28:25 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA18181 for ; Sat, 9 Nov 1996 22:28:20 -0800 (PST) Received: by sovcom.kiae.su id AA20209 (5.65.kiae-1 ); Sun, 10 Nov 1996 09:24:57 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sun, 10 Nov 96 09:24:57 +0300 Received: (from ache@localhost) by nagual.ru (8.8.2/8.8.2) id JAA00321; Sun, 10 Nov 1996 09:17:09 +0300 (MSK) Message-Id: <199611100617.JAA00321@nagual.ru> Subject: Re: SCSI system becomes broken in -current? In-Reply-To: <199611100501.VAA13610@freefall.freebsd.org> from "Justin T. Gibbs" at "Nov 9, 96 09:01:20 pm" To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Sun, 10 Nov 1996 09:17:08 +0300 (MSK) Cc: scsi@freebsd.org From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >I turn tagged queue off about two hours ago and extensively test > >my drives under hard load. And still not have this bug, so it seems > >it _is_ tagged queue related. I have one good news, Tagged Queueing WORK after firmware upgrade!!! BTW, SCB Paging still not work for two devices and cause serious inode damages as before. It work for any of device alone. > I wasn't expecting you to run it yet, just pointing out that I had the 1060 > in mind when I added generic tagged queueing support to the SCSI system. > As for stability, the aic7xxx cards have been the only ones tested heavily > with the new code. 8-) If you can send me the inquiry data again for your > drive, I can probably combine that with the info in the Linux FAQ entry to > only penalize the drives with that version of the firmware. Before upgrade I have (ahc0:0:0): "CONNER CFP1060S 1.05GB 2135" type 0 fixed SCSI 2 and after upgrade I got (ahc0:0:0): "CONNER CFP1060S 1.05GB 213C" type 0 fixed SCSI 2 As you can notice, they change 2135->213C, so it seems any CONNER < 213C can be treated as "known rogue" with proper kernel warning about its upgrade. As I already say, it will be nice to put this firmware upgrade somewhere on FreeBSD ftp with proper link from the hardware FAQ to eliminate possible problems... -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-scsi Sat Nov 9 22:37:13 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA18428 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 22:37:13 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA18418; Sat, 9 Nov 1996 22:37:10 -0800 (PST) Message-Id: <199611100637.WAA18418@freefall.freebsd.org> To: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) cc: scsi@freebsd.org Subject: Re: SCSI system becomes broken in -current? In-reply-to: Your message of "Sun, 10 Nov 1996 09:17:08 +0300." <199611100617.JAA00321@nagual.ru> Date: Sat, 09 Nov 1996 22:37:10 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I have one good news, Tagged Queueing WORK after firmware upgrade!!! > >BTW, SCB Paging still not work for two devices and cause >serious inode damages as before. It work for any of device alone. Hmmm. Jake Hamby has your same card and uses SCB paging with three tagged queueing devices at once. I also use SCB paging here, although with a 2940, and two devices each supporting 15 tags. I know that I have had more than 16 transactions active at a time since a simple sync will make this happen. I'll try to simulate your card by telling the driver I only have 4 SCBs, but I don't expect to find anything. Were there any aic7xxx driver messages on your console that indicated there was a problem? >-- >Andrey A. Chernov > >http://www.nagual.ru/~ache/ -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Sat Nov 9 23:04:04 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA19298 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 23:04:04 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA19261; Sat, 9 Nov 1996 23:03:55 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <19402(3)>; Sat, 9 Nov 1996 23:03:20 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177557>; Sat, 9 Nov 1996 23:03:10 -0800 To: "Justin T. Gibbs" cc: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) , current@freebsd.org (FreeBSD-current), scsi@freebsd.org Subject: Re: SCSI system becomes broken in -current? In-reply-to: Your message of "Sat, 09 Nov 96 18:15:43 PST." <199611100215.SAA04532@freefall.freebsd.org> Date: Sat, 9 Nov 1996 23:03:01 PST From: Bill Fenner Message-Id: <96Nov9.230310pst.177557@crevenia.parc.xerox.com> Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199611100215.SAA04532@freefall.freebsd.org> you write: >I tried www.conner.com, but Seagate has that now... Seagate bought Conner earlier this year. They have all the conner-related stuff mixed in on their web and ftp site. (e.g. look through the drive model numbers and you will find the CFP1080S, etc.) Bill From owner-freebsd-scsi Sat Nov 9 23:46:32 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA21474 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 23:46:32 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA21467; Sat, 9 Nov 1996 23:46:28 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.6.12/8.6.12) with SMTP id XAA18443; Sat, 9 Nov 1996 23:46:27 -0800 Date: Sat, 9 Nov 1996 23:46:27 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org, scsi@freebsd.org Subject: Anybody compiling -current with AHC_DEBUG? 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 Fails miserably for me on kernel supped 11/8, with undefined structure stuff. cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Winline -Wpointer-arith -nostdinc -I- -I. -I../.. -I../../../include -DAHC_DEBUG -DCOMPAT_43 -DNFS -DFFS -DINET -DKERNEL ../../i386/scsi/aic7xxx.c ../../i386/scsi/aic7xxx.c: In function `ahc_print_scb': ../../i386/scsi/aic7xxx.c:318: structure has no member named `control' ../../i386/scsi/aic7xxx.c:319: structure has no member named `tcl' ../../i386/scsi/aic7xxx.c:320: structure has no member named `cmdlen' ../../i386/scsi/aic7xxx.c:321: structure has no member named `cmdpointer' ../../i386/scsi/aic7xxx.c:323: structure has no member named `datalen' ../../i386/scsi/aic7xxx.c:324: structure has no member named `data' ../../i386/scsi/aic7xxx.c:325: structure has no member named `SG_segment_count' ../../i386/scsi/aic7xxx.c:326: structure has no member named `SG_list_pointer' ../../i386/scsi/aic7xxx.c: In function `ahc_scsi_cmd': ../../i386/scsi/aic7xxx.c:2187: `DEBUGTARGET' undeclared (first use this function) ../../i386/scsi/aic7xxx.c:2187: (Each undeclared identifier is reported only once ../../i386/scsi/aic7xxx.c:2187: for each function it appears in.) *** Error code 1 From owner-freebsd-scsi Sat Nov 9 23:50:39 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA21758 for freebsd-scsi-outgoing; Sat, 9 Nov 1996 23:50:39 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA21752; Sat, 9 Nov 1996 23:50:37 -0800 (PST) Message-Id: <199611100750.XAA21752@freefall.freebsd.org> To: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) cc: scsi@freebsd.org Subject: Re: SCSI system becomes broken in -current? In-reply-to: Your message of "Sat, 09 Nov 1996 22:37:10 PST." <199611100637.WAA18418@freefall.freebsd.org> Date: Sat, 09 Nov 1996 23:50:37 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I take this back. I was just able to reproduce this. I think I even know what the problem is. Stay tuned... >Hmmm. Jake Hamby has your same card and uses SCB paging with three tagged >queueing devices at once. I also use SCB paging here, although with a >2940, and two devices each supporting 15 tags. I know that I have had more >than 16 transactions active at a time since a simple sync will make this >happen. I'll try to simulate your card by telling the driver I only have 4 >SCBs, but I don't expect to find anything. Were there any aic7xxx driver >messages on your console that indicated there was a problem? -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================