From owner-freebsd-drivers@FreeBSD.ORG Sun May 15 16:22:32 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 208FE1065670 for ; Sun, 15 May 2011 16:22:32 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from mailout-us.gmx.com (mailout-us.gmx.com [74.208.5.67]) by mx1.freebsd.org (Postfix) with SMTP id BF5238FC0C for ; Sun, 15 May 2011 16:22:31 +0000 (UTC) Received: (qmail 18578 invoked by uid 0); 15 May 2011 16:22:30 -0000 Received: from 67.206.162.54 by rms-us012.v300.gmx.net with HTTP Content-Type: text/plain; charset="utf-8" Date: Sun, 15 May 2011 16:22:28 +0000 From: "Dieter BSD" Message-ID: <20110515162230.227510@gmx.com> MIME-Version: 1.0 To: mav@freebsd.org X-Authenticated: #74169980 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 Content-Transfer-Encoding: 8bit X-GMX-UID: /8X5BJcf5lfwf0uIAnFpxEtCNzg2NUKc Cc: freebsd-drivers@freebsd.org Subject: Re: Siis(4) does not play well with others! :-( X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 May 2011 16:22:32 -0000 > For now, I can only say that you are still running not the latest driver > version. Latest have some delays reduced and report connect time in > "us". May be some more of remaining could be replaced with interrupts > (specifically on siis hardware), but I need to think and experiment more > with it. I was able to swap cables and put that disk on the JMB363 controller. (directly, no port multiplier) I now just get read errors from the disk and a "error = 5" message from g_vfs_done(), but no messages from ahci(4) at all, and no other problems. So much for testing the disk before putting it into service.  I read the entire disk, then wrote the entire disk with 0x00, 0xff, 0x55 and 0xaa, reading it back each time into hexdump -C.  Put it into service, and after 82 GB of real data (on a 2 TB drive) it fails.  grumble My todo list: 1) Build new kernel with the latest siis(4) and achi(4) bits. 2) Test if a read error causes achi(4) to lock out Ethernet for too long. 3) Test with achi(4) with and without a port multiplier. 3) Test with siis(4) with and without a port multiplier. > Generally, the situation when the system doesn't reboot with the reset > button doesn't smell good to me. FreeBSD does something that disables the soft power switch.  I don't recall if I've had problems with reset before.  Stopping the PM LEDS blinking but not doing a full reset seems pretty odd.  Something important must not be getting reset.  I thought Tyan's mainboards were supposed to be "tier 1".  :-( I'm still puzzled that one Ethernet responded to ping but another did not.