[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B50915E.8000308@blueyonder.co.uk>
Date: Fri, 15 Jan 2010 16:01:34 +0000
From: Sid Boyce <sboyce@...eyonder.co.uk>
To: "Rafael J. Wysocki" <rjw@...k.pl>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: HDA Intel Audio hang on boot
With the PCI Audigy card in, the box wouldn't even enter POST, either
the Audigy is bad (unknown - from a box that couldn't see the drives) or
there is something faulty on the motherboard. I am currently running
2.6.33-rc4-git2 on the box with a Terratec Aureon 5.1 USB MK II sound card.
Regards
Sid.
On 15/01/10 01:24, Sid Boyce wrote:
> Renaming this bug as the "only 1 CPU" bug has been fixed, but the hang
> at HDA remains.
> I shall plug in a SB Audigy and see if it will boot with that.
> By disabling the on-board HDA Intel audio in the BIOS, the system boots.
> 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"
>
> Regards
> Sid.
>
> On 11/01/10 03:39, Sid Boyce wrote:
>> On 10/01/10 22:32, 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=14946
>>> Subject : All kernels after 2.6.32-git10 show only 1 CPU
>>> Submitter : Sid Boyce <sboyce@...eyonder.co.uk>
>>> Date : 2009-12-23 16:55 (19 days old)
>>> References : http://marc.info/?l=linux-kernel&m=126158734326801&w=4
>>>
>>>
>>>
>>>
>>
>> With 2.6.33-rc3-git3 I now see 2 CPU's every on a normal boot, but its
>> locking up solid at this part of the boot process as usual.
>> ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
>> HDA Intel 0000:00:0e.1: PCI INT B -> Link[AAZA] -> GSI 22 (level, low)
>> -> IRQ 22.
>> With acpi=noirq (2 CPU's)
>> ================
>> kvm: Nested Virtualization enabled.
>> IT8716 Super IO detected
>> Parport_PC 00:0a: reported by plug and Play ACPI
>> Parport 0: PC-Style at 0x378, irq 7 [PCSPP, TRISTATE,EPP]
>> parport: irq 7 in use, resorting to polled operation
>> HDA Intel 0000:00:0e.1: PCI -> APIC IRQ transform: INT B -> IRQ 11
>>
>> With acpi=ht (1 CPU)
>> =============
>> Hangs at:-
>> Loading drivees, configuring devices do_IRQ: 0.65 No irq handler for
>> vector (irq -1)
>>
>> With acpi=off (2 CPU's)
>> ========================
>> Hangs at same point as with acpi=noirq.
>>
>> 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists