From owner-freebsd-bugs@FreeBSD.ORG Sun Apr 15 21:00:16 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B5BF516A406 for ; Sun, 15 Apr 2007 21:00:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 60F1C13C44C for ; Sun, 15 Apr 2007 21:00:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l3FL0Gco065048 for ; Sun, 15 Apr 2007 21:00:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3FL0GIe065045; Sun, 15 Apr 2007 21:00:16 GMT (envelope-from gnats) Date: Sun, 15 Apr 2007 21:00:16 GMT Message-Id: <200704152100.l3FL0GIe065045@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Alex Trull Cc: Subject: Re: kern/90206: [ata] [crash] Server reboot after "FAILURE - out of memory in ata_raid_init_request" X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alex Trull List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Apr 2007 21:00:16 -0000 The following reply was made to PR kern/90206; it has been noted by GNATS. From: Alex Trull To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/90206: [ata] [crash] Server reboot after "FAILURE - out of memory in ata_raid_init_request" Date: Sun, 15 Apr 2007 21:30:30 +0100 I see the opener of this PR no longer has a valid email address. I am experiencing the same symptoms on 6.2-Release amd64 + sil raid1. Can I help at all by providing dumps or access to a developer to my system ? If anyone is interested in solving this bug I would be happy to donate hardware (I checked the request list and no developer has asked for an ata raid1 card + hdds to test this with). This issue does not appear to be universal (atleast, it doesn't appear to be fixed yet so I imagine it isn't universal). I get these errors from nightly periodic filesystem checks on a system with multiple jails - the IO of each jail performing its periodics within the same few minutes causes the errors to show up in dmesg and an occasional reboot. Regards, Alex Trull