Bug 6801 - lspci missing my CardBus Ether card
Summary: lspci missing my CardBus Ether card
Status: CLOSED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: PCI (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: linux-pcmcia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-07 07:11 UTC by TAKADA Yoshihito
Modified: 2006-11-09 16:02 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.17.3
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
dmesg of 2.6.16.20 (6.52 KB, text/plain)
2006-07-07 07:12 UTC, TAKADA Yoshihito
Details
dmesg of kernel 2.6.17.3 (6.53 KB, text/plain)
2006-07-07 07:15 UTC, TAKADA Yoshihito
Details
output of lspci with 2.6.16.20. (1.94 KB, text/plain)
2006-07-07 07:17 UTC, TAKADA Yoshihito
Details
output of lspci with 2.6.17.3 (1.45 KB, text/plain)
2006-07-07 07:17 UTC, TAKADA Yoshihito
Details
pci access - pcibios as last fallback (306 bytes, patch)
2006-07-07 16:14 UTC, Daniel Ritz
Details | Diff

Description TAKADA Yoshihito 2006-07-07 07:11:25 UTC
Most recent kernel where this bug did not occur:2.6.16.20
Distribution:Fedora Core 5
Hardware Environment:Cyrix/MediaGX, CS5520(SouthBridge), Ricoh RL5c475
Software Environment:kernel 2.6.17.3
Problem Description:
kernel can't found CardBus card.
From /proc/ioports, kernel 2.6.17 excludes region.
dmesg of kernel 2.6.16.20:
pccard: CardBus card inserted into slot 0
cs: IO port probe 0x3d4-0x4ff: excluding 0x47c-0x493 0x4cc-0x4d3
cs: IO port probe 0x3c0-0x3d2: clean.
cs: IO port probe 0x100-0x3af: excluding 0x398-0x39f
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0xa00-0xaff: clean.

dmesg of kernel 2.6.17.3:
pccard: CardBus card inserted into slot 0
cs: IO port probe 0x3d4-0x4ff: excluding 0x47c-0x493 0x4cc-0x4d3
cs: IO port probe 0x3c0-0x3d2: clean.
cs: IO port probe 0x100-0x3af: excluding 0x398-0x39f
cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0xa00-0xaff: clean.

/proc/ioports of 2.6.16.20
0cf8-0cff : PCI conf1
1000-10ff : PCI CardBus #01
  1000-10ff : 0000:01:00.0
    1000-10ff : 8139too
/proc/ioports of 2.6.17.3
1000-10ff : PCI CardBus #01
1400-14ff : PCI CardBus #01

Why will not 2.6.17-kernel assign "PCI conf1" region?

Steps to reproduce:
Comment 1 TAKADA Yoshihito 2006-07-07 07:12:54 UTC
Created attachment 8498 [details]
dmesg of 2.6.16.20
Comment 2 TAKADA Yoshihito 2006-07-07 07:15:23 UTC
Created attachment 8499 [details]
dmesg of kernel 2.6.17.3

diff. with 2.6.16.20:
- cs: IO port probe 0xc00-0xcff: clean.
+ cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff
Comment 3 TAKADA Yoshihito 2006-07-07 07:17:01 UTC
Created attachment 8500 [details]
output of lspci with 2.6.16.20.

output of lspci, lspci -tv, lspci -v.
Comment 4 TAKADA Yoshihito 2006-07-07 07:17:46 UTC
Created attachment 8501 [details]
output of lspci with 2.6.17.3
Comment 5 Diego Calleja 2006-07-07 07:44:47 UTC
Well, if /proc/ioports shows it is because it's actually _assigned_ to
something: "conf1" (I don't know if that means something though)

There're differences between the 2.6.16 and the 2.6.17 dmesg, but that doesn't
neccesarily means there's a bug, if everything works.
Comment 6 Anonymous Emailer 2006-07-07 07:51:39 UTC
Reply-To: matthew@wil.cx

On Fri, Jul 07, 2006 at 07:47:08AM -0700, bugme-daemon@bugzilla.kernel.org wrote:
> Well, if /proc/ioports shows it is because it's actually _assigned_ to
> something: "conf1" (I don't know if that means something though)

PCI config space 1.  If that range were assigned to a cardbus card, you'd
not be able to access it as the chipset would intercept writes to that
address, and generate config space cycles instead.

This is a red herring, the problem is something different.

Comment 7 TAKADA Yoshihito 2006-07-07 08:31:17 UTC
"PCI conf1" is allocated even when don't insert a CardBus card.
I think that a problem is a region 0xcf8-0xcff to be excluded. 
However, a difference is not found in claim_region() and do_io_probe() of linux/
drivers/pcmcia/rsrc_nonstatic.c in kernel-2.6.16.20 and 2.6.17.3.
Comment 8 TAKADA Yoshihito 2006-07-07 08:41:24 UTC
Of course the Ethernet card which lspci do not show does not work.
As for 8139too, it is not found a Ethernet card with kernel 2.6.17. When it is 
2.6.16.20, it works well.
Comment 9 Daniel Ritz 2006-07-07 16:12:23 UTC
it's PCI problem, not PCMCIA:
in 2.6.17 the ordering of the PCI access function probing was changed
(commit 92c05fc1a32e5ccef5e0e8201f32dcdab041524c). the diff between the
to dmesg makes it clear:

the behaviour should be changed back to have PCIBIOS as last fallback.
Comment 10 Daniel Ritz 2006-07-07 16:14:44 UTC
Created attachment 8504 [details]
pci access - pcibios as last fallback
Comment 11 TAKADA Yoshihito 2006-07-07 20:38:38 UTC
Thanks for many comments.
I tried to modify arch/i386/pci/init.c.(applied #10) CardBus did not work.
Next, I changed CONFIG_PCI_ANY to CONFIG_PCI_BIOS in .config. After all the 
CardBus did not work.
Comment 12 Daniel Ritz 2006-07-08 05:57:34 UTC
the BIOS access methos is broken on your box (broken BIOS):
  PCI: PCI BIOS revision 2.10 entry at 0xfb9a0, last bus=0
"last bus=0" is wrong. your 2.6.16 kernel shows this additional line:
  PCI: Using configuration type 1
so what you want is direct access. my patch should have enabled that again, but
it seems i missed something. anyway, set PCI access method to "Direct" using
menuconfig and recompile the kernel.
Comment 13 TAKADA Yoshihito 2006-07-08 06:51:56 UTC
OK, The problem was solved.
CardBus works when change CONFIG_PCI_BIOS to CONFIG_PCI_DIRECT in .config.
Thanks.
Comment 14 Adrian Bunk 2006-08-06 04:06:39 UTC
*** Bug 6834 has been marked as a duplicate of this bug. ***
Comment 15 Adrian Bunk 2006-08-06 04:20:06 UTC
Sorry, this was a typo.
Comment 16 Diego Calleja 2006-08-16 07:18:12 UTC
Could people take a look at #6920? It's the same bug?
Comment 17 Dominik Brodowski 2006-11-07 19:17:01 UTC
can this bug be closed, as per comment #13 ?
Comment 18 TAKADA Yoshihito 2006-11-09 16:02:19 UTC
Yes, This bug is fixed in 2.6.18.

Note You need to log in before you can comment on or make changes to this bug.