linux-kernel - [regression, bisected] Xonar DX invalid PCI I/O range since 977d17bb174

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-next>] [day] [month] [year] [list]

Date:	Mon, 19 Apr 2010 08:56:09 +0200
From:	Clemens Ladisch <clemens@...isch.de>
To:	Yinghai Lu <yinghai@...nel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
CC:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [regression, bisected] Xonar DX invalid PCI I/O range since 977d17bb174

I got the following bug report:
| After upgrading kernel from 2.6.32 to 2.6.34-rc4 my Xonar DX stopped
| working. Kernel log has:
| 
| [kernel] AV200 0000:09:04.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
| [kernel] invalid PCI I/O range
| [kernel] AV200 0000:09:04.0: PCI INT A disabled
| [kernel] ALSA device list:
| [kernel]   No soundcards found.
| 
| According to git bisect the culprit is:
| 
| commit 977d17bb1749517b353874ccdc9b85abc7a58c2a
| Author: Yinghai Lu <yinghai@...nel.org>
| Date:   Fri Jan 22 01:02:24 2010 -0800
| PCI: update bridge resources to get more big ranges in PCI assign unssigned

Unfortunately, the bug tracker is dead, so I cannot ask for further
information.  (If somebody renews the domain, this report will be at
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4982>.)

The Xonar DX is a PCI chip with a 256-byte I/O range behind a PCI-E/PCI
bridge.  The driver code that caught this looks as follows:

	err = pci_enable_device(pci);
	...
	err = pci_request_regions(pci, DRIVER);
	...
	if (!(pci_resource_flags(pci, 0) & IORESOURCE_IO) ||
	    pci_resource_len(pci, 0) < OXYGEN_IO_SIZE) {
		snd_printk(KERN_ERR "invalid PCI I/O range\n");

Regards,
Clemens
--
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/