Re: [bug report] pcmcia in kernel 2.4.0-test8
Alessandro Suardi wrote: > Kernel pcmcia code works fine with 2.4.0-test8 and my Xircom RBEM56G100TX, > in fact I am writing from my laptop connected through it. See lsmod output > and relevant part of .config. > > [asuardi@princess asuardi]$ lsmod > Module Size Used by > serial_cb 1456 1 > xircom_tulip_cb30168 1 > cb_enabler 2536 2 [serial_cb] > ds 6540 2 [cb_enabler] > yenta_socket9932 4 > pcmcia_core39264 0 [cb_enabler ds yenta_socket] > sb 1712 1 (autoclean) > sb_lib 33660 0 (autoclean) [sb] > uart401 6436 0 (autoclean) [sb_lib] > [asuardi@princess asuardi]$ For a good many people, yes it does work. For this hardware it doesn't work. pcmcia_core and yenta_socket are the only two modules I can load, and once loaded they can't be unloaded. Trying to rmmod yenta_socket yeilds a segfault and the module remains in a (deleted) state. The kernel pcmcia can't get the sockets set up correctly. It used to work; on 1 socket only and randomly blew up the kernel. The other socket hung the interrupts. -d -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." begin:vcard n:Ford;David x-mozilla-html:TRUE org:http://www.kalifornia.com/images/paradise.jpg"> adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Blue Labs Developer x-mozilla-cpt:;28256 fn:David Ford end:vcard
Re: [bug report] pcmcia in kernel 2.4.0-test8
David Ford wrote: > > Summary: > > Kernel pcmcia code doesn't work. > DHinds pcmcia code works only if kernel pcmcia code is completely disabled. > USB Pegasus driver fails when kernel pcmcia code is enabled. > Kernel pcmcia code works fine with 2.4.0-test8 and my Xircom RBEM56G100TX, in fact I am writing from my laptop connected through it. See lsmod output and relevant part of .config. [asuardi@princess asuardi]$ lsmod Module Size Used by serial_cb 1456 1 xircom_tulip_cb30168 1 cb_enabler 2536 2 [serial_cb] ds 6540 2 [cb_enabler] yenta_socket9932 4 pcmcia_core39264 0 [cb_enabler ds yenta_socket] sb 1712 1 (autoclean) sb_lib 33660 0 (autoclean) [sb] uart401 6436 0 (autoclean) [sb_lib] [asuardi@princess asuardi]$ CONFIG_PCMCIA=m CONFIG_CARDBUS=y CONFIG_NET_PCMCIA=y CONFIG_PCMCIA_XIRTULIP=m CONFIG_PCMCIA_SERIAL=m CONFIG_PCMCIA_SERIAL_CB=m The only hack I've done is to work around the known cardmgr issue with the 2.4 API not providing proper device names. I haven't tried 2.2.18pre7 but pre3 broke tulip_cb for the Xircom and pre5 hadn't fixed it yet. Ciao, --alessandro <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Linux: kernel 2.2.18p5/2.4.0-t8 glibc-2.1.3 gcc-2.95.2 binutils-2.10.0.24 Oracle: Oracle8i 8.1.6.1.0 Enterprise Edition for Linux motto: Tell the truth, there's less to remember. - 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/
[bug report] pcmcia in kernel 2.4.0-test8
Summary:
Kernel pcmcia code doesn't work.
DHinds pcmcia code works only if kernel pcmcia code is completely
disabled.
USB Pegasus driver fails when kernel pcmcia code is enabled.
Attached is a text writeup of several tests.
-d
--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."
Test reports:
dmesg
dump_cardbus
dump_cis
dump_pirq
lspci
sed -n '/^CONFIG.*\(CARDBUS\|PCMCIA\)/ {s/CONFIG_// p;}' .config
physical layout, two CB sockets. According to dhinds package, the bottom
socket is #0 and the top socket is #1
===
test8:
+ reiserfs 3.6.14
kernel pcmcia (pci=biosirq)
PCMCIA=m
CARDBUS=y
NET_PCMCIA=y
PCMCIA_PCNET=m
NET_PCMCIA_RADIO=y
PCMCIA_RAYCS=m
PCMCIA_SERIAL=m
PCMCIA_SERIAL_CS=m
PCMCIA_SERIAL_CB=m
>modprobe yenta_socket
yenta_socket9740 0
pcmcia_core39808 0 [yenta_socket]
>dmesg
Linux PCMCIA Card Services 3.1.20
options: [pci] [cardbus] [pm]
PCI: No IRQ known for interrupt pin B of device 00:03.1.
Yenta: unable to register irq 0
PCI: No IRQ known for interrupt pin A of device 00:03.0.
Yenta: unable to register irq 0
>modprobe ds
/lib/modules/2.4.0-test8/kernel/drivers/pcmcia/ds.o: init_module: Operation not
permitted
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO
or IRQ parameters
/lib/modules/2.4.0-test8/kernel/drivers/pcmcia/ds.o: insmod
/lib/modules/2.4.0-test8/kernel/drivers/pcmcia/ds.o failed
/lib/modules/2.4.0-test8/kernel/drivers/pcmcia/ds.o: insmod ds failed
>dmesg
ds: no socket drivers loaded!
>strace -o /tmp/out -s 512 -f rmmod yenta_socket
>tail -n 5 /tmp/out
1317 query_module(NULL, QM_MODULES, { /* 2 entries */ }, 2) = 0
1317 query_module("yenta_socket", QM_INFO, {address=0xcc90b000, size=9740,
flags=MOD_RUNNING|MOD_VISITED|MOD_USED_ONCE, usecount=0}, 16) = 0
1317 query_module("pcmcia_core", QM_INFO, {address=0xcc90, size=39808,
flags=MOD_RUNNING|MOD_USED_ONCE, usecount=0}, 16) = 0
1317 delete_module("yenta_socket"
1317 +++ killed by SIGSEGV +++
>lsmod
yenta_socket 0 0 (deleted)
pcmcia_core39808 0 [yenta_socket]
++ reboot
test8:
+ reiserfs 3.6.14
dhinds pcmcia (pci=biosirq)
>modprobe pcmcia_core
>dmesg
Linux PCMCIA Card Services 3.1.21
kernel build: 2.4.0-test8 #4 Thu Sep 14 21:10:53 PDT 2000
options: [pci] [cardbus] [apm]
>modprobe i82365
>dmesg
Intel PCIC probe: <4>PCI: No IRQ known for interrupt pin A of device
00:03.0.
PCI: No IRQ known for interrupt pin B of device 00:03.1.
Ricoh RL5C478 rev 03 PCI-to-CardBus at slot 00:03, mem 0x1000
host opts [0]: [serial irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 168/176] [bus
2/3]
host opts [1]: [serial irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 168/176] [bus
4/5]
ISA irqs (default) = 3,4,7,11 polling interval = 1000 ms
>modprobe ds
>dmesg
cs: cb_alloc(bus 2): vendor 0x1011, device 0x0019
>modprobe cb_enabler
>modprobe tulip_cb
>cardmgr
>dmesg
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x398-0x39f 0x3c0-0x3df 0x400-0x44f
0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: cb_config(bus 2)
fn 0 bar 1: io 0x200-0x27f
fn 0 bar 2: mem 0x600c-0x600c03ff
fn 0 rom: mem 0x6008-0x600b
irq 3
cs: cb_enable(bus 2)
bridge io map 0 (flags 0x21): 0x200-0x27f
bridge mem map 0 (flags 0x1): 0x6008-0x600c0fff
tulip_attach(device 02:00.0)
tulip.c:v0.91g-ppc 7/16/99 [EMAIL PROTECTED] (modified by
[EMAIL PROTECTED] for XIRCOM CBE, fixed by Doug Ledford)
eth1: Digital DS21143 Tulip rev 65 at 0x200, 00:E0:98:70:1E:AF, IRQ 3.
eth1: EEPROM default media type Autosense.
eth1: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
eth1: MII transceiver #0 config 3000 status 7809 advertising 01e1.
>dump_pirq
Interrupt routing table found at address 0xf5a80:
Version 1.0, size 0x0080
Interrupt router is device 00:07.0
PCI exclusive interrupt mask: 0x
Compatible router: vendor 0x8086 device 0x1234
Device 00:01.0 (slot 0):
INTA: link 0x60, irq mask 0x0420
Device 00:03.0 (slot 0):
INTA: link 0x60, irq mask 0x0420
INTB: link 0x61, irq mask 0x0420
Device 00:04.0 (slot 0):
INTA: link 0x61, irq mask 0x0420
Device 00:05.0 (slot 0):
INTA: link 0x60, irq mask 0x0420
Device 00:07.0 (slot 0):
INTA: link 0xfe, irq mask 0x4000
INTB: link 0xff, irq mask 0x8000
INTD: link 0x63, irq mask 0x0200
Device 00:11.0 (slot 1):
INTA: link 0x60, irq mask 0x0420
INTB: link 0x61, irq mask 0x0420
INTC: link 0x62, irq mask 0x0800
INTD: link 0x61, irq mask 0x0420
Interrupt router: Intel 82371AB PIIX4/PIIX4E PCI-to-ISA bridge
PIRQ1 (link 0x60): irq 10
PIRQ2 (link 0x61):
[bug report] pcmcia in kernel 2.4.0-test8
Summary:
Kernel pcmcia code doesn't work.
DHinds pcmcia code works only if kernel pcmcia code is completely
disabled.
USB Pegasus driver fails when kernel pcmcia code is enabled.
Attached is a text writeup of several tests.
-d
--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."
Test reports:
dmesg
dump_cardbus
dump_cis
dump_pirq
lspci
sed -n '/^CONFIG.*\(CARDBUS\|PCMCIA\)/ {s/CONFIG_// p;}' .config
physical layout, two CB sockets. According to dhinds package, the bottom
socket is #0 and the top socket is #1
===
test8:
+ reiserfs 3.6.14
kernel pcmcia (pci=biosirq)
PCMCIA=m
CARDBUS=y
NET_PCMCIA=y
PCMCIA_PCNET=m
NET_PCMCIA_RADIO=y
PCMCIA_RAYCS=m
PCMCIA_SERIAL=m
PCMCIA_SERIAL_CS=m
PCMCIA_SERIAL_CB=m
modprobe yenta_socket
yenta_socket9740 0
pcmcia_core39808 0 [yenta_socket]
dmesg
Linux PCMCIA Card Services 3.1.20
options: [pci] [cardbus] [pm]
PCI: No IRQ known for interrupt pin B of device 00:03.1.
Yenta: unable to register irq 0
PCI: No IRQ known for interrupt pin A of device 00:03.0.
Yenta: unable to register irq 0
modprobe ds
/lib/modules/2.4.0-test8/kernel/drivers/pcmcia/ds.o: init_module: Operation not
permitted
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO
or IRQ parameters
/lib/modules/2.4.0-test8/kernel/drivers/pcmcia/ds.o: insmod
/lib/modules/2.4.0-test8/kernel/drivers/pcmcia/ds.o failed
/lib/modules/2.4.0-test8/kernel/drivers/pcmcia/ds.o: insmod ds failed
dmesg
ds: no socket drivers loaded!
strace -o /tmp/out -s 512 -f rmmod yenta_socket
tail -n 5 /tmp/out
1317 query_module(NULL, QM_MODULES, { /* 2 entries */ }, 2) = 0
1317 query_module("yenta_socket", QM_INFO, {address=0xcc90b000, size=9740,
flags=MOD_RUNNING|MOD_VISITED|MOD_USED_ONCE, usecount=0}, 16) = 0
1317 query_module("pcmcia_core", QM_INFO, {address=0xcc90, size=39808,
flags=MOD_RUNNING|MOD_USED_ONCE, usecount=0}, 16) = 0
1317 delete_module("yenta_socket" unfinished ...
1317 +++ killed by SIGSEGV +++
lsmod
yenta_socket 0 0 (deleted)
pcmcia_core39808 0 [yenta_socket]
++ reboot
test8:
+ reiserfs 3.6.14
dhinds pcmcia (pci=biosirq)
modprobe pcmcia_core
dmesg
Linux PCMCIA Card Services 3.1.21
kernel build: 2.4.0-test8 #4 Thu Sep 14 21:10:53 PDT 2000
options: [pci] [cardbus] [apm]
modprobe i82365
dmesg
Intel PCIC probe: 4PCI: No IRQ known for interrupt pin A of device
00:03.0.
PCI: No IRQ known for interrupt pin B of device 00:03.1.
Ricoh RL5C478 rev 03 PCI-to-CardBus at slot 00:03, mem 0x1000
host opts [0]: [serial irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 168/176] [bus
2/3]
host opts [1]: [serial irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 168/176] [bus
4/5]
ISA irqs (default) = 3,4,7,11 polling interval = 1000 ms
modprobe ds
dmesg
cs: cb_alloc(bus 2): vendor 0x1011, device 0x0019
modprobe cb_enabler
modprobe tulip_cb
cardmgr
dmesg
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x398-0x39f 0x3c0-0x3df 0x400-0x44f
0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: cb_config(bus 2)
fn 0 bar 1: io 0x200-0x27f
fn 0 bar 2: mem 0x600c-0x600c03ff
fn 0 rom: mem 0x6008-0x600b
irq 3
cs: cb_enable(bus 2)
bridge io map 0 (flags 0x21): 0x200-0x27f
bridge mem map 0 (flags 0x1): 0x6008-0x600c0fff
tulip_attach(device 02:00.0)
tulip.c:v0.91g-ppc 7/16/99 [EMAIL PROTECTED] (modified by
[EMAIL PROTECTED] for XIRCOM CBE, fixed by Doug Ledford)
eth1: Digital DS21143 Tulip rev 65 at 0x200, 00:E0:98:70:1E:AF, IRQ 3.
eth1: EEPROM default media type Autosense.
eth1: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
eth1: MII transceiver #0 config 3000 status 7809 advertising 01e1.
dump_pirq
Interrupt routing table found at address 0xf5a80:
Version 1.0, size 0x0080
Interrupt router is device 00:07.0
PCI exclusive interrupt mask: 0x
Compatible router: vendor 0x8086 device 0x1234
Device 00:01.0 (slot 0):
INTA: link 0x60, irq mask 0x0420
Device 00:03.0 (slot 0):
INTA: link 0x60, irq mask 0x0420
INTB: link 0x61, irq mask 0x0420
Device 00:04.0 (slot 0):
INTA: link 0x61, irq mask 0x0420
Device 00:05.0 (slot 0):
INTA: link 0x60, irq mask 0x0420
Device 00:07.0 (slot 0):
INTA: link 0xfe, irq mask 0x4000
INTB: link 0xff, irq mask 0x8000
INTD: link 0x63, irq mask 0x0200
Device 00:11.0 (slot 1):
INTA: link 0x60, irq mask 0x0420
INTB: link 0x61, irq mask 0x0420
INTC: link 0x62, irq mask 0x0800
INTD: link 0x61, irq mask 0x0420
Interrupt router: Intel 82371AB PIIX4/PIIX4E PCI-to-ISA bridge
PIRQ1 (link 0x60): irq 10
PIRQ2 (link 0x61): irq 5
Re: [bug report] pcmcia in kernel 2.4.0-test8
David Ford wrote: Summary: Kernel pcmcia code doesn't work. DHinds pcmcia code works only if kernel pcmcia code is completely disabled. USB Pegasus driver fails when kernel pcmcia code is enabled. Kernel pcmcia code works fine with 2.4.0-test8 and my Xircom RBEM56G100TX, in fact I am writing from my laptop connected through it. See lsmod output and relevant part of .config. [asuardi@princess asuardi]$ lsmod Module Size Used by serial_cb 1456 1 xircom_tulip_cb30168 1 cb_enabler 2536 2 [serial_cb] ds 6540 2 [cb_enabler] yenta_socket9932 4 pcmcia_core39264 0 [cb_enabler ds yenta_socket] sb 1712 1 (autoclean) sb_lib 33660 0 (autoclean) [sb] uart401 6436 0 (autoclean) [sb_lib] [asuardi@princess asuardi]$ CONFIG_PCMCIA=m CONFIG_CARDBUS=y CONFIG_NET_PCMCIA=y CONFIG_PCMCIA_XIRTULIP=m CONFIG_PCMCIA_SERIAL=m CONFIG_PCMCIA_SERIAL_CB=m The only hack I've done is to work around the known cardmgr issue with the 2.4 API not providing proper device names. I haven't tried 2.2.18pre7 but pre3 broke tulip_cb for the Xircom and pre5 hadn't fixed it yet. Ciao, --alessandro [EMAIL PROTECTED] [EMAIL PROTECTED] Linux: kernel 2.2.18p5/2.4.0-t8 glibc-2.1.3 gcc-2.95.2 binutils-2.10.0.24 Oracle: Oracle8i 8.1.6.1.0 Enterprise Edition for Linux motto: Tell the truth, there's less to remember. - 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: [bug report] pcmcia in kernel 2.4.0-test8
Alessandro Suardi wrote: Kernel pcmcia code works fine with 2.4.0-test8 and my Xircom RBEM56G100TX, in fact I am writing from my laptop connected through it. See lsmod output and relevant part of .config. [asuardi@princess asuardi]$ lsmod Module Size Used by serial_cb 1456 1 xircom_tulip_cb30168 1 cb_enabler 2536 2 [serial_cb] ds 6540 2 [cb_enabler] yenta_socket9932 4 pcmcia_core39264 0 [cb_enabler ds yenta_socket] sb 1712 1 (autoclean) sb_lib 33660 0 (autoclean) [sb] uart401 6436 0 (autoclean) [sb_lib] [asuardi@princess asuardi]$ For a good many people, yes it does work. For this hardware it doesn't work. pcmcia_core and yenta_socket are the only two modules I can load, and once loaded they can't be unloaded. Trying to rmmod yenta_socket yeilds a segfault and the module remains in a (deleted) state. The kernel pcmcia can't get the sockets set up correctly. It used to work; on 1 socket only and randomly blew up the kernel. The other socket hung the interrupts. -d -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." begin:vcard n:Ford;David x-mozilla-html:TRUE org:img src="http://www.kalifornia.com/images/paradise.jpg" adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Blue Labs Developer x-mozilla-cpt:;28256 fn:David Ford end:vcard
