From owner-freebsd-arm@FreeBSD.ORG Mon Jul 6 09:46:21 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B81591065677 for ; Mon, 6 Jul 2009 09:46:21 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (backbone.deglitch.com [IPv6:2001:16d8:fffb:4::abba]) by mx1.freebsd.org (Postfix) with ESMTP id 737248FC0C for ; Mon, 6 Jul 2009 09:46:21 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from stasss.yandex.ru (dhcp170-227-red.yandex.net [95.108.170.227]) by mx0.deglitch.com (Postfix) with ESMTPSA id D1B9F8FC27; Mon, 6 Jul 2009 13:46:19 +0400 (MSD) Date: Mon, 6 Jul 2009 13:46:12 +0400 From: Stanislav Sedov To: Michal Hajduk Message-Id: <20090706134612.5cf860e4.stas@FreeBSD.org> In-Reply-To: <4A51BFF6.4090401@semihalf.com> References: <4A51BFF6.4090401@semihalf.com> Organization: The FreeBSD Project X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Mon__6_Jul_2009_13_46_12_+0400_6BfucpCp+E3UrWB8" Cc: tinguely@casselton.net, freebsd-arm@freebsd.org Subject: Re: pmap problem in FreeBSD current X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jul 2009 09:46:22 -0000 --Signature=_Mon__6_Jul_2009_13_46_12_+0400_6BfucpCp+E3UrWB8 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 06 Jul 2009 11:12:22 +0200 Michal Hajduk mentioned: > Hello Mark, >=20 > While testing EHCI (FreeBSD 8-current with new USB-stack) on > ARM machine I have found some problem probably related to > svn commit *194459*=20 > http://svn.freebsd.org/viewvc/base?view=3Drevision&revision=3D194459 > With compiled USB-stack I had vm_fault: >=20 Hi, Michal! This is the known problem and we currently working on fixing it. It looks like that r194459, while certainly good, uncovered a memory corruption problem in ARM code. As a workaround you can revert r194459 for now. --=20 Stanislav Sedov ST4096-RIPE --Signature=_Mon__6_Jul_2009_13_46_12_+0400_6BfucpCp+E3UrWB8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJKUcfqAAoJEKN82nOYvCd0rUQQALFk77UjxaHliEdmkBOeGXUj qpP+3MTmC6RRAzaZqzvF2nf9PMNUSv7pIPbwOLo2m+wtSYzpdpVcyGLXOJR/7mMn Qdwlye8YHd3h4880W47F19R5yzl8S+mHmG913/wjaemiE3f8HL2wpTQmaP2pEvNt T4fYRsXD+oJiXpnnXJWdEk4EE1tCU3hru2mGxxahZP7d+vOx4jr5KAMAaiHO6NDo dX7LJspXXUR5G3TNDdE9OLH/bcM/NDbRtjWWR+JbfJz28m12bcRBBsAD3oBCGYFM q9jyC3Ta3wxYmIKQZX+FV+llWeia/ZNmxocdEfiE0mXW6QR0iMBtp/84h73+faUj +beRFJ+FLaCgjXDRn+Q7V3Jkdd03dyMCgEEg8VzsFM0qmL7ERhtKKlbPm6ZURfEz M+hN55TcM0EzzetXAFPmtZfU5oh1hWpA+gYP0bxx7dgH4dfpkFPAB4yBENihbBgE W74JQXVGPNV0bjo4aBu6veSxGLSwhLKiYu/JTVcZyql3jqTIz2gcD+w4nU2hvKxh M6KZGFAiZvnIjnthX7ZLJSs641slT/eFdlMyuUlvzIf0qipDoLr3GA5MPyDK2b3O UeF5KvfRD0NPJ9CtffwixoFy2oD4UKWv17mMdkR2kPm0wMxngsdS1iOwkM4u3eTR k+8vgY4JgwKL6kR47KIO =vLHp -----END PGP SIGNATURE----- --Signature=_Mon__6_Jul_2009_13_46_12_+0400_6BfucpCp+E3UrWB8--