From owner-freebsd-current@FreeBSD.ORG  Fri Aug 30 13:31:16 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id E874BDFD;
 Fri, 30 Aug 2013 13:31:16 +0000 (UTC) (envelope-from hps@bitfrost.no)
Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202])
 by mx1.freebsd.org (Postfix) with ESMTP id 9E034253B;
 Fri, 30 Aug 2013 13:31:16 +0000 (UTC)
Received: from mail.lockless.no (mail.lockless.no [46.29.221.38])
 by mta.bitpro.no (Postfix) with ESMTP id DF27E7A164;
 Fri, 30 Aug 2013 15:31:15 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by mail.lockless.no (Postfix) with ESMTP id 0D9F48F5134;
 Fri, 30 Aug 2013 15:31:29 +0200 (CEST)
X-Virus-Scanned: by amavisd-new-2.6.4 (20090625) (Debian) at lockless.no
Received: from mail.lockless.no ([127.0.0.1])
 by localhost (mail.lockless.no [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id EPy454qBpgSy; Fri, 30 Aug 2013 15:31:28 +0200 (CEST)
Received: from laptop015.home.selasky.org
 (cm-176.74.213.204.customer.telag.net [176.74.213.204])
 by mail.lockless.no (Postfix) with ESMTPSA id C58FB8F5135;
 Fri, 30 Aug 2013 15:31:27 +0200 (CEST)
Message-ID: <52209EEC.6060609@bitfrost.no>
Date: Fri, 30 Aug 2013 15:32:28 +0200
From: Hans Petter Selasky <hps@bitfrost.no>
Organization: Bitfrost A/S
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130522 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Lundberg, Johannes" <johannes@brilliantservice.co.jp>
Subject: Re: xhci broken on 10-CURRENT and 2013 MacBook Air?
References: <CAASDrV=_8XDFZqcVP7aHdgEwxtMEDyNDQAyM5dgPmJ6=toOpow@mail.gmail.com>
 <CAASDrVmyduRKwsp5oURYuHX8G4hoODn0TftbC5MfV=3XhhocrA@mail.gmail.com>
 <521B9CD7.8010902@bitfrost.no>
 <CAASDrVk5xjptRPttbQA6b7Tg_Pgf005EqMQpUhv-jNje+352+A@mail.gmail.com>
 <521C6C26.7050207@bitfrost.no>
 <CAASDrVnJj4+khHB-StW3JpVuCqZx7MBcmqA59_Ay-06Jgu5PnQ@mail.gmail.com>
 <CAASDrVk4eWVLj0=VHygKk5iG9Zd0tSwNkqLX+LJjP=mD_LRrUw@mail.gmail.com>
 <52203EC9.4060808@bitfrost.no>
 <CAASDrVnwKOwqAVAu19gExpNvPYcwXo1V+g=kVbnZWq5ic4NDvA@mail.gmail.com>
 <52207030.8050107@bitfrost.no>
 <CAASDrV=xi-qW-8tpYK-pyhh5xh7n90sy7s4uE3W405jgDkCcaw@mail.gmail.com>
 <52208F63.4060308@bitfrost.no>
 <CAASDrV=oOv2aDvikU=wWc85ATBy3f0TnbqxA_s=pPRu9Y4Jmsw@mail.gmail.com>
In-Reply-To: <CAASDrV=oOv2aDvikU=wWc85ATBy3f0TnbqxA_s=pPRu9Y4Jmsw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Alexander Motin <mav@freebsd.org>,
 FreeBSD Current <freebsd-current@freebsd.org>,
 "freebsd-usb@freebsd.org" <freebsd-usb@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
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: Fri, 30 Aug 2013 13:31:17 -0000

On 08/30/13 15:19, Lundberg, Johannes wrote:
> Hi Hans
>
> I tried that too and no change... But, the variable overflow you
> introduced, it is never increased, right? So, it will never become zero...
>

It will become zero when it wraps. Maybe 2**32 is too long. You could 
add a printf while it is running, and see if it goes == 1000000 for example.

--HPS

> Johannes Lundberg
> BRILLIANTSERVICE CO., LTD. <http://www.brilliantservice.co.jp>
>
>
> On Fri, Aug 30, 2013 at 2:26 PM, Hans Petter Selasky <hps@bitfrost.no>wrote:
>
>> On 08/30/13 13:54, Lundberg, Johannes wrote:
>>
>>> Still got the same behaviour after applying the patch...
>>>
>>> Johannes Lundberg
>>> BRILLIANTSERVICE CO., LTD. <http://www.brilliantservice.**co.jp<http://www.brilliantservice.co.jp>