Re: CNet CNWLC-811 (PRISM2), kernel panic
On Sun, 2002-11-03 at 00:16, M. Warner Losh wrote: > pccardc pccard_mem # pccardc pccardmem PCCARD Memory address set to 0xd > pccardc pccard_mem 0xf800 # pccardc pccardmem 0xf800 PCCARD Memory address set to 0xf800 > pccardc dumpcis # pccardc pccardmem PCCARD Memory address set to 0xf800 # pccardc dumpcis Configuration data for card in slot 1 Tuple #1, code = 0x17 (Attribute memory descriptor), length = 3 000: d9 01 ff Attribute memory device information: Device number 1, type Function specific, WPS = ON Speed = 250nS, Memory block size = 2Kb, 1 units Tuple #2, code = 0x1d (Other conditions for attribute memory), length = 4 000: 01 d9 01 ff (MWAIT) Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 00 00 00 00 PCMCIA ID = 0x0, OEM ID = 0x0 Tuple #4, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #5, code = 0x15 (Version 1 info), length = 39 000: 05 00 4f 45 4d 00 31 31 4d 62 70 73 20 57 69 72 010: 65 6c 65 73 73 20 4c 41 4e 20 50 43 20 43 61 72 020: 64 20 56 2d 33 00 ff Version = 5.0, Manuf = [OEM], card vers = [11Mbps Wireless LAN PC Card V-3] Tuple #6, code = 0x1a (Configuration map), length = 6 000: 01 02 00 08 03 ff Reg len = 2, config register addr = 0x800, last config = 0xff Registers: XX-- 1 bytes in subtuples Tuple #7, code = 0x1b (Configuration entry), length = 15 000: c1 81 9d 71 55 2e 2e 2d fc 14 45 10 b8 ff 20 Config index = 0x1(default) Interface byte = 0x81 (I/O) wait signal supported Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 2.5 x 100mA Max current average over 10 ms: 2.5 x 100mA Power down supply current: 2.5 x 10mA Wait scale Speed = 1.2 x 10 us Card decodes 5 address lines, limited 8/16 Bit I/O IRQ modes: IRQs: 3 4 5 7 8 9 10 11 12 13 14 15 Max twin cards = 0 Misc attr: (Power down supported) Tuple #8, code = 0xff (Terminator), length = 0 2 slots found > > (well, where 0xf800 is the same address that NEWCARD reported it > was using for ccb bridge). > > Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CNet CNWLC-811 (PRISM2), kernel panic
In message: <[EMAIL PROTECTED]> Frode Nordahl <[EMAIL PROTECTED]> writes: : I get the following output from the driver: : wi0 at port 0x240-0x27f irq 11 slot 1 on pccard1 : wi0: timeout in wi_cmd 0x; event status 0x : wi0: timeout in wi_cmd 0x; event status 0x : wi0: timeout in wi_cmd 0x; event status 0x : wi0: init failed : wi0: timeout in wi_cmd 0x0021; event status 0x : wi0: timeout in wi_cmd 0x0021; event status 0x : wi0: mac read failed 5 : device_probe_and_attach: wi0 attach returned 5 This tells me that the wi driver likely doesn't support this (or 0x240 isn't a good place to put it, you might try 0x300 instead)... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CNet CNWLC-811 (PRISM2), kernel panic
In message: <[EMAIL PROTECTED]> Frode Nordahl <[EMAIL PROTECTED]> writes: : With OLDCARD it does not crash! I'll answer this twice... Can I ask you to do the following: pccardc pccard_mem pccardc pccard_mem 0xf800 pccardc dumpcis (well, where 0xf800 is the same address that NEWCARD reported it was using for ccb bridge). Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CNet CNWLC-811 (PRISM2), kernel panic
Hello, With OLDCARD it does not crash! After crafting a pccard.conf entry for the card, wi does not successfully attach to the card. Do you think it is feasible to add support for this card in the "wi" driver? Please don't hesitate to ask me for more information if you need it, thanks! If there is any dirty work to be done to make it work, tell me. I'll be more than happy to do it for you :) pccard.conf line: # CNet CNWLC-811 card "OEM" "11Mbps Wireless LAN PC Card V-3" config auto "wi" ? insert /etc/pccard_ether $device start remove /etc/pccard_ether $device stop I get the following output from the driver: wi0 at port 0x240-0x27f irq 11 slot 1 on pccard1 wi0: timeout in wi_cmd 0x; event status 0x wi0: timeout in wi_cmd 0x; event status 0x wi0: timeout in wi_cmd 0x; event status 0x wi0: init failed wi0: timeout in wi_cmd 0x0021; event status 0x wi0: timeout in wi_cmd 0x0021; event status 0x wi0: mac read failed 5 device_probe_and_attach: wi0 attach returned 5 # pccardc dumpcis Configuration data for card in slot 1 Tuple #1, code = 0x17 (Attribute memory descriptor), length = 3 000: d9 01 ff Attribute memory device information: Device number 1, type Function specific, WPS = ON Speed = 250nS, Memory block size = 2Kb, 1 units Tuple #2, code = 0x1d (Other conditions for attribute memory), length = 4 000: 01 d9 01 ff (MWAIT) Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 00 00 00 00 PCMCIA ID = 0x0, OEM ID = 0x0 Tuple #4, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #5, code = 0x15 (Version 1 info), length = 39 000: 05 00 4f 45 4d 00 31 31 4d 62 70 73 20 57 69 72 010: 65 6c 65 73 73 20 4c 41 4e 20 50 43 20 43 61 72 020: 64 20 56 2d 33 00 ff Version = 5.0, Manuf = [OEM], card vers = [11Mbps Wireless LAN PC Card V-3] Tuple #6, code = 0x1a (Configuration map), length = 6 000: 01 02 00 08 03 ff Reg len = 2, config register addr = 0x800, last config = 0xff Registers: XX-- 1 bytes in subtuples Tuple #7, code = 0x1b (Configuration entry), length = 15 000: c1 81 9d 71 55 2e 2e 2d fc 14 45 10 b8 ff 20 Config index = 0x1(default) Interface byte = 0x81 (I/O) wait signal supported Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 2.5 x 100mA Max current average over 10 ms: 2.5 x 100mA Power down supply current: 2.5 x 10mA Wait scale Speed = 1.2 x 10 us Card decodes 5 address lines, limited 8/16 Bit I/O IRQ modes: IRQs: 3 4 5 7 8 9 10 11 12 13 14 15 Max twin cards = 0 Misc attr: (Power down supported) Tuple #8, code = 0xff (Terminator), length = 0 2 slots found Mvh, Frode Nordahl On Sat, 2002-11-02 at 19:15, M. Warner Losh wrote: > Does this happen with OLDCARD? I have a couple of cards that do this, > but haven't been able to track down why this happens. > > Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CNet CNWLC-811 (PRISM2), kernel panic
Does this happen with OLDCARD? I have a couple of cards that do this, but haven't been able to track down why this happens. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CNet CNWLC-811 (PRISM2), kernel panic
Hello,
Just bought a CNet WLAN card, and it makes -CURRENT panic when inserted,
or if it is inserted while booting.
Userland installed from 20021101 snapshot.
Kernel from today: FreeBSD 5.0-CURRENT #0: Sat Nov 2 09:50:05 CET 2002
(second panic from me issuing panic from ddb)
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xd11fa000
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01aa2d5
stack pointer = 0x10:0xcc00494c
frame pointer = 0x10:0xcc004b78
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 9 (cbb1)
panic: from debugger
Fatal trap 3: breakpoint instruction fault while in kernel mode
instruction pointer = 0x8:0xc03b47d4
stack pointer = 0x10:0xcc0046bc
frame pointer = 0x10:0xcc0046c8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= IOPL = 0
current process = 9 (cbb1)
panic: from debugger
Uptime: 1m11s
Dumping 224 MB
ata0: resetting devices ..
done
16 32 48 64 80 96 112 128 144 160 176 192 208
---
#0 doadump () at ../../../kern/kern_shutdown.c:232
232 dumping++;
(kgdb) bt
#0 doadump () at ../../../kern/kern_shutdown.c:232
#1 0xc0242d89 in boot (howto=260) at ../../../kern/kern_shutdown.c:364
#2 0xc0242fd3 in panic () at ../../../kern/kern_shutdown.c:517
#3 0xc0147ac2 in db_panic () at ../../../ddb/db_command.c:450
#4 0xc0147a42 in db_command (last_cmdp=0xc0429b40, cmd_table=0x0,
aux_cmd_tablep=0xc0422fb8, aux_cmd_tablep_end=0xc0422fbc)
at ../../../ddb/db_command.c:346
#5 0xc0147b56 in db_command_loop () at ../../../ddb/db_command.c:472
#6 0xc014a80a in db_trap (type=12, code=0) at ../../../ddb/db_trap.c:72
#7 0xc03b4532 in kdb_trap (type=12, code=0, regs=0xcc00490c)
at ../../../i386/i386/db_interface.c:166
#8 0xc03c5e12 in trap_fatal (frame=0xcc00490c, eva=0)
at ../../../i386/i386/trap.c:841
#9 0xc03c5b22 in trap_pfault (frame=0xcc00490c, usermode=0,
eva=3508510720)
at ../../../i386/i386/trap.c:760
#10 0xc03c558d in trap (frame=
{tf_fs = -1037107176, tf_es = -872415216, tf_ds = -1072168944,
tf_edi = -1036984320, tf_esi = -1037051392, tf_ebp = -872395912, tf_isp
= -872396488, tf_ebx = 0, tf_edx = -786460672, tf_ecx = -1037071868,
tf_eax = 4096, tf_trapno = 12, tf_err = 0, tf_eip = -1071996203, tf_cs =
8, tf_eflags = 66050, tf_esp = -1037051392, tf_ss = -1036984320}) at
../../../i386/i386/trap.c:446
#11 0xc03b5d08 in calltrap () at {standard input}:98
#12 0xc01aa105 in pccard_read_cis (sc=0x0)
at ../../../dev/pccard/pccard_cis.c:98
#13 0xc01a7ab2 in pccard_attach_card (dev=0xc230e000)
at ../../../dev/pccard/pccard.c:168
#14 0xc01afd26 in cbb_insert (sc=0xc22f8a00) at card_if.h:66
#15 0xc01afad8 in cbb_event_thread (arg=0xc22f8a00)
at ../../../dev/pccbb/pccbb.c:917
#16 0xc022dab4 in fork_exit (callout=0xc01afa40 ,
arg=0x0,
frame=0x0) at ../../../kern/kern_fork.c:860
(kgdb)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
