[Bug 1157035] New: Xen 4.13.0 RC1, dom0 backtrace in xen_mc_flush
http://bugzilla.suse.com/show_bug.cgi?id=1157035 Bug ID: 1157035 Summary: Xen 4.13.0 RC1, dom0 backtrace in xen_mc_flush Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xen Assignee: xen-bugs@suse.de Reporter: ohering@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 824366 --> http://bugzilla.suse.com/attachment.cgi?id=824366&action=edit tw.txt A fresh TW 20191112 shows the attached backtrace in dom0 after initial boot. Only the Xenstore domU is running. [ 61.673738] WARNING: CPU: 2 PID: 1416 at arch/x86/xen/multicalls.c:102 xen_mc_flush+0x1d0/0x200 [ 61.680650] CPU: 2 PID: 1416 Comm: (agetty) Not tainted 5.3.9-1-default #1 openSUSE Tumbleweed (unreleased) [ 61.685777] Hardware name: HP ProLiant SL160z G6 /ProLiant SL160z G6 , BIOS O33 07/28/2009 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1157035 Charles Arnold <carnold@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|xen-bugs@suse.de |jgross@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1157035 http://bugzilla.suse.com/show_bug.cgi?id=1157035#c1 --- Comment #1 from Olaf Hering <ohering@suse.com> --- This backtrace appeared just once. It was in fact after the second boot of a dom0. After fresh install yast will configure the system in the second stage of install, then another reboot is triggered via autoyast.xml. The backtrace happend afte that second reboot. I did two more installs from the same TW snapshot, it id not happen anymore. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1157035 https://bugzilla.suse.com/show_bug.cgi?id=1157035#c2 J�rgen Gro� <jgross@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from J�rgen Gro� <jgross@suse.com> --- The stack backtrace is a strong hint that this is a duplicate of bsc#1175749. *** This bug has been marked as a duplicate of bug 1175749 *** -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com