From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 3 11:03:05 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 CB58016A400 for ; Mon, 3 Apr 2006 11:03:05 +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 935F943D45 for ; Mon, 3 Apr 2006 11:03:05 +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 k33B35Xs006049 for ; Mon, 3 Apr 2006 11:03:05 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k33B340Y006043 for freebsd-scsi@freebsd.org; Mon, 3 Apr 2006 11:03:04 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 3 Apr 2006 11:03:04 GMT Message-Id: <200604031103.k33B340Y006043@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, 03 Apr 2006 11:03:05 -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 Thu Apr 6 19:28:07 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 E9F3816A8D6; Thu, 6 Apr 2006 19:28:07 +0000 (UTC) (envelope-from os@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6878D466C2; Thu, 6 Apr 2006 19:08:06 +0000 (GMT) (envelope-from os@rsu.ru) Received: from wolf.os.rsu.ru (os@os.adsl.r61.net [195.208.243.95]) (authenticated bits=0) by mail.r61.net (8.13.4/8.13.4) with ESMTP id k36J7qSj022892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 6 Apr 2006 23:07:55 +0400 (MSD) (envelope-from os@rsu.ru) Date: Thu, 6 Apr 2006 23:07:53 +0400 (MSD) From: Oleg Sharoiko To: John Baldwin In-Reply-To: <20060328201134.S763@brain.cc.rsu.ru> Message-ID: <20060406223724.S1099@wolf.os.rsu.ru> References: <20060215102749.D58480@brain.cc.rsu.ru> <200603271607.09550.jhb@freebsd.org> <20060328185449.F763@brain.cc.rsu.ru> <200603281108.25548.jhb@freebsd.org> <20060328201134.S763@brain.cc.rsu.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean 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: Thu, 06 Apr 2006 19:28:08 -0000 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? 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? 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? On Tue, 28 Mar 2006, Oleg Sharoiko wrote: OS> OS>On Tue, 28 Mar 2006, John Baldwin wrote: OS> OS>JB>Is this an Intel box? OS> OS>This is IBM xSeries 226. Motherboard is labeled 'MS 9151 Ver.1'. It OS>appears to be MSI E7525 Master-S2 or a modification of it. I couldn't find OS>information about it in the net. Just few short notes and nothing else. I OS>suppose it's based on Intel's E7525 chipset. OS> OS>JB>It only detects it if the interrupt line is constantly on. If the interrupt OS>JB>line goes off for a little bit and then back on often enough the istorm logic OS>JB>won't kick in. You can try lowering the threshold via the tunable to see if OS>JB>you can get it to kick in perhaps. OS> OS>No luck here. OS> OS> -- Oleg Sharoiko. Software and Network Engineer Computer Center of Rostov State University. From owner-freebsd-scsi@FreeBSD.ORG Thu Apr 6 20:12:04 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 2985C16A406; Thu, 6 Apr 2006 20:12:04 +0000 (UTC) (envelope-from os@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0860843D86; Thu, 6 Apr 2006 20:12:00 +0000 (GMT) (envelope-from os@rsu.ru) Received: from brain.cc.rsu.ru (brain.cc.rsu.ru [195.208.252.154]) (authenticated bits=0) by mail.r61.net (8.13.4/8.13.4) with ESMTP id k36KBsqX029583 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Apr 2006 00:11:57 +0400 (MSD) (envelope-from os@rsu.ru) Date: Fri, 7 Apr 2006 00:11:55 +0400 (MSD) From: Oleg Sharoiko To: John Baldwin In-Reply-To: <20060406223724.S1099@wolf.os.rsu.ru> Message-ID: <20060407000934.R17852@brain.cc.rsu.ru> References: <20060215102749.D58480@brain.cc.rsu.ru> <200603271607.09550.jhb@freebsd.org> <20060328185449.F763@brain.cc.rsu.ru> <200603281108.25548.jhb@freebsd.org> <20060328201134.S763@brain.cc.rsu.ru> <20060406223724.S1099@wolf.os.rsu.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean 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: Thu, 06 Apr 2006 20:12:04 -0000 On Thu, 6 Apr 2006, Oleg Sharoiko wrote: OS>It looks like the mis-routed interrupt is the one from ips. In my kernel OS>ips is on vector 49 and bge is on vector 60. I've added OS> if (vector == 60) OS> vector = 49; OS>to sys/amd64/amd64/local_apic.c and I have no more interrupt storm until I forgot to mention that I inserted this 'if' into lapic_handle_intr(). OS>bge really generates interrupt. Am I right with my conclusion about ips OS>interrupt being mis-directed to bge? OS> OS>There's also another interesting point: it looks like ips triggers OS>interrupt on both vectors (49 and 60 - irq 28 and irq 16). Why do I think OS>so? OS> OS>1. ips works fine even when there's no bge in kernel (I suppose irq 16 is OS>not activated in this case). I suppose this should mean that interrupts OS>are properly delivered to ips driver. OS> OS>2. I've added debug printf to bge_intr and in single mode when preemption OS>is disabled I see exact the same number of interrupts delivered to ips OS>(checked counters with showintrcnt) and to bge (incorrectly delivered - OS>bge is not in UP state and bge registers say "no interrupt"). OS> OS>This seems really strange to me, how can this be possible? Is there any OS>way to fix this? OS> OS>On Tue, 28 Mar 2006, Oleg Sharoiko wrote: OS> OS>OS> OS>OS>On Tue, 28 Mar 2006, John Baldwin wrote: OS>OS> OS>OS>JB>Is this an Intel box? OS>OS> OS>OS>This is IBM xSeries 226. Motherboard is labeled 'MS 9151 Ver.1'. It OS>OS>appears to be MSI E7525 Master-S2 or a modification of it. I couldn't find OS>OS>information about it in the net. Just few short notes and nothing else. I OS>OS>suppose it's based on Intel's E7525 chipset. OS>OS> OS>OS>JB>It only detects it if the interrupt line is constantly on. If the interrupt OS>OS>JB>line goes off for a little bit and then back on often enough the istorm logic OS>OS>JB>won't kick in. You can try lowering the threshold via the tunable to see if OS>OS>JB>you can get it to kick in perhaps. OS>OS> OS>OS>No luck here. OS>OS> OS>OS> OS> OS> -- Oleg Sharoiko. Software and Network Engineer Computer Center of Rostov State University.