From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932348AbWA3PwX (ORCPT ); Mon, 30 Jan 2006 10:52:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932349AbWA3PwX (ORCPT ); Mon, 30 Jan 2006 10:52:23 -0500 Received: from ns1.suse.de ([195.135.220.2]:13522 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S932348AbWA3PwW (ORCPT ); Mon, 30 Jan 2006 10:52:22 -0500 Date: Mon, 30 Jan 2006 16:52:12 +0100 Message-ID: From: Takashi Iwai To: Martin Michlmayr Cc: Atsushi Nemoto , hugh@veritas.com, linux-kernel@vger.kernel.org, t.sailer@alumni.ethz.ch, perex@suse.cz, ralf@linux-mips.org Subject: Re: ALSA on MIPS platform In-Reply-To: <20060130154617.GC15563@deprecation.cyrius.com> References: <20060128.004540.59467062.anemo@mba.ocn.ne.jp> <20060130.185608.30186596.nemoto@toshiba-tops.co.jp> <20060130154617.GC15563@deprecation.cyrius.com> User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 MULE XEmacs/21.5 (beta21) (corn) (+CVS-20050720) (i386-suse-linux) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org At Mon, 30 Jan 2006 15:46:17 +0000, Martin Michlmayr wrote: > > * Takashi Iwai [2006-01-30 11:18]: > > Well, as Hugu pointed out, that page reservation plays no longer any > > role. The patch below should work too on 2.6.15 or later. > > It doesn't solve the problem I have, those "wait source ready timeout > 0x1410 [0x8c8c8c8c]" messages on a Cobalt Qube2 with a 64-bit MIPS > kernel. Of course not. Your problem is totally irrelevant with the page allocation stuff we discussed. > wait source ready timeout 0x1410 [0x8c8c8c8c] <- repeated 180 times > AC'97 0 analog subsections not ready > wait source ready timeout 0x1410 [0x8c8c8c8c] <- repeated 453 times > snd-ens1371: loaded successfully The messages above imply that the h/w access doesn't work properly, e.g. the wrong PCI resource assignment or the insufficient initialization. Takashi