mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: bp@alien8.de, hpa@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [3.9-rc1 x86] Bug in ioremap code?
Date: Wed, 06 Mar 2013 09:51:43 -0800	[thread overview]
Message-ID: <5137822F.2030501@linux.vnet.ibm.com> (raw)
In-Reply-To: <201303062358.EFG90616.HLtSQFJFOMVOFO@I-love.SAKURA.ne.jp>

On 03/06/2013 06:58 AM, Tetsuo Handa wrote:
> Borislav Petkov wrote:
>> 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.
> 
> I'm using CentOS 6.3 x86_32 guest running on VMware Workstation 6.5.5 for
> Windows XP x86_32 host and VMware Player 4.0.5 for Windows 7 x86_64 host.
> 
> Kernel version is 3.9-rc1 x86_32. This bug can be triggered only when the
> guest has little RAM such that /proc/meminfo reports that HighTotal == 0.
> Config is at http://I-love.SAKURA.ne.jp/tmp/config-3.9-rc1-acpi .
> 
> I don't know why but changing kernel config to CONFIG_ACPI=n
> ( http://I-love.SAKURA.ne.jp/tmp/config-3.9-rc1-noacpi ) solves this bug.
> Well, should I run bisection on ACPI code?

I was able to reproduce and got some better debugging out of this:

[    0.193170] __cpa_process_fault(c1673e90, e4afa000, 1)
[    0.208752] max_pfn_mapped: 150528
[    0.218886] PAGE_OFFSET: c0000000
[    0.228597] PAGE_OFFSET + (max_pfn_mapped << PAGE_SHIFT)): e4c00000
[    0.247837] slow_virt_to_phys(e4afa000): 0

The pte looks to actually _be_ empty:

[   44.038145] slow_virt_to_phys() pte: 0000000000000000 level: 1

Not sure what's going on in the end, but it does appear this is another
win for the new BUG_ON().  There really does look to be a real bug here.

BTW, the BUG_ON() is proving to be woefully inadequate.  We need some
better diagnostic messages out of there, and probably a nice dump of the
pagetable walk too.


  parent reply	other threads:[~2013-03-06 17:52 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
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 [this message]
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=5137822F.2030501@linux.vnet.ibm.com \
    --to=dave@linux.vnet.ibm.com \
    --cc=bp@alien8.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome