On Sat, 2013-04-20 at 23:32 +0200, Sandro Tosi wrote: > Hello Ben, > > On Thu, Apr 18, 2013 at 7:09 AM, Ben Hutchings <ben@decadent.org.uk> wrote: > > On Tue, 2013-04-02 at 10:59 +0200, Sandro Tosi wrote: > >> Hello Ben, > >> i'm a collegue of Daniele and I'd like to add some more information on > >> this issue, which we're still facing with 3.2.35-2~bpo60+1 . > > [...] > >> Please let us know if you need more information, if we can run some > >> diagnostics or try some solutions, it's really important for us to get > >> that fixed. > > > > Sorry, I can't afford to spend any more time on this bug. > > Thanks for your honest reply. > > We reached you also because you're the current maintainer of upstream > 3.2 branch and because we didn't want Wheezy to release with this bug. > We're testing a custom-built 3.7.10 kernel and the slab memory leak > seems to be gone (but we're facing with system freezes). > > Can you please propose what would be the best way for us (and for > Debian) to have this problem fixed? If you want to just , you have the option of using the 3.8 kernel from experimental and then, once wheezy is out, from testing or wheezy-backports. But if you want to help get this fixed in the standard packages, which would then presumably help some other users, the thing to do would be what Jonathan says - find a way to replicate the problem on a test system, and then bisect to find out when it was fixed. You said that it takes 7-10 days, but it seems that this is the time it takes to become a serious problem. The leak appears to grow fast enough that it should be possible to detect it much earlier if you monitor slabinfo. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club.
Attachment:
signature.asc
Description: This is a digitally signed message part