From mboxrd@z Thu Jan 1 00:00:00 1970 From: Valtteri Kiviniemi Subject: Re: Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)" Date: Wed, 13 Oct 2010 10:03:49 +0300 Message-ID: <4CB559D5.2070002@dataproof.fi> References: <19629.39326.337589.71778@wylie.me.uk> <4CB41800.7050806@hfp.de> <4CB4ADB9.2030704@goop.org> <4CB4BEB8.6090208@dataproof.fi> <4CB4FCB9.9090303@goop.org> Reply-To: valtteri.kiviniemi@dataproof.fi Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4CB4FCB9.9090303@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: "Alan J. Wylie" , xen-devel@lists.xensource.com, Andreas Kinzler List-Id: xen-devel@lists.xenproject.org Hi, Yes, probably some kernel hacking option. I have enabled these options: /boot/config-dom0 - Linux Kernel v2.6.32.24 Configuration Kernel hacking [*] Enable __must_check logic [*] Magic SysRq key -*- Debug Filesystem [*] Kernel debugging [*] Collect scheduler statistics [*] Collect kernel timers statistics [*] Compile the kernel with frame pointers [*] Sysctl checks [*] Tracers ---> [*] Support for tracing block io actions [*] Remote debugging over FireWire early on boot [*] Enable verbose x86 bootup info messages -*- Early printk [*] Early printk via EHCI debug port [*] Check for stack overflows [*] Write protect kernel read-only data structures [*] Debug boot parameters [*] Allow gcc to uninline functions marked 'inline' All the other options are disabled. So it one/some of those that need to be enabled to get the kernel booting. Let me know if you need my config-file - Valtteri Kiviniemi Jeremy Fitzhardinge kirjoitti: > On 10/12/2010 01:02 PM, Valtteri Kiviniemi wrote: >> Hi, >> >> I just compiled Xen 4.0.0.1 with 2.6.32.24 and I stuck on this same >> problem with my own compiled kernel. However the default kernel with >> comes from "make world" boots fine. I traced the problem down to some >> settings in kernel's menuconfig "Kernel hacking" menu. I dont exactly >> know what the option needs to be enabled in the "Kernel hacking" to >> get the kernel booting. In my own compiled kernels I have almost all >> the options in that "Kernel hacking" menu disabled, and when I enabled >> the same options in that menu that are in the default kernel which >> comes when you do "make world" the system booted fine. >> >> You probably know the problem already but I just thought that I should >> share this information with you anyway. > > No, that's interesting. So some kernel debugging config option makes > the problem go away? That gives me some way to possibly repro the problem. > > J > > >> - Valtteri Kiviniemi >> >> Jeremy Fitzhardinge kirjoitti: >>> On 10/12/2010 01:10 AM, Andreas Kinzler wrote: >>>> On 07.10.2010 11:57, Alan J. Wylie wrote: >>>>> System: Supermicro SM-SC825TQ-R720LPB, 8GB RAM >>>>> Motherboard: X8DTL >>>>> Processor: 1 x Intel XEON E5506 quad core >>>>> RAID controller: LSI MegaRAID SAS 8708 >>>>> >>>>> Bisected (by hand) to between >>>>> 69e50db2 (good) 2.6.32.21 "Merge commit 'v2.6.32.21' into >>>>> xen/next-2.6.32" >>>>> and >>>>> dda56688 (bad) "Merge branch 'xen/next' into >>>>> xen/next-2.6.32" >>>>> >>>>> ffffffff8100bd10 T get_phys_to_machine >>>>> ffffffff8100bd4c t pin_pagetable_pfn >>>> I am afflicted by this problem for a long while now. Should look very >>>> familiar to you. See >>>> http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00758.html >>>> >>>> >>>> No solution till now. >>> Is it not fixed by current xen/stable-2.6.32.x kernels? >>> >>> J >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel