From owner-freebsd-current@freebsd.org Fri Aug 19 11:06:25 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24CACBBF4B9 for ; Fri, 19 Aug 2016 11:06:25 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9739B19FC; Fri, 19 Aug 2016 11:06:24 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: by mail-lf0-x233.google.com with SMTP id f93so30363369lfi.2; Fri, 19 Aug 2016 04:06:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=8bEjMhNwRJ5uIy1L0e9plEh1ns8rsURspIjM3EAjL18=; b=WLhkDCeQzsSNlNs9oYYmJ4ZdUSbtXxDlq0Z4N8ZjVnprNIq+y66wyT6SxNPHINAxZS cNnsF0x0AqWA1BvrUXRvQW3puRAWEn0hfljva7uN8qq/OSsAp3fCqdphtIvuy+njyJkq XBqF4s+LEn46UIQJg/S6lvvD6Gecae+5QLiSlG9YQpsrs6NRGaWRNJKX5jNGYH6v/LTV CkoS7mJV7OdSfdt+q5PypgLlA2Eio9f0rLN1ye060hYA7e0RKfX8ev4jOQLvT4gtHWD9 sqcLKrbtKDyQKfr5ZxaGS55QHG+UzKb0cEIO93xYvbG/OQDJJKzBcYuDP54zN3CvNVbO UqVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=8bEjMhNwRJ5uIy1L0e9plEh1ns8rsURspIjM3EAjL18=; b=YwTvJfcCB/a7a1FEbsM/HyYfBloy/A37aA+gGfOT0OScBqJV9UfTMTG5x2OZpeFdOE 7k+1Cn9/bpV8Q1+gd/K6hCq2zWBJTpjlpUliQC4jX72GBh79uB4xRL4BAP639zFHEvFx s9PFsq8Ak/55FHuqBKXs2XK4wKqQvawIrUaySerpIYeN/E18XfG9dGIxVqcrjqP25+7C MMzDdyykdrcbcSTDi9PP7YG8AIKnaqgKnL40rsbhdM9/+s+dTuimSg3EHEDV6L4aZe1r F1VPKgIuySeI4gne/ZUnyzyFja+XG8AUjAHm2p0J3eM7SkyfpQLGa6crtaTrYsZbNCQw No+Q== X-Gm-Message-State: AEkoouuW2kJuU/AbKUlqsDNI2ech1RZhbw4tgIBxuz6AEAl/sz1dt/2O0dbTW1K43zlXgw== X-Received: by 10.46.5.6 with SMTP id 6mr1873105ljf.66.1471604782559; Fri, 19 Aug 2016 04:06:22 -0700 (PDT) Received: from mavbook.mavhome.dp.ua ([134.249.139.101]) by smtp.gmail.com with ESMTPSA id 65sm1127860ljb.48.2016.08.19.04.06.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Aug 2016 04:06:21 -0700 (PDT) Sender: Alexander Motin Subject: Re: ahci timeout during boot on a particular mobo To: Andriy Gapon , FreeBSD Current References: <4fed11f6-533d-4ec3-81ea-9d326dcb1f45@FreeBSD.org> From: Alexander Motin Message-ID: <2a643c9d-db5b-5cb0-e429-8eadba4fea79@FreeBSD.org> Date: Fri, 19 Aug 2016 14:06:20 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <4fed11f6-533d-4ec3-81ea-9d326dcb1f45@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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: Fri, 19 Aug 2016 11:06:25 -0000 On 19.08.16 11:30, Andriy Gapon wrote: > So, what's suspicious here is that we discover two AHCI channels on the JMicron > device and we seem to discover some sort of a device on one of them. But the > communication with that (phantom?) device times out and that causes a very long > delay during the boot. This fake device is the most interesting part. Marvell AHCI RAID chips in such way expose RAID management device, but I doubt that JMicron is so advanced, at least it seems like not implemented properly enough. > Is there a way to fix the boot delay? > > Searched for JMB361 in the source code, looked at some nearby device entries, > and - is it as simple as adding AHCI_Q_1CH quick for this device? AHCI_Q_1CH quirk was added for early Marvell chips that were ever dirtier mix of legacy ATA and AHCI, that reported total number of ports instead of expected AHCI ones. May be JMB361 is also like that, but I never had those check. JMB362 I have does not have this problem, reporting two real SATA ports, even though it has one legacy PATA port also. I don't have strong objections against this quirk. I am not sure whether it is right solution, but suppose that in couple years nobody will bother about that hardware at all. -- Alexander Motin