From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 4 07:01:10 2013 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8FFDD7C1; Wed, 4 Sep 2013 07:01:10 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9DA8C28C1; Wed, 4 Sep 2013 07:01:09 +0000 (UTC) Received: by mail-wg0-f51.google.com with SMTP id a12so2264428wgh.18 for ; Wed, 04 Sep 2013 00:01:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=qQcQ3lQg5yW+MrAD8YAtILdaaJNlfmGx3bzF9F7m8w4=; b=q8BByWIwrdXM0K8ttL7/CYbzTbXgtwpUKxUd5p0FbZVX2X9XpDwckinfdQuHvyrBUY nRy6UzUA1z/Zcr4TamS6QIfLFesAEaP2U4PhFAXGEBSAZovv++c+xBCE9aXc/ItIjdcg /0vhg42kSaV0JcI7uY1boJ8qr0hL8jyc7+gn3J8SaLGwgzP70UagttzyHZ7iPe9EGmRi PHG8OioZTgzu7P/TZA4Y/yKO7AAtgZyGP9s9ZU4wOAmww5/6AD/twLjYA+Bb7TlMi4mk Qfg8zOuneoPIQrJQoT7BsOpaJ4h4zEdJCmGmbwTr+lHJF569lSfAvRBY36ifozGjD7zy h2nw== X-Received: by 10.180.75.16 with SMTP id y16mr767253wiv.59.1378278067954; Wed, 04 Sep 2013 00:01:07 -0700 (PDT) Received: from mavbook.mavhome.dp.ua ([37.229.21.195]) by mx.google.com with ESMTPSA id mw9sm1595508wic.4.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Sep 2013 00:01:06 -0700 (PDT) Sender: Alexander Motin Message-ID: <5226DAB0.1060303@FreeBSD.org> Date: Wed, 04 Sep 2013 10:01:04 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130616 Thunderbird/17.0.6 MIME-Version: 1.0 To: =?windows-1252?Q?Olivier_Cochard-Labb=E9?= Subject: Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking References: <520D4ADB.50209@FreeBSD.org> <5224511D.4090503@FreeBSD.org> <20130903134251.GB43281@caravan.chchile.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: Outback Dingo , freebsd-geom@freebsd.org, "freebsd-current@freebsd.org" , freebsd-hackers@freebsd.org, FreeBSD SCSI X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Sep 2013 07:01:10 -0000 On 04.09.2013 00:48, Olivier Cochard-Labbé wrote: > On Tue, Sep 3, 2013 at 8:10 PM, Outback Dingo wrote: >> Can anyone confirm how well tested/stable this patch set might be?? if >> theres positive input i have a zoo of dev machines i could load it on, to >> help further it. >> Just checking to see how widely its been tested, > > I've installed this patch on 3 differents machines there status after > about 12hours: > - SUN FIRE X4170 M2 (amd64: r255178) with 6 SAS harddrives in one big > zraid (LSI MegaSAS Gen2 controller): Used for generating package with > poudriere… no probleme since; > - HAL/Fujitsu SPARC64-V (sparc64: r255178) with two SCSI-3 disks in > gmirror: Used for generating package with poudriere too… no probleme > since; I've forgot to mention, but GEOM direct dispatch is now active only on x86 because GET_STACK_USAGE macro now defined only there and I wanted to stay on a safe side. On other archs GEOM works in old queued way. Somebody should port that small macro to other archs. But that is still interesting data point. Thanks. > - HP EliteBook 8460p (amd64: r255188) with DVD replaced by a second > hardrive (where fbsd is installed): It crash just after the message > "GEOM: new disk ada1" during boot > > screenshot of the crash screen: > http://goo.gl/tW1VIx > > A little more information: > addr2line -e /boot/kernel/kernel.symbols 0xffffffff8083abd3 > /usr/src/sys/geom/geom_io.c:129 Unfortunately I can't reproduce that and have not enough clues. It may be specific to some GEOM class. Could you describe/show all GEOM topology, file systems, etc. you have there? gpart show sysctl kern.geom.confxml ... Thank you! -- Alexander Motin