WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]

To: Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
From: PUCCETTI Armand <armand.puccetti@xxxxxx>
Date: Wed, 03 Jan 2007 14:58:55 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 03 Jan 2007 04:56:50 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1C13223.7011%keir@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C1C13223.7011%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.8 (X11/20061115)
The function vprintk is concerned, as the trace contains:

ffffffff80129fb0 <vprintk>:
ffffffff80129fb0:    55                       push   %rbp
ffffffff80129fb1:    48 89 e5                 mov    %rsp,%rbp
ffffffff80129fb4:    41 57                    push   %r15
ffffffff80129fb6:    41 56                    push   %r14
ffffffff80129fb8:    41 55                    push   %r13
ffffffff80129fba:    41 54                    push   %r12
ffffffff80129fbc:    53                       push   %rbx
ffffffff80129fbd:    48 83 ec 58              sub    $0x58,%rsp
ffffffff80129fc1: 44 8b 1d 38 c1 51 00 mov 5357880(%rip),%r11d # ffffffff80646100 <oops_in_progress> ffffffff80129fc8: 64 48 8b 04 25 28 00 mov %fs:0x28,%rax ffffffff80129fcf: 00 00 ffffffff80129fd1: 48 89 45 c8 mov %rax,0xffffffffffffffc8(%rbp)
ffffffff80129fd5:    31 c0                    xor    %eax,%eax
ffffffff80129fd7:    45 85 db                 test   %r11d,%r11d
ffffffff80129fda: 74 68 je ffffffff8012a044 <vprintk+0x94> ffffffff80129fdc: 8b 05 ea 8c 3e 00 mov 4099306(%rip),%eax # ffffffff80512ccc <printk_cpu>
ffffffff80129fe2:    85 c0                    test   %eax,%eax
ffffffff80129fe4: 75 5e jne ffffffff8012a044 <vprintk+0x94> ffffffff80129fe6: 48 8b 05 13 e2 4a 00 mov 4907539(%rip),%rax # ffffffff805d8200 <jiffies> ffffffff80129fed: 48 8b 15 2c c5 51 00 mov 5358892(%rip),%rdx # ffffffff80646520 <oops_timestamp.17285>

Now, that should correspond to source code:

asmlinkage int vprintk(const char *fmt, va_list args)
{
   unsigned long flags;
   int printed_len;
   char *p;
   static char printk_buf[1024];
   static int log_level_unknown = 1;

   preempt_disable();
   if (unlikely(oops_in_progress) && printk_cpu == smp_processor_id())
       /* If a crash is occurring during printk() on this CPU,
        * make sure we can't deadlock */
       zap_locks();

which isn't so much clearer to me...

Keir Fraser a écrit :

On 3/1/07 11:04, "PUCCETTI Armand" <armand.puccetti@xxxxxx> wrote:

I removed both options but exactly the same trace comes out.
Are there any other options I should add?

Armand

You could add 'debug' as a boot parameter, but it looks like you are
crashing too early to get any output. Have you tried disassembling the Linux
kernel image (objdump -d vmlinux) and see what function contains address
ffffffff80129fc8 (the crashing RIP value)?

 -- Keir




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