From owner-freebsd-current@FreeBSD.ORG  Sat Sep 28 08:06:04 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 A7D39B07;
 Sat, 28 Sep 2013 08:06:04 +0000 (UTC)
 (envelope-from scottl@samsco.org)
Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6E4D721E9;
 Sat, 28 Sep 2013 08:06:04 +0000 (UTC)
Received: from [127.0.0.1] (Scott4long@pooker.samsco.org [168.103.85.57])
 (authenticated bits=0)
 by pooker.samsco.org (8.14.5/8.14.5) with ESMTP id r8S8605W075379;
 Sat, 28 Sep 2013 02:06:01 -0600 (MDT)
 (envelope-from scottl@samsco.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: r255873: ahcich7: Timeout on slot 0 port 0 FLOODING kernel
 messages
From: Scott Long <scottl@samsco.org>
In-Reply-To: <20130928093438.78b4bd8e@thor.walstatt.dyndns.org>
Date: Sat, 28 Sep 2013 02:06:00 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9CD49A1-7DDF-44BB-9BFB-895EA3206D56@samsco.org>
References: <20130926085326.72b53660@thor.walstatt.dyndns.org>
 <20130926154026.4be04064@laptop.minsk.domain>
 <20130926130718.GH41229@kib.kiev.ua>
 <20130927083647.39956586@laptop.minsk.domain>
 <977CE1C1-B96C-4553-8C08-0077E1738496@samsco.org>
 <20130927145251.6532d339@laptop.minsk.domain>
 <0B95678C-4C3A-4234-B2EA-77156ED905B9@samsco.org>
 <20130927125934.GA87559@gahrfit.gahr.ch> <52458A41.6040004@passap.ru>
 <E7A06817-FAD4-4B3A-9BBA-BB4EB6C10FF8@samsco.org>
 <20130927170753.3f171e91@telesto>
 <49D7E568-C260-4F68-8382-DAE3F5B451BE@samsco.org>
 <20130928093438.78b4bd8e@thor.walstatt.dyndns.org>
To: "O. Hartmann" <ohartman@zedat.fu-berlin.de>
X-Mailer: Apple Mail (2.1510)
Cc: Konstantin Belousov <kostikbel@gmail.com>,
 "Sergey V. Dyatko" <sergey.dyatko@gmail.com>, Boris Samorodov <bsam@passap.ru>,
 gahr@FreeBSD.org, FreeBSD CURRENT <freebsd-current@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: Sat, 28 Sep 2013 08:06:04 -0000


On Sep 28, 2013, at 1:34 AM, O. Hartmann <ohartman@zedat.fu-berlin.de> =
wrote:

> On Sat, 28 Sep 2013 01:10:08 -0600
> Scott Long <scottl@samsco.org> wrote:
>=20
>>=20
>> On Sep 27, 2013, at 9:07 AM, O. Hartmann
>> <ohartman@zedat.fu-berlin.de> wrote:
>>=20
>>>>>>=20
>>>>>> reverting those two commits solved the issue.
>>>>>=20
>>>>> In my case just rebuilding and restarting of sysutils/hal helped.
>>>>=20
>>>>=20
>>>> Interesting.  I didn't test hal, probably should have.  The compat
>>>> shims I put in place should have made it work without a rebuild.  I
>>>> wonder if it's somehow corrupting kernel state.  Are others who are
>>>> experiencing problems also running the hal package?
>>>>=20
>>>> Scott
>>>>=20
>>>=20
>>> Yes, I do ... I just rebuild HAL and wait for rebooting the systems
>>> affected ...
>>=20
>> DId this fix the problem?
>>=20
>> Scott
>=20
>=20
> Yes, it did.
>=20
> Oliver.

Thanks.  It sounds like the bug is in the compat shims I wrote, not the =
primary work.  I'll look into it.

Scott