From owner-freebsd-scsi Mon Jul 1 13: 5: 8 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 0565437B400 for ; Mon, 1 Jul 2002 13:05:06 -0700 (PDT) Received: from moutvdomng0.schlund.de (moutvdomng0.kundenserver.de [195.20.224.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD94243E09 for ; Mon, 1 Jul 2002 13:05:04 -0700 (PDT) (envelope-from ai@duettra.de) Received: from [172.19.20.62] (helo=mrvdomng1.kundenserver.de) by moutvdomng0.schlund.de with esmtp (Exim 3.22 #2) id 17P7Pz-0005TG-00 for freebsd-scsi@freebsd.org; Mon, 01 Jul 2002 22:05:03 +0200 Received: from [80.131.205.167] (helo=duettra.de) by mrvdomng1.kundenserver.de with esmtp (Exim 3.22 #2) id 17P7Px-0005I6-00 for freebsd-scsi@freebsd.org; Mon, 01 Jul 2002 22:05:01 +0200 Message-ID: <3D20B619.7080503@duettra.de> Date: Mon, 01 Jul 2002 22:05:45 +0200 From: Rene Duettra Reply-To: lola21@gmx.net User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: de,en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: problem on booting scsi 53c810 device from from FreeBSD 4.6 boot disks Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit 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, I tried to install FreeBSD 4.6 from the 2 boot disks (kern, mfsroot). everything seems fine: sym0: ID7 Fast10, parity checking then I got these messages (which loops): sym0: PCI Status=0x8100 sym0: suspicious SCSI data while resetting the BUS sym0: dp0,d7-0,rst,req,ack,asy,sel,atn,msq,c/d,i/o=0x180,expecting 0x100 (noperiph:sym0:0:-1:-1): SCSI BUS reset detected sym0: Error(c0:0) (e-aa-0) (0/3)@(scrpla90 1e000000). sym0: script cmd=82030000 sym0: regdump: da 10 80 03 47 00 30 1f 00 0e 07 aa 80 00 0a 00 00 60 be 07 2a ff ff ff. I installed an OpenBSD3.0 some weeks ago, and this worked just fine. I want to avoid to install FreeBSD by using an FTP server and recompile the kernel with the ncr module (which I think is used by OpenBSD). On comp.unix.bsd.freebsd.misc I read about people having the same problem (--> dk@mobile.rogers.com; NCR 53c810 SCSI controller and the new 'sym' driver), but they didnīt get any answers. my hardware: AMD K6-200, 128MB RAM, 6 GB HDD (IDE), Symbios 8100S PCI SCSI Adapter (53C810 Device) with Yahama SCSI burner and Ultraplex 32xCDROM Thanks for your help. Rene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 3 22:58: 1 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 6EEDD37B400 for ; Wed, 3 Jul 2002 22:58:00 -0700 (PDT) Received: from mother.ludd.luth.se (mother.ludd.luth.se [130.240.16.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3012843E4A for ; Wed, 3 Jul 2002 22:57:59 -0700 (PDT) (envelope-from pb@ludd.luth.se) Received: from brother.ludd.luth.se (brother.ludd.luth.se [130.240.16.78]) by mother.ludd.luth.se (8.10.2+Sun/8.9.3) with ESMTP id g645vvj03070 for ; Thu, 4 Jul 2002 07:57:57 +0200 (MEST) From: Peter B Received: (from pb@localhost) by brother.ludd.luth.se (8.10.2+Sun/8.9.3) id g642sAu04188 for freebsd-scsi@freebsd.org; Thu, 4 Jul 2002 04:54:10 +0200 (MEST) Message-Id: <200207040254.g642sAu04188@brother.ludd.luth.se> Subject: S.M.A.R.T tool for FreeBSD. To: freebsd-scsi@freebsd.org Date: Thu, 4 Jul 2002 04:54:10 +0200 (MEST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have made some first steps towards a s.m.a.r.t tool for freebsd-scsi. It's based on the linux tool 'smartsuite' (as can be understood easily). Right now it compiles under FreeBSD 4.x and at least prints usage. I have not tested it on any physical unit yet. Feedback on testing the code would be interesting. (on your own risk) http://wave.campus.luth.se/~pb/tmp/smartsuite-2.1_mod020704.tar.gz /P To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 4 12:41:16 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 886C937B400 for ; Thu, 4 Jul 2002 12:41:08 -0700 (PDT) Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBDE243E31 for ; Thu, 4 Jul 2002 12:41:07 -0700 (PDT) (envelope-from groudier@free.fr) Received: from [192.168.1.129] (213.36.63.19) by mail.libertysurf.net (5.1.053) id 3CEE22B400A3FB5C; Thu, 4 Jul 2002 21:40:20 +0200 Date: Tue, 2 Jul 2002 03:18:43 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: groudier@localhost.my.domain To: lola21@gmx.net Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: problem on booting scsi 53c810 device from from FreeBSD 4.6 boot disks In-Reply-To: <3D20B619.7080503@duettra.de> Message-ID: <20020702023237.X3415-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 Mon, 1 Jul 2002, Rene Duettra wrote: > Hello, > I tried to install FreeBSD 4.6 from the 2 boot disks (kern, mfsroot). > > everything seems fine: > sym0: ID7 Fast10, parity checking > > then I got these messages (which loops): > sym0: PCI Status=3D0x8100 The device is reporting a PCI error condition: - bit 0x8000 -> detected parity error (detected or observed as a master) - bit 0x0100 -> data parity error detected This means that the PCI device acting as a master detected a parity error on the PCI bus or observed the PERR bit asserted (assumed by the PCI target) > sym0: suspicious SCSI data while resetting the BUS > sym0: dp0,d7-0,rst,req,ack,asy,sel,atn,msq,c/d,i/o=3D0x180,expecting This means that the device reported that the SCSI/REQ signal was still asserted and SCSI/RESET was asserted since 200 micro-seconds. Btw, this one looks extremally weird, since this SCSI signal is normally driven by the SCSI initiator. > 0x100 (noperiph:sym0:0:-1:-1): SCSI BUS reset detected > sym0: Error(c0:0) (e-aa-0) (0/3)@(scrpla90 1e000000). DSTAT=3D0xc0 bit 0x40 -> Master data parity error (Same condition as reported from the PCI Status register above) > sym0: script cmd=3D82030000 > sym0: regdump: da 10 80 03 47 00 30 1f 00 0e 07 aa 80 00 0a 00 00 60 > be 07 2a ff ff ff. > > I installed an OpenBSD3.0 some weeks ago, and this worked just fine. I > want to avoid to install FreeBSD by using an FTP server and recompile > the kernel with the ncr module (which I think is used by OpenBSD). > > On comp.unix.bsd.freebsd.misc I read about people having the same > problem (--> dk@mobile.rogers.com; NCR 53c810 SCSI controller and the > new 'sym' driver), but they didn=B4t get any answers. > > my hardware: > AMD K6-200, 128MB RAM, 6 GB HDD (IDE), Symbios 8100S PCI SCSI Adapter > (53C810 Device) with Yahama SCSI burner and Ultraplex 32xCDROM The sym driver does enable PCI parity checking. FYI, only a few PCI device drivers are picky about that. In other words, most just disable this checking or donnot care about it. For example, the ncr driver does not enable it (even if the source let think that it wants to enable it). As seen from PCI specifications, PCI parity checking is not a option for such device class. As a result, this checking should be enabled by default (as does sym for example). May-be, 'sym' works reliably on your system with PCI parity checking disabled (not 100% sure given the 2nd error which is SCSI related). Just the sym driver maintainer does not want to silently not enable this checking. Note that there is some heuristic in the driver that tries to detect spurious PCI parity errors and automatically disable the thing, but it does not seem to apply to your system. Indeed, you may switch to another driver or O/S that works for you. You also could give a try with sym with PCI parity checking disabled, at your own risks obviously. Setting the SYM_SETUP_PCI_PARITY driver config option to 0 should do the trick. File /usr/sys/dev/sym/sym_conf.h or add the corresponding define to your kernel config file: (You may also read the sym(4) man page that documents this option) -- /* * PCI parity checking. * It should not be an option, but some poor or broken * PCI-HOST bridges have been reported to make problems * when this feature is enabled. * Setting this option to 0 tells the driver not to * enable the checking against PCI parity. */ #ifndef SYM_SETUP_PCI_PARITY #define SYM_SETUP_PCI_PARITY=09(1) #endif -- Regards, G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 4 13:28:47 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 8B37A37B400 for ; Thu, 4 Jul 2002 13:28:45 -0700 (PDT) Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C6E743E09 for ; Thu, 4 Jul 2002 13:28:45 -0700 (PDT) (envelope-from groudier@free.fr) Received: from [192.168.1.129] (213.36.63.19) by mail.libertysurf.net (5.1.053) id 3D1C59A60016586A; Thu, 4 Jul 2002 22:27:31 +0200 Date: Tue, 2 Jul 2002 04:06:21 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: groudier@localhost.my.domain To: lola21@gmx.net Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: problem on booting scsi 53c810 device from from FreeBSD 4.6 boot disks In-Reply-To: <20020702023237.X3415-100000@localhost.my.domain> Message-ID: <20020702040144.A3415-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 Just following up my email to fix an obvious mistake. :-) On Tue, 2 Jul 2002, G=E9rard Roudier wrote: > > sym0: suspicious SCSI data while resetting the BUS > > sym0: dp0,d7-0,rst,req,ack,asy,sel,atn,msq,c/d,i/o=3D0x180,expecting > > This means that the device reported that the SCSI/REQ signal was still > asserted and SCSI/RESET was asserted since 200 micro-seconds. Btw, this > one looks extremally weird, since this SCSI signal is normally driven by > the SCSI initiator. It is the SCSI target that drives the SCSI/REQ message. I have been confused by the PCI REQ# signal as I was reading some PCI related paper.. (Or my brain gets too old, who knows... :)) > > 0x100 (noperiph:sym0:0:-1:-1): SCSI BUS reset detected > > sym0: Error(c0:0) (e-aa-0) (0/3)@(scrpla90 1e000000). Confused "G=E9rard", :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message