console freeze after "ifconfig wlan0 scan" with wi(4) pccard device

2011-01-09 Thread Anton Shterenlikht
On amd64 r217010 laptop (HP Compaq 6715s)
I'm trying to use this wi(4) device:

wi0: 
 at port 0x100-0x13f irq 20 function 0 config 1 on pccard0

I do

# ifconfig wlan0 create wlandev wi0
# ifconfig -a
bge0: flags=8843 metric 0 mtu 1500
options=8009b
ether 00:1a:4b:89:4b:4e
inet 192.168.1.102 netmask 0xff00 broadcast 192.168.1.255
media: Ethernet autoselect (100baseTX )
status: active
lo0: flags=8049 metric 0 mtu 16384
options=3
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
nd6 options=21
wi0: flags=8802 metric 0 mtu 2290
ether 00:06:25:10:56:3b
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
status: no carrier
wlan0: flags=8802 metric 0 mtu 1500
ether 00:06:25:10:56:3b
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
status: no carrier
ssid "" channel 1 (2412 MHz 11b)
country US authmode OPEN privacy OFF txpower 0 bmiss 7 scanvalid 60
bintval 0

But after

# ifconfig wlan0 up scan

I get console freeze requiring cold reboot.
No panic, just a LOR:

 wi0:  at port 
0x100-0x13f irq 20 function 0 config 1 on pccard0
 wlan0: Ethernet address: 00:06:25:10:56:3b
 lock order reversal:
 1st 0xff80012be018 wi0_com_lock (wi0_com_lock) @ 
/usr/src/sys/net80211/ieee80211_scan.c:806
 2nd 0xfe0001b8d010 wi0 (network driver) @ /usr/src/sys/dev/wi/if_wi.c:1083
 KDB: stack backtrace:
 db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
 kdb_backtrace() at kdb_backtrace+0x37
 _witness_debugger() at _witness_debugger+0x2e
 witness_checkorder() at witness_checkorder+0x807
 _mtx_lock_flags() at _mtx_lock_flags+0x79
 wi_raw_xmit() at wi_raw_xmit+0x68
 ieee80211_send_probereq() at ieee80211_send_probereq+0x3f7
 scan_curchan() at scan_curchan+0x49
 scan_task() at scan_task+0x2d5
 taskqueue_run_locked() at taskqueue_run_locked+0x93
 taskqueue_thread_loop() at taskqueue_thread_loop+0x3f
 fork_exit() at fork_exit+0x12a
 fork_trampoline() at fork_trampoline+0xe
 --- trap 0, rip = 0, rsp = 0xff80d401ad00, rbp = 0 ---


In case it matters I've

hw.cbb.start_memory="0xf480"

in /boot/loader.conf, according to
http://www.freebsd.org/cgi/query-pr.cgi?pr=115623


Please advise

many thanks
anton

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: console freeze after "ifconfig wlan0 scan" with wi(4) pccard device

2011-01-10 Thread Bernhard Schmidt
On Sunday, January 09, 2011 23:22:28 Anton Shterenlikht wrote:
> On amd64 r217010 laptop (HP Compaq 6715s)
> I'm trying to use this wi(4) device:
> 
> wi0: 
>  at port 0x100-0x13f irq 20 function 0 config 1 on pccard0
> 
> I do
> 
> # ifconfig wlan0 create wlandev wi0
> # ifconfig -a
> bge0: flags=8843 metric 0 mtu 1500
>
> options=8009b E>
> ether 00:1a:4b:89:4b:4e
> inet 192.168.1.102 netmask 0xff00 broadcast 192.168.1.255
> media: Ethernet autoselect (100baseTX )
> status: active
> lo0: flags=8049 metric 0 mtu 16384
> options=3
> inet 127.0.0.1 netmask 0xff00
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
> nd6 options=21
> wi0: flags=8802 metric 0 mtu 2290
> ether 00:06:25:10:56:3b
> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
> status: no carrier
> wlan0: flags=8802 metric 0 mtu 1500
> ether 00:06:25:10:56:3b
> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
> status: no carrier
> ssid "" channel 1 (2412 MHz 11b)
> country US authmode OPEN privacy OFF txpower 0 bmiss 7 scanvalid 60
> bintval 0
> 
> But after
> 
> # ifconfig wlan0 up scan
> 
> I get console freeze requiring cold reboot.
> No panic, just a LOR:
> 
>  wi0:  at port
> 0x100-0x13f irq 20 function 0 config 1 on pccard0 wlan0: Ethernet address:
> 00:06:25:10:56:3b
>  lock order reversal:
>  1st 0xff80012be018 wi0_com_lock (wi0_com_lock) @
> /usr/src/sys/net80211/ieee80211_scan.c:806 2nd 0xfe0001b8d010 wi0
> (network driver) @ /usr/src/sys/dev/wi/if_wi.c:1083 KDB: stack backtrace:
> [..]

This is a known LOR, many wireless do have that. It happens right after a scan 
iteration if there is a network to connect to.

> In case it matters I've
> 
> hw.cbb.start_memory="0xf480"
> 
> in /boot/loader.conf, according to
> http://www.freebsd.org/cgi/query-pr.cgi?pr=115623

Do you by any change have another device you can test the pccard slot with? 

Also, you might want to try 'ifconfig wlan0 ssid 
somethingwhichdoesdefinitelynotexist up; ifconfig wlan0 list scan'
instead of 'ifconfig wlan0 up scan'.

-- 
Bernhard
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: console freeze after "ifconfig wlan0 scan" with wi(4) pccard device

2011-01-12 Thread Anton Shterenlikht
On Mon, Jan 10, 2011 at 09:22:58AM +0100, Bernhard Schmidt wrote:
> On Sunday, January 09, 2011 23:22:28 Anton Shterenlikht wrote:
> > On amd64 r217010 laptop (HP Compaq 6715s)
> > I'm trying to use this wi(4) device:
> > 
> > wi0: 
> >  at port 0x100-0x13f irq 20 function 0 config 1 on pccard0
> > 
> > I do
> > 
> > # ifconfig wlan0 create wlandev wi0
> > # ifconfig -a
> > bge0: flags=8843 metric 0 mtu 1500
> >
> > options=8009b > E>
> > ether 00:1a:4b:89:4b:4e
> > inet 192.168.1.102 netmask 0xff00 broadcast 192.168.1.255
> > media: Ethernet autoselect (100baseTX )
> > status: active
> > lo0: flags=8049 metric 0 mtu 16384
> > options=3
> > inet 127.0.0.1 netmask 0xff00
> > inet6 ::1 prefixlen 128
> > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
> > nd6 options=21
> > wi0: flags=8802 metric 0 mtu 2290
> > ether 00:06:25:10:56:3b
> > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
> > status: no carrier
> > wlan0: flags=8802 metric 0 mtu 1500
> > ether 00:06:25:10:56:3b
> > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
> > status: no carrier
> > ssid "" channel 1 (2412 MHz 11b)
> > country US authmode OPEN privacy OFF txpower 0 bmiss 7 scanvalid 60
> > bintval 0
> > 
> > But after
> > 
> > # ifconfig wlan0 up scan
> > 
> > I get console freeze requiring cold reboot.
> > No panic, just a LOR:
> > 
> >  wi0:  at port
> > 0x100-0x13f irq 20 function 0 config 1 on pccard0 wlan0: Ethernet address:
> > 00:06:25:10:56:3b
> >  lock order reversal:
> >  1st 0xff80012be018 wi0_com_lock (wi0_com_lock) @
> > /usr/src/sys/net80211/ieee80211_scan.c:806 2nd 0xfe0001b8d010 wi0
> > (network driver) @ /usr/src/sys/dev/wi/if_wi.c:1083 KDB: stack backtrace:
> > [..]
> 
> This is a known LOR, many wireless do have that. It happens right after a 
> scan 
> iteration if there is a network to connect to.
> 
> > In case it matters I've
> > 
> > hw.cbb.start_memory="0xf480"
> > 
> > in /boot/loader.conf, according to
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=115623
> 
> Do you by any change have another device you can test the pccard slot with? 

Following some advice I read on the net, resetting
bios to default settings seems to help. So I don't
see this freeze anymore. I haven't investigated further.

I've got 2 more devices, but these aren't much help..

first:

wi0:  at port 0x100-0x13f irq 20 function 0 config 
1 on pccard0
wi0: Sorry, this card is not supported (type 2, firmware ver 704)
device_attach: wi0 attach returned 45

second:

an0:  at port 0x100-0x13f irq 20 
function 0 config 5 on pccard0
: record length mismatch -- expected 194, got 196 for Rid ff10
: record length mismatch -- expected 192, got 200 for Rid ff00
an0: got RSSI <-> dBM map
an0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
an0: Ethernet address: 00:0b:fd:7f:ae:3d
an0: [GIANT-LOCKED]
an0: record length mismatch -- expected 194, got 196 for Rid ff10
an0: record length mismatch -- expected 194, got 196 for Rid ff10
an0: record length mismatch -- expected 194, got 196 for Rid ff10
an0: record length mismatch -- expected 194, got 196 for Rid ff10

I'm struggling to make Aironet 350 work.
The best I can get is:

zzz# dhclient an0
DHCPREQUEST on an0 to 255.255.255.255 port 67
DHCPREQUEST on an0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.103 -- renewal in 43200 seconds.

zzz# ifconfig an0
an0: flags=8847 metric 0 mtu 1500
ether 00:0b:fd:7f:ae:3d
inet 192.168.1.103 netmask 0xff00 broadcast 192.168.1.255
media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps)
status: associated
ssid  1:lagartixa channel 11 (2462 MHz 11b)
stationname BUZI
authmode SHARED privacy ON deftxkey 1 txpower 0 rtsthreshold 0
fragthreshold 0 bmiss 0 ucastrate 0 mcastrate 0 mgmtrate 0 maxretry 0
roaming DEVICE bintval 0

and I can see on the DHCP router (gateway):

DHCP Active IP Table 
DHCP Server IP Address:   192.168.1.1   
Client Host NameIP Address  MAC Address Expires 
zzz 192.168.1.103   00:0b:fd:7f:ae:3d   23:58:38

but still can't connect to the gateway:

PING 192.168.1.1 (192.168.1.1): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
^C
--- 192.168.1.1 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss


> 
> Also, you might want to try 'ifconfig wlan0 ssid 
> somethingwhichdoesdefinitelynotexist up; ifconfig wlan0 list scan'
> instead of 'ifconfig wlan0 up scan'.


# ifconfig wlan0 ssid somethingwhichdoesdefinitely up
# ifconfig wlan0
wlan0: flags=8843 metric 0 mtu 1500
ether 00:06:25:10:56:3b
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
status: no carrier
ssid somethingwhichdoesdefinitely channel 

Re: console freeze after "ifconfig wlan0 scan" with wi(4) pccard device

2011-01-13 Thread Chris Brennan
On Wed, Jan 12, 2011 at 7:56 PM, Anton Shterenlikht wrote:

>  but still can't connect to the gateway:
>
> PING 192.168.1.1 (192.168.1.1): 56 data bytes
> ping: sendto: No route to host
> ping: sendto: No route to host
> ping: sendto: No route to host
> ^C
> --- 192.168.1.1 ping statistics ---
> 3 packets transmitted, 0 packets received, 100.0% packet loss
>

After you get the IP, assign a default gw

route add default gw 192.168.1.1

that should do it

hth/c-
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"