linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: ak@suse.de, discuss@x86-64.org, Pavel Machek <pavel@ucw.cz>,
	Andrew Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [discuss] Re: [PATCH][Fix][Resend] Fix Bug #4959: Page tables corrupted during resume on x86-64 (take 3)
Date: Sat, 1 Oct 2005 09:47:25 +0200	[thread overview]
Message-ID: <200510010947.25841.rjw@sisk.pl> (raw)
In-Reply-To: <20050930182530.E28092@unix-os.sc.intel.com>

Hi,

On Saturday, 1 of October 2005 03:25, Siddha, Suresh B wrote:
> On Fri, Sep 30, 2005 at 08:51:08AM +0200, Rafael J. Wysocki wrote:
> > On Friday, 30 of September 2005 07:26, Rafael J. Wysocki wrote:
> > > Of course.  The .config is attached.  Generally, it's a non-SMP box, and commenting
> > > out the zap_low_mappings((0) in setup_arch() makes the box boot again.
> > 
> > One more datapoint: The box boots if I move the zap_low_mappings((0)
> > in the following way:
> > 
> > --- linux-2.6.14-rc2-git7.orig/arch/x86_64/kernel/setup.c	2005-09-30 07:39:35.000000000 +0200
> > +++ linux-2.6.14-rc2-git7/arch/x86_64/kernel/setup.c	2005-09-30 08:31:20.000000000 +0200
> > @@ -571,8 +571,6 @@
> >  
> >  	init_memory_mapping(0, (end_pfn_map << PAGE_SHIFT));
> >  
> > -	zap_low_mappings(0);
> > -
> >  #ifdef CONFIG_ACPI
> >  	/*
> >  	 * Initialize the ACPI boot-time table parser (gets the RSDP and SDT).
> > @@ -680,6 +678,8 @@
> >  		get_smp_config();
> >  	init_apic_mappings();
> >  #endif
> > +	zap_low_mappings(0);
> > +
> 
> Rafael, I still can't reproduce the issue. All of my EM64T systems are SMP
> and looks like this problem happens only on an UP system. Looks like
> there is some code flow which is still assuming the presence of low mappings.

I think so too.

> Andi, can you please see if you can reproduce this on one of your systems
> similar to Rafael's.
> 
> >  	/*
> >  	 * Request address space for all standard RAM and ROM resources
> > 
> > iHowever, if I place the zap_low_mappings((0) before the
> > #define CONFIG_X86_LOCAL_APIC in line 673, it doesn't boot.
> > 
> > Certainly init_apic_mappings() is at fault.  Could that be a reult of a call to
> > alloc_bootmem_pages()?.
> 
> I looked at init_apic_mappings() and didn't give me any clue.
> alloc_bootmem_pages() don't use low direct mappings.

OK, I'll try to narrow this a bit more.

> > And one more: I have to boot with "noapic".
> 
> Are you saying "noapic" is the second data point or you need to use "noapic"
> along with moving zap_low_mappings(0) 

It could be the second data point.  I always boot with "noapic", since otherwise
the sharing of IRQs is not handled properly on my box.

Greetings
Rafael

  reply	other threads:[~2005-10-01  7:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 14:24 [PATCH][Fix][Resend] Fix Bug #4959: Page tables corrupted during resume on x86-64 (take 3) Rafael J. Wysocki
2005-09-28 19:18 ` Andi Kleen
2005-09-28 20:24   ` Rafael J. Wysocki
2005-09-28 20:33     ` [discuss] " Andi Kleen
2005-09-28 22:11       ` Rafael J. Wysocki
2005-09-28 22:35         ` Pavel Machek
2005-09-29 11:25           ` Rafael J. Wysocki
2005-09-29  0:00     ` Siddha, Suresh B
2005-09-29 10:58       ` Rafael J. Wysocki
2005-09-29 22:01       ` Rafael J. Wysocki
2005-09-29 22:29         ` Siddha, Suresh B
2005-09-29 23:04           ` Rafael J. Wysocki
2005-09-29 23:59             ` Siddha, Suresh B
2005-09-30  5:26               ` Rafael J. Wysocki
2005-09-30  6:51                 ` [discuss] " Rafael J. Wysocki
2005-10-01  1:25                   ` Siddha, Suresh B
2005-10-01  7:47                     ` Rafael J. Wysocki [this message]
2005-10-01 10:03                       ` Rafael J. Wysocki
2005-10-02  1:08                         ` Siddha, Suresh B
2005-10-02  9:54                           ` Rafael J. Wysocki
2005-09-29 20:02 ` Andrew Morton
2005-09-29 21:35   ` Rafael J. Wysocki

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=200510010947.25841.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=suresh.b.siddha@intel.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).