Hello Andrea, Daniel,
can you see a kernel stacktrace anywhere? Are you in a GUI when the system
freezes, i.e. running some desktop? In that case you probably won't be
able to see the stacktrace, but you could try to CTRL-ALT-Fx to some of
your consoles and maybe be lucky. I have not investigated this any further
but you can find a lot of ressources on the internet that try to explain
how to get a kerneldump when your system freezes. Maybe one could proceed
from there with the help of kernel people.
One guess what causes this bug is, that the system runs into memory
pressure - i.e. something similar like [1] - that is the system runs into
a situation where it's lacking memory, it wants to swap stuff out, in
order to swap out it needs to allocate memory, or swap something back in -
like f.ex. noflushd -> deadlock.
I feel that the noflushd package has its value. Getting further with this
bug might prevent noflushd being dropped from the next release.
?
*t
[1] http://lists.linbit.com/pipermail/drbd-user/2011-May/016009.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
