Errors when building a kernel

Ralf Mardorf ralf.mardorf at
Sat Aug 22 11:21:04 UTC 2015

On Sat, 22 Aug 2015 12:20:33 +0200, Oliver Grawert wrote:
>if you just want to know if an arch kernel wakes up your disk when
>running with ubuntu userspace you could as well just copy over the
>binaries from a running arch system.

Or just edit grub.cfg to mix the Arch kernel with the Ubuntu install,
this at least could be done with older grub releases. However, this is
not what I need, since this approach has got weak points.

>if you want to find an offending config option in an ubuntu kernel you
>should probably not switch all variables at the same time as the
>result will be pointless.

I haven't done this. As I pointed out, I compiled the kernel several
times and edited one CONFIG after the other, it solved the issue for
each config, one after the other, just the latest issue
with CONFIG_MPILIB isn't that easy to solve.

>there are upstream based kernel trees as well as mainline that have the
>right config setup for in their debian/rules on, if
>you want to verify *anything* kernel side by changing a config setup
>you should do it with the right tree not with an upstream tarball
>where you obviously also edited the config by hand ...

>it is really hard to help you if you refuse to accept any help all the

Perhaps you understand an analogy. Doing it that way would be like
measuring with a meter, that is powered by the same current source as
the circuit you'll measure. IOW I quasi try to archive "galvanic
isolation" from Ubuntu configs and Ubuntu/Debian rules, to build a
kernel for Ubuntu. This usually doesn't cause issues, neither for
vanilla, nor for vanilla rt patched kernels, from Now it
does cause an issue and I ask for help to do it that way. I know how to
do it in other ways. Perhaps you understand the "galvanic isolation"

More information about the Ubuntu-devel-discuss mailing list