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]
Date:	Thu, 12 Mar 2009 20:36:30 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org
Subject:  Re: How can PCI resource allocation fail?

Christian P. Schmidt wrote:
> Hi all,
> 
> I'm toying with the alsa-driver for the Creative Labs X-Fi. I'm working on the PCI Express version of this card, though, which is
> the same as the PCI version plus a PCIe to PCI bridge but has a different ID:
> 
>           +-1c.2-[0000:03-04]----00.0-[0000:04]----00.0  1102:0009
> 
> 03:00.0 PCI bridge: Creative Labs Device 7006
> 04:00.0 Audio device: Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG
> 
> Now, after adding the ID, the driver fails:
> 
> [46833.487579] CA0106 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> [46833.487586] CA0106 0000:04:00.0: PCI INT A disabled
> [46833.487588] cannot allocate the port
> [46833.487594] CA0106: probe of 0000:04:00.0 failed with error -16
> 
> The actual error is occurring in
> 
> 	chip->port = pci_resource_start(pci, 0);
> 	chip->res_port = request_region(chip->port, pci_resource_len(pci,0), "snd_ca0106");
> 	if (!chip->res_port) {
> 		snd_ca0106_free(chip);
> 		printk(KERN_ERR "cannot allocate the port\n");
> 		return -EBUSY;
> 	}
> 
> This from /proc/iomem:
> 
> f9f00000-f9ffffff : PCI Bus 0000:03
>   f9f00000-f9ffffff : PCI Bus 0000:04
>     f9ffc000-f9ffffff : 0000:04:00.0
> 
> Some additional debug output tells me that the code is actually trying to allocate 16k starting from f9ffc000. What could be
> potential reasons for the failure? Do I have to do something with the bridge before I can try to request the region?

request_region is requesting IO ports. The PCI BAR on the card is MMIO 
memory, not IO ports, so request_mem_region has to be used. It's 
possible that this driver isn't set up to handle MMIO space.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ