Problems with wi on 5.1-CURRENT

Thu Jun 19 09:43:37 PDT 2003

Hi, 

I'm reposting this to freebsd-mobile with some more information after
Kevin Oberman and Warner suggested that I did so:

I posted this to current earlier today, but I'm not sure if that's the
best place. As WLAN cards tend to be for mobile devices I thought it
would be good to make a little noise here in case the people who
submitted the patches that broke wi are hanging around here :D

Hi,

I'm having some problems with wi in 5-CURRENT and 5.1.

I'm using a Proxim Skyline 802.11b PC Card (which I believe uses the
Prism 2 chipset)on Dell Inspiron 8200. The PC Card is using the 0.3.0
primary and 0.8.3 secondary firmware (which I believe is the latest).

The card works fine in Windows XP and FreeBSD 5.0, but in 5.1 if I use
ifconfig to bring up the card (for example during boot) it locks my
laptop up for about a minute while I get loads of error messages appear
on screen. Eventually I get a 'init failed' and 'tx buffer allocation
failed (error 12)' error, and although ifconfig says the interface is up
it doesn't actually work.

I'm using 128bit wep, but have tried it with wep turned off and I get
the same problem.

It doesn't work on 5.1-CURRENT:
FreeBSD hal9000 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Wed Jun 18 11:30:44
BST 2003     robhu at joshua.robhulme.com:/usr/obj/usr/src/sys/GENERIC
i386

But does work on 5.0-RELEASE:
FreeBSD hal9000 5.0-RELEASE-p7 FreeBSD 5.0-RELEASE-p7 #1: Tue Jun 17
02:42:05 BST 2003     root@:/usr/obj/usr/src/sys/GENERIC  i386

I am using the 5.1 world for both kernels.

I would really appreciate some help with this as I really need wi0 to
work so I can access the internet!

I am happy to try out suggestions, patches, etc...

I am including my rc.conf, dmesg, and an email from someone else
experiencing the same (or a similar) problem below:

# -- sysinstall generated deltas -- # Wed Apr 30 01:14:54 2003
# Created: Wed Apr 30 01:14:54 2003
# Enable network daemons for user convenience.
# Please make all changes to this file, not to /etc/defaults/rc.conf.
# This file now contains just the overrides from /etc/defaults/rc.conf.
kern_securelevel_enable="NO"
linux_enable="YES"
moused_enable="YES"
#sendmail_enable="YES"
sshd_enable="YES"
usbd_enable="YES"
devd_enable="YES"
hostname="hal9000"
#ifconfig_xl0="inet 192.168.7.99 netmask 255.255.255.0"
ifconfig_wi0="inet 192.168.7.49 netmask 255.255.255.0 channel 6" 
#ifconfig_wi0="inet 192.168.7.49 netmask 255.255.255.0 channel 6 wepmode
on wepkey 1:0x720E92DA7880F5673864C8081B"
defaultrouter="192.168.7.1"

Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights
reserved.
FreeBSD 5.1-CURRENT #1: Wed Jun 18 11:30:44 BST 2003
    robhu at joshua.robhulme.com:/usr/obj/usr/src/sys/GENERIC
Preloaded elf kernel "/boot/kernel/kernel" at 0xc06f3000.
Preloaded elf module "/boot/kernel/linux.ko" at 0xc06f31cc.
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 1695010476 Hz
CPU: Mobile Intel(R) Pentium(R) 4 - M CPU 1.70GHz (1695.01-MHz 686-class
CPU)
  Origin = "GenuineIntel"  Id = 0xf27  Stepping = 7

Features=0xbfebf9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,
CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
real memory  = 536748032 (511 MB)
avail memory = 513839104 (490 MB)
Pentium Pro MTRR support enabled
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcibios: BIOS version 2.10
Using $PIR table, 11 entries at 0xc00fbb90
pcib0: <Host to PCI bridge> at pcibus 0 on motherboard
pci0: <PCI bus> on pcib0
pci_cfgintr: 0:29 INTA BIOS irq 11
pci_cfgintr: 0:29 INTC BIOS irq 11
pci_cfgintr: 0:31 INTB BIOS irq 11
pci_cfgintr: 0:31 INTB BIOS irq 11
agp0: <Intel 82845 host to AGP bridge> mem 0xe8000000-0xebffffff at
device 0.0 on pci0
pcib1: <PCIBIOS PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci_cfgintr: 1:0 INTA BIOS irq 11
pci1: <display, VGA> at device 0.0 (no driver attached)
uhci0: <Intel 82801CA/CAM (ICH3) USB controller USB-A> port
0xbf80-0xbf9f irq 11 at device 29.0 on pci0
usb0: <Intel 82801CA/CAM (ICH3) USB controller USB-A> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ums0: Microsoft Microsoft Wheel Mouse Optical\M-., rev 1.10/1.21, addr
2, iclass 3/1
ums0: 3 buttons and Z dir.
uhci1: <Intel 82801CA/CAM (ICH3) USB controller USB-C> port
0xbf20-0xbf3f irq 11 at device 29.2 on pci0
usb1: <Intel 82801CA/CAM (ICH3) USB controller USB-C> on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
pcib2: <PCIBIOS PCI-PCI bridge> at device 30.0 on pci0
pci2: <PCI bus> on pcib2
pci_cfgintr: 2:0 INTA BIOS irq 11
pci_cfgintr: 2:1 INTA BIOS irq 11
pci_cfgintr: 2:1 INTA BIOS irq 11
pci_cfgintr: 2:1 INTA BIOS irq 11
xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xec80-0xecff mem
0xf8fffc00-0xf8fffc7f irq 11 at device 0.0 on pci2
xl0: Ethernet address: 00:08:74:e5:b9:b3
miibus0: <MII bus> on xl0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
cbb0: <TI4451 PCI-CardBus Bridge> irq 11 at device 1.0 on pci2
cardbus0: <CardBus bus> on cbb0
pccard0: <16-bit PCCard bus> on cbb0
cbb1: <TI4451 PCI-CardBus Bridge> irq 11 at device 1.1 on pci2
cardbus1: <CardBus bus> on cbb1
pccard1: <16-bit PCCard bus> on cbb1
fwohci0: <Texas Instruments PCI4451> mem
0xf8ff8000-0xf8ffbfff,0xf8fff000-0xf8fff7ff irq 11 at device 1.2 on pci2
fwohci0: OHCI version 1.0 (ROM=1)
fwohci0: No. of Isochronous channel is 4.
fwohci0: EUI64 32:4f:c0:00:3a:98:48:10
fwohci0: Phy 1394a available S400, 1 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: <IEEE1394(FireWire) bus> on fwohci0
if_fwe0: <Ethernet over FireWire> on firewire0
if_fwe0: Fake Ethernet address: 32:4f:c0:98:48:10
sbp0: <SBP2/SCSI over firewire> on firewire0
fwohci0: Initiate bus reset
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH3 UDMA100 controller> port
0xbfa0-0xbfaf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device
31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: <multimedia, audio> at device 31.5 (no driver attached)
pci0: <simple comms> at device 31.6 (no driver attached)
orm0: <Option ROMs> at iomem 0xcf800-0xcffff,0xc0000-0xcf7ff on isa0
pmtimer0 on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x64,0x60 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model GlidePoint, device ID 0
fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> at port
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on
isa0
unknown: <PNP0c01> can't assign resources (port)
unknown: <PNP0c01> can't assign resources (port)
unknown: <PNP0303> can't assign resources (port)
unknown: <PNP0f13> can't assign resources (irq)
unknown: <PNP0501> can't assign resources (port)
unknown: <PNP0401> can't assign resources (port)
unknown: <PNP0700> can't assign resources (port)
Timecounters tick every 10.000 msec
fwohci0: BUS reset
fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode
firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
firewire0: bus manager 0 (me)
wi0: <INTERSIL HFA384x/IEEE> at port 0x100-0x13f irq 11 function 0
config 1 on pccard1
wi0: 802.11 address: 00:00:c5:09:91:eb
wi0: using RF:PRISM2 MAC:HFA3841 CARD:HWB3163 rev.B
wi0: Intersil Firmware: Primary (0.3.0), Station (0.8.3)
wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ad0: 38154MB <IC25N040ATCS05-0> [77520/16/63] at ata0-master UDMA100
acd0: DVD-ROM <TOSHIBA DVD-ROM SD-C2612> at ata0-slave PIO4
Mounting root from ufs:/dev/ad0s2a
wi0: timeout in wi_seek to fc80/0
wi0: timeout in wi_cmd 0x0002; event status 0x8000
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: init failed
wi0: timeout in wi_seek to fc00/0
wi0: timeout in wi_seek to fc81/0
wi0: timeout in wi_seek to fc0c/0
wi0: timeout in wi_seek to fc02/0
wi0: timeout in wi_seek to fc03/0
wi0: timeout in wi_seek to fc04/0
wi0: timeout in wi_seek to fc01/0
wi0: timeout in wi_seek to fc09/0
wi0: timeout in wi_seek to fc07/0
wi0: timeout in wi_seek to fc83/0
wi0: timeout in wi_seek to fc82/0
wi0: timeout in wi_seek to fc06/0
wi0: timeout in wi_seek to fc2d/0
wi0: timeout in wi_seek to fc84/0
wi0: timeout in wi_seek to fc0e/0
wi0: timeout in wi_seek to fc85/0
wi0: timeout in wi_seek to fc2a/0
wi0: timeout in wi_seek to fc28/0
wi0: timeout in wi_seek to fc80/0
wi0: wi_cmd: busy bit won't clear.
wi0: failed to allocate 2372 bytes on NIC
wi0: tx buffer allocation failed (error 12)
wi0: interface not running
wi0: timeout in wi_seek to fc80/0
wi0: timeout in wi_seek to fc80/0
wi0: timeout in wi_seek to fc80/0

From: Oliver Brandmueller [ob at e-Gitt.NET]

Hello.

On Tue, Jun 17, 2003 at 11:48:13AM +0100, Robert Hulme wrote:
> I'm having some problems with wi in 5-CURRENT and 5.1 in general.

The problem came up between June 7 and June 15 in -CURRENT.

> I'm using a Proxim Skyline 802.11b PC Card (which I believe uses the 
> Prism 2 chipset). The PC Card is using the 0.3.0 primary and 0.8.3 
> secondary firmware (which I believe is the latest). I have a Dell 
> Inspiron 8200.

I have an Orinoco Gold Card. HP Omnibook 500. ACPI disabled (the
notebook has APM, with ACPI I don't see battery capacity). I tried with
and without WEP. The network works fine for some time, then blocks for a
while and starts working again.

> wi0: timeout in wi_cmd 0x0002; event status 0x8000
> wi0: wi_cmd: busy bit won't clear.

Looks similar at my Notebook:

wi0: <Lucent Technologies WaveLAN/IEEE> at port 0x100-0x13f irq 10
function 0 config 1 on pccard0
wi0: 802.11 address: 00:02:2d:51:a2:35
wi0: using Lucent Technologies, WaveLAN/IEEE
wi0: Lucent Firmware: Station (8.10.1)
wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wi0: bad alloc 21e != 207, cur 0 nxt 0
wi0: bad alloc 24b != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 26a != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 283 != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 29a != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 2b1 != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 2c8 != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 2df != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 2f6 != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 30d != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 324 != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 33b != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 352 != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 369 != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 380 != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 397 != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 3ae != 234, cur 0 nxt 0
wi0: device timeout
wi0: bad alloc 3c5 != 234, cur 0 nxt 0
wi0: device timeout
[and further]

complete dmesg, debugging output and stuff will be sent on request. I
was silently hoping that others have this problem too and somebody
cares, because I do not have any time to do anything at the moment. But
at least I offer my help in giving hints.

Thanx, Oliver

I hope someone can help me!
-Rob

> 
> -----Original Message-----
> From: Kevin Oberman [mailto:oberman at es.net] 
> Sent: 18 June 2003 22:16
> To: Robert Hulme
> Cc: freebsd-current at freebsd.org
> 
> > From: "Robert Hulme" <rob at robhulme.com>
> > Date: Wed, 18 Jun 2003 21:03:18 +0100
> > Sender: owner-freebsd-current at freebsd.org
> > 
> > Hi,
> > 
> > Yesterday I sent in an email to freebsd-current about the problems 
> > with wi in 5.1-Current. There haven't been any replies to suggest 
> > anyone knows why this is happening, how to fix it, or 
> anyone looking 
> > into fixing it.
> > 
> > Can someone please direct me as to which list (or which person) I 
> > should contact to make them aware of the problem?
> > 
> > I've checked the cvs entries @
> > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/wi/
> > 
> > All the recent changes were done by someone called 'imp'. Should I 
> > email this person? (if so what is there email address?)
> 
> 
> Could you let us know EXACTLY how you are doing the configuration?
> rc.conf or start_if.wi0? I use start_if.wi0 and it seems to work well.
> With the exception of the key, could you post what you use to 
> do the configuration?
> 
> 'imp' is M. Warner Losh who posts to both this list and 
> mobile quite often. He is the person primarily responsible 
> for laptop work and related stuff and is also core. 
> Unfortunately, like everyone else, his time is a bit limited.
> 
> I'm not sure that this will help you, but Warner is the one 
> with the non-disclosure specs for Prism chips, so he will 
> almost certainly be the one to get it fixed.
> 
> While I would not recommend running this way, could you try 
> not turning on WEP and see if the problem still occurs? This 
> would, at least, provide another data point.
> --
> R. Kevin Oberman, Network Engineer
> Energy Sciences Network (ESnet)
> Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
> E-mail: oberman at es.net			Phone: +1 510 486-8634
> 