From owner-freebsd-scsi Mon Dec 4 17:43:40 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 4 17:43:37 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from echunga.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 5C9B237B400 for ; Mon, 4 Dec 2000 17:43:35 -0800 (PST) Received: (from grog@localhost) by echunga.lemis.com (8.11.1/8.9.3) id eB51eTb85527; Tue, 5 Dec 2000 12:10:29 +1030 (CST) (envelope-from grog) Date: Tue, 5 Dec 2000 12:10:28 +1030 From: Greg Lehey To: Kenneth Wayne Culver Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: kernel panics in 4.2 Message-ID: <20001205121028.D84692@echunga.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from culverk@wam.umd.edu on Fri, Dec 01, 2000 at 05:26:49PM -0500 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: grog@echunga.lemis.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Friday, 1 December 2000 at 17:26:49 -0500, Kenneth Wayne Culver wrote: > I sent this message to -questions,-current, and -stable earlier, but > nobody seems to know about my problem: > > I just recently tried putting an adaptec 2940w SCSI controller into my > FreeBSD machine (running -STABLE cvsupped and recompiled every night at > 1:30AM) and since including the driver in my kernel I've noticed some > random panics. Most of the time they occur during heavy disk activity, and > usually only when I'm running X (hence the reason I couldn't tell you the > panic message). Even wierder still, I don't even have any SCSI devices > connected yet; I'm using only IDE disks connected via the motherboard's > builtin ATA66. I have also searched the various FreeBSD mailinglist > archives and found some people with the same problems I was having, but no > solutions. Crashes do not occur in Windows with this configuration (at > least not any more than usual :-) ) and when I take the ahc driver out of > the kernel, the panics stop. I've included my dmesg -v output and my > kernel config file, please let me know if anything else is needed. I've been ignoring these messages so far, since you don't include any information about the panics. Take a dump with a kernel with symbols, and things might look different. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 4 19:59:59 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 4 19:59:57 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 90CDF37B401 for ; Mon, 4 Dec 2000 19:59:56 -0800 (PST) Received: from rac3.wam.umd.edu (IDENT:root@rac3.wam.umd.edu [128.8.10.143]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id WAA18092; Mon, 4 Dec 2000 22:59:39 -0500 (EST) Received: from rac3.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id XAA14806; Mon, 4 Dec 2000 23:00:19 -0500 (EST) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA14798; Mon, 4 Dec 2000 23:00:19 -0500 (EST) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Mon, 4 Dec 2000 23:00:19 -0500 (EST) From: Kenneth Wayne Culver To: Greg Lehey Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: kernel panics in 4.2 In-Reply-To: <20001205121028.D84692@echunga.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've been ignoring these messages so far, since you don't include any > information about the panics. Take a dump with a kernel with symbols, > and things might look different. I'm working on getting it to crash again. It appears that with DDB in the kernel, it's reluctant to panic. Anyway, I wanted to make sure that I didn't do something wrong, so I sent this message so that somebody might be able to tell me if I made any mistakes. It appears that I made no mistakes... so I'll have a dump, and a backtrace and anything else that is needed for debugging as soon as I can cause it to crash again. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 5 21:45:31 2000 From owner-freebsd-scsi@FreeBSD.ORG Tue Dec 5 21:45:30 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id BD37237B400 for ; Tue, 5 Dec 2000 21:45:28 -0800 (PST) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 143WiO-00054K-00 for freebsd-scsi@freebsd.org; Tue, 5 Dec 2000 21:02:00 -0800 Date: Tue, 5 Dec 2000 21:01:57 -0800 (PST) From: Tom Samplonius To: freebsd-scsi@freebsd.org Subject: IBM ServeRAID cards? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't see any mention of IBM ServeRAID cards being supported, but I'm holding out hope that they are some kind of rebranded AMI or Mylex. Does anyone know of the details about what exactly an IBM ServeRAID is? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 5 21:56: 8 2000 From owner-freebsd-scsi@FreeBSD.ORG Tue Dec 5 21:56:07 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 9665537B400 for ; Tue, 5 Dec 2000 21:56:06 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB6652F24541; Tue, 5 Dec 2000 22:05:03 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012060605.eB6652F24541@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Samplonius Cc: freebsd-scsi@freebsd.org Subject: Re: IBM ServeRAID cards? In-reply-to: Your message of "Tue, 05 Dec 2000 21:01:57 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Dec 2000 22:05:02 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I don't see any mention of IBM ServeRAID cards being supported, but I'm > holding out hope that they are some kind of rebranded AMI or Mylex. > > Does anyone know of the details about what exactly an IBM ServeRAID is? They're an IBM ServeRAID. I'm working on a driver, but not having a lot of luck (or time) just yet. If someone wanted to take it over, I'd be happy to help out... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 1:43:19 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 01:43:17 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from isc.LF.net (mail.LF.net [212.9.160.2]) by hub.freebsd.org (Postfix) with ESMTP id D09CA37B400 for ; Wed, 6 Dec 2000 01:43:16 -0800 (PST) Received: by isc.LF.net (Smail3.2.0.111/isc.LF.net) via LF.net GmbH Internet Services via remotehost plotin with uucp from plotin!plotin.vortex.de!achim for freebsd-scsi@freebsd.org for hub.freebsd.org id m143b6Y-000ulvC; Wed, 6 Dec 2000 10:43:14 +0100 (CET) Received: by plotin.vortex.de (UUPC/extended 1.12b_vortex); Wed, 06 Dec 2000 10:25:58 CET X-PM-Identity: From: "Achim" Sender: Mail Gateway Message-ID: <3a2e0626.plotin@plotin.vortex.de> To: freebsd-scsi@freebsd.org Date: Wed, 6 Dec 2000 10:34:46 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: SCSI HBA Driver Message-ID: <3A2E1646.10982.419AA8@localhost> Priority: urgent X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm developing a CAM SCSI HBA driver for our ICP Disk Array Controllers for FreeBSD. I tested the driver under FreeBSD 4.1-RELEASE. I'm already in the test phase and now I have some questions. 1. I heared that FreeBSD supports boot-time loadable drivers. What's the required format of the driver disk and which files are required? 2. We want to make the driver publicly available. What's the usual procedure to do this? 3. We need a major device number for our driver to have access from our configuration tool. How can we get a free number? Any help is greatly appreciated. Thank you! Best regards Achim Leubner ICP vortex Computersysteme GmbH Research & Development To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 1:56:32 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 01:56:30 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 1A82A37B400 for ; Wed, 6 Dec 2000 01:56:29 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id WAA13711 for ; Wed, 6 Dec 2000 22:56:26 +1300 (NZDT) Message-Id: <200012060956.WAA13711@ducky.nz.freebsd.org> From: "Dan Langille" Organization: langille.org To: freebsd-scsi@freebsd.org Date: Wed, 6 Dec 2000 22:56:24 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: sym SCSI card problems during settle wait Reply-To: dan@langille.org Priority: normal X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -previously posted to questions I'm trying to install 4.2-RELEASE from floppies. The SCSI card is giving me some grief. I'm using an ASUS PCI SCSI card. During the probes, I see this: sym0: <810a> port 0x6100-0x61ff mem 0xc1001000-0x10010ff irq 9 at device 17.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE parity checking The card has 53C810A on a SYMBIOS chip if that helps. The last message displayed is: Waiting 15 seconds for SCSI devices to settle. Then it stops and never comes back. Any ideas why? I've checked termination, duplicate ids, and there are no IRQ conflicts that I can see. thanks -- Dan Langille The FreeBSD Diary - http://www.freebsddiary.org/ NZ ADSL - http://www.unixathome.org/adsl/ NZ Broadband - http://www.unixathome.org/broadband/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 12:14:24 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 12:14:22 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from front3.grolier.fr (front3.grolier.fr [194.158.96.53]) by hub.freebsd.org (Postfix) with ESMTP id 50C7E37B400 for ; Wed, 6 Dec 2000 12:14:21 -0800 (PST) Received: from nas2-251.mea.club-internet.fr (nas2-251.mea.club-internet.fr [195.36.200.251]) by front3.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id VAA07749; Wed, 6 Dec 2000 21:14:08 +0100 (MET) Date: Wed, 6 Dec 2000 20:14:10 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Dan Langille Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sym SCSI card problems during settle wait In-Reply-To: <200012060956.WAA13711@ducky.nz.freebsd.org> Message-ID: 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 X-Loop: FreeBSD.org On Wed, 6 Dec 2000, Dan Langille wrote: > -previously posted to questions >=20 > I'm trying to install 4.2-RELEASE from floppies. The SCSI card is giving= =20 > me some grief. >=20 > I'm using an ASUS PCI SCSI card. During the probes, I see this:=20 >=20 > sym0: <810a> port 0x6100-0x61ff mem 0xc1001000-0x10010ff irq 9 at=20 > device 17.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE parity=20 > checking=20 >=20 > The card has 53C810A on a SYMBIOS chip if that helps.=20 >=20 > The last message displayed is: Waiting 15 seconds for SCSI devices to=20 > settle. Then it stops and never comes back. Any ideas why?=20 >=20 > I've checked termination, duplicate ids, and there are no IRQ conflicts= =20 > that I can see. You must check that JP1/JP2 are configured for PCI INTA, which is normally the default setting. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 12:22:57 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 12:22:55 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 82F0B37B401 for ; Wed, 6 Dec 2000 12:22:47 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id JAA18516; Thu, 7 Dec 2000 09:22:35 +1300 (NZDT) Message-Id: <200012062022.JAA18516@ducky.nz.freebsd.org> From: "Dan Langille" Organization: langille.org To: Gérard Roudier Date: Thu, 7 Dec 2000 09:22:31 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: Quoted-printable Subject: Re: sym SCSI card problems during settle wait Reply-To: dan@langille.org Cc: freebsd-scsi@FreeBSD.ORG Priority: normal References: <200012060956.WAA13711@ducky.nz.freebsd.org> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 6 Dec 2000, at 20:14, G=E9rard Roudier wrote: > You must check that JP1/JP2 are configured for PCI INTA, which is normal= ly > the default setting. I checked it. It's set to INTA. Thanks. Could there be a corresponding item in the BIOS? -- Dan Langille The FreeBSD Diary - http://www.freebsddiary.org/ NZ ADSL - http://www.unixathome.org/adsl/ NZ Broadband - http://www.unixathome.org/broadband/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 13:30:35 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 13:30:32 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 61D9B37B400 for ; Wed, 6 Dec 2000 13:30:32 -0800 (PST) Received: (from dkelly@localhost) by mail.hiwaay.net (8.11.0/8.11.0) id eB6LU8f01098; Wed, 6 Dec 2000 15:30:08 -0600 (CST) Date: Wed, 6 Dec 2000 15:30:08 -0600 From: David Kelly To: Dan Langille Cc: =?iso-8859-1?Q?G=E9rard_Roudier?= , freebsd-scsi@FreeBSD.ORG Subject: Re: sym SCSI card problems during settle wait Message-ID: <20001206153008.A1465@HiWAAY.net> References: <200012060956.WAA13711@ducky.nz.freebsd.org> <200012062022.JAA18516@ducky.nz.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200012062022.JAA18516@ducky.nz.freebsd.org>; from dan@langille.org on Thu, Dec 07, 2000 at 09:22:31AM +1300 Sender: dkelly@mail.hiwaay.net Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Dec 07, 2000 at 09:22:31AM +1300, Dan Langille wrote: > On 6 Dec 2000, at 20:14, Gérard Roudier wrote: > > > You must check that JP1/JP2 are configured for PCI INTA, which is normally > > the default setting. > > I checked it. It's set to INTA. Thanks. Could there be a corresponding > item in the BIOS? Dan, you did check that nothing was on IRQ 2 as IRQ 9 is really IRQ 2? -- David Kelly N4HHE, dkelly@hiwaay.net (hm) ====================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 13:32:53 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 13:32:51 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 54BB337B400 for ; Wed, 6 Dec 2000 13:32:50 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id KAA20067; Thu, 7 Dec 2000 10:32:35 +1300 (NZDT) Message-Id: <200012062132.KAA20067@ducky.nz.freebsd.org> From: "Dan Langille" Organization: langille.org To: David Kelly Date: Thu, 7 Dec 2000 10:32:27 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: Quoted-printable Subject: Re: sym SCSI card problems during settle wait Reply-To: dan@langille.org Cc: Gérard Roudier , freebsd-scsi@FreeBSD.ORG Priority: normal In-reply-to: <20001206153008.A1465@HiWAAY.net> References: <200012062022.JAA18516@ducky.nz.freebsd.org>; from dan@langille.org on Thu, Dec 07, 2000 at 09:22:31AM +1300 X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 6 Dec 2000, at 15:30, David Kelly wrote: > On Thu, Dec 07, 2000 at 09:22:31AM +1300, Dan Langille wrote: > > On 6 Dec 2000, at 20:14, G=E9rard Roudier wrote: > > > > > You must check that JP1/JP2 are configured for PCI INTA, which is no= rmally > > > the default setting. > > > > I checked it. It's set to INTA. Thanks. Could there be a correspond= ing > > item in the BIOS? > > Dan, you did check that nothing was on IRQ 2 as IRQ 9 is really > IRQ 2? At the suggestion of someone offlist, I've had success with 3.5- RELEASE boot disks. Now I'm putting the disks back into the box to do a proper install. Watch this space. thanks. -- Dan Langille The FreeBSD Diary - http://www.freebsddiary.org/ NZ ADSL - http://www.unixathome.org/adsl/ NZ Broadband - http://www.unixathome.org/broadband/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 13:45:57 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 13:45:55 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from front7.grolier.fr (front7.grolier.fr [194.158.96.57]) by hub.freebsd.org (Postfix) with ESMTP id 8C91B37B400 for ; Wed, 6 Dec 2000 13:45:54 -0800 (PST) Received: from nas1-44.mea.club-internet.fr (nas1-44.mea.club-internet.fr [195.36.139.44]) by front7.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA02399; Wed, 6 Dec 2000 22:45:39 +0100 (MET) Date: Wed, 6 Dec 2000 21:45:40 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Dan Langille Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sym SCSI card problems during settle wait In-Reply-To: <200012062022.JAA18516@ducky.nz.freebsd.org> Message-ID: 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 X-Loop: FreeBSD.org On Thu, 7 Dec 2000, Dan Langille wrote: > On 6 Dec 2000, at 20:14, G=E9rard Roudier wrote: >=20 > > You must check that JP1/JP2 are configured for PCI INTA, which is norma= lly > > the default setting. >=20 > I checked it. It's set to INTA. Thanks. Could there be a corresponding= =20 > item in the BIOS? Probably not. This is just glue external to the chip. The fact that the boot went up to the "wait for SCSI devices to settle..." = =20 kernel message means that the driver succeeded chip initialization and did run successfully some simple SCSI scripts to check DMA was working. But the driver does not check if interrupts are happening properly. That was the reason I suspected the PCI INT pin setting. I donnot see any other obvious reason that may explain the hang-up. You can try a 'boot -v' (verbose) and see if additionnal messages are printed to the console. You may also remove devices from the SCSI BUS and see if it makes differences, for example, etc... G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 14: 7:12 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 14:07:09 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id AF20337B400 for ; Wed, 6 Dec 2000 14:07:08 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id LAA20805; Thu, 7 Dec 2000 11:07:00 +1300 (NZDT) Message-Id: <200012062207.LAA20805@ducky.nz.freebsd.org> From: "Dan Langille" Organization: langille.org To: Gérard Roudier Date: Thu, 7 Dec 2000 11:06:40 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: Quoted-printable Subject: Re: sym SCSI card problems during settle wait Reply-To: dan@langille.org Cc: freebsd-scsi@FreeBSD.ORG Priority: normal References: <200012062022.JAA18516@ducky.nz.freebsd.org> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 6 Dec 2000, at 21:45, G=E9rard Roudier wrote: > On Thu, 7 Dec 2000, Dan Langille wrote: > > > On 6 Dec 2000, at 20:14, G=E9rard Roudier wrote: > > > > > You must check that JP1/JP2 are configured for PCI INTA, which is no= rmally > > > the default setting. > > > > I checked it. It's set to INTA. Thanks. Could there be a correspond= ing > > item in the BIOS? > > Probably not. This is just glue external to the chip. > > The fact that the boot went up to the "wait for SCSI devices to settle..= ." > kernel message means that the driver succeeded chip initialization and d= id > run successfully some simple SCSI scripts to check DMA was working. But > the driver does not check if interrupts are happening properly. That was > the reason I suspected the PCI INT pin setting. > > I donnot see any other obvious reason that may explain the hang-up. You > can try a 'boot -v' (verbose) and see if additionnal messages are printe= d > to the console. You may also remove devices from the SCSI BUS and see if > it makes differences, for example, etc... I don't know if you saw or not, but 3.5.1-RELEASE disks got me to the installation screen. Does that help? -- Dan Langille The FreeBSD Diary - http://www.freebsddiary.org/ NZ ADSL - http://www.unixathome.org/adsl/ NZ Broadband - http://www.unixathome.org/broadband/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 14:17:39 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 14:17:38 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from front1.grolier.fr (front1.grolier.fr [194.158.96.51]) by hub.freebsd.org (Postfix) with ESMTP id 440F837B400 for ; Wed, 6 Dec 2000 14:17:37 -0800 (PST) Received: from nas1-32.cgy.club-internet.fr (nas1-32.cgy.club-internet.fr [195.36.197.32]) by front1.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id XAA15725; Wed, 6 Dec 2000 23:17:22 +0100 (MET) Date: Wed, 6 Dec 2000 22:17:23 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Dan Langille Cc: David Kelly , freebsd-scsi@FreeBSD.ORG Subject: Re: sym SCSI card problems during settle wait In-Reply-To: <200012062132.KAA20067@ducky.nz.freebsd.org> Message-ID: 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 X-Loop: FreeBSD.org On Thu, 7 Dec 2000, Dan Langille wrote: > On 6 Dec 2000, at 15:30, David Kelly wrote: >=20 > > On Thu, Dec 07, 2000 at 09:22:31AM +1300, Dan Langille wrote: > > > On 6 Dec 2000, at 20:14, G=E9rard Roudier wrote: > > >=20 > > > > You must check that JP1/JP2 are configured for PCI INTA, which is n= ormally > > > > the default setting. > > >=20 > > > I checked it. It's set to INTA. Thanks. Could there be a correspon= ding=20 > > > item in the BIOS? > >=20 > > Dan, you did check that nothing was on IRQ 2 as IRQ 9 is really > > IRQ 2? >=20 > At the suggestion of someone offlist, I've had success with 3.5- > RELEASE boot disks. Now I'm putting the disks back into the box to=20 > do a proper install. Watch this space. In 3.5, it was probably the `ncr' driver and not the `sym' that attached your SCSI card. The `ncr' uses a clock and timely polls the interrupt status register of the PCI-SCSI chip. This was probably intended to reap lost interrupts in early time of broken PCI bridging implementations. But this has also the effect of silently band-aiding chips that have interrupt wiring misconfigured or just broken. The `sym' driver hasn't such an interrupt reaping clock. I donnot want unaware user to run such band-aiding for years instead of having caught and fixed such INT problem on day one. Instead, dummy PCI reads are theorically in proper place in both SCSI scripts and C codes for not losing interrupts in presence of posted transactions (not too broken PCI-HOST bridges assumed). This works so since 5 years under Linux, btw. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 14:23: 4 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 14:23:02 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 0C9AA37B400 for ; Wed, 6 Dec 2000 14:23:01 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id LAA20969; Thu, 7 Dec 2000 11:22:48 +1300 (NZDT) Message-Id: <200012062222.LAA20969@ducky.nz.freebsd.org> From: "Dan Langille" Organization: langille.org To: Gérard Roudier Date: Thu, 7 Dec 2000 11:22:29 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: Quoted-printable Subject: Re: sym SCSI card problems during settle wait Reply-To: dan@langille.org Cc: David Kelly , freebsd-scsi@FreeBSD.ORG Priority: normal References: <200012062132.KAA20067@ducky.nz.freebsd.org> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 6 Dec 2000, at 22:17, G=E9rard Roudier wrote: > In 3.5, it was probably the `ncr' driver and not the `sym' that attached > your SCSI card. The `ncr' uses a clock and timely polls the interrupt > status register of the PCI-SCSI chip. This was probably intended to reap > lost interrupts in early time of broken PCI bridging implementations. Bu= t > this has also the effect of silently band-aiding chips that have interru= pt > wiring misconfigured or just broken. > > The `sym' driver hasn't such an interrupt reaping clock. I donnot want > unaware user to run such band-aiding for years instead of having caught > and fixed such INT problem on day one. Instead, dummy PCI reads are > theorically in proper place in both SCSI scripts and C codes for not > losing interrupts in presence of posted transactions (not too broken > PCI-HOST bridges assumed). This works so since 5 years under Linux, btw. Hmm. OK. What do you suggest for this box? I was going to use 3.5.1 to get started, then upgrade to 4-stable. Given that the default 4.= 2 boot floppies won't work for me, will I have the same problem once I upgrade to 4-stable? thanks. -- Dan Langille The FreeBSD Diary - http://www.freebsddiary.org/ NZ ADSL - http://www.unixathome.org/adsl/ NZ Broadband - http://www.unixathome.org/broadband/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 14:55: 4 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 14:55:01 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from front3m.grolier.fr (front3m.grolier.fr [195.36.216.53]) by hub.freebsd.org (Postfix) with ESMTP id 92BF837B400 for ; Wed, 6 Dec 2000 14:55:00 -0800 (PST) Received: from nas1-128.cgy.club-internet.fr (nas1-128.cgy.club-internet.fr [195.36.197.128]) by front3m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id XAA14360; Wed, 6 Dec 2000 23:53:03 +0100 (MET) Date: Wed, 6 Dec 2000 22:53:04 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Dan Langille Cc: David Kelly , freebsd-scsi@FreeBSD.ORG Subject: Re: sym SCSI card problems during settle wait In-Reply-To: <200012062222.LAA20969@ducky.nz.freebsd.org> Message-ID: 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 X-Loop: FreeBSD.org On Thu, 7 Dec 2000, Dan Langille wrote: > On 6 Dec 2000, at 22:17, G=E9rard Roudier wrote: >=20 > > In 3.5, it was probably the `ncr' driver and not the `sym' that attache= d > > your SCSI card. The `ncr' uses a clock and timely polls the interrupt > > status register of the PCI-SCSI chip. This was probably intended to rea= p > > lost interrupts in early time of broken PCI bridging implementations. B= ut > > this has also the effect of silently band-aiding chips that have interr= upt > > wiring misconfigured or just broken. > >=20 > > The `sym' driver hasn't such an interrupt reaping clock. I donnot want > > unaware user to run such band-aiding for years instead of having caught > > and fixed such INT problem on day one. Instead, dummy PCI reads are > > theorically in proper place in both SCSI scripts and C codes for not > > losing interrupts in presence of posted transactions (not too broken > > PCI-HOST bridges assumed). This works so since 5 years under Linux, btw= =2E >=20 > Hmm. OK. What do you suggest for this box? I was going to use=20 > 3.5.1 to get started, then upgrade to 4-stable. Given that the default 4= =2E2=20 > boot floppies won't work for me, will I have the same problem once I=20 > upgrade to 4-stable? If it is IRQ 9 that is not functionning as it should for whatever reason, then `sym' will not work for your hardware as long as the problem will not be fixed. A simple way to make the BIOS use another IRQ number for your PCI-SCSI card is to move it to another PCI slot. Or, if your motherboard set-up software allows to declare IRQ used by legacy ISA devices, you can tell it that IRQ 9 is used by a legacy ISA device. The latter way has the advantage not to require a screw-driver :). G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 17: 4:48 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 17:04:42 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id DA5AC37B400; Wed, 6 Dec 2000 17:04:41 -0800 (PST) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA04227; Wed, 6 Dec 2000 20:04:40 -0500 (EST) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id UAA23986; Wed, 6 Dec 2000 20:04:40 -0500 (EST) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA23982; Wed, 6 Dec 2000 20:04:40 -0500 (EST) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Wed, 6 Dec 2000 20:04:40 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Subject: 4.2 crash with AHA-2940 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This crash doesn't look like it has anything to do with SCSI at all, but here it is: GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /usr/tmp/kernel.0 (kgdb) core-file /usr/tmp/vmcore.0 IdlePTD 3563520 initial pcb at 28e760 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x98 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0172778 stack pointer = 0x10:0xcd46bdbc frame pointer = 0x10:0xcd46bdc8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 2249 (imake) interrupt mask = none panic: from debugger panic: from debugger Uptime: 5h55m42s dumping to dev #ad/0x20009, offset 10368 dump ata1: resetting devices .. done #0 0xc014c40a in dumpsys () #1 0xc014c22b in boot () #2 0xc014c5c1 in panic () #3 0xc012a051 in db_panic () #4 0xc0129ff1 in db_command () #5 0xc012a0b6 in db_command_loop () #6 0xc012c1c3 in db_trap () #7 0xc020384e in kdb_trap () #8 0xc020fa40 in trap_fatal () #9 0xc020f719 in trap_pfault () #10 0xc020f2bb in trap () #11 0xc0172778 in cache_lookup () #12 0xc0172c14 in vfs_cache_lookup () #13 0xc01b8e79 in ufs_vnoperate () #14 0xc0175b5c in lookup () #15 0xc017564c in namei () #16 0xc017ae31 in access () #17 0xc020fc8e in syscall2 () #18 0xc0204195 in Xint0x80_syscall () #19 0x804a381 in ?? () #20 0x8048f25 in ?? () #21 0x8048c95 in ?? () the trace command in DDB starts at the cache_lookup function. None of this really looks scsi related... I have the kernel.0, vmcore.0 and kernel.debug files here waiting if anyone wants to see them. I can provide anything anyone else needs to debug this problem too, I have no experience debugging a kernel like this so I'd like to help with whatever happens. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 17:29:59 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 17:29:58 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 0163437B400 for ; Wed, 6 Dec 2000 17:29:57 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id OAA22551; Thu, 7 Dec 2000 14:29:31 +1300 (NZDT) Message-Id: <200012070129.OAA22551@ducky.nz.freebsd.org> From: "Dan Langille" Organization: langille.org To: Gérard Roudier Date: Thu, 7 Dec 2000 14:28:29 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: Quoted-printable Subject: Re: sym SCSI card problems during settle wait Reply-To: dan@langille.org Cc: David Kelly , freebsd-scsi@FreeBSD.ORG Priority: normal References: <200012062222.LAA20969@ducky.nz.freebsd.org> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 6 Dec 2000, at 22:53, G=E9rard Roudier wrote: > If it is IRQ 9 that is not functionning as it should for whatever reason= , > then `sym' will not work for your hardware as long as the problem will n= ot > be fixed. A simple way to make the BIOS use another IRQ number for your > PCI-SCSI card is to move it to another PCI slot. Or, if your motherboard > set-up software allows to declare IRQ used by legacy ISA devices, you ca= n > tell it that IRQ 9 is used by a legacy ISA device. The latter way has th= e > advantage not to require a screw-driver :). I tried the motherboard setup change and made IRQ 9 into a legacy device. Then I tried 4.2-RELEASE boot floppies again. The system halts at "waiting 15 seconds...". Any suggestions? btw: I've been told this offline: "That's a DFI motherboard, and you may not be able to boot from a SCSI drive with the SC200 because it doesn't have its own BIOS - it uses the BIOS on an ASUS motherboard (for which it was designed). It should work OK as a non-booting controller (for CDROM, scanner, etc.), however." -- Dan Langille The FreeBSD Diary - http://www.freebsddiary.org/ NZ ADSL - http://www.unixathome.org/adsl/ NZ Broadband - http://www.unixathome.org/broadband/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 17:32:18 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 17:32:16 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from grumpy.dyndns.org (cm-24-246-28-166.toney.mediacom.ispchannel.com [24.246.28.166]) by hub.freebsd.org (Postfix) with ESMTP id 55CC337B400 for ; Wed, 6 Dec 2000 17:32:13 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id eB71UhF10699; Wed, 6 Dec 2000 19:30:44 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200012070130.eB71UhF10699@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: Dan Langille , freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: sym SCSI card problems during settle wait In-reply-to: Message from =?ISO-8859-1?Q?G=E9rard_Roudier?= of "Wed, 06 Dec 2000 22:53:04 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Wed, 06 Dec 2000 19:30:43 -0600 Sender: dkelly@grumpy.dyndns.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org =3D?ISO-8859-1?Q?G=3DE9rard_Roudier?=3D writes: > = > = > On Thu, 7 Dec 2000, Dan Langille wrote: > = > > Hmm. OK. What do you suggest for this box? I was going to use = > > 3.5.1 to get started, then upgrade to 4-stable. Given that the defau= lt 4.2 = > > boot floppies won't work for me, will I have the same problem once I = > > upgrade to 4-stable? > = > If it is IRQ 9 that is not functionning as it should for whatever reaso= n, > then `sym' will not work for your hardware as long as the problem will = not > be fixed. A simple way to make the BIOS use another IRQ number for your= > PCI-SCSI card is to move it to another PCI slot. Or, if your motherboar= d > set-up software allows to declare IRQ used by legacy ISA devices, you c= an > tell it that IRQ 9 is used by a legacy ISA device. The latter way has t= he > advantage not to require a screw-driver :). Asus MB's (sample size: 1 PPro, 1 P-III) like to share one free IRQ for = all PCI cards. And it works. Usually IRQ 11 unless the 2nd IDE/ATA is = disabled then 15 is used. Mandatory SCSI content: I haven't found a soft way to alter boot order = when there is more than one SCSI card installed. I always guess exactly = wrong and have to take it apart and swap the cards or cables. The one = thing I can do is with the onboard Adaptec SCSI, can force it to be = last, or default to first, from tbe BIOS setup. Is it safe to share an IRQ between, say, a SCSI card and the onboard = "PCI" ATA stuff? If so, then why do they use both IRQs 14 and 15? -- David Kelly N4HHE, dkelly@hiwaay.net =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 18:45:24 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 18:45:22 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from grumpy.dyndns.org (cm-24-246-28-166.toney.mediacom.ispchannel.com [24.246.28.166]) by hub.freebsd.org (Postfix) with ESMTP id 5CB2E37B400 for ; Wed, 6 Dec 2000 18:45:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id eB72hnF11399; Wed, 6 Dec 2000 20:43:54 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200012070243.eB72hnF11399@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: dan@langille.org Cc: =?iso-8859-1?Q?G=E9rard?= Roudier , freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: sym SCSI card problems during settle wait In-reply-to: Message from "Dan Langille" of "Thu, 07 Dec 2000 14:28:29 +1300." <200012070129.OAA22551@ducky.nz.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Wed, 06 Dec 2000 20:43:49 -0600 Sender: dkelly@grumpy.dyndns.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Dan Langille" writes: > btw: I've been told this offline: > = > "That's a DFI motherboard, and you may not be able to boot from a SCSI > drive with the SC200 because it doesn't have its own BIOS - it uses the= > BIOS on an ASUS motherboard (for which it was designed). It should = > work OK as a non-booting controller (for CDROM, scanner, etc.), = > however." Is it possible the BIOS inits something the sym driver doesn't? As to BIOS on the MB, in the olden days NCR had a semi-successful kit = for grafting the NCR BIOS routines into flashable BIOS. May have pulled = it as many trashed their BIOS good and dead. Maybe DFI offers an = updated BIOS with NCR BIOS? As I think I stated earlier, the Symbios chips ending with 5 have the = proper glue for BIOS PROM/Flash on the card. Dan, haven't looked into their policies on foreign orders but their = name is Centrix *International*, and they offer Symbios-brand '825 = cards for US $39. http://www.centrix-intl.com/. Have purchased from = them in the past and not been disappointed. Well, *am* disappointed = they are out of the '875 cards. -- David Kelly N4HHE, dkelly@hiwaay.net =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 18:53:16 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 18:53:14 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 288F837B400 for ; Wed, 6 Dec 2000 18:53:13 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id PAA23251; Thu, 7 Dec 2000 15:53:00 +1300 (NZDT) Message-Id: <200012070253.PAA23251@ducky.nz.freebsd.org> From: "Dan Langille" Organization: langille.org To: David Kelly Date: Thu, 7 Dec 2000 15:52:58 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: sym SCSI card problems during settle wait Reply-To: dan@langille.org Cc: Gérard Roudier , freebsd-scsi@FreeBSD.ORG Priority: normal In-reply-to: <200012070243.eB72hnF11399@grumpy.dyndns.org> References: Message from "Dan Langille" of "Thu, 07 Dec 2000 14:28:29 +1300." <200012070129.OAA22551@ducky.nz.freebsd.org> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 6 Dec 2000, at 20:43, David Kelly wrote: > Dan, haven't looked into their policies on foreign orders but their > name is Centrix *International*, and they offer Symbios-brand '825 > cards for US $39. http://www.centrix-intl.com/. Have purchased from > them in the past and not been disappointed. Well, *am* disappointed > they are out of the '875 cards. Thanks for that. At this point, buying a card is not an option. I'm just trying to get this donated P133 running. But I'll put the word out and see if anyone has a spare card around. Thanks. -- Dan Langille The FreeBSD Diary - http://www.freebsddiary.org/ NZ ADSL - http://www.unixathome.org/adsl/ NZ Broadband - http://www.unixathome.org/broadband/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 6 23:39:13 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 23:39:11 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id D293E37B400 for ; Wed, 6 Dec 2000 23:39:09 -0800 (PST) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 143uxs-00070K-00 for freebsd-scsi@freebsd.org; Wed, 6 Dec 2000 22:55:36 -0800 Date: Wed, 6 Dec 2000 22:55:35 -0800 (PST) From: Tom Samplonius To: freebsd-scsi@freebsd.org Subject: Multipath SCSI IO? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org How difficult would adding multipath support to the SCSI be? I'd like to be able to access an external storage system using two busses. I've heard rumours that such a thing is in the works. I also wonder whether there is any kind of very unique serial number in the partition table or disklabel that could be used by such a system for autoconfiguration. For instance, if the disk at bus 0, target 1 and the disk at bus 1, target 2 have the same serial number, they must be the same disk, so use multipath? Or am too much of an optimist? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 7 10:44:24 2000 From owner-freebsd-scsi@FreeBSD.ORG Thu Dec 7 10:44:23 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 8E53337B400 for ; Thu, 7 Dec 2000 10:44:22 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 14461d-0002qh-00; Thu, 07 Dec 2000 18:44:13 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eB7Ihnp01414; Thu, 7 Dec 2000 19:43:49 +0100 (CET) (envelope-from wkb) Date: Thu, 7 Dec 2000 19:43:49 +0100 From: Wilko Bulte To: Tom Samplonius Cc: freebsd-scsi@freebsd.org Subject: Re: Multipath SCSI IO? Message-ID: <20001207194349.B842@freebie.demon.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from tom@sdf.com on Wed, Dec 06, 2000 at 10:55:35PM -0800 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Dec 06, 2000 at 10:55:35PM -0800, Tom Samplonius wrote: > > How difficult would adding multipath support to the SCSI be? I'd like > to be able to access an external storage system using two busses. I've > heard rumours that such a thing is in the works. > > I also wonder whether there is any kind of very unique serial number in > the partition table or disklabel that could be used by such a system for > autoconfiguration. For instance, if the disk at bus 0, target 1 and > the disk at bus 1, target 2 have the same serial number, they must be the > same disk, so use multipath? Or am too much of an optimist? You can get the serial number from a SCSI disk, it is in the VPD pages IIRC. -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 8 19:40:30 2000 From owner-freebsd-scsi@FreeBSD.ORG Fri Dec 8 19:40:27 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id CF29637B400 for ; Fri, 8 Dec 2000 19:40:26 -0800 (PST) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id WAA15510; Fri, 8 Dec 2000 22:40:23 -0500 (EST) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id WAA07796; Fri, 8 Dec 2000 22:40:22 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id WAA07792; Fri, 8 Dec 2000 22:40:22 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Fri, 8 Dec 2000 22:40:22 -0500 (EST) From: Kenneth Wayne Culver To: "Justin T. Gibbs" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: kernel panics in 4.2 In-Reply-To: <200012021447.eB2ElF487377@aslan.scsiguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It may be code displacement that has caused some uninilialized data to > be hit. The SCSI driver will never be touched after the initial bus > scan, so it is hard to believe that this is directly caused by the > SCSI subsystem. You really need to capture the panic message in order > for this to be debugged. > Alright, here is what I managed to get: (kgdb) bt #0 dumpsys () at ../../kern/kern_shutdown.c:469 #1 0xc014c22f in boot (howto=260) at ../../kern/kern_shutdown.c:309 #2 0xc014c5c5 in panic (fmt=0xc02229b4 "from debugger") at ../../kern/kern_shutdown.c:556 #3 0xc012a055 in db_panic (addr=-1072224404, have_addr=0, count=-1, modif=0xcd4b2c28 "") at ../../ddb/db_command.c:433 #4 0xc0129ff5 in db_command (last_cmdp=0xc024f5ec, cmd_table=0xc024f44c, aux_cmd_tablep=0xc0289d08) at ../../ddb/db_command.c:333 #5 0xc012a0ba in db_command_loop () at ../../ddb/db_command.c:455 #6 0xc012c1c7 in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 #7 0xc0203826 in kdb_trap (type=12, code=0, regs=0xcd4b2d7c) at ../../i386/i386/db_interface.c:158 #8 0xc020fa10 in trap_fatal (frame=0xcd4b2d7c, eva=152) at ../../i386/i386/trap.c:946 #9 0xc020f6e9 in trap_pfault (frame=0xcd4b2d7c, usermode=0, eva=152) at ../../i386/i386/trap.c:844 #10 0xc020f28b in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = -850353856, tf_esi = -850710760, tf_ebp = -850711096, tf_isp = -850711128, tf_ebx = 128, tf_edx = -1061277696, tf_ecx = -861838324, tf_eax = 683, tf_trapno = 12, tf_err = 0, tf_eip = -1072224404, tf_cs = 8, tf_eflags = 66054, tf_esp = 0, tf_ss = -850353856}) at ../../i386/i386/trap.c:443 #11 0xc017276c in cache_lookup (dvp=0xcd50a140, vpp=0xcd4b2f04, cnp=0xcd4b2f18) at ../../kern/vfs_cache.c:213 #12 0xc0172c08 in vfs_cache_lookup (ap=0xcd4b2e58) at ../../kern/vfs_cache.c:451 #13 0xc01b8e51 in ufs_vnoperate (ap=0xcd4b2e58) at ../../ufs/ufs/ufs_vnops.c:2287 ---Type to continue, or q to quit--- #14 0xc0175b50 in lookup (ndp=0xcd4b2ef0) at vnode_if.h:52 #15 0xc0175640 in namei (ndp=0xcd4b2ef0) at ../../kern/vfs_lookup.c:153 #16 0xc017ae25 in access (p=0xcca02ea0, uap=0xcd4b2f80) at ../../kern/vfs_syscalls.c:1599 #17 0xc020fc5e in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134524429, tf_esi = 134522776, tf_ebp = -1077939796, tf_isp = -850710572, tf_ebx = 134524416, tf_edx = -1, tf_ecx = 2, tf_eax = 33, tf_trapno = 12, tf_err = 2, tf_eip = 671749180, tf_cs = 31, tf_eflags = 643, tf_esp = -1077939840, tf_ss = 47}) at ../../i386/i386/trap.c:1150 #18 0xc0204165 in Xint0x80_syscall () I looked at what caused the trap and it seems to be in the line if (ncp->nc_dvp == dvp && ncp->nc_nlen == cnp->cn_namelen && !bcmp(ncp->nc_name, cnp->cn_nameptr, ncp->nc_nlen)) break; I think it is because ncp->nc_name has a value: (kgdb) print ncp->nc_name $7 = 0x804ae00 "admindefines" but cnp->cn_nameptr is a null pointer: (kgdb) print cnp->cn_nameptr $8 = 0x0 but the length argument to bcmp is: (kgdb) print ncp->nc_nlen $9 = 73 'I' I don't know where to go from here though, I have absolutely no idea why cnp->cn_nameptr would be NULL. Anyway, any help is appreciated. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message