From owner-freebsd-scsi Sun Sep 20 04:17:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06583 for freebsd-scsi-outgoing; Sun, 20 Sep 1998 04:17:44 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from asterix.webaffairs.net (port187.bonn.ndh.net [195.94.93.187]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06411 for ; Sun, 20 Sep 1998 04:16:48 -0700 (PDT) (envelope-from stefhe@gmx.net) Received: from obelix (obelix.webaffairs.net [192.168.10.3]) by asterix.webaffairs.net (8.8.8/8.8.8) with SMTP id MAA05748 for ; Sun, 20 Sep 1998 12:52:25 +0200 (CEST) (envelope-from stefhe@gmx.net) From: "Stefan Herrmann" To: Subject: Spin down SCSI disc Date: Sun, 20 Sep 1998 12:47:26 +0200 Message-ID: <000001bde484$0e71d8c0$030aa8c0@obelix.webaffairs.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <000401bde3c7$62a54fc0$030aa8c0@obelix.webaffairs.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, sorry, my first email had a foreign subject. I'd like to spin down a fast but noicy scsi disk, which is built into my pc. When I need it, it should spin up automatically. Is that possible (I think yes ;-) and what is the scsi command (under FreeBSD-2.2.7) ? A hint to an URL would help me already. Ciao Stefan -- --- Communications powered by FreeBSD --- Stefan Herrmann Löwenburgstr. 81 D-53229 Bonn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 20 10:16:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27314 for freebsd-scsi-outgoing; Sun, 20 Sep 1998 10:16:29 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27297 for ; Sun, 20 Sep 1998 10:16:21 -0700 (PDT) (envelope-from son@cezanne.prism.uvsq.fr) Received: from cezanne.prism.uvsq.fr (rtc104.reseau.uvsq.fr [193.51.24.20]) by soleil.uvsq.fr (8.9.1/jtpda-5.3.1) with ESMTP id TAA00549 ; Sun, 20 Sep 1998 19:15:47 +0200 (METDST) Received: (from son@localhost) by cezanne.prism.uvsq.fr (8.9.1/8.8.5) id TAA04482; Sun, 20 Sep 1998 19:21:26 GMT Message-ID: <19980920192126.51870@breizh.prism.uvsq.fr> Date: Sun, 20 Sep 1998 19:21:26 +0000 From: Nicolas Souchu To: Eivind Eklund Cc: "Kenneth D. Merry" , scsi@FreeBSD.ORG Subject: Re: Fixing LINT References: <19980918184204.00622@follo.net> <199809181707.LAA10835@panzer.plutotech.com> <19980918194533.52865@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <19980918194533.52865@follo.net>; from Eivind Eklund on Fri, Sep 18, 1998 at 07:45:33PM +0200 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Sep 18, 1998 at 07:45:33PM +0200, Eivind Eklund wrote: > >> > @@ -1558,7 +1558,7 @@ >> > # ppc ISA-bus parallel port interfaces. >> > # >> > controller ppbus0 >> > -controller vpo0 at ppbus? >> > +#!CAM# controller vpo0 at ppbus? >> >> I believe this one will be brought back shortly. > >Great! Still, it block LINT from compiling/linking at the moment. >(It is unfortunate that the CAM team didn't use it as resource during >development, but these things happen - let us now get it fixed :-) > >Eivind. > It is, with ZIP+ support added. Nicolas. -- Nicolas.Souchu@prism.uvsq.fr FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 20 14:45:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13965 for freebsd-scsi-outgoing; Sun, 20 Sep 1998 14:45:29 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13947 for ; Sun, 20 Sep 1998 14:45:26 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA07860 for freebsd-scsi@FreeBSD.ORG; Sun, 20 Sep 1998 23:44:49 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id D48941513; Sun, 20 Sep 1998 23:08:25 +0200 (CEST) Date: Sun, 20 Sep 1998 23:08:25 +0200 From: Ollivier Robert To: "FreeBSD SCSI Users' list" Subject: CAM & ncr driver Message-ID: <19980920230825.A10113@keltia.freenix.fr> Mail-Followup-To: FreeBSD SCSI Users' list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4654 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I finally converted by system to CAM (I have one SC-875 and one SC-200). It works w/o any problem... (older snapshots used to misbehave with my SC-200 card). Thanks Justin and Ken ! Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-BETA #0: Sat Sep 19 23:38:25 CEST 1998 roberto@keltia.freenix.fr:/src/src/sys/compile/KELTIA_CAM Timecounter "i8254" frequency 1193182 Hz cost 2399 ns Timecounter "TSC" frequency 200465821 Hz cost 117 ns CPU: AMD-K6tm w/ multimedia extensions (200.47-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping=2 Features=0x8001bf real memory = 134217728 (131072K bytes) avail memory = 128217088 (125212K bytes) Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 vga0: rev 0x01 int a irq 15 on pci0.9.0 ncr0: rev 0x03 int a irq 9 on pci0.11.0 ncr1: rev 0x12 int a irq 11 on pci0.12.0 [...] sa1 at ncr0 bus 0 target 4 lun 0 sa1: Removable Sequential Access SCSI2 device sa1: 3.300MB/s transfers sa0 at ncr1 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 5.0MB/s transfers (5.0MHz, offset 8) da12 at ncr1 bus 0 target 2 lun 0 da12: Fixed Direct Access SCSI2 device da12: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da12: 1030MB (2110812 512 byte sectors: 255H 63S/T 131C) cd1 at ncr1 bus 0 target 3 lun 0 cd1: Removable CD-ROM SCSI2 device cd1: 10.0MB/s transfers (10.0MHz, offset 8) cd1: cd present [6216 x 2048 byte records] da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI2 device da2: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-BETA #0: Sat Sep 19 23:38:25 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 21 11:47:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04491 for freebsd-scsi-outgoing; Mon, 21 Sep 1998 11:47:30 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04388 for ; Mon, 21 Sep 1998 11:47:08 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id UAA00768; Mon, 21 Sep 1998 20:46:16 +0200 (MEST) (envelope-from kuku) Date: Mon, 21 Sep 1998 20:46:16 +0200 (MEST) From: Christoph Kukulies Message-Id: <199809211846.UAA00768@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.cdrom.com, freebsd-scsi@FreeBSD.ORG Subject: ncr - new log messages appearing Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just FYI, don't know whether I should bother but since the recent upgrade to -current (aout) I'm seeing the following log messages: Sep 21 20:35:58 blues /kernel: (da0:ncr0:0:0:0): tagged openings now 15 (Stefan?) -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de Latest feature of Visual C++ 6.0: 'Command-line builds' - msdev crc.dsw /MAKE "WinCRC - Win32 Debug" /Rebuild /OUT wincrc.log Taken from: MSJ Oct 98, p. 19 -- :-O To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 21 12:04:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09200 for freebsd-scsi-outgoing; Mon, 21 Sep 1998 12:04:24 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09087 for ; Mon, 21 Sep 1998 12:03:58 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA08416; Mon, 21 Sep 1998 13:02:43 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809211902.NAA08416@panzer.plutotech.com> Subject: Re: ncr - new log messages appearing In-Reply-To: <199809211846.UAA00768@gilberto.physik.RWTH-Aachen.DE> from Christoph Kukulies at "Sep 21, 98 08:46:16 pm" To: kuku@gilberto.physik.RWTH-Aachen.DE (Christoph Kukulies) Date: Mon, 21 Sep 1998 13:02:43 -0600 (MDT) Cc: freebsd-current@freefall.cdrom.com, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christoph Kukulies wrote... > > Just FYI, don't know whether I should bother but > since the recent upgrade to -current (aout) I'm seeing > the following log messages: > > Sep 21 20:35:58 blues /kernel: (da0:ncr0:0:0:0): tagged openings now 15 > > (Stefan?) That's quite normal. It means your disk only has space for 15 commands at a time. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 21 12:15:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12400 for freebsd-scsi-outgoing; Mon, 21 Sep 1998 12:15:27 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12372 for ; Mon, 21 Sep 1998 12:15:13 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id NAA02743; Mon, 21 Sep 1998 13:07:57 -0600 (MDT) Date: Mon, 21 Sep 1998 13:07:57 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809211907.NAA02743@narnia.plutotech.com> To: Christoph Kukulies cc: scsi@FreeBSD.ORG Subject: Re: ncr - new log messages appearing Newsgroups: pluto.freebsd.scsi In-Reply-To: <199809211846.UAA00768@gilberto.physik.RWTH-Aachen.DE> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199809211846.UAA00768@gilberto.physik.RWTH-Aachen.DE> you wrote: > > Just FYI, don't know whether I should bother but > since the recent upgrade to -current (aout) I'm seeing > the following log messages: > > Sep 21 20:35:58 blues /kernel: (da0:ncr0:0:0:0): tagged openings now 15 It's just telling you that the system determined that your drive can only handle 15 transactions at a time and has lowered the maximum allowed for that device appropriately. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 21 12:31:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16555 for freebsd-scsi-outgoing; Mon, 21 Sep 1998 12:31:11 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16524 for ; Mon, 21 Sep 1998 12:30:52 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id OAA28394; Mon, 21 Sep 1998 14:28:49 -0500 (CDT) Date: Mon, 21 Sep 1998 14:28:49 -0500 From: Dan Nelson To: Christoph Kukulies , freebsd-current@freefall.cdrom.com, freebsd-scsi@FreeBSD.ORG Subject: Re: ncr - new log messages appearing Message-ID: <19980921142849.A28314@emsphone.com> References: <199809211846.UAA00768@gilberto.physik.RWTH-Aachen.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: <199809211846.UAA00768@gilberto.physik.RWTH-Aachen.DE>; from "Christoph Kukulies" on Mon Sep 21 20:46:16 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In the last episode (Sep 21), Christoph Kukulies said: > > Just FYI, don't know whether I should bother but since the recent > upgrade to -current (aout) I'm seeing the following log messages: > > Sep 21 20:35:58 blues /kernel: (da0:ncr0:0:0:0): tagged openings now 15 That just means your drive can't handle more than 15 tagged commands at once. CAM's max is 64 (is there any way to raise this?), so the first time your system hits the disk heavily, your drive will complain about the number of tags it can't handle, and the kernel message will pop up. There's no way to query the drive for this information (as far as I know), so the system basically tries to use as many tagged commands as possible until the drive complains. Some of Netware's SCSI drivers print the same messages. It's actually nice to see the message; then I know what drives not to buy next time :) -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 21 13:22:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26158 for freebsd-scsi-outgoing; Mon, 21 Sep 1998 13:22:29 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26149 for ; Mon, 21 Sep 1998 13:22:24 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id OAA08872; Mon, 21 Sep 1998 14:20:59 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809212020.OAA08872@panzer.plutotech.com> Subject: Re: ncr - new log messages appearing In-Reply-To: <19980921142849.A28314@emsphone.com> from Dan Nelson at "Sep 21, 98 02:28:49 pm" To: dnelson@emsphone.com (Dan Nelson) Date: Mon, 21 Sep 1998 14:20:59 -0600 (MDT) Cc: kuku@gilberto.physik.RWTH-Aachen.DE, freebsd-current@freefall.cdrom.com, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dan Nelson wrote... > In the last episode (Sep 21), Christoph Kukulies said: > > > > Just FYI, don't know whether I should bother but since the recent > > upgrade to -current (aout) I'm seeing the following log messages: > > > > Sep 21 20:35:58 blues /kernel: (da0:ncr0:0:0:0): tagged openings now 15 > > That just means your drive can't handle more than 15 tagged commands at > once. CAM's max is 64 (is there any way to raise this?), so the first > time your system hits the disk heavily, your drive will complain about > the number of tags it can't handle, and the kernel message will pop up. You can adjust the maximum by adjusting the default quirk entry in cam_xpt.c or by putting in a specific quirk entry for your device that sets the limit higher. Most drives don't have any more than 64 tags. I think there are some external RAID controllers that may have more. > There's no way to query the drive for this information (as far as I > know), so the system basically tries to use as many tagged commands as > possible until the drive complains. Although some drives, like the Atlas II, will keep returning queue full until we've reduced the number of tags to 0. That's why we've got quirk entries that set the lower limit for those drives to 24. > Some of Netware's SCSI drivers print the same messages. It's actually > nice to see the message; then I know what drives not to buy next time > :) Yep. Many (most?) of the better Seagates handle 63 tags. My IBM Ultrastar 9ZX has 64. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 21 19:46:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23461 for freebsd-scsi-outgoing; Mon, 21 Sep 1998 19:46:25 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from rmstar.campus.luth.se (rmstar.campus.luth.se [130.240.197.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23324 for ; Mon, 21 Sep 1998 19:45:29 -0700 (PDT) (envelope-from murduth@rmstar.campus.luth.se) Received: from rmstar.campus.luth.se (murduth@localhost [127.0.0.1]) by rmstar.campus.luth.se (8.9.1/8.9.1) with ESMTP id EAA00991 for ; Tue, 22 Sep 1998 04:44:49 +0200 (CEST) (envelope-from murduth@rmstar.campus.luth.se) Message-Id: <199809220244.EAA00991@rmstar.campus.luth.se> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@FreeBSD.ORG Subject: ncr + CAM still broken for me Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Sep 1998 04:44:49 +0200 From: Joakim Henriksson Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org CAM is still breaking down for me when i'm making world, during the installworld phase. I'm running with 1.130 of ncr.c . This is what i see in the logs: Sep 22 01:09:27 rmstar /kernel: (da1:ncr0:0:2:0): tagged openings now 28 Sep 22 01:09:28 rmstar /kernel: (da1:ncr0:0:2:0): tagged openings now 2 Sep 22 01:10:20 rmstar /kernel: swap_pager: indefinite wait buffer: device: 0x40 9, blkno: 296, size: 4096 Sep 22 01:10:29 rmstar /kernel: ncr0: queue empty. Sep 22 01:10:40 rmstar last message repeated 11 times Sep 22 01:10:40 rmstar /kernel: swap_pager: indefinite wait buffer: device: 0x40 9, blkno: 296, size: 4096 Sep 22 01:10:41 rmstar /kernel: ncr0: queue empty. Sep 22 01:11:00 rmstar last message repeated 19 times Sep 22 01:11:00 rmstar /kernel: swap_pager: indefinite wait buffer: device: 0x40 9, blkno: 296, size: 4096 And the devices: sa0: Removable Sequential Access SCSI2 device sa0: 4.32MB/s transfers (4.32MHz, offset 8) changing root device to wd0s3a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da0: 1034MB (2118144 512 byte sectors: 255H 63S/T 131C) da2 at ncr0 bus 0 target 3 lun 0 da2: Fixed Direct Access SCSI2 device da2: 10.0MB/s transfers (10.0MHz, offset 8) da2: 698MB (1431518 512 byte sectors: 64H 32S/T 698C) da1 at ncr0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da1: 2048MB (4194304 512 byte sectors: 255H 63S/T 261C) cd0 at ncr0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 10.0MB/s transfers (10.0MHz, offset 8) cd0: cd present [328498 x 2048 byte records] -- regards/ Joakim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 21 20:16:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29733 for freebsd-scsi-outgoing; Mon, 21 Sep 1998 20:16:45 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA29669 for ; Mon, 21 Sep 1998 20:16:14 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA32296 (5.67b/IDA-1.5); Tue, 22 Sep 1998 05:00:01 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id XAA02617; Mon, 21 Sep 1998 23:54:49 +0200 (CEST) From: Wilko Bulte Message-Id: <199809212154.XAA02617@yedi.iaf.nl> Subject: Re: ncr - new log messages appearing In-Reply-To: <199809212020.OAA08872@panzer.plutotech.com> from "Kenneth D. Merry" at "Sep 21, 98 02:20:59 pm" To: ken@plutotech.com (Kenneth D. Merry) Date: Mon, 21 Sep 1998 23:54:49 +0200 (CEST) Cc: dnelson@emsphone.com, kuku@gilberto.physik.RWTH-Aachen.DE, freebsd-current@freefall.cdrom.com, freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Kenneth D. Merry wrote... > > That just means your drive can't handle more than 15 tagged commands at > > once. CAM's max is 64 (is there any way to raise this?), so the first > > time your system hits the disk heavily, your drive will complain about > > the number of tags it can't handle, and the kernel message will pop up. > > You can adjust the maximum by adjusting the default quirk entry in > cam_xpt.c or by putting in a specific quirk entry for your device that sets > the limit higher. Most drives don't have any more than 64 tags. I think > there are some external RAID controllers that may have more. Quite true. For example the Digital HSZ40 controllers have a pool of 300 tags, that are shared by all LUNs that are configured on the array. There is one thing that must be kept in mind for those RAID boxes: you might encounter a QUEUE FULL even when that particular LUN had no I/O outstanding. Other I/O on different LUNs in that case has used up all tags from the pool. I've seen drivers choke on this before ;-) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 21 21:31:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11418 for freebsd-scsi-outgoing; Mon, 21 Sep 1998 21:31:08 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11411 for ; Mon, 21 Sep 1998 21:31:07 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id WAA06949; Mon, 21 Sep 1998 22:24:08 -0600 (MDT) Date: Mon, 21 Sep 1998 22:24:08 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809220424.WAA06949@narnia.plutotech.com> To: Wilko Bulte cc: scsi@FreeBSD.ORG Subject: Re: ncr - new log messages appearing Newsgroups: pluto.freebsd.scsi In-Reply-To: <199809212154.XAA02617@yedi.iaf.nl> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199809212154.XAA02617@yedi.iaf.nl> you wrote: > There is one thing that must be kept in mind for those RAID boxes: you might > encounter a QUEUE FULL even when that particular LUN had no I/O outstanding. > Other I/O on different LUNs in that case has used up all tags from the pool. > > I've seen drivers choke on this before ;-) CAM treats this as if we saw BUSY instead of QUEUE FULL. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 21 21:46:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14194 for freebsd-scsi-outgoing; Mon, 21 Sep 1998 21:46:55 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14185 for ; Mon, 21 Sep 1998 21:46:45 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id WAA07048; Mon, 21 Sep 1998 22:39:45 -0600 (MDT) Date: Mon, 21 Sep 1998 22:39:45 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809220439.WAA07048@narnia.plutotech.com> To: Joakim Henriksson cc: scsi@FreeBSD.ORG Subject: Re: ncr + CAM still broken for me Newsgroups: pluto.freebsd.scsi In-Reply-To: <199809220244.EAA00991@rmstar.campus.luth.se> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199809220244.EAA00991@rmstar.campus.luth.se> you wrote: > CAM is still breaking down for me when i'm making world, during the > installworld phase. I'm running with 1.130 of ncr.c . This is what i see in > the logs: > > Sep 22 01:09:27 rmstar /kernel: (da1:ncr0:0:2:0): tagged openings now 28 > Sep 22 01:09:28 rmstar /kernel: (da1:ncr0:0:2:0): tagged openings now 2 Wow. This drive doesn't like tagged queuing.... We may have killed it by attempting to queue to many things. Have you looked to see if Quantum has any new firmware for it? We may want to limit the amount of tagged I/O performed to this class of drive via a quirk entry. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 21 23:08:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27175 for freebsd-scsi-outgoing; Mon, 21 Sep 1998 23:08:34 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27151 for ; Mon, 21 Sep 1998 23:08:27 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.9.1/8.7.3) id IAA13194 for freebsd-scsi@freebsd.org; Tue, 22 Sep 1998 08:07:56 +0200 (CEST) From: Holm Tiffe Message-Id: <199809220607.IAA13194@magnet.geophysik.tu-freiberg.de> Subject: Quantum Viking-II and NCR, new firmware! To: freebsd-scsi@FreeBSD.ORG Date: Tue, 22 Sep 1998 08:07:56 +0200 (CEST) Reply-To: freebsd@magnet.geophysik.tu-freiberg.de X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, A friend of mine has several problems with the Quantum Viking-II and an 53C875 based controller (SC875). (well known here) I have looked at www.quantum.com --- nothing. But on ftp.quantum.com in /Firmware/Viking-II is a tool to download new firmware and firmware from August 18. Has anybody already tried to upgrade the drives ? Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 22 11:20:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26271 for freebsd-scsi-outgoing; Tue, 22 Sep 1998 11:20:16 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from jane.lfn.org (jobfair.nocitycouncil.com [209.16.92.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA26154 for ; Tue, 22 Sep 1998 11:20:01 -0700 (PDT) (envelope-from caj@lfn.org) Received: (qmail 20184 invoked by uid 100); 22 Sep 1998 18:19:28 -0000 Date: Tue, 22 Sep 1998 13:19:28 -0500 (CDT) From: Craig Johnston To: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: diamond fireport 20, ok? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can someone confirm this works well with FreeBSD? I've seen reports on the 40 but not the 20. Which symbios chip does the 20 use -- is it an 875 or an 860? Diamond doesn't supply this info in the specs on their website. (typical) -- Craig Johnston, caj@lfn.org abort(); /* live fast, die young and leave a good-looking core file */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 22 12:22:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09468 for freebsd-scsi-outgoing; Tue, 22 Sep 1998 12:22:24 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09391 for ; Tue, 22 Sep 1998 12:22:06 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1a/8.9.1) with ESMTP id VAA02679 for ; Tue, 22 Sep 1998 21:21:29 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1a/8.9.1) with ESMTP id VAA16250 for ; Tue, 22 Sep 1998 21:21:29 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id VAA18275 for ; Tue, 22 Sep 1998 21:21:30 +0200 (CEST) From: Andre Albsmeier Message-Id: <199809221921.VAA01081@internal> Subject: Re: Quantum Viking-II and NCR, new firmware! In-Reply-To: <199809220607.IAA13194@magnet.geophysik.tu-freiberg.de> from Holm Tiffe at "Sep 22, 98 08:07:56 am" To: freebsd@magnet.geophysik.tu-freiberg.de Date: Tue, 22 Sep 1998 21:21:26 +0200 (CEST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > > A friend of mine has several problems with the Quantum Viking-II > and an 53C875 based controller (SC875). (well known here) > I have looked at www.quantum.com --- nothing. > But on ftp.quantum.com in /Firmware/Viking-II is a tool to > download new firmware and firmware from August 18. Has anybody > already tried to upgrade the drives ? I have done it yesterday on a DLT 4700, on 9 Atlas II and on 3 Viking I (but no Viking II). Worked great, after getting help here from the list because I couldn't figure out which file to use for the Atlas II :-) -Andre P.S.: Anyone who wants to upgrade a Atlas II: use the QSHR_LDR3.EXE from the Atlas-II directory; not the QSHR_LDR.EXE in LYK8. I couldn't get the drive(s) back onto the bus by using QSHR_LDR.EXE (This doesn't appear to hurt, but takes quite long to comlete.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 22 15:33:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18274 for freebsd-scsi-outgoing; Tue, 22 Sep 1998 15:33:33 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18182 for ; Tue, 22 Sep 1998 15:32:55 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id AAA13007; Wed, 23 Sep 1998 00:32:18 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id AAA00381; Wed, 23 Sep 1998 00:32:18 +0200 (MET DST) Message-ID: <19980923003214.35208@follo.net> Date: Wed, 23 Sep 1998 00:32:14 +0200 From: Eivind Eklund To: scsi@FreeBSD.ORG Cc: shimon@simon-shapiro.org Subject: DPT boot Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just tried to boot my box with a CAMified kernel, and found that it wouldn't. Everything probed fine, but after the NPX message it just hung for a long while. After a number of minutes (more than 2, as that was what I tried first, but less than 17, which was when I got back to the box) it spit out a message (something like "CCB (0:0:0:0:0) Timed out" - I unfortunately didn't write it down). This is with the following DPT controller: dpt0: rev 0x02 int a irq 10 on pci0.11.0 dpt0: DPT type 3, model PM3224W firmware 07H1, Protocol 0 on port d810 with Write-Back cache. LED = 0000 0000 dpt0: Enabled Options: dpt0: waiting for scsi devices to settle scbus0 at dpt0 bus 0 ... and an Adaptec 2940: ahc0: rev 0x00 int a irq 9 on pci0.13.0 ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs ahc0: waiting for scsi devices to settle scbus1 at ahc0 bus 0 The CCB message was the only I got - no disk descriptions from either controller (though I don't know if I should expect them - this is my first CAM experiement). Any clues? Anything I should test? (I can hook up a pretty complete debugging environment here, including doing remote kernel debugging if necessary - at the moment I also have 'scratch' disks I can use for testing, though not having this controller operational means I my main workstation is not usable, so I'd prefer to avoid tests that take a long time). Oh, and while this was happening, the DPT kept a steady light #3 (as counted from the connector-less end of the DPT). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 22 19:31:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02054 for freebsd-scsi-outgoing; Tue, 22 Sep 1998 19:31:05 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA02007 for ; Tue, 22 Sep 1998 19:30:59 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 12363 invoked by uid 1000); 23 Sep 1998 03:06:48 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19980923003214.35208@follo.net> Date: Tue, 22 Sep 1998 23:06:48 -0400 (EDT) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Eivind Eklund Subject: RE: DPT boot Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Eivind Eklund, On 22-Sep-98 you wrote: > I just tried to boot my box with a CAMified kernel, and found that it > wouldn't. Everything probed fine, but after the NPX message it just > hung > for a long while. After a number of minutes (more than 2, as that was > what > I tried first, but less than 17, which was when I got back to the box) > it > spit out a message (something like "CCB (0:0:0:0:0) Timed out" - I > unfortunately didn't write it down). I get similar symptoms, but much shorter timeouts, like fraction of a second per CCB. Then I get the panic I reported. since there is no documentation for the driver layer, I can only guess at what I see; for each possible drive, there is a CCB. Probably to handle the Inquiry or some such. For non-existing drives, these indeed should timeout. > This is with the following DPT controller: > dpt0: rev 0x02 int a irq 10 on > pci0.11.0 > dpt0: DPT type 3, model PM3224W firmware 07H1, Protocol 0 > on port d810 with Write-Back cache. LED = 0000 0000 > dpt0: Enabled Options: > dpt0: waiting for scsi devices to settle > scbus0 at dpt0 bus 0 > ... and an Adaptec 2940: > ahc0: rev 0x00 int a irq 9 on > pci0.13.0 > ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs > ahc0: waiting for scsi devices to settle > scbus1 at ahc0 bus 0 > > The CCB message was the only I got - no disk descriptions from either > controller (though I don't know if I should expect them - this is my > first > CAM experiement). I would imagine these should come later, once the CCBs are answered. > Any clues? Anything I should test? (I can hook up a pretty complete > debugging environment here, including doing remote kernel debugging if > necessary - at the moment I also have 'scratch' disks I can use for > testing, > though not having this controller operational means I my main > workstation is > not usable, so I'd prefer to avoid tests that take a long time). I assume this controller works on the pre-CAM driver... :-) > Oh, and while this was happening, the DPT kept a steady light #3 (as > counted > from the connector-less end of the DPT). On a 3224 it is bus transfer from adapter, or adapter reset (depends on how you look at it, and assuming first LED is 1). If it is a transfer LED, then the DMA engine is stuck. If it is a reset, that means the controller was reset and never released. In either case I would suspect the initialization code does not work correctly. I have some work-work emergencies to handle right now, but will start debugging this driver any day soon. ``...And Carthage shall fall..'' - Cicero ``Documentation would have been nice'' - Simon Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 22 19:33:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02880 for freebsd-scsi-outgoing; Tue, 22 Sep 1998 19:33:28 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02841 for ; Tue, 22 Sep 1998 19:33:22 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id VAA12168 for ; Tue, 22 Sep 1998 21:55:11 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: scsi@FreeBSD.ORG From: "Gary Palmer" Subject: CDROM weirdness Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Sep 1998 21:55:10 -0400 Message-ID: <12164.906515710@gjp.erols.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've tried interpreting this, but I don't grok CDB tables so I'll leave it to the experts: found-> vendor=0x1077, dev=0x1020, revid=0x02 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=17 map[0]: type 4, range 32, base 00000000, size 8 map[1]: type 1, range 32, base 82221000, size 12 Qlogic ISP Driver, FreeBSD CAM Version 0.97, Core Version 1.3 isp0: rev 0x02 int a irq 17 on pci1.1.0 isp0: using Memory space register mapping isp0: Board Revision 1020A, loaded F/W Revision 7.55 isp0: Last F/W revision was 2.10 found-> vendor=0x1077, dev=0x1020, revid=0x02 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=18 map[0]: type 4, range 32, base 00010000, size 8 map[1]: type 1, range 32, base 82220000, size 12 isp1: rev 0x02 int a irq 18 on pci1.2.0 isp1: using Memory space register mapping isp1: Board Revision 1020A, loaded F/W Revision 7.55 isp0: driver initiated bus reset isp1: driver initiated bus reset (probe5:isp0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe5:isp0:0:5:0): ILLEGAL REQUEST asc:24,0 (probe5:isp0:0:5:0): Invalid field in CDB sks:c8,1 (cd0:isp0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:isp0:0:5:0): NOT READY asc:3a,0 (cd0:isp0:0:5:0): Medium not present cd0 at isp0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 10.0MB/s transfers (10.0MHz, offset 12) cd0: Attempt to query device size failed: NOT READY, Medium not present (I snipped the SCSI HD's out since they probed ok). Is this something else in need of a quirk? Or should I just stop booting -v? :) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 22 21:31:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27384 for freebsd-scsi-outgoing; Tue, 22 Sep 1998 21:31:01 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27359; Tue, 22 Sep 1998 21:30:45 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id WAA19437; Tue, 22 Sep 1998 22:30:41 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809230430.WAA19437@panzer.plutotech.com> Subject: Re: CDROM weirdness In-Reply-To: <12164.906515710@gjp.erols.com> from Gary Palmer at "Sep 22, 98 09:55:10 pm" To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Tue, 22 Sep 1998 22:30:41 -0600 (MDT) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gary Palmer wrote... > > I've tried interpreting this, but I don't grok CDB tables so I'll leave it to > the experts: I wouldn't call myself an expert, but I did write the CD driver (and some of the probe code). > found-> vendor=0x1077, dev=0x1020, revid=0x02 > class=01-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=17 > map[0]: type 4, range 32, base 00000000, size 8 > map[1]: type 1, range 32, base 82221000, size 12 > Qlogic ISP Driver, FreeBSD CAM Version 0.97, Core Version 1.3 > isp0: rev 0x02 int a irq 17 on pci1.1.0 > isp0: using Memory space register mapping > isp0: Board Revision 1020A, loaded F/W Revision 7.55 > isp0: Last F/W revision was 2.10 > found-> vendor=0x1077, dev=0x1020, revid=0x02 > class=01-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=18 > map[0]: type 4, range 32, base 00010000, size 8 > map[1]: type 1, range 32, base 82220000, size 12 > isp1: rev 0x02 int a irq 18 on pci1.2.0 > isp1: using Memory space register mapping > isp1: Board Revision 1020A, loaded F/W Revision 7.55 > > isp0: driver initiated bus reset > isp1: driver initiated bus reset > (probe5:isp0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 > (probe5:isp0:0:5:0): ILLEGAL REQUEST asc:24,0 > (probe5:isp0:0:5:0): Invalid field in CDB sks:c8,1 This is pretty standard. Your CDROM drive doesn't like serial number requests. Most CDROM drives don't. > (cd0:isp0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (cd0:isp0:0:5:0): NOT READY asc:3a,0 > (cd0:isp0:0:5:0): Medium not present All this means is that you don't have a CD in the drive. You shouldn't see that when you boot without -v. > cd0 at isp0 bus 0 target 5 lun 0 > cd0: Removable CD-ROM SCSI2 device > cd0: 10.0MB/s transfers (10.0MHz, offset 12) > cd0: Attempt to query device size failed: NOT READY, Medium not present That's the standard "compact" error message we print out when there's no media in the drive. For instance: cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 10.0MB/s transfers (10.0MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present > (I snipped the SCSI HD's out since they probed ok). > > Is this something else in need of a quirk? Or should I just stop booting -v? :) You should probably stop booting with -v. :) All of those things are normal. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 22 21:58:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01264 for freebsd-scsi-outgoing; Tue, 22 Sep 1998 21:58:13 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01221; Tue, 22 Sep 1998 21:57:54 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id WAA00662; Tue, 22 Sep 1998 22:51:21 -0600 (MDT) Date: Tue, 22 Sep 1998 22:51:21 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809230451.WAA00662@narnia.plutotech.com> To: "Gary Palmer" cc: scsi@FreeBSD.ORG Subject: Re: CDROM weirdness Newsgroups: pluto.freebsd.scsi In-Reply-To: <12164.906515710@gjp.erols.com> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <12164.906515710@gjp.erols.com> you wrote: > (probe5:isp0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 > (probe5:isp0:0:5:0): ILLEGAL REQUEST asc:24,0 > (probe5:isp0:0:5:0): Invalid field in CDB sks:c8,1 Device doesn't have a serial number. No big deal, we can live without it. This error will only show up with a boot -v. > (cd0:isp0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (cd0:isp0:0:5:0): NOT READY asc:3a,0 > (cd0:isp0:0:5:0): Medium not present No disc in the drive. No big deal, we can live without it. This error will only show up with a boot -v. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 22 22:17:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04261 for freebsd-scsi-outgoing; Tue, 22 Sep 1998 22:17:07 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04236 for ; Tue, 22 Sep 1998 22:16:54 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id XAA00733; Tue, 22 Sep 1998 23:10:20 -0600 (MDT) Date: Tue, 22 Sep 1998 23:10:20 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809230510.XAA00733@narnia.plutotech.com> To: shimon@simon-shapiro.org cc: scsi@FreeBSD.ORG Subject: Re: DPT boot In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > > Eivind Eklund, On 22-Sep-98 you wrote: >> I just tried to boot my box with a CAMified kernel, and found that it >> wouldn't. Everything probed fine, but after the NPX message it just >> hung >> for a long while. After a number of minutes (more than 2, as that was >> what >> I tried first, but less than 17, which was when I got back to the box) >> it >> spit out a message (something like "CCB (0:0:0:0:0) Timed out" - I >> unfortunately didn't write it down). Was Eivind's message originally on the SCSI list? This is the second time I've heard you reference messages that I haven't seen on the list. Strange. > I get similar symptoms, but much shorter timeouts, like fraction of a > second per CCB. Then I get the panic I reported. This is with the latest version of dpt.c in the tree? > since there is no > documentation for the driver layer, I can only guess at what I see; for > each possible drive, there is a CCB. Probably to handle the Inquiry or > some such. For non-existing drives, these indeed should timeout. For non-existing drives, the inquiry should not timeout. It should come back after a `selection timeout' (which is quite different than a command timeout) with a selection timeout error code. This, however, was not where the problem was. >> The CCB message was the only I got - no disk descriptions from either >> controller (though I don't know if I should expect them - this is my >> first CAM experiement). > > I would imagine these should come later, once the CCBs are answered. Yes. They come up after interrupt services are available and probing has been completed. >> Any clues? Anything I should test? (I can hook up a pretty complete >> debugging environment here, including doing remote kernel debugging if >> necessary - at the moment I also have 'scratch' disks I can use for >> testing, >> though not having this controller operational means I my main >> workstation is >> not usable, so I'd prefer to avoid tests that take a long time). > > I assume this controller works on the pre-CAM driver... :-) This problem has nothing to do with either DPT driver. It has to do with multi-lun probing and serial number inquiries. On my PM3224A card, it seems that RAID-1 DPT volumes will not tolerate inquiry requests to luns greater than 0. An inquiry request for a VPD page also hangs the controller. This was under firmware 7BG0. I need to get a 2Mb eeprom before I can test out newer firmware. Since the description of this problem matches my own experience, I can only guess that even the latest firmware still has this bug. I've added quirk entries to the generic SCSI layer to disable multi-lun probing and serial number requests to all DPT RAID volumes (although RAID-5 volumes did not seem to have this problem). If this is not sufficient to address your problem, please let me know. > ``...And Carthage shall fall..'' - Cicero > ``Documentation would have been nice'' - Simon This simply isn't fair Simon. I told you I couldn't provide CAM documentation because of my time constraints, so you asked me to port the DPT driver to CAM. If you are displeased with the results, you should talk to me about ways that this can be addressed instead of posting messages full of inuendo to a public list. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 22 23:53:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21302 for freebsd-scsi-outgoing; Tue, 22 Sep 1998 23:53:54 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21296 for ; Tue, 22 Sep 1998 23:53:52 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id CAA16469 for ; Wed, 23 Sep 1998 02:53:51 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: scsi@FreeBSD.ORG From: "Gary Palmer" Subject: Re: CDROM weirdness In-reply-to: Your message of "Tue, 22 Sep 1998 22:30:41 MDT." <199809230430.WAA19437@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Sep 1998 02:53:50 -0400 Message-ID: <16465.906533630@gjp.erols.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" wrote in message ID <199809230430.WAA19437@panzer.plutotech.com>: > You should probably stop booting with -v. :) All of those things are > normal. Okie. Just wanted to make sure. This came from my Alpha, and I'd never seen those messages in pre-CAM (that I remember), and I tend to boot -v so I can catch any kernel oddities.... thanks guys for cam ... its a treat :) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 23 04:15:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05475 for freebsd-scsi-outgoing; Wed, 23 Sep 1998 04:15:33 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA05288 for ; Wed, 23 Sep 1998 04:13:51 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id NAA23202; Wed, 23 Sep 1998 13:12:29 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id NAA02914; Wed, 23 Sep 1998 13:12:23 +0200 (MET DST) Message-ID: <19980923131222.21236@follo.net> Date: Wed, 23 Sep 1998 13:12:22 +0200 From: Eivind Eklund To: shimon@simon-shapiro.org Cc: scsi@FreeBSD.ORG Subject: Re: DPT boot References: <19980923003214.35208@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Simon Shapiro on Tue, Sep 22, 1998 at 11:06:48PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Sep 22, 1998 at 11:06:48PM -0400, Simon Shapiro wrote: > Eivind Eklund, On 22-Sep-98 you wrote: > > Any clues? Anything I should test? (I can hook up a pretty complete > > debugging environment here, including doing remote kernel debugging if > > necessary - at the moment I also have 'scratch' disks I can use for > > testing, though not having this controller operational means I my main > > workstation is not usable, so I'd prefer to avoid tests that take a > > long time). > > I assume this controller works on the pre-CAM driver... :-) Yes, perfectly. The only problem is that the DPT is attempting to outsmart the BIOS, but once it is in FreeBSD, everything works perfectly. > > Oh, and while this was happening, the DPT kept a steady light #3 (as > > counted from the connector-less end of the DPT). > > On a 3224 it is bus transfer from adapter, or adapter reset (depends on how > you look at it, and assuming first LED is 1). First LED is 1, and I counted from the end of the board that hasn't got a connector to the outside world (ie, not the end where the PCI-bus and the disk-connectors are, but the end with the little black plastic thing that support the board. The end I'm talking about is where usual PCI boards are no more (due to being smaller) :-) > If it is a transfer LED, then the DMA engine is stuck. If it is a reset, > that means the controller was reset and never released. In either case I > would suspect the initialization code does not work correctly. I have > some work-work emergencies to handle right now, but will start debugging > this driver any day soon. OK, great. Tell me if you want me to do anything. If you start wiping disks, a pre-alpha version of my testbox building scripts are at http://www.freebsd.org/~eivind/testbox-0.1.tar.gz Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 23 09:47:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27967 for freebsd-scsi-outgoing; Wed, 23 Sep 1998 09:47:08 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27925 for ; Wed, 23 Sep 1998 09:46:48 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id SAA29439; Wed, 23 Sep 1998 18:46:44 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA03978; Wed, 23 Sep 1998 18:46:44 +0200 (MET DST) Message-ID: <19980923184643.21602@follo.net> Date: Wed, 23 Sep 1998 18:46:43 +0200 From: Eivind Eklund To: "Justin T. Gibbs" Cc: scsi@FreeBSD.ORG Subject: Re: DPT boot References: <199809230510.XAA00733@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199809230510.XAA00733@narnia.plutotech.com>; from Justin T. Gibbs on Tue, Sep 22, 1998 at 11:10:20PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Sep 22, 1998 at 11:10:20PM -0600, Justin T. Gibbs wrote: > Was Eivind's message originally on the SCSI list? This is the second > time I've heard you reference messages that I haven't seen on the list. > Strange. My message was originally on the SCSI list, and I got it back to my freebsd-scsi mailbox. I'm including a Cc: to the list about this, in case this (missing mail) might be a problem that affect more people. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 23 10:12:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03369 for freebsd-scsi-outgoing; Wed, 23 Sep 1998 10:12:28 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02903; Wed, 23 Sep 1998 10:10:27 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id TAA29636; Wed, 23 Sep 1998 19:10:24 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id TAA00321; Wed, 23 Sep 1998 19:10:23 +0200 (MET DST) Message-ID: <19980923191023.27496@follo.net> Date: Wed, 23 Sep 1998 19:10:23 +0200 From: Eivind Eklund To: "Justin T. Gibbs" , shimon@simon-shapiro.org Cc: scsi@FreeBSD.ORG, postmaster@FreeBSD.ORG Subject: Re: DPT boot References: <199809230510.XAA00733@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199809230510.XAA00733@narnia.plutotech.com>; from Justin T. Gibbs on Tue, Sep 22, 1998 at 11:10:20PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Sep 22, 1998 at 11:10:20PM -0600, Justin T. Gibbs wrote: > In article you wrote: > > Eivind Eklund, On 22-Sep-98 you wrote: > >> I just tried to boot my box with a CAMified kernel, and found that it > >> wouldn't. Everything probed fine, but after the NPX message it just > >> hung for a long while. After a number of minutes (more than 2, as > >> that was what I tried first, but less than 17, which was when I got > >> back to the box) it spit out a message (something like "CCB > >> (0:0:0:0:0) Timed out" - I unfortunately didn't write it down). > > Was Eivind's message originally on the SCSI list? This is the second > time I've heard you reference messages that I haven't seen on the list. > Strange. Correction to previous comment: It didn't get back to me through freebsd-scsi after all. However, it _was_ sent to scsi@freebsd.org (according to my outbox). Sounds like hub may be dropping messages (Simon got it due to an explicit Cc:). > > I get similar symptoms, but much shorter timeouts, like fraction of a > > second per CCB. Then I get the panic I reported. > > This is with the latest version of dpt.c in the tree? I thought it was, but it obviously wasn't - it now works (with sources current as of 16:52 GMT today - supped directly from freefall). It now works here! :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 23 12:26:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26888 for freebsd-scsi-outgoing; Wed, 23 Sep 1998 12:26:24 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26749 for ; Wed, 23 Sep 1998 12:26:03 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id VAA24130; Wed, 23 Sep 1998 21:25:53 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Wed, 23 Sep 1998 21:25:52 +0200 (MET DST) Mime-Version: 1.0 To: "Justin T. Gibbs" Cc: Joakim Henriksson , scsi@FreeBSD.ORG Subject: Re: ncr + CAM still broken for me References: <199809220439.WAA07048@narnia.plutotech.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 23 Sep 1998 21:25:51 +0200 In-Reply-To: "Justin T. Gibbs"'s message of "Mon, 21 Sep 1998 22:39:45 -0600 (MDT)" Message-ID: Lines: 27 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA26837 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Justin T. Gibbs" writes: > In article <199809220244.EAA00991@rmstar.campus.luth.se> you wrote: > > Sep 22 01:09:27 rmstar /kernel: (da1:ncr0:0:2:0): tagged openings now 28 > > Sep 22 01:09:28 rmstar /kernel: (da1:ncr0:0:2:0): tagged openings now 2 > Wow. This drive doesn't like tagged queuing.... We may have killed it > by attempting to queue to many things. Have you looked to see if Quantum > has any new firmware for it? We may want to limit the amount of tagged > I/O performed to this class of drive via a quirk entry. It's a Conner, not a Quantum... the CFP2107S is an Antigua or Barbados or something, must be two or three years old. Conner is dead and buried (bought up by Seagate), so don't expect too much from them. BTW, I have a three-year-old CFP1080S (Antigua) myself, it works like a charm. I keep my CVS repository on it and it's steady as a rock; can't say the same of my recently acquired (and soon to be scrapped) Quantum Fireball. Joakim wrote: > da1 at ncr0 bus 0 target 2 lun 0 > da1: Fixed Direct Access SCSI2 device > da1: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled > da1: 2048MB (4194304 512 byte sectors: 255H 63S/T 261C) DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 24 10:46:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10219 for freebsd-scsi-outgoing; Thu, 24 Sep 1998 10:46:25 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA10086 for ; Thu, 24 Sep 1998 10:46:07 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 26441 invoked by uid 1000); 23 Sep 1998 17:50:02 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19980923131222.21236@follo.net> Date: Wed, 23 Sep 1998 13:50:02 -0400 (EDT) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Eivind Eklund Subject: Re: DPT boot Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Eivind Eklund, On 23-Sep-98 you wrote: > On Tue, Sep 22, 1998 at 11:06:48PM -0400, Simon Shapiro wrote: > > Eivind Eklund, On 22-Sep-98 you wrote: > > > Any clues? Anything I should test? (I can hook up a pretty > > > complete > > > debugging environment here, including doing remote kernel debugging > > > if > > > necessary - at the moment I also have 'scratch' disks I can use for > > > testing, though not having this controller operational means I my > > > main > > > workstation is not usable, so I'd prefer to avoid tests that take a > > > long time). > > > > I assume this controller works on the pre-CAM driver... :-) > > Yes, perfectly. The only problem is that the DPT is attempting to > outsmart > the BIOS, but once it is in FreeBSD, everything works perfectly. I talked to someone who knows at DPT; This is a knwon problem on certain motherboards. I suspect that due to age, etc., they will not fix this minor problem anytime soon. Anyway, this is a BIOS geometry, if I remember correctly. > > > Oh, and while this was happening, the DPT kept a steady light #3 (as > > > counted from the connector-less end of the DPT). > > > > On a 3224 it is bus transfer from adapter, or adapter reset (depends on > > how > > you look at it, and assuming first LED is 1). > > First LED is 1, and I counted from the end of the board that hasn't got > a > connector to the outside world (ie, not the end where the PCI-bus and > the > disk-connectors are, but the end with the little black plastic thing > that > support the board. The end I'm talking about is where usual PCI boards > are > no more (due to being smaller) :-) Yup. This is the Data Transfer From Adaper LED. It means a DMA trasfer starts and then the card hangs. Either Justin is correct and you walked on a firmware bug, or the new driver is missing something in the initialization, that was done correctly in the precambian days. I will look at it, once Justin has saturated his changes to the driver. > > If it is a transfer LED, then the DMA engine is stuck. If it is a > > reset, > > that means the controller was reset and never released. In either case > > I > > would suspect the initialization code does not work correctly. I have > > some work-work emergencies to handle right now, but will start > > debugging > > this driver any day soon. > > OK, great. Tell me if you want me to do anything. If you start wiping > disks, a pre-alpha version of my testbox building scripts are at > http://www.freebsd.org/~eivind/testbox-0.1.tar.gz I am going to test on Bras, and ONLY on brass. IF anyone (Justin?) needs access to it, just say so. Once Brass is passing regression, I will test on Nomis. Then Sendero, then performance... Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 24 11:25:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15116 for freebsd-scsi-outgoing; Thu, 24 Sep 1998 11:25:44 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA15097 for ; Thu, 24 Sep 1998 11:25:15 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 26114 invoked by uid 1000); 23 Sep 1998 15:02:27 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199809230510.XAA00733@narnia.plutotech.com> Date: Wed, 23 Sep 1998 11:02:27 -0400 (EDT) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: "Justin T. Gibbs" Subject: Re: DPT boot Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs, On 23-Sep-98 you wrote: > In article you wrote: > > > > Eivind Eklund, On 22-Sep-98 you wrote: > >> I just tried to boot my box with a CAMified kernel, and found that it > >> wouldn't. Everything probed fine, but after the NPX message it just > >> hung > >> for a long while. After a number of minutes (more than 2, as that > >> was > >> what > >> I tried first, but less than 17, which was when I got back to the > >> box) > >> it > >> spit out a message (something like "CCB (0:0:0:0:0) Timed out" - I > >> unfortunately didn't write it down). > > Was Eivind's message originally on the SCSI list? This is the second > time I've heard you reference messages that I haven't seen on the list. > Strange. I belive it was on current, not scsi. There is no conspiracy here :-) > > I get similar symptoms, but much shorter timeouts, like fraction of a > > second per CCB. Then I get the panic I reported. > > This is with the latest version of dpt.c in the tree? Nope, one that is three days old. > > since there is no > > documentation for the driver layer, I can only guess at what I see; > > for > > each possible drive, there is a CCB. Probably to handle the Inquiry or > > some such. For non-existing drives, these indeed should timeout. > > For non-existing drives, the inquiry should not timeout. It should > come back after a `selection timeout' (which is quite different > than a command timeout) with a selection timeout error code. This, > however, was not where the problem was. Ah... We are learning as we go... > >> The CCB message was the only I got - no disk descriptions from either > >> controller (though I don't know if I should expect them - this is my > >> first CAM experiement). > > > > I would imagine these should come later, once the CCBs are answered. > > Yes. They come up after interrupt services are available and probing > has been completed. I have to chech the driver. The DPT will not do anything (IRT to sending completions) until you clear the interrupt that was queued. Further, it will accept (on most boards) up to 64 commands, but will respond to exactly one and then wait. If I understand you correctly, we may have a situation where the DPT generates an interrupt on the first completed command. Since iti is not served, none of the others is served. then they timeout. > >> Any clues? Anything I should test? (I can hook up a pretty complete > >> debugging environment here, including doing remote kernel debugging > >> if > >> necessary - at the moment I also have 'scratch' disks I can use for > >> testing, > >> though not having this controller operational means I my main > >> workstation is > >> not usable, so I'd prefer to avoid tests that take a long time). > > > > I assume this controller works on the pre-CAM driver... :-) > > This problem has nothing to do with either DPT driver. It has to do > with multi-lun probing and serial number inquiries. On my PM3224A > card, it seems that RAID-1 DPT volumes will not tolerate inquiry > requests to luns greater than 0. An inquiry request for a VPD page > also hangs the controller. This was under firmware 7BG0. I need > to get a 2Mb eeprom before I can test out newer firmware. Since > the description of this problem matches my own experience, I can > only guess that even the latest firmware still has this bug. I've added > quirk entries to the generic SCSI layer to disable multi-lun probing > and serial number requests to all DPT RAID volumes (although RAID-5 > volumes did not seem to have this problem). If this is not sufficient > to address your problem, please let me know. I will. I'll test again today or tomorrow. > > ``...And Carthage shall fall..'' - Cicero > > ``Documentation would have been nice'' - Simon > > This simply isn't fair Simon. I told you I couldn't provide CAM > documentation because of my time constraints, so you asked me to > port the DPT driver to CAM. If you are displeased with the results, > you should talk to me about ways that this can be addressed instead > of posting messages full of inuendo to a public list. Apologies submitted. There was no innuendo intended. I am a bit frustrated, yes. but we can continue the discussion in private. It was wrong of me to make it public. I am sorry. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 24 11:55:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19824 for freebsd-scsi-outgoing; Thu, 24 Sep 1998 11:55:07 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19790; Thu, 24 Sep 1998 11:54:55 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id NAA16433; Thu, 24 Sep 1998 13:54:48 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 24 Sep 1998 13:54:47 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Craig Johnston cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: diamond fireport 20, ok? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 22 Sep 1998, Craig Johnston wrote: > Can someone confirm this works well with FreeBSD? I've seen reports > on the 40 but not the 20. Which symbios chip does the 20 use -- is it > an 875 or an 860? Diamond doesn't supply this info in the specs on their > website. (typical) Should be the 810. If so, it will work fine. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://www.freebsd.org) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 24 19:32:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10006 for freebsd-scsi-outgoing; Thu, 24 Sep 1998 19:32:46 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tbuswell.ne.mediaone.net (tbuswell.ne.mediaone.net [24.128.24.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09884 for ; Thu, 24 Sep 1998 19:32:25 -0700 (PDT) (envelope-from tbuswell@tbuswell.ne.mediaone.net) Received: (from tbuswell@localhost) by tbuswell.ne.mediaone.net (8.9.1/8.8.8) id WAA00412; Thu, 24 Sep 1998 22:31:28 -0400 (EDT) (envelope-from tbuswell) From: Ted Buswell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 24 Sep 1998 22:31:28 -0400 (EDT) To: freebsd-scsi@FreeBSD.ORG Subject: opinions on possible bad disk? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13834.64837.90623.826831@tbuswell.ne.mediaone.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just wondering if anyone knew off the top of their heads what these messages are trying to say; is this disk just about dead? I dropped it once, and it used to not respond to anything [check condition for anything you sent it], but today when I plugged it in it was working well enough for me to recover some data that hadn't been backed up. Now I'm trying to repartition and newfs it, but am being slowed down by the appended. For software, it's -current from 9/22. Thanks for any insight, -Ted Sep 24 22:11:02 tbuswell /kernel: ahc0: rev 0x00 int a irq 19 on pci0.6.0 Sep 24 22:11:02 tbuswell /kernel: ahc0: Illegal cable configuration!!. Only two connectors on the adapter may be used at a time! Sep 24 22:11:02 tbuswell /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Sep 24 22:11:03 tbuswell /kernel: da0 at ahc0 bus 0 target 3 lun 0 Sep 24 22:11:03 tbuswell /kernel: da0: Fixed Direct Access SCSI2 device Sep 24 22:11:03 tbuswell /kernel: da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled Sep 24 22:11:03 tbuswell /kernel: da0 Sep 24 22:11:03 tbuswell /kernel: : 4095MB (8386733 512 byte sectors: 255H 63S/T 522C) Sep 24 16:04:35 tbuswell /kernel: (da0:ahc0:0:3:0): tagged openings now 63 Sep 24 22:13:25 tbuswell /kernel: (da0:ahc0:0:3:0): SCB 0x5 - timed out in datain phase, SCSISIGI == 0x44 Sep 24 22:13:25 tbuswell /kernel: SEQADDR == 0x153 Sep 24 22:13:25 tbuswell /kernel: SSTAT1 == 0x2 Sep 24 22:13:25 tbuswell /kernel: (da0:ahc0:0:3:0): BDR message in message buffer Sep 24 22:13:27 tbuswell /kernel: (da0:ahc0:0:3:0): SCB 0x5 - timed out in datain phase, SCSISIGI == 0x54 Sep 24 22:13:27 tbuswell /kernel: SEQADDR == 0x153 Sep 24 22:13:27 tbuswell /kernel: SSTAT1 == 0x2 Sep 24 22:13:27 tbuswell /kernel: (da0:ahc0:0:3:0): no longer in timeout, status = 34b Sep 24 22:13:27 tbuswell /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Sep 24 22:14:42 tbuswell /kernel: (da0:ahc0:0:3:0): SCB 0x5 - timed out in datain phase, SCSISIGI == 0x44 Sep 24 22:14:42 tbuswell /kernel: SEQADDR == 0x153 Sep 24 22:14:42 tbuswell /kernel: SSTAT1 == 0x2 Sep 24 22:14:42 tbuswell /kernel: (da0:ahc0:0:3:0): BDR message in message buffer Sep 24 22:14:44 tbuswell /kernel: (da0:ahc0:0:3:0): SCB 0x5 - timed out in datain phase, SCSISIGI == 0x54 Sep 24 22:14:44 tbuswell /kernel: SEQADDR == 0x153 Sep 24 22:14:44 tbuswell /kernel: SSTAT1 == 0x2 Sep 24 22:14:44 tbuswell /kernel: (da0:ahc0:0:3:0): no longer in timeout, status = 34b Sep 24 22:14:44 tbuswell /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 24 21:55:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27237 for freebsd-scsi-outgoing; Thu, 24 Sep 1998 21:55:13 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27213 for ; Thu, 24 Sep 1998 21:55:06 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id WAA00972; Thu, 24 Sep 1998 22:48:29 -0600 (MDT) Date: Thu, 24 Sep 1998 22:48:29 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809250448.WAA00972@narnia.plutotech.com> To: Ted Buswell cc: scsi@FreeBSD.ORG Subject: Re: opinions on possible bad disk? Newsgroups: pluto.freebsd.scsi In-Reply-To: <13834.64837.90623.826831@tbuswell.ne.mediaone.net> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <13834.64837.90623.826831@tbuswell.ne.mediaone.net> you wrote: > > Just wondering if anyone knew off the top of their heads > what these messages are trying to say; is this disk > just about dead? > ahc0: rev 0x00 int a irq 19 on pci0.6.0 > ahc0: Illegal cable configuration!! > Only two connectors on the adapter may be used at a time! I don't know how to be much clearer than that. 8-) You can only use two of the three connectors on a 2940UW without 'T'ing the bus. Your system is suffering from SCSI bus signal integrety problems because of your illegal cable configuration. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 24 22:12:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29006 for freebsd-scsi-outgoing; Thu, 24 Sep 1998 22:12:39 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28999 for ; Thu, 24 Sep 1998 22:12:35 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id OAA28654; Fri, 25 Sep 1998 14:42:21 +0930 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199809250448.WAA00972@narnia.plutotech.com> Date: Fri, 25 Sep 1998 14:42:20 +0930 (CST) From: "Daniel O'Connor" To: "Justin T. Gibbs" Subject: Re: opinions on possible bad disk? Cc: scsi@FreeBSD.ORG, Ted Buswell Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 25-Sep-98 Justin T. Gibbs wrote: > > ahc0: rev 0x00 int a irq 19 on pci0.6.0 > > ahc0: Illegal cable configuration!! > > Only two connectors on the adapter may be used at a time! > I don't know how to be much clearer than that. 8-) You can only use > two of the three connectors on a 2940UW without 'T'ing the bus. Your > system is suffering from SCSI bus signal integrety problems because of > your illegal cable configuration. I get this on a 7895 built into a Super Micro motherboard.. Which is kind of suprising since it has 2 chains, and there is one device plugged into each chain :) The BIOS is set to auto-terminate, which I was told was the cause, and to turn auto terminate off (then again, it actually works as it stands.. :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 24 23:28:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05922 for freebsd-scsi-outgoing; Thu, 24 Sep 1998 23:28:51 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05917 for ; Thu, 24 Sep 1998 23:28:50 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id AAA14626; Fri, 25 Sep 1998 00:28:34 -0600 (MDT) Message-Id: <199809250628.AAA14626@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG, Ted Buswell Subject: Re: opinions on possible bad disk? In-reply-to: Your message of "Fri, 25 Sep 1998 14:42:20 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Sep 1998 00:22:02 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >On 25-Sep-98 Justin T. Gibbs wrote: >>> ahc0: rev 0x00 int a irq 19 on pci0.6.0 >>> ahc0: Illegal cable configuration!! >>> Only two connectors on the adapter may be used at a time! ... >I get this on a 7895 built into a Super Micro motherboard.. >Which is kind of suprising since it has 2 chains, and there is one device >plugged into each chain :) >The BIOS is set to auto-terminate, which I was told was the cause, and to >turn auto terminate off (then again, it actually works as it stands.. :) I don't know why MB manufacturers insist on allowing the user to enable auto-term when they didn't put auto-term logic on the MB. Anyway, you are currently playing a very dangerous game by leaving auto-term enabled. The bus is not properly terminated and will someday start showing errors. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 24 23:30:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06117 for freebsd-scsi-outgoing; Thu, 24 Sep 1998 23:30:42 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06112 for ; Thu, 24 Sep 1998 23:30:39 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id PAA29172; Fri, 25 Sep 1998 15:59:56 +0930 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199809250628.AAA14626@pluto.plutotech.com> Date: Fri, 25 Sep 1998 15:59:55 +0930 (CST) From: "Daniel O'Connor" To: "Justin T. Gibbs" Subject: Re: opinions on possible bad disk? Cc: Ted Buswell , scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 25-Sep-98 Justin T. Gibbs wrote: > >The BIOS is set to auto-terminate, which I was told was the cause, and to > >turn auto terminate off (then again, it actually works as it stands.. :) > I don't know why MB manufacturers insist on allowing the user to enable > auto-term when they didn't put auto-term logic on the MB. Anyway, > you are currently playing a very dangerous game by leaving auto-term > enabled. The bus is not properly terminated and will someday start > showing errors. OK.. Thanks, I did not realise this was the case :( Thanks again for the warning. *Daniel gets his large axe out and starts sharpening some more --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 24 23:55:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10066 for freebsd-scsi-outgoing; Thu, 24 Sep 1998 23:55:10 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09963 for ; Thu, 24 Sep 1998 23:54:38 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.9.1/8.7.3) id IAA00398 for freebsd-scsi@freebsd.org; Fri, 25 Sep 1998 08:54:19 +0200 (CEST) From: Holm Tiffe Message-Id: <199809250654.IAA00398@magnet.geophysik.tu-freiberg.de> Subject: AHA 2742T+CAM+SMP problems 2nd. try To: freebsd-scsi@FreeBSD.ORG Date: Fri, 25 Sep 1998 08:54:19 +0200 (CEST) Reply-To: freebsd@magnet.geophysik.tu-freiberg.de X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, this is the 2nd try to get a ligth on tis prob. 1. my system is an freebsd-current-aout from 3 days ago. 2. the Motherboard is aN ASUS PCI/E P54NP4 Dual P5/100 board 3. both Processors are now P5/100 Mask SX963. 4. the SCSI Controller is an Adaptec AHA 2742T Rev. C 5. the system is running stable for years. 6. the system boots properly in Uniprocessor mode, dmesg: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-BETA #6: Tue Sep 22 23:57:59 MET DST 1998 root@unicorn.pppnet.tu-freiberg.de:/usr/src/sys/compile/UNICORN Timecounter "i8254" frequency 1193175 Hz cost 3575 ns Timecounter "TSC" frequency 99998845 Hz cost 229 ns CPU: Pentium/P54C (100.00-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x3bf real memory = 67108864 (65536K bytes) avail memory = 62869504 (61396K bytes) DEVFS: ready for devices eisa0: Probing for devices on the EISA bus ahc0: at 0x1c00-0x1cff irq 11 on eisa0 slot 1 ahc0: aic7770 <= Rev C, Twin Channel, A SCSI Id=7, B SCSI Id=7, 4/255 SCBs Probing for devices on PCI bus 0: chip0: rev 0x11 on pci0.0. 0 chip1: rev 0x04 on pci0.2.0 vga0: rev 0x00 int a irq 9 on pci0.5.0 de0: rev 0x23 int a irq 10 on pci0.6.0 de0: Cogent 21040 [10Mb/s] pass 2.3 de0: address 00:00:92:90:09:8d Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16450 dgb0: PC/Xe 64K dgb0 at 0x300-0x303 maddr 0xd0000 msize 65536 on isa dgb0: 8 ports lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in npx0 on motherboard npx0: INT 16 interface de0: enabling AUI/BNC port Intel Pentium F00F detected, installing workaround DEVFS: ready to run (probe9:ahc0:1:2:0): Sending SDTR!! sa0 at ahc0 bus 1 target 3 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 4.464MB/s transfers (4.464MHz, offset 8) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI1 device da0: 3.676MB/s transfers (3.676MHz, offset 8) da0: 203MB (415872 512 byte sectors: 64H 32S/T 203C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 2048MB (4194304 512 byte sectors: 64H 32S/T 2048C) da2 at ahc0 bus 1 target 2 lun 0 da2: Fixed Direct Access SCSI2 device da2: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da2: 1910MB (3912172 512 byte sectors: 64H 32S/T 1910C) changing root device to da1s1a cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 4.32MB/s transfers (4.32MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present (da1:ahc0:0:2:0): tagged openings now 33 (da1:ahc0:0:2:0): tagged openings now 32 (da1:ahc0:0:2:0): tagged openings now 31 here comes the mptable output: MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f8360 signature: '_MP_' length: 16 bytes version: 1.1 checksum: 0x9d mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f8374 signature: 'PCMP' base table length: 228 version: 1.1 checksum: 0x51 OEM ID: 'ASUSTEK0' Product ID: 'P54NP4000000' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 20 local APIC address: 0xfee00000 extended table length: 0 extended table checksum: 0 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 5 2 1 0x07bf 1 0x11 AP, usable 5 2 1 0x07bf -- Bus: Bus ID Type 0 EISA 1 PCI -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# INT conforms conforms 0 1 2 1 INT conforms conforms 0 0 2 2 INT conforms conforms 0 3 2 3 INT conforms conforms 0 4 2 4 INT conforms conforms 0 5 2 5 INT conforms conforms 0 6 2 6 INT conforms conforms 0 7 2 7 INT conforms conforms 0 8 2 8 INT conforms conforms 0 9 2 9 INT conforms conforms 0 10 2 10 INT conforms conforms 0 11 2 11 INT conforms conforms 0 12 2 12 INT conforms conforms 0 13 2 13 INT conforms conforms 0 14 2 14 INT conforms conforms 0 15 2 15 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ------------------------------------------------------------------------------- # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional (built-in defaults will work in most cases): #options NCPU=2 # number of CPUs #options NBUS=2 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs the devfs is configured in the kernel but not mounted. 7. when I boot up the SMP kernel the system hangs after the line SMP: AP CPU #1 Launched! after ca. 1,5 minutes I get: (typed from the display by hand, maybe these a bit incorrect) (probe9:ahc0:1:2:0): sending SDTR!! (probe9:ahc0:1:2:0): SCB 0x09 timed out in message phasem SCSISIGI == 0xe6 SEQADDR == 0xdc SSTAT1 == 0x03 (some line with Bus Device Reset) (probe9:ahc0:1:2:0) BDR message in message buffer Bus Device Reset Message sent ahc0: Bus Device Reset on B:2 1 SCBs aborted than comes the same on Channel A for every possible TARGET+LUN nothing other happens, the machine loops there. .. sorry cold'nt write down this better, must manage to get a 2nd. computer to cut this from a serial console.... The problem only occurs with the SMP kernel, in UP mode the machine boots up successfully. Can please anyone enlighten me where I have to look to find the bug ? Here comes the kernel config file from the SMP kernel: # # UNICORN # # machine "i386" cpu "I586_CPU" ident UNICORN maxusers 20 options INET #InterNETworking options FFS #Berkeley Fast Filesystem #options SOFTUPDATES options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options UCONSOLE #Allow users to grab the console options SYSVSHM options SYSVSEM options SYSVMSG options "SHMMAX=16777216" options "SHMSEG=32" options "SHMMNI=128" options "SHMALL=4096" options KTRACE #options "AUTO_EOI_2" options "CLK_CALIBRATION_LOOP" options "CLK_USE_I8254_CALIBRATION" options "CLK_USE_TSC_CALIBRATION" options PQ_LARGECACHE #options DDB options "NDGBPORTS=8" #options "VM86" options DEVFS options SMP options APIC_IO options NCPU=2 options DDB config kernel root on da1 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 controller eisa0 controller ahc0 controller scbus0 at ahc0 bus 0 controller scbus1 at ahc0 bus 1 device da0 at scbus0 target 0 device da1 at scbus0 target 2 device da2 at scbus1 target 2 device sa0 at scbus1 target 3 device sa1 device cd0 at scbus0 target 4 device pass0 # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options "PCVT_FREEBSD=210" # pcvt running on FreeBSD 2.1 #options XSERVER # include code for XFree86 device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr #device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr #device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr #device sio4 at isa? port 0x2a0 tty flags 0x781 #device sio5 at isa? port 0x2a8 tty flags 0x781 #device sio6 at isa? port 0x2b0 tty flags 0x781 #device sio7 at isa? port 0x2b8 tty flags 0x781 irq5 vector siointr device dgb0 at isa? tty port 0x300 iomem 0xd0000 iosiz ? flags 0x0 device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmint r #controller snd0 #device sb0 at isa? port 0x220 irq9 conflicts drq1 vector sb intr #device opl0 at isa? port 0x388 conflicts #controller snd0 #device mss0 at isa? port 0x530 irq 9 drq 1 vector adintr #device mpu0 at isa? port 0x330 irq 5 drq 0 device de0 pseudo-device loop pseudo-device ether pseudo-device sl 1 # ijppp uses tun instead of ppp device pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 64 pseudo-device gzip # Exec gzipped a.out's pseudo-device bpfilter 4 # Berkeley Packet Filter pseudo-device vn 2 # Vnode Driver -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 25 05:07:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21905 for freebsd-scsi-outgoing; Fri, 25 Sep 1998 05:07:50 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21871; Fri, 25 Sep 1998 05:07:23 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199809251207.FAA21871@hub.freebsd.org> Subject: Re: DPT boot In-Reply-To: <19980923191023.27496@follo.net> from Eivind Eklund at "Sep 23, 98 07:10:23 pm" To: eivind@yes.no (Eivind Eklund) Date: Fri, 25 Sep 1998 05:07:22 -0700 (PDT) Cc: gibbs@narnia.plutotech.com, shimon@simon-shapiro.org, scsi@FreeBSD.ORG, postmaster@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org can you give me the Message-Id: from the message that may have been dropped? i hope to be able to determine what happened to it. jmb Eivind Eklund wrote: > On Tue, Sep 22, 1998 at 11:10:20PM -0600, Justin T. Gibbs wrote: > > In article you wrote: > > > Eivind Eklund, On 22-Sep-98 you wrote: > > >> I just tried to boot my box with a CAMified kernel, and found that it > > >> wouldn't. Everything probed fine, but after the NPX message it just > > >> hung for a long while. After a number of minutes (more than 2, as > > >> that was what I tried first, but less than 17, which was when I got > > >> back to the box) it spit out a message (something like "CCB > > >> (0:0:0:0:0) Timed out" - I unfortunately didn't write it down). > > > > Was Eivind's message originally on the SCSI list? This is the second > > time I've heard you reference messages that I haven't seen on the list. > > Strange. > > Correction to previous comment: It didn't get back to me through > freebsd-scsi after all. However, it _was_ sent to scsi@freebsd.org > (according to my outbox). Sounds like hub may be dropping messages (Simon > got it due to an explicit Cc:). > > > > I get similar symptoms, but much shorter timeouts, like fraction of a > > > second per CCB. Then I get the panic I reported. > > > > This is with the latest version of dpt.c in the tree? > > I thought it was, but it obviously wasn't - it now works (with sources > current as of 16:52 GMT today - supped directly from freefall). > > It now works here! :-) > > Eivind. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 25 10:04:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01903 for freebsd-scsi-outgoing; Fri, 25 Sep 1998 10:04:30 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from arjun.niksun.com (gw.niksun.com [206.20.52.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01895 for ; Fri, 25 Sep 1998 10:04:26 -0700 (PDT) (envelope-from ath@niksun.com) Received: from stiegl.niksun.com (stiegl.niksun.com [10.0.0.44]) by arjun.niksun.com (8.8.8/8.8.8) with ESMTP id NAA21612; Fri, 25 Sep 1998 13:04:19 -0400 (EDT) Received: (from ath@localhost) by stiegl.niksun.com (8.8.8/8.8.7) id NAA09275; Fri, 25 Sep 1998 13:04:19 -0400 (EDT) (envelope-from ath) To: Chris Dillon cc: freebsd-scsi@FreeBSD.ORG Subject: Re: diamond fireport 20, ok? References: From: Andrew Heybey Date: 25 Sep 1998 17:04:18 +0000 In-Reply-To: Chris Dillon's message of Thu, 24 Sep 1998 13:54:47 -0500 (CDT) Message-ID: <85k92si0od.fsf@stiegl.niksun.com> Lines: 19 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chris Dillon writes: > > Can someone confirm this works well with FreeBSD? I've seen reports > > on the 40 but not the 20. Which symbios chip does the 20 use -- is it > > an 875 or an 860? Diamond doesn't supply this info in the specs on their > > website. (typical) > > Should be the 810. If so, it will work fine. No and yes. It is the 875, and it does work just fine. Probes as: ncr0 rev 4 int a irq 9 on pci0:13:0 Note that the board that I have has a *narrow* bus, despite the probe message. It seems that the only difference between the narrow and wide is the connector(s) soldered on the board. I also have a 40 (wide bus) in another machine, and it probes as the same thing. andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 25 10:32:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06008 for freebsd-scsi-outgoing; Fri, 25 Sep 1998 10:32:12 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tbuswell.ne.mediaone.net (tbuswell.ne.mediaone.net [24.128.24.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05995 for ; Fri, 25 Sep 1998 10:32:10 -0700 (PDT) (envelope-from tbuswell@tbuswell.ne.mediaone.net) Received: (from tbuswell@localhost) by tbuswell.ne.mediaone.net (8.9.1/8.8.8) id NAA00836; Fri, 25 Sep 1998 13:31:15 -0400 (EDT) (envelope-from tbuswell) From: Ted Buswell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 25 Sep 1998 13:31:15 -0400 (EDT) To: "Justin T. Gibbs" Cc: "Daniel O'Connor" , scsi@FreeBSD.ORG Subject: Re: opinions on possible bad disk? In-Reply-To: <199809250628.AAA14626@pluto.plutotech.com> References: <199809250628.AAA14626@pluto.plutotech.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13835.54027.545411.245713@tbuswell.ne.mediaone.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks for the feedback; I was too absorbed with the fact that this drive is only recently back-from-the-dead to check the bus; it was a termination problem and the onboard 7880 not doing the right thing was only the start. ;( Thanks, -Ted Justin T. Gibbs writes: > > > >On 25-Sep-98 Justin T. Gibbs wrote: > >>> ahc0: rev 0x00 int a irq 19 on pci0.6.0 > >>> ahc0: Illegal cable configuration!! > >>> Only two connectors on the adapter may be used at a time! > > ... > > >I get this on a 7895 built into a Super Micro motherboard.. > >Which is kind of suprising since it has 2 chains, and there is one device > >plugged into each chain :) > >The BIOS is set to auto-terminate, which I was told was the cause, and to > >turn auto terminate off (then again, it actually works as it stands.. :) > > I don't know why MB manufacturers insist on allowing the user to enable > auto-term when they didn't put auto-term logic on the MB. Anyway, > you are currently playing a very dangerous game by leaving auto-term > enabled. The bus is not properly terminated and will someday start > showing errors. > > -- > Justin > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 25 12:54:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29214 for freebsd-scsi-outgoing; Fri, 25 Sep 1998 12:54:38 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29184; Fri, 25 Sep 1998 12:54:23 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.9.1/8.7.3) id VAA02617; Fri, 25 Sep 1998 21:50:02 +0200 (CEST) From: Holm Tiffe Message-Id: <199809251950.VAA02617@magnet.geophysik.tu-freiberg.de> Subject: AHA 2742T+CAM+SMP problems 2nd. try #2 To: freebsd-scsi@FreeBSD.ORG Date: Fri, 25 Sep 1998 21:50:01 +0200 (CEST) Cc: freebsd-smp@FreeBSD.ORG Reply-To: freebsd@magnet.geophysik.tu-freiberg.de X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org More from my SMP problem: Today evening I have upgraded my src/sys to cvs-cur.4676 (cam_xpt.c version 1.13) and now I get the following with the new SMP kernel: SMP: AP CPU #1 Launched! ........................... here is a long pause with a stady lightening SCSI LED (probe9:ahc0:1:2:0): Sending SDTR! (what this means Scsi Device Target Reset ?) (probe9:ahc0:1:2:0): SCB 0x9 timed out in message in phase, SCSISIGI == 0xb6 SEQADDR == 0x15b SSTAT1 == 0x13 (probe9:ahc0:1:2:0): BDR message in message buffer Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1, lapicid = 01000000 fault virtual address = 0xb8 funkt code = supervisor read, page not present instruction pointer = 0x8:0xf0106a78 stack pointer = 0x10:0xff804cc4 frame pointer = 0x10:0xff805e04 code segment = base 0x0,limit 0xfffff, type 0x16 = DPL0; pres1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = Idle interrupt mask = cam <- SMP: XXX kernel type 12 trap, code=0 stopped at _xpt_set_transfer_settings+0xd8: -> testb $0x20,0xb8(%esi) trace: _xpt_set_transfer_settings(ff804e78,1) at _xpt_set_transfer_settings+0xd8 _xpt_async(200,f05acc40,ff804e78,ff804e78,f05acc40,1,f07b8000) at _xpt_async+0xb0 _ahc_set_syncrate(f07b8000,ff804f38,f05acc40,0,0,0,1,f07b8000,ff804f38,f05acc40,0,1) at ahc_set_syncrate+0x1de _ahc_handle_devreset() _ahc_handle_scsiint() _ahc_intr() .... this is shorted, pencil broken :-) this seams to be a NULL pointer reference in cam_xpt.c around line 5302 , maybe device->quirk is not jet initialized ? Holm PS: Changing the AHA 2742T to another (rev C) and changing the P5/90 CPU to a P5/100 has nothing changed. The SCSI bus hangs after the SMP: AP CPU #1 Launched line... -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 25 13:56:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10711 for freebsd-scsi-outgoing; Fri, 25 Sep 1998 13:56:08 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10666 for ; Fri, 25 Sep 1998 13:56:04 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id OAA20765; Fri, 25 Sep 1998 14:49:19 -0600 (MDT) Date: Fri, 25 Sep 1998 14:49:19 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809252049.OAA20765@narnia.plutotech.com> To: freebsd@magnet.geophysik.tu-freiberg.de cc: scsi@FreeBSD.ORG Subject: Re: AHA 2742T+CAM+SMP problems 2nd. try Newsgroups: pluto.freebsd.scsi In-Reply-To: <199809250654.IAA00398@magnet.geophysik.tu-freiberg.de> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199809250654.IAA00398@magnet.geophysik.tu-freiberg.de> you wrote: > > 7. when I boot up the SMP kernel the system hangs after the line > SMP: AP CPU #1 Launched! > after ca. 1,5 minutes I get: (typed from the display by hand, > maybe these a bit incorrect) > > (probe9:ahc0:1:2:0): sending SDTR!! > (probe9:ahc0:1:2:0): SCB 0x09 timed out in message phasem SCSISIGI == 0xe6 > SEQADDR == 0xdc > SSTAT1 == 0x03 It looks like we are not seeing interrupts. I do not know why, but I doubt that CAM is at fault. Looks like an SMP problem. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 25 15:02:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21340 for freebsd-scsi-outgoing; Fri, 25 Sep 1998 15:02:30 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA21156 for ; Fri, 25 Sep 1998 15:02:08 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 12454 invoked by uid 1000); 25 Sep 1998 23:04:58 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 25 Sep 1998 19:04:58 -0400 (EDT) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: freebsd-scsi@FreeBSD.ORG Subject: DPT Under CAM - Confirmation Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The kernel, as of last night, boots DPT off the CAM source. Although loads are light/moderate on nomis, it seems that the lost interrupt problem is not there. I still am a bit puzzled by how drive IDs are assigned, and how/why hard wiring devices does not seem to be honored, but am far from complaining about it (yet :-). I will work on that and the measure_performance issues this weekend. Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 26 03:07:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14157 for freebsd-scsi-outgoing; Sat, 26 Sep 1998 03:07:00 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14145 for ; Sat, 26 Sep 1998 03:06:57 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id MAA09500 for freebsd-scsi@FreeBSD.ORG; Sat, 26 Sep 1998 12:06:49 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id ED8F71556; Sat, 26 Sep 1998 11:47:08 +0200 (CEST) Date: Sat, 26 Sep 1998 11:47:08 +0200 From: Ollivier Robert To: freebsd-scsi@FreeBSD.ORG Subject: Re: DPT Under CAM - Confirmation Message-ID: <19980926114708.A16804@keltia.freenix.fr> Mail-Followup-To: freebsd-scsi@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i In-Reply-To: ; from Simon Shapiro on Fri, Sep 25, 1998 at 07:04:58PM -0400 X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4660 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Simon Shapiro: > I still am a bit puzzled by how drive IDs are assigned, and how/why hard > wiring devices does not seem to be honored, but am far from complaining > about it (yet :-). I'm not using a DPT controller but my hardwired devices are honored: -=-=- cd1 at ncr1 bus 0 target 3 lun 0 da0 at ncr0 bus 0 target 0 lun 0 da1 at ncr0 bus 0 target 1 lun 0 da2 at ncr0 bus 0 target 2 lun 0 da12 at ncr1 bus 0 target 2 lun 0 sa0 at ncr1 bus 0 target 5 lun 0 sa1 at ncr0 bus 0 target 4 lun 0 -=-=- with this: -=-=- controller scbus0 at ncr0 controller scbus1 at ncr1 # NCR0: ASUS SC-875 # # IBM DCAS 34330W ID #0 # IBM DCAS 34330W ID #1 # IBM DORS 32160 ID #2 # Tandberg TDC-3600 ID #4 # disk da0 at scbus0 target 0 disk da1 at scbus0 target 1 disk da2 at scbus0 target 2 disk da3 at scbus0 target 3 tape sa1 at scbus0 target 4 # # NCR1: ASUS SC-200 # # CONNER CFP-1080S ID #2 # SONY CDU-415 ID #3 # HP 35480A ID #5 # disk da10 at scbus1 target 0 disk da11 at scbus1 target 1 disk da12 at scbus1 target 2 disk da13 at scbus1 target 3 tape sa0 at scbus1 target 5 device cd0 at scbus1 target 6 -=-=- -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-BETA #0: Sat Sep 19 23:38:25 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 26 11:04:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02237 for freebsd-scsi-outgoing; Sat, 26 Sep 1998 11:04:03 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02183; Sat, 26 Sep 1998 11:03:57 -0700 (PDT) (envelope-from digital@www2.shoppersnet.com) Received: from localhost (digital@localhost) by www2.shoppersnet.com (8.8.8/8.8.8) with SMTP id LAA02708; Sat, 26 Sep 1998 11:04:43 -0700 (PDT) (envelope-from digital@www2.shoppersnet.com) Date: Sat, 26 Sep 1998 11:04:43 -0700 (PDT) From: Howard Lew To: Dan Busarow cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: NCR 53c875 SCSI Problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 26 Sep 1998, Dan Busarow wrote: > On Fri, 25 Sep 1998, Howard Lew wrote: > > on FreeBSD 2.2.6... > > > > ncr0 rev 4 int a irq 12 on pci0:11 > > sd0(ncr0:2:0):COMMAND FAILED (9 ff) @ f0692c00 > > ncr0: aborting job... > > ncr0:0: ERROR (90:0) (8-a6-0) (0/5) @ (script a0:43000060). > > ncr0: script cmd=878b0000 > > ncr0: regdump:da 00 00 05 47 00 02 0f 71 08 00 a6 80 00 00 02. > > ncr0: restart (fatal error). > > > > > > I'd check cables and termination. Might be a DOA adapter as well. > This is from 2.2.5 but I have also used the FP40 on 2.2.6. > > ncr0 rev 4 int a irq 9 on pci0:8 > ncr0 waiting for scsi devices to settle > (ncr0:0:0): "QUANTUM FIREBALL SE2.1S PJ09" type 0 fixed SCSI 2 > sd0(ncr0:0:0): Direct-Access > sd0(ncr0:0:0): 20.0 MB/s (50 ns, offset 15) > 2051MB (4201304 512 byte sectors) > (ncr0:1:0): "QUANTUM FIREBALL ST4.3S 0F0C" type 0 fixed SCSI 2 > sd1(ncr0:1:0): Direct-Access > sd1(ncr0:1:0): 20.0 MB/s (50 ns, offset 15) > 4136MB (8471232 512 byte sectors) > (ncr0:3:0): "NEC CD-ROM DRIVE:222 3.0i" type 5 removable SCSI 2 > cd0(ncr0:3:0): CD-ROM > cd0(ncr0:3:0): asynchronous. > can't get the size > (ncr0:4:0): "CONNER CTT8000-S 1.17" type 1 removable SCSI 2 > st0(ncr0:4:0): Sequential-Access > st0(ncr0:4:0): 5.0 MB/s (200 ns, offset 15) > density code 0x45, drive empty > Yes it is terminated correctly. This is the same exact setup I had with the 810 card. I also checked out the card by loading win95 and it works okay, so it must be a software issue. However, if I pull the Seagate hard disk off the scsi bus, the bootup works fine. Of course, then I could not use the drive for FreeBSD. Somehow, the Seagate Hawk drive is having or causing the command failure problem -- something that never occurred with the 810 when using freebsd. Does anyone know what kind of command it is failing on? Is it trying to query the drive speed or something? Any ideas guys? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 26 13:15:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13213 for freebsd-scsi-outgoing; Sat, 26 Sep 1998 13:15:38 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from java.dpcsys.com (java.dpcsys.com [206.16.184.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13202; Sat, 26 Sep 1998 13:15:34 -0700 (PDT) (envelope-from dan@dpcsys.com) Received: from localhost (dan@localhost) by java.dpcsys.com (8.8.7/8.8.2) with SMTP id NAA03108; Sat, 26 Sep 1998 13:15:56 -0700 (PDT) Date: Sat, 26 Sep 1998 13:15:56 -0700 (PDT) From: Dan Busarow Reply-To: Dan Busarow To: Howard Lew cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: NCR 53c875 SCSI Problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 26 Sep 1998, Howard Lew wrote: > Somehow, the Seagate Hawk drive is having or causing the command failure > problem -- something that never occurred with the 810 when using freebsd. Try going into the SCSI setup on boot up and set the transfer speed to 20MB so it doesn't try wide negotiation. Dan -- Dan Busarow 949 443 4172 Dana Point Communications, a California corporation dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 26 17:26:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10416 for freebsd-scsi-outgoing; Sat, 26 Sep 1998 17:26:40 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10409; Sat, 26 Sep 1998 17:26:38 -0700 (PDT) (envelope-from digital@www2.shoppersnet.com) Received: from localhost (digital@localhost) by www2.shoppersnet.com (8.8.8/8.8.8) with SMTP id RAA05346; Sat, 26 Sep 1998 17:27:35 -0700 (PDT) (envelope-from digital@www2.shoppersnet.com) Date: Sat, 26 Sep 1998 17:27:34 -0700 (PDT) From: Howard Lew To: Dan Busarow cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: NCR 53c875 SCSI Problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 26 Sep 1998, Dan Busarow wrote: > On Sat, 26 Sep 1998, Howard Lew wrote: > > Somehow, the Seagate Hawk drive is having or causing the command failure > > problem -- something that never occurred with the 810 when using freebsd. > > Try going into the SCSI setup on boot up and set the transfer speed > to 20MB so it doesn't try wide negotiation. > I tried setting the speed to 20MB and keeping it at 8 bit, but regardless of what I do the FreeBSD bootup probe still says it is wide scsi and that 16 bit is enabled. Right after that it starts all the command failed messages. I flashed upgraded the bios and it didn't help. Is there a way to force the driver to use narrow mode? I know this hard disk can do wide scsi, but I am using the 50 pin connector right now. Is narrow the default? So if I comment out the code in the setwide in ncr.c should that do the trick? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 26 23:17:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16627 for freebsd-scsi-outgoing; Sat, 26 Sep 1998 23:17:51 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16622; Sat, 26 Sep 1998 23:17:48 -0700 (PDT) (envelope-from digital@www2.shoppersnet.com) Received: from localhost (digital@localhost) by www2.shoppersnet.com (8.8.8/8.8.8) with SMTP id XAA02547; Sat, 26 Sep 1998 23:18:41 -0700 (PDT) (envelope-from digital@www2.shoppersnet.com) Date: Sat, 26 Sep 1998 23:18:41 -0700 (PDT) From: Howard Lew To: Dan Busarow cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: NCR 53c875 SCSI Problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 26 Sep 1998, Howard Lew wrote: > On Sat, 26 Sep 1998, Dan Busarow wrote: > > > On Sat, 26 Sep 1998, Howard Lew wrote: > > > Somehow, the Seagate Hawk drive is having or causing the command failure > > > problem -- something that never occurred with the 810 when using freebsd. > > > > Try going into the SCSI setup on boot up and set the transfer speed > > to 20MB so it doesn't try wide negotiation. > > > > I tried setting the speed to 20MB and keeping it at 8 bit, but regardless > of what I do the FreeBSD bootup probe still says it is wide scsi and that > 16 bit is enabled. Right after that it starts all the command failed > messages. I flashed upgraded the bios and it didn't help. > > Is there a way to force the driver to use narrow mode? I know this hard > disk can do wide scsi, but I am using the 50 pin connector right now. Is > narrow the default? So if I comment out the code in the setwide in ncr.c > should that do the trick? > > I did some more checking around and found out that Debian Linux also works fine with the Seagate Hawk/Diamond Fireport 40 combination. But FreeBSD, NetBSD, and OpenBSD all suffer from the same problem of being locked on "wide bus" when I am using the narrow connector. Any ideas? Thanks for the help so far. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message