Re: Updated 2.4 TODO List - more on PCI resources...]
I have tested Linus' patch and it makes a difference: cs: cb_alloc(bus 6): vendor 0x115d, device 0x0003 Found 06:00 [115d/0003] 000200 00 bus res 0 1200 1c00-1fff bus res 1 200 2000-23ff bus res 2 100 1800-18ff bus res 0 1200 1c00-1fff bus res 1 200 2000-23ff bus res 0 1200 1c00-1fff bus res 1 200 2000-23ff bus res 0 1200 1c00-1fff PCI: Error while updating region 06:00.0/6 (1c01 != 1801) PCI: Enabling device 06:00.0 ( -> 0003) Found 06:01 [115d/0103] 000300 00 bus res 0 1200 1c00-1fff bus res 1 200 2000-23ff bus res 2 100 1800-18ff bus res 0 1200 1c00-1fff bus res 1 200 2000-23ff bus res 0 1200 1c00-1fff bus res 1 200 2000-23ff bus res 0 1200 1c00-1fff PCI: Error while updating region 06:00.1/6 (1c004001 != 18004001) PCI: Enabling device 06:00.1 ( -> 0003) VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 192k freed Warning: unable to open an initial console. cs: IO port probe 0x0c00-0x0cff: clean. cs: IO port probe 0x0800-0x08ff: clean. cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x370-0x37f 0x4d0-0x4d7 cs: IO port probe 0x0a00-0x0aff: clean. eth0: first available media type: MII tulip_attach(06:00.0) PCI: Enabling bus mastering for device 06:00.0 PCI: Setting latency timer of device 06:00.0 to 64 xircom_tulip_cb.c:v0.91 4/14/99 [EMAIL PROTECTED] (modified by [EMAIL PROTECTED] for XIRCOM CBE, fixed by Doug Ledford) eth1: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x1800, 00:00:00:00:00:00, IRQ 11. lspci: 06:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03) Subsystem: Xircom Cardbus Ethernet 10/100 Flags: bus master, medium devsel, latency 64, IRQ 11 I/O ports at 1800 [size=128] Memory at 2000 (32-bit, non-prefetchable) [size=2K] Memory at 2800 (32-bit, non-prefetchable) [size=2K] Expansion ROM at 1c00 [size=16K] Capabilities: [dc] Power Management version 1 06:00.1 VGA compatible controller: Xircom Cardbus Ethernet + 56k Modem (rev 03) (prog-if 02) Subsystem: Xircom CBEM56G-100 Ethernet + 56k Modem Flags: medium devsel, IRQ 11 I/O ports at 1880 [size=8] Memory at 20001000 (32-bit, non-prefetchable) [size=2K] Memory at 20001800 (32-bit, non-prefetchable) [size=2K] Expansion ROM at 1c004000 [size=16K] Capabilities: [dc] Power Management version 1 It still doesn't work. It looks very much like a stuck bit, but at least we get a slightly "better" error message and the expansion ROM now gets enabled. progress! Linus wants to "debug this to death" (his words, not mine) but I don't have access to the suspect hardware for the next five weeks, and it will probably be serviced some time during those weeks. Thank you for being patient, Linus. And sorry for not being able to provide more debug data. Dag B - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Updated 2.4 TODO List - more on PCI resources...
Linus Torvalds wrote: > > On Wed, 11 Oct 2000, Dag B wrote: > > 2.4.0-test9/10p1 > > Can you do another test with this (ie in-kernel pcmcia), AND enable > debugging in both drivers/pci/pci.c and in arch/i386/kernel/pci-i386.h (in [snip] > drivers/pcmcia/yenta.c to allocate more than 4MB of PCI memory window. [snip] > align = size = 32*1024*1024; Done. Didn't work. But it certainly made a difference. lspci -v now says: 06:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03) Subsystem: Xircom Cardbus Ethernet 10/100 Flags: medium devsel, IRQ 11 I/O ports at 1800 [size=128] [virtual] Memory at 1800 (32-bit, non-prefetchable) [size=32M] [virtual] Memory at 1800 (32-bit, non-prefetchable) [size=32M] Expansion ROM at 1800 [disabled] [size=32M] Capabilities: [dc] Power Management version 1 What used to be a 4M expansion ROM is now 32M. Just for grins, I made a version with align = size = 64*1024*1024; and got [virtual] Memory at 2000 (32-bit, non-prefetchable) [size=64M] Expansion ROM at 2000 [disabled] [size=64M] debug output from boot follows: dagblap:~# dmesg | more Linux version 2.4.0-test9 (root@dagblap) (gcc version 2.95.2 19991024 (release)) #3 Wed Oct 11 22:0 6:48 CEST 2000 BIOS-provided physical RAM map: BIOS-e820: 0009fc00 @ (usable) BIOS-e820: 0400 @ 0009fc00 (reserved) BIOS-e820: c000 @ 000c (reserved) BIOS-e820: 05ef @ 0010 (usable) BIOS-e820: 0001 @ 05ff (ACPI data) BIOS-e820: 0006 @ 100a (reserved) BIOS-e820: 0020 @ ffe0 (reserved) On node 0 totalpages: 24560 zone(0): 4096 pages. zone(1): 20464 pages. zone(2): 0 pages. Kernel command line: BOOT_IMAGE=test10p1a ro root=/dev/discs/disc0/part5 pci=rom [...] PCI: Using configuration type 1 PCI: Probing PCI hardware Scanning bus 00 Found 00:00 [8086/7190] 000600 00 Found 00:08 [8086/7191] 000604 01 Found 00:18 [104c/ac1c] 000607 02 Found 00:19 [104c/ac1c] 000607 02 Found 00:38 [8086/7110] 000680 00 Found 00:39 [8086/7111] 000101 00 PCI: IDE base address fixup for 00:07.1 Found 00:3a [8086/7112] 000c03 00 Found 00:3b [8086/7113] 000680 00 Found 00:68 [10b7/9050] 000200 00 Fixups for bus 00 PCI: Scanning for ghost devices on bus 0 Scanning behind PCI bridge 00:01.0, config 010100, pass 0 Scanning bus 01 Found 01:00 [10c8/0005] 000300 00 Found 01:01 [10c8/8005] 000401 00 Fixups for bus 01 PCI: Scanning for ghost devices on bus 1 Bus scan for 01 returning with max=01 Scanning behind PCI bridge 00:03.0, config 00, pass 0 Scanning behind PCI bridge 00:03.1, config 00, pass 0 Scanning behind PCI bridge 00:01.0, config 010100, pass 1 Scanning behind PCI bridge 00:03.0, config 00, pass 1 Scanning behind PCI bridge 00:03.1, config 00, pass 1 Bus scan for 00 returning with max=09 PCI: IRQ init PCI: Interrupt Routing Table found at 0xc00fbda0 00:07 slot=00 0:00/ 1:00/ 2:00/ 3:63/def8 01:00 slot=00 0:60/def8 1:61/def8 2:00/ 3:00/ 00:03 slot=00 0:63/def8 1:63/def8 2:00/ 3:00/ 00:0d slot=00 0:62/def8 1:00/ 2:00/ 3:00/ 00:11 slot=00 0:62/def8 1:62/def8 2:62/def8 3:62/def8 PCI: Bus 01 already known PCI: Using IRQ router default [8086/1234] at 00:07.0 PCI: IRQ fixup PCI: Allocating resources PCI: Resource f400-f7ff (f=1208, d=0, p=0) PCI: Resource 0860-086f (f=101, d=0, p=0) PCI: Resource ece0-ecff (f=101, d=0, p=0) PCI: Resource ec80-ecbf (f=101, d=0, p=0) PCI: Resource fb00-fbff (f=1208, d=0, p=0) PCI: Resource fdc0-fdff (f=200, d=0, p=0) PCI: Resource fdb0-fdbf (f=200, d=0, p=0) PCI: Resource fac0-faff (f=1208, d=0, p=0) PCI: Resource fda0-fdaf (f=200, d=0, p=0) Limiting direct PCI/PCI transfers. Linux NET4.0 for Linux 2.4 [...] NeoMagic 256AV/256ZX audio driver, version 1.1 NM256: Found card signature in video RAM: 0x27ec00 Trying to free nonexistent resource NM256: Mapping port 1 from 0x266c00 - 0x27ec00 Initialized NeoMagic 256AV audio in PCI native mode Initialized AC97 mixer Done installing NM256 audio driver. Linux PCMCIA Card Services 3.1.20 options: [pci] [cardbus] [pm] devfs: v0.102 (2622) Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options: 0x2 kmem_create: Forcing size word alignment - nfs_fh Yenta IRQ list 0298, PCI irq11 Socket status: 3006 Yenta IRQ list 0298, PCI irq11 Socket status: 3020 ACPI: support found ACPI: PBLK 1 @ 0x0810:0 ACPI: S1 supported ACPI: S5 supported cs: cb_alloc(bus 6): vendor 0x115d, device 0x0003 Found 06:00 [115d/0003] 000200 00 PCI: Failed to allocate resource 1 for PCI device 115d:0003 PCI: Failed to allocate resource 2 for PCI device 115d:0003 PCI: Failed to allocate resource 6 for PCI device 115d:0003 PCI: Enabling device 06:00.0 ( -> 0003) Found 0
Re: Updated 2.4 TODO List - more on PCI resources...
Keywords: cardbus, dell, xircom, pci, resources In short: Xircom Realport cardbus cards still do not work under Linux in (my) Dell Latitude CPi laptop. A problem indication shows up even before loading the xircom driver. This is not the Latitude docking-station problem, which has been noted by others. AFAICT. Tested with: 2.2.18pre15 + pcmcia-cs 3.1.21 2.4.0-test9/10p1 2.4.0-test9 + pcmcia-cs 3.1.21 quite a few other combinations, including older versions of 2.2 and 2.4-test* kernels and pcmcia-cs. I have tried every combination of "rom,bios,direct" as options to the "pci=" kernel boot-option, 3 different BIOS versions, with and without the docking (which has never caused me any grief, mind you), with cardbus support compiled-in and as modules, and quite a few other tricks and stupidities. No go. As soon as I insert the card (or if the card was inserted prior to boot, during boot-time), I get: cs: cb_alloc(bus 6): vendor 0x115d, device 0x0003 PCI: Failed to allocate resource 1 for PCI device 115d:0003 PCI: Failed to allocate resource 2 for PCI device 115d:0003 PCI: Failed to allocate resource 6 for PCI device 115d:0003 PCI: Enabling device 06:00.0 ( -> 0003) PCI: Failed to allocate resource 1 for PCI device 115d:0103 PCI: Failed to allocate resource 2 for PCI device 115d:0103 PCI: Failed to allocate resource 6 for PCI device 115d:0103 PCI: Enabling device 06:00.1 ( -> 0003) (-test9) or, in the case of 2.2.18pre15+pcmcia-cs 3.1.21: Oct 8 20:58:56 dagblap pcmcia: Starting PCMCIA services: Oct 8 20:58:56 dagblap pcmcia: modules Oct 8 20:58:57 dagblap kernel: Linux PCMCIA Card Services 3.1.21 Oct 8 20:58:57 dagblap kernel: kernel build: 2.2.18pre15 #1 Sun Oct 8 20:31:01 CEST 2000 Oct 8 20:58:57 dagblap kernel: options: [pci] [cardbus] [apm] [pnp] Oct 8 20:58:57 dagblap kernel: PCI routing table version 1.0 at 0xfbda0 Oct 8 20:58:57 dagblap kernel: 00:03.0 -> irq 11 Oct 8 20:58:57 dagblap kernel: 00:03.1 -> irq 11 Oct 8 20:58:57 dagblap kernel: PnP: PNP BIOS installation structure at 0xc00fe2d0 Oct 8 20:58:57 dagblap kernel: PnP: PNP BIOS version 1.0, entry at f:e2f4, dseg at 40 Oct 8 20:58:57 dagblap kernel: Intel PCIC probe: Oct 8 20:58:57 dagblap kernel: TI 1225 rev 01 PCI-to-CardBus at slot 00:03, mem 0x6800 Oct 8 20:58:57 dagblap kernel: host opts [0]: [ring] [serial pci & irq] [pci irq 11] [lat 32/32] [bus 32/34] Oct 8 20:58:57 dagblap kernel: host opts [1]: [ring] [serial pci & irq] [pci irq 11] [lat 32/32] [bus 35/37] Oct 8 20:58:57 dagblap kernel: ISA irqs (scanned) = 3,7,9 PCI status changes Oct 8 20:58:57 dagblap pcmcia: cardmgr. Oct 8 20:58:57 dagblap rc: Starting pcmcia succeeded Oct 8 20:58:57 dagblap cardmgr[481]: starting, version is 3.1.21 Oct 8 20:58:57 dagblap kernel: cs: cb_alloc(bus 35): vendor 0x115d, device 0x0003 Oct 8 20:58:57 dagblap cardmgr[481]: watching 2 sockets Oct 8 20:58:57 dagblap kernel: cs: IO port probe 0x1000-0x17ff: clean. Oct 8 20:58:57 dagblap kernel: cs: IO port probe 0x0100-0x04ff: clean. Oct 8 20:58:57 dagblap kernel: cs: IO port probe 0x0a00-0x0aff: clean. Oct 8 20:58:57 dagblap cardmgr[481]: initializing socket 1 Oct 8 20:58:57 dagblap kernel: cs: no valid ROM images found! Oct 8 20:58:57 dagblap cardmgr[481]: unsupported card in socket 1 Oct 8 20:58:57 dagblap cardmgr[481]: no product info available Oct 8 20:58:57 dagblap cardmgr[481]: PCI id: 0x115d, 0x0003 The hardware is functional. (Tested on NT4.) lspci -v says: 06:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03) Subsystem: Xircom Cardbus Ethernet 10/100 Flags: medium devsel, IRQ 11 I/O ports at 1800 [size=128] [virtual] Memory at 1100 (32-bit, non-prefetchable) [size=4M] [virtual] Memory at 1100 (32-bit, non-prefetchable) [size=4M] Expansion ROM at 1100 [disabled] [size=4M] Capabilities: [dc] Power Management version 1 06:00.1 VGA compatible controller: Xircom Cardbus Ethernet + 56k Modem (rev 03) (prog-if 02) Subsystem: Xircom CBEM56G-100 Ethernet + 56k Modem Flags: medium devsel, IRQ 11 I/O ports at 1880 [size=8] [virtual] Memory at 1100 (32-bit, non-prefetchable) [size=4M] [virtual] Memory at 1100 (32-bit, non-prefetchable) [size=4M] Expansion ROM at 1100 [disabled] [size=4M] Capabilities: [dc] Power Management version 1 This line: "Expansion ROM at 1100 [disabled] [size=4M]" doesn't look very positive. Can the PCI resource allocation code handle a 4M ROM image? (To the extent which the PCI code cares...?) I do know other users with the exact same type of Xircom card, so this is quite possible some quirk with this particular laptop model. (CPiA 366XT) Any takers? Let me know what debug-switches and knobs I can turn on, and what information I can provide. Regards, Dag B - To unsubscribe from
Re: Updated 2.4 TODO List - more on PCI resources...
Keywords: cardbus, dell, xircom, pci, resources In short: Xircom Realport cardbus cards still do not work under Linux in (my) Dell Latitude CPi laptop. A problem indication shows up even before loading the xircom driver. This is not the Latitude docking-station problem, which has been noted by others. AFAICT. Tested with: 2.2.18pre15 + pcmcia-cs 3.1.21 2.4.0-test9/10p1 2.4.0-test9 + pcmcia-cs 3.1.21 quite a few other combinations, including older versions of 2.2 and 2.4-test* kernels and pcmcia-cs. I have tried every combination of "rom,bios,direct" as options to the "pci=" kernel boot-option, 3 different BIOS versions, with and without the docking (which has never caused me any grief, mind you), with cardbus support compiled-in and as modules, and quite a few other tricks and stupidities. No go. As soon as I insert the card (or if the card was inserted prior to boot, during boot-time), I get: cs: cb_alloc(bus 6): vendor 0x115d, device 0x0003 PCI: Failed to allocate resource 1 for PCI device 115d:0003 PCI: Failed to allocate resource 2 for PCI device 115d:0003 PCI: Failed to allocate resource 6 for PCI device 115d:0003 PCI: Enabling device 06:00.0 ( - 0003) PCI: Failed to allocate resource 1 for PCI device 115d:0103 PCI: Failed to allocate resource 2 for PCI device 115d:0103 PCI: Failed to allocate resource 6 for PCI device 115d:0103 PCI: Enabling device 06:00.1 ( - 0003) (-test9) or, in the case of 2.2.18pre15+pcmcia-cs 3.1.21: Oct 8 20:58:56 dagblap pcmcia: Starting PCMCIA services: Oct 8 20:58:56 dagblap pcmcia: modules Oct 8 20:58:57 dagblap kernel: Linux PCMCIA Card Services 3.1.21 Oct 8 20:58:57 dagblap kernel: kernel build: 2.2.18pre15 #1 Sun Oct 8 20:31:01 CEST 2000 Oct 8 20:58:57 dagblap kernel: options: [pci] [cardbus] [apm] [pnp] Oct 8 20:58:57 dagblap kernel: PCI routing table version 1.0 at 0xfbda0 Oct 8 20:58:57 dagblap kernel: 00:03.0 - irq 11 Oct 8 20:58:57 dagblap kernel: 00:03.1 - irq 11 Oct 8 20:58:57 dagblap kernel: PnP: PNP BIOS installation structure at 0xc00fe2d0 Oct 8 20:58:57 dagblap kernel: PnP: PNP BIOS version 1.0, entry at f:e2f4, dseg at 40 Oct 8 20:58:57 dagblap kernel: Intel PCIC probe: Oct 8 20:58:57 dagblap kernel: TI 1225 rev 01 PCI-to-CardBus at slot 00:03, mem 0x6800 Oct 8 20:58:57 dagblap kernel: host opts [0]: [ring] [serial pci irq] [pci irq 11] [lat 32/32] [bus 32/34] Oct 8 20:58:57 dagblap kernel: host opts [1]: [ring] [serial pci irq] [pci irq 11] [lat 32/32] [bus 35/37] Oct 8 20:58:57 dagblap kernel: ISA irqs (scanned) = 3,7,9 PCI status changes Oct 8 20:58:57 dagblap pcmcia: cardmgr. Oct 8 20:58:57 dagblap rc: Starting pcmcia succeeded Oct 8 20:58:57 dagblap cardmgr[481]: starting, version is 3.1.21 Oct 8 20:58:57 dagblap kernel: cs: cb_alloc(bus 35): vendor 0x115d, device 0x0003 Oct 8 20:58:57 dagblap cardmgr[481]: watching 2 sockets Oct 8 20:58:57 dagblap kernel: cs: IO port probe 0x1000-0x17ff: clean. Oct 8 20:58:57 dagblap kernel: cs: IO port probe 0x0100-0x04ff: clean. Oct 8 20:58:57 dagblap kernel: cs: IO port probe 0x0a00-0x0aff: clean. Oct 8 20:58:57 dagblap cardmgr[481]: initializing socket 1 Oct 8 20:58:57 dagblap kernel: cs: no valid ROM images found! Oct 8 20:58:57 dagblap cardmgr[481]: unsupported card in socket 1 Oct 8 20:58:57 dagblap cardmgr[481]: no product info available Oct 8 20:58:57 dagblap cardmgr[481]: PCI id: 0x115d, 0x0003 The hardware is functional. (Tested on NT4.) lspci -v says: 06:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03) Subsystem: Xircom Cardbus Ethernet 10/100 Flags: medium devsel, IRQ 11 I/O ports at 1800 [size=128] [virtual] Memory at 1100 (32-bit, non-prefetchable) [size=4M] [virtual] Memory at 1100 (32-bit, non-prefetchable) [size=4M] Expansion ROM at 1100 [disabled] [size=4M] Capabilities: [dc] Power Management version 1 06:00.1 VGA compatible controller: Xircom Cardbus Ethernet + 56k Modem (rev 03) (prog-if 02) Subsystem: Xircom CBEM56G-100 Ethernet + 56k Modem Flags: medium devsel, IRQ 11 I/O ports at 1880 [size=8] [virtual] Memory at 1100 (32-bit, non-prefetchable) [size=4M] [virtual] Memory at 1100 (32-bit, non-prefetchable) [size=4M] Expansion ROM at 1100 [disabled] [size=4M] Capabilities: [dc] Power Management version 1 This line: "Expansion ROM at 1100 [disabled] [size=4M]" doesn't look very positive. Can the PCI resource allocation code handle a 4M ROM image? (To the extent which the PCI code cares...?) I do know other users with the exact same type of Xircom card, so this is quite possible some quirk with this particular laptop model. (CPiA 366XT) Any takers? Let me know what debug-switches and knobs I can turn on, and what information I can provide. Regards, Dag B - To unsubscribe from this list: send the
Re: Updated 2.4 TODO List - more on PCI resources...
Linus Torvalds wrote: On Wed, 11 Oct 2000, Dag B wrote: 2.4.0-test9/10p1 Can you do another test with this (ie in-kernel pcmcia), AND enable debugging in both drivers/pci/pci.c and in arch/i386/kernel/pci-i386.h (in [snip] drivers/pcmcia/yenta.c to allocate more than 4MB of PCI memory window. [snip] align = size = 32*1024*1024; Done. Didn't work. But it certainly made a difference. lspci -v now says: 06:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03) Subsystem: Xircom Cardbus Ethernet 10/100 Flags: medium devsel, IRQ 11 I/O ports at 1800 [size=128] [virtual] Memory at 1800 (32-bit, non-prefetchable) [size=32M] [virtual] Memory at 1800 (32-bit, non-prefetchable) [size=32M] Expansion ROM at 1800 [disabled] [size=32M] Capabilities: [dc] Power Management version 1 What used to be a 4M expansion ROM is now 32M. Just for grins, I made a version with align = size = 64*1024*1024; and got [virtual] Memory at 2000 (32-bit, non-prefetchable) [size=64M] Expansion ROM at 2000 [disabled] [size=64M] debug output from boot follows: dagblap:~# dmesg | more Linux version 2.4.0-test9 (root@dagblap) (gcc version 2.95.2 19991024 (release)) #3 Wed Oct 11 22:0 6:48 CEST 2000 BIOS-provided physical RAM map: BIOS-e820: 0009fc00 @ (usable) BIOS-e820: 0400 @ 0009fc00 (reserved) BIOS-e820: c000 @ 000c (reserved) BIOS-e820: 05ef @ 0010 (usable) BIOS-e820: 0001 @ 05ff (ACPI data) BIOS-e820: 0006 @ 100a (reserved) BIOS-e820: 0020 @ ffe0 (reserved) On node 0 totalpages: 24560 zone(0): 4096 pages. zone(1): 20464 pages. zone(2): 0 pages. Kernel command line: BOOT_IMAGE=test10p1a ro root=/dev/discs/disc0/part5 pci=rom [...] PCI: Using configuration type 1 PCI: Probing PCI hardware Scanning bus 00 Found 00:00 [8086/7190] 000600 00 Found 00:08 [8086/7191] 000604 01 Found 00:18 [104c/ac1c] 000607 02 Found 00:19 [104c/ac1c] 000607 02 Found 00:38 [8086/7110] 000680 00 Found 00:39 [8086/7111] 000101 00 PCI: IDE base address fixup for 00:07.1 Found 00:3a [8086/7112] 000c03 00 Found 00:3b [8086/7113] 000680 00 Found 00:68 [10b7/9050] 000200 00 Fixups for bus 00 PCI: Scanning for ghost devices on bus 0 Scanning behind PCI bridge 00:01.0, config 010100, pass 0 Scanning bus 01 Found 01:00 [10c8/0005] 000300 00 Found 01:01 [10c8/8005] 000401 00 Fixups for bus 01 PCI: Scanning for ghost devices on bus 1 Bus scan for 01 returning with max=01 Scanning behind PCI bridge 00:03.0, config 00, pass 0 Scanning behind PCI bridge 00:03.1, config 00, pass 0 Scanning behind PCI bridge 00:01.0, config 010100, pass 1 Scanning behind PCI bridge 00:03.0, config 00, pass 1 Scanning behind PCI bridge 00:03.1, config 00, pass 1 Bus scan for 00 returning with max=09 PCI: IRQ init PCI: Interrupt Routing Table found at 0xc00fbda0 00:07 slot=00 0:00/ 1:00/ 2:00/ 3:63/def8 01:00 slot=00 0:60/def8 1:61/def8 2:00/ 3:00/ 00:03 slot=00 0:63/def8 1:63/def8 2:00/ 3:00/ 00:0d slot=00 0:62/def8 1:00/ 2:00/ 3:00/ 00:11 slot=00 0:62/def8 1:62/def8 2:62/def8 3:62/def8 PCI: Bus 01 already known PCI: Using IRQ router default [8086/1234] at 00:07.0 PCI: IRQ fixup PCI: Allocating resources PCI: Resource f400-f7ff (f=1208, d=0, p=0) PCI: Resource 0860-086f (f=101, d=0, p=0) PCI: Resource ece0-ecff (f=101, d=0, p=0) PCI: Resource ec80-ecbf (f=101, d=0, p=0) PCI: Resource fb00-fbff (f=1208, d=0, p=0) PCI: Resource fdc0-fdff (f=200, d=0, p=0) PCI: Resource fdb0-fdbf (f=200, d=0, p=0) PCI: Resource fac0-faff (f=1208, d=0, p=0) PCI: Resource fda0-fdaf (f=200, d=0, p=0) Limiting direct PCI/PCI transfers. Linux NET4.0 for Linux 2.4 [...] NeoMagic 256AV/256ZX audio driver, version 1.1 NM256: Found card signature in video RAM: 0x27ec00 Trying to free nonexistent resource c6a63c00-c6a63c0f NM256: Mapping port 1 from 0x266c00 - 0x27ec00 Initialized NeoMagic 256AV audio in PCI native mode Initialized AC97 mixer Done installing NM256 audio driver. Linux PCMCIA Card Services 3.1.20 options: [pci] [cardbus] [pm] devfs: v0.102 (2622) Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options: 0x2 kmem_create: Forcing size word alignment - nfs_fh Yenta IRQ list 0298, PCI irq11 Socket status: 3006 Yenta IRQ list 0298, PCI irq11 Socket status: 3020 ACPI: support found ACPI: PBLK 1 @ 0x0810:0 ACPI: S1 supported ACPI: S5 supported cs: cb_alloc(bus 6): vendor 0x115d, device 0x0003 Found 06:00 [115d/0003] 000200 00 PCI: Failed to allocate resource 1 for PCI device 115d:0003 PCI: Failed to allocate resource 2 for PCI device 115d:0003 PCI: Failed to allocate resource 6 for PCI device 115d:0003 PCI: Enabling device 06:00.0 ( - 0003) Found 06:01 [115d/0103] 000300 00 PCI
reserve= specifies ..... iomem or ioport?
This may be obvious to a programmer, but...: ./Documentation/more kernel-parameters.txt : reserve=[KNL,BUGS] force the kernel to ignore some iomem area. http://cuip.uchicago.edu/doc/lilo-0.21/ : reserve=,,... reserves IO port regions. This can be used to prevent device drivers from auto-probing addresses where other devices are located, which get confused by the probing. 'man bootparam' : `reserve=...' This is used to protect I/O port regions from probes. The form of the command is: reserve=iobase,extent[,iobase,extent]... In some machines it may be necessary to prevent device drivers from checking for devices (auto-probing) in a specific region. This may be because of hardware that reacts badly to the probing, or hardware that would be mistakenly identified, or merely hardware you don't want the kernel to initialize. The reserve boot-time argument specifies an I/O port region that shouldn't be probed. A device driver will not probe a reserved region, unless another boot argument explicitly specifies that it do so. For example, the boot line reserve=0x300,32 blah=0x300 keeps all device drivers except the driver for `blah' from probing 0x300-0x31f. The more recent Linux documentation says iomem, while the majority of other documentation says io port. Given that /proc/ contains both, I'd like to see a clearification... Dag B - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0-test9-pre2: pcmcia 3c59x doesn't work
Linus Torvalds wrote:
In article <[EMAIL PROTECTED]>, Dag Bakke <[EMAIL PROTECTED]> wrote:
>Tigran Aivazian wrote:
>>
>> On Mon, 18 Sep 2000, Derek Wildstar wrote:
>>
>> > On 18 Sep 2000, Alex Romosan wrote:
>> >
>> > I get the same thing with a Xircon realport 10/100/modem card. Works
>> > great in test9-pre1 and test8.
[note: neither of these kernels worked for me]
>> >
>> > -dwild
>> >
>>
>> did you try this patch?
>>
>> --- linux/drivers/pci/pci.c Mon Sep 18 12:35:11 2000
>> +++ work/drivers/pci/pci.c Mon Sep 18 13:12:20 2000
[snip]
> >I did.
> >Didn't work for me.
> >My Xircom is still being detected. But PCI resource allocation still fails.
> >I'll be happy to set up a remote debug session for anyone interested...
>
> There seem to be two potential problems with the new code. How about
> this instead:
>
> First off, it's doing the subordinate bus write with a byte write, which
> is, as far as I can tell, not legal. When you update the bus
> information, you have to update it all at the same time.
>
> Does it help if you change drivers/pci/pci.c pci_scan_bridge(), the line
> that says
>
> pci_write_config_byte(dev, PCI_SUBORDINATE_BUS, max);
>
> and you replace that with
>
> buses = (buses & 0xff00) | ((unsigned int)(child->subordinate) << 16);
> pci_write_config_dword(dev, PCI_PRIMARY_BUS, buses);
>
> instead.
>
> Second, if the cardbus bridge is already allocated by the BIOS, the "max
> bus" logic looks bogus. It looks like
>
> if (!is_cardbus) {
> unsigned int cmax = pci_do_scan_bus(child);
> if (cmax > max) max = cmax;
> }
>
> and it _should_ probably have something like
>
> if (!is_cardbus) {
> .. same logic ..
> } else {
> unsigned int cmax = child->subordinate + 3;
> if (cmax > max) max = cmax;
> }
>
> because otherwise we'd completely ignore the cardbus "max" values as far
> as I can tell, and if the machine has another bus it might be given the
> same bus value as the already-configured cardbus bridge.
>
> Do the above two fixes help? If not, I suspect that we're better off
> just reverting the new PCI bus allocation until it's fixed.
>
> Linus
Nah. Didn't help:
Yenta IRQ list 0698, PCI irq11
Socket status: 3006
Yenta IRQ list 0698, PCI irq11
Socket status: 3020
cs: cb_alloc(bus 6): vendor 0x115d, device 0x0003
PCI: Failed to allocate resource 0 for PCI device 115d:0003
PCI: Failed to allocate resource 1 for PCI device 115d:0003
PCI: Failed to allocate resource 2 for PCI device 115d:0003
PCI: Failed to allocate resource 6 for PCI device 115d:0003
PCI: Device 06:00.0 not available because of resource collisions
PCI: Failed to allocate resource 0 for PCI device 115d:0103
PCI: Failed to allocate resource 1 for PCI device 115d:0103
PCI: Failed to allocate resource 2 for PCI device 115d:0103
PCI: Failed to allocate resource 6 for PCI device 115d:0103
PCI: Device 06:00.1 not available because of resource collisions
With Tigran's fix, resource 0 is successfully allocated, and the message
is approximately:
Found 04:00 [115d/0003] 000200 00
PCI: Failed to allocate resource 1 for PCI device 115d:0003
PCI: Failed to allocate resource 2 for PCI device 115d:0003
PCI: Failed to allocate resource 6 for PCI device 115d:0003
PCI: Enabling device 04:00.0 ( -> 0003)
Found 04:01 [115d/0103] 000300 00
PCI: Failed to allocate resource 1 for PCI device 115d:0103
PCI: Failed to allocate resource 2 for PCI device 115d:0103
PCI: Failed to allocate resource 6 for PCI device 115d:0103
PCI: Enabling device 04:00.1 ( -> 0003)
But loading the driver reveals hw-addr == 0:0:0:0:0:0, and ifconfig'ing
the interface causes a hang.
If I parse the message from Martin Mares
(http://www.cs.helsinki.fi/linux/linux-kernel/2000-38/0532.html)
correctly, a fix is possibly needed in
./drivers/pcmcia/yenta.c , and not in ./drivers/pci/pci.c ?
I tried to grok it, but I never got very much beyond 'Hello World\n'
I notice that most devices in this laptop get IRQ 11. Is this an
indication of anything?
dagblap:~# lspci -v | grep -i irq
Flags: bus master, medium devsel, latency 168, IRQ 11
Flags: bus master, medium devsel, latency 168, IRQ 11
Flags: bus master, medium devsel, latency 32, IRQ 11
Flags: bus master, medium devsel, latency 32, IRQ 11
Flags: bus master, medium devsel, latency 32, IRQ 11
Flags: medium devsel, IRQ 5
Flags: medium devsel, IRQ 11
Flags: medium devsel, IRQ 11
dagblap:~# cat /proc/interrupts
CPU0
0: 92925 XT-PIC timer
1: 3 XT-PIC keyboard
2: 0 XT-PIC cascade
11:431 XT
Re: Linux-2.4.0-test9-pre2 -> still CardBus problems
ruments PCI1225 (rev 01) 00:03.1 CardBus bridge: Texas Instruments PCI1225 (rev 01) 00:07.0 Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02) 00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) 00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) 00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02) 00:0d.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang] 01:00.0 VGA compatible controller: Neomagic Corporation [MagicMedia 256AV] (rev 20) 01:00.1 Multimedia audio controller: Neomagic Corporation [MagicMedia 256AV Audio] (rev 20) 06:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03) 06:00.1 VGA compatible controller: Xircom Cardbus Ethernet + 56k Modem (rev 03) # cat /proc/ioports -001f : dma1 0020-003f : pic1 0040-005f : timer 0060-006f : keyboard 0080-008f : dma page reg 00a0-00bf : pic2 00c0-00df : dma2 00f0-00ff : fpu 0170-0177 : ide1 01f0-01f7 : ide0 02e8-02ef : serial(auto) 0376-0376 : ide1 03c0-03df : vesafb 03f6-03f6 : ide0 03f8-03ff : serial(auto) 0800-083f : Intel Corporation 82371AB PIIX4 ACPI 0840-085f : Intel Corporation 82371AB PIIX4 ACPI 0860-086f : Intel Corporation 82371AB PIIX4 IDE 0860-0867 : ide0 0868-086f : ide1 0cf8-0cff : PCI conf1 1000-10ff : PCI CardBus #02 1400-14ff : PCI CardBus #02 1800-18ff : PCI CardBus #06 1c00-1cff : PCI CardBus #06 c000-cfff : PCI Bus #01 ec80-ecbf : 3Com Corporation 3c905 100BaseTX [Boomerang] ec80-ecbf : eth0 ece0-ecff : Intel Corporation 82371AB PIIX4 USB # modprobe xircom_tulip_cb PCI: Device 06:00.1 not available because of resource collisions tulip_attach(06:00.0) PCI: Device 06:00.0 not available because of resource collisions tulip_attach(06:00.0) PCI: Device 06:00.0 not available because of resource collisions Anyone able to tell me what resource collisions we are talking about here? Dag B - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-2.4.0-test9-pre2 - still CardBus problems
) 00:03.1 CardBus bridge: Texas Instruments PCI1225 (rev 01) 00:07.0 Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02) 00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) 00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) 00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02) 00:0d.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang] 01:00.0 VGA compatible controller: Neomagic Corporation [MagicMedia 256AV] (rev 20) 01:00.1 Multimedia audio controller: Neomagic Corporation [MagicMedia 256AV Audio] (rev 20) 06:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03) 06:00.1 VGA compatible controller: Xircom Cardbus Ethernet + 56k Modem (rev 03) # cat /proc/ioports -001f : dma1 0020-003f : pic1 0040-005f : timer 0060-006f : keyboard 0080-008f : dma page reg 00a0-00bf : pic2 00c0-00df : dma2 00f0-00ff : fpu 0170-0177 : ide1 01f0-01f7 : ide0 02e8-02ef : serial(auto) 0376-0376 : ide1 03c0-03df : vesafb 03f6-03f6 : ide0 03f8-03ff : serial(auto) 0800-083f : Intel Corporation 82371AB PIIX4 ACPI 0840-085f : Intel Corporation 82371AB PIIX4 ACPI 0860-086f : Intel Corporation 82371AB PIIX4 IDE 0860-0867 : ide0 0868-086f : ide1 0cf8-0cff : PCI conf1 1000-10ff : PCI CardBus #02 1400-14ff : PCI CardBus #02 1800-18ff : PCI CardBus #06 1c00-1cff : PCI CardBus #06 c000-cfff : PCI Bus #01 ec80-ecbf : 3Com Corporation 3c905 100BaseTX [Boomerang] ec80-ecbf : eth0 ece0-ecff : Intel Corporation 82371AB PIIX4 USB # modprobe xircom_tulip_cb PCI: Device 06:00.1 not available because of resource collisions tulip_attach(06:00.0) PCI: Device 06:00.0 not available because of resource collisions tulip_attach(06:00.0) PCI: Device 06:00.0 not available because of resource collisions Anyone able to tell me what resource collisions we are talking about here? Dag B - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
PROBLEM: ds.o fails to properly enable CardBus card (2.4.0t8)
3.0 CardBus bridge: Texas Instruments PCI1225 (rev 01) 00:03.1 CardBus bridge: Texas Instruments PCI1225 (rev 01) 00:07.0 Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02) 00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) 00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) 00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02) 00:0d.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang] 01:00.0 VGA compatible controller: Neomagic Corporation [MagicMedia 256AV] (rev 20) 01:00.1 Multimedia audio controller: Neomagic Corporation [MagicMedia 256AV Audio] (rev 20) 04:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03) 04:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03) 04:00.1 VGA compatible controller: Xircom Cardbus Ethernet + 56k Modem (rev 03) 04:00.1 VGA compatible controller: Xircom Cardbus Ethernet + 56k Modem (rev 03) Repeating the rmmod/insmod cycle adds more duplicate entries. Is this a CardBus problem, a PCI problem, or hardware? (I don't think the BIOS can be made responsible for removable hardware, but..) I'd like to note that the hardware is known good. Any takers? Dag B - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
PROBLEM: ds.o fails to properly enable CardBus card (2.4.0t8)
Instruments PCI1225 (rev 01) 00:03.1 CardBus bridge: Texas Instruments PCI1225 (rev 01) 00:07.0 Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02) 00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) 00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) 00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02) 00:0d.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang] 01:00.0 VGA compatible controller: Neomagic Corporation [MagicMedia 256AV] (rev 20) 01:00.1 Multimedia audio controller: Neomagic Corporation [MagicMedia 256AV Audio] (rev 20) 04:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03) 04:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03) 04:00.1 VGA compatible controller: Xircom Cardbus Ethernet + 56k Modem (rev 03) 04:00.1 VGA compatible controller: Xircom Cardbus Ethernet + 56k Modem (rev 03) Repeating the rmmod/insmod cycle adds more duplicate entries. Is this a CardBus problem, a PCI problem, or hardware? (I don't think the BIOS can be made responsible for removable hardware, but..) I'd like to note that the hardware is known good. Any takers? Dag B - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
PROBLEM: Xircom Realport gets MAC 00:00:00...... Card known good.
This is very verbose. Sorry. I much prefer to toss all the pieces on the
table at the same time.
Dag B
[1.] One line summary of the problem:
-test7/8 version of xircom_tulip_cb does not enable my Xircom Realport
(RBEM56G-100)
Nor any of the other kernels I have tried...
[2.] Full description of the problem/report:
My Xircom Realport (RBEM56G-100) is causing headaches. It works with
NT4/SP5 on my Dell CPi laptop, so the hardware is functional. (Tested
this morning. )
When loading the xircom_tulip_cb.c:v0.91 driver, things looks ok, until
you study the MAC address, which is all zeros. What follows is the
output from -test7 and test8:
-test7:
Linux PCMCIA Card Services 3.1.11
options: [pci] [cardbus] [pm]
Yenta IRQ list 0098, PCI irq11
Socket status: 3006
Yenta IRQ list 0098, PCI irq11
Socket status: 3020
devfs: v0.102 (2622) Richard Gooch ([EMAIL PROTECTED])
devfs: boot_options: 0x0
kmem_create: Forcing size word alignment - nfs_fh
cs: cb_alloc(bus 4): vendor 0x115d, device 0x0003
PCI: Failed to allocate resource 1 for PCI device 115d:0003
PCI: Failed to allocate resource 2 for PCI device 115d:0003
PCI: Failed to allocate resource 6 for PCI device 115d:0003
PCI: Enabling device 04:00.0 ( -> 0003)
PCI: Failed to allocate resource 1 for PCI device 115d:0103
PCI: Failed to allocate resource 2 for PCI device 115d:0103
PCI: Failed to allocate resource 6 for PCI device 115d:0103
PCI: Enabling device 04:00.1 ( -> 0003)
[snip]
tulip_attach(04:00.0)
PCI: Setting latency timer of device 04:00.0 to 64
xircom_tulip_cb.c:v0.91 4/14/99 [EMAIL PROTECTED] (modified by
[EMAIL PROTECTED] for XIRCOM CBE, fixed by Doug Ledford)
eth1: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at
0x1800, 00:00:00:00:00:00, IRQ 11.
-test8:
Linux PCMCIA Card Services 3.1.20
options: [pci] [cardbus] [pm]
Yenta IRQ list 0298, PCI irq11
Socket status: 3006
devfs: v0.102 (2622) Richard Gooch ([EMAIL PROTECTED])
devfs: boot_options: 0x2
kmem_create: Forcing size word alignment - nfs_fh
Yenta IRQ list 0298, PCI irq11
Socket status: 3020
cs: cb_alloc(bus 4): vendor 0x115d, device 0x0003
PCI: Failed to allocate resource 1 for PCI device 115d:0003
PCI: Failed to allocate resource 2 for PCI device 115d:0003
PCI: Failed to allocate resource 6 for PCI device 115d:0003
PCI: Enabling device 04:00.0 ( -> 0003)
PCI: Failed to allocate resource 1 for PCI device 115d:0103
PCI: Failed to allocate resource 2 for PCI device 115d:0103
PCI: Failed to allocate resource 6 for PCI device 115d:0103
PCI: Enabling device 04:00.1 ( -> 0003)
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 204k freed
Warning: unable to open an initial console.
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x300-0x307 0x378-0x37f
0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
eth0: first available media type: MII
tulip_attach(04:00.0)
PCI: Setting latency timer of device 04:00.0 to 64
xircom_tulip_cb.c:v0.91 4/14/99 [EMAIL PROTECTED] (modified by
[EMAIL PROTECTED] for XIRCOM CBE, fixed by Doug Ledford)
eth1: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at
0x1800, 00:00:00:00:00:00, IRQ 11.
I can use ifconfig to set a hw-address (does the card really support
this?), but if I try to set an IP-address, the system hangs hard.
Donald Becker's tulip-diag says:
dagblap:/tmp# ./tulip-diag -p 0x1800 -t 4 -ee
tulip-diag.c:v2.03 7/31/2000 Donald Becker ([EMAIL PROTECTED])
http://www.scyld.com/diag/index.html
Assuming a Digital DS21143 Tulip adapter at 0x1800.
Port selection is MII, half-duplex.
Transmit stopped, Receive stopped, half-duplex.
The Rx process state is 'Stopped'.
The Tx process state is 'Stopped'.
PCI bus error!: Parity Error.
The transmit threshold is 128.
The NWay status register is 00c6.
EEPROM size is 8.
WARNING: The EEPROM is missing or erased!
This interface is missing the EEPROM.
This is likely the non-primary interface on a multiport board.
EEPROM contents:
ID block CRC 0xfa (vs. 0xff).
Full contents CRC 0x6a15 (read as 0x).
Internal autonegotiation state is 'Invalid state'.
This is a 10/100BaseTX/56K modem combo card. Loading serial_cb produces
nothing. And the card still works under that other OS...
[3.] Keywords (i.e., modules, networking, kernel):
Xircom, cardbus, xircom_tulip_cb, mac, hwaddress
[4.] Kernel version (from /proc/version):
2.4.0-test8 (gcc version 2.95.2 19991024 (release))
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
