From owner-freebsd-questions@FreeBSD.ORG Sat Jan 27 17:19:37 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7B2A616A400 for ; Sat, 27 Jan 2007 17:19:37 +0000 (UTC) (envelope-from thadman08@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 1AF6213C487 for ; Sat, 27 Jan 2007 17:19:36 +0000 (UTC) (envelope-from thadman08@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so1439264nfc for ; Sat, 27 Jan 2007 09:19:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=l8a5q2tg8jLY2td090ROn6bF9t5gZ/OoVHN8k4W36UOUt7w9FBHHxaeqwt47SIxSf/z9vV3eittqk8ChZkW8Y1kD9chk6Qo6Snz8JZWrCFIy4GKtX0AAu68PTnyV7et2ZEJ6dQO+V/VtwGpCi7XdcjvbF43E6P584vMffVpe8Z8= Received: by 10.49.8.16 with SMTP id l16mr1689701nfi.1169916803359; Sat, 27 Jan 2007 08:53:23 -0800 (PST) Received: by 10.49.37.14 with HTTP; Sat, 27 Jan 2007 08:53:23 -0800 (PST) Message-ID: Date: Sat, 27 Jan 2007 11:53:23 -0500 From: "Thaddeus Quintin" To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Issues with mpt driver X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2007 17:19:37 -0000 Hey everyone. I'm trying to get an install done of FreeBSD 6.2 on a Dell PowerEdge SC1435 w/ a Dell SAS 5 adapter (Made by LSI). The mpt driver detects this correctly, but as soon as I do something that involves a stream of disk activity (like update the ports tree), it goes into a frenzy, reporting a constant stream of- Attempting to abort req [REQ INFO] abort of req [REQ INFO] completed into the syslog. This is an AMD Opteron system and I've tried it with AMD64 and i386 and both have the same result. Are there any immediate, obvious solutions for such a thing? Even a complicated solution would be ok at this point! What other information might I need to provide to help you out? Thanks to all- Thaddeus