Comment # 55 on bug 935993 from Walther Pelser

(In reply to Takashi Iwai from comment #48)
> (In reply to Walther Pelser from comment #47)
> > Thanks for your answer!
> > 1. There are no "desktop"-kernels in repsitory/Kernel/Head or
> > /Kernel/standard anymore. So I will wait or try a default-kernel later on.
> 
> Right, we deprecated kernel-desktop flavor.  It's replaced with
> kernel-default now.
>  
> > 2. Now I am used to built my own kernel (act. version 4.1.10,
> > localyesconfig, size 20,7 MB, built-time 27 min) and this kernel is always
> > working fine (with some timing-problems caused by systemd). So it must be a
> > SUSE-specific problem and not a raid0.ko one. But, as I seem to be the only
> > one with it, it should be dropped or closed.
> 
> You should try localmodconfig instead of localyesconfig.  We take only few
> SUSE-specific patches (except for ARM64 and Xen ones).  The possible
> difference is rather whether it's a built-in or a module -- which influences
> on the timing.

Two days ago I had to install a complete new tumbleweed-OS because of massive
data-corruption. F.i. /proc was indicated with asize of 150 TB!
This new system shows the same booting-problem with with wicked (randomly  only
parts of wicked are started, mostly parts of wicked are deleted by systemd
because of dependencies). There is obviously no relation to the kind of kernel,
which is used.
And there occurs a similar problem: Only after hibernation my DVB-USB-Stick is
not correctly installed. I avoid this by my own kernel with built- module and
built-in firmware.