From owner-freebsd-scsi Sun Dec 1 2:48:26 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78E3237B401 for ; Sun, 1 Dec 2002 02:48:24 -0800 (PST) Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05F3343EBE for ; Sun, 1 Dec 2002 02:48:24 -0800 (PST) (envelope-from groudier@free.fr) Received: from [192.168.1.129] (212.232.50.94) by mail.libertysurf.net (6.5.026) id 3DB7CDCE00B24F12; Sun, 1 Dec 2002 11:48:08 +0100 Date: Sun, 1 Dec 2002 12:48:21 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: groudier@localhost.my.domain To: "Ronald F. Guilmette" Cc: Wilko Bulte , "Justin T. Gibbs" , Subject: Re: Upgrade from Adaptec 2940UW to 29160N - Problem solved! In-Reply-To: <15086.1038605400@monkeys.com> Message-ID: <20021201124031.B2519-100000@localhost.my.domain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 29 Nov 2002, Ronald F. Guilmette wrote: > In message <20021129202056.A59622@freebie.xs4all.nl>, you wrote: > > >On Fri, Nov 29, 2002 at 11:04:45AM -0800, Ronald F. Guilmette wrote: > >> > >> In message <2793220000.1038502309@aslan.scsiguy.com>, you wrote: > >> > >> >>>> The only mystery that still remains after this whole ordeal is ``= Why > >> >>>> was it possible to boot from the mis-allocated partition back whe= n I > >> >>>> was using the Adaptec 2940UW, even though it was clearly _not_ po= ssible > >> >>>> to boot from the exact same bleedin' partition when using a newer= and > >> >>>> ``more advanced'' Adaptec 29160N ? > >> >>> > >> >>> Most likely because the setting for "extended translation" was not= the > >> >>> same on both controllers. > >> >> > >> >> Actually, it was. I am quite sure on that point. > >> >> > >> >> Both controllers had "BIOS support for disks > 1 GB" set to "disble= d". > >> > > >> >And you use a geometry of 255/63? That's just plain wrong. 8-) > >> > >> It is? > >> > >> Who says it is? > > > >Justin, who happens to work Adaptec, and has been one of the chief > >developers of the FreeBSD SCSI subsystem > > OK. That's good enough for me. > > But I wish that some of this stuff was written down someplace, for > the benefit of poor ignorant sods like me who are just trying to > make their peripherials work. > > > P.S. As we speak, I am typing this on a machine whose root partition is > on my shiny new IBM 18GB SCSI drive, with geometry set to 255/63, *and* > the 29160N it is hooked up to is (I'm quite sure) set to "Support for > disks > 1GB" *disabled*. > > So if this isn't supposed to work, then somebody please explain to me > why it _does_ clearly work. The BIOS can read the partition table and fix your broken setup when possible. One BIOS is probably slightly more lazy than the other one. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 1 4:54:28 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2D8037B401; Sun, 1 Dec 2002 04:54:24 -0800 (PST) Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 043EE43EBE; Sun, 1 Dec 2002 04:54:17 -0800 (PST) (envelope-from groudier@free.fr) Received: from [192.168.1.129] (212.232.50.94) by mail.libertysurf.net (6.5.026) id 3DD89CB9003D5CDE; Sun, 1 Dec 2002 13:54:10 +0100 Date: Sun, 1 Dec 2002 14:54:25 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: groudier@localhost.my.domain To: Peter Much Cc: freebsd-scsi@FreeBSD.ORG, , Subject: Re: Getting SCSI Scanner to work (with Symbios 53c810a and FreeBSD 4.4) In-Reply-To: <200212010221.gB12LZk02947@disp.oper.dinoex.org> Message-ID: <20021201142316.K2519-100000@localhost.my.domain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 1 Dec 2002, Peter Much wrote: > Keywords: FreeBSD SANE Scanner Mustek SCSI MFS-6000CX synchronous disable= Symbios 53c810a > > Just for the records, or: to whom it may concern. > > This is what I had to do to get a scsi scanner to work. I post it > here so others having a similar problem may get inspired. > > I got some Mustek MFS-6000CX. The SANE docs say this scanner > will not run synchronous scsi transfers and will not disconnect/ > reconnect. Such simplistic SCSI devices always surprise me a lot. :) > The Qlogic 1020 controller does not detect it, but instead it will > hang infinitely at biosboot. > > The WD7000 controller will detect it, but either it does not report > it to the host, or the FreeBSD driver does not recognize it. I did > not check this further, as this ISA controller is rather outdated > (although it likely might be good enough for a scanner). And seem to have surprised other SCSI people too. :) > The Symbios 53c810a will detect the scanner at biosboot as an > asynchronous scsi device, and also FreeBSD detects it as devicetype > "Scanner" when looking for devices. But it is not possible > to send any scsi command (like tur, inquiry, etc.) to the scanner; > none will be answered. > > Modifying parameters with "camcontrol negotiate" does not help. > > The scanner will be lost at "camcontrol rescan" and will never be > detected again until system reboot. > > Each time a scsi command is issued to the scanner, there will be > no answer, but a kernel error message is logged: > > /kernel: (probe5:sym0:0:6:0): phase change 6-7 6@07c5bf8c resid=3D5. > > ------------------------------------------------------------------- > > I investigated the source of the Symbios driver and found out: > It is not possible to switch off synchronous transfer negotiation > for a device. There is a variable named "period" in the source, > and it is set to 25, and it has to do something with synchronous > transfer. Indeed it has to do. This value is set for USER SETTINGS. As your controller hasn't NVRAM, the driver sets it to the capability of the controller. The driver doesn't try to negotiate by itself but wait either for a negotiation from the device, or for CAM to say that transfer settings must be changed. If your device reports its uncapabilities ;) to CAM correctly by the INQUIRY response, CAM should tell the driver that transfer settings are sync_period=3D0 and sync_offset=3D0. If you can display the INQUIRY data of the device, we could check at least that the device didn't confuse CAM by reporting features it doesn't want to support. Anyway, the sym driver code let me think that it will not behave correctly in such situation. The issue is that the driver will scale the new transfer setting values against controller capabilities without considering that period=3D0 means asynchronous, and thus fall back to 25. You may try this tiny patch. Even if there is a couple of other places where the equivalent change has to be done, this one-liner has chance to also make the driver work with your scanner. You may let me know. --- sym_hipd.c.orig=09Sun Dec 2 20:01:10 2001 +++ sym_hipd.c=09Sun Dec 1 14:42:44 2002 @@ -8791,7 +8791,7 @@ =09=09=09tip->offset =3D np->maxoffs_dt; =09} =09else { -=09=09if (tip->period < np->minsync) +=09=09if (tip->period !=3D 0 && tip->period < np->minsync) =09=09=09tip->period =3D np->minsync; =09=09if (tip->period > np->maxsync) =09=09=09tip->period =3D np->maxsync; ------------- CUT HERE --------------- Thanks for your report. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 1 6:52:36 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9336537B404; Sun, 1 Dec 2002 06:52:34 -0800 (PST) Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DA0043E88; Sun, 1 Dec 2002 06:52:34 -0800 (PST) (envelope-from groudier@free.fr) Received: from [192.168.1.129] (212.232.50.94) by mail.libertysurf.net (6.5.026) id 3DCA8A7A006B5D9F; Sun, 1 Dec 2002 15:52:27 +0100 Date: Sun, 1 Dec 2002 16:52:40 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: groudier@localhost.my.domain To: Peter Much Cc: freebsd-scsi@FreeBSD.ORG, , Subject: Re: Getting SCSI Scanner to work (with Symbios 53c810a and FreeBSD 4.4) In-Reply-To: <200212010221.gB12LZk02947@disp.oper.dinoex.org> Message-ID: <20021201163916.O195-100000@localhost.my.domain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi Peter, You may ignore my previous minute patch and give a try with the below one. It makes more sense to ignore the period (synchronous period factor) when the offset (REQ/ACK offset) is zero, facing synchronous data transfer negotiation in SCSI. Even if the period should be ignored by SCSI devices when the offset is zero, I would prefer the driver to behave correctly by design here (i.e.: ignore the period value when offset is zero). The below patch just does so in the 2 places the driver checks against a needed sync. negotiation. Btw, I would consider as broken any SCSI code that makes decision about data transfer being asynchronous on period value =3D 0. ;-) --- sym_hipd.c.021201=09Sun Dec 1 16:09:55 2002 +++ sym_hipd.c=09Sun Dec 1 16:13:23 2002 @@ -3074,8 +3074,9 @@ =09/* =09 * negotiate synchronous transfers? =09 */ -=09else if (tp->tinfo.current.period !=3D tp->tinfo.goal.period || -=09=09 tp->tinfo.current.offset !=3D tp->tinfo.goal.offset) +=09else if (tp->tinfo.current.offset !=3D tp->tinfo.goal.offset || +=09=09 (tp->tinfo.goal.offset && +=09=09 tp->tinfo.current.period !=3D tp->tinfo.goal.period)) =09=09nego =3D NS_SYNC; =09switch (nego) { @@ -7838,8 +7839,9 @@ =09 */ =09cp->nego_status =3D 0; =09if (tp->tinfo.current.width !=3D tp->tinfo.goal.width || -=09 tp->tinfo.current.period !=3D tp->tinfo.goal.period || =09 tp->tinfo.current.offset !=3D tp->tinfo.goal.offset || +=09 (tp->tinfo.goal.offset && +=09 tp->tinfo.current.period !=3D tp->tinfo.goal.period)|| =09 tp->tinfo.current.options !=3D tp->tinfo.goal.options) { =09=09if (!tp->nego_cp && lp) =09=09=09msglen +=3D sym_prepare_nego(np, cp, 0, msgptr + msglen); ------------------------ CUT HERE ------------------------ Let me know if this patch makes the driver work with your asynchronous-only SCSI scanner. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 1 9:37:24 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B620E37B401; Sun, 1 Dec 2002 09:37:22 -0800 (PST) Received: from smart.eusc.inter.net (smart.eusc.inter.net [213.73.101.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13A2D43EB2; Sun, 1 Dec 2002 09:37:22 -0800 (PST) (envelope-from msch@snafu.de) Received: from tc01-n71-112.de.inter.net ([213.73.71.112] helo=current.best-eng.de) by smart.eusc.inter.net with esmtp (Exim 3.36 #4) id 18IY1r-0003Ro-00; Sun, 01 Dec 2002 18:37:15 +0100 Content-Type: text/plain; charset="iso-8859-15" From: Matthias Schuendehuette Reply-To: msch@snafu.de Organization: Micro$oft-free Zone To: freebsd-scsi@freebsd.org Subject: cdrecord/SCSI problems Date: Sun, 1 Dec 2002 18:37:14 +0100 User-Agent: KMail/1.4.3 Cc: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200212011837.14584.msch@snafu.de> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, I just found problems writing audio-CDs under -current . These problems don't occur writing ISO-(Data-)files nor do they occur writing audio-CDs or Data-iso-files under -STABLE. I append the standard-output of the 'cdrecord'-command below, SCSI-Controller is a LSI Logic U-SCSI model using the sym-driver. 'dmesg | grep sym1' says: sym1: <875> port 0xe000-0xe0ff mem 0xe3003000-0xe3003fff,0xe3002000-0xe30020ff irq 15 at device 10.0 on pci0 sym1: Symbios NVRAM, ID 7, Fast-20, SE, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: SCAN AT BOOT disabled for targets 8 9 10 11 12 13 14 15. sym1: SCAN FOR LUNS disabled for targets 0 1 2 3 4 5 6 8 9 10 11 12 13 14 15. (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. sa0 at sym1 bus 0 target 4 lun 0 da4 at sym1 bus 0 target 0 lun 0 cd1 at sym1 bus 0 target 5 lun 0 cd0 at sym1 bus 0 target 3 lun 0 ... where 'cd1' is the YAMAHA CRW4416 drive. And here is the cdrecord-session: root@current - /raid/audio/tmp 111 # cdrecord -dummy dev=1,5,0 -dao -useinfo -text *.wav pregap1: -1 Cdrecord 1.11a39 (i386-unknown-freebsd5.0) Copyright (C) 1995-2002 Jörg Schilling scsidev: '1,5,0' scsibus: 1 target: 5 lun: 0 Using libscg version 'schily-0.7' Device type : Removable CD-ROM Version : 2 Response Format: 2 Capabilities : SYNC Vendor_info : 'YAMAHA ' Identifikation : 'CRW4416S ' Revision : '1.0j' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : MMC SWABAUDIO Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R96R Starting to write CD/DVD at speed 4 in dummy SAO mode for single session. Last chance to quit, starting dummy write 0 seconds. Operation starts. SAO startsec: -11615 cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error CDB: 2A 00 FF FF D2 A1 00 02 9A 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 21 00 00 00 00 00 00 00 00 00 00 08 00 00 00 00 00 00 08 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x21 Qual 0x00 (logical block address out of range) Fru 0x0 Sense flags: Blk 0 (not valid) resid: 63936 cmd finished after 0.003s timeout 200s write CD-Text data: error after 0 bytes cdrecord: Could not write Lead-in. Are these error messages of any use for anybody? -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 5.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 1 11:34:52 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6351F37B401 for ; Sun, 1 Dec 2002 11:34:51 -0800 (PST) Received: from webspacesolutions.com (ns.webspacesolutions.com [64.29.20.190]) by mx1.FreeBSD.org (Postfix) with SMTP id AD22443E9C for ; Sun, 1 Dec 2002 11:34:50 -0800 (PST) (envelope-from ntwaddel@webspacesolutions.com) Received: (qmail 20222 invoked from network); 1 Dec 2002 19:34:50 -0000 Received: from 24-205-226-59.ata-cres.charterpipeline.net (HELO beastie) (24.205.226.59) by webspacesolutions.com with SMTP; 1 Dec 2002 19:34:50 -0000 From: "Nick Twaddell" To: Subject: ServeRAID 4Lx SCSI RAID Controller Date: Sun, 1 Dec 2002 10:34:52 -0800 Organization: WebSpaceSolutions Message-ID: <000a01c29968$56f301d0$0700a8c0@beastie> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have an IBM rack mount server with an IBM ServeRAID 4Lx SCSI RAID Controller. I downloaded the FreeBSD 4.7 ISO, but I don't think it supports the card because it shows up as an unknown device on boot up. On http://www.tux.org/pub/bsd/freebsd/FreeBSD-current/src/share/misc/pci_ve ndors It lists the card as 020E ServeRAID 4Lx SCSI RAID Controller Is this only in FreeBSD -current possibly? The raid is going to be my boot up device, so I will need to make a bootable cd of -current. Is there an easy way to do this? What does everyone recommend? Thanks Nick Twaddell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 1 13:26:18 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EE7737B401 for ; Sun, 1 Dec 2002 13:26:17 -0800 (PST) Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE09743EBE for ; Sun, 1 Dec 2002 13:26:16 -0800 (PST) (envelope-from Scott_Long@adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6+Sun/8.11.6) with ESMTP id gB1LQFj15596; Sun, 1 Dec 2002 13:26:16 -0800 (PST) Received: from OTCEXC01.otc.adaptec.com (otcexc01.otc.adaptec.com [10.12.1.27]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id NAA07166; Sun, 1 Dec 2002 13:26:04 -0800 (PST) Received: by otcexc01.otc.adaptec.com with Internet Mail Service (5.5.2653.19) id <4TQCX7WA>; Sun, 1 Dec 2002 16:26:03 -0500 Message-ID: <6100BCEB85F8E244959C756C04E0EDD161CBC4@otcexc01.otc.adaptec.com> From: "Long, Scott" To: "'Nick Twaddell'" , freebsd-scsi@FreeBSD.ORG Subject: RE: ServeRAID 4Lx SCSI RAID Controller Date: Sun, 1 Dec 2002 16:25:55 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > I have an IBM rack mount server with an IBM ServeRAID 4Lx SCSI RAID > Controller. I downloaded the FreeBSD 4.7 ISO, but I don't think it > supports the card because it shows up as an unknown device on boot up. > On > > http://www.tux.org/pub/bsd/freebsd/FreeBSD-current/src/share/m > isc/pci_ve > ndors > > It lists the card as > 020E ServeRAID 4Lx SCSI RAID Controller > > Is this only in FreeBSD -current possibly? > > The raid is going to be my boot up device, so I will need to make a > bootable cd of -current. Is there an easy way to do this? What does > everyone recommend? > > Thanks > > Nick Twaddell > There is no ServeRAID driver in FreeBSD yet. I have a driver provided by the ServeRAID guys, and I'm working on polishing it off and making it work in -current. I'll make an announcement once it's ready for testing. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 1 16: 1:37 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 590EA37B401 for ; Sun, 1 Dec 2002 16:01:36 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id E31A343E4A for ; Sun, 1 Dec 2002 16:01:35 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 2078 invoked by uid 1000); 2 Dec 2002 00:01:37 -0000 Date: Sun, 1 Dec 2002 16:01:37 -0800 (PST) From: Nate Lawson To: Dan Langille Cc: bugs@FreeBSD.org, scsi@FreeBSD.org Subject: Re: kern/45324 - 4.7 kernel does not find aha In-Reply-To: <20021130141747.C27627-100000@m20.unixathome.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 30 Nov 2002, Dan Langille wrote: > re: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/45324 > > Can you think of any additional information which would help to diagnose > this problem? I'd like to move this server to 4.7, but it does not > recognize the onboard SCSI which 4.6 did. > > Clues please. > > cheers I looked at the aha code and nothing changed there so the problem is likely elsewhere, prolly in the ISA pnp code. Please ask on stable@. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 1 16:59:18 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87D2D37B417 for ; Sun, 1 Dec 2002 16:59:17 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 4CA4543ECF for ; Sun, 1 Dec 2002 16:59:16 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 2285 invoked by uid 1000); 2 Dec 2002 00:59:17 -0000 Date: Sun, 1 Dec 2002 16:59:17 -0800 (PST) From: Nate Lawson To: Yar Tikhiy Cc: freebsd-scsi@freebsd.org Subject: Re: {da,sa,...}open bug? In-Reply-To: <20021129223817.D34288@comp.chem.msu.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 29 Nov 2002, Yar Tikhiy wrote: > On Mon, Nov 25, 2002 at 12:10:14PM -0800, Nate Lawson wrote: > > On Mon, 25 Nov 2002, Yar Tikhiy wrote: > > > > > While preparing the fix, I noticed an additional couple of oddities. > > > First, files under sys/cam/scsi are inconsistent as to the order of > > > calling cam_periph_release() and cam_periph_unlock(): Some of them > > > will call cam_periph_release() first, and the others will call it second. > > > Then, there's a number of places in the code where cam_periph_unlock() > > > won't be called before return on a cam_periph_acquire() error, though > > > the "periph" has been locked. > > > > I think this should be fixed. Please submit a patch for this. > > Here it is. It a) reorders unlock()'s and release()'s where > necessary, b) adds missing unlock()'s, and finally c) changes > "return(error)" to "return(0)" where "error" will be always 0. > The latter is essentially a style fix, but it is important > WRT the discussed necessity to release a peripheral on errors. > Having no "if (error) cam_periph_release(periph)" before such > returns would be confusing. > > To Nate: If the patch looks good to you, please just say OK, and > I'll do the dirty work of obtaining the high approval and committing. patch looks good to me. pls run past ken@ to get a 2nd opinion and re@ for commit approval. mfc after 1 week. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 2 3:38:24 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7F9737B401 for ; Mon, 2 Dec 2002 03:38:22 -0800 (PST) Received: from rly-ip03.mx.aol.com (rly-ip03.mx.aol.com [64.12.138.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id A241F43EB2 for ; Mon, 2 Dec 2002 03:38:21 -0800 (PST) (envelope-from danielgeske@gmx.net) Received: from logs-mtc-ta.proxy.aol.com (logs-mtc-ta.proxy.aol.com [64.12.105.5]) by rly-ip03.mx.aol.com (v89.10) with ESMTP id RELAYIN1-1202063745; Mon, 02 Dec 2002 06:37:45 1900 Received: from Bowman (ACA23663.ipt.aol.com [172.162.54.99]) by logs-mtc-ta.proxy.aol.com (8.10.0/8.10.0) with ESMTP id gB2BbCq137675; Mon, 2 Dec 2002 06:37:13 -0500 (EST) From: "Daniel Geske" To: , "'Daniel Geske'" Cc: Subject: RE: fsck: PLEASE RERUN FSCK - does not fix problem :-( Date: Mon, 2 Dec 2002 12:34:15 +0100 Organization: - Message-ID: <000001c299f6$c7341900$a52efea9@Bowman> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: <20021130133520.GA83659@walton.maths.tcd.ie> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Apparently-From: BigOnLRAR@aol.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi David, I checked all my drives 1) if AWRE = 1 and ARRE = 1 Result: enabled on all 2) for defects Result: no defects on any drive. Now, the information on that drive is somewhat valuable to me. Interestingly, fsck shows me the number and overall size of the files the slice contains. So the files are still there. Can they be made accessible? How can I mount the filesystem without cleaning it, so I can copy the good files before wiping the slice? Normally, mount on a dirty disk gives "Operation not permitted". Is there a way to manually mark the fs clean? Greetings Daniel > -----Original Message----- > From: dwmalone@maths.tcd.ie [mailto:dwmalone@maths.tcd.ie] > Sent: Saturday, November 30, 2002 2:35 PM > To: Daniel Geske > Cc: 'Daniel Geske'; freebsd-scsi@FreeBSD.ORG > Subject: Re: fsck: PLEASE RERUN FSCK - does not fix problem :-( > > > On Sat, Nov 30, 2002 at 12:29:20PM +0100, Daniel Geske wrote: > > Thanks for your reply. Is there anything I can do like make > the disk > > skip the bad parts and keep on using the parts that are still good? > > As I unserstand it, the "MEDIUM ERROR" is the disk saying > that it tried to read the requested block, but couldn't. SCSI > Drives should be clever enough to be able to map these blocks > to spare blocks elsewhere on the disk, but this remapping can > only be done on a write. (This is usually enabeled by > default, but you may need to enable it with camcontrol.) > > So, if the information on the disk isn't too important you > can try rewriting the sectors on the disk to get the disk to > remap them. Something like "dd if=/dev/zero of=/dev/da1" > should work, but remember it will wipe the information on the disk. > > While this often works, if the disk is going bad you find > that it will quickly reach a state where you are loosing > blocks often enough that the disk is useless and you're > better off buying a new one. > > (On our busier disks we probably see one or two blocks go bad > a month, as shown by "camcontrol defects daX". Disks that are > going bad any faster than that should be backed up before they die...) > > David. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 2 11: 2: 2 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFD9D37B404 for ; Mon, 2 Dec 2002 11:01:59 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 669AA43E4A for ; Mon, 2 Dec 2002 11:01:59 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id gB2J1xx3030696 for ; Mon, 2 Dec 2002 11:01:59 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id gB2J1wci030690 for scsi@freebsd.org; Mon, 2 Dec 2002 11:01:58 -0800 (PST) Date: Mon, 2 Dec 2002 11:01:58 -0800 (PST) Message-Id: <200212021901.gB2J1wci030690@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: scsi@FreeBSD.org Subject: Current problem reports assigned to you Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [2002/02/18] kern/35082 scsi IBM Intellistation will not reboot with S 1 problem total. Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [1999/12/21] kern/15608 scsi acd0 / cd0 give inconsistent errors on em 1 problem total. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 2 14:20:27 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45B8537B407 for ; Mon, 2 Dec 2002 14:20:24 -0800 (PST) Received: from russell.hamline.edu (russell.hamline.edu [138.192.24.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52F7143EEC for ; Mon, 2 Dec 2002 14:20:17 -0800 (PST) (envelope-from rjohanne@piper.hamline.edu) Received: from piper.hamline.edu (piper.hamline.edu [138.192.2.101]) by russell.hamline.edu (8.11.6+Sun/8.11.6) with ESMTP id gB2MJxD04734; Mon, 2 Dec 2002 16:20:00 -0600 (CST) Received: from mendeleev.hamline.edu (mendeleev [138.192.2.109]) by piper.hamline.edu (8.12.6/8.12.6) with ESMTP id gB2MK4aP006937; Mon, 2 Dec 2002 16:20:05 -0600 (CST) Received: from localhost (rjohanne@localhost) by mendeleev.hamline.edu (8.9.1b+Sun/8.9.1) with ESMTP id QAA28697; Mon, 2 Dec 2002 16:18:34 -0600 (CST) X-Authentication-Warning: mendeleev.hamline.edu: rjohanne owned process doing -bs Date: Mon, 2 Dec 2002 16:18:34 -0600 (CST) From: Robert Johannes X-X-Sender: rjohanne@mendeleev.hamline.edu To: Daniel Geske Cc: freebsd-scsi@FreeBSD.ORG Subject: RE: fsck: PLEASE RERUN FSCK - does not fix problem :-( In-Reply-To: <000001c299f6$c7341900$a52efea9@Bowman> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Have you tried mounting it read-only? That's worked for me lately when I couldn't mount a filesystem because it was 'dirty'. mount -o ro /dev/dxxxx /mnt robert On Mon, 2 Dec 2002, Daniel Geske wrote: > Hi David, > > I checked all my drives > 1) if AWRE = 1 and ARRE = 1 > Result: enabled on all > 2) for defects > Result: no defects on any drive. > > Now, the information on that drive is somewhat valuable to me. > Interestingly, fsck shows me the number and overall size of the files > the slice contains. > So the files are still there. Can they be made accessible? > How can I mount the filesystem without cleaning it, so I can copy the > good files before wiping the slice? > Normally, mount on a dirty disk gives "Operation not permitted". Is > there a way to manually mark the fs clean? > > Greetings > > Daniel > > > -----Original Message----- > > From: dwmalone@maths.tcd.ie [mailto:dwmalone@maths.tcd.ie] > > Sent: Saturday, November 30, 2002 2:35 PM > > To: Daniel Geske > > Cc: 'Daniel Geske'; freebsd-scsi@FreeBSD.ORG > > Subject: Re: fsck: PLEASE RERUN FSCK - does not fix problem :-( > > > > > > On Sat, Nov 30, 2002 at 12:29:20PM +0100, Daniel Geske wrote: > > > Thanks for your reply. Is there anything I can do like make > > the disk > > > skip the bad parts and keep on using the parts that are still good? > > > > As I unserstand it, the "MEDIUM ERROR" is the disk saying > > that it tried to read the requested block, but couldn't. SCSI > > Drives should be clever enough to be able to map these blocks > > to spare blocks elsewhere on the disk, but this remapping can > > only be done on a write. (This is usually enabeled by > > default, but you may need to enable it with camcontrol.) > > > > So, if the information on the disk isn't too important you > > can try rewriting the sectors on the disk to get the disk to > > remap them. Something like "dd if=/dev/zero of=/dev/da1" > > should work, but remember it will wipe the information on the disk. > > > > While this often works, if the disk is going bad you find > > that it will quickly reach a state where you are loosing > > blocks often enough that the disk is useless and you're > > better off buying a new one. > > > > (On our busier disks we probably see one or two blocks go bad > > a month, as shown by "camcontrol defects daX". Disks that are > > going bad any faster than that should be backed up before they die...) > > > > David. > > > > > 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 Mon Dec 2 14:46: 4 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4A1837B401 for ; Mon, 2 Dec 2002 14:46:03 -0800 (PST) Received: from alpha.zavood.ee (alpha.zavood.ee [213.168.28.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10E1543EA9 for ; Mon, 2 Dec 2002 14:46:03 -0800 (PST) (envelope-from mario@zavood.ee) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by alpha.zavood.ee (Postfix) with ESMTP id 02E8D6365DF for ; Tue, 3 Dec 2002 00:45:56 +0200 (EET) Received: from alpha.zavood.ee (localhost.localdomain [127.0.0.1]) by localhost.localdomain (AvMailGate-2.0.1.9) id 24663-3BD617E8; Tue, 03 Dec 2002 00:45:25 +0200 Received: from beta (beta.zavood.ee [192.168.0.2]) by alpha.zavood.ee (Postfix) with ESMTP id B6DC16365DF for ; Tue, 3 Dec 2002 00:45:24 +0200 (EET) From: "Mario R. Pizzolanti" To: Subject: Problem installing Freebsd 4.7 Date: Tue, 3 Dec 2002 00:45:26 +0200 Organization: =?us-ascii?Q?Zavood_OU?= Message-ID: <000201c29a54$82678d30$0200a8c0@beta> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-AntiVirus: checked by AntiVir MailGate (version: 2.0.1.9; AVE: 6.16.0.0; VDF: 6.16.0.22; host: alpha.zavood.ee) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi! I'm having trouble installing FreeBSD v. 4.7 on a Mylex Acceleraid 160 (170LP) array. The install disk gives an error pci0 Unknown device Vendor (0x1069) dev (0x0050) IRQ 11 The card is installed on a Tyan S2469 motherboard. The firmware on the Mylex adaptor is 7.01-00 I also had a problem installing Linux Mandrake. The install works: I can partition the array logical drives, etc., but I am unable to bootup the installed system. The error it gives me is: "No boot signature in partition" Any help would be deeply appreciated :) Thanx, ______________________________ Mario R. Pizzolanti To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 2 17:12:46 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E211637B401 for ; Mon, 2 Dec 2002 17:12:44 -0800 (PST) Received: from ws1-2.us4.outblaze.com (205-158-62-54.outblaze.com [205.158.62.54]) by mx1.FreeBSD.org (Postfix) with SMTP id CEC3743EB2 for ; Mon, 2 Dec 2002 17:12:38 -0800 (PST) (envelope-from gadothaah@programmer.net) Received: (qmail 83657 invoked by uid 1001); 3 Dec 2002 01:12:23 -0000 Message-ID: <20021203011223.83656.qmail@mail.com> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [195.206.60.5] by ws1-2.us4.outblaze.com with http for gadothaah@programmer.net; Mon, 02 Dec 2002 20:12:22 -0500 From: "Vadim Stanovov" To: scsi@freebsd.org Cc: mario@zavood.ee Date: Mon, 02 Dec 2002 20:12:22 -0500 Subject: Re: Problem installing Freebsd 4.7 X-Originating-Ip: 195.206.60.5 X-Originating-Server: ws1-2.us4.outblaze.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Mario R. Pizzolanti wrote: > Hi! > I'm having trouble installing FreeBSD v. 4.7 on a Mylex Acceleraid 160 > (170LP) array. > The install disk gives an error pci0 Unknown device Vendor (0x1069) dev > (0x0050) IRQ 11 > The card is installed on a Tyan S2469 motherboard. The firmware on the > Mylex adaptor is 7.01-00 > > I also had a problem installing Linux Mandrake. > The install works: I can partition the array logical drives, etc., but > I am unable to bootup the installed system. > The error it gives me is: "No boot signature in partition" > > Any help would be deeply appreciated :) > > Thanx, > ______________________________ > Mario R. Pizzolanti Hi! Look at open PR i386/45383 http://www.freebsd.org/cgi/query-pr.cgi?pr=45383 And ask bmah@acm.org include mly driver back to install kernel. -- Vadim Stanovov -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup One click access to the Top Search Engines http://www.exactsearchbar.com/mailcom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 2 17:36: 0 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36F7837B401 for ; Mon, 2 Dec 2002 17:36:00 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id BB1E943E4A for ; Mon, 2 Dec 2002 17:35:56 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 5643 invoked by uid 1000); 3 Dec 2002 01:35:58 -0000 Date: Mon, 2 Dec 2002 17:35:58 -0800 (PST) From: Nate Lawson To: scsi@FreeBSD.org Subject: Re: Current problem reports assigned to you In-Reply-To: <200212021901.gB2J1wci030690@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 2 Dec 2002, FreeBSD bugmaster wrote: > Non-critical problems > S Submitted Tracker Resp. Description > ------------------------------------------------------------------------------- > f [1999/12/21] kern/15608 scsi acd0 / cd0 give inconsistent errors on em Ken, Did you and bde work this out enough to close it? -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 2 18:14:17 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D97737B401; Mon, 2 Dec 2002 18:14:16 -0800 (PST) Received: from alpha.zavood.ee (alpha.zavood.ee [213.168.28.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 538BB43E88; Mon, 2 Dec 2002 18:14:15 -0800 (PST) (envelope-from mario@zavood.ee) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by alpha.zavood.ee (Postfix) with ESMTP id 3BB646365DF; Tue, 3 Dec 2002 04:14:07 +0200 (EET) Received: from alpha.zavood.ee (localhost.localdomain [127.0.0.1]) by localhost.localdomain (AvMailGate-2.0.1.9) id 23560-6A25D59E; Tue, 03 Dec 2002 04:14:03 +0200 Received: from beta (beta.zavood.ee [192.168.0.2]) by alpha.zavood.ee (Postfix) with ESMTP id DB90F6365DF; Tue, 3 Dec 2002 04:13:59 +0200 (EET) From: "Mario R. Pizzolanti" To: , , Subject: Re: i386/45383: Failed installation FreeBSD 4.7-RELEASE and 4.7-STABLE with disks attached to Mylex AcceleRAID 170 Date: Tue, 3 Dec 2002 04:14:02 +0200 Organization: =?us-ascii?Q?Zavood_OU?= Message-ID: <001901c29a71$a64fba20$0200a8c0@beta> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-AntiVirus: checked by AntiVir MailGate (version: 2.0.1.9; AVE: 6.16.0.0; VDF: 6.16.0.22; host: alpha.zavood.ee) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi! It seems that the install.htm for both 4.62 and 4.7 has an error. It says: 4.3.21. When I install onto a drive managed by a Mylex PCI RAID controller, the system fails to boot (eg. with a read error message). There is a bug in the Mylex driver which results in it ignoring the ``8GB'' geometry mode setting in the BIOS. Use the 2GB mode instead. Actually, when using 2GB geometry, the install gives a "no disks found" error. Using 8GB geometry, install for 4.62 worked without any problems. Btw, the controller in question is a Mylex Acceleraid 160 (170LP) ;) In amy case, many thanx for your help! Bol'shoje spasibo :) ______________________________ Mario R. Pizzolanti To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 2 18:15:19 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3615237B401 for ; Mon, 2 Dec 2002 18:15:18 -0800 (PST) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77CEF43EB2 for ; Mon, 2 Dec 2002 18:15:17 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.5/8.12.5) with ESMTP id gB32FGKD028692; Mon, 2 Dec 2002 19:15:16 -0700 (MST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.5/8.12.5/Submit) id gB32FGUf028691; Mon, 2 Dec 2002 19:15:16 -0700 (MST) (envelope-from ken) Date: Mon, 2 Dec 2002 19:15:16 -0700 From: "Kenneth D. Merry" To: Nate Lawson Cc: scsi@FreeBSD.ORG Subject: Re: Current problem reports assigned to you Message-ID: <20021202191516.A28635@panzer.kdm.org> References: <200212021901.gB2J1wci030690@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from nate@root.org on Mon, Dec 02, 2002 at 05:35:58PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Dec 02, 2002 at 17:35:58 -0800, Nate Lawson wrote: > On Mon, 2 Dec 2002, FreeBSD bugmaster wrote: > > Non-critical problems > > S Submitted Tracker Resp. Description > > ------------------------------------------------------------------------------- > > f [1999/12/21] kern/15608 scsi acd0 / cd0 give inconsistent errors on em > > Ken, > > Did you and bde work this out enough to close it? Not yet. It's still on my to-do list. BDE sent me a big patch, Poul-Henning is going to make the cd(4) driver work with disklabels again, and I've got a large set of patches for the cd(4) driver as well. It'll take a while to work it all out. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 2 22:50:33 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E172C37B401 for ; Mon, 2 Dec 2002 22:50:32 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EA2C43EC2 for ; Mon, 2 Dec 2002 22:50:31 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id HAA26415; Tue, 3 Dec 2002 07:50:02 +0100 (CET) Received: from uriah.heep.sax.de (localhost.heep.sax.de [127.0.0.1]) by uriah.heep.sax.de (8.12.5/8.12.5) with ESMTP id gB36e4I8049029; Tue, 3 Dec 2002 07:40:04 +0100 (MET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.12.5/8.12.5/Submit) id gB36dxms049009; Tue, 3 Dec 2002 07:39:59 +0100 (MET) (envelope-from j) Date: Tue, 3 Dec 2002 07:39:59 +0100 (MET) Message-Id: <200212030639.gB36dxms049009@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <20021130133520.GA83659@walton.maths.tcd.ie> <20021201074308.N15913-100000@hewey.af.speednet.com.au> From: j@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: fsck: PLEASE RERUN FSCK - does not fix problem :-( X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Cc: Andy Farkas Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Andy Farkas wrote: > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da0: 2014MB (4124736 512 byte sectors: 255H 63S/T 256C) Oh, a Quantum drive. See to get rid of it as soon as you can. It might be reliable enough to serve as a big /tmp, but i wouldn't trust it for anything else. Btw., i've got patches for "camcontrol reassign" that would allow to force blocks onto the bad block table. Well, assuming Quantum drives actually implement that SCSI command at all... -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 3 15:58: 2 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BA3537B401 for ; Tue, 3 Dec 2002 15:57:59 -0800 (PST) Received: from rly-ip03.mx.aol.com (rly-ip03.mx.aol.com [64.12.138.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24DA343EC2 for ; Tue, 3 Dec 2002 15:57:58 -0800 (PST) (envelope-from danielgeske@gmx.net) Received: from logs-we.proxy.aol.com (logs-we.proxy.aol.com [205.188.195.5]) by rly-ip03.mx.aol.com (v89.10) with ESMTP id RELAYIN1-1203185710; Tue, 03 Dec 2002 18:57:10 1900 Received: from Bowman (AC85CB3F.ipt.aol.com [172.133.203.63]) by logs-we.proxy.aol.com (8.10.0/8.10.0) with ESMTP id gB3NsPr90114; Tue, 3 Dec 2002 18:54:27 -0500 (EST) From: "Daniel Geske" To: "'Robert Johannes'" Cc: Subject: RE: fsck: PLEASE RERUN FSCK - does not fix problem :-( Date: Wed, 4 Dec 2002 00:51:29 +0100 Organization: - Message-ID: <003201c29b26$ee79d6e0$6ef9a8c0@Bowman> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: X-Apparently-From: BigOnLRAR@aol.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear Robert: Yes, I have now mounted the FS RO to copy my data. Thanks for your tip. Pretty good, I only lost six files. From here, I will continue to investigate the failure and try to fix the problem. Don't really have ideas on how to go on though... I'll have to do some reading before, I guess. Greetings Daniel > -----Original Message----- > From: Robert Johannes [mailto:rjohanne@piper.hamline.edu] > Sent: Monday, December 02, 2002 11:19 PM > To: Daniel Geske > Cc: freebsd-scsi@FreeBSD.ORG > Subject: RE: fsck: PLEASE RERUN FSCK - does not fix problem :-( > > > Have you tried mounting it read-only? That's worked for me > lately when I couldn't mount a filesystem because it was 'dirty'. > > mount -o ro /dev/dxxxx /mnt > > robert > > On Mon, 2 Dec 2002, Daniel Geske wrote: > > > Hi David, > > > > I checked all my drives > > 1) if AWRE = 1 and ARRE = 1 > > Result: enabled on all > > 2) for defects > > Result: no defects on any drive. > > > > Now, the information on that drive is somewhat valuable to me. > > Interestingly, fsck shows me the number and overall size of > the files > > the slice contains. So the files are still there. Can they be made > > accessible? How can I mount the filesystem without cleaning > it, so I > > can copy the good files before wiping the slice? > > Normally, mount on a dirty disk gives "Operation not permitted". Is > > there a way to manually mark the fs clean? > > > > Greetings > > > > Daniel > > > > > -----Original Message----- > > > From: dwmalone@maths.tcd.ie [mailto:dwmalone@maths.tcd.ie] > > > Sent: Saturday, November 30, 2002 2:35 PM > > > To: Daniel Geske > > > Cc: 'Daniel Geske'; freebsd-scsi@FreeBSD.ORG > > > Subject: Re: fsck: PLEASE RERUN FSCK - does not fix problem :-( > > > > > > > > > On Sat, Nov 30, 2002 at 12:29:20PM +0100, Daniel Geske wrote: > > > > Thanks for your reply. Is there anything I can do like make > > > the disk > > > > skip the bad parts and keep on using the parts that are still > > > > good? > > > > > > As I unserstand it, the "MEDIUM ERROR" is the disk saying that it > > > tried to read the requested block, but couldn't. SCSI > Drives should > > > be clever enough to be able to map these blocks to spare blocks > > > elsewhere on the disk, but this remapping can only be done on a > > > write. (This is usually enabeled by default, but you may need to > > > enable it with camcontrol.) > > > > > > So, if the information on the disk isn't too important > you can try > > > rewriting the sectors on the disk to get the disk to remap them. > > > Something like "dd if=/dev/zero of=/dev/da1" should work, but > > > remember it will wipe the information on the disk. > > > > > > While this often works, if the disk is going bad you find that it > > > will quickly reach a state where you are loosing blocks > often enough > > > that the disk is useless and you're better off buying a new one. > > > > > > (On our busier disks we probably see one or two blocks go bad a > > > month, as shown by "camcontrol defects daX". Disks that are going > > > bad any faster than that should be backed up before they die...) > > > > > > David. > > > > > > > > > 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 Tue Dec 3 17: 1:28 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F10DF37B401 for ; Tue, 3 Dec 2002 17:01:26 -0800 (PST) Received: from msgbas1x.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EBFF43E4A for ; Tue, 3 Dec 2002 17:01:26 -0800 (PST) (envelope-from ctuffli@rose.agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id 5D3EA13559 for ; Tue, 3 Dec 2002 17:29:54 -0700 (MST) Received: from rtl.rose.agilent.com (rtl.rose.agilent.com [130.30.179.189]) by relcos2.cos.agilent.com (Postfix) with ESMTP id E6B6272A for ; Tue, 3 Dec 2002 17:29:50 -0700 (MST) Received: from mail.rose.agilent.com (mailsrv@bellhop [130.30.179.19]) by rtl.rose.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.1.0) with ESMTP id QAA23569 for ; Tue, 3 Dec 2002 16:29:49 -0800 (PST) Received: from thegrail (anu.rose.agilent.com [156.140.225.186]) by mail.rose.agilent.com (Netscape Messaging Server 3.6) with ESMTP id AAA629D for ; Tue, 3 Dec 2002 16:29:46 -0800 Received: by thegrail (Postfix, from userid 1001) id 7AA9B849BE; Tue, 3 Dec 2002 16:25:33 -0800 (PST) Date: Tue, 3 Dec 2002 16:25:33 -0800 From: Chuck Tuffli To: freebsd-scsi@freebsd.org Subject: decoding a double fault Message-ID: <20021204002532.GB23841@thegrail.rose.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm developing a CAM driver that works with 4.7-RELEASE and am running into a double fault. The driver is a KLD which loads and then detects a device on the loop. After detecting the device, I ran llama# camcontrol rescan 0:0:0 at which point the system double faults and prints the following on the console Fatal double fault: eip = 0xc0354952 esp = 0xc8b8a000 ebp = 0xc8b8a078 panic: double fault Debugger("panic") 0xc0354952 is the 3rd instruction into the function alltraps (i386/i386/exception.s:222) .globl _alltraps .type _alltraps,@function _alltraps: pushal pushl %ds pushl %es pushl %fs alltraps_with_regs_pushed: The backtrace looks like (kgdb) bt #0 Debugger (msg=0xc03aec3b "panic") at ../../i386/i386/db_interface.c:319 #1 0xc0211ea0 in panic (fmt=0xc03d9cc3 "double fault") at ../../kern/kern_shutdown.c:593 #2 0xc03637c7 in dblfault_handler () at ../../i386/i386/trap.c:1004 and the contents of common_tss in frame #2 are (kgdb) p/x common_tss $1 = {tss_link = 0x0, tss_esp0 = 0xc8b8dff0, tss_ss0 = 0x10, tss_esp1 = 0x0, tss_ss1 = 0x0, tss_esp2 = 0x0, tss_ss2 = 0x0, tss_cr3 = 0x0, tss_eip = 0xc0354952, tss_eflags = 0x10803, tss_eax = 0x0, tss_ecx = 0x0, tss_edx = 0xc8b8a080, tss_ebx = 0xc7e1bee0, tss_esp = 0xc8b8a000, tss_ebp = 0xc8b8a078, tss_esi = 0xc, tss_edi = 0x0, tss_es = 0x10, tss_cs = 0x8, tss_ss = 0x10, tss_ds = 0x10, tss_fs = 0x10, tss_gs = 0x2f, tss_ldt = 0x0, tss_ioopt = 0x680000} Is there enough information from the above to figure out what code was being executed, what address caused the fault, what exception was the OS handling when the fault occured, etc.? Any suggestions, including RTFM, are welcomed as long as you also include which manual I should be reading ;) -- Chuck Tuffli Agilent Technologies, Storage and Networking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 3 23:11:52 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E8EF37B401 for ; Tue, 3 Dec 2002 23:11:51 -0800 (PST) Received: from msgbas1x.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E5C343EAF for ; Tue, 3 Dec 2002 23:11:50 -0800 (PST) (envelope-from yiding_wang@agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id 20D4C136AF for ; Tue, 3 Dec 2002 18:32:09 -0700 (MST) Received: from axcsbh4.cos.agilent.com (axcsbh4.cos.agilent.com [130.29.152.145]) by relcos2.cos.agilent.com (Postfix) with SMTP id E4AB5472 for ; Tue, 3 Dec 2002 18:32:08 -0700 (MST) Received: from 130.29.152.145 by axcsbh4.cos.agilent.com (InterScan E-Mail VirusWall NT); Tue, 03 Dec 2002 18:32:08 -0700 Received: by axcsbh4.cos.agilent.com with Internet Mail Service (5.5.2653.19) id ; Tue, 3 Dec 2002 18:32:08 -0700 Message-ID: <334DD5C2ADAB9245B60F213F49C5EBCD019C7AB5@axcs03.cos.agilent.com> From: yiding_wang@agilent.com To: freebsd-scsi@freebsd.org Subject: Starting questions about FreeBSD PCI scsi driver. Date: Tue, 3 Dec 2002 18:32:07 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello There, This is the first expecrience for me with FreeBSD and I am going to start making fuss here. I am writing a drivers for iSCSI and FC PCI initiator as well as target ramdisk on FreeBSD, and just installed 4.7 and downloaded a few docs. By looking into CVS, I got a few initial questions. I will use Buslogic driver bt.c as an example. For better understanding, any reference to scsi driver under Linux, Unixware. Solaris, SCO OS5 will be welcomed since I have written drivers for scsi / FC / iSCSI under those enviornments. Here comes the first set of question: 1, I noticed that there are a few places drivers are spreaded. For example /sys/dev/buslogic/bt.c, v /sys/dev/buslogic/bt_pci.c, v /sys/dev/buslogic/btreg.h, v and same files and others which cover same hardware are located at: /sys/i386/scsi/Attic/bt.c, v /sys/i386/scsi/Attic/btreg.h, v /sys/pci/Attic/bt9xx.c, v /sys/pci/Attic/bt_pci.c, v etc. Why these drivers are spreaded? If I only have a pci initiator driver, can the source only be located under /sys/dev/vendor instead of also put some part of code under /sys/pci/Attic? 2, Does FreeBSD requires realmode driver to boot? Those bus (EISA, ISA, PCI) related subdirectories look like Solaris realmode driver distribution. 3, Where is proper place for driver source code? If this driver does not intend for a boot device, can it be placed anywhere like other Unixes? 4, There are Makefiles for aic7xxx, e.g. under module, but nothing for bt.c. Does that mean buslogic driver not supporting loadable module? 5, There are utility of "pkg_add" for driver loading, similar to Solaris, and "kldload" for module loading, similar to Linux. Can I assume both methods work for scsi driver. The difference will be kldload works only for this boot and module will be gone after "kldunload" or system reboot, but "pkg_add" will hook driver to kernel from boot to boot till pkg_delete is performed. 6, If driver will be loaded with pkg_add, where are those related package required header files located? 7, Does FreeBSD support multi-initiator? If it does, how the devices are scanned? For example, if I have two card in the system. During the xxx-probe routine, pci_get_devid(dev) is called. Is this function being called once for every card by kernel or driver needs to call the function multi times to discover those cards? 8, If driver support character device too, how to determine the major number? Assign it randomly by driver or assigned by kernel and can be retreaved by driver? 9, I don't see detailed driver structure and system function calls from man page as well as handbooks (e.g. pci_get_devid). Where is the best place to get those information? Many thanks! Eddie (Yiding) Wang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 3 23:53:56 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A5F137B401 for ; Tue, 3 Dec 2002 23:53:53 -0800 (PST) Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0C3F43E9C for ; Tue, 3 Dec 2002 23:53:52 -0800 (PST) (envelope-from scottl@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6+Sun/8.11.6) with ESMTP id gB47rpj26259; Tue, 3 Dec 2002 23:53:51 -0800 (PST) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [10.100.0.52]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id XAA08418; Tue, 3 Dec 2002 23:53:40 -0800 (PST) Received: from hollin.btc.adaptec.com (hollin [10.100.253.56]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id AAA17450; Wed, 4 Dec 2002 00:53:39 -0700 (MST) Received: from hollin.btc.adaptec.com (localhost [127.0.0.1]) by hollin.btc.adaptec.com (8.12.6/8.12.5) with ESMTP id gB47olwD000621; Wed, 4 Dec 2002 00:50:47 -0700 (MST) (envelope-from scottl@hollin.btc.adaptec.com) Received: (from scottl@localhost) by hollin.btc.adaptec.com (8.12.6/8.12.5/Submit) id gB47okDq000620; Wed, 4 Dec 2002 00:50:46 -0700 (MST) Date: Wed, 4 Dec 2002 00:50:46 -0700 From: Scott Long To: yiding_wang@agilent.com Cc: freebsd-scsi@freebsd.org Subject: Re: Starting questions about FreeBSD PCI scsi driver. Message-ID: <20021204075046.GA587@hollin.btc.adaptec.com> References: <334DD5C2ADAB9245B60F213F49C5EBCD019C7AB5@axcs03.cos.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <334DD5C2ADAB9245B60F213F49C5EBCD019C7AB5@axcs03.cos.agilent.com> User-Agent: Mutt/1.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Dec 03, 2002 at 06:32:07PM -0700, yiding_wang@agilent.com wrote: > Hello There, > > This is the first expecrience for me with FreeBSD and I am going to start making fuss here. > > I am writing a drivers for iSCSI and FC PCI initiator as well as target ramdisk on FreeBSD, and just installed 4.7 and downloaded a few docs. By looking into CVS, I got a few initial questions. I will use Buslogic driver bt.c as an example. For better understanding, any reference to scsi driver under Linux, Unixware. Solaris, SCO OS5 will be welcomed since I have written drivers for scsi / FC / iSCSI under those enviornments. > > Here comes the first set of question: > > 1, I noticed that there are a few places drivers are spreaded. For example > /sys/dev/buslogic/bt.c, v > /sys/dev/buslogic/bt_pci.c, v > /sys/dev/buslogic/btreg.h, v > > and same files and others which cover same hardware are located at: > /sys/i386/scsi/Attic/bt.c, v > /sys/i386/scsi/Attic/btreg.h, v > /sys/pci/Attic/bt9xx.c, v > /sys/pci/Attic/bt_pci.c, v > etc. You're looking at the CVS RCS files, which are the internal 'database' files for the CVS system. What you need to do is use the 'cvs checkout' command to check the appropriate versions of these files out. Attic directories are part of the CVS database and denote files that have been deleted from the CVS system. There are many guides and books for using CVS, so I suggest doing a simple Google search on CVS and reading up on it. > > Why these drivers are spreaded? > If I only have a pci initiator driver, can the source only be located under /sys/dev/vendor instead of also put some part of code under /sys/pci/Attic? It should be in /sys/dev/ > > 2, Does FreeBSD requires realmode driver to boot? Those bus (EISA, ISA, PCI) related subdirectories look like Solaris realmode driver distribution. No real mode driver is needed. > > 3, Where is proper place for driver source code? If this driver does not intend for a boot device, can it be placed anywhere like other Unixes? /sys/dev/ > > 4, There are Makefiles for aic7xxx, e.g. under module, but nothing for bt.c. Does that mean buslogic driver not supporting loadable module? /sys/modules is the place for makefiles for drivers that can be built as modules. You would put your makefile in /sys/modules/ > > 5, There are utility of "pkg_add" for driver loading, similar to Solaris, and "kldload" for module loading, similar to Linux. Can I assume both methods work for scsi driver. The difference will be kldload works only for this boot and module will be gone after "kldunload" or system reboot, but "pkg_add" will hook driver to kernel from boot to boot till pkg_delete is performed. pkg_add is a tool for installing binary packages onto a system. It is similar to the package system in solaris and the rpm system in linux. pkg_add can contain scripts that do post-install actions, like modifying the the system to cause a driver to be loaded on bootup. kldload is similar to insmod in linux. > > 6, If driver will be loaded with pkg_add, where are those related package required header files located? No header files are needed. See the manual page for pkg_create. > > 7, Does FreeBSD support multi-initiator? If it does, how the devices are scanned? > For example, if I have two card in the system. During the xxx-probe routine, pci_get_devid(dev) is called. Is this function being called once for every card by kernel or > driver needs to call the function multi times to discover those cards? I think that you are confusing the 'multi-initiator' term. Yes, you can have more than one of a certain PCI device in your system. Your driver's probe and attach routines will be called once for each card. The framework that you need to use is called 'newbus'. See the manual pages for 'device' and 'driver'. > > 8, If driver support character device too, how to determine the major number? Assign it randomly by driver or assigned by kernel and can be retreaved by driver? Driver assignments are done in /sys/conf/majors. Once a major number is assigned, the driver is free to assume that it won't change. This will change in the future with DEVFS. > > 9, I don't see detailed driver structure and system function calls from man page as well as handbooks (e.g. pci_get_devid). Where is the best place to get those information? Unfortunately this is not well documented. Several articles have been written in the past and can probably be found by searching the 'articles' section of www.freebsd.org and/or deamonnews.org. You should search for 'newbus' and 'cam'. > > Many thanks! > > Eddie (Yiding) Wang > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 4 7:26:23 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD18737B401 for ; Wed, 4 Dec 2002 07:26:21 -0800 (PST) Received: from msgbas2x.cos.agilent.com (msgbas2x.cos.agilent.com [192.25.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8F5143E4A for ; Wed, 4 Dec 2002 07:26:20 -0800 (PST) (envelope-from ctuffli@rose.agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas2x.cos.agilent.com (Postfix) with ESMTP id A1211159D for ; Wed, 4 Dec 2002 08:26:14 -0700 (MST) Received: from rtl.rose.agilent.com (rtl.rose.agilent.com [130.30.179.189]) by relcos2.cos.agilent.com (Postfix) with ESMTP id AE7E1471 for ; Wed, 4 Dec 2002 08:26:12 -0700 (MST) Received: from mail.rose.agilent.com (mailsrv@bellhop [130.30.179.19]) by rtl.rose.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.1.0) with ESMTP id HAA03512 for ; Wed, 4 Dec 2002 07:26:08 -0800 (PST) Received: from cre85086tuf ([130.30.174.150]) by mail.rose.agilent.com (Netscape Messaging Server 3.6) with ESMTP id AAA2B06; Wed, 4 Dec 2002 07:25:52 -0800 Received: by cre85086tuf (Postfix, from userid 1001) id 859A119DE95; Mon, 2 Dec 2002 17:00:52 -0800 (PST) Date: Mon, 2 Dec 2002 17:00:52 -0800 From: Chuck Tuffli To: freebsd-scsi@FreeBSD.ORG Subject: decoding a double fault Message-ID: <20021203010051.GA96898@cre85086tuf.rose.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm working on a CAM driver for 4.7-RELEASE and am looking for some pointers on figuring out how I caused a double fault. The driver is a KLD and had already been loaded. The command I was executing just before the panic was a camcontrol rescan of the individual devices. Before running rescan, the driver did sucessfully detect 4 devices (This problem doesn't show up if I run rescan manually for each device). smallrocks# while 1 while? smallrocks# foreach d (0 1 2 3) foreach? camcontrol rescan 0:$d\:0 foreach? end Re-scan of 0:0:0 was successful Re-scan of 0:1:0 was successful The info on the terminal after the panic is Fatal double fault: eip = 0xc0371e68 esp = 0xc60aea50 ebp = 0xc612ea7c where 0xc0371e68 is in bus_dmamap_load at line 437 ... vaddr = (vm_offset_t)buf; sg = &dm_segments[0]; seg = 1; sg->ds_len = 0; /* !!! line 437 */ nextpaddr = 0; do { ... The backtrace just shows the fault (kgdb) bt #0 Debugger (msg=0xc03ce15b "panic") at ../../i386/i386/db_interface.c:319 #1 0xc021158c in panic (fmt=0xc03fc7c3 "double fault") at ../../kern/kern_shutdown.c:593 #2 0xc0382f13 in dblfault_handler () at ../../i386/i386/trap.c:1004 In frame #2, the contents of common_tss are (kgdb) p/x common_tss $4 = {tss_link = 0x0, tss_esp0 = 0xc612eff0, tss_ss0 = 0x10, tss_esp1 = 0x0, tss_ss1 = 0x0, tss_esp2 = 0x0, tss_ss2 = 0x0, tss_cr3 = 0x0, tss_eip = 0xc0371e68, tss_eflags = 0x10246, tss_eax = 0xc0d86284, tss_ecx = 0x0, tss_edx = 0xc60aea50, tss_ebx = 0xc0ecc220, tss_esp = 0xc60aea50, tss_ebp = 0xc612ea7c, tss_esi = 0xc0ed0800, tss_edi = 0xc0ed0800, tss_es = 0x10, tss_cs = 0x8, tss_ss = 0x10, tss_ds = 0x10, tss_fs = 0x10, tss_gs = 0x2f, tss_ldt = 0x0, tss_ioopt = 0x680000} Is there enough information from the above to figure out what code was calling bus_dmamap_load, is the fault from a stack overflow or other bad address, etc.? Any comments, including RTFM, are welcomed as long as you mention which manual to read :) -- Chuck Tuffli Agilent Technologies, Storage and Networking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 4 13:22:59 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A448337B401 for ; Wed, 4 Dec 2002 13:22:58 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 574AC43EAF for ; Wed, 4 Dec 2002 13:22:58 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 11043 invoked by uid 1000); 4 Dec 2002 21:22:59 -0000 Date: Wed, 4 Dec 2002 13:22:59 -0800 (PST) From: Nate Lawson To: yiding_wang@agilent.com Cc: freebsd-scsi@freebsd.org Subject: Re: Starting questions about FreeBSD PCI scsi driver. In-Reply-To: <334DD5C2ADAB9245B60F213F49C5EBCD019C7AB5@axcs03.cos.agilent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org use aic7xxx as an example how to write a cam sim driver, not bt. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 4 13:29:46 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AA7237B401 for ; Wed, 4 Dec 2002 13:29:45 -0800 (PST) Received: from webspacesolutions.com (ns.webspacesolutions.com [64.29.20.190]) by mx1.FreeBSD.org (Postfix) with SMTP id EEC3E43EC2 for ; Wed, 4 Dec 2002 13:29:44 -0800 (PST) (envelope-from ntwaddel@webspacesolutions.com) Received: (qmail 12373 invoked from network); 4 Dec 2002 21:29:34 -0000 Received: from 24-205-226-59.ata-cres.charterpipeline.net (HELO beastie) (24.205.226.59) by webspacesolutions.com with SMTP; 4 Dec 2002 21:29:34 -0000 From: "Nick Twaddell" To: Subject: supported devices Date: Wed, 4 Dec 2002 13:29:34 -0800 Organization: WebSpaceSolutions Message-ID: <002601c29bdc$3dd86f20$0700a8c0@beastie> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Are all the devices listed in FreeBSD-current/src/share/misc/pci_vendors supported? Soon to be supported? Or what? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 4 13:36:23 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 847E937B401 for ; Wed, 4 Dec 2002 13:36:22 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC2E743EC2 for ; Wed, 4 Dec 2002 13:36:21 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.3/8.12.3) with ESMTP id gB4LaCh0032072; Wed, 4 Dec 2002 13:36:12 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.3/8.12.3/Submit) id gB4LaBNH032069; Wed, 4 Dec 2002 13:36:11 -0800 Date: Wed, 4 Dec 2002 13:36:11 -0800 From: Brooks Davis To: Nick Twaddell Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: supported devices Message-ID: <20021204133611.B24227@Odin.AC.HMC.Edu> References: <002601c29bdc$3dd86f20$0700a8c0@beastie> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="JYK4vJDZwFMowpUq" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <002601c29bdc$3dd86f20$0700a8c0@beastie>; from ntwaddel@webspacesolutions.com on Wed, Dec 04, 2002 at 01:29:34PM -0800 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --JYK4vJDZwFMowpUq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 04, 2002 at 01:29:34PM -0800, Nick Twaddell wrote: > Are all the devices listed in FreeBSD-current/src/share/misc/pci_vendors > supported? Soon to be supported? Or what? No, it's just a list of every PCI device listed in the two public databases listed at the top of the file. It exists to provide more useful "pciconf -lv" output. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --JYK4vJDZwFMowpUq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE97nVKXY6L6fI4GtQRAggDAJ96jNdZbYhLP08t1BAHOELD03VPOgCgrq1H MUAaN8eNOZbQyu3mp7AdAuM= =SaGq -----END PGP SIGNATURE----- --JYK4vJDZwFMowpUq-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 4 14: 2:23 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4DA337B401 for ; Wed, 4 Dec 2002 14:02:21 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 47D3343E4A for ; Wed, 4 Dec 2002 14:02:21 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 11159 invoked by uid 1000); 4 Dec 2002 22:02:22 -0000 Date: Wed, 4 Dec 2002 14:02:22 -0800 (PST) From: Nate Lawson To: Chuck Tuffli Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: decoding a double fault In-Reply-To: <20021203010051.GA96898@cre85086tuf.rose.agilent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 2 Dec 2002, Chuck Tuffli wrote: > I'm working on a CAM driver for 4.7-RELEASE and am looking for some > pointers on figuring out how I caused a double fault. The driver is a > KLD and had already been loaded. The command I was executing just > before the panic was a camcontrol rescan of the individual devices. > Before running rescan, the driver did sucessfully detect 4 devices > (This problem doesn't show up if I run rescan manually for each device). > > The info on the terminal after the panic is > > Fatal double fault: > eip = 0xc0371e68 > esp = 0xc60aea50 > ebp = 0xc612ea7c > > where 0xc0371e68 is in bus_dmamap_load at line 437 > ... > vaddr = (vm_offset_t)buf; > sg = &dm_segments[0]; > seg = 1; > sg->ds_len = 0; /* !!! line 437 */ > > nextpaddr = 0; > do { > ... Nothing in CAM calls bus_* so you must be calling it. :) isp calls it in its reset routine. async handler problems? > The backtrace just shows the fault > > (kgdb) bt > #0 Debugger (msg=0xc03ce15b "panic") at ../../i386/i386/db_interface.c:319 > #1 0xc021158c in panic (fmt=0xc03fc7c3 "double fault") > at ../../kern/kern_shutdown.c:593 > #2 0xc0382f13 in dblfault_handler () at ../../i386/i386/trap.c:1004 That's because you lost the frame when the fault handler faulted. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 6 3:57:54 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3754137B401 for ; Fri, 6 Dec 2002 03:57:53 -0800 (PST) Received: from comp.chem.msu.su (comp-ext.chem.msu.su [158.250.32.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACF7043EBE for ; Fri, 6 Dec 2002 03:57:50 -0800 (PST) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.12.3/8.12.3) with ESMTP id gB6Bxkg7089026; Fri, 6 Dec 2002 14:59:47 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.12.3/8.12.3/Submit) id gB6BxgQ5089025; Fri, 6 Dec 2002 14:59:42 +0300 (MSK) Date: Fri, 6 Dec 2002 14:59:42 +0300 From: Yar Tikhiy To: Nate Lawson Cc: freebsd-scsi@freebsd.org Subject: Re: {da,sa,...}open bug? Message-ID: <20021206145942.I80257@comp.chem.msu.su> References: <20021129223817.D34288@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from nate@root.org on Sun, Dec 01, 2002 at 04:59:17PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi there, Yet another daopen() issue came to my attention. The DA_OPEN_FLAG bit won't be reset back to 0 if daopen() has failed, thus leaving the device marked as open. Isn't the below patch necessary? The rest of scsi_* modules seem to not have this bug. -- Yar Index: scsi_da.c =================================================================== RCS file: /home/ncvs/src/sys/cam/scsi/scsi_da.c,v retrieving revision 1.116 diff -u -r1.116 scsi_da.c --- scsi_da.c 29 Nov 2002 15:40:10 -0000 1.116 +++ scsi_da.c 6 Dec 2002 11:49:57 -0000 @@ -612,6 +612,7 @@ if ((softc->flags & DA_FLAG_PACK_REMOVABLE) != 0) daprevent(periph, PR_PREVENT); } else { + softc->flags &= ~DA_FLAG_OPEN; cam_periph_release(periph); } cam_periph_unlock(periph); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 6 7:50:52 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3A5D37B401 for ; Fri, 6 Dec 2002 07:50:51 -0800 (PST) Received: from CPE0004761ac738-CM00109515bc65.cpe.net.cable.rogers.com (CPE0004761ac738-CM00109515bc65.cpe.net.cable.rogers.com [24.103.39.131]) by mx1.FreeBSD.org (Postfix) with SMTP id BE69F43EBE for ; Fri, 6 Dec 2002 07:50:50 -0800 (PST) (envelope-from miro@cybershade.us) Received: (qmail 41483 invoked from network); 6 Dec 2002 15:50:34 -0000 Received: from unknown (HELO vsivyoung) (66.46.21.253) by cpe0004761ac738-cm00109515bc65.cpe.net.cable.rogers.com with SMTP; 6 Dec 2002 15:50:34 -0000 Message-ID: <003b01c29d3f$36d69c10$c801a8c0@vsivyoung> From: "Miroslav Pendev" To: "SCSI FreeBSD" Subject: OT: UltraTrac SX8000 SCSI-to-ATA RAID - 1TB Date: Fri, 6 Dec 2002 10:50:25 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, This is OT, I will appreciate all answers. Thanks. I'm going to buy UltraTrak SX 8000 SCSI-to-ATA RAID and it will be connected to FreeBSD 4.6 RELEASE (file server). It is Ultra 160 SCSI and it must appear as standard SCSI device to any OS, but I just would like to ask if there is anybody with SX8000 under FreeBSD with production system, any problems? It will be setup as 8x160GB RAID 5 which means I will almost hit 1TB. Is it good idea to format the whole thing as one slice or not? Can somebody recommend a nice Ultra 160 SCSI card for this thing under FreeBSD? I'm pretty sure any Adaptec U160 can handle it, but... Sorry, for asking too many questions in one email. :-| Thanks in advance! Miroslav Pendev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 6 11: 5:14 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DE8937B401 for ; Fri, 6 Dec 2002 11:05:13 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 2911643EB2 for ; Fri, 6 Dec 2002 11:05:13 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 16126 invoked by uid 1000); 6 Dec 2002 19:05:14 -0000 Date: Fri, 6 Dec 2002 11:05:14 -0800 (PST) From: Nate Lawson To: Miroslav Pendev Cc: SCSI FreeBSD Subject: Re: OT: UltraTrac SX8000 SCSI-to-ATA RAID - 1TB In-Reply-To: <003b01c29d3f$36d69c10$c801a8c0@vsivyoung> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 6 Dec 2002, Miroslav Pendev wrote: > I'm going to buy UltraTrak SX 8000 SCSI-to-ATA RAID and it will > be connected to FreeBSD 4.6 RELEASE (file server). > > It is Ultra 160 SCSI and it must appear as standard SCSI device to > any OS, but I just would like to ask if there is anybody with > SX8000 under FreeBSD with production system, any problems? There are many products like this and I'd be surprised if there was a problem with its SCSI emulation. The question that is more important to me is "are the IDE drives hot swappable?" > It will be setup as 8x160GB RAID 5 which means I will almost hit 1TB. > Is it good idea to format the whole thing as one slice or not? You lose a lot of space if you format that as one volume. > Can somebody recommend a nice Ultra 160 SCSI card for this thing > under FreeBSD? I'm pretty sure any Adaptec U160 can handle it, but... I like the 29160 and have had no problems with it. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 6 11:19:58 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 522CF37B401 for ; Fri, 6 Dec 2002 11:19:57 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id C82BF43EB2 for ; Fri, 6 Dec 2002 11:19:56 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.3/8.12.3) with ESMTP id gB6JJqAm010637; Fri, 6 Dec 2002 11:19:52 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.3/8.12.3/Submit) id gB6JJp7j010635; Fri, 6 Dec 2002 11:19:51 -0800 Date: Fri, 6 Dec 2002 11:19:50 -0800 From: Brooks Davis To: Nate Lawson Cc: Miroslav Pendev , SCSI FreeBSD Subject: Re: OT: UltraTrac SX8000 SCSI-to-ATA RAID - 1TB Message-ID: <20021206111950.D1950@Odin.AC.HMC.Edu> References: <003b01c29d3f$36d69c10$c801a8c0@vsivyoung> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="AbQceqfdZEv+FvjW" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from nate@root.org on Fri, Dec 06, 2002 at 11:05:14AM -0800 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --AbQceqfdZEv+FvjW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 06, 2002 at 11:05:14AM -0800, Nate Lawson wrote: > On Fri, 6 Dec 2002, Miroslav Pendev wrote: > > I'm going to buy UltraTrak SX 8000 SCSI-to-ATA RAID and it will > > be connected to FreeBSD 4.6 RELEASE (file server). > >=20 > > It is Ultra 160 SCSI and it must appear as standard SCSI device to > > any OS, but I just would like to ask if there is anybody with > > SX8000 under FreeBSD with production system, any problems? I've got one with 120GB disks. It works quite well was as the ftp storage for the internal mirror server at work. > > It will be setup as 8x160GB RAID 5 which means I will almost hit 1TB. > > Is it good idea to format the whole thing as one slice or not? >=20 > You lose a lot of space if you format that as one volume. At least with 120GB disks it does work: /dev/da1s1e 789G 441G 285G 61% /mirrors/ftp It looks like we're going to need something better next year though. :-) -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --AbQceqfdZEv+FvjW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE98PhVXY6L6fI4GtQRAvHiAKCGy0nhQYciCiFJvrFdIHNFOGQDogCghxKS UXlr5KPus/Ur8fUknHsVuf4= =tqDC -----END PGP SIGNATURE----- --AbQceqfdZEv+FvjW-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 6 11:23:57 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E88E537B404 for ; Fri, 6 Dec 2002 11:23:55 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 59CA243EC5 for ; Fri, 6 Dec 2002 11:23:55 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 16208 invoked by uid 1000); 6 Dec 2002 19:23:56 -0000 Date: Fri, 6 Dec 2002 11:23:56 -0800 (PST) From: Nate Lawson To: Yar Tikhiy Cc: freebsd-scsi@freebsd.org Subject: Re: {da,sa,...}open bug? In-Reply-To: <20021206145942.I80257@comp.chem.msu.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 6 Dec 2002, Yar Tikhiy wrote: > Yet another daopen() issue came to my attention. The DA_OPEN_FLAG bit > won't be reset back to 0 if daopen() has failed, thus leaving the device > marked as open. Isn't the below patch necessary? > > The rest of scsi_* modules seem to not have this bug. > > -- > Yar > > Index: scsi_da.c > =================================================================== > RCS file: /home/ncvs/src/sys/cam/scsi/scsi_da.c,v > retrieving revision 1.116 > diff -u -r1.116 scsi_da.c > --- scsi_da.c 29 Nov 2002 15:40:10 -0000 1.116 > +++ scsi_da.c 6 Dec 2002 11:49:57 -0000 > @@ -612,6 +612,7 @@ > if ((softc->flags & DA_FLAG_PACK_REMOVABLE) != 0) > daprevent(periph, PR_PREVENT); > } else { > + softc->flags &= ~DA_FLAG_OPEN; > cam_periph_release(periph); > } > cam_periph_unlock(periph); You are correct. Ok to commit this w/ re@ approval The other periphs don't use this flag. There is another important fix that should be made that exists in several other drivers as well: --- scsi_da.c.orig Fri Dec 6 11:07:33 2002 +++ scsi_da.c Fri Dec 6 11:10:44 2002 @@ -545,8 +545,10 @@ if ((error = cam_periph_lock(periph, PRIBIO|PCATCH)) != 0) return (error); /* error code from tsleep */ - if (cam_periph_acquire(periph) != CAM_REQ_CMP) + if (cam_periph_acquire(periph) != CAM_REQ_CMP) { + cam_periph_unlock(periph); return(ENXIO); + } softc->flags |= DA_FLAG_OPEN; if ((softc->flags & DA_FLAG_PACK_INVALID) != 0) { i.e. unlock if locked on return. Can you put together a patch for all of these? Thanks, -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 6 11:34: 6 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E2B537B401; Fri, 6 Dec 2002 11:34:04 -0800 (PST) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25DC443ED8; Fri, 6 Dec 2002 11:34:03 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.6/8.12.5) with ESMTP id gB6JY2nU023317; Fri, 6 Dec 2002 12:34:02 -0700 (MST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.6/8.12.5/Submit) id gB6JY2Cg023316; Fri, 6 Dec 2002 12:34:02 -0700 (MST) (envelope-from ken) Date: Fri, 6 Dec 2002 12:34:01 -0700 From: "Kenneth D. Merry" To: Nate Lawson Cc: Yar Tikhiy , freebsd-scsi@FreeBSD.ORG Subject: Re: {da,sa,...}open bug? Message-ID: <20021206123401.A23249@panzer.kdm.org> References: <20021206145942.I80257@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from nate@root.org on Fri, Dec 06, 2002 at 11:23:56AM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Dec 06, 2002 at 11:23:56 -0800, Nate Lawson wrote: > On Fri, 6 Dec 2002, Yar Tikhiy wrote: > > Yet another daopen() issue came to my attention. The DA_OPEN_FLAG bit > > won't be reset back to 0 if daopen() has failed, thus leaving the device > > marked as open. Isn't the below patch necessary? > > > > The rest of scsi_* modules seem to not have this bug. > > > > -- > > Yar > > > > Index: scsi_da.c > > =================================================================== > > RCS file: /home/ncvs/src/sys/cam/scsi/scsi_da.c,v > > retrieving revision 1.116 > > diff -u -r1.116 scsi_da.c > > --- scsi_da.c 29 Nov 2002 15:40:10 -0000 1.116 > > +++ scsi_da.c 6 Dec 2002 11:49:57 -0000 > > @@ -612,6 +612,7 @@ > > if ((softc->flags & DA_FLAG_PACK_REMOVABLE) != 0) > > daprevent(periph, PR_PREVENT); > > } else { > > + softc->flags &= ~DA_FLAG_OPEN; > > cam_periph_release(periph); > > } > > cam_periph_unlock(periph); > > You are correct. Ok to commit this w/ re@ approval The other periphs > don't use this flag. > > There is another important fix that should be made that exists in several > other drivers as well: > > --- scsi_da.c.orig Fri Dec 6 11:07:33 2002 > +++ scsi_da.c Fri Dec 6 11:10:44 2002 > @@ -545,8 +545,10 @@ > if ((error = cam_periph_lock(periph, PRIBIO|PCATCH)) != 0) > return (error); /* error code from tsleep */ > > - if (cam_periph_acquire(periph) != CAM_REQ_CMP) > + if (cam_periph_acquire(periph) != CAM_REQ_CMP) { > + cam_periph_unlock(periph); > return(ENXIO); > + } > softc->flags |= DA_FLAG_OPEN; > > if ((softc->flags & DA_FLAG_PACK_INVALID) != 0) { > > i.e. unlock if locked on return. Can you put together a patch for all of > these? Yar asked me to review his previous patch to a number of peripheral drivers that modifed the acquire/unlock/etc. order. I've asked Justin to take a look at it as well (thus the reason I haven't completed the review yet), but what you have above will likely cause a panic. cam_periph_acquire() only returns an error when periph == NULL. If, for some wild reason, a locked periph manages to get freed (thus causing cam_periph_acquire() to return CAM_REQ_CMP_ERR), cam_periph_unlock() will panic (NULL pointer deference) when called with a NULL periph. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message