From owner-freebsd-questions@FreeBSD.ORG Sat Nov 13 14:51:27 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 667A71065675 for ; Sat, 13 Nov 2010 14:51:27 +0000 (UTC) (envelope-from freebsd.user@seibercom.net) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 152B28FC2B for ; Sat, 13 Nov 2010 14:51:26 +0000 (UTC) Received: by yxe1 with SMTP id 1so397976yxe.13 for ; Sat, 13 Nov 2010 06:51:26 -0800 (PST) Received: by 10.150.177.15 with SMTP id z15mr6005541ybe.247.1289659886074; Sat, 13 Nov 2010 06:51:26 -0800 (PST) Received: from scorpio.seibercom.net (cpe-071-077-039-064.nc.res.rr.com [71.77.39.64]) by mx.google.com with ESMTPS id m12sm1664090ybn.0.2010.11.13.06.51.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 13 Nov 2010 06:51:25 -0800 (PST) Received: from scorpio (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: FreeBSD.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id E467BE5487D for ; Sat, 13 Nov 2010 09:51:23 -0500 (EST) Date: Sat, 13 Nov 2010 09:51:23 -0500 From: Jerry To: FreeBSD Message-ID: <20101113095123.202b5558@scorpio> In-Reply-To: References: Organization: seibercom.net X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; amd64-portbld-freebsd8.1) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: JMicron JMB363 PCIe controler doesn't work X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Nov 2010 14:51:27 -0000 On Sat, 13 Nov 2010 14:58:03 +0100 (CET) Wojciech Puchar articulated: > > I have motherboard with total 8 SATA ports but seems it's broken as > > i'm having regular server hangs after heavy disk I/O, usually with > > messages about disconnected AHCI device. cables ARE OK. > > > > i bought extra controllers - 2 2-port PCIe based on said chipset. > > > > to make things more strange - 2 of 8 motherboard SATA ports ARE > > JMB363 based too! > > > > on motherboard ports are all detected by AHCI driver. > > > > THE same chips on cards are NOT detected as AHCI. > > pciconv shows they are in ATA/RAID mode. > > > > But builtin controller BIOS does not allow setting it in AHCI mode. > > tried ata/atadisk driver - it doesn't attach disk at all, but just > > waits 15 seconds on each port where disk is connected at boot. > > > > Disks ARE properly attached, as cards BIOS shows them up properly. > > > > > > How can FreeBSD be set up to simply force switching to AHCI mode on > > that chips? > > nobody knows? or just this mail was missed within hundreds of trash > about why devil is a mascot or tips for installing windows. Except for the "top Posting" (corrected) faux pas, that is the best answer I have seen here in quite awhile. -- Jerry ✌ FreeBSD.user@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ When the going gets tough, the tough go shopping.