Arch Linux

danij3l

Member

From: Osijek, Croatia

Registered: 2007-12-08

Posts: 36

ALSA/snd_hda_intel problem

hi

on boot get delay of 10-15 sec and a looooot of lines in dmesg
sound is ok, but log is full of "hda-intel: spurious response 0x0:0x0, last cmd=0x0f0000"
on ASUS UL30Vt laptop, running Archlinux - kernel 2.6.35.2
if i blacklist snd-hda-intel delay is gone, but so is sound

here are some reports:
dmesg - http://pastebin.com/FAVRNQER
lsmod - http://pastebin.com/mwzNHkgw
lspci - http://pastebin.com/A5sPCaMv
alsa-info.sh - http://pastebin.com/if0W4CXe

TY for any incite or suggestions in advance.

danij3l

Last edited by danij3l (2010-08-24 22:39:19)

torpe23

Member

From: Paris, France

Registered: 2009-06-11

Posts: 24

Re: ALSA/snd_hda_intel problem

Same here, with asus ul30vt also..

laik

Member

Registered: 2010-10-07

Posts: 2

Re: ALSA/snd_hda_intel problem

I also have this problem (ul30vt)

fphillips

Member

From: Austin, TX

Registered: 2009-01-24

Posts: 202

Re: ALSA/snd_hda_intel problem

The word "spurious" in the kernel is usually associated with interrupts. Just before these messages there is

hda_intel: Disable MSI for Nvidia chipset

, but it's not clear if this is a suggestion or it has already been done. So this may be due to the (disabled) nvidia sound and interrupts.

cat /sys/module/snd_hda_intel/parameters/enable_msi

-1 is null (not set), 0 is false (disabled), 1 is true (enabled). Try booting with nomsi or

[fp@viron ~]$ cat /etc/modprobe.d/modprobe.conf 
#
# /etc/modprobe.d/modprobe.conf (for v2.6 kernels)
#
options snd-hda-intel enable_msi=0

to disable it if it isn't already.

Otherwise ask alsa developers on their list since I see this group have been asking here since at least July without any solution.

Last edited by fphillips (2010-10-14 20:52:46)

danij3l

Member

From: Osijek, Croatia

Registered: 2007-12-08

Posts: 36

Re: ALSA/snd_hda_intel problem

I think i have found solution:
blacklist nvidia-g210m-acpi in rc.conf
modprobe nvidia-g210m-acpi in rc.local
this moves it's loading further down the boot process
seems that this module is problematic. can anyone confirm?