This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] pv_ops domU crashes on pv_ops dom0 (directly at boot)

To: Markus Schuster <ml@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] pv_ops domU crashes on pv_ops dom0 (directly at boot)
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 15 Dec 2009 11:57:30 -0800
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 15 Dec 2009 11:58:49 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200912151349.42598.ml@xxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <200912052352.06078.ml@xxxxxxxxxxxxxxxxxxxx> <4B1D938F.7040409@xxxxxxxx> <200912092235.45173.ml@xxxxxxxxxxxxxxxxxxxx> <200912151349.42598.ml@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20091203 Fedora/3.0-3.13.rc2.fc12 Thunderbird/3.0
On 12/15/2009 04:49 AM, Markus Schuster wrote:
On Wednesday 09 December 2009 22:35:44 Markus Schuster wrote:
On Tuesday 08 December 2009 00:45:19 Jeremy Fitzhardinge wrote:
On 12/06/09 14:08, Markus Schuster wrote:

What to do to find out the line in code that crashes?
If you built the kernel, then:

You'll get best results if you enable CONFIG_DEBUG_INFO.
Sorry for the delay, but I used a Debian binary kernel, so I had to grab
Debian sources and rebuild it in order to have reproduceable results. I've
enabled CONFIG_DEBUG_INFO from the start - it produced giant binaries :)

So I've done:
# gdb vmlinux
This GDB was configured as "x86_64-linux-gnu"...
(gdb) x/i 0xffffffff813861af
0xffffffff813861af<cache_add_dev+46>:  mov    (%rdi),%r14d
(gdb) list *0xffffffff813861af
0xffffffff813861af is in cache_add_dev
ernel/cpu/intel_cacheinfo.c:902). 897     static
  DECLARE_BITMAP(cache_dev_map, NR_CPUS);
899     /* Add/Remove cache interface for CPU device */
900     static int __cpuinit cache_add_dev(struct sys_device * sys_dev)
901     {
902             unsigned int cpu = sys_dev->id;
903             unsigned long i, j;
904             struct _index_kobject *this_object;
905             int retval;
Hi Jeremy, sorry for beeing a bit cumbersome, but have you been able to get
some findings from my debugger output? Do you need additional input?

I don't understand what's happening here. It looks like there's some kind of initialization order problem in sysfs, but I don't have any handle on the details here.

It would be interesting to compare the .config of the working kernel with the crashing one (using scripts/diffconfig in the kernel source tree) to see if there's some kernel option which may be related to the crash.


Xen-users mailing list