> Can you attach your X and kernel logs, and track the contents of > /sys/kernel/debug/dri/0/gem_objects (you can mount debugfs with 'mount > -t debugfs none /sys/kernel/debug)?
Sorry, I cannot: ever since 2:2.11.0-1, the problem either went away or is at
least a LOT less severe. I now have 41 days old X process, and the
unreclaimable kernel memory is 244584 kB, where it previously rose to a
gigabyte in less than 14 days.
The file /sys/kernel/debug/dri/0/gem_objects is 0 bytes long, how do I "track
its contents"?
> Does this also happen with debian's 2.6.32 kernel?
It happens with everything Debian (including experimental) has had since
2.6.31. Only the .35 kernels I have not tested (because the problem seems to
have gone away before they came available).
Cheers,
Juha
--
-----------------------------------------------
| Juha Jäykkä, [email protected] |
| http://www.maths.leeds.ac.uk/~juhaj |
-----------------------------------------------
signature.asc
Description: This is a digitally signed message part.
