[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOuPNLjZhnK8zxLM-4Zcq3pjZCPKxDFg1es3d7ocv9EadzAauA@mail.gmail.com>
Date: Mon, 2 Oct 2017 00:17:29 +0530
From: Pintu Kumar <pintu.ping@...il.com>
To: Mike Galbraith <efault@....de>
Cc: Randy Dunlap <rdunlap@...radead.org>,
Damian Tometzki <damian.tometzki@...oud.com>,
"Theodore Ts'o" <tytso@....edu>,
Valdis Kletnieks <valdis.kletnieks@...edu>,
linux-kernel@...r.kernel.org, kernelnewbies@...nelnewbies.org
Subject: Re: How to verify linux-next
On Sun, Oct 1, 2017 at 10:33 PM, Mike Galbraith <efault@....de> 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.
Powered by blists - more mailing lists