From owner-freebsd-current@FreeBSD.ORG Mon Sep 29 12:38:09 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4568716A4B3 for ; Mon, 29 Sep 2003 12:38:09 -0700 (PDT) Received: from procyon.firepipe.net (procyon.firepipe.net [198.78.66.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD6C643F75 for ; Mon, 29 Sep 2003 12:38:08 -0700 (PDT) (envelope-from will@csociety.org) Received: by procyon.firepipe.net (Postfix, from userid 1000) id 3673320A65; Mon, 29 Sep 2003 12:38:08 -0700 (PDT) Date: Mon, 29 Sep 2003 12:38:08 -0700 From: Will Andrews To: Soren Schmidt Message-ID: <20030929193808.GT72999@procyon.firepipe.net> Mail-Followup-To: Soren Schmidt , freebsd-current@FreeBSD.ORG References: <61180692781.20030929202947@buz.ch> <200309291913.h8TJDmCI013173@spider.deepcore.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200309291913.h8TJDmCI013173@spider.deepcore.dk> User-Agent: Mutt/1.4.1i cc: freebsd-current@FreeBSD.ORG Subject: Re: SiL3112 SATA (RAID) Controller drives aren't working at all. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2003 19:38:09 -0000 X-List-Received-Date: Mon, 29 Sep 2003 19:38:09 -0000 On Mon, Sep 29, 2003 at 09:13:48PM +0200, Soren Schmidt wrote: > First off, there is ONLY support for Promise and HPT "soft RAID" > in the ATA driver, other vendors products are *not* supported (yet). > > Second, there seem to be a problem with some sil3112 setups where > timeouts and what not ruins the lunch, but so far I've not been > able to reproduce.. I am still unable to use my SATA drive, it's probed incorrectly as I posted earlier. Reverting to the August 10th 00:00 UTC kernel fixes this problem, so I concluded that ATAng broke this. If it makes any difference, my model is a SiI3112 RAID controller, but I only have one drive and it probes as ad4... the situation doesn't improve any if I add "ataraid". But maybe ATAng doesn't take into account the difference between a "normal" and a "RAID" SiI 3112, if any? Here are my dmesg's again (Sep 18th, Aug 10th kernels): http://csociety.org/~will/dmesg.badATAng http://csociety.org/~will/dmesg.Aug10.preATAng The problem shown in the first dmesg still showed itself when I tried a new kernel on Sep 25th. Regards, -- wca