From: Martin Burnicki <martin.burnicki@meinberg.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: PCI card not accessible; I/O ports at <ignored>
Date: Wed, 18 Jan 2012 19:27:13 +0100 [thread overview]
Message-ID: <4F170F01.9090602@meinberg.de> (raw)
In-Reply-To: <CAErSpo6Ei=XgWTXp6f=UgY90QA78fSVMaJ8Gf7NvF5fMiPX12w@mail.gmail.com>
Bjorn Helgaas wrote:
> On Wed, Jan 18, 2012 at 8:49 AM, Martin Burnicki
> <martin.burnicki@meinberg.de> wrote:
>> Hi folks,
>>
>> I'm maintaining the driver software for the PCI cards manufactured by our
>> company, Meinberg Funkuhren in Germany. Basically our Linux driver supports
>> all our PCI cards on all Linux kernels 2.6.x and 3.x. The PCI cards are e.g.
>> GPS receivers, radio clocks, or IRIG time code receivers.
>>
>> Recently I've run into a problem with our PCI Express cards in a certain
>> server PC: There are 8 PCI Express slots on the mainboard, and in some of
>> the slots the cards work properly, but in some other slots on the same
>> machine they don't work since the cards are not accessible by the kernel
>> driver.
>>
>> In cases where the cards are not accessible lspci -v reports
>> for the I/O base address 0:
>>
>> Region 0: I/O ports at<ignored>
>
> From the lspci source (http://mj.ucw.cz/sw/pciutils/), it looks like
> this happens when the BAR contains zero.
>
>> Finally I tried different Linux distributions with different kernel versions
>> and found that the same card in the same slot with the same driver works
>> properly under kernel 2.6.32 and earlier, but doesn't work anymore under
>> kernel 2.6.36 and later, including kernel 3.1.4. So there must have been
>> some code changes in the newer kernel versions which prevent the card from
>> being accessed via I/O, and let lspci say "I/O ports at<ignored>".
>
> Please open a bug report at http://bugzilla.kernel.org, category
> Drivers/PCI, mark it as a regression, add me to the CC: list, and
> attach complete dmesg logs from 2.6.32 and 3.1.4 with the card in the
> slot that no longer works.
>
> Bjorn
Thanks for your reply. I've just sent a lengthy explanation to this list ;-)
I'll care about the bug report tomorrow.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
next prev parent reply other threads:[~2012-01-18 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 15:49 PCI card not accessible; I/O ports at <ignored> Martin Burnicki
2012-01-18 16:28 ` Greg KH
2012-01-18 18:22 ` Martin Burnicki
2012-01-18 20:03 ` Rolf Eike Beer
2012-01-18 20:35 ` Greg KH
2012-01-19 9:43 ` Martin Burnicki
2012-01-18 17:16 ` Bjorn Helgaas
2012-01-18 18:27 ` Martin Burnicki [this message]
2012-01-19 11:34 ` Martin Burnicki
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=4F170F01.9090602@meinberg.de \
--to=martin.burnicki@meinberg.de \
--cc=bhelgaas@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox