>
> I recently bought a Microtek E6 scanner to use with SANE (Scanner Access
> Made Easy, http://www.mostang.com/sane). The scanner came with the
> Adaptec AVA-1502 AE scsi card, which works with aha152x module (from
> conf.modules, options aha152x aha152x=0x140,11,7,0). I'm running RedHat
> 5.0, kernel 2.0.33 pretty much with the default RedHat settings. The
> memory leak occurs whether scsi is compiled into the kernel or is used
> as a loadable module, and occurs with SANE 0.70 and 0.71, the latest two
> versions. Anyhow, after about 25 scans I run out of 128 MB of memory
> and most of my 128 MB of swap. I applied the unofficial memleak-deluxe
> patch to the 2.0.33 kernel. The memleak patch writes a file called
> /proc/memleak which can be analyzed by a few enclosed scripts.
>
> From the FAQ, which explains the output below:
>
> the first number the 'allocation count', the number of memory objects
> allocated in a certain FILE:LINE. If some allocation point shows a
> constantly increasing allocation count, it's probably a memory leak.
>
> The FAQ goes on to say:
>
> NOTE: the VM subsystems usually have very fluctuating allocation counts,
> think twice before calling them a memory leak.
The following may help you get closer. Run Bonnie with a size arg
larger than your physical memory to free up as much buffer memory as
possible, then run dofind immediately after. One thing I do is to
use dotimestamp to create a nice sorted list, edit out the obviously OK
stuff and feed this list to a modified dofind. If you know how many
seconds since boot that you started losing memory, you can limit your
search accordingly.
-Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu