linux-kernel - Re: x86/pci Oops with CONFIG_SND_HDA

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: <4BF42786.2080603@oracle.com>
Date:	Wed, 19 May 2010 11:01:42 -0700
From:	Yinghai <yinghai.lu@...cle.com>
To:	Graham Ramsey <ramsey.graham@...world.com>
CC:	Bjorn Helgaas <bjorn.helgaas@...com>, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org
Subject: Re: x86/pci Oops with CONFIG_SND_HDA_INTEL

On 05/19/2010 10:16 AM, Graham Ramsey wrote:
> On 19/05/10 17:44, Bjorn Helgaas wrote:
>> On Wednesday, May 19, 2010 09:13:24 am Graham Ramsey wrote:
>>   
>>> I am on x86_64 with latest (v2.6.34) kernel. When i set
>>> CONFIG_SND_HDA_INTEL=Y It hangs at an early stage in boot with kernel
>>> oops.
>>> When i use CONFIG_SND_HDA_INTEL=M the machine will boot, and i get the
>>> dmesg (below).
>>>
>>> I have bisected down to one commit that causes the problem:
>>>
>>>     commit 3e3da00c01d050307e753fb7b3e84aefc16da0d0
>>>     x86/pci: AMD one chain system to use pci read out res
>>>     ...
>>>      
>> I CC'd Yinghai, the author of that patch.  That commit went in after
>> 2.6.33, so this is probably a regression between .33 and .34.  Can
>> you open a report at https://bugzilla.kernel.org and respond to this
>> thread with the URL?
>>
>> Please attach the complete dmesg (with SND_HDA_INTEL=m) to the
>> bugzilla.
>>
>> Thanks a lot for your report!
>>

please send out bootlog with pci=earlydump.

looks like your system have a very sick BIOS, 

system have two HT chains.

PCI: Probing PCI hardware (bus 00)
...
PCI: Discovered primary peer bus 80 [IRQ]


rt to non-coherent only set one link:
node 0 link 0: io port [1000, ffffff]
TOM: 0000000080000000 aka 2048M
node 0 link 0: mmio [e0000000, efffffff]
node 0 link 0: mmio [a0000, bffff]
node 0 link 0: mmio [80000000, ffffffff]
bus: [00, ff] on node 0 link 0

YH
--
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/