On Mon, Jul 14, 2014 at 10:37:07PM +0200, John Hay wrote:
On Mon, Jul 14, 2014 at 01:02:03PM -0700, Adrian Chadd wrote:
Ah, you're not even using it in 11n mode. Ok.
Well, that's 72 mbufs allocated, and up to 200 more being allocated
during transmit. Then there's the handful of pages
I've seen some weird cases in the past where there's just no
interrupts making out after boot. I don't know why.
Chances are that's what you're seeing - the frame is going out but
there's no interrupts.
Check vmstat -ia ; see if ath0 is generating interrupts.
-a
On 17 July 2014 03:34, John
On Thu, Jul 17, 2014 at 12:17:19PM -0700, Adrian Chadd wrote:
I've seen some weird cases in the past where there's just no
interrupts making out after boot. I don't know why.
Chances are that's what you're seeing - the frame is going out but
there's no interrupts.
Check vmstat -ia ; see
okay, I think that needs to be fixed first. I can't debug it otherwise. :)
-a
On 17 July 2014 12:24, John Hay j...@meraka.org.za wrote:
On Thu, Jul 17, 2014 at 12:17:19PM -0700, Adrian Chadd wrote:
I've seen some weird cases in the past where there's just no
interrupts making out after
On Mon, Jul 14, 2014 at 12:06:34PM -0700, Adrian Chadd wrote:
.. why's it need bounce buffers?
I found this:
arm/xscale/ixp425/ixp425_pci.c: /* NB: PCI dma window is 64M so anything above
must be bounced */
John
-a
On 14 July 2014 11:42, John Hay j...@meraka.org.za wrote:
On Mon,
On Mon, Jul 14, 2014 at 09:09:46PM +0200, John Hay wrote:
On Mon, Jul 14, 2014 at 12:06:34PM -0700, Adrian Chadd wrote:
.. why's it need bounce buffers?
I found this:
arm/xscale/ixp425/ixp425_pci.c: /* NB: PCI dma window is 64M so anything
above must be bounced */
I found a sysctl to
On Mon, Jul 14, 2014 at 12:23:47PM -0700, Adrian Chadd wrote:
Ah, you're going to need more than 64 bounce pages. That's just not
enough for all the mbufs the 11n support requires.
It likely didn't show up in previous incarnations of this because
pre-11n support had a much smaller pool of
Right. What's the output of hw.ath ?
-a
On 14 July 2014 12:49, John Hay j...@meraka.org.za wrote:
On Mon, Jul 14, 2014 at 12:23:47PM -0700, Adrian Chadd wrote:
Ah, you're going to need more than 64 bounce pages. That's just not
enough for all the mbufs the 11n support requires.
It likely
On Mon, Jul 14, 2014 at 12:55:19PM -0700, Adrian Chadd wrote:
Right. What's the output of hw.ath ?
tst-11-arm:~ # sysctl hw.ath
hw.ath.bstuck: 4
hw.ath.txbuf_mgmt: 32
hw.ath.txbuf: 200
hw.ath.rxbuf: 40
hw.ath.anical: 100
hw.ath.resetcal: 1200
hw.ath.shortcal: 100
hw.ath.longcal: 30
hw.ath.debug:
On 14 July 2014 13:00, John Hay j...@meraka.org.za wrote:
On Mon, Jul 14, 2014 at 12:55:19PM -0700, Adrian Chadd wrote:
Right. What's the output of hw.ath ?
tst-11-arm:~ # sysctl hw.ath
hw.ath.bstuck: 4
hw.ath.txbuf_mgmt: 32
hw.ath.txbuf: 200
hw.ath.rxbuf: 40
hw.ath.anical: 100
On Wed, Jul 09, 2014 at 06:46:12AM +0200, John Hay wrote:
Hi Guys,
The problem is back / still there. I initially saw the problem during
boot, with the interface configs in rc.conf, but because it is so
mixed with the rest, I took it out and put it in the script, then
after multi-user boot
Hi Guys,
The problem is back / still there. I initially saw the problem during
boot, with the interface configs in rc.conf, but because it is so
mixed with the rest, I took it out and put it in the script, then
after multi-user boot was finished, I did a login and ran the script,
with the output
hi,
That call is returning ENOMEM. I'm not sure why. It allocated an mbuf
fine, but it couldn't allocate the DMA map.
What's the output of vmstat -z ? I wonder if it's failing an allocation.
-a
On 7 July 2014 07:25, John Hay j...@meraka.org.za wrote:
Hi Guys,
I'm further with getting my
On Mon, Jul 07, 2014 at 09:25:34AM -0700, Adrian Chadd wrote:
hi,
That call is returning ENOMEM. I'm not sure why. It allocated an mbuf
fine, but it couldn't allocate the DMA map.
What's the output of vmstat -z ? I wonder if it's failing an allocation.
:~ # vmstat -z
ITEM
On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote:
hi,
That call is returning ENOMEM. I'm not sure why. It allocated an mbuf
fine, but it couldn't allocate the DMA map.
What's the output of vmstat -z ? I wonder if it's failing an allocation.
-a
Lack of bounce buffers is a
On 7 July 2014 10:12, Ian Lepore i...@freebsd.org wrote:
On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote:
hi,
That call is returning ENOMEM. I'm not sure why. It allocated an mbuf
fine, but it couldn't allocate the DMA map.
What's the output of vmstat -z ? I wonder if it's failing an
On Mon, Jul 7, 2014 at 11:31 AM, Adrian Chadd adr...@freebsd.org wrote:
On 7 July 2014 11:28, John Hay j...@meraka.org.za wrote:
On Mon, Jul 07, 2014 at 11:22:46AM -0700, Adrian Chadd wrote:
On 7 July 2014 10:12, Ian Lepore i...@freebsd.org wrote:
On Mon, 2014-07-07 at 09:25 -0700, Adrian
On Mon, Jul 07, 2014 at 11:59:03AM -0700, hiren panchasara wrote:
On Mon, Jul 7, 2014 at 11:31 AM, Adrian Chadd adr...@freebsd.org wrote:
On 7 July 2014 11:28, John Hay j...@meraka.org.za wrote:
On Mon, Jul 07, 2014 at 11:22:46AM -0700, Adrian Chadd wrote:
On 7 July 2014 10:12, Ian Lepore
Sweet!
Can you run the same commands above on the Avila board?
Would you mind filing a PR to ensure we get that option into the
relevant kernel(s) ?
(I'm kinda tempted to suggest we auto-select the scaling factor at
startup depending upon physical RAM .. )
-a
On 7 July 2014 12:32, John Hay
19 matches
Mail list logo
