From owner-freebsd-bugs@FreeBSD.ORG Thu Jan 5 07:58:39 2006 Return-Path: X-Original-To: freebsd-bugs@FreeBSD.ORG Delivered-To: freebsd-bugs@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AA9116A41F for ; Thu, 5 Jan 2006 07:58:39 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 009E443D46 for ; Thu, 5 Jan 2006 07:58:38 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from [194.192.25.142] (spider.deepcore.dk [194.192.25.142]) by spider.deepcore.dk (8.13.4/8.13.4) with ESMTP id k057wLcr094841; Thu, 5 Jan 2006 08:58:25 +0100 (CET) (envelope-from sos@deepcore.dk) Message-ID: <43BCD19C.9050803@deepcore.dk> Date: Thu, 05 Jan 2006 08:58:20 +0100 From: =?UTF-8?B?U8O4cmVuIFNjaG1pZHQ=?= User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mikhail Teterin References: <200601050025.k050PHkq054535@freefall.freebsd.org> <200601042044.33084@aldan> In-Reply-To: <200601042044.33084@aldan> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.16 Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/71999: [ata] [panic] recurring panic in 4.10: ata_dmasetup: transfer active on this device! X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 07:58:39 -0000 Mikhail Teterin wrote: > On Wednesday 04 January 2006 07:25 pm, SЬren Schmidt wrote: > = Synopsis: [ata] [panic] recurring panic in 4.10: ata_dmasetup: > = transfer active on this device! > = > = State-Changed-From-To: open->closed > = State-Changed-By: sos > = State-Changed-When: Thu Jan 5 00:24:41 UTC 2006 > = State-Changed-Why: > = Upgrade to 6.0 or later. > > Is the fix available in the 4.x branch too? Otherwise, the PR is > not really closeable :-( Its not directly applicable to 4.x. To quote the PR pages: "A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned." As I do this in my spare time I have to prioritize my time, and I think its better spent on -current and 6.x. -Søren