I plan to use Ubiquiti Unifi AC LR.
On Sun, Nov 27, 2016 at 4:25 PM, Jan Stary <h...@stare.cz> wrote:
> After an upgrade to the latest i386 snapshots,
> those messages have disappeared. Looking at the source,
> it's because it became a DEBUG only message.
> (Yes, the ral throughput still sucks.)
>
> What kind of wifi are people using
> on the ALIX serving as an AP?
>
> Jan
>
> OpenBSD 6.0-current (GENERIC) #0: Fri Nov 25 10:47:36 MST 2016
> bu...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class)
> 432 MHz
> cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW
> real mem = 133713920 (127MB)
> avail mem = 118501376 (113MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: date 12/10/07, BIOS32 rev. 0 @ 0xfceb2
> pcibios0 at bios0: rev 2.1 @ 0xf0000/0x10000
> pcibios0: pcibios_get_intr_routing - function not supported
> pcibios0: PCI IRQ Routing information unavailable.
> pcibios0: PCI bus #0 is the last bus
> bios0: ROM list: 0xe0000/0xa800
> cpu0 at mainbus0: (uniprocessor)
> mtrr: K6-family MTRR support (2 registers)
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x31
> glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
> vr0 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 10,
> address 00:0d:b9:12:9f:2c
> ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> 0x004063, model 0x0034
> vr1 at pci0 dev 10 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11,
> address 00:0d:b9:12:9f:2d
> ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> 0x004063, model 0x0034
> vr2 at pci0 dev 11 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 12,
> address 00:0d:b9:12:9f:2e
> ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> 0x004063, model 0x0034
> ral0 at pci0 dev 12 function 0 "Ralink RT2560" rev 0x01: irq 9, address
> 00:11:09:0d:d3:36
> ral0: MAC/BBP RT2560 (rev 0x04), RF RT2525
> glxpcib0 at pci0 dev 15 function 0 "AMD CS5536 ISA" rev 0x03: rev 3,
> 32-bit 3579545Hz timer, watchdog, gpio, i2c
> gpio0 at glxpcib0: 32 pins
> iic0 at glxpcib0
> pciide0 at pci0 dev 15 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel
> 0 wired to compatibility, channel 1 wired to compatibility
> wd0 at pciide0 channel 0 drive 0: <ELITE PRO CF CARD 8GB>
> wd0: 1-sector PIO, LBA, 7279MB, 14909328 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> pciide0: channel 1 ignored (disabled)
> ohci0 at pci0 dev 15 function 4 "AMD CS5536 USB" rev 0x02: irq 15, version
> 1.0, legacy support
> ehci0 at pci0 dev 15 function 5 "AMD CS5536 USB" rev 0x02: irq 15
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 configuration 1 interface 0 "AMD EHCI root hub" rev
> 2.00/1.00 addr 1
> isa0 at glxpcib0
> isadma0 at isa0
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com0: console
> pcppi0 at isa0 port 0x61
> spkr0 at pcppi0
> npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
> usb1 at ohci0: USB revision 1.0
> uhub1 at usb1 configuration 1 interface 0 "AMD OHCI root hub" rev
> 1.00/1.00 addr 1
> vmm at mainbus0 not configured
> nvram: invalid checksum
> vscsi0 at root
> scsibus1 at vscsi0: 256 targets
> softraid0 at root
> scsibus2 at softraid0: 256 targets
> root on wd0a (bf940e6c7aaf2c50.a) swap on wd0b dump on wd0b
> clock: unknown CMOS layout
> On Sep 20 10:46:54, h...@stare.cz wrote:
>
> > This is ALIX 2C1, just upgraded to current/i386 (dmesg below).
> > It serves as a wifi AP using ral(4). The console gets spammed with
> >
> > ral0: sending data frame failed 0x02faaafa
> >
> > This used to work fine since 5.9/i386.
> >
> > $ cat /hostname.ral0
> > inet 192.168.33.1 255.255.255.0 NONE \
> > media autoselect mediaopt hostap nwid stare.cz chan 11 \
> > wpakey XXX
> >
> > $ netstat -I ral0
> > Name Mtu Network Address Ipkts Ierrs Opkts
> Oerrs Colls
> > ral0 1500 <Link> 00:11:09:0d:d3:36 310 327 326
> 120 0
> > ral0 1500 192.168.33/ 192.168.33.1 310 327 326
> 120 0
> >
> > Typical wifi clients of this AP are the phones
> > and tablets in the family; they all seem to connect fine.
> >
> > How can I help debug this?
> >
> > Jan
> >
> >
> > OpenBSD 6.0-current (GENERIC) #2064: Mon Sep 19 20:35:29 MDT 2016
> > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> > cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD"
> 586-class) 432 MHz
> > cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW
> > real mem = 133713920 (127MB)
> > avail mem = 118611968 (113MB)
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: date 12/10/07, BIOS32 rev. 0 @ 0xfceb2
> > pcibios0 at bios0: rev 2.1 @ 0xf0000/0x10000
> > pcibios0: pcibios_get_intr_routing - function not supported
> > pcibios0: PCI IRQ Routing information unavailable.
> > pcibios0: PCI bus #0 is the last bus
> > bios0: ROM list: 0xe0000/0xa800
> > cpu0 at mainbus0: (uniprocessor)
> > mtrr: K6-family MTRR support (2 registers)
> > pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> > pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x31
> > glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
> > vr0 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 10,
> address 00:0d:b9:12:9f:2c
> > ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> 0x004063, model 0x0034
> > vr1 at pci0 dev 10 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11,
> address 00:0d:b9:12:9f:2d
> > ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> 0x004063, model 0x0034
> > vr2 at pci0 dev 11 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 12,
> address 00:0d:b9:12:9f:2e
> > ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> 0x004063, model 0x0034
> > ral0 at pci0 dev 12 function 0 "Ralink RT2560" rev 0x01: irq 9, address
> 00:11:09:0d:d3:36
> > ral0: MAC/BBP RT2560 (rev 0x04), RF RT2525
> > glxpcib0 at pci0 dev 15 function 0 "AMD CS5536 ISA" rev 0x03: rev 3,
> 32-bit 3579545Hz timer, watchdog, gpio, i2c
> > gpio0 at glxpcib0: 32 pins
> > iic0 at glxpcib0
> > pciide0 at pci0 dev 15 function 2 "AMD CS5536 IDE" rev 0x01: DMA,
> channel 0 wired to compatibility, channel 1 wired to compatibility
> > wd0 at pciide0 channel 0 drive 0: <ELITE PRO CF CARD 8GB>
> > wd0: 1-sector PIO, LBA, 7279MB, 14909328 sectors
> > wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> > pciide0: channel 1 ignored (disabled)
> > ohci0 at pci0 dev 15 function 4 "AMD CS5536 USB" rev 0x02: irq 15,
> version 1.0, legacy support
> > ehci0 at pci0 dev 15 function 5 "AMD CS5536 USB" rev 0x02: irq 15
> > usb0 at ehci0: USB revision 2.0
> > uhub0 at usb0 configuration 1 interface 0 "AMD EHCI root hub" rev
> 2.00/1.00 addr 1
> > isa0 at glxpcib0
> > isadma0 at isa0
> > com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> > com0: console
> > pcppi0 at isa0 port 0x61
> > spkr0 at pcppi0
> > npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
> > usb1 at ohci0: USB revision 1.0
> > uhub1 at usb1 configuration 1 interface 0 "AMD OHCI root hub" rev
> 1.00/1.00 addr 1
> > nvram: invalid checksum
> > vscsi0 at root
> > scsibus1 at vscsi0: 256 targets
> > softraid0 at root
> > scsibus2 at softraid0: 256 targets
> > root on wd0a (bf940e6c7aaf2c50.a) swap on wd0b dump on wd0b
> > clock: unknown CMOS layout
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02f9aafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x060caafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x060caafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x060caafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x060caafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaa1a
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> > ral0: sending data frame failed 0x001003fa
> > ral0: sending data frame failed 0x02faaafa
> >
>
> On Sep 20 11:53:41, s...@stsp.name wrote:
> > On Tue, Sep 20, 2016 at 10:46:54AM +0200, Jan Stary wrote:
> > > This is ALIX 2C1, just upgraded to current/i386 (dmesg below).
> > > It serves as a wifi AP using ral(4). The console gets spammed with
> > >
> > > ral0: sending data frame failed 0x02faaafa
> > >
> > > This used to work fine since 5.9/i386.
> >
> > This is the only known fallout from ieee80211_proto.c r1.68 and seems to
> > affect ral 2560 chips only. Apparently this driver has always had a bug
> > with RTS/CTS and the wireless stack is now triggering it.
> >
> > It's on my TODO list. In the mean time you can back out r1.68 as a
> > workaround, for example like this:
> >
> > Index: ieee80211_proto.c
> > ===================================================================
> > RCS file: /cvs/src/sys/net80211/ieee80211_proto.c,v
> > retrieving revision 1.68
> > diff -u -p -r1.68 ieee80211_proto.c
> > --- ieee80211_proto.c 20 Jul 2016 15:40:27 -0000 1.68
> > +++ ieee80211_proto.c 20 Sep 2016 09:45:32 -0000
> > @@ -88,7 +88,7 @@ ieee80211_proto_attach(struct ifnet *ifp
> >
> > ifp->if_hdrlen = sizeof(struct ieee80211_frame);
> >
> > - ic->ic_rtsthreshold = IEEE80211_RTS_DEFAULT;
> > + ic->ic_rtsthreshold = IEEE80211_RTS_MAX;
> > ic->ic_fragthreshold = 2346; /* XXX not used yet */
> > ic->ic_fixed_rate = -1; /* no fixed rate */
> > ic->ic_fixed_mcs = -1; /* no fixed mcs */
> >
> >
> >
> > > How can I help debug this?
> >
> > sebastia@ reported this to me already, and he kindly spent the time
> > involved in tracking down the commit that introduced this problem.
> > You could have done that, too, but now sebastia@ already did that work.
> >
> > You could still help by becoming a wireless hacker and fix the driver
> yourself.
> >
>
> On Oct 06 01:28:32, s...@stsp.name wrote:
> > On Tue, Sep 20, 2016 at 11:53:41AM +0200, Stefan Sperling wrote:
> > > On Tue, Sep 20, 2016 at 10:46:54AM +0200, Jan Stary wrote:
> > > > This is ALIX 2C1, just upgraded to current/i386 (dmesg below).
> > > > It serves as a wifi AP using ral(4). The console gets spammed with
> > > >
> > > > ral0: sending data frame failed 0x02faaafa
> > > >
> > > > This used to work fine since 5.9/i386.
> > >
> > > This is the only known fallout from ieee80211_proto.c r1.68 and seems
> to
> > > affect ral 2560 chips only. Apparently this driver has always had a bug
> > > with RTS/CTS and the wireless stack is now triggering it.
> >
> > This seems to be a transmission failure mode which Linux rt2x00 simply
> > ignores. We don't have a name for it, and neither has linux, and
> > I don't have docs, so I don't know what the reason for the failure
> > mode could be.
> >
> > It's curious that this started showing up when we enabled RTS/CTS
> > for large frames, but RTS/CTS seems to be working fine and was
> > already being enabled in other cases.
> > For now, I'd just disable this message and only show it if the
> > driver is compiled in debug mode.
> >
> > The only problem with this driver/device I've observed is that transmit
> > rates are fairly slow. It settles at 1Mbit/s and never recovers, which
> > means the ral(4) device is retrying frames excessively.
> > But I don't believe that's a new problem. I remember using ral(4) as my
> > AP years ago and speed always sucked even back then. There might be other
> > bugs to fix in here but this message by itself won't help us find them.
> >
> > Index: rt2560.c
> > ===================================================================
> > RCS file: /cvs/src/sys/dev/ic/rt2560.c,v
> > retrieving revision 1.80
> > diff -u -p -r1.80 rt2560.c
> > --- rt2560.c 13 Apr 2016 10:49:26 -0000 1.80
> > +++ rt2560.c 5 Oct 2016 22:53:37 -0000
> > @@ -959,9 +959,10 @@ rt2560_tx_intr(struct rt2560_softc *sc)
> > case RT2560_TX_FAIL_INVALID:
> > case RT2560_TX_FAIL_OTHER:
> > default:
> > - printf("%s: sending data frame failed 0x%08x\n",
> > - sc->sc_dev.dv_xname, letoh32(desc->flags));
> > + DPRINTF(("%s: sending data frame failed 0x%08x\n",
> > + sc->sc_dev.dv_xname, letoh32(desc->flags)));
> > ifp->if_oerrors++;
> > + break;
> > }
> >
> > /* descriptor is no longer valid */
> > @@ -1031,8 +1032,9 @@ rt2560_prio_intr(struct rt2560_softc *sc
> > case RT2560_TX_FAIL_INVALID:
> > case RT2560_TX_FAIL_OTHER:
> > default:
> > - printf("%s: sending mgt frame failed 0x%08x\n",
> > - sc->sc_dev.dv_xname, letoh32(desc->flags));
> > + DPRINTF(("%s: sending mgt frame failed 0x%08x\n",
> > + sc->sc_dev.dv_xname, letoh32(desc->flags)));
> > + break;
> > }
> >
> > /* descriptor is no longer valid */
> > @@ -1945,6 +1947,8 @@ rt2560_start(struct ifnet *ifp)
> > break;
> >
> > } else {
> > + /* Because RTS/CTS requires an extra frame we need
> > + * space for 2 frames on the regular Tx queue. */
> > if (sc->txq.queued >= RT2560_TX_RING_COUNT - 1) {
> > ifq_set_oactive(&ifp->if_snd);
> > sc->sc_flags |= RT2560_DATA_OACTIVE;
