Fine, it seems that upgrade kernel is the only effective solution. > On 18 Oct 2017, at 10:00 PM, Stephen John Smoogen <smooge@xxxxxxxxx> wrote: > > On 18 October 2017 at 04:50, wuzhouhui <wuzhouhui14@xxxxxxxxxxxxxxxx> wrote: >> I googled this issue and found so many people have encountered, but most of >> them just said "the newer kernel doesn't have this problem, so upgrade >> kernel". We can't upgrade kernel easily, so we need to *really* solve this >> problem. >> >> > > If you can't update the kernel then how can anyone fix the problem? > The kernel needs to be changed out in some way. [Yes there are ways to > binary patch a running kernel but it is a) frought with danger b) > experts only area. People who do that do not offer their services for > free for a reason.] > > -- > Stephen J Smoogen. > _______________________________________________ > CentOS mailing list > CentOS@xxxxxxxxxx > https://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx https://lists.centos.org/mailman/listinfo/centos