From: Ingo Molnar <mingo@elte.hu>
To: Alok Kataria <akataria@vmware.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"H. Peter Anvin" <hpa@zytor.com>,
the arch/x86 maintainers <x86@kernel.org>,
Zach Amsden <zach@vmware.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Rohit Jain <rjain@vmware.com>,
LKML <linux-kernel@vger.kernel.org>,
tj@kernel.org
Subject: Re: [PARAVIRT/x86] BUGFIX: Put a missing paravirt_release_pmd in pgd_dtor
Date: Wed, 11 Feb 2009 13:48:02 +0100 [thread overview]
Message-ID: <20090211124802.GI16535@elte.hu> (raw)
In-Reply-To: <1234210794.16177.35.camel@alok-dev1>
* Alok Kataria <akataria@vmware.com> wrote:
> On Mon, 2009-02-09 at 04:10 -0800, Ingo Molnar wrote:
>
> >
> > Applied to tip:x86/urgent, thanks guys!
>
> Thanks Ingo,
>
> I gave the tip tree a spin today and hit this bug.
>
> BUG: unable to handle kernel NULL pointer dereference at (null)
> IP: [<(null)>] (null)
> *pdpt = 0000000000839001 *pde = 0000000000c97067 *pte = 0000000000000163
> Oops: 0000 [#1] SMP
> last sysfs file:
> Modules linked in:
>
> Pid: 1, comm: swapper Not tainted (2.6.29-rc4-tip #18) VMware Virtual
> Platform
> EIP: 0062:[<00000000>] EFLAGS: 00010293 CPU: 0
> EIP is at 0x0
> EAX: 00000001 EBX: 00006000 ECX: c077ed00 EDX: 00006000
> ESI: 00000001 EDI: 00000001 EBP: ef04cf40 ESP: ef04cf1c
> DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 006a
> Process swapper (pid: 1, ti=ef04c000 task=ef050000 task.ti=ef04c000)
> Stack:
> c0644e52 00000000 ef04cf24 ef04cf24 c064468d c0886dc0 00000000 c0702aea
> ef055480 00000001 00000101 dead4ead ffffffff ffffffff c08af530 00000000
> c0709715 ef04cf60 ef04cf60 00000001 00000000 00000000 dead4ead ffffffff
> Call Trace:
> [<c0644e52>] ? native_cpu_up+0x2de/0x45b
> [<c064468d>] ? do_fork_idle+0x0/0x19
> [<c0645c5e>] ? _cpu_up+0x88/0xe8
> [<c0645d20>] ? cpu_up+0x42/0x4e
> [<c07e7462>] ? kernel_init+0x99/0x14b
> [<c07e73c9>] ? kernel_init+0x0/0x14b
> [<c040375f>] ? kernel_thread_helper+0x7/0x10
> Code: Bad EIP value.
> EIP: [<00000000>] 0x0 SS:ESP 006a:ef04cf1c
This is the crash fixed by your later genapic patch, right?
> This happens with out the fix too. So was wondering if there is any
> other known bug in the tip tree.
> Also note that i synced to the mainline tree (29-rc4) and that works
> fine. So this only exists in tip.
> I will debug this later today, but if anyone has any ideas about this
> bug do let me know.
>
> And ya i also had to apply this patch to get tip to compile.
yes, that should be fixed too - it appeared briefly.
Let me know if you can see any problems with the latest -tip tree.
Ingo
prev parent reply other threads:[~2009-02-11 12:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 2:02 [PARAVIRT/x86] BUGFIX: Put a missing paravirt_release_pmd in pgd_dtor Alok Kataria
2009-02-06 2:30 ` Jeremy Fitzhardinge
2009-02-06 6:17 ` Alok Kataria
2009-02-06 6:52 ` Jeremy Fitzhardinge
2009-02-06 14:53 ` Ingo Molnar
2009-02-06 17:00 ` Jeremy Fitzhardinge
2009-02-06 18:29 ` Alok Kataria
2009-02-09 12:10 ` Ingo Molnar
2009-02-09 20:19 ` Alok Kataria
2009-02-11 12:48 ` Ingo Molnar [this message]
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=20090211124802.GI16535@elte.hu \
--to=mingo@elte.hu \
--cc=akataria@vmware.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjain@vmware.com \
--cc=rusty@rustcorp.com.au \
--cc=tj@kernel.org \
--cc=x86@kernel.org \
--cc=zach@vmware.com \
/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;
as well as URLs for NNTP newsgroup(s).