From owner-freebsd-bugs@FreeBSD.ORG Tue Feb 26 21:50:02 2008 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB2BA106566B for ; Tue, 26 Feb 2008 21:50:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D80E413C442 for ; Tue, 26 Feb 2008 21:50:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m1QLo2ev039915 for ; Tue, 26 Feb 2008 21:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m1QLo2cl039914; Tue, 26 Feb 2008 21:50:02 GMT (envelope-from gnats) Date: Tue, 26 Feb 2008 21:50:02 GMT Message-Id: <200802262150.m1QLo2cl039914@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Yuri Cc: Subject: Re: kern/120636: Ndis driver causes system to hang while bringing AirLink101-AWLC3026 card up X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Yuri List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2008 21:50:03 -0000 The following reply was made to PR kern/120636; it has been noted by GNATS. From: Yuri To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/120636: Ndis driver causes system to hang while bringing AirLink101-AWLC3026 card up Date: Tue, 26 Feb 2008 13:45:19 -0800 There are numerous problems that I observe with this card. First some information. On the client host: when the driver loads in the presence of this card dmesg is: ndis0: mem 0x88000000-0x8800ffff,0x88010000-0x8801ffff irq 9 at device 0.0 on cardbus0 ndis0: [ITHREAD] ndis0: NDIS API version: 5.1 ndis0: using obsoleted if_watchdog interface ndis0: Ethernet address: 00:40:f4:e3:6b:4b On the AP side: FreeBSD access point is setup with the command: ifconfig ral0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap wepmode on weptxkey 3 wepkey 3:0x3456789012 mode 11g mediaopt hostap On the AP side: 'ifconfig -v' prints: ral0: flags=8843 metric 0 mtu 1500 ether 00:18:f8:2e:40:25 inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated ssid freebsdap channel 3 (2422 Mhz 11g) bssid 00:18:f8:2e:40:25 authmode OPEN privacy ON deftxkey 3 wepkey 1:104-bit wepkey 3:40-bit powersavemode OFF powersavesleep 100 txpower 50 txpowmax 50.0 rtsthreshold 2346 fragthreshold 2346 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11a 7 roam:rate11a 12 roam:rssi11b 7 roam:rate11b 1 roam:rssi11g 7 roam:rate11g 5 -pureg protmode CTS -ht -htcompat -ampdu ampdulimit 8k ampdudensity - -amsdu -shortgi htprotmode RTSCTS -puren -wme -burst -ff -dturbo -hidessid apbridge dtimperiod 1 doth inact bintval 100 On the client host: I set it up the card to connect to "freebsdap" network: ifconfig ndis0 ssid freebsdap wepmode on weptxkey 3 wepkey 3:0x3456789012 authmode open ifconfig ndis0 mode 11g ifconfig ndis0 inet 192.168.0.2 netmask 255.255.255.0 ifconfig ndis0 up Card's transmit light blinks few times and stops. Based on lights it looks like card is connected. On the client host: 'ifconfig -v' prints: ndis0: flags=8843 metric 0 mtu 1500 ether 00:40:f4:e3:6b:4b inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g (DS/1Mbps) status: associated ssid freebsdap channel 3 (2422 Mhz 11g) bssid 00:18:f8:2e:40:25 authmode OPEN privacy OFF deftxkey 3 wepkey 3:40-bit powersavemode OFF powersavesleep 100 txpowmax 100 rtsthreshold 2346 fragthreshold 2346 bmiss 7 mcastrate 1 scanvalid 60 -bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11a 14 roam:rate11a 12 roam:rssi11b 14 roam:rate11b 1 roam:rssi11g 14 roam:rate11g 5 -pureg protmode CTS -wme -burst -ff -dturbo roaming AUTO bintval 100 PROBLEM#1: On the client host: when I try to ping AP (ping 192.168.0.1) I get 100% packet loss. Transmit light doesn't blink in sync with ping. On the client host: I reset the card: 'ifconfig ndis0 down; ifconfig ndis0 sid ""'. On the client side: 'ifconfig -v' prints: ndis0: flags=8802 metric 0 mtu 1500 ether 00:40:f4:e3:6b:4b inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g (DS/1Mbps) status: no carrier ssid "" channel 3 (2422 Mhz 11g) bssid 00:00:00:00:00:00 authmode OPEN privacy OFF deftxkey 3 wepkey 3:40-bit powersavemode OFF powersavesleep 100 txpowmax 100 rtsthreshold 2346 fragthreshold 2346 bmiss 7 mcastrate 1 scanvalid 60 -bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11a 14 roam:rate11a 12 roam:rssi11b 14 roam:rate11b 1 roam:rssi11g 14 roam:rate11g 5 -pureg protmode CTS -wme -burst -ff -dturbo roaming AUTO bintval 100 PROBLEM#2: On the client side: 'ifconfig ndis0 up scan' hangs. First transmit light flashes few times but then command never returns and never prints anything. PROBLEM#3 (similar to PROBLEM#1): On the client host side: when I pull the card out and put it back in and repeat the setup step (above) ping causes transmit light to flash in sync with ping few times and then power light begins to flash for a while. And then power light stops flashing. Also on the client host side every time when I ping AP dmesg gets: ndis0: link state changed to DOWN ndis0: link state changed to UP This seems very strange: why link state changes just because of ping? PROBLEM#4: I was also able to get kernel crash earlier. But I can;t reproduce it now. I will append this PR when I am able to reproduce. PROBLEM#5: (from subject) I can't reproduce it now, but I will keep trying. Remko: please let me know if I can do something more to debug these problems.