From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: M A Young <m.a.young@durham.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Crash on boot with 2.6.37-rc8-git3
Date: Thu, 20 Jan 2011 14:24:34 -0500 [thread overview]
Message-ID: <20110120192434.GA10001@dumpdata.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1101192249200.30335@vega4.dur.ac.uk>
On Wed, Jan 19, 2011 at 10:54:00PM +0000, M A Young wrote:
> On Tue, 18 Jan 2011, M A Young wrote:
>
> >My next theory is that the issue is that the system is an
> >alignment issue. The NODE DATA is put in the range
> >00000000df659800 to 00000000df66d7ff (the top end of the second
> >"usable" chunk) and the problem come when it tries to write to the
> >final 2K piece (00000000df66d000 to 00000000df66d800 -
> >00000000df66d000 occurs on the stack) which hasn't been
> >initialized properly because it isn't a 4K piece.
> >Does this sound plausible?
>
> Further experiments confirm that it is this 2K piece causing the
> problem - if I reserve the 2K chunk in the same was that NODE DATA
> is reserved (though without zeroing it) the system boots, if I
> reduce this to reserving only 1K then it doesn't.
I think my math is off here. The reserve call is made on the
df659800 -> df66d7ff, that would be 20 pages of data. The last
PFN df66d is where it dies b/c there is no PTE entry set for it?
What happens if you fudge the code so it allocates those pages to be
page aligned. So df65a000->df66e000 ? We skip this way the region
df659800->df659fff and start on a new PFN (and pte).
next prev parent reply other threads:[~2011-01-20 19:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 20:34 Crash on boot with 2.6.37-rc8-git3 M A Young
2011-01-07 21:23 ` Konrad Rzeszutek Wilk
2011-01-08 0:10 ` M A Young
2011-01-10 18:42 ` Konrad Rzeszutek Wilk
2011-01-10 21:43 ` M A Young
2011-01-16 20:48 ` M A Young
2011-01-16 20:56 ` Keir Fraser
2011-01-18 0:52 ` M A Young
2011-01-19 22:54 ` M A Young
2011-01-20 19:24 ` Konrad Rzeszutek Wilk [this message]
2011-01-20 22:39 ` M A Young
2011-01-21 15:27 ` Konrad Rzeszutek Wilk
2011-01-21 21:43 ` M A Young
2011-01-24 14:14 ` Konrad Rzeszutek Wilk
2011-01-24 23:12 ` M A Young
2011-01-25 12:03 ` Stefano Stabellini
2011-01-25 13:24 ` Ian Campbell
2011-01-25 13:31 ` Stefano Stabellini
2011-01-25 13:45 ` Ian Campbell
2011-01-25 15:19 ` Stefano Stabellini
2011-01-25 15:52 ` Konrad Rzeszutek Wilk
2011-01-25 15:56 ` Stefano Stabellini
2011-01-25 16:05 ` M A Young
2011-01-24 19:04 ` Stefano Stabellini
2011-01-25 0:22 ` M A Young
-- strict thread matches above, loose matches on Subject: below --
2011-01-04 22:01 M A Young
2011-01-05 15:43 ` Konrad Rzeszutek Wilk
2011-01-05 23:11 ` M A Young
2011-01-06 14:56 ` Konrad Rzeszutek Wilk
2011-01-07 0:37 ` M A Young
2011-01-07 19:18 ` Konrad Rzeszutek Wilk
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=20110120192434.GA10001@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=m.a.young@durham.ac.uk \
--cc=xen-devel@lists.xensource.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 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.