[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Thomas Goirand <thomas@xxxxxxxxxx>
  • Date: Sun, 11 Apr 2010 17:49:30 +0800
  • Delivery-date: Sun, 11 Apr 2010 02:49:16 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=goirand.fr; h=message-id:date :from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=J6g d3foDXfCtQBBqsHo7q3pRBGawtL4/EPZSQDOY4WETgHrPbLVo8H7l2wKyKiLlK64 lINiU/k4Z6XviT2R/9LhM7xNUA261HzHUvJ6iMl9maCImph7WogDGINj8+ZtxLWG tm/xBhLqHNpnYCsG+VZ8G2FyYW4GQDcVt2Ekbs2Q=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Openpgp: id=98EF9A49

Jeremy Fitzhardinge wrote:
> On 04/10/2010 03:13 PM, Thomas Schwinge wrote:
>>> Normally that would be OK, because it uses:
>>>
>>>     __get_user(pfn, &machine_to_phys_mapping[mfn]);
>>>
>>> to dereference the array.  But at this early stage, none of the kernel's
>>> exception handlers have been set up, so this will just fault into Xen.
>>>
>>> It would be interesting to confirm this by building your kernel with
>>> CONFIG_DEBUG_INFO=y in the .config, and verify that the faulting
>>> instruction is actually this line.
>>>     
>> Bingo!
>>   
> 
> Excellent.

Could this be also the reason why I had very funky memory management
(eg: some RAM missing between "xm list" and "xm info")?

Thomas

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.