Re: HDA Intel Audio hang on boot

Takashi Iwai
2010-01-26T06:58:57Z

At Tue, 26 Jan 2010 07:40:03 +0100,
I wrote:
>
> At Tue, 26 Jan 2010 00:59:15 +0000,
> Sid Boyce wrote:
> >
> > On 25/01/10 21:55, Takashi Iwai wrote:
> > > At Mon, 25 Jan 2010 22:54:23 +0100,
> > > I wrote:
> > >>
> > >> At Mon, 25 Jan 2010 22:39:02 +0100,
> > >> Rafael J. Wysocki wrote:
> > >>>
> > >>> On Monday 25 January 2010, Sid Boyce wrote:
> > >>>> On 15/01/10 01:24, Sid Boyce wrote:
> > >>>> This is the only outstanding bug. No problems up 2.6.32-git1, but I get
> > >>>> a solid lock-up on 2.6.32-git2 through 2.6.33-rc5 if the on-board audio
> > >>>> is not disabled in the BIOS.
> > >>>
> > >>> I guess we should let Takashi know.
> > >>
> > >> Thanks.
> > >>
> > >>>>> tindog:~ # uname -r
> > >>>>> 2.6.33-rc4-smp
> > >>>>> On 2.6.32-git1 which boots, hwinfo shows:-
> > >>>>> oss.card_id = 'HDA NVidia'
> > >>>>> oss.card_id = 'HDA NVidia'
> > >>>>> oss.card_id = 'HDA NVidia'
> > >>>>> alsa.card_id = 'HDA NVidia'
> > >>>>> alsa.card_id = 'HDA NVidia'
> > >>>>> alsa.card_id = 'HDA NVidia'
> > >>>>> alsa.card_id = 'HDA NVidia'
> > >>>>> info.product = 'HDA NVidia ALSA hardware specific Device'
> > >>>>> alsa.card_id = 'HDA NVidia'
> > >>>>> info.product = 'HDA NVidia ALSA Control Device'
> > >>>>> alsa.card_id = 'HDA NVidia'
> > >>>>> info.product = 'HDA NVidia Sound Card'
> > >>>>> sound.card_id = 'HDA NVidia'
> > >>>>> info.linux.driver = 'HDA Intel'
> > >>>>> 22: 489835 578 IO-APIC-fasteoi sata_nv, HDA Intel
> > >>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
> > >>>>> HDA Intel: module = snd_hda_intel
> > >>>>> irq:0 22 ( 490413) "sata_nv" "HDA Intel"
> > >>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
> > >>>>> HDA Intel: module = snd_hda_intel
> > >>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
> > >>>>> HDA Intel: module = snd_hda_intel
> > >>>>> E: DRIVER=HDA Intel
> > >>>>> <6>HDA Intel 0000:00:0e.1: PCI INT B -> Link[AAZA] -> GSI 22 (level,
> > >>>>> low) -> IRQ 22
> > >>>>> <7>HDA Intel 0000:00:0e.1: setting latency timer to 64
> > >>>>> Driver: "HDA Intel"
> > >>
> > >> What I'd try first is to pass enable_msi=0 option.
> > >
> > > Just to be sure -- it's an option for snd-hda-intel module.
> > >
> > >
> > > Takashi
> > >
> >
> > I passed "modprobe snd-hda-intel enable_msi=0" on the kernel command
> > line,

Oh, I overlooked this text. Of course, this can't work :)

"modprobe..." isn't for the kernel command line but for modprobe
configs, usually specified in /etc/modprobe.d/* file.

And... is this report for 2.6.32 or for 2.6.33?
If it's with 2.6.32, enable_msi=1 may help instead.

Takashi