Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1742859
| From | Pintu Kumar <pintu.ping@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: How to verify linux-next |
| Date | 2017-10-01 20:50 +0200 |
| Message-ID | <uvRtn-5BE-9@gated-at.bofh.it> (permalink) |
| References | (8 earlier) <uvivD-8h5-1@gated-at.bofh.it> <uvPhT-4nz-1@gated-at.bofh.it> <uvPBg-4ux-21@gated-at.bofh.it> <uvPBh-4ux-33@gated-at.bofh.it> <uvPUC-4Q7-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sun, Oct 1, 2017 at 10:33 PM, Mike Galbraith <efault@gmx.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.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-09-29 11:50 +0200
Re: How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-09-29 11:50 +0200
Re: How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-09-29 12:40 +0200
Re: How to verify linux-next valdis.kletnieks@vt.edu - 2017-09-29 15:00 +0200
Re: How to verify linux-next Damian Tometzki <damian.tometzki@icloud.com> - 2017-09-29 15:20 +0200
Re: How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-09-29 16:30 +0200
Re: How to verify linux-next valdis.kletnieks@vt.edu - 2017-09-29 17:50 +0200
Re: How to verify linux-next Kamil Konieczny <k.konieczny@partner.samsung.com> - 2017-10-02 10:20 +0200
Re: How to verify linux-next valdis.kletnieks@vt.edu - 2017-10-02 13:10 +0200
Re: How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-09-29 20:00 +0200
Re: How to verify linux-next Theodore Ts'o <tytso@mit.edu> - 2017-09-30 00:00 +0200
Re: How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-09-30 06:00 +0200
Re: How to verify linux-next Theodore Ts'o <tytso@mit.edu> - 2017-09-30 07:30 +0200
Re: How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-10-01 18:30 +0200
Re: How to verify linux-next Damian Tometzki <damian.tometzki@icloud.com> - 2017-10-01 18:50 +0200
Re: How to verify linux-next Randy Dunlap <rdunlap@infradead.org> - 2017-10-01 18:50 +0200
Re: How to verify linux-next Mike Galbraith <efault@gmx.de> - 2017-10-01 19:10 +0200
Re: How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-10-01 20:50 +0200
Re: How to verify linux-next Theodore Ts'o <tytso@mit.edu> - 2017-10-01 18:50 +0200
Re: How to verify linux-next Damian Tometzki <damian.tometzki@icloud.com> - 2017-09-29 16:10 +0200
csiph-web