From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757415AbYEEHwp (ORCPT ); Mon, 5 May 2008 03:52:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754084AbYEEHwh (ORCPT ); Mon, 5 May 2008 03:52:37 -0400 Received: from www.tglx.de ([62.245.132.106]:50356 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753273AbYEEHwg (ORCPT ); Mon, 5 May 2008 03:52:36 -0400 Date: Mon, 5 May 2008 09:49:51 +0200 (CEST) From: Thomas Gleixner To: Andrey Panin cc: Glauber Costa , Hugh Dickins , linux-visws-devel@lists.sourceforge.net, "J.A. Magall??n" , Ingo Molnar , Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: Problems with -git14 In-Reply-To: <20080505071300.GA3456@pazke.donpac.ru> Message-ID: References: <20080430015655.5a42f63d@werewolf.home> <4818962D.4040906@redhat.com> <20080505071300.GA3456@pazke.donpac.ru> User-Agent: Alpine 1.10 (LFD 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 5 May 2008, Andrey Panin wrote: > > However, since this problem was raised, I'm still concerned that visws may > > have the same problem, since it uses the same logic that i386 mach_default > > used to. (and I did not touched, since x86_64 code went int o > > mach_default). > > > > Could anyone with access to such hardware give it a try ? > > Unfortunately, no. Visws port is in non-bootable state currently, 2.6.25 hangs > in calibrate_delay_direct() and I still do not know why :( What was the last kernel which booted on visws ? Thanks, tglx