NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

kern/45531: otus(4) unstable

>Number:         45531
>Category:       kern
>Synopsis:       otus(4) unstable
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Oct 28 03:05:04 +0000 2011
>Originator:     Thomas Klausner
>Release:        NetBSD 5.99.56

Architecture: x86_64
Machine: amd64
When using otus(4) on NetBSD-current with the following hardware:
otus0 at uhub7 port 5otus0: ATHER USB2.0 WLAN, rev 2.00/1.06, addr 4
otus0: MAC/BBP AR9170, RF AR9101, MIMO 1T2R, address xxxxxxxxxxxxxxxxx
otus0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
otus0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 
36Mbps 48Mbps 54Mbps

and wpa_supplicant on a wpa2 network, setting up the network connection works 
but after a short time using rtorrent with a few torrents, the network 
is lost. (It lives longer than with ral(4) though.)
When I then ping, I see:
ping: sendto: No buffer space available

Same load & setup works fine with a wired network card, e.g.
re0 at pci7 dev 0 function 0: RealTek 8168/8111 PCIe Gigabit Ethernet (rev. 
re0: interrupting at ioapic0 pin 17
re0: Ethernet address xxxxxxxxxxxxxxxxx
re0: using 256 tx descriptors
rgephy0 at re0 phy 7: RTL8169S/8110S/8211 1000BASE-T media interface, rev. 2

Additionally, when in this state, I did:
# ifconfig otus0 down
# ifconfig otus0 up
rather quickly, and got a kernel panic (I was in X so I didn't see

Also, when unplugging otus0 immediately after booting (when the login
prompt is visible) I got:
otus0: could not send command 0x1 (error=IOERROR)
ehci_idone: ex=0xffff80001634d200 is done!
otus0: detached
otus0: at uhub7 port 5 (addr 4) disconnected

configure otus(4) with a WPA2 network, produce load & wait a few minutes to
perhaps a few hours
not provided


Home | Main Index | Thread Index | Old Index