Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1457397 > unrolled thread
| Started by | Guenter Roeck <linux@roeck-us.net> |
|---|---|
| First post | 2016-08-07 00:50 +0200 |
| Last post | 2016-08-07 07:20 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
Traceback seen once when running x86 qemu emulation with latest kernel Guenter Roeck <linux@roeck-us.net> - 2016-08-07 00:50 +0200
Re: Traceback seen once when running x86 qemu emulation with latest kernel Borislav Petkov <bp@alien8.de> - 2016-08-07 07:20 +0200
| From | Guenter Roeck <linux@roeck-us.net> |
|---|---|
| Date | 2016-08-07 00:50 +0200 |
| Subject | Traceback seen once when running x86 qemu emulation with latest kernel |
| Message-ID | <s3izM-3u7-7@gated-at.bofh.it> |
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
[toc] | [next] | [standalone]
| From | Borislav Petkov <bp@alien8.de> |
|---|---|
| Date | 2016-08-07 07:20 +0200 |
| Message-ID | <s3oFc-7N7-3@gated-at.bofh.it> |
| In reply to | #1457397 |
On Sat, Aug 06, 2016 at 03:41:23PM -0700, Guenter Roeck wrote:
> 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
We were debugging this but it has gone nowhere AFAIR:
https://lkml.kernel.org/r/20160211192741.GG5565@pd.tnic
https://lkml.kernel.org/r/87d1rk9str.fsf@yhuang-dev.intel.com
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web