You don't need to attach syslog for every bisection run, only if something weird happens like having absolutely no wireless.
I don't know what happened in 0001, but we can ignore it for now. It will only become an issue if the problem is with a nearby commit. And the apparmor messages are nothing to worry about.
The next kernel is building, should be ready before too much longer.
You don't need to attach syslog for every bisection run, only if something weird happens like having absolutely no wireless.
I don't know what happened in 0001, but we can ignore it for now. It will only become an issue if the problem is with a nearby commit. And the apparmor messages are nothing to worry about.
The next kernel is building, should be ready before too much longer.