From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 10:28:03 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0A9F16A41F for ; Tue, 29 Nov 2005 10:28:03 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D25143D5D for ; Tue, 29 Nov 2005 10:28:02 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 73C161FFDD4; Tue, 29 Nov 2005 11:28:00 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id C99E21FFAD1; Tue, 29 Nov 2005 11:27:57 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 68465444F6B; Tue, 29 Nov 2005 10:22:30 +0000 (UTC) Date: Tue, 29 Nov 2005 10:22:30 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Dmitry Malkin In-Reply-To: <98f0db4a0511290217m69c812c8rc74ec0e9538eb2f9@mail.gmail.com> Message-ID: <20051129101619.F23990@maildrop.int.zabbadoz.net> References: <200511252005.jAPK5qTo097801@www.freebsd.org> <98f0db4a0511290217m69c812c8rc74ec0e9538eb2f9@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/89549: [amd64] nve timeouts on 6.0-release X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2005 10:28:03 -0000 On Tue, 29 Nov 2005, Dmitry Malkin wrote: > is there no fix yet? > mb it fixed in 7.0-current? depends on how much of the problem you are seeing. If it used to work for some time before you were seeing the timeouts things might be better now and some more patches have been posted to current@ I think for testing. If it simply didn't work at all it still won't. Might be a problem of specific hardware but as long as nobdoy has detailed information from nvidia I'd expect that we will not be able to fix that easily. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT