linux-kernel - Re: PCI BAR1 Unassigned

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, 19 May 2011 12:50:35 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Jan Zwiegers <jan@...icalsystems.co.za>
Cc:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: PCI BAR1 Unassigned

On Thu, May 19, 2011 at 10:28 AM, Jan Zwiegers <jan@...icalsystems.co.za> wrote:
> I have the problem below where my PCI card's second BAR does not get
> assigned.
> What can be the cause of this problem?
> The last kernel I tested on which worked OK was 2.6.27.
> My current problematic kernel 2.6.35.
>
> 05:01.0 Unassigned class [ff00]: Eagle Technology PCI-703 Analog I/O Card
> (rev 5c)
>    Flags: bus master, slow devsel, latency 32, IRQ 22
>    Memory at 93b00000 (type 3, prefetchable) [size=2K]
>    Memory at <unassigned> (type 3, prefetchable)
>    Capabilities: [80] #00 [0600]
>    Kernel modules: pci703drv

Could be resource exhaustion or, more likely, we ran out because we
now assign resource to things that don't need them, leaving none for
things that *do* need them.  This sounds like a regression, so we
should open a bugzilla for it and attach dmesg logs from 2.6.27 and
2.6.35.

Does this problem keep the driver from working?  (Sometimes drivers
don't actually use all the BARs a device supports.)

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