From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261189AbVFTLfW (ORCPT ); Mon, 20 Jun 2005 07:35:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261201AbVFTLfW (ORCPT ); Mon, 20 Jun 2005 07:35:22 -0400 Received: from mx2.suse.de ([195.135.220.15]:32151 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S261189AbVFTLfR (ORCPT ); Mon, 20 Jun 2005 07:35:17 -0400 Date: Mon, 20 Jun 2005 13:35:11 +0200 Message-ID: From: Takashi Iwai To: Rafael =?ISO-8859-1?Q?Rodr=EDguez?= Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.12: codec_semaphore: semaphore is not ready In-Reply-To: <200506191402.02287.apt-drink@gulic.org> References: <200506191402.02287.apt-drink@gulic.org> 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 (beta18) (chestnut) (+CVS-20041021) (i386-suse-linux) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org At Sun, 19 Jun 2005 14:02:02 +0100, Rafael Rodríguez wrote: > > Hi. Since I upgraded to 2.6.12, i get messages like > > codec_semaphore: semaphore is not ready [0x1][0x > 301300] > codec_write 1: semaphoreis not ready for register 0x54 > > _randomly_ (meaning that in some boots it shows up, but in others doesn't) in > some init scripts (for example, alsa). This comes from either snd-intel8x0 or snd-intel8x0m. You can see the driver name when CONFIG_SND_DEBUG=y is set. If it's snd-intel8x0m (modem), you can ignore it unless you use the drvier indeed. If it's the former one (audio), it might be an ACPI problem. Try to tune acpi/pci boot option. Takashi