From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 10 11:02:59 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 81C5916A401 for ; Mon, 10 Apr 2006 11:02:59 +0000 (UTC) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48DC043D48 for ; Mon, 10 Apr 2006 11:02:59 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k3AB2xD0092668 for ; Mon, 10 Apr 2006 11:02:59 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k3AB2v9i092662 for freebsd-scsi@freebsd.org; Mon, 10 Apr 2006 11:02:57 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 10 Apr 2006 11:02:57 GMT Message-Id: <200604101102.k3AB2v9i092662@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 11:02:59 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/05/03] kern/27059 scsi [sym] SCSI subsystem hangs under heavy lo o [2001/06/29] kern/28508 scsi problems with backup to Tandberg SLR40 st o [2002/06/17] kern/39388 scsi ncr/sym drivers fail with 53c810 and more o [2002/07/22] kern/40895 scsi wierd kernel / device driver bug o [2003/05/24] kern/52638 scsi [panic] SCSI U320 on SMP server won't run s [2003/09/30] kern/57398 scsi [mly] Current fails to install on mly(4) o [2003/12/26] kern/60598 scsi wire down of scsi devices conflicts with o [2003/12/27] kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C81 s [2004/01/10] kern/61165 scsi [panic] kernel page fault after calling c o [2004/12/02] kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5 o [2005/06/04] kern/81887 scsi [aac] Adaptec SCSI 2130S aac0: GetDeviceP o [2005/12/12] kern/90282 scsi [sym] SCSI bus resets cause loss of ch de o [2006/02/04] kern/92798 scsi [ahc] SCSI problem with timeouts o [2006/02/10] kern/93128 scsi [sym] FreeBSD 6.1 BETA 1 has problems wit o [2006/03/22] kern/94838 scsi Kernel panic while mounting SD card with 15 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/12/06] kern/23314 scsi aic driver fails to detect Adaptec 1520B o [2002/02/23] kern/35234 scsi World access to /dev/pass? (for scanner) o [2002/06/02] kern/38828 scsi [feature request] DPT PM2012B/90 doesn't o [2002/10/29] kern/44587 scsi dev/dpt/dpt.h is missing defines required o [2005/01/12] kern/76178 scsi [ahd] Problem with ahd and large SCSI Rai 5 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 10 18:04:38 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 EF79E16A404 for ; Mon, 10 Apr 2006 18:04:38 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD1D643D48 for ; Mon, 10 Apr 2006 18:04:35 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3AI4UO7009092; Mon, 10 Apr 2006 14:04:31 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Oleg Sharoiko Date: Mon, 10 Apr 2006 14:01:10 -0400 User-Agent: KMail/1.9.1 References: <20060215102749.D58480@brain.cc.rsu.ru> <20060328201134.S763@brain.cc.rsu.ru> <20060406223724.S1099@wolf.os.rsu.ru> In-Reply-To: <20060406223724.S1099@wolf.os.rsu.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604101401.12479.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1389/Mon Apr 10 08:58:55 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-scsi@freebsd.org, Andrey Beresovsky Subject: Re: Boot hangs on ips0: resetting adapter, this may take up to 5 minutes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 18:04:39 -0000 On Thursday 06 April 2006 15:07, Oleg Sharoiko wrote: > Hi, that's me again. > > John, I've got more information on my problem: > > It looks like the mis-routed interrupt is the one from ips. In my kernel > ips is on vector 49 and bge is on vector 60. I've added > > if (vector == 60) > vector = 49; > > to sys/amd64/amd64/local_apic.c and I have no more interrupt storm until > bge really generates interrupt. Am I right with my conclusion about ips > interrupt being mis-directed to bge? Well, the vectors is the wrong thing to mess with as vector's are IDT entries. > There's also another interesting point: it looks like ips triggers > interrupt on both vectors (49 and 60 - irq 28 and irq 16). Why do I think > so? This happens in several machines with Intel server chipsets due to a bug in the PXH host bridges with no real workaround. > 1. ips works fine even when there's no bge in kernel (I suppose irq 16 is > not activated in this case). I suppose this should mean that interrupts > are properly delivered to ips driver. > > 2. I've added debug printf to bge_intr and in single mode when preemption > is disabled I see exact the same number of interrupts delivered to ips > (checked counters with showintrcnt) and to bge (incorrectly delivered - > bge is not in UP state and bge registers say "no interrupt"). > > This seems really strange to me, how can this be possible? Is there any > way to fix this? One thing you can do w/o hacking the code is to reroute ips0 to IRQ 16. Find the dmesg line for ips0, it should say something like: ips0 <...> ... at device 4.0 on pci2 These numbers (4 from '4.0' and 2 from 'pci2') are the slot and bus for ips0. We'll assume INTA is being used as single function cards using INTA. Then, set a tunable like so in the loader to force ips0 to use IRQ 16: 'set hw.pci2.4.INTA.irq=16' This may not work for 6.0 but should work for 6.1 and later. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 10 18:43:42 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 C423916A403; Mon, 10 Apr 2006 18:43:42 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DAEE43D49; Mon, 10 Apr 2006 18:43:39 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k3AIhau0032836; Mon, 10 Apr 2006 12:43:37 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <443AA752.3070304@samsco.org> Date: Mon, 10 Apr 2006 12:43:30 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20060215102749.D58480@brain.cc.rsu.ru> <20060328201134.S763@brain.cc.rsu.ru> <20060406223724.S1099@wolf.os.rsu.ru> <200604101401.12479.jhb@freebsd.org> In-Reply-To: <200604101401.12479.jhb@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org, Andrey Beresovsky Subject: Re: Boot hangs on ips0: resetting adapter, this may take up to 5 minutes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 18:43:42 -0000 John Baldwin wrote: > On Thursday 06 April 2006 15:07, Oleg Sharoiko wrote: > >>Hi, that's me again. >> >>John, I've got more information on my problem: >> >>It looks like the mis-routed interrupt is the one from ips. In my kernel >>ips is on vector 49 and bge is on vector 60. I've added >> >> if (vector == 60) >> vector = 49; >> >>to sys/amd64/amd64/local_apic.c and I have no more interrupt storm until >>bge really generates interrupt. Am I right with my conclusion about ips >>interrupt being mis-directed to bge? > > > Well, the vectors is the wrong thing to mess with as vector's are IDT > entries. > > >>There's also another interesting point: it looks like ips triggers >>interrupt on both vectors (49 and 60 - irq 28 and irq 16). Why do I think >>so? > > > This happens in several machines with Intel server chipsets due to a bug > in the PXH host bridges with no real workaround. > Well, the work around is to not mask the APIC and instead let the driver handle masking or ACKing the interrupt =-) It sucks that there are undocumented gotchas like this in the PC platform, but it is important to acknowledge them. Scott From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 10 18:48:23 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 C1DED16A406 for ; Mon, 10 Apr 2006 18:48:23 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AE4743D45 for ; Mon, 10 Apr 2006 18:48:23 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k3AImMIP031635 for ; Mon, 10 Apr 2006 13:48:23 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <443AA86A.5020207@centtech.com> Date: Mon, 10 Apr 2006 13:48:10 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1389/Mon Apr 10 07:58:55 2006 on mh1.centtech.com X-Virus-Status: Clean Subject: LIP destroyed xxx active commands X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 18:48:23 -0000 What are these, and what do they mean to me? isp0: LIP destroyed 255 active commands isp0: LIP destroyed 59 active commands isp0: LIP destroyed 129 active commands isp0: LIP destroyed 1 active commands isp0: LIP destroyed 1 active commands isp0: LIP destroyed 252 active commands isp0: LIP destroyed 60 active commands isp0: LIP destroyed 127 active commands Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 10 19:51:11 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 B598316A401 for ; Mon, 10 Apr 2006 19:51:11 +0000 (UTC) (envelope-from tom@uniserve.com) Received: from mx6.uniserve.ca (mx6a.uniserve.ca [216.113.192.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FAC743D46 for ; Mon, 10 Apr 2006 19:51:11 +0000 (GMT) (envelope-from tom@uniserve.com) Received: from mgmt.uniserve.ca ([216.113.192.30]) by mx6.uniserve.ca with esmtp (Exim 4.50) id 1FT2Pm-000NJn-RO; Mon, 10 Apr 2006 12:51:10 -0700 Date: Mon, 10 Apr 2006 12:51:10 -0700 (PDT) From: Tom Samplonius X-X-Sender: tom@mgmt.uniserve.ca To: Eric Anderson In-Reply-To: <443AA86A.5020207@centtech.com> Message-ID: <20060410120647.W46924@mgmt.uniserve.ca> References: <443AA86A.5020207@centtech.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanner: OK. Scanned. Cc: freebsd-scsi@freebsd.org Subject: Re: LIP destroyed xxx active commands X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 19:51:11 -0000 Eric, It seems that isp0 is connected to a loop topology network (as opposed to a point to point, or fabric), and something keeps initializing the loop by sending a LIP command. Are you plugging or unplugging things into the loop all of the time? Or are you loop part on a switch, and someone else is plugging or unplugging things from the fabric? If you are going straight into a switch, it might be better to change the port to a fabric port instead. Tom On Mon, 10 Apr 2006, Eric Anderson wrote: > What are these, and what do they mean to me? > > isp0: LIP destroyed 255 active commands > isp0: LIP destroyed 59 active commands > isp0: LIP destroyed 129 active commands > isp0: LIP destroyed 1 active commands > isp0: LIP destroyed 1 active commands > isp0: LIP destroyed 252 active commands > isp0: LIP destroyed 60 active commands > isp0: LIP destroyed 127 active commands > > > Eric > > > > > -- > ------------------------------------------------------------------------ > Eric Anderson Sr. Systems Administrator Centaur Technology > Anything that works is better than anything that doesn't. > ------------------------------------------------------------------------ > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 10 20:50:03 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 5581E16A409 for ; Mon, 10 Apr 2006 20:50:03 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D886843D79 for ; Mon, 10 Apr 2006 20:49:54 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k3AKnrhR038184; Mon, 10 Apr 2006 15:49:54 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <443AC4E4.9030808@centtech.com> Date: Mon, 10 Apr 2006 15:49:40 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Tom Samplonius References: <443AA86A.5020207@centtech.com> <20060410120647.W46924@mgmt.uniserve.ca> In-Reply-To: <20060410120647.W46924@mgmt.uniserve.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1389/Mon Apr 10 07:58:55 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: LIP destroyed xxx active commands X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 20:50:03 -0000 Tom Samplonius wrote: > > Eric, > > It seems that isp0 is connected to a loop topology network (as opposed > to a point to point, or fabric), and something keeps initializing the > loop by sending a LIP command. > > Are you plugging or unplugging things into the loop all of the time? > Or are you loop part on a switch, and someone else is plugging or > unplugging things from the fabric? If you are going straight into a > switch, it might be better to change the port to a fabric port instead. This host has it's isp device directly connected to a fiber channel array. The array is not disappearing, or being rebooted, nor is there any other machine rebooting or resetting. I see these same errors on another box that has 3 arrays connected to a qlogic switch. I seem to only see these when the machine is heavily accessing the disks. Eric > On Mon, 10 Apr 2006, Eric Anderson wrote: > >> What are these, and what do they mean to me? >> >> isp0: LIP destroyed 255 active commands >> isp0: LIP destroyed 59 active commands >> isp0: LIP destroyed 129 active commands >> isp0: LIP destroyed 1 active commands >> isp0: LIP destroyed 1 active commands >> isp0: LIP destroyed 252 active commands >> isp0: LIP destroyed 60 active commands >> isp0: LIP destroyed 127 active commands >> >> >> Eric >> >> >> >> >> -- >> ------------------------------------------------------------------------ >> Eric Anderson Sr. Systems Administrator Centaur Technology >> Anything that works is better than anything that doesn't. >> ------------------------------------------------------------------------ >> _______________________________________________ >> freebsd-scsi@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi >> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" >> -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 10 21:40:35 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 67B0916A400 for ; Mon, 10 Apr 2006 21:40:35 +0000 (UTC) (envelope-from tom@uniserve.com) Received: from mx5.uniserve.ca (mx5.uniserve.ca [216.113.192.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A62943D46 for ; Mon, 10 Apr 2006 21:40:34 +0000 (GMT) (envelope-from tom@uniserve.com) Received: from mgmt.uniserve.ca ([216.113.192.30]) by mx5.uniserve.ca with esmtp (Exim 4.60) (envelope-from ) id 1FT47e-000BRF-DL; Mon, 10 Apr 2006 14:40:34 -0700 Date: Mon, 10 Apr 2006 14:40:34 -0700 (PDT) From: Tom Samplonius X-X-Sender: tom@mgmt.uniserve.ca To: Eric Anderson In-Reply-To: <443AC4E4.9030808@centtech.com> Message-ID: <20060410143733.V89316@mgmt.uniserve.ca> References: <443AA86A.5020207@centtech.com> <20060410120647.W46924@mgmt.uniserve.ca> <443AC4E4.9030808@centtech.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanner: OK. Scanned. Cc: freebsd-scsi@freebsd.org Subject: Re: LIP destroyed xxx active commands X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 21:40:35 -0000 On Mon, 10 Apr 2006, Eric Anderson wrote: > Tom Samplonius wrote: >> >> Eric, >> >> It seems that isp0 is connected to a loop topology network (as opposed to >> a point to point, or fabric), and something keeps initializing the loop by >> sending a LIP command. >> >> Are you plugging or unplugging things into the loop all of the time? Or >> are you loop part on a switch, and someone else is plugging or unplugging >> things from the fabric? If you are going straight into a switch, it might >> be better to change the port to a fabric port instead. > > > This host has it's isp device directly connected to a fiber channel array. Probably should use point-to-point mode instead. See if you can change the port type on the array controller. > The array is not disappearing, or being rebooted, nor is there any other > machine rebooting or resetting. I see these same errors on another box that > has 3 arrays connected to a qlogic switch. I seem to only see these when the > machine is heavily accessing the disks. Same here. You shouldn't see LIPs on a fabric. So the QLogic switch must be trying to maintain a loop per port. I suspect that loop mode is also less stable than point-to-point or fabric. There is an indication in the isp manpage that it is possible for the driver to hang on boot waiting for a LIP. The solution to that problem has been to force a LIP (unplug something), or don't use a loop mode. > > Eric Tom From owner-freebsd-scsi@FreeBSD.ORG Tue Apr 11 03:08:13 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 599DE16A404 for ; Tue, 11 Apr 2006 03:08:13 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C185B43D46 for ; Tue, 11 Apr 2006 03:08:12 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k3B38BZG054291; Mon, 10 Apr 2006 22:08:11 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <443B1D8E.5000805@centtech.com> Date: Mon, 10 Apr 2006 22:07:58 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Tom Samplonius References: <443AA86A.5020207@centtech.com> <20060410120647.W46924@mgmt.uniserve.ca> <443AC4E4.9030808@centtech.com> <20060410143733.V89316@mgmt.uniserve.ca> In-Reply-To: <20060410143733.V89316@mgmt.uniserve.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1389/Mon Apr 10 07:58:55 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: LIP destroyed xxx active commands X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2006 03:08:13 -0000 Tom Samplonius wrote: > > On Mon, 10 Apr 2006, Eric Anderson wrote: > >> Tom Samplonius wrote: >>> >>> Eric, >>> >>> It seems that isp0 is connected to a loop topology network (as >>> opposed to a point to point, or fabric), and something keeps >>> initializing the loop by sending a LIP command. >>> >>> Are you plugging or unplugging things into the loop all of the >>> time? Or are you loop part on a switch, and someone else is plugging >>> or unplugging things from the fabric? If you are going straight into >>> a switch, it might be better to change the port to a fabric port >>> instead. >> >> >> This host has it's isp device directly connected to a fiber channel >> array. > > Probably should use point-to-point mode instead. See if you can > change the port type on the array controller. Ok - I can do that. If I do that, will that disrupt filesystem activity? >> The array is not disappearing, or being rebooted, nor is there any >> other machine rebooting or resetting. I see these same errors on >> another box that has 3 arrays connected to a qlogic switch. I seem to >> only see these when the machine is heavily accessing the disks. > > Same here. You shouldn't see LIPs on a fabric. So the QLogic switch > must be trying to maintain a loop per port. > > I suspect that loop mode is also less stable than point-to-point or > fabric. There is an indication in the isp manpage that it is possible > for the driver to hang on boot waiting for a LIP. The solution to that > problem has been to force a LIP (unplug something), or don't use a loop > mode. What do I need to change on the qlogic switch/initiator/target ends to force things? Thanks for your help! Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-scsi@FreeBSD.ORG Tue Apr 11 03:15:06 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 06FCF16A400 for ; Tue, 11 Apr 2006 03:15:05 +0000 (UTC) (envelope-from tom@uniserve.com) Received: from mx4.uniserve.ca (mx4.uniserve.ca [216.113.192.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id B25CC43D45 for ; Tue, 11 Apr 2006 03:15:05 +0000 (GMT) (envelope-from tom@uniserve.com) Received: from mgmt.uniserve.ca ([216.113.192.30]) by mx4.uniserve.ca with esmtp (Exim 4.50) id 1FT9LN-000Gpe-Cp; Mon, 10 Apr 2006 20:15:05 -0700 Date: Mon, 10 Apr 2006 20:15:05 -0700 (PDT) From: Tom Samplonius X-X-Sender: tom@mgmt.uniserve.ca To: Eric Anderson In-Reply-To: <443B1D8E.5000805@centtech.com> Message-ID: <20060410201012.X46924@mgmt.uniserve.ca> References: <443AA86A.5020207@centtech.com> <20060410120647.W46924@mgmt.uniserve.ca> <443AC4E4.9030808@centtech.com> <20060410143733.V89316@mgmt.uniserve.ca> <443B1D8E.5000805@centtech.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanner: OK. Scanned. Cc: freebsd-scsi@freebsd.org Subject: Re: LIP destroyed xxx active commands X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2006 03:15:06 -0000 >>>> It seems that isp0 is connected to a loop topology network (as opposed >>>> to a point to point, or fabric), and something keeps initializing the >>>> loop by sending a LIP command. >>>> >>>> Are you plugging or unplugging things into the loop all of the time? >>>> Or are you loop part on a switch, and someone else is plugging or >>>> unplugging things from the fabric? If you are going straight into a >>>> switch, it might be better to change the port to a fabric port instead. >>> >>> >>> This host has it's isp device directly connected to a fiber channel array. >> >> Probably should use point-to-point mode instead. See if you can change >> the port type on the array controller. > > Ok - I can do that. If I do that, will that disrupt filesystem activity? You will probably have to reboot, actually. The isp driver will probably get confused if the port changed type. So do a shutdown, change the port, and then boot up. >>> The array is not disappearing, or being rebooted, nor is there any other >>> machine rebooting or resetting. I see these same errors on another box >>> that has 3 arrays connected to a qlogic switch. I seem to only see these >>> when the machine is heavily accessing the disks. >> >> Same here. You shouldn't see LIPs on a fabric. So the QLogic switch >> must be trying to maintain a loop per port. >> >> I suspect that loop mode is also less stable than point-to-point or >> fabric. There is an indication in the isp manpage that it is possible for >> the driver to hang on boot waiting for a LIP. The solution to that problem >> has been to force a LIP (unplug something), or don't use a loop mode. > > What do I need to change on the qlogic switch/initiator/target ends to force > things? I don't know how do this on QLogic switch. If it is actually a switch, it should have a cli or http management interface to configure ports. If it does not have an interface, it may be a hub, in which it is actually a loop (fibre channel hubs are effectively a daisy chained loop of ports). > Thanks for your help! > > > Eric Tom From owner-freebsd-scsi@FreeBSD.ORG Tue Apr 11 03:23:35 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 0FFC016A400 for ; Tue, 11 Apr 2006 03:23:35 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D62C43D45 for ; Tue, 11 Apr 2006 03:23:34 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k3B3NX40053994; Mon, 10 Apr 2006 22:23:33 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <443B2128.3000309@centtech.com> Date: Mon, 10 Apr 2006 22:23:20 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Tom Samplonius References: <443AA86A.5020207@centtech.com> <20060410120647.W46924@mgmt.uniserve.ca> <443AC4E4.9030808@centtech.com> <20060410143733.V89316@mgmt.uniserve.ca> <443B1D8E.5000805@centtech.com> <20060410201012.X46924@mgmt.uniserve.ca> In-Reply-To: <20060410201012.X46924@mgmt.uniserve.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1389/Mon Apr 10 07:58:55 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: LIP destroyed xxx active commands X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2006 03:23:35 -0000 Tom Samplonius wrote: > >>>>> It seems that isp0 is connected to a loop topology network (as >>>>> opposed to a point to point, or fabric), and something keeps >>>>> initializing the loop by sending a LIP command. >>>>> >>>>> Are you plugging or unplugging things into the loop all of the >>>>> time? Or are you loop part on a switch, and someone else is >>>>> plugging or unplugging things from the fabric? If you are going >>>>> straight into a switch, it might be better to change the port to a >>>>> fabric port instead. >>>> >>>> >>>> This host has it's isp device directly connected to a fiber channel >>>> array. >>> >>> Probably should use point-to-point mode instead. See if you can >>> change the port type on the array controller. >> >> Ok - I can do that. If I do that, will that disrupt filesystem activity? > > You will probably have to reboot, actually. The isp driver will > probably get confused if the port changed type. So do a shutdown, > change the port, and then boot up. Ok - that's what I figured, just making sure. >>>> The array is not disappearing, or being rebooted, nor is there any >>>> other machine rebooting or resetting. I see these same errors on >>>> another box that has 3 arrays connected to a qlogic switch. I seem >>>> to only see these when the machine is heavily accessing the disks. >>> >>> Same here. You shouldn't see LIPs on a fabric. So the QLogic >>> switch must be trying to maintain a loop per port. >>> >>> I suspect that loop mode is also less stable than point-to-point or >>> fabric. There is an indication in the isp manpage that it is possible >>> for the driver to hang on boot waiting for a LIP. The solution to >>> that problem has been to force a LIP (unplug something), or don't use >>> a loop mode. >> >> What do I need to change on the qlogic switch/initiator/target ends to >> force things? > > I don't know how do this on QLogic switch. If it is actually a > switch, it should have a cli or http management interface to configure > ports. If it does not have an interface, it may be a hub, in which it > is actually a loop (fibre channel hubs are effectively a daisy chained > loop of ports). These are real switches. I actually thought that they defaulted to fabric mode, but they must not be. I'll check it out, thanks. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-scsi@FreeBSD.ORG Thu Apr 13 18:05:30 2006 Return-Path: X-Original-To: freebsd-scsi@hub.freebsd.org Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6320A16A400; Thu, 13 Apr 2006 18:05:30 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F87F43D45; Thu, 13 Apr 2006 18:05:30 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k3DI5TGP070604; Thu, 13 Apr 2006 18:05:29 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k3DI5TeQ070600; Thu, 13 Apr 2006 18:05:29 GMT (envelope-from linimon) Date: Thu, 13 Apr 2006 18:05:29 GMT From: Mark Linimon Message-Id: <200604131805.k3DI5TeQ070600@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-scsi@FreeBSD.org Cc: Subject: Re: kern/95707: [cam] [patch] iostat's transfer rate for cdroms is wrong X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 18:05:30 -0000 Synopsis: [cam] [patch] iostat's transfer rate for cdroms is wrong Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi Responsible-Changed-By: linimon Responsible-Changed-When: Thu Apr 13 18:05:20 UTC 2006 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=95707