From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751540AbdJASrc (ORCPT ); Sun, 1 Oct 2017 14:47:32 -0400 Received: from mail-lf0-f65.google.com ([209.85.215.65]:57141 "EHLO mail-lf0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750929AbdJASrb (ORCPT ); Sun, 1 Oct 2017 14:47:31 -0400 X-Google-Smtp-Source: AOwi7QB/EYobezo2gF006PZ5KNMU0xEjPmfZegqZbmelhcodLvUN9HVOP3sc0bKAVsdz3+zvzw/UrirC6+jX10rPua0= MIME-Version: 1.0 In-Reply-To: <1506877383.5529.1.camel@gmx.de> References: <159555.1506688878@turing-police.cc.vt.edu> <1506690885.1771.6.camel@icloud.com> <20170929215007.kpea2kan6hg7jzcw@thunk.org> <20170930052530.rf7bcwe3o327sobe@thunk.org> <1506876289.2536.2.camel@icloud.com> <649f4bab-608d-9422-f2c3-401038c036c3@infradead.org> <1506877383.5529.1.camel@gmx.de> From: Pintu Kumar Date: Mon, 2 Oct 2017 00:17:29 +0530 Message-ID: Subject: Re: How to verify linux-next To: Mike Galbraith Cc: Randy Dunlap , Damian Tometzki , "Theodore Ts'o" , Valdis Kletnieks , linux-kernel@vger.kernel.org, kernelnewbies@kernelnewbies.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Oct 1, 2017 at 10:33 PM, Mike Galbraith wrote: > On Sun, 2017-10-01 at 09:48 -0700, Randy Dunlap wrote: >> On 10/01/17 09:44, Damian Tometzki wrote: >> >> > i resolved the issue with: >> > sudo /etc/init.d/apparmor stop >> >> or boot with: apparmor=0 > > or systemctl mask apparmor Ok, thanks everyone for your quick help. Stopping apparmor really helped to restore the connection. Mr. Tso, thanks for your help too for QEMU. After finishing my patch next I will looking into QEMU issues as per your suggestions. From mboxrd@z Thu Jan 1 00:00:00 1970 From: pintu.ping@gmail.com (Pintu Kumar) Date: Mon, 2 Oct 2017 00:17:29 +0530 Subject: How to verify linux-next In-Reply-To: <1506877383.5529.1.camel@gmx.de> References: <159555.1506688878@turing-police.cc.vt.edu> <1506690885.1771.6.camel@icloud.com> <20170929215007.kpea2kan6hg7jzcw@thunk.org> <20170930052530.rf7bcwe3o327sobe@thunk.org> <1506876289.2536.2.camel@icloud.com> <649f4bab-608d-9422-f2c3-401038c036c3@infradead.org> <1506877383.5529.1.camel@gmx.de> Message-ID: To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On Sun, Oct 1, 2017 at 10:33 PM, Mike Galbraith wrote: > On Sun, 2017-10-01 at 09:48 -0700, Randy Dunlap wrote: >> On 10/01/17 09:44, Damian Tometzki wrote: >> >> > i resolved the issue with: >> > sudo /etc/init.d/apparmor stop >> >> or boot with: apparmor=0 > > or systemctl mask apparmor Ok, thanks everyone for your quick help. Stopping apparmor really helped to restore the connection. Mr. Tso, thanks for your help too for QEMU. After finishing my patch next I will looking into QEMU issues as per your suggestions.