From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752965Ab0CZRbZ (ORCPT ); Fri, 26 Mar 2010 13:31:25 -0400 Received: from cantor.suse.de ([195.135.220.2]:34970 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751426Ab0CZRbY (ORCPT ); Fri, 26 Mar 2010 13:31:24 -0400 Date: Fri, 26 Mar 2010 18:31:22 +0100 Message-ID: From: Takashi Iwai To: Torsten Kaiser Cc: Jaroslav Kysela , alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org Subject: Re: Regressions: MSI vs HDA-Intel In-Reply-To: <64bb37e1003261025l14e2d82r64ba1e90d024bea6@mail.gmail.com> References: <64bb37e1003261025l14e2d82r64ba1e90d024bea6@mail.gmail.com> User-Agent: Wanderlust/2.15.6 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.7 Emacs/23.1 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) 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 List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At Fri, 26 Mar 2010 18:25:22 +0100, Torsten Kaiser wrote: > > I have two systems that use the alsa hda-intel driver, both show > regressions in relation to MSI. > > System 1: Athlon(tm) X2 BE-2400 with an AMD RS690/SB600 chipset > 00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel > HDA) [1002:4383] > (Mainboard is a MSI MS-7368) > > After upgrading from 2.6.31 to 2.6.33 I get a delay during bootup: > [ 1.155925] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, > low) -> IRQ 16 > [ 1.159143] input: AT Translated Set 2 keyboard as > /devices/platform/i8042/serio0/input/input2 > [ 1.232595] firewire_core: created device fw0: GUID 00dc10000129c48f, S400 > [ 1.252677] hda_codec: ALC888: BIOS auto-probing. > [ 1.259226] HDA Intel 0000:01:05.2: PCI INT B -> GSI 19 (level, > low) -> IRQ 19 > [ 1.260293] HDA Intel 0000:01:05.2: irq 27 for MSI/MSI-X > [ 1.314712] input: GenPS/2 Genius Mouse as > /devices/platform/i8042/serio1/input/input3 > [ 4.322508] hda-intel: azx_get_response timeout, switching to > polling mode: last cmd=0x000f0000 > [ 5.332508] hda-intel: No response from codec, disabling MSI: last > cmd=0x000f0000 > [ 6.342508] hda-intel: Codec #0 probe error; disabling it... > [ 7.392508] hda_intel: azx_get_response timeout, switching to > single_cmd mode: last cmd=0x000f0000 > [ 7.430464] ALSA device list: > [ 7.431549] #0: HDA ATI SB at 0xfe7f4000 irq 16 > [ 7.432656] #1: HDA ATI HDMI at 0xfe9e8000 irq 27 > > 2.6.34-rc2 does not boot on this system, something related to the new > bootmem allocator, so I can't say if this might already be fixed for > 2.6.34. > > Should the system be blacklisted like the two Asus Athlon X2 boards, > or is this some other bug? If it happens on 2.6.33 and enable_msi=0 solves the issue, then yes, we should put them on the blacklist. > System 2: Opteron(tm) 2218 with an nVidia MCP55 chipset > 00:06.1 Audio device [0403]: nVidia Corporation MCP55 High Definition > Audio [10de:0371] (rev a2) > (Mainboard is an ASUS KFN5-D SLI) > > Commit 80c43ed724797627d8f86855248c497a6161a214 disabled MSI for this > system, but the MSI mode was working fine for all 2.6.33 versions I > used. > > Should the generic blacklist disable MSI for all Athlon X2 instead of > all nNvidia chipsets? Well, it's not clear yet. I don't bet that non-athlon would have any problem. So I keep it still disabled for Nvidia controllers. You can put it in the whitelist instead. thanks, Takashi