Hi Jonathan, I still have the system, but I have upgraded it to a testing/unstable mix and I'm currently running the 3.2 kernel.
I'm not sure if it would be reasonable to test with 2.6.32 kernel from squeeze on a wheezy system. If it is I can do that, but installing squeeze just to test it seems too much work for me now. Since nobody else seems to care about this issue and I have moved on to kernel versions where this problem does not exist I suggest to close this bug. Thanks for your help, Zsolt On Thu, Feb 9, 2012 at 9:29 AM, Jonathan Nieder <[email protected]> wrote: > Hi Zsolt, > > Zsolt Rizsanyi wrote: > > > Booted into 2.6.32-21, expecting the issue to be gone. To my surprise > > the issue is still present! I don't how this could be. It might be > > that it is caused by some other part of the kernel. > > > > I'm back to the 2.6.35 kernel from experimental. > > > > If you have any idea what to try or check then please ask. Trying many > > kernel version would be too much for me, but I would be willing to try > > a few version or patches. > > Sorry for the long quiet. Do you still have access to this system? > Can you reproduce the bug with current squeeze kernels? (No > particular relevant change I can think of; just would like to know > before hunting for a patch to apply.) > > If you can still reproduce it, please attach full "dmesg" output from > booting and reproducing the problem on an affected kernel and from > booting an unaffected kernel. > > Thanks, > Jonathan >
