Re: [Bug #15144] HDA Intel Audio hang on boot

[Sid Boyce]

On 15/02/10 12:53, Takashi Iwai wrote:
> At Mon, 15 Feb 2010 12:46:35 +0000,
> Sid Boyce wrote:
>>
>> On 15/02/10 07:12, yTakashi Iwai wrote:
>>> At Sun, 14 Feb 2010 20:29:01 +0000,
>>> Sid Boyce wrote:
>>>>
>>>> On 01/02/10 06:43, Takashi Iwai wrote:
>>>>> At Mon, 01 Feb 2010 02:01:21 +0000,
>>>>> Sid Boyce wrote:
>>>>>>
>>>>>> On 01/02/10 00:22, Rafael J. Wysocki wrote:
>>>>>>> This message has been generated automatically as a part of a report
>>>>>>> of recent regressions.
>>>>>>>
>>>>>>> The following bug entry is on the current list of known regressions
>>>>>>> from 2.6.32.  Please verify if it still should be listed and let me know
>>>>>>> (either way).
>>>>>>>
>>>>>>>
>>>>>>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15144
>>>>>>> Subject		: HDA Intel Audio hang on boot
>>>>>>> Submitter	: Sid Boyce <sboyce@xxxxxxxxxxxxxxxx>
>>>>>>> Date		: 2010-01-15 1:24 (17 days old)
>>>>>>> References	: http://marc.info/?l=linux-kernel&m=126351866722507&w=4
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Still not fixed in 2.6.33-rc6. Takashi wrote that the fix was scheduled
>>>>>> for 2.6.33-rc6, but it did not appear.
>>>>>
>>>>> It just slipped from rc6 due to my busy load.
>>>>> The pull request was sent yesterday.
>>>>>
>>>>>
>>>>> Takashi
>>>>>
>>>>
>>>> Up to 2.6.33-rc8 still needs the work around in
>>>> /etc/modprobe.d/50-sound.conf, so the kernel blacklist fix does not work.
>>>
>>> Check the kernel message.  Don't you have a message like "hda_intel:
>>> msi for device 1043:829c set to 0"?  Otherwise give alsa-info.sh
>>> again.
>>>
>> No mention of it - 2.6.33-rc8.
>> tindog:~ # dmesg|grep 1043
>> tindog:~ # grep 1043 /var/log/boot.msg
>> tindog:~ # grep 1043 /var/log/messages
>> tindog:~ #
>> The patch seems to be addressing the wrong  device, alsa-info.sh shows
>> it as
>>         Subsystem: 1043:81f6
>> Subsystem Id: 0x104381f6
>>   Components    : 'HDA:11d4198b,104381f6,00100300'
>>
>> tindog:/usr/src/linux-2.6.33-rc8 # grep 1043 ./sound/pci/hda/hda_intel.c
>>         SND_PCI_QUIRK(0x1043, 0x813d, "ASUS P5AD2", POS_FIX_LPIB),
>>         SND_PCI_QUIRK(0x1043, 0x1262, "ASUS W5Fm", 0x103),
>>         SND_PCI_QUIRK(0x1043, 0x81f2, "ASUS", 0), /* Athlon64 X2 + nvidia */
>>         SND_PCI_QUIRK(0x1043, 0x829c, "ASUS", 0), /* nvidia */
>>
>> I shall change the 0x81f2 to 0x81f6 and test.
> 
> Yes, please.  And update the bugzilla with the correct alsa-info.sh
> output, too.
> 
>>> But, essentially this is a problem of your mobo and Linux MSI
>>> handling, not exactly a driver issue, IMO...
>>>
>> I think you are correct, could be the motherboard or BIOS. I have tried
>> a number of BIOS versions with the same result. I am about to change to
>> a Asus Crosshair III motherboard in a few days when the memory arrives.
>> It also wouldn't boot if I have kgdb enabled in .config, I get a stream
>> of Traces with "Tainted".
>>
>>> I guess the problem will go away if you remove your another sound card
>>> on the PCI slot.  Or maybe it'd work even by moving to another
>>> slot...
>>>
>> It's the on-board sound. Before the work around I had to disable it in
>> the BIOS and use the USB sound card.
> 
> Hm, then I must I have checking really a different alsa-info.sh.
>
I went back and checked the first alsa-info.txt I sent.

My mistake this end, using ssh into that box, used scp to copy it to
this box and inadvertently provided the wrong alsa-info.txt which was
the one (1043:829c) for this box where email lives.
Sincere apologies for the mixup.
> 
> thanks,
> 
The change works, it should be "0x1043, 0x81f6" instead of 0x829c.
> Takashi
> 
Regards
Sid.


-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

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