From owner-freebsd-current@FreeBSD.ORG Wed Apr 18 20:52:37 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 076AA16A402 for ; Wed, 18 Apr 2007 20:52:37 +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 C14CB13C457 for ; Wed, 18 Apr 2007 20:52:36 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l3IKpwBv040973; Wed, 18 Apr 2007 14:51:58 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <462684E0.20105@samsco.org> Date: Wed, 18 Apr 2007 14:51:44 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 MIME-Version: 1.0 To: "Gelsema, P (Patrick)" References: <200704162247.29909.gelsemap@superhero.nl> <16295.195.50.100.20.1176825375.squirrel@www.superhero.nl> <4624F4C3.30006@samsco.org> <200704182222.32069.gelsemap@superhero.nl> In-Reply-To: <200704182222.32069.gelsemap@superhero.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Wed, 18 Apr 2007 14:51:58 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: Difference between 6.2 and 7.0 Adaptec 39320D - 7.0 performing less X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2007 20:52:37 -0000 Gelsema, P (Patrick) wrote: > On Tuesday 17 April 2007 18:24, Scott Long wrote: >> Gelsema, P (Patrick) - FreeBSD wrote: >>> On Tue, April 17, 2007 16:45, Scott Long wrote: >>>> Gelsema, P (Patrick) - FreeBSD wrote: >>> >>> >>>> The 39320D is a finicky card. I don't recall putting in the code that >>>> would downshift the speed like this, but it wouldn't surprise me if it >>>> is a side effect of the system going slower. Anyways, it sounds like >>>> you're a good candidate/victim for the MPSAFE locking changes that I >>>> just made to the SCSI layer and the ahc/ahd drivers. Would you mind >>>> testing it out (just update to the latest 7-CURRENT sources) and let me >>>> know how it works for you? > > >>> Is building world/kernel sufficient as test or do you want me to do more >>> tests? >> Any amount of testing that you can do is appreciated. Even verifying >> that it boots is helpful =-) > > Cvsupped this evening at about 6.15 UTC time (20:15 CET zone) > FreeBSD hulk.superhero.nl 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Wed Apr 18 > 21:56:58 CEST 2007 root@hulk.superhero.nl:/usr/obj/usr/src/sys/GENERIC > amd64 > > After buildworld and the whole lot the computer boots fine, however the disk > is still detected as only 160.00MB/s. > > I do get the following crash. It seems to be related to pressing scroll lock > on the console and hitting the page up/down buttons. When I just log on > locally or remotely it seems to be ok. When I hit the scroll lock key before > or after logging on I get the below crash. > > Apr 18 22:08:22 hulk kernel: lock order reversal: (Giant after non-sleepable) > Apr 18 22:08:22 hulk kernel: 1st 0xffffff007b413358 ahd_lock (ahd_lock) > @ /usr/src/sys/cam/cam_periph.c:559 > Apr 18 22:08:22 hulk kernel: 2nd 0xffffffff80977f20 Giant (Giant) > @ /usr/src/sys/vm/vm_contig.c:590 > Apr 18 22:08:22 hulk kernel: KDB: stack backtrace: > Apr 18 22:08:22 hulk kernel: db_trace_self_wrapper() at > db_trace_self_wrapper+0x3a > Apr 18 22:08:22 hulk kernel: witness_checkorder() at witness_checkorder+0x4f9 > Apr 18 22:08:22 hulk kernel: _mtx_lock_flags() at _mtx_lock_flags+0x75 > Apr 18 22:08:22 hulk kernel: contigmalloc() at contigmalloc+0x63 > Apr 18 22:08:22 hulk kernel: bus_dmamem_alloc() at bus_dmamem_alloc+0x8d > Apr 18 22:08:22 hulk kernel: ahd_alloc_scbs() at ahd_alloc_scbs+0x32a > Apr 18 22:08:22 hulk kernel: ahd_get_scb() at ahd_get_scb+0x69 > Apr 18 22:08:22 hulk kernel: ahd_action() at ahd_action+0x47c > Apr 18 22:08:22 hulk kernel: xpt_run_dev_sendq() at xpt_run_dev_sendq+0x1ae > Apr 18 22:08:22 hulk kernel: xpt_action() at xpt_action+0x4d3 > Apr 18 22:08:22 hulk kernel: dastart() at dastart+0x211 > Apr 18 22:08:22 hulk kernel: xpt_run_dev_allocq() at xpt_run_dev_allocq+0xf4 > Apr 18 22:08:22 hulk kernel: dastrategy() at dastrategy+0x78 > Apr 18 22:08:22 hulk kernel: g_disk_start() at g_disk_start+0xe6 > Apr 18 22:08:22 hulk kernel: g_io_schedule_down() at g_io_schedule_down+0x189 > Apr 18 22:08:22 hulk kernel: g_down_procbody() at g_down_procbody+0x7a > Apr 18 22:08:22 hulk kernel: fork_exit() at fork_exit+0xaa > Apr 18 22:08:22 hulk kernel: fork_trampoline() at fork_trampoline+0xe > Apr 18 22:08:22 hulk kernel: --- trap 0, rip = 0, rsp = 0xffffffffac102d30, > rbp = 0 --- > > Is this information sufficient? If not please let me know what more is > required. > > Rgds, > > Patrick > Thanks for the info. Fixing this problem is going to be a royal pain. You can probably get around it by disabling WITNESS and INVARIANTS. Scott