From: Borislav Petkov <bp@alien8.de>
To: Dave Hansen <dave@linux.vnet.ibm.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: hpa@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [3.9-rc1 x86] Bug in ioremap code?
Date: Tue, 5 Mar 2013 23:44:32 +0100 [thread overview]
Message-ID: <20130305224432.GD27022@pd.tnic> (raw)
In-Reply-To: <51367104.5050200@linux.vnet.ibm.com>
On Tue, Mar 05, 2013 at 02:26:12PM -0800, Dave Hansen wrote:
> Just booted a qemu-kvm guest with this .config. It didn't trip over
> anything, so I'm looking for some more ACPI tables to feed in to it.
>
> Looking through the code, it looks like this is the __pa() that's
> hitting the BUG_ON():
Shouldn't it be this one:
#ifdef CONFIG_DEBUG_VIRTUAL
unsigned long __phys_addr(unsigned long x)
{
unsigned long phys_addr = x - PAGE_OFFSET;
/* VMALLOC_* aren't constants */
VIRTUAL_BUG_ON(x < PAGE_OFFSET);
VIRTUAL_BUG_ON(__vmalloc_start_set && is_vmalloc_addr((void *) x));
/* max_low_pfn is set early, but not _that_ early */
if (max_low_pfn) {
VIRTUAL_BUG_ON((phys_addr >> PAGE_SHIFT) > max_low_pfn);
BUG_ON(slow_virt_to_phys((void *)x) != phys_addr); <--- **
}
return phys_addr;
}
EXPORT_SYMBOL(__phys_addr);
#endif
?
At least this is what the oops says:
> [ 0.083350] ------------[ cut here ]------------
> [ 0.084000] kernel BUG at arch/x86/mm/physaddr.c:79!
> [ 0.084000] invalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC
Tetsuo says in some of the earlier mails:
"But I get VMware's virtual machine kernel stack fault (hardware reset)
as soon as kernel is loaded if CONFIG_DEBUG_VIRTUAL=y is added to the
config above."
> What kind of hardware is this?
[ 0.084000] Pid: 0, comm: swapper/0 Not tainted 3.8.0-rc5-00105-g68d00bb #47 VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform
I asked Tetsuo to confirm but it looks like 32-bit guest running in
vmware.
Ok, before we continue guessing stuff, Tetsuo, can you please explain
how exactly you're triggering this. More specifically, we need .config,
hypervisor version, I'm assuming kernel is 3.9-rc1, Linux is guest/host
etc, etc.
Basically everything one would need to know if one would like to
reproduce this bug in his environment.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-03-05 22:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 15:35 [linux-next-20130205] Bug in bootup code or debug code? Tetsuo Handa
2013-03-04 15:15 ` [3.9-rc1] " Tetsuo Handa
2013-03-05 11:31 ` [3.9-rc1 x86/microcode] Bug in CONFIG_MICROCODE_INTEL_EARLY=y Tetsuo Handa
2013-03-05 15:41 ` [3.9-rc1 x86] Bug in ioremap code? Tetsuo Handa
2013-03-05 18:06 ` Borislav Petkov
2013-03-05 21:28 ` Tetsuo Handa
2013-03-05 22:15 ` H. Peter Anvin
2013-03-05 23:46 ` Dave Hansen
2013-03-05 23:58 ` H. Peter Anvin
2013-03-06 0:39 ` Yu, Fenghua
2013-03-06 1:12 ` Yu, Fenghua
2013-03-06 1:35 ` H. Peter Anvin
2013-03-05 22:26 ` Dave Hansen
2013-03-05 22:44 ` Borislav Petkov [this message]
2013-03-06 0:22 ` Dave Hansen
2013-03-06 10:16 ` Tetsuo Handa
2013-03-06 11:16 ` H. Peter Anvin
2013-03-06 14:58 ` Tetsuo Handa
2013-03-06 15:44 ` Dave Hansen
2013-03-06 17:51 ` Dave Hansen
2013-03-06 18:15 ` Dave Hansen
2013-03-06 23:17 ` Dave Hansen
2013-03-13 13:24 ` [3.9-rc1] Bug in bootup code or debug code? Tetsuo Handa
2013-03-13 15:22 ` Yu, Fenghua
2013-03-13 17:44 ` H. Peter Anvin
2013-03-13 20:45 ` Tetsuo Handa
2013-03-19 22:12 ` Yu, Fenghua
2013-03-20 14:24 ` Shaun Ruffell
2013-03-20 16:32 ` Yu, Fenghua
2013-03-20 17:03 ` Shaun Ruffell
2013-03-20 17:05 ` Yu, Fenghua
2013-03-20 17:14 ` Shaun Ruffell
2013-03-22 1:24 ` [tip:x86/urgent] x86, microcode_intel_early: Mark apply_microcode_early() as cpuinit tip-bot for H. Peter Anvin
2013-03-13 17:45 ` [3.9-rc1] Bug in bootup code or debug code? H. Peter Anvin
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=20130305224432.GD27022@pd.tnic \
--to=bp@alien8.de \
--cc=dave@linux.vnet.ibm.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.