From owner-freebsd-stable@FreeBSD.ORG Sun Oct 22 09:32:37 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 1C46216A494; Sun, 22 Oct 2006 09:32:37 +0000 (UTC) (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 A044E43D5F; Sun, 22 Oct 2006 09:32:28 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from [194.192.25.130] (sos.deepcore.dk [194.192.25.130]) by spider.deepcore.dk (8.13.6/8.13.4) with ESMTP id k9M9WQll019799; Sun, 22 Oct 2006 11:32:27 +0200 (CEST) (envelope-from sos@deepcore.dk) Message-ID: <453B3AAB.6060407@deepcore.dk> Date: Sun, 22 Oct 2006 11:32:27 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 1.5.0.2 (X11/20060531) MIME-Version: 1.0 To: Jon Passki References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v2.0beta Cc: Matthew Dettinger , freebsd-stable@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: Panic on "DOH! ata_alloc_request failed!" 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: Sun, 22 Oct 2006 09:32:37 -0000 Jon Passki wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hey all, > > (I'm off list, please include me in any replies) > > (Søren, please let me know if you do not want to be emailed in the > future directly! You seem to be the ATA RAID FreeBSD goto guy. > Apologies if you did not want to be solicited). > > I just received a panic w/ this in /var/log/messages (uname and dmesg > at the end of the email / book): > > Oct 21 04:17:05 prometheus kernel: DOH! ata_alloc_composite failed! I fixed a few nits in this area after 6.1-RELEASE, so you should upgrade to 6-stable or 6.2-betasomething to get this fixed. -Søren