On Mittwoch, 3. Februar 2016, 18:54:07 CET wrote Ruediger Meier:
On Wednesday 03 February 2016, Adrian Schröter wrote:
On Mittwoch, 3. Februar 2016, 16:46:42 CET wrote Ruediger Meier:
On Wednesday 03 February 2016, Adrian Schröter wrote:
On Montag, 1. Februar 2016, 09:49:59 CET wrote Adrian Schröter:
On Montag, 1. Februar 2016, 09:43:53 CET wrote Ruediger Meier:
On Thursday 07 May 2015, Ruediger Meier wrote: > Hi, > > I get kernel oopses very often for SLE_12 builds on x86_64 > and ppc64le. Is this a known problem?
This kernel oops still happens. Where can I bug report this for SLE_12_SP1?
SP1 is not yet imported at all. Sorry, had not time for it yet.
So this is either a generic SP0 issue or a build host issue.
SP1 is imported since monday.
One build is currently hanging again osc remotebuildlog home:rudi_m:ul-all/ul-plain SLE_12_SP1 ppc64le
I have created a bugreport for this against the kernel people:
Thanks! I'am on CC there but unfortunately I have no access to the bug report.
Last year I have collected a few hundred SLE_12 build logs. 17% of them have such oops, see, http://akne.unxz.net/~rudi/tmp/obs-log-SLE12.tar.xz $ grep -l "Oops" log-*/bl_*SLE_12* | wc -l 112 $ grep -L "Oops" log-*/bl_*SLE_12* | wc -l 538
Would be nice if one could reproduce that on a real machine (non-OBS). I don't own SLE.
Using osc build --vm-type=kvm will setup the same environment on your system, if you use openSUSE_13.2, you would even have the same host (but I doubt it does matter here). -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org