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] [Fwd: RE: [Fwd: x86_64 - Kernel BUG at hypervisor:53]]

To: David F Barrera <dfbp@xxxxxxxxxx>
Subject: Re: [Xen-devel] [Fwd: RE: [Fwd: x86_64 - Kernel BUG at hypervisor:53]]
From: "Scott Parish" <srparish@xxxxxxxxxx>
Date: Wed, 8 Jun 2005 18:53:55 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 08 Jun 2005 19:36:28 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1118257993.5393.10.camel@xxxxxxxxxxxxxxxxxxxxxxx>
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: <1118257993.5393.10.camel@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
DomUs aren't known to work yet, we're getting there...

sRp

On Wed, Jun 08, 2005 at 02:13:13PM -0500, David F Barrera wrote:

> Jun,
> 
> OK. I am able to boot Dom0 on x86_64 SLES 9 now with the patch you
> suggested (Scott's). I haven't tried booting a DomU yet..
> 
> David
> 
> -------- Forwarded Message --------
> From: David F Barrera <dfbp@xxxxxxxxxx>
> To: Nakajima, Jun <jun.nakajima@xxxxxxxxx>
> Subject: RE: [Fwd: x86_64 - Kernel BUG at hypervisor:53]
> Date: Wed, 08 Jun 2005 13:20:46 -0500
> Jun,
> 
> It went further this time, past the previous failure. I need to figure
> out what is going on now. Thx for the suggestion.
> 
> This is the error I'm getting now (I did build an initrd for the xen0
> kernel).
> 
> EXT3-fs: mounted filesystem with ordered data mode.
> VFS: Mounted root (ext3 filesystem) readonly.
> Warning: unable to open an initial console.
> Kernel panic - not syncing: No init found.  Try passing init= option to
> kernel.
> 
> On Wed, 2005-06-08 at 09:22 -0700, Nakajima, Jun wrote: 
> > David F Barrera wrote:
> > > Jun,
> > > 
> > > This is a more complete log than the previous on. Both the tg3 AND the
> > > pcnet32 drivers show up. I guess the serial port munges data
> > > sometimes.
> > David,
> > 
> > Can you try the one Scott did? See attached. I suspect it's NX bit or
> > the physical frame is beyond dom0, and Xen does not allow dom0 to map.
> > 
> > Jun
> >  
> > > 
> > > David
> > > 
> > > Intel(R) PRO/1000 Network Driver - version 5.6.10.1-k2
> > > Copyright (c) 1999-2004 Intel Corporation.
> > > pcnet32.c:v1.30i 06.28.2004 tsbogend@xxxxxxxxxxxxxxxx
> > > e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
> > > e100: Copyright(c) 1999-2004 Intel Corporation
> > > tg3.c:v3.23 (February 15, 2005)
> > > ----------- [cut here ] --------- [please bite here ] ---------
> > > Kernel BUG at hypervisor:53
> > > invalid operand: 0000 [1]
> > > CPU 0
> > > Modules linked in:
> > > Pid: 1, comm: swapper Not tainted 2.6.11.11-xen0
> > > RIP: e030:[<ffffffff80118db1>] <ffffffff80118db1>{xen_l1_entry_update
> > > +113}
> > > RSP: e02b:ffff8800017c3bf8  EFLAGS: 00010282
> > > RAX: 00000000ffffffea RBX: ffff88001f189000 RCX: ffffffff80118dad
> > > RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8800017c3bf8
> > > RBP: 0000000000000000 R08: 0000000000007ff0 R09: ffff8800017c3c48
> > > R10: 0000000000007ff0 R11: 0000000000000206 R12: ffff88001f189000
> > > R13: 003fffe20027c624 R14: 000000000007c624 R15: 000000000001f189
> > > FS:  0000000000000000(0000) GS:ffffffff804d8200(0000)
> > > knlGS:0000000000000000
> > > CS:  e03L*\uffff\uffff\uffff\u0745\uffff\uffff\uffff\uffff\uffff\uffff
> > >
> > \uffff\u0461\u0255\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff
> > > \uffff\uffff\u0445\u036d\uffff\uffff\uffff\uffff\uffffM\u0445\uffff
> > >
> > \uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff
> > >
> > \uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff
> > > \uffff\uffff0803248f2
> > >        ffff8800017c3cc0 0000000000000400
> > > Call Trace:<ffffffff80113de2>{dma_alloc_coherent+1074}
> > > <ffffffff8052aa5f>{tg3_init_one+6783}
> > >        <ffffffff8020a1a1>{pci_device_probe+113}
> > > <ffffffff80242cdd>{driver_probe_device+77}
> > >        <ffffffff80242fd6>{driver_attach+70}
> > > <ffffffff802430b8>{bus_add_driver+152}
> > >        <ffffffff80243802>{driver_register+50}
> > > <ffffffff80526d40>{pcnet32_init_module+96}
> > >        <fffff
> > > 
> > > 
> > > -------- Forwarded Message --------
> > > From: David F Barrera <dfbp@xxxxxxxxxx>
> > > To: jun.nakajima@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
> > > Subject: x86_64 - Kernel BUG at hypervisor:53
> > > Date: Wed, 08 Jun 2005 09:04:07 -0500
> > > Jun,
> > > 
> > > Notice the difference: no tg3 but now pcnet32 shows up on the dump.
> > > Same 
> > > machine as before, though.
> > > 
> > > David
> > > 
> > > This is the log from todays boot attempt:
> > > 
> > >  __  __            _____  ___         _                _
> > >  \ \/ /___ _ __   |___ / / _ \     __| | _____   _____| |
> > >   \  // _ \ '_ \    |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
> > >   /  \  __/ | | |  ___) | |_| |__| (_| |  __/\ V /  __/ |
> > >  /_/\_\___|_| |_| |____(_)___/    \__,_|\___| \_/ \___|_|
> > > 
> > >  http://www.cl.cam.ac.uk/netos/xen
> > >  University of Cambridge Computer Laboratory
> > > 
> > >  Xen version 3.0-devel (root@xxxxxxxxxxxxxxxxxx) (gcc version 3.3.3
> > > (SuSE 
> > > Linux)) Wed Jun  8 02:46:34 CDT 2005
> > >  Latest ChangeSet: information unavailable
> > > 
> > > (XEN) Physical RAM map:
> > > (XEN)  0000000000000000 - 000000000009d400 (usable)
> > > (XEN)  000000000009d400 - 00000000000a0000 (reserved)
> > > (XEN)  00000000000e0000 - 0000000000100000 (reserved)
> > > (XEN)  0000000000100000 - 000000003ffbe680 (usable)
> > > (XEN)  000000003ffbe680 - 000000003ffd0000 (ACPI data)
> > > (XEN)  000000003ffd0000 -
> > >
> > 00000000\uffffM\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\u0465\uf
> > fff\uffff\uffffXEN)
> > >     Virtual Wire compatibility mode.
> > > (XEN) OEM ID: IBM ENSW Product ID: BLADER SMP   APIC at: 0xFEE00000
> > > (XEN) Processor #0 15:4 APIC version 20
> > > (XEN) Processor #6 15:4 APIC version 20
> > > (XEN) I/O APIC #14 Version 32 at 0xFEC00000.
> > > (XEN) I/O APIC #13 Version 32 at 0xFEC10000.
> > > (XEN) I/O APIC #12 Version 32 at 0xFEC81000.
> > > (XEN) I/O APIC #11 Version 32 at 0xFEC81400.
> > > (XEN) Enabling APIC mode:  Flat.  Using 4 I/O APICs
> > > (XEN) Processors: 2
> > > (XEN) Initializing CPU#0
> > > (XEN)\uffff-XEN) CPU: Physical Processor ID: 3
> > > (XEN) CPU1: Intel(R) Xeon(TM) CPU 3.60GHz stepping 01
> > > (XEN) Total of 2 processors activated.
> > > (XEN) WARNING: 1 siblings found for CPU0, should be 2
> > > (XEN) WARNING: 1 siblings found for CPU1, should be 2
> > > (XEN) ENABLING IO-APIC IRQs
> > > (XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
> > > (XEN) checking TSC synchronization across 2 CPUs: passed.
> > > (XEN) Time init:
> > > (XEN) .... cpu_freq:    00000000:D69873E0
> > > (XEN) .... scale:       00000001:1C6B6645
> > >
> > AU\uffffa9\uffff\uffff\uffff\uffff\uffffa91=%9=5%9a9a\uffff\uffff1\uffff
> > \uffff\uffff\uffff\uffff\u0259\uffff\u0579\uffffUMQ}=M\uffff\uffff\uffff
> > \uffff\uffffUMQ}YIa9}YIY%IQ}
> > >  M155=IeII959Qa9\uffff\uffff\uffff\uffff\uffff\uffff\uffff00020000000
> > > (62464 pages to be allocated)
> > > (XEN) VIRTUAL MEMORY ARRANGEMENT:
> > > (XEN)  Loaded kernel: ffffffff80100000->ffffffff80576086
> > > (XEN)  Init. ramdisk: ffffffff80577000->ffffffff80577000
> > > (XEN)  Phys-Mach map: ffffffff80577000->ffffffff805f4000
> > > (XEN)  Page tables:   ffffffff805f4000->ffffffff805fb000
> > > (XEN)  Start info:    ffffffff805fb000->f 65536 (order: 7, 524288
> > > bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> > > Memory: 493568k/512000k available (2610k kernel code, 7872k reserved,
> > > 949k data, 428k init)
> > > Mount-cache hash table entries: 256 (order: 0, 4096 bytes)
> > > CPU: Trace cache: 12K uops, L1 D cache: 16K
> > > CPU: L2 cache: 1024K
> > > CPU:                   Intel(R) Xeon(TM) CPU 3.60GHz stepping 01
> > > NET: Registered protocol family 16
> > > PCI: Using configuration type 1
> > > ACPI: Subsystem revision 20050211
> > > ACPI: Interprfloppy0: no floppy controllers found
> > > RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> > > loop: loaded (max 8 devices)
> > > HP CISS Driver (v 2.6.4)
> > > Intel(R) PRO/1000 Network Driver - version 5.6.10.1-k2
> > > Copyright (c) 1999-2004 Intel Corporation.
> > > pcnet32.c:v1.30i 06.28.2004 tsbogend@xxxxxxxxxxxxxxxx
> > > e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
> > > e100: Copyright(c) 1999-2004 Intel Corporation
> > > tg3.c:v3.23 (February 15, 2005)
> > > ----------- [cut here ] --------- [please bite here ] ---------
> > > Kernel BUG at hypervisor:53
> > > invalid operand: 0000 [1]
> > > CPU 0
> > > Modules linked in:
> > > Pid: 1, comm: swapper Not tainted 2.6.11.11-xen0
> > > RIP: e030:[<ffffffff80118db1>]
> > > <ffffffff80118db1>{xen_l1_entry_update+113} 
> > > RSP: e02b:ffff8800017c3bf8  EFLAGS: 00010282
> > > RAX: 00000000ffffffea RBX: ffff88001f189000 RCX: ffffffff80118dad
> > > RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8800017c3bf8
> > > RBP: 0000000000000000 R08: 0000000000007ff0 R09: ffff8800017c3c48
> > > R10: 0000000000007ff0 R11: 0000000000000206 R12: ffff88001f189000
> > > R13: 003fffe20027c624 R14: 000000000007c624 R15: 000000000001f189
> > > FS:  0000000000000000(0000) GS:ffffffff804d8200(0000)
> > > knlGS:0000000000000000 
> > > CS:  e033 DS: 0000 ES:20a1a1>{pci_device_probe+113}
> > > <ffffffff80242cdd>{driver_probe_device+77}
> > >        <ffffffff80242fd6>{driver_attach+70}
> > >        <ffffffff802430b8>{bus_add_driver+152}
> > > <ffffffff80243802>{driver_register+50}
> > >        <ffffffff80526d40>{pcnet32_init_module+96}
> > >        <ffffffff8020a249>{pci_register_driver+73}
> > >        <ffffffff801090ea>{init+170} <ffffffff8010deeb>{child_rip+8}
> > > <ffffffff8028e441>{kcons_write_dom0+33} <ffffffff80109040>{init+0}
> > > <ffffffff8010dee3>{child_rip+0}  
> > > 
> > > 
> > > Code: 0f
> > > 
> > > 
> > > -------- Forwarded Message --------
> > > From: David F Barrera <dfbp@xxxxxxxxxx>
> > > To: Nakajima, Jun <jun.nakajima@xxxxxxxxx>
> > > Subject: RE: [Xen-devel] Latest bk can NOT compile on x86_64
> > > Date: Thu, 02 Jun 2005 11:01:41 -0500
> > > On Thu, 2005-06-02 at 08:04 -0700, Nakajima, Jun wrote:
> > >> David,
> > >> 
> > >> Does your machine have Broadcom Tigon3?
> > > Yes, it does. I see the 'tg3' module loaded.
> > >> 
> > >> Jun
> > >> ---
> > >> Intel Open Source Technology Center
> > >> 
> > >> -----Original Message-----
> > >> From: David F Barrera [mailto:dfbp@xxxxxxxxxx]
> > >> Sent: Thursday, June 02, 2005 7:53 AM
> > >> To: Nakajima, Jun
> > >> Subject: RE: [Xen-devel] Latest bk can NOT compile on x86_64
> > >> 
> > >> On Wed, 2005-06-01 at 11:11 -0700, Nakajima, Jun wrote:
> > >>> David F Barrera wrote:
> > >>>> On Wed, 2005-06-01 at 09:26 -0700, Nakajima, Jun wrote:
> > >>>>> David F Barrera wrote:
> > >>>>>> On Wed, 2005-06-01 at 08:21 -0700, Nakajima, Jun wrote:
> > >>>>>>> David, Hi,
> > >>>>>>>> Jun,
> > >>>>>>>> 
> > >>>>>>>> I got your message this morning, so I did not get a chance to
> > >>>>>>>> give you the info you requested. This morning, I am seeing a
> > >>>>>>>> different error on x86_63 (refer to my earlier post to the
> > >>>>>>>> xen-developer list). 
> > >>>>>>>> 
> > >>>>>>> Yes, I saw it. I think the PAE patch caused some regression.
> > >>>>>>> BTW, did x86-64 xenlinux ever boot on the machine?
> > >>>>>> 
> > >>>>>> Jun, please excuse my ignorance, but how do I boot xenlinux?
> > >>>>>>> 
> > >>>>> 
> > >>>>> I mean dom0 xenlinux, i.e. vmlinuz-2.6.11-xen0. Is this the first
> > >>>>> for you try x86-64 xenlinux on the machine? How much memory do
> > >>>>> you have on the machine?
> > >>>> I've never been able to boot Dom0 on an x86_64 machine. The machine
> > >>>> has 1GB of memory.
> > >>>>> 
> > >>> Are you using loadable drivers? Can you remove the initrd from the
> > >>> boot file (making the things static)?
> > >> 
> > >> Jun, I tried it and it made no difference.
> > >> I am still  seeing the same error with the latest BK build. Here's
> > >> the log: 
> > >> 
> > >> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024
> > >> blocksize loop: loaded (max 8 devices) HP CISS Driver (v 2.6.4)
> > >> Intel(R) PRO/1000 Network Driver - version 5.6.10.1-k2
> > >> Copyright (c) 1999-2004 Intel Corporation.
> > >> pcnet32.c:v1.30i 06.28.2004 tsbogend@xxxxxxxxxxxxxxxx
> > >> e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
> > >> e100: Copyright(c) 1999-2004 Intel Corporation
> > >> tg3.c:v3.23 (February 15, 2005)
> > >> ACPI: PCI interrupt 0000:05:01.0[A] -> GSI 77 (level, low) -> IRQ 77
> > >> ----------- [cut here ] --------- [please bite here ] ---------
> > >> Kernel BUG at hypervisor:53 invalid operand: 0000 [1]
> > >> CPU 0
> > >> Modules linked in:
> > >> Pid: 1, comm: swapper Not tainted 2.6.11.11-xen0
> > >> RIP: e030:[<ffffffff80118db1>]
> > >> <ffffffff80118db1>{xen_l1_entry_update +113} RSP:
> > >> e02b:ffff880000a05bf8  EFLAGS: 00010282 
> > >> RAX: 00000000ffffffea RBX: ffff88000f9e4000 RCX: ffffffff80118dad
> > >> RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff880000a05bf8
> > >>
> > M\uffffMMA\u027d\uffff\uffff\uffff\uffff\uffff\u0745\uffff\uffff\uffff
> > >>
> > \uffff\uffff\uffff\uffff\u0461\u0255\uffff\uffff\uffff\uffff\uffff\uffff
> > >> \uffff\uffff\uffff\uffff\uffff\u0445\u036d\uffff\uffff\uffff\uffff
> > >> \uffffM\u0445\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff
> > >>
> > \uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff
> > >> \uffff\uffff\uffff\uffff\uffff\uffff24952
> > >>        ffff880000a05cc0 0000000000000400
> > >> Call Trace:<ffffffff80113de2>{dma_alloc_coherent+1074}
> > >> <ffffffff8052aaaf>{tg3_init_one+6783}
> > >>        <ffffffff801221fb>{__do_softirq+107}
> > >> <ffffffff8012229d>{do_softirq+61}
> > >>        <ffffffff8010dcd1>{do_hypervisor_callback+17}
> > >> <ffffffff8020a1a1>{pci_device_probe+113}
> > >>        <ffffffff80242cdd>{driver_probe_device+77}g: Attempted to
> > >> kill init! 
> > >> 
> > >> 
> > >> 
> > >>> 
> > >>> Jun
> > >>> ---
> > >>> Intel Open Source Technology Center
> > 
> > 
> > 
> > Jun
> > ---
> > Intel Open Source Technology Center
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 

-- 
Scott Parish
Signed-off-by: srparish@xxxxxxxxxx

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

<Prev in Thread] Current Thread [Next in Thread>