All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Jan Zwiegers <jan@radicalsystems.co.za>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: PCI BAR1 Unassigned
Date: Thu, 19 May 2011 12:50:35 -0600	[thread overview]
Message-ID: <BANLkTi=g=fKaXF4uwwjLSX-R+pk0FUa6OQ@mail.gmail.com> (raw)
In-Reply-To: <sig.9120f46b2d.4DD5452F.9050108@radicalsystems.co.za>

On Thu, May 19, 2011 at 10:28 AM, Jan Zwiegers <jan@radicalsystems.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

  reply	other threads:[~2011-05-19 18:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 16:28 PCI BAR1 Unassigned Jan Zwiegers
2011-05-19 18:50 ` Bjorn Helgaas [this message]
2011-05-19 20:27   ` Jan Zwiegers
2011-05-19 20:50     ` Xianghua Xiao
2011-05-20  7:42       ` Jan Zwiegers
2011-05-20 14:53         ` Bjorn Helgaas
2011-05-20 15:09           ` Jan Zwiegers
2011-05-20 15:57             ` Bjorn Helgaas
2011-05-24 10:22           ` Jan Zwiegers
2011-05-24 12:35             ` Bjorn Helgaas
2011-05-26 20:38               ` Bjorn Helgaas
2011-05-31  3:02                 ` Bjorn Helgaas
2011-06-01 14:36                   ` Jan Zwiegers
2011-05-19 22:13     ` Bjorn Helgaas
2011-05-19 22:20       ` Jan Zwiegers
2011-05-19 22:38         ` Bjorn Helgaas
2011-05-19 22:49           ` Jan Zwiegers
2011-05-20  7:13           ` Jan Zwiegers

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='BANLkTi=g=fKaXF4uwwjLSX-R+pk0FUa6OQ@mail.gmail.com' \
    --to=bhelgaas@google.com \
    --cc=jan@radicalsystems.co.za \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.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.