From: Guenter Roeck <linux@roeck-us.net>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Traceback seen once when running x86 qemu emulation with latest kernel
Date: Sat, 6 Aug 2016 15:41:23 -0700 [thread overview]
Message-ID: <57A66793.2060907@roeck-us.net> (raw)
Hi, I have seen the following traceback once when running the latest mainline in qemu.
Starting udev
random: crng init done
udevd[117]: starting version 182
Starting Bootlog daemon: bootlogd.
EXT4-fs (hda): re-mounted. Opts: errors=remount-ro,data=ordered
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1 at ./arch/x86/include/asm/fpu/internal.h:534 fpu__restore+0x120/0x220
Modules linked in:
CPU: 0 PID: 1 Comm: init Not tainted 4.7.0-yocto-standard+ #1
Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
00000000 00000000 cf893e58 c1390e2a cf893e88 c1042ea1 c19ea4bc 00000000
00000001 c19e5428 00000216 c1021100 00000216 cf8e8d40 00000000 cf8e8000
cf893e9c c1042eea 00000009 00000000 00000000 cf893eb4 c1021100 00000000
Call Trace:
[<c1390e2a>] dump_stack+0x16/0x1c
[<c1042ea1>] __warn+0xe1/0x100
[<c1021100>] ? fpu__restore+0x120/0x220
[<c1042eea>] warn_slowpath_null+0x2a/0x30
[<c1021100>] fpu__restore+0x120/0x220
[<c1022669>] __fpu__restore_sig+0x139/0x610
[<c1022dff>] fpu__restore_sig+0x2f/0x50
[<c1017bda>] restore_sigcontext.isra.7+0xda/0x100
[<c1018451>] sys_sigreturn+0x91/0xb0
[<c100161a>] do_int80_syscall_32+0x5a/0xa0
[<c1800e1e>] entry_INT80_32+0x2a/0x2a
---[ end trace b5a2004ac28f878b ]---
Configuring network interfaces... done.
Command line:
qemu-system-i386 -kernel arch/x86/boot/bzImage -M isapc -cpu n270 -no-reboot \
-m 256 -drive file=core-image-minimal-qemux86.ext3,format=raw,if=ide \
--append "root=/dev/hda rw mem=256M vga=0 uvesafb.mode_option=640x480-32 oprofile.timer=1 console=ttyS0 console=tty"
-nographic
Kernel version: v4.7-12388-g0cbbc422d566
Scripts and root file system used for test:
https://github.com/groeck/linux-build-test/tree/master/rootfs/x86
Log file:
http://kerneltests.org/builders/qemu-x86-master/builds/581/steps/qemubuildcommand/logs/stdio
Unfortunately, I was unable to reproduce the problem by re-running the test manually.
Please let me know if there is anything I can do to help reproduce or fix the problem.
Thanks,
Guenter
next reply other threads:[~2016-08-06 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 22:41 Guenter Roeck [this message]
2016-08-07 5:14 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57A66793.2060907@roeck-us.net \
--to=linux@roeck-us.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®