linux-kernel - Re: Regressions: MSI vs HDA-Intel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hfx3nm1lh.wl%tiwai@suse.de>
Date:	Fri, 26 Mar 2010 18:31:22 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Torsten Kaiser <just.for.lkml@...glemail.com>
Cc:	Jaroslav Kysela <perex@...ex.cz>, alsa-devel@...a-project.org,
	linux-kernel@...r.kernel.org
Subject: Re: Regressions: MSI vs HDA-Intel

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/