From: Clemens Ladisch <clemens@ladisch.de>
To: Yinghai Lu <yinghai@kernel.org>, Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [regression, bisected] Xonar DX invalid PCI I/O range since 977d17bb174
Date: Mon, 19 Apr 2010 08:56:09 +0200 [thread overview]
Message-ID: <4BCBFE89.9070401@ladisch.de> (raw)
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@kernel.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
next reply other threads:[~2010-04-19 6:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 6:56 Clemens Ladisch [this message]
2010-04-19 7:44 ` [regression, bisected] Xonar DX invalid PCI I/O range since 977d17bb174 Peter Henriksson
2010-04-19 8:06 ` Clemens Ladisch
2010-04-19 8:42 ` Peter Henriksson
[not found] ` <4BCCA5FD.6060002@oracle.com>
2010-04-19 19:42 ` Peter Henriksson
2010-04-20 6:41 ` Yinghai
2010-04-20 8:03 ` Peter Henriksson
2010-04-20 17:22 ` Yinghai Lu
2010-04-20 18:45 ` Peter Henriksson
2010-04-21 6:06 ` Yinghai
2010-04-21 9:06 ` Peter Henriksson
2010-04-21 15:54 ` Jesse Barnes
2010-05-10 19:07 ` Peter Henriksson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BCBFE89.9070401@ladisch.de \
--to=clemens@ladisch.de \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.