Bug#384692: This appears to be fixed in 2.6.18

2006-10-25 Thread dann frazier
Version: 2.6.18-1 On Wed, Oct 25, 2006 at 05:15:41PM +0400, Sheplyakov Alexei wrote: > The patch I've mentioned went into 2.6.18 (according to ChangeLog-2.6.18), > so 2.6.18 should work. That said, I can't test 2.6.18 now :( Great, thanks for debugging. I'll marked as fixed in 2.6.18-1. -- dann

Bug#384692: This appears to be fixed in 2.6.18

2006-10-25 Thread Sheplyakov Alexei
Hello, On Wed, 4 Oct 2006 19:09:39 +1000, Andree Leidenfrost wrote: > I have so far been unable to reproduce the error with kernel 2.6.18. > Give that this is 100% reproducible for me on 2.6.17 I assume the > problem is fixed in 2.6.18. The problem was also fixed in 2.6.17.12, the patch can be

Bug#384692: This appears to be fixed in 2.6.18

2006-10-04 Thread Andree Leidenfrost
I have so far been unable to reproduce the error with kernel 2.6.18. Give that this is 100% reproducible for me on 2.6.17 I assume the problem is fixed in 2.6.18. I suggest to close this bug once 2.6.17 is removed from the archive (which may already have happened). Alexei, could you retest with 2.