weird pcmcia problem

weird pcmcia problem

[Narayan Desai]

Running 2.6.0-test3 (both with and without your recent yenta socket
patches) pcmcia cards present during boot don't show up until they are
removed and reinserted. Once reinserted, they work fine. This only
seems to occur if yenta_socket is build into the kernel; if support is
modular, cards appear to be recognized properly at boot time. I am
running on a thinkpad t21.  Let me know if I can help with this
problem in any way...  thanks
 -nld

messages from boot:
Yenta: CardBus bridge found at 0000:00:02.0 [1014:0130]
Yenta: Using INTVAL to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta: ISA IRQ list 04b8, PCI irq11
Socket status: 30000010
Yenta: CardBus bridge found at 0000:00:02.1 [1014:0130]
Yenta: Using INTVAL to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta: ISA IRQ list 04b8, PCI irq11
Socket status: 30000006

<later>

cs: warning: no high memory space available!
cs: unable to map card memory!
cs: unable to map card memory!
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x370-0x377 0x3b8-0x3df 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.

Re: weird pcmcia problem

[Jamie Lokier]

Narayan Desai wrote:
> Running 2.6.0-test3 (both with and without your recent yenta socket
> patches) pcmcia cards present during boot don't show up until they are
> removed and reinserted. Once reinserted, they work fine. This only
> seems to occur if yenta_socket is build into the kernel; if support is
> modular, cards appear to be recognized properly at boot time. I am
> running on a thinkpad t21.  Let me know if I can help with this
> problem in any way...  thanks

I see the same problem.  "cardctl eject; cardctl insert" is enough to
get the card recognised for me.

-- Jamie

Re: weird pcmcia problem

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]

On Mon, 18 Aug 2003 19:34:59 CDT, Narayan Desai <desai@mcs.anl.gov>  said:
> Running 2.6.0-test3 (both with and without your recent yenta socket
> patches) pcmcia cards present during boot don't show up until they are
> removed and reinserted. Once reinserted, they work fine. This only
> seems to occur if yenta_socket is build into the kernel; if support is
> modular, cards appear to be recognized properly at boot time. I am
> running on a thinkpad t21.  Let me know if I can help with this
> problem in any way...  thanks

Same issue on 2.6.0-test3-mm2 on a Dell Latitude C840 with a TrueMobile 1150
wireless (uses orinoco_cs driver) - card is recognized at boot, and somewhat
configured:

Aug 18 11:16:52 turing-police kernel: eth1: Station identity 001f:0001:0008:000a
Aug 18 11:16:53 turing-police kernel: eth1: Looks like a Lucent/Agere firmware version 8.10
Aug 18 11:16:53 turing-police kernel: eth1: Ad-hoc demo mode supported
Aug 18 11:16:53 turing-police kernel: eth1: IEEE standard IBSS ad-hoc mode supported
Aug 18 11:16:53 turing-police kernel: eth1: WEP supported, 104-bit key
Aug 18 11:16:53 turing-police kernel: eth1: MAC address 00:02:2D:5C:11:48
Aug 18 11:16:53 turing-police kernel: eth1: Station name "HERMES I"
Aug 18 11:16:53 turing-police kernel: eth1: ready
Aug 18 11:16:53 turing-police kernel: eth1: index 0x01: Vcc 3.3, irq 11, io 0x0100-0x013f

but it takes a 'cardctl eject 2;cardctl insert 2' to actually finish the job
and get things started (actually popping the card out not required, and not
possible, it's a built-in). Relevant .config:

CONFIG_YENTA=y
CONFIG_HERMES=y
# CONFIG_PLX_HERMES is not set
# CONFIG_TMD_HERMES is not set
CONFIG_PCI_HERMES=y
CONFIG_PCMCIA_HERMES=y

I'm wondering if this is a cardmgr/hotplug bug - if they can't insmod the Yenta
support, they don't realize that it could already be onboard so they don't even
try to start the cards?


[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Re: weird pcmcia problem

[Russell King]

On Mon, Aug 18, 2003 at 07:34:59PM -0500, Narayan Desai wrote:
> cs: warning: no high memory space available!
> cs: unable to map card memory!
> cs: unable to map card memory!

Hmm, this looks suspicious.  For some reason, we can't find any memory
resources to map the CIS, so we can't identify the card type, which
means we'll probably identify the card as a memory card.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html

Re: weird pcmcia problem

[Russell King]

On Mon, Aug 18, 2003 at 07:34:59PM -0500, Narayan Desai wrote:
> Running 2.6.0-test3 (both with and without your recent yenta socket
> patches) pcmcia cards present during boot don't show up until they are
> removed and reinserted. Once reinserted, they work fine. This only
> seems to occur if yenta_socket is build into the kernel; if support is
> modular, cards appear to be recognized properly at boot time. I am
> running on a thinkpad t21.  Let me know if I can help with this
> problem in any way...  thanks

As a general thing, when people report this problem (or any other problem),
can they please include at least the following details please:

- make/model of machine
- type of cardbus bridge (from lspci)
- type of card (pcmcia or cardbus)
- make/model of card
- full kernel dmesg (including yenta, card services messages)
- cardmgr messages from system log

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html

Re: weird pcmcia problem

[Henrik Persson]

[-- Attachment #1: Type: text/plain, Size: 4559 bytes --]

On Tue, 19 Aug 2003 12:45:47 +0100
Russell King <rmk@arm.linux.org.uk> wrote:

> On Mon, Aug 18, 2003 at 07:34:59PM -0500, Narayan Desai wrote:
> > Running 2.6.0-test3 (both with and without your recent yenta socket
> > patches) pcmcia cards present during boot don't show up until they are
> > removed and reinserted. Once reinserted, they work fine. This only
> > seems to occur if yenta_socket is build into the kernel; if support is
> > modular, cards appear to be recognized properly at boot time. I am
> > running on a thinkpad t21.  Let me know if I can help with this
> > problem in any way...  thanks
> 
> As a general thing, when people report this problem (or any other
> problem), can they please include at least the following details please:
> 
> - make/model of machine
> - type of cardbus bridge (from lspci)
> - type of card (pcmcia or cardbus)
> - make/model of card
> - full kernel dmesg (including yenta, card services messages)
> - cardmgr messages from system log

I see something similar on my Acer Aspire 1300XV.

On 2.4 everything seems to be working properly (except that i have to
eject and insert it twice to get the card up and running (more people have
reported this issue, I think). In 2.6 things aren't working that well..

/* insertion of card */
Aug 19 15:35:07 [cardmgr] socket 0: Anonymous Memory
Aug 19 15:35:07 [cardmgr] executing: 'modprobe sram_mtd'
Aug 19 15:35:07 [cardmgr] + FATAL: Module sram_mtd not found.
Aug 19 15:35:07 [cardmgr] modprobe exited with status 1
Aug 19 15:35:07 [cardmgr] module
/lib/modules/2.6.0-test3/pcmcia/sram_mtd.o not available
Aug 19 15:35:07 [cardmgr] Common memory region at 0x4000: Generic or SRAM
Aug 19 15:35:07 [cardmgr] Common memory region at 0x0: Generic or SRAM
Aug 19 15:35:07 [cardmgr] bind MTD 'sram_mtd' to socket 0 failed: Invalid
argument
Aug 19 15:35:07 [cardmgr] executing: 'modprobe memory_cs'
Aug 19 15:35:07 [cardmgr] + FATAL: Module memory_cs not found.
Aug 19 15:35:07 [cardmgr] modprobe exited with status 1
Aug 19 15:35:07 [cardmgr] module
/lib/modules/2.6.0-test3/pcmcia/memory_cs.o not available
Aug 19 15:35:07 [cardmgr] bind 'memory_cs' to socket 0 failed: Invalid
argument

/* and here I eject: */
Aug 19 15:36:31 [cardmgr] unbind MTD 'sram_mtd' from socket 0 failed: No
such device
Aug 19 15:36:31 [cardmgr] executing: 'modprobe -r memory_cs'
Aug 19 15:36:31 [cardmgr] + FATAL: Module memory_cs not found.
Aug 19 15:36:31 [cardmgr] modprobe exited with status 1
Aug 19 15:36:31 [cardmgr] executing: 'modprobe -r sram_mtd'
Aug 19 15:36:31 [cardmgr] + FATAL: Module sram_mtd not found.
Aug 19 15:36:31 [cardmgr] modprobe exited with status 1


And it keeps doing that until I restart cardmgr. After that:

/* Restart of cardmgr */
Aug 19 15:37:52 [cardmgr] exiting
Aug 19 15:37:54 [cardmgr] watching 1 sockets
Aug 19 15:37:54 [kernel] cs: IO port probe 0x0c00-0x0cff: clean.
Aug 19 15:37:54 [kernel] cs: IO port probe 0x0800-0x08ff: clean.
Aug 19 15:37:54 [kernel] cs: IO port probe 0x0100-0x04ff: excluding
0x2c8-0x2cf 0x378-0x37f 0x4d0-0x4d7
Aug 19 15:37:54 [kernel] cs: IO port probe 0x0a00-0x0aff: clean.
Aug 19 15:37:54 [cardmgr] starting, version is 3.2.4
Aug 19 15:37:59 [su(pam_unix)] session closed for user root
Aug 19 15:39:13 [cardmgr] socket 0: NETGEAR MA401RA 11Mbps 802.11 WLAN
Card
Aug 19 15:39:13 [cardmgr] executing: 'modprobe orinoco_cs'
Aug 19 15:39:14 [cardmgr] executing: './network start eth1'

And it's working properly. Except for the insert-twice-issue.. dmesg
attached.

Here is lspci -vvv for the cardbus:

00:0a.0 CardBus bridge: O2 Micro, Inc. OZ6912 Cardbus Controller
        Subsystem: Acer Incorporated [ALI]: Unknown device 001d
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping+ SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 168
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at 10000000 (32-bit, non-prefetchable) [size=4K]
        Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
        Memory window 0: 10400000-107ff000 (prefetchable)
        Memory window 1: 10800000-10bff000
        I/O window 0: 00001000-000010ff
        I/O window 1: 00001400-000014ff
        BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+
PostWrite+
        16-bit legacy interface ports at 0001

uname -a :
Linux vega 2.6.0-test3 #6 Fri Aug 15 13:00:17 CEST 2003 i686 mobile AMD
Athlon(tm) XP 1400+  AuthenticAMD GNU/Linux

Thanks.

-- 
Henrik Persson  nix@syndicalist.net

[-- Attachment #2: dmesg --]
[-- Type: application/octet-stream, Size: 10484 bytes --]

Linux version 2.6.0-test3 (root@vega.nix.homeunix.net) (gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r2, propolice)) #6 Fri Aug 15 13:00:17 CEST 2003
Video mode to be used for restore is 317
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000000eff0000 (usable)
 BIOS-e820: 000000000eff0000 - 000000000effffc0 (ACPI data)
 BIOS-e820: 000000000effffc0 - 000000000f000000 (ACPI NVS)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
239MB LOWMEM available.
On node 0 totalpages: 61424
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 57328 pages, LIFO batch:13
  HighMem zone: 0 pages, LIFO batch:1
ACPI: RSDP (v000 OID_00                     ) @ 0x000e4010
ACPI: RSDT (v001 OID_00 RSDT_000 12336.12336) @ 0x0efffbc0
ACPI: FADT (v002 INSYDE FACP_000 00000.00256) @ 0x0efffac0
ACPI: BOOT (v001 INSYDE SYS_BOOT 00000.00256) @ 0x0efffb50
ACPI: DBGP (v001 INSYDE SYS_DBGP 00000.00256) @ 0x0efffb80
ACPI: DSDT (v001 INSYDE   VT8362 00000.04096) @ 0x00000000
ACPI: BIOS passes blacklist
Building zonelist for node : 0
Kernel command line: BOOT_IMAGE=Linux ro root=301
Initializing CPU#0
PID hash table entries: 1024 (order 10: 8192 bytes)
Detected 1200.357 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 2367.48 BogoMIPS
Memory: 239232k/245696k available (2142k kernel code, 5764k reserved, 866k data, 144k init, 0k highmem)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
-> /dev
-> /dev/console
-> /root
CPU:     After generic identify, caps: 0183f9ff c1cbf9ff 00000000 00000000
CPU:     After vendor identify, caps: 0183f9ff c1cbf9ff 00000000 00000000
Enabling disabled K7/SSE Support.
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU:     After all inits, caps: 0383f9ff c1cbf9ff 00000000 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD mobile AMD Athlon(tm) XP 1400+  stepping 00
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
Initializing RT netlink socket
PCI: PCI BIOS revision 2.10 entry at 0xe8a64, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
BIO: pool of 256 setup, 14Kb (56 bytes/bio)
biovec pool[0]:   1 bvecs: 256 entries (12 bytes)
biovec pool[1]:   4 bvecs: 256 entries (48 bytes)
biovec pool[2]:  16 bvecs: 256 entries (192 bytes)
biovec pool[3]:  64 bvecs: 256 entries (768 bytes)
biovec pool[4]: 128 bvecs: 256 entries (1536 bytes)
biovec pool[5]: 256 bvecs: 256 entries (3072 bytes)
ACPI: Subsystem revision 20030714
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
Disabling VIA memory write queue (PCI ID 0305, rev 80): [55] 3c & 1f -> 1c
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Embedded Controller [EC0] (gpe 1)
ACPI: PCI Interrupt Link [LNKA] (IRQs 10 *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 10 11, disabled)
ACPI: PCI Interrupt Link [LNKC] (IRQs *10)
ACPI: PCI Interrupt Link [LNKD] (IRQs 10 *11)
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
Linux Kernel Card Services 3.1.22
  options:  [pci] [cardbus] [pm]
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
PCI: Cannot allocate resource region 0 of device 0000:00:0a.0
vesafb: framebuffer at 0x90000000, mapped to 0xcf807000, size 15296k
vesafb: mode is 1024x768x16, linelength=2048, pages=8
vesafb: protected mode interface info at c000:7926
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
fb0: VESA VGA frame buffer device
Console: switching to colour frame buffer device 128x48
pty: 256 Unix98 ptys configured
SBF: Simple Boot Flag extension found and enabled.
SBF: Setting boot flags 0x1
Machine check exception polling timer started.
powernow: AMD K7 CPU detected.
powernow: PowerNOW! Technology present. Can scale: frequency and voltage.
powernow: Found PSB header at c00e50e0
powernow: Table version: 0x12
powernow: Flags: 0x0 (Mobile voltage regulator)
powernow: Settling Time: 100 microseconds.
powernow: Has 1 PST tables. (Only dumping ones relevant to this CPU).
powernow: PST:0 (@c00e50f0)
powernow:  cpuid: 0x780	fsb: 100	maxFID: 0x2	startvid: 0xb
powernow:    FID: 0x4 (5.0x [500MHz])	VID: 0x17 (1.100V)
powernow:    FID: 0x6 (6.0x [600MHz])	VID: 0x15 (1.150V)
powernow:    FID: 0x8 (7.0x [700MHz])	VID: 0x13 (1.200V)
powernow:    FID: 0xa (8.0x [800MHz])	VID: 0xe (1.300V)
powernow:    FID: 0xc (9.0x [900MHz])	VID: 0xe (1.300V)
powernow:    FID: 0xe (10.0x [1000MHz])	VID: 0xd (1.350V)
powernow:    FID: 0x0 (11.0x [1100MHz])	VID: 0xc (1.400V)
powernow:    FID: 0x2 (12.0x [1200MHz])	VID: 0xb (1.450V)

powernow: Minimum speed 500 MHz. Maximum speed 1200 MHz.
Journalled Block Device driver loaded
devfs: v1.22 (20021013) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
Applying VIA southbridge workaround.
ACPI: AC Adapter [ADP0] (off-line)
ACPI: Battery Slot [BAT0] (battery present)
ACPI: Power Button (FF) [PWRF]
ACPI: Lid Switch [LID]
ACPI: Processor [CPU0] (supports C1 C2)
ACPI: Thermal Zone [THRM] (41 C)
Real Time Clock Driver v1.11
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA Apollo Pro KT133/KM133/TwisterK chipset
agpgart: Maximum main memory to use for agp memory: 189M
agpgart: AGP aperture is 64M @ 0xa0000000
Using anticipatory scheduling elevator
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt8231 (rev 10) IDE UDMA100 controller on pci0000:00:11.1
    ide0: BM-DMA at 0x1100-0x1107, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0x1108-0x110f, BIOS settings: hdc:DMA, hdd:pio
hda: TOSHIBA MK2018GAP, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: QSI DVD-ROM SDR-083, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 39070080 sectors (20003 MB), CHS=38760/16/63, UDMA(100)
 /dev/ide/host0/bus0/target0/lun0: p1 p2 p3
hdc: ATAPI 24X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
Console: switching to colour frame buffer device 128x48
Yenta: CardBus bridge found at 0000:00:0a.0 [1025:001d]
Yenta IRQ list 0038, PCI irq11
Socket status: 30000007
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
uhci-hcd 0000:00:11.2: UHCI Host Controller
uhci-hcd 0000:00:11.2: irq 11, io base 00001200
uhci-hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
hub 1-0:0: USB hub found
hub 1-0:0: 2 ports detected
Initializing USB Mass Storage driver...
drivers/usb/core/usb.c: registered new driver usb-storage
USB Mass Storage support registered.
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
mice: PS/2 mouse device common for all mice
input: PC Speaker
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
input: PS/2 Generic Mouse on isa0060/serio4
serio: i8042 AUX3 port at 0x60,0x64 irq 12
input: AT Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
Advanced Linux Sound Architecture Driver Version 0.9.6 (Mon Jul 28 11:08:42 2003 UTC).
PCI: Setting latency timer of device 0000:00:11.5 to 64
ALSA device list:
  #0: VIA 82C686A/B rev40 at 0xe000, irq 10
NET4: Linux TCP/IP 1.0 for NET4.0
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 144k freed
Adding 491392k swap on /dev/hda2.  Priority:-1 extents:1
EXT3 FS on hda1, internal journal
via-rhine.c:v1.10-LK1.1.19-2.5  July-12-2003  Written by Donald Becker
  http://www.scyld.com/network/via-rhine.html
PCI: Enabling device 0000:00:12.0 (0001 -> 0003)
eth0: VIA VT6102 Rhine-II at 0xe800, 00:c0:9f:0d:d1:dd, IRQ 11.
eth0: MII PHY found at address 1, status 0x7829 advertising 01e1 Link 45e1.
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
EXT3 FS on hda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x2c8-0x2cf 0x378-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
eth0: Setting full-duplex based on MII #1 link partner capability of 45e1.
mtrr: 0x90000000,0x1000000 overlaps existing 0x90000000,0x800000
spurious 8259A interrupt: IRQ7.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x2c8-0x2cf 0x378-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
orinoco.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
orinoco_cs.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
eth1: Station identity xxxx:xxxx:xxxx:xxxx
eth1: Looks like an Intersil firmware version 1.3.6
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address XX:XX:XX:XX:XX:XX /* Yes, I censored this */
eth1: Station name "Prism  I"
eth1: ready
eth1: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f

Re: weird pcmcia problem

[Narayan Desai]

>>>>> "Russell" == Russell King <rmk@arm.linux.org.uk> writes:

  Russell> On Mon, Aug 18, 2003 at 07:34:59PM -0500, Narayan Desai
  Russell> wrote:
  >> Running 2.6.0-test3 (both with and without your recent yenta
  >> socket patches) pcmcia cards present during boot don't show up
  >> until they are removed and reinserted. Once reinserted, they work
  >> fine. This only seems to occur if yenta_socket is build into the
  >> kernel; if support is modular, cards appear to be recognized
  >> properly at boot time. I am running on a thinkpad t21.  Let me
  >> know if I can help with this problem in any way...  thanks

  Russell> As a general thing, when people report this problem (or any
  Russell> other problem), can they please include at least the
  Russell> following details please:

  Russell> - make/model of machine
  Russell> - type of cardbus bridge (from lspci)
  Russell> - type of card (pcmcia or cardbus)
  Russell> - make/model of card
  Russell> - full kernel dmesg (including yenta, card services
  Russell>   messages)
  Russell> - cardmgr messages from system log

This is an IBM thinkpad t21. the cardbus bridge is:
00:02.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00:02.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)

The problem is occurring with an orinoco gold pcmcia card.

the unable to map cs memory errors were the only odd thing in the
kernel messages, and it looks like your diagnosis was right on the
money. i these cardmgr messages:
Aug 18 20:38:06 topaz cardmgr[374]: watching 2 sockets
Aug 18 20:38:06 topaz cardmgr[375]: starting, version is 3.2.2
Aug 18 20:38:06 topaz cardmgr[375]: socket 0: Anonymous Memory
Aug 18 20:38:06 topaz cardmgr[375]: executing: 'modprobe memory_cs'
Aug 18 20:38:06 topaz cardmgr[375]: + FATAL: Module memory_cs not found.
Aug 18 20:38:06 topaz cardmgr[375]: modprobe exited with status 1
Aug 18 20:38:06 topaz cardmgr[375]: module /lib/modules/2.6.0-test3-p2/pcmcia/memory_cs.o not available
Aug 18 20:38:06 topaz cardmgr[375]: bind 'memory_cs' to socket 0 failed: Invalid argument

let me know if there is more info that would be useful.
 -nld

Re: weird pcmcia problem

[Russell King]

On Tue, Aug 19, 2003 at 02:16:23PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 19 Aug 2003 00:47:00 EDT, Valdis.Kletnieks@vt.edu said:
> 
> > On Mon, 18 Aug 2003 19:34:59 CDT, Narayan Desai <desai@mcs.anl.gov>  said:
> > > Running 2.6.0-test3 (both with and without your recent yenta socket
> > > patches) pcmcia cards present during boot don't show up until they are
> > > removed and reinserted. Once reinserted, they work fine. This only
> 
> > Same issue on 2.6.0-test3-mm2 on a Dell Latitude C840 with a TrueMobile 1150
> > wireless (uses orinoco_cs driver) - card is recognized at boot, and somewhat
> > configured:
> 
> Went to 2.6.0-test3-mm3, and the problem is resolved on my laptop.  Not sure if
> Narayan's machine is using a different "recent Yenta socket patches" than
> what's in -mm3, or if there's something ELSE that made the difference.

That wasn't expected.

Can you provide all the following information please:

- make/model of machine
- type of cardbus bridge (from lspci)
- type of card (pcmcia or cardbus)
- make/model of card
- full kernel dmesg (including yenta, card services messages)
- cardmgr messages from system log

thx.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html

Re: weird pcmcia problem

[Sven Dowideit]

thank god its not just my t21 :)

this is the same issue that I've had since somewhere between 2.5.70
2.5.75 (i didn't use any of the ones in between)

Russell - sorry for no tbugging you after OLS :) 

sven

On Tue, 2003-08-19 at 18:34, Russell King wrote:
> On Mon, Aug 18, 2003 at 07:34:59PM -0500, Narayan Desai wrote:
> > cs: warning: no high memory space available!
> > cs: unable to map card memory!
> > cs: unable to map card memory!
> 
> Hmm, this looks suspicious.  For some reason, we can't find any memory
> resources to map the CIS, so we can't identify the card type, which
> means we'll probably identify the card as a memory card.

Re: weird pcmcia problem

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 5953 bytes --]

On Tue, 19 Aug 2003 19:19:48 BST, Russell King said:

> That wasn't expected.

Well, I hadn't tried any Yenta patch on top of -mm2, so I wasn't sure..

> Can you provide all the following information please:
> 
> - make/model of machine

Dell Latitude C840

> - type of cardbus bridge (from lspci)


02:01.0 CardBus bridge: Texas Instruments PCI4451 PC card Cardbus Controller
        Subsystem: Dell Computer Corporation: Unknown device 00d5

> - type of card (pcmcia or cardbus)

%  cardctl ident 2
  product info: "Dell", "TrueMobile 1150 Series PC Card", "Version 01.01", ""
  manfid: 0x0156, 0x0002
  function: 6 (network)

> - make/model of card

> - full kernel dmesg (including yenta, card services messages)

Aug 19 14:04:19 turing-police kernel: Yenta: CardBus bridge found at 0000:02:01.0 [1028:00d5]
Aug 19 14:04:19 turing-police kernel: Yenta: Using CSCINT to route CSC interrupts to PCI
Aug 19 14:04:19 turing-police kernel: Yenta: Routing CardBus interrupts to PCI
Aug 19 14:04:19 turing-police kernel: Yenta: ISA IRQ list 00b8, PCI irq9
Aug 19 14:04:19 turing-police kernel: Socket status: 30000020
Aug 19 14:04:19 turing-police kernel: PCI: Enabling device 0000:02:01.1 (0000 -> 0002)
Aug 19 14:04:19 turing-police kernel: Yenta: CardBus bridge found at 0000:02:01.1 [1028:00d5]
Aug 19 14:04:19 turing-police kernel: Yenta: Using CSCINT to route CSC interrupts to PCI
Aug 19 14:04:19 turing-police kernel: Yenta: Routing CardBus interrupts to PCI
Aug 19 14:04:19 turing-police kernel: Yenta: ISA IRQ list 00b8, PCI irq9
Aug 19 14:04:19 turing-police kernel: Socket status: 30000006
Aug 19 14:04:19 turing-police kernel: Yenta: CardBus bridge found at 0000:02:03.0 [12a3:ab01]
Aug 19 14:04:19 turing-police kernel: Yenta: Enabling burst memory read transactions
Aug 19 14:04:19 turing-police kernel: Yenta: Using CSCINT to route CSC interrupts to PCI
Aug 19 14:04:20 turing-police kernel: Yenta: Routing CardBus interrupts to PCI
Aug 19 14:04:20 turing-police kernel: Yenta: ISA IRQ list 0000, PCI irq9
Aug 19 14:04:20 turing-police kernel: Socket status: 30000010

Aug 19 14:04:24 turing-police kernel: cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcffff 0xe0000-0xfffff
Aug 19 14:04:24 turing-police kernel: eth1: Station identity 001f:0001:0008:000a
Aug 19 14:04:24 turing-police kernel: eth1: Looks like a Lucent/Agere firmware version 8.10
Aug 19 14:04:24 turing-police kernel: eth1: Ad-hoc demo mode supported
Aug 19 14:04:24 turing-police kernel: eth1: IEEE standard IBSS ad-hoc mode supported
Aug 19 14:04:24 turing-police kernel: eth1: WEP supported, 104-bit key
Aug 19 14:04:25 turing-police kernel: eth1: MAC address 00:02:2D:5C:11:48
Aug 19 14:04:25 turing-police kernel: eth1: Station name "HERMES I"
Aug 19 14:04:25 turing-police kernel: eth1: ready
Aug 19 14:04:25 turing-police kernel: eth1: index 0x01: Vcc 3.3, irq 9, io 0x0100-0x013f
Aug 19 14:04:25 turing-police kernel: eth1: New link status: Connected (0001)
Aug 19 14:04:25 turing-police kernel: eth1: no IPv6 routers present

Aug 19 14:34:14 turing-police dhcpcd[746]: sending DHCP_REQUEST for 198.82.168.169 to 198.82.247.67
Aug 19 14:34:14 turing-police dhcpcd[746]: sendto: Socket operation on non-socket
Aug 19 14:34:14 turing-police dhcpcd[746]: broadcasting DHCP_REQUEST for 198.82.168.169
Aug 19 14:34:14 turing-police dhcpcd[746]: sendto: Socket operation on non-socket
Aug 19 14:34:14 turing-police dhcpcd[746]: dhcpStop: ioctl SIOCSIFADDR: Inappropriate ioctl for device
Aug 19 14:34:14 turing-police dhcpcd[746]: dhcpStop: ioctl SIOCSIFFLAGS: Inappropriate ioctl for device
Aug 19 14:34:14 turing-police dhcpcd[746]: broadcasting DHCP_DISCOVER
Aug 19 14:34:14 turing-police dhcpcd[746]: broadcastAddr option is missing in DHCP server response. Assuming 198.82.168.255
Aug 19 14:34:14 turing-police dhcpcd[746]: broadcasting second DHCP_DISCOVER

Aug 19 14:34:14 turing-police dhcpcd[746]: DHCP_OFFER received from  (198.82.247.67)
Aug 19 14:34:14 turing-police dhcpcd[746]: broadcasting DHCP_REQUEST for 198.82.168.169 

> - cardmgr messages from system log

Aug 19 14:04:13 turing-police pcmcia:  cardmgr.
Aug 19 14:04:13 turing-police cardmgr[657]: starting, version is 3.1.31
Aug 19 14:04:13 turing-police rc: Starting pcmcia:  succeeded
Aug 19 14:04:13 turing-police modprobe: FATAL: Module /dev/cm_657_2 not found. 
Aug 19 14:04:13 turing-police modprobe: FATAL: Module /dev/cm_657_5 not found. 
Aug 19 14:04:13 turing-police modprobe: FATAL: Module /dev/cm_657_8 not found. 
Aug 19 14:04:13 turing-police modprobe: FATAL: Module /dev/cm_657_11 not found.
Aug 19 14:04:13 turing-police cardmgr[657]: watching 3 sockets
Aug 19 14:04:13 turing-police cardmgr[657]: Card Services release does not match
Aug 19 14:04:13 turing-police cardmgr[657]: socket 0: CardBus hotplug device
Aug 19 14:04:14 turing-police cardmgr[657]: socket 2: Intersil PRISM2 11 Mbps Wireless Adapter 
Aug 19 14:04:14 turing-police cardmgr[657]: executing: 'modprobe hermes'
Aug 19 14:04:14 turing-police cardmgr[657]: + FATAL: Module hermes not found.
Aug 19 14:04:14 turing-police cardmgr[657]: modprobe exited with status 1
Aug 19 14:04:14 turing-police cardmgr[657]: module /lib/modules/2.6.0-test3-mm3/pcmcia/hermes.o not available
Aug 19 14:04:14 turing-police cardmgr[657]: executing: 'modprobe orinoco'
Aug 19 14:04:14 turing-police cardmgr[657]: + FATAL: Module orinoco not found.
Aug 19 14:04:14 turing-police cardmgr[657]: modprobe exited with status 1
Aug 19 14:04:14 turing-police cardmgr[657]: module /lib/modules/2.6.0-test3-mm3/pcmcia/orinoco.o not available
Aug 19 14:04:15 turing-police cardmgr[657]: executing: './network start eth1'
Aug 19 14:04:15 turing-police /etc/hotplug/net.agent: invoke ifup eth1

Looking at an earlier boot, the only difference seems to be that net.agent is now
invoking 'ifup'...

Now to figure out why the 100mbit Ethernet won't answer ARP if the wireless card is up,
I suspect it's related to that other thread...  :)

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Re: weird pcmcia problem

[Sven Dowideit]

On Tue, 2003-08-19 at 21:45, Russell King wrote:
> - make/model of machine
IBM thinkpad t21
> - type of cardbus bridge (from lspci)
00:02.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)
        Subsystem: IBM: Unknown device 0130
        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: 168, cache line size 08
        Interrupt: pin A routed to IRQ 9
        Region 0: Memory at 50000000 (32-bit, non-prefetchable)
[size=4K]
        Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
        Memory window 0: 20000000-203ff000 (prefetchable)
        Memory window 1: 20400000-207ff000
        I/O window 0: 00001400-000014ff
        I/O window 1: 00002400-000024ff
        BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+
PostWrite+
        16-bit legacy interface ports at 0001

00:02.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)
        Subsystem: IBM: Unknown device 0130
        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: 168, cache line size 08
        Interrupt: pin B routed to IRQ 9
        Region 0: Memory at 50100000 (32-bit, non-prefetchable)
[size=4K]
        Bus: primary=00, secondary=06, subordinate=09, sec-latency=176
        Memory window 0: 20800000-20bff000 (prefetchable)
        Memory window 1: 20c00000-20fff000
        I/O window 0: 00002800-000028ff
        I/O window 1: 00002c00-00002cff
        BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+
PostWrite+
        16-bit legacy interface ports at 0001

> - type of card (pcmcia or cardbus)

> - make/model of card
cisco aironet 340
> - full kernel dmesg (including yenta, card services messages)

> - cardmgr messages from system log

Re: weird pcmcia problem

[Sven Dowideit]

On Tue, 2003-08-19 at 21:45, Russell King asked for:

> - make/model of machine
IBM thinkpad t21

> - type of cardbus bridge (from lspci)
00:02.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)
        Subsystem: IBM: Unknown device 0130
        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: 168, cache line size 08
        Interrupt: pin A routed to IRQ 9
        Region 0: Memory at 50000000 (32-bit, non-prefetchable)
[size=4K]
        Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
        Memory window 0: 20000000-203ff000 (prefetchable)
        Memory window 1: 20400000-207ff000
        I/O window 0: 00001400-000014ff
        I/O window 1: 00002400-000024ff
        BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+
PostWrite+
        16-bit legacy interface ports at 0001

00:02.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)
        Subsystem: IBM: Unknown device 0130
        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: 168, cache line size 08
        Interrupt: pin B routed to IRQ 9
        Region 0: Memory at 50100000 (32-bit, non-prefetchable)
[size=4K]
        Bus: primary=00, secondary=06, subordinate=09, sec-latency=176
        Memory window 0: 20800000-20bff000 (prefetchable)
        Memory window 1: 20c00000-20fff000
        I/O window 0: 00002800-000028ff
        I/O window 1: 00002c00-00002cff
        BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+
PostWrite+
        16-bit legacy interface ports at 0001

> - type of card (pcmcia or cardbus)
cardbus

> - make/model of card
cisco aironet 340

> - full kernel dmesg (including yenta, card services messages)
Linux Kernel Card Services 3.1.22
  options:  [pci] [cardbus] [pm]
Intel PCIC probe: not found.
PCI: Found IRQ 9 for device 0000:00:02.0
PCI: Sharing IRQ 9 with 0000:00:05.0
PCI: Sharing IRQ 9 with 0000:01:00.0
Yenta: CardBus bridge found at 0000:00:02.0 [1014:0130]
Yenta IRQ list 00b8, PCI irq9
Socket status: 30000010
PCI: Found IRQ 9 for device 0000:00:02.1
Yenta: CardBus bridge found at 0000:00:02.1 [1014:0130]
Yenta IRQ list 00b8, PCI irq9
Socket status: 30000006
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x3c0-0x3df 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.

(then when i re-insert it)
airo: Doing fast bap_reads
airo: MAC enabled eth0 0:40:96:33:e:a4
eth0: index 0x05: Vcc 5.0, Vpp 5.0, irq 3, io 0x0100-0x013f
bad: scheduling while atomic!
Call Trace:
 [<c011a487>] schedule+0x3b7/0x3c0
 [<e0852d3a>] sendcommand+0xaa/0xe0 [airo]
 [<e0852c5c>] issuecommand+0x5c/0x90 [airo]
 [<e085321a>] PC4500_accessrid+0x4a/0x90 [airo]
 [<c010b855>] error_code+0x2d/0x38
 [<e08532c1>] PC4500_readrid+0x61/0x130 [airo]
 [<e0850661>] readStatsRid+0x31/0x50 [airo]
 [<e0850d17>] airo_read_stats+0x67/0x150 [airo]
 [<c01189c8>] pgd_alloc+0x18/0x20
 [<c013745c>] find_get_page+0x2c/0x60
 [<c013861e>] filemap_nopage+0x28e/0x320
 [<c013b131>] buffered_rmqueue+0xd1/0x170
 [<c017fd2c>] proc_alloc_inode+0x4c/0x80
 [<c017fd2c>] proc_alloc_inode+0x4c/0x80
 [<c016afec>] alloc_inode+0x1c/0x140
 [<c013ae60>] __rmqueue+0xd0/0x120
 [<c013b131>] buffered_rmqueue+0xd1/0x170
 [<c0202466>] vsnprintf+0x246/0x470
 [<e0850e16>] airo_get_stats+0x16/0x20 [airo]
 [<c0299bbb>] dev_seq_printf_stats+0xeb/0x100
 [<c0299bf8>] dev_seq_show+0x28/0x90
 [<c01705ad>] seq_read+0x1dd/0x310
 [<c0152498>] vfs_read+0xb8/0x130
 [<c0152742>] sys_read+0x42/0x70
 [<c010ae4b>] syscall_call+0x7/0xb

bad: scheduling while atomic!
Call Trace:
 [<c011a487>] schedule+0x3b7/0x3c0
 [<e0852d3a>] sendcommand+0xaa/0xe0 [airo]
 [<e0852c5c>] issuecommand+0x5c/0x90 [airo]
 [<e085321a>] PC4500_accessrid+0x4a/0x90 [airo]
 [<e08532c1>] PC4500_readrid+0x61/0x130 [airo]
 [<e0850661>] readStatsRid+0x31/0x50 [airo]
 [<e0850d17>] airo_read_stats+0x67/0x150 [airo]
 [<c0202466>] vsnprintf+0x246/0x470
 [<e0850e16>] airo_get_stats+0x16/0x20 [airo]
 [<c0299bbb>] dev_seq_printf_stats+0xeb/0x100
 [<c0299bf8>] dev_seq_show+0x28/0x90
 [<c01705ad>] seq_read+0x1dd/0x310
 [<c0152498>] vfs_read+0xb8/0x130
 [<c0152742>] sys_read+0x42/0x70
 [<c010ae4b>] syscall_call+0x7/0xb
 


> - cardmgr messages from system log
Aug 20 09:37:19 sven cardmgr[322]: starting, version is 3.2.2
Aug 20 09:37:19 sven cardmgr[322]: socket 0: Anonymous Memory
Aug 20 09:37:19 sven cardmgr[322]: executing: 'modprobe memory_cs'
Aug 20 09:37:19 sven cardmgr[322]: + FATAL: Module memory_cs not found.
Aug 20 09:37:19 sven cardmgr[322]: modprobe exited with status 1
Aug 20 09:37:19 sven cardmgr[322]: module /lib/modules/2.6.0-test3/pcmcia/memory_cs.o not available
Aug 20 09:37:19 sven cardmgr[322]: bind 'memory_cs' to socket 0 failed: Invalid argument
Aug 20 09:37:19 sven cardmgr[322]: socket 0: Anonymous Memory
Aug 20 09:38:35 sven cardmgr[322]: executing: 'modprobe -r memory_cs'
Aug 20 09:38:35 sven cardmgr[322]: + FATAL: Module memory_cs not found.
Aug 20 09:38:35 sven cardmgr[322]: modprobe exited with status 1
Aug 20 09:38:44 sven cardmgr[322]: socket 0: Aironet PC4800
Aug 20 09:38:44 sven cardmgr[322]: executing: 'modprobe airo_cs'
Aug 20 09:38:45 sven cardmgr[322]: executing: './network start eth0'
Aug 20 09:38:45 sven cardmgr[322]: + Ignoring unknown interface eth0=eth0.