linux-kernel - Re: [Alsa-devel] HDA Intel sound driver fails on Acer notebook

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: <s5hfybcfbz8.wl%tiwai@suse.de>
Date:	Tue, 19 Dec 2006 10:53:31 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Chuck Ebbert <76306.1226@...puserve.com>
Cc:	alsa-devel <alsa-devel@...a-project.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Alsa-devel] HDA Intel sound driver fails on Acer notebook

Hi,

sorry for the late reply since I've been on vacation.

At Sun, 3 Dec 2006 02:30:34 -0500,
Chuck Ebbert wrote:
> 
> The HDA Intel sound driver still fails to load on my Acer Aspire 5102
> notebook (Turion64 X2, ATI chipset):
> 
> Here is the PCI info while running x86_64.  I tried i386 and x86_64 and it fails
> on both:
> 
> 00:14.2 Audio device: ATI Technologies Inc Unknown device 437b (rev 01)
>         Subsystem: Acer Incorporated [ALI] Unknown device 009f
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64, Cache Line Size 08
>         Interrupt: pin ? routed to IRQ 16
>         Region 0: Memory at c0000000 (64-bit, non-prefetchable) [size=16K]
>         Capabilities: [50] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>         Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
>                 Address: 0000000000000000  Data: 0000
> 00: 02 10 7b 43 06 00 10 04 01 00 03 04 08 40 00 00
> 10: 04 00 00 c0 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 25 10 9f 00
> 30: 00 00 00 00 50 00 00 00 00 00 00 00 0a 00 00 00
> 40: 00 00 02 40 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 01 60 42 c8 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 05 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 
> On i386 I get this after doing
>         insmod snd-hda-codec.ko ;  insmod snd-hda-intel.ko
> 
> Dec  1 17:38:29 ac kernel: ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 18
> Dec  1 17:38:29 ac kernel: codec_mask = 0xb
> Dec  1 17:38:30 ac kernel: hda_codec: PCI 1025:9f, codec config 5 is selected
> Dec  1 17:38:31 ac kernel: hda_intel: azx_get_response timeout, switching to polling mode...
> Dec  1 17:38:32 ac kernel: hda_intel: azx_get_response timeout, switching to single_cmd mode...

These messages are scary.  It means that the communication between the
controller chip and the codec chip doesn't work, usually incorrect IRQ
handling, and often due to broken BIOS or ACPI support.  Any change if
you pass pci=noacpi or acpi=off boot option?

Anyway, you can try alsa-git patch in mm tree.  It's a better support
code for Acer laptops, and this might work slightly differently.


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/