Re: [Bug #14141] order 2 page allocation failures in iwlagn

[Frans Pop <elendil@planet.nl>]

[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]

On Thursday 15 October 2009, reinette chatre wrote:
> > The log file timestamps don't tell much as the logging gets delayed,
> > so they all end up at the same time. Maybe I should enable the kernel
> > timestamps so we can see how far apart these failures are.
>
> If you can get accurate timing it will be very useful. I am interested
> to see how quickly it goes from "48 free buffers" to "0 free buffers".

Attached the dmesg for three consecutive test runs (i.e. without 
rebooting). Not that the 2nd one includes only "0 free buffers" messages, 
even though the behavior (point where desktop freezes and music stops) 
looked similar.

Not sure if you can tell all that much from the data.

N.B. You may want to clean this up in iwlwifi code:
iwl-dev.h:#include "iwl-fh.h"
iwl-dev.h:#define RX_LOW_WATERMARK 8
iwl-fh.h:#define RX_LOW_WATERMARK 8

I.e: RX_LOW_WATERMARK is defined in iwl-dev.h even though that includes 
iwl-fh.h where it's also defined. The same may be true for other defines.

I think this gave me an incorrect result the first time I increased the 
limit as I only changed one of the two files (iwl-dev.h IIRC).

Cheers,
FJP


[-- Attachment #2: dmesg.tgz --]
[-- Type: application/x-tgz, Size: 44980 bytes --]