From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 16 17:27:22 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FBCD1065675 for ; Mon, 16 Feb 2009 17:27:22 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from mx04.pub.collaborativefusion.com (mx04.pub.collaborativefusion.com [206.210.72.84]) by mx1.freebsd.org (Postfix) with ESMTP id 189DC8FC2B for ; Mon, 16 Feb 2009 17:27:21 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from [192.168.2.164] ([206.210.89.202]) by mx04.pub.collaborativefusion.com (StrongMail Enterprise 4.1.1.4(4.1.1.4-47689)); Mon, 16 Feb 2009 11:38:10 -0500 X-VirtualServerGroup: Default X-MailingID: 00000::00000::00000::00000::::1 X-SMHeaderMap: mid="X-MailingID" X-Destination-ID: freebsd-hardware@freebsd.org X-SMFBL: ZnJlZWJzZC1oYXJkd2FyZUBmcmVlYnNkLm9yZw== Message-ID: <49999672.6020801@comcast.net> Date: Mon, 16 Feb 2009 11:38:10 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: "Brian A. Seklecki" References: <1234363891.15909.35.camel@ompc.insign.local> <1234366709.3500.62.camel@ingress.ws.pitbpa0.priv.collaborativefusion.com> <1234794122.22023.76.camel@ompc.insign.local> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: spolyack@gmail.com, Olivier Mueller , freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: poweredge 1850 won't boot 7.1? maybe LSI-related : amr0: adapter is busy X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 17:27:22 -0000 Brian A. Seklecki wrote: > NOTE: You're using the 4e/Si, which we have as well. We're experiencing > random crashes on the 1850/8th gen, as a result of a (believed) DMA bug > introduced into 7.x > > Just to note, we are only seeing these issues in combination with megarc (/usr/ports/sysutils/megarc) monitoring.