Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
"Adrian Chadd" writes:
> Look in ath/makefile .. At the bottom. There's clang warning overrides
> there. Uncomment them!
Thanks, that did the trick.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wirele
Adrian Chadd writes:
> I've just updated the AR9300 HAL to the March 13 snapshot from QCA.
>
> This includes calibration and TX power calibration changes that may
> improve stability.
>
> As always, it's possible I broke something!
>
> I'd appreciate it if people would test this in STA and AP mod
64 bit kernel? >4 gig RAM?
Adrian
On 1 April 2013 08:07, Raphael Kubo da Costa wrote:
> Adrian Chadd writes:
>
>> I've just updated the AR9300 HAL to the March 13 snapshot from QCA.
>>
>> This includes calibration and TX power calibration changes that may
>> improve stability.
>>
>> As alway
Adrian Chadd writes:
> 64 bit kernel? >4 gig RAM?
Yes, amd64 with 8GB of RAM.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freeb
Please reboot with 4GB of RAM configured.
See if that fixes it.
Adrian
On 1 April 2013 08:13, Raphael Kubo da Costa wrote:
> Adrian Chadd writes:
>
>> 64 bit kernel? >4 gig RAM?
>
> Yes, amd64 with 8GB of RAM.
>
> ___
> freebsd-wireless@freebsd.or
Adrian Chadd writes:
> Please reboot with 4GB of RAM configured.
>
> See if that fixes it.
Indeed, booting with hw.physmem="4G" makes the connection much more
reliable -- I do see some of those warnings in the beginning, but they
go away after the connection is established.
My gut feeling is th
On 1 April 2013 08:44, Raphael Kubo da Costa wrote:
> Adrian Chadd writes:
>
>> Please reboot with 4GB of RAM configured.
>>
>> See if that fixes it.
>
> Indeed, booting with hw.physmem="4G" makes the connection much more
> reliable -- I do see some of those warnings in the beginning, but they
>
On 31 March 2013 15:24, Adrian Chadd wrote:
> The problem isn't contigmalloc, it's making sure that it gets bounced via
> the local 32 bits of address space right.
>
> I'll talk with other developers and see what the deal is with 64 bit address
> space for 32 bit nics.
Please do an svn update in
I just tested it, the network problem's the same.
On 4/1/2013 3:22 PM, Adrian Chadd wrote:
On 31 March 2013 15:24, Adrian Chadd wrote:
The problem isn't contigmalloc, it's making sure that it gets bounced via
the local 32 bits of address space right.
I'll talk with other developers and see wh
update again again; I just did some TX related changes.
adrian
On 1 April 2013 14:04, Joshua Isom wrote:
> I just tested it, the network problem's the same.
>
>
> On 4/1/2013 3:22 PM, Adrian Chadd wrote:
>>
>> On 31 March 2013 15:24, Adrian Chadd wrote:
>>>
>>> The problem isn't contigmalloc
Adrian Chadd writes:
> On 1 April 2013 08:44, Raphael Kubo da Costa wrote:
>> My gut feeling is that the average connection speed is still below the
>> one I get when I use my WLAN->Ethernet adapter, but I haven't done any
>> precise measurements to back that up.
>
> It's still a work in progres
Adrian Chadd writes:
> update again again; I just did some TX related changes.
No changes as of r248988.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd
I was the same. I got these two messages, but I'm only assuming it's
related because the val makes me think of the pci id. These were while
using 16GB, and trying an ifconfig scan.
Apr 1 16:32:51 jri kernel: Memory modified after free
0xfe003ce3a000(4096) val=168c000c @ 0xfe003ce3a0
I'm still trying to chase down the root cause of these. I doubt it's
specifically bceause of your particular issue.
Adrian
On 1 April 2013 14:41, Joshua Isom wrote:
> I was the same. I got these two messages, but I'm only assuming it's
> related because the val makes me think of the pci id.
Hello,
I have a question about 802.11n performance for AR9280 ( my card is Ubiquiti
SR71E ) in hostap mode. To measure performance, I'm looking at the download
speeds from my file server (Samba) through a FreeBSD AP to a laptop with
Centrino 6300 (agn 3x3:3).
I see 3-4 MBytes/s on the 2.4 GHz b
Hi,
9.x doesn't implement 11n aggregation transmission. It only supports
11n MCS rate transmission (with no aggregation) and 11n RX with MCS
and aggregation.
If you update to -HEAD you should see the performance increase.
Adrian
On 1 April 2013 15:10, Gleb Romanov wrote:
> Hello,
>
> I have
Thanks!
Do you recommend to update everything or only ATH module will be enough?
IE get all the sources and follow
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
Or
Download the ATH sources and "make all install" ?
Gleb
> -Original Message-
> From: adrian.ch.
On 1 April 2013 15:38, Gleb Romanov wrote:
> Thanks!
>
> Do you recommend to update everything or only ATH module will be enough?
I suggest that people who wish to try the ath 11n support update and
track -HEAD.
Make sure you add this to your kernel config as well:
options ATH_ENABLE_11N
option
... and that particular value means that some TX descriptor was
written into free'd memory.
Sigh. As I said, I'll chase this down later, but I don't think it's
the root cause of your bug.
I still have a lot more review of the TX path and descriptor handling
but it may take some time.
Thanks,
a
Hi Joshua,
Would you please reboot back into full RAM, let it fail for a bit,
then record dmesg:
dmesg > ~/dmesg.txt
and sysctl:
sysctl dev.ath.0 > ~/sysctl.txt
then reboot back to normal, and email me those two textfiles?
Thanks,
Adrian
___
freeb
.. and please supply the output of 'sysctl hw.busdma' too when it's failing:
sysctl hw.busdma > ~/sysctl-busdma.txt
and include that too.
Thanks,
adrian
On 1 April 2013 20:24, Adrian Chadd wrote:
> Hi Joshua,
>
> Would you please reboot back into full RAM, let it fail for a bit,
> then recor
.. and there's been some more work in -HEAD, so please svn update first!
Thanks,
adrian
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr
23 matches
Mail list logo
