Prev: perf probe: Support DW_OP_call_frame_cfa in debuginfo
Next: [PATCH 0/8] Moorestown changes in arch/x86 for 35 merge window
From: Greg KH on 7 May 2010 13:20 On Fri, May 07, 2010 at 10:10:23AM +0300, roma1390 wrote: > Greg KH wrote: > > On Thu, May 06, 2010 at 08:47:27AM +0300, roma1390 wrote: > >> Hello, > >> > >> after some nfs server start/stop i hit kernel bug on 2.6.26. > There is hope[1] that this bug is fixed[2], and fix is merged[3] > into 2.6.29. But there is missing bugfix for older stable kernels. > > > > 2.6.26 is not supported by the community anymore. > > Sadly, the debian 5.0 (current stable) chose 2.6.26 as distribution > kernel. Of course they do kernel as part of distribution support by > them self. > > > Is this a problem on the latest 2.6.27-stable kernel release? If so, > > which specific patches in Linus's tree do you think resolves this? Is > > it just the 22945e4a1c7454c97f5d8aee1ef526 commit that is needed to be > > added there? > > Currently there isn't any free resources to do 2.6.27-stable > testing. Switching from distribution kernel to custom one adds much > more work for system admin, so this options is the last one none > other will work. > > If there is any demand to test 22945e4a1c7454c97f5d8aee1ef526, there > can be such test done. But this issue was found only once, and on > first hour after nfs server configuration was started. If you can't test it, if I add that commit id to .27, I don't see how that would help you out at all, right? Can you poke the debian developers about this? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |