public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.33-rc2: Xen/Guest switching to user mode with no user page tables
Date: Wed, 6 Jan 2010 14:21:33 +0300	[thread overview]
Message-ID: <20100106112133.GA5815@lenovo> (raw)
In-Reply-To: <alpine.DEB.2.01.1001060240010.3483@bogon.housecafe.de>

On Wed, Jan 06, 2010 at 03:06:05AM -0800, Christian Kujau wrote:
> On Wed, 6 Jan 2010 at 14:38, Jeremy Fitzhardinge wrote:
> > this message before, even during development.  I'd suspect either a compiler
> > bug, a miscompile, or some bad interaction with another patch.
> 
> I'm using the same compiler (gcc-4.4.2-8, binutils-2.20) for the 
> (working) 2.6.32 (Linus' git tree) and did a "make 
> distclean" to double check, but 2.6.33-rc2/3 just wouldn't boot.
> 
> > A bisection would be useful.
> 
> I'm *almost* there, only 1 or 2 revisions revisions left, I attached the 
> bisect log below. However, now this happens during "xm create" on the 
> DomU console:
> 
> ------------[ cut here ]------------
> WARNING: at /mnt/d1/linux-2.6-git/arch/x86/kernel/apic/apic_noop.c:130 
> noop_apic_write+0x40/0x50()
> Modules linked in:Pid: 0, comm: swapper Not tainted 2.6.32 #1
> Call Trace:
>  [<ffffffff81032563>] ? warn_slowpath_common+0x73/0xb0
>  [<ffffffff8101a7c0>] ? noop_apic_write+0x40/0x50
>  [<ffffffff81334160>] ? init_hw_perf_events+0x33d/0x3dd
>  [<ffffffff8100622f>] ? xen_restore_fl_direct_end+0x0/0x1
>  [<ffffffff81333cab>] ? identify_boot_cpu+0x15/0x3e
>  [<ffffffff81333dfe>] ? check_bugs+0x9/0x2e
>  [<ffffffff8132ec6e>] ? start_kernel+0x324/0x334
> ---[ end trace a7919e7f17c0a725 ]---
> 
...

This one should be fixed by the commit 125580380f418000b1a06d9a54700f1191b6e561
I believe.

	-- Cyrill

  reply	other threads:[~2010-01-06 11:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06  1:03 2.6.33-rc2: Xen/Guest switching to user mode with no user page tables Christian Kujau
2010-01-06  3:38 ` Jeremy Fitzhardinge
2010-01-06  3:48   ` Christian Kujau
2010-01-06  5:14     ` Jeremy Fitzhardinge
2010-01-06 11:06   ` Christian Kujau
2010-01-06 11:21     ` Cyrill Gorcunov [this message]
2010-01-06 12:43       ` Christian Kujau
2010-01-07 19:06         ` Christian Kujau
2010-01-07 19:20           ` Cyrill Gorcunov
2010-01-07 19:31             ` Christian Kujau
2010-01-07 19:34               ` Cyrill Gorcunov
2010-01-07 19:19         ` H. Peter Anvin
2010-01-07 19:30           ` Christian Kujau
2010-01-08 21:50             ` Cyrill Gorcunov
2010-01-09 23:55               ` Christian Kujau
2010-01-10  1:50               ` Brian Gerst
2010-01-10  8:09                 ` Cyrill Gorcunov
2010-01-10 12:59                   ` Ian Campbell
2010-01-10 13:36                     ` Cyrill Gorcunov
2010-01-10 13:49                       ` Cyrill Gorcunov
2010-01-10 14:05                         ` Ian Campbell
2010-01-15  8:36                     ` Christian Kujau
2010-01-15 11:29                       ` Ian Campbell
2010-01-15 12:03                         ` Cyrill Gorcunov
2010-01-15 12:00                       ` Cyrill Gorcunov

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=20100106112133.GA5815@lenovo \
    --to=gorcunov@gmail.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    /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