From owner-freebsd-current@FreeBSD.ORG  Sun Sep 28 07:10:02 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 6568BB17;
 Sun, 28 Sep 2014 07:10:02 +0000 (UTC)
Received: from srv56-45.cdn.bestreaming.com (srv56-46.cdn.bestreaming.com
 [204.140.16.4])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D745FC55;
 Sun, 28 Sep 2014 07:10:00 +0000 (UTC)
Received: from mail.yourbox.net (localhost [127.0.0.1])
 by srv56-45.cdn.bestreaming.com (8.14.5/8.14.5) with ESMTP id s8S79umP007143; 
 Sun, 28 Sep 2014 07:09:56 GMT (envelope-from fbl@aoek.com)
From: "=?UTF-8?Q?Jos=C3=A9_P=C3=A9rez_Arauz?=o" <fbl@aoek.com>
To: Warner Losh <imp@bsdimp.com>, Adrian Chadd <adrian@freebsd.org>
Subject: Re: AHCI after 271145 does not work for me
Date: Sun, 28 Sep 2014 09:09:51 +0200
Message-Id: <20140928070425.M39629@aoek.com>
In-Reply-To: <D49FC8F7-2EC4-4C3F-A4E4-563F26B8C177@bsdimp.com>
References: <20140925153725.M29130@beckpeccoz.com>
 <CAJ-Vmo=VFiU9PqGea2Cn4S+z8Zio0HyVWKdLgCzYUJV1mKuV7w@mail.gmail.com>
 <D49FC8F7-2EC4-4C3F-A4E4-563F26B8C177@bsdimp.com>
X-Mailer: OpenWebMail 2.53 
X-OriginatingIP: 213.37.0.220 (ame)
MIME-Version: 1.0
Content-Type: text/plain;
	charset=utf-8
Cc: freebsd-current <freebsd-current@freebsd.org>,
 Warner Losh <imp@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Sep 2014 07:10:02 -0000

Hi Warner,
it's not AHCI, it's something else I am trying to track down. Sorry for thinking it was AHCI,
the kernel loops at the latest probe, which happens to be AHCI, but if I remove that from
the kernel it loops on something else (usb, clock, whatever).


Cheers,




On Thu, 25 Sep 2014 17:55:09 -0700, Warner Losh wrote
> I’m afraid I have no clue. I’ll need hardware to debug this, since I 
> don’t have any, or someone that can provide some feedback or even 
> probe messages with it going off the rails (before/after).
> 
> Warner
> 
> On Sep 25, 2014, at 9:12 AM, Adrian Chadd <adrian@freebsd.org> wrote:
> 
> > Hi!
> > 
> > 271146 was Warner's AHCI probe/attach changes. Maybe he'll have some ideas. :)
> > 
> > Warner?
> > 
> > 
> > -a
> > 
> > 
> > On 25 September 2014 08:48, José Pérez Arauzo <fbl@aoek.com> wrote:
> >> Hi,
> >> on my Acer Aspire V5, AHCI does not complete device_attach after 271145.
> >> 
> >> Am I the only one experiencing this? Can I help fixing it? Thank you.
> >> 
> >> BR,
> >> 
> >> --
> >> José Pérez Arauzo
> >> 
> >> _______________________________________________
> >> freebsd-current@freebsd.org mailing list
> >> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


--
José Pérez Arauzo