Comment # 18 on bug 1175893 from Jiri Slaby

(In reply to Jiri Slaby from comment #17)
> (In reply to Ruediger Oertel from comment #16)
> > no the .44 kernel did not show this problem,
> 
> 914f31e37c30f32baa66f8440141b852519f4c47
> 
> >  only the .47
> 
> 41f7396defec6284cc6873246964a0b9e9ca9a6d

I cannot see anything obvious in that range:
> git one --no-merges 914f31e37c30f32baa66f8440141b852519f4c47..41f7396defec6284cc6873246964a0b9e9ca9a6d|grep -viE 'scsi|media|crypto|btrfs|rbd|mmc|spi|bluetooth|serial|nfs'


Sched changes seem to be only numa-specific by Mel:
> 30c0b50f mm: call cond_resched() from deferred_init_memmap() (git fixes (mm/init), bsc#1177697).
> 759de680 Delete patches.suse/sched-fair-update_pick_idlest-Select-group-with-lowest-group_util-when-idle_cpus-are-equal.patch.
> a9a7020e sched/fair: Ignore cache hotness for SMT migration (bnc#1155798 (CPU scheduler functional and performance backports)).
> c9c51db4 sched/numa: Use runnable_avg to classify node (bnc#1155798 (CPU scheduler functional and performance backports)).
> cedbcc9e sched/fair: Use dst group while checking imbalance for NUMA balancer (bnc#1155798 (CPU scheduler functional and performance backports)).
> aa3fc2ac sched/numa: Avoid creating large imbalances at task creation time (bnc#1176588).
> 576f70b9 sched/numa: Check numa balancing information only when enabled (bnc#1176588).

Looking at them, I don't think they could cause this.