On 29.8.2010 15.38, Mikael Abrahamsson wrote:Do you see these out-of-memory problems with 2.6.35?
Haven't tried it.There aren't any debug options that need to be enabled. The reason I'm asking is because we had a bunch of similar issues being reported earlier that got fixed and it's been calm for a while. That's why it would be interesting to know if 2.6.35 or 2.6.36-rc2 (if it's not too unstable to test) fixes things.
Has there been substantial work done there that changes things so that if I reproduce it on 2.6.35, someone will look into the issue in earnest? Since I'll most likely have to compile a new kernel, are there any debug options I should enable to give more information to aid fault finding?