From: "Manu Abraham" <abraham.manu@gmail.com>
To: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: PCI BIST is running
Date: Mon, 5 Feb 2007 01:06:09 +0400 [thread overview]
Message-ID: <1a297b360702041306x73b4be24j32922aed2a95f7d4@mail.gmail.com> (raw)
Hi,
I have 3 similar PCI cards all 32 bit in 32 bit PCI slots on a x86 (32 bit) CPU
On booting up 2.6.17.7, i get this message,
PCI: Unable to handle 64-bit address space for device 02:0a.0
i get one more message stating that an address could not be mapped for
the same slot.
running lspci, i get thus ..
All the 3 PCI cards are the same except that the first one is Rev 08
card and the others Rev 01
can somebody point me as to what's happening on the first card ? I
understand that some Built In Self Test is Running, but syill don't
understand why it doesn't terminate or so
Thanks,
Manu
02:0a.0 4e35: 1800:4e35 (rev 08) (prog-if 18)
Subsystem: 002c:c200
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR+ <PERR+
Latency: 0, Cache Line Size 0c
BIST is running
Region 0: Memory at f7ee0000 (32-bit, non-prefetchable) [disabled] [size=4K]
Region 2: Memory at e9b00000 (32-bit, prefetchable) [disabled] [size=4K]
Region 3: Memory at <unassigned> (32-bit, prefetchable) [disabled]
Region 4: Memory at <ignored> (32-bit, non-prefetchable) [disabled]
Region 5: Memory at <invalid-64bit-slot> (64-bit, non-prefetchable) [disabled]
Expansion ROM at e9b01000 [disabled] [size=4K]
02:0c.0 0480: 1822:4e35 (rev 01)
Subsystem: 1822:0014
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (2000ns min, 63750ns max)
Interrupt: pin A routed to IRQ 19
Region 0: Memory at e9bfe000 (32-bit, prefetchable) [size=4K]
02:0d.0 0480: 1822:4e35 (rev 01)
Subsystem: 1822:0024
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (2000ns min, 63750ns max)
Interrupt: pin A routed to IRQ 20
Region 0: Memory at e9bfd000 (32-bit, prefetchable) [size=4K]
reply other threads:[~2007-02-04 21:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1a297b360702041306x73b4be24j32922aed2a95f7d4@mail.gmail.com \
--to=abraham.manu@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®