mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans Rosenfeld <hans.rosenfeld@amd.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "hpa@zytor.com" <hpa@zytor.com>,
	"brgerst@gmail.com" <brgerst@gmail.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"suresh.b.siddha@intel.com" <suresh.b.siddha@intel.com>,
	"eranian@google.com" <eranian@google.com>,
	"Richter, Robert" <robert.richter@amd.com>,
	"Herrmann3, Andreas" <Andreas.Herrmann3@amd.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC v3 0/8] x86, xsave: rework of extended state handling, LWP support
Date: Thu, 7 Apr 2011 17:30:29 +0200	[thread overview]
Message-ID: <20110407153029.GU13@escobedo.osrc.amd.com> (raw)
In-Reply-To: <20110407072305.GA20291@elte.hu>

On Thu, Apr 07, 2011 at 03:23:05AM -0400, Ingo Molnar wrote:
> 
> FYI, the bits in tip:x86/xsave crash on boot on an AMD X2 testbox:
> 
> [   10.823492] Freeing unused kernel memory: 616k freed
> [   11.087787] ------------[ cut here ]------------
> [   11.088312] Kernel BUG at ffffffff8100a140 [verbose debug info unavailable]
> [   11.088312] invalid opcode: 0000 [#1] SMP 
> [   11.088312] last sysfs file: 
> [   11.088312] CPU 1 
> [   11.088312] Modules linked in:
> [   11.088312] 
> [   11.088312] Pid: 41, comm: modprobe Not tainted 2.6.39-rc2-tip+ #113394  
> [   11.088312] RIP: 0010:[<ffffffff8100a140>]  [<ffffffff8100a140>] start_thread_common.constprop.1+0x100/0x110
> [   11.088312] RSP: 0018:ffff88003d7c5c40  EFLAGS: 00010246
> [   11.088312] RAX: ffff88003d7c5fd8 RBX: ffff88003d74bd40 RCX: 0000000000000033
> [   11.088312] RDX: 00007ffffffff000 RSI: 000000310f600ac0 RDI: 0000000000000000
> [   11.088312] RBP: ffff88003d7c5c60 R08: 0000000000000000 R09: 0000000000000004
> [   11.088312] R10: 00007fff4ae4dd68 R11: 0000000000000000 R12: 00007fff4ae4dd60
> [   11.088312] R13: 000000310f600ac0 R14: 0000000000000033 R15: ffff88003d74bd40
> [   11.088312] FS:  00007f48d909f780(0000) GS:ffff88003fd00000(0000) knlGS:0000000000000000
> [   11.088312] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> [   11.088312] CR2: 00007fff4ae4def9 CR3: 000000003d7af000 CR4: 00000000000006e0
> [   11.088312] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [   11.088312] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [   11.088312] Process modprobe (pid: 41, threadinfo ffff88003d7c4000, task ffff88003d74bd40)
> [   11.088312] Stack:
> [   11.088312]  ffff88003d72c400 ffff88003d60a400 0000000000000000 ffff88003d7c5e80
> [   11.088312]  ffff88003d7c5c70 ffffffff8100a546 ffff88003d7c5d90 ffffffff8117c7de
> [   11.088312]  ffff88003d74bd40 0000000000000004 00007fff4ae4dda8 00007fff4ae4dd68
> [   11.088312] Call Trace:
> [   11.088312]  [<ffffffff8100a546>] start_thread+0x16/0x20
> [   11.088312]  [<ffffffff8117c7de>] load_elf_binary+0x14fe/0x1980
> [   11.088312]  [<ffffffff81138392>] search_binary_handler+0xc2/0x2a0
> [   11.088312]  [<ffffffff8117b2e0>] ? load_elf_library+0x2b0/0x2b0
> [   11.088312]  [<ffffffff8113a35c>] do_execve+0x24c/0x2d0
> [   11.088312]  [<ffffffff81014b97>] sys_execve+0x47/0x80
> [   11.088312]  [<ffffffff8145b698>] kernel_execve+0x68/0xd0
> [   11.088312]  [<ffffffff8106ca83>] ? ____call_usermodehelper+0x93/0xa0
> [   11.088312]  [<ffffffff8145b624>] kernel_thread_helper+0x4/0x10
> [   11.088312]  [<ffffffff81459f54>] ? retint_restore_args+0x13/0x13
> [   11.088312]  [<ffffffff8106c9f0>] ? call_usermodehelper_setup+0xe0/0xe0
> [   11.088312]  [<ffffffff8145b620>] ? gs_change+0x13/0x13
> [   11.088312] Code: f0 4c 8b 75 f8 c9 c3 0f 1f 40 00 48 8b 3d 19 01 64 00 48 85 ff 74 14 48 89 bb a0 04 00 00 48 c7 05 02 01 64 00 00 00 00 00 eb a1 <0f> 0b 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 66 
> [   11.088312] RIP  [<ffffffff8100a140>] start_thread_common.constprop.1+0x100/0x110
> [   11.088312]  RSP <ffff88003d7c5c40>

Sorry for that, it seems I made a wrong assumption about
kernel_execve() usage. Updated patches will follow shortly.


Hans


-- 
%SYSTEM-F-ANARCHISM, The operating system has been overthrown


  reply	other threads:[~2011-04-07 15:30 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 19:14 [RFC 0/8] " Hans Rosenfeld
2011-03-09 19:14 ` [RFC 1/8] x86, xsave: cleanup fpu/xsave support Hans Rosenfeld
2011-03-09 19:14 ` [RFC 2/8] x86, xsave: rework " Hans Rosenfeld
2011-03-09 19:14 ` [RFC 3/8] x86, xsave: cleanup fpu/xsave signal frame setup Hans Rosenfeld
2011-03-09 19:14 ` [RFC 4/8] x86, xsave: remove unused code Hans Rosenfeld
2011-03-09 19:14 ` [RFC 5/8] x86, xsave: more cleanups Hans Rosenfeld
2011-03-09 19:15 ` [RFC 6/8] x86, xsave: add support for non-lazy xstates Hans Rosenfeld
2011-03-09 19:15 ` [RFC 7/8] x86, xsave: add kernel support for AMDs Lightweight Profiling (LWP) Hans Rosenfeld
2011-03-09 19:15 ` [RFC 8/8] x86, xsave: remove lazy allocation of xstate area Hans Rosenfeld
2011-03-23 15:27   ` [RFC v2 0/8] x86, xsave: rework of extended state handling, LWP support Hans Rosenfeld
2011-03-23 15:27   ` [RFC v2 1/8] x86, xsave: cleanup fpu/xsave support Hans Rosenfeld
2011-03-23 15:27   ` [RFC v2 2/8] x86, xsave: rework " Hans Rosenfeld
2011-03-23 15:27   ` [RFC v2 3/8] x86, xsave: cleanup fpu/xsave signal frame setup Hans Rosenfeld
2011-03-23 15:27   ` [RFC v2 4/8] x86, xsave: remove unused code Hans Rosenfeld
2011-03-23 15:27   ` [RFC v2 5/8] x86, xsave: more cleanups Hans Rosenfeld
2011-03-23 15:27   ` [RFC v2 6/8] x86, xsave: add support for non-lazy xstates Hans Rosenfeld
2011-03-23 15:27   ` [RFC v2 7/8] x86, xsave: add kernel support for AMDs Lightweight Profiling (LWP) Hans Rosenfeld
2011-03-23 15:27   ` [RFC v2 8/8] x86, xsave: remove lazy allocation of xstate area Hans Rosenfeld
2011-03-24 11:39     ` Brian Gerst
2011-03-29 14:17       ` Hans Rosenfeld
2011-03-29 15:27         ` H. Peter Anvin
2011-03-30 13:11           ` Hans Rosenfeld
2011-04-05 15:50           ` [RFC v3 0/8] x86, xsave: rework of extended state handling, LWP support Hans Rosenfeld
2011-04-07  7:23             ` Ingo Molnar
2011-04-07 15:30               ` Hans Rosenfeld [this message]
2011-04-07 16:08                 ` [RFC v4 6/8] x86, xsave: add support for non-lazy xstates Hans Rosenfeld
2011-04-07 16:08                 ` [RFC v4 8/8] x86, xsave: remove lazy allocation of xstate area Hans Rosenfeld
2011-04-13 10:58                 ` [PATCH] x86, xsave: fix non-lazy allocation of the xsave area Hans Rosenfeld
2011-04-13 23:21                   ` H. Peter Anvin
2011-04-15 16:47                     ` [PATCH 1/1] " Hans Rosenfeld
2011-05-16 19:10               ` [RFC v3 0/8] x86, xsave: rework of extended state handling, LWP support Hans Rosenfeld
2011-05-17 11:30                 ` Ingo Molnar
2011-05-17 15:22                   ` Hans Rosenfeld
2011-05-18 11:22                     ` Ingo Molnar
2011-05-18 13:51                     ` Ingo Molnar
2011-05-18  8:16                   ` Joerg Roedel
2011-05-18 10:59                     ` Ingo Molnar
2011-05-18 18:02                   ` Andreas Herrmann
2011-04-05 15:50           ` [RFC v3 1/8] x86, xsave: cleanup fpu/xsave support Hans Rosenfeld
2011-04-05 15:50           ` [RFC v3 2/8] x86, xsave: rework " Hans Rosenfeld
2011-04-05 15:50           ` [RFC v3 3/8] x86, xsave: cleanup fpu/xsave signal frame setup Hans Rosenfeld
2011-04-05 15:50           ` [RFC v3 4/8] x86, xsave: remove unused code Hans Rosenfeld
2011-04-05 15:50           ` [RFC v3 5/8] x86, xsave: more cleanups Hans Rosenfeld
2011-04-05 15:50           ` [RFC v3 6/8] x86, xsave: add support for non-lazy xstates Hans Rosenfeld
2011-04-05 15:50           ` [RFC v3 7/8] x86, xsave: add kernel support for AMDs Lightweight Profiling (LWP) Hans Rosenfeld
2011-04-06 22:06             ` [tip:x86/xsave] " tip-bot for Hans Rosenfeld
2011-04-05 15:50           ` [RFC v3 8/8] x86, xsave: remove lazy allocation of xstate area Hans Rosenfeld
2011-04-06 22:06             ` [tip:x86/xsave] " tip-bot for Hans Rosenfeld

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=20110407153029.GU13@escobedo.osrc.amd.com \
    --to=hans.rosenfeld@amd.com \
    --cc=Andreas.Herrmann3@amd.com \
    --cc=brgerst@gmail.com \
    --cc=eranian@google.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=robert.richter@amd.com \
    --cc=suresh.b.siddha@intel.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

Powered by JetHome