Reproducible Lockup

Sun May 18 02:17:02 PDT 2003

On Sat, 17 May 2003, Jouni Malinen wrote:

> > I can reproducibly lockup the hostap-0.0.2 driver with RHL 7.3 stock
> 
> Please first test that with the latest CVS version of Host AP. It fixes
> at least two issues that were in v0.0.2 and caused kernel hanging. If
> you can reproduce that lockup with the latest CVS snapshot, please give
> some more details.

Yup, I tried 2003-05-18 - v0.0.3 and it reset the card very quickly. In
hindsight I don't think I was unloading the hostap-2002-10-12 I was using
before I can go back and try 0.0.2 but whichever I was running it lasted
a little longer than 2003-05-18.

SETUP:

IBM T30 with mini-pci "Intel" wireless running two floors up from the base
station but Intel software in Win2K reports connection is "Excellent". The
base station is Linksys WAP11 S4 4 port switch version 2. I'm using 128
bit wep on channel 9.

TEST:

I'm running "torture" clients for testing a thread pool based network
server event loop I'm writing. The clients are running on a workstation
connected directly to one of the ports on the WAP. The server is running
on the laptop with hostap. Each client writes 20000 separate requests (7
megs total) and then checks the response in a table to make sure it all
checks up. Over loopback I can run 40 clients at the same time for a total
of ~250MB. This takes ~60sec for overall throughput of about 3-4MB/sec.

This is what I see in the log:

2003-05-18 just reset the card immediately:

May 18 04:56:22 quark kernel: hostap_pci: Netdevice wlan0 unregistered
May 18 04:56:22 quark kernel: hostap_pci: Driver unloaded
May 18 04:56:22 quark /etc/hotplug/net.agent: NET unregister event not supported
May 18 04:56:49 quark kernel: hostap_pci: CVS (Jouni Malinen <jkmaline at cc.hut.fi>)
May 18 04:56:49 quark kernel: PCI: Found IRQ 11 for device 02:02.0
May 18 04:56:49 quark kernel: PCI: Sharing IRQ 11 with 00:1d.2
May 18 04:56:49 quark kernel: PCI: Sharing IRQ 11 with 00:1f.1
May 18 04:56:50 quark kernel: hostap_pci: Registered netdevice wlan0
May 18 04:56:50 quark kernel: wlan0: NIC: id=0x8013 v1.0.0
May 18 04:56:50 quark kernel: wlan0: PRI: id=0x15 v1.1.0
May 18 04:56:50 quark kernel: wlan0: STA: id=0x1f v1.4.9
May 18 04:56:50 quark kernel: wlan0: Intersil Prism2.5 PCI: mem=0xf8000000, irq=11
May 18 04:56:50 quark /etc/hotplug/net.agent: invoke ifup wlan0
May 18 04:58:12 quark kernel: hostap_pci: wlan0: resetting card

There was barely a blip on GKrellM. The 4 torture clients only processed 151, 310, 72, 295, and 458 requests. But before I was testing wither 0.0.2 or 2002-10-12 and it lasted a little longer. They managed to do between 7000 and 9000 requests each:

May 18 04:24:03 quark kernel: hostap_pci: Netdevice wlan0 unregistered
May 18 04:24:03 quark kernel: hostap_pci: Driver unloaded
May 18 04:24:03 quark /etc/hotplug/net.agent: NET unregister event not supported
May 18 04:24:32 quark kernel: hostap_pci: hostap_pci.c 0.0.0 2002-10-12 (SSH Communications Security Corp, Jouni Malinen)
May 18 04:24:32 quark kernel: hostap_pci: (c) Jouni Malinen <jkmaline at cc.hut.fi>
May 18 04:24:32 quark kernel: PCI: Found IRQ 11 for device 02:02.0
May 18 04:24:32 quark kernel: PCI: Sharing IRQ 11 with 00:1d.2
May 18 04:24:32 quark kernel: PCI: Sharing IRQ 11 with 00:1f.1
May 18 04:24:32 quark kernel: hostap_pci: Registered netdevice wlan0
May 18 04:24:32 quark kernel: wlan0: NIC: id=0x8013 v1.0.0
May 18 04:24:32 quark kernel: wlan0: PRI: id=0x15 v1.1.0
May 18 04:24:32 quark kernel: wlan0: STA: id=0x1f v1.4.9
May 18 04:24:32 quark kernel: wlan0: Intersil Prism2.5 PCI: mem=0xf8000000, irq=11
May 18 04:24:32 quark /etc/hotplug/net.agent: invoke ifup wlan0
May 18 04:24:37 quark su(pam_unix)[21606]: session closed for user root
May 18 04:26:32 quark kernel: hostap_pci: wlan0: resetting card
May 18 04:26:38 quark kernel: NETDEV WATCHDOG: wlan0: transmit timed out
May 18 04:26:38 quark kernel: wlan0 Tx timed out! Resetting card
May 18 04:26:39 quark kernel: hostap_pci: wlan0: resetting card
[root at quark xio-0.2.4]# date
Sun May 18 04:26:59 EDT 2003
[root at quark xio-0.2.4]# ifdown wlan0
[root at quark xio-0.2.4]# ifup wlan0
Error for wireless request "Set Frequency" (8B04) :
    SET failed on device wlan0 ; Invalid argument.
Error for wireless request "Set Encode" (8B2A) :
    SET failed on device wlan0 ; Invalid argument.
Error for wireless request "Set ESSID" (8B1A) :
    SET failed on device wlan0 ; Invalid argument.

The attached screenshot was with 4 clients and what appears to be
2002-10-12.

Could this just be an old-fashioned hardware conflict or something?

Otherwise everything works great. It's only when I "torture" it to
death. Bhwahahhah.

Mike

-- 
A  program should be written to model the concepts of the task it
performs rather than the physical world or a process because this
maximizes  the  potential  for it to be applied to tasks that are
conceptually  similar and, more important, to tasks that have not
yet been conceived. 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: wlan0.jpeg
Type: image/jpeg
Size: 11750 bytes
Desc: 
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20030518/4ea28ba7/attachment.jpeg 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: lspci.txt
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20030518/4ea28ba7/attachment.txt 