linux-kernel - Re: BAR 0: can't allocate resource

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

Message-Id: <201001051600.14982.bjorn.helgaas@hp.com>
Date:	Tue, 5 Jan 2010 16:00:13 -0700
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Alex Brooks <a.brooks@...athon-robotics.com>
Cc:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: BAR 0: can't allocate resource

On Tuesday 05 January 2010 03:19:47 pm Alex Brooks wrote:
> > > I have a problem getting a couple of PCI cards to play nicely together.
> > > ...
> > >
> > > And (for both kernels) the output of lspci has the following line:
> > >   01:04.0 Unclassified device [0080]: Device 0002:0080
> >
> > When you have only the 8-port serial card installed, it appears at
> > 01:04.0.  When you have both cards installed, we don't see a new device,
> > and whatever is at 01:04.0 no longer looks like the octal UART.
> 
> I'm pretty sure that it is the octal UART, but it isn't being recognised 
> properly.

I'm sure it *is* the UART, but we're getting the wrong data back from
it, so we can't use it.  The Mini PCI adapter must be interfering with
the UART board somehow.  Since you said the Mini PCI slot on the adapter
is empty, and the jumpers are programmed correctly, I suspect the adapter
is broken.  Maybe a connector problem?  Do you have another one that
behaves the same way?

If you put a Mini PCI card in the slot and try this in a system without
the UART card, does the Mini PCI card work correctly?  The jumpers on
the adapter should determine the PCI bus number where the Mini PCI device
appears.

> To test this theory, I tried with (a) no cards at all, and (b)  
> just the MiniPCI adapter (no serial card) -- nothing else appears at 01:04.0 
> (output of lspci attached).

The PC/104+ to Mini PCI adapter looks like it's completely passive.  It
should be invisible to the OS, so it won't appear in lspci.  For both
cases, the lspci output you attached is exactly what I would expect.

I don't see any indication that this is a software problem (I know nothing
about PC/104, so let me know if you disagree, and why).

> > If so, both of those web pages mention jumpers that set the card's
> > PCI device ("slot") number.  My guess is that both of your cards
> > are set to the same number.
> 
> I'd already looked for this, I'm certain I have the jumpers right (I tried 
> intentionally setting them incorrectly, the failure mode is different).

How did you set them, and what was the failure?  If the adapter is really
passive and the Mini PCI slot is empty, it seems strange that the adapter
jumper setting would make any difference at all.

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/