From owner-freebsd-current@FreeBSD.ORG Sat Sep 28 07:34:43 2013 Return-Path: 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 03C4BDDE; Sat, 28 Sep 2013 07:34:43 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B02212DF3; Sat, 28 Sep 2013 07:34:42 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) with esmtp (envelope-from ) id <1VPp30-001kCp-OA>; Sat, 28 Sep 2013 09:34:38 +0200 Received: from f052240096.adsl.alicedsl.de ([78.52.240.96] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) with esmtpsa (envelope-from ) id <1VPp30-002hqy-JJ>; Sat, 28 Sep 2013 09:34:38 +0200 Date: Sat, 28 Sep 2013 09:34:38 +0200 From: "O. Hartmann" To: Scott Long Subject: Re: r255873: ahcich7: Timeout on slot 0 port 0 FLOODING kernel messages Message-ID: <20130928093438.78b4bd8e@thor.walstatt.dyndns.org> In-Reply-To: <49D7E568-C260-4F68-8382-DAE3F5B451BE@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> <20130927170753.3f171e91@telesto> <49D7E568-C260-4F68-8382-DAE3F5B451BE@samsco.org> Organization: FU Berlin X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/AoXU+Q5XoEzCa0Eo8HFyXdg"; protocol="application/pgp-signature" X-Originating-IP: 78.52.240.96 Cc: Konstantin Belousov , "Sergey V. Dyatko" , Boris Samorodov , gahr@FreeBSD.org, FreeBSD CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 28 Sep 2013 07:34:43 -0000 --Sig_/AoXU+Q5XoEzCa0Eo8HFyXdg Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 28 Sep 2013 01:10:08 -0600 Scott Long wrote: >=20 > On Sep 27, 2013, at 9:07 AM, O. Hartmann > 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 Yes, it did. Oliver. --Sig_/AoXU+Q5XoEzCa0Eo8HFyXdg Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (FreeBSD) iQEcBAEBAgAGBQJSRoaOAAoJEOgBcD7A/5N8JnQH/jePI76BAb9NmiqjDvAAg4d0 FhdGUKQfNUSL5TLQh3BBKLQxmISdr2xWEPAbAotpae/1fUc5blpknk93YPm/GCAP wkqKTgEOFD9G4iVARmjM7AQMj4ZOcsfjrQAVrQ63UUF/HR8orzFUrPDakPH5WicG YRVL6f+o3819pelTeaVW+4IOe/1w8uNZt2P9SbLQW7xkdrmMvoPxjJSOYaXfiIRB U8DqwGlL6RGD3TmrdkO6znk+bfo8jV6TpBYpEepJV0qCUxFw9Pz7aIpd/yd8OLEc ZUatlQUqxx4FtxU0LwX+T0TB07Ljh6zrFmME7d4AOrstHLTMfVa6lXe+walsX2g= =veXk -----END PGP SIGNATURE----- --Sig_/AoXU+Q5XoEzCa0Eo8HFyXdg--