From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 30 11:07:04 2008 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A5DC1065716 for ; Mon, 30 Jun 2008 11:07:04 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DE9328FC32 for ; Mon, 30 Jun 2008 11:07:03 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5UB73sI095877 for ; Mon, 30 Jun 2008 11:07:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5UB73Dr095873 for freebsd-scsi@FreeBSD.org; Mon, 30 Jun 2008 11:07:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 30 Jun 2008 11:07:03 GMT Message-Id: <200806301107.m5UB73Dr095873@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org 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, 30 Jun 2008 11:07:04 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/40895 scsi wierd kernel / device driver bug o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o kern/60598 scsi wire down of scsi devices conflicts with config o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/94838 scsi Kernel panic while mounting SD card with lock switch o o kern/99954 scsi [ahc] reading from DVD failes on 6.x [regression] o kern/110847 scsi [ahd] Tyan U320 onboard problem with more than 3 disks o kern/120247 scsi [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s o kern/124667 scsi [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi 15 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce o kern/38828 scsi [dpt] [request] DPT PM2012B/90 doesn't work o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/114597 scsi [sym] System hangs at SCSI bus reset with dual HBAs o kern/119668 scsi [cam] [patch] certain errors are too verbose comparing o kern/120487 scsi [sg] scsi_sg incompatible with scanners o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc o kern/123666 scsi [aac] aac(4) will not work with Adaptec SAS RAID 3805 o kern/123674 scsi [ahc] ahc driver dumping 10 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 30 15:48:46 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C390106567A for ; Mon, 30 Jun 2008 15:48:45 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id AA3668FC17 for ; Mon, 30 Jun 2008 15:48:45 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1KDL1Y-000CnB-1l for freebsd-scsi@freebsd.org; Mon, 30 Jun 2008 18:10:36 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: freebsd-scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Jun 2008 18:10:36 +0300 From: Danny Braniss Message-ID: Subject: iscsi target failure ... 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, 30 Jun 2008 15:48:46 -0000 Hi, I'm trying to get the iscsi_initiator to handle errors in a better way, and so far if if I report to the cam via XPT_DONE, with status = CAM_REQ_ABORTED the kernel panics after printing many g_vfs_done():da1s1d[WRITE(offset=6428672, length=2048)]error = 5 (the offset= changes), so I was wandering, is there a better (CAM_REQ_CMP_ERR?) status? the return when a terminal error has occurred? danny From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 30 16:18:39 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C2461065683 for ; Mon, 30 Jun 2008 16:18:39 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id 4A2588FC1C for ; Mon, 30 Jun 2008 16:18:39 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id 3924A1A91A2; Mon, 30 Jun 2008 08:53:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at X-Spam-Flag: NO X-Spam-Score: -4.399 X-Spam-Level: X-Spam-Status: No, score=-4.399 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599] Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MHRx2ObWaP3X; Mon, 30 Jun 2008 08:53:25 -0700 (PDT) Received: from [10.47.1.30] (vpn.office.miralink.com [10.0.0.5]) by plato.miralink.com (Postfix) with ESMTP id BC36F1A919F; Mon, 30 Jun 2008 08:53:25 -0700 (PDT) Message-ID: <486901AB.2030804@miralink.com> Date: Mon, 30 Jun 2008 08:54:19 -0700 From: Sean Bruno User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Danny Braniss References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@freebsd.org Subject: Re: iscsi target failure ... 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, 30 Jun 2008 16:18:39 -0000 Danny Braniss wrote: > Hi, > I'm trying to get the iscsi_initiator to handle errors in a better way, > and so far if if I report to the cam via XPT_DONE, with status = > CAM_REQ_ABORTED > the kernel panics after printing many > g_vfs_done():da1s1d[WRITE(offset=6428672, length=2048)]error = 5 > (the offset= changes), > so I was wandering, is there a better (CAM_REQ_CMP_ERR?) status? the return > when > a terminal error has occurred? > > danny > > > _______________________________________________ > 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" > Are you talking about the macro XPT_DONE() or the CAM status XPT_DONE? Also, is there a spot in the code that you are specifically looking at? Sean From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 30 16:35:04 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AA691065671 for ; Mon, 30 Jun 2008 16:35:04 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 017A38FC12 for ; Mon, 30 Jun 2008 16:35:03 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1KDMLG-000DfS-BH; Mon, 30 Jun 2008 19:35:02 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Sean Bruno In-reply-to: Your message of Mon, 30 Jun 2008 08:54:19 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Jun 2008 19:35:02 +0300 From: Danny Braniss Message-ID: Cc: freebsd-scsi@freebsd.org Subject: Re: iscsi target failure ... 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, 30 Jun 2008 16:35:04 -0000 > Danny Braniss wrote: > > Hi, > > I'm trying to get the iscsi_initiator to handle errors in a better way, > > and so far if if I report to the cam via XPT_DONE, with status = > > CAM_REQ_ABORTED > > the kernel panics after printing many > > g_vfs_done():da1s1d[WRITE(offset=6428672, length=2048)]error = 5 > > (the offset= changes), > > so I was wandering, is there a better (CAM_REQ_CMP_ERR?) status? the return > > when > > a terminal error has occurred? > > > > danny > Are you talking about the macro XPT_DONE() or the CAM status XPT_DONE? > > Also, is there a spot in the code that you are specifically looking at? > Hi Sean, in iscsi_subr.c/iscsi_cleanup -> _scsi_done->[macro]XPT_DONE() From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 30 18:06:43 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C5E3106566C for ; Mon, 30 Jun 2008 18:06:43 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id DEA958FC19 for ; Mon, 30 Jun 2008 18:06:42 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id AB01D1A91AC; Mon, 30 Jun 2008 11:05:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at X-Spam-Flag: NO X-Spam-Score: -4.399 X-Spam-Level: X-Spam-Status: No, score=-4.399 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599] Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LFa+MVZFYLg6; Mon, 30 Jun 2008 11:05:43 -0700 (PDT) Received: from [10.47.1.30] (vpn.office.miralink.com [10.0.0.5]) by plato.miralink.com (Postfix) with ESMTP id 2F8B31A91AB; Mon, 30 Jun 2008 11:05:43 -0700 (PDT) Message-ID: <486920AD.2070206@miralink.com> Date: Mon, 30 Jun 2008 11:06:37 -0700 From: Sean Bruno User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Danny Braniss References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@freebsd.org Subject: Re: iscsi target failure ... 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, 30 Jun 2008 18:06:43 -0000 Danny Braniss wrote: >> Danny Braniss wrote: >> >>> Hi, >>> I'm trying to get the iscsi_initiator to handle errors in a better way, >>> and so far if if I report to the cam via XPT_DONE, with status = >>> CAM_REQ_ABORTED >>> the kernel panics after printing many >>> g_vfs_done():da1s1d[WRITE(offset=6428672, length=2048)]error = 5 >>> (the offset= changes), >>> so I was wandering, is there a better (CAM_REQ_CMP_ERR?) status? the return >>> when >>> a terminal error has occurred? >>> >>> danny >>> > > >> Are you talking about the macro XPT_DONE() or the CAM status XPT_DONE? >> >> Also, is there a spot in the code that you are specifically looking at? >> >> > > Hi Sean, > in iscsi_subr.c/iscsi_cleanup -> _scsi_done->[macro]XPT_DONE() > > > How are you attempting to make the failure occur with the initiator? Just pulling the cable or some such operation while running an write? Sean