From owner-freebsd-stable@FreeBSD.ORG Tue Jan 24 16:18:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F8E116A41F; Tue, 24 Jan 2006 16:18:07 +0000 (GMT) (envelope-from freebsd@azimut-tour.ru) Received: from azimutprint.ru (azimutprint.ru [217.15.145.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA99C43D5E; Tue, 24 Jan 2006 16:18:06 +0000 (GMT) (envelope-from freebsd@azimut-tour.ru) Received: from azimutprint.ru (localhost [127.0.0.1]) by crom.azimutprint.ru (Postfix) with ESMTP id 197C9B8AC; Tue, 24 Jan 2006 19:18:04 +0300 (MSK) Received: from [192.168.1.2] (greencomp.azimutprint.ru [192.168.1.2]) by crom.azimutprint.ru (Postfix) with ESMTP id 8887DB89B; Tue, 24 Jan 2006 19:18:02 +0300 (MSK) Message-ID: <43D65339.90709@azimut-tour.ru> Date: Tue, 24 Jan 2006 19:18:01 +0300 From: GreenX FreeBSD User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Michael Butler References: <43D09224.2050304@azimut-tour.ru> <43D4EDDA.8060901@protected-networks.net> <43D5BBA3.8070606@azimut-tour.ru> <43D62265.8020401@protected-networks.net> In-Reply-To: <43D62265.8020401@protected-networks.net> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org, greenx@azimutprint.ru, sos@freebsd.org Subject: Re: panic: kmem_malloc X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2006 16:18:07 -0000 Hi, Has applied this patch, has rebuild the world and also used kernel GENERIC with little changes. Has tried a little to test, copied on a network in two streams mp3 collections in total volume about 40G. Periodically checked these variable. Like it's OK, Big human thanks:) Below I bring quotations where variable USED strongly differed from zero, but it was not often and she always in the end was nulled. [skip] # sysctl -a | grep ^ata_ ata_composit: 196, 0, 6, 34, 76424 ata_request: 200, 0, 12, 26, 159617 [skip] # sysctl -a | grep ^ata_ ata_composit: 196, 0, 7, 33, 99189 ata_request: 200, 0, 14, 43, 205497 [skip] # sysctl -a | grep ^ata_ ata_composit: 196, 0, 79, 41, 115195 ata_request: 200, 0, 158, 70, 237653 [skip] # sysctl -a | grep ^ata_ ata_composit: 196, 0, 46, 74, 130415 ata_request: 200, 0, 92, 136, 268260 [skip] # sysctl -a | grep ^ata_ ata_composit: 196, 0, 11, 29, 189552 ata_request: 200, 0, 22, 35, 387287 [skip] root@crom# sysctl -a | grep ^ata_ ata_composit: 196, 0, 0, 40, 190637 ata_request: 200, 0, 0, 38, 389460 Michael Butler пишет: > GreenX FreeBSD wrote: > >> #sysctl -a | grep ^ata >> ata_composit: 192, 0, 22663, 617, 65421 >> ata_request: 200, 0, 45326, 1015, 468333 > > Right - this is a symptom of a memory leak in the ATA raid driver .. > >> But, I little cvsup system. >> #uname -a >> FreeBSD crom.azimutprint.ru 6.0-STABLE FreeBSD 6.0-STABLE #0: Mon Jan >> 23 11:18:32 MSK 2006 -skip- > > .. which has not been merged from current. It should look like .. > > ITEM SIZE LIMIT USED FREE REQUESTS > [ .. ] > ata_composit: 196, 0, 0, 320, 2039342 > ata_request: 200, 0, 0, 437, 9260705 > ^^^^