Xen project Mailing List

Thanks a lot guys...

Patch provided by Jan simply worked... :)
and I need to be more careful to give attention to the wiki.... the kernel tree indeed is not maintained.
should have used XCI (Xen Client Initiative) Linux 2.6.27 Xen kernel tree or others

Best Regards,
Muhammad Atif

From: Pasi Kärkkäinen <pasik@xxxxxx>
To: Jan Beulich <JBeulich@xxxxxxxxxx>
Cc: Muhammad Atif <m_atif_s@xxxxxxxxx>; xen-devel@xxxxxxxxxxxxxxxxxxx
Sent: Monday, August 24, 2009 9:48:08 PM
Subject: Re: [Xen-devel] Xenoprofile on 2.6.27.hg xen dom0 kernel - cannot shotdown

On Mon, Aug 24, 2009 at 12:35:20PM +0100, Jan Beulich wrote:
> This is the result of the tree you're using not really being maintained - the
> bug you describe has long been fixed, but as you can see, the tree saw
> just a single update over its whole life time.
>

Yep, see here for more information:
http://wiki.xensource.com/xenwiki/XenDom0Kernels

-- Pasi

>
> >>> Muhammad Atif <m_atif_s@xxxxxxxxx> 24.08.09 11:50 >>>
> Hi
> I tried using Xen 3.3 on Sun Ultra 45 machine running a Intel Core 2 Q6600 (quard core). I never got 2.6.18 kernel (dom0) going on that machine so tried 2.6.27-xen.hg kernel which worked.
> When I tried profiling (passive profiling) I got an error about the code 1....... patched the 2.6.27-xen.hg kernel using the patch as suggested by [PATCH] Oprofile patch for 2.6.27 tree. Fix collision between Xen and Cell processor escape codes - http://markmail.org/thread/mmc532fxxt733kgi
>
> xenoprofile works with this patch and I am able to do profiling and see results. But as soon as i try to shutdown profile using opcontrol --shutdown, my kernel gives the error pasted at the end of the message.
>
> After this, my system does not respond and does not even reboot (unless i do it manually).
> Any ideas? Please suggest if I need to provide more information.
>
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> [ 3067.492083] kernel BUG at /usr/src/linux-2.6.27-xen.hg/drivers/xen/core/evtchn.c:204!
> [ 3067.492134] invalid opcode: 0000 [1] SMP
> [ 3067.492182] last sysfs file: /sys/devices/xen-backend/vbd-1-2050/statistics/wr_sect
> [ 3067.492230] CPU 2
> [ 3067.492257] Modules linked in: oprofile(N) xt_physdev(N) bridge(N) stp(N) ipv6(N) nfs(N) lockd(N) nfs_acl(N) sunrpc(N) iptable_filter(N) ip_tables(N) x_tables(N) ac(N) sbp2(N) parport_pc(N) lp(N) parport(N) loop(N) psmouse(N) tpm_infineon(N) snd_hda_intel(N) tpm(N) serio_raw(N) pcspkr(N) snd_pcm(N) tpm_bios(N) snd_timer(N) snd(N) soundcore(N) shpchp(N) button(N) evdev(N) pci_hotplug(N) snd_page_alloc(N) iTCO_wdt(N) ext3(N) jbd(N) mbcache(N) sg(N) sd_mod(N) usbhid(N) ide_pci_generic(N) ide_core(N) ata_generic(N) hid(N) ff_memless(N) ata_piix(N) libata(N) ohci1394(N) scsi_mod(N) ieee1394(N) dock(N) uhci_hcd(N) ehci_hcd(N) e1000e(N) thermal(N) processor(N) fan(N) thermal_sys(N) fuse(N)
> [ 3067.492732] Supported: No
> [ 3067.492757] Pid: 4367, comm: oprofiled Tainted: G 2.6.27.5 #1
> [ 3067.492789] RIP: e030:[<ffffffff80391be5>] [<ffffffff80391be5>] bind_evtchn_to_cpu+0x1d/0xa7
> [ 3067.492843] RSP: e02b:ffff8800cd19bdc0 EFLAGS: 00010246
> [ 3067.492872] RAX: 0000000000000000 RBX: 000000000000002b RCX: ffffffff80598a00
> [ 3067.492905] RDX: 000000000000050b RSI: 0000000000000000 RDI: 000000000000002b
> [ 3067.492938] RBP: 0000000000000000 R08: 0000000000000020 R09: ffffffff806711e8
> [ 3067.492970] R10: 0000000000000002 R11: 000000000000000c R12: 0000000000000000
> [ 3067.493003] R13: ffffffffa0349a40 R14: 000000000000050b R15: ffff8800cd027090
> [ 3067.493037] FS: 00007f2a2c0456e0(0000) GS:ffff880001a9b540(0000) knlGS:0000000000000000
> [ 3067.493087] CS: e033 DS: 0000 ES: 0000
> [ 3067.493114] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ 3067.493147] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [ 3067.493179] Process oprofiled (pid: 4367, threadinfo ffff8800cd19a000, task ffff8800ec4fb3d0)
> [ 3067.493228] Stack: ffffffff80392f98 000000000000002b ffff8800cd13a6b0 0000000000000000
> [ 3067.493295] 0000000000000000 ffff8800e99c0910 ffff8800e9bb22f0 ffff8800ebcf00c0
> [ 3067.493357] ffffffffa0345284 ffff8800cd027090 ffff8800ecb9b600 ffff8800ecb9b600
> [ 3067.493400] Call Trace:
> [ 3067.493445] [<ffffffff80392f98>] unbind_from_per_cpu_irq+0x1ab/0x1ff
> [ 3067.493481] [<ffffffffa0345284>] unbind_virq+0x26/0x4a [oprofile]
> [ 3067.493516] [<ffffffffa0345312>] xenoprof_shutdown+0x6a/0xae [oprofile]
> [ 3067.493551] [<ffffffffa034310b>] oprofile_shutdown+0x35/0x57 [oprofile]
> [ 3067.493586] [<ffffffffa0344072>] event_buffer_release+0xe/0x3b [oprofile]
> [ 3067.493620] [<ffffffff802963a5>] __fput+0xa1/0x165
> [ 3067.493649] [<ffffffff802937cc>] filp_close+0x5b/0x62
> [ 3067.493679] [<ffffffff80231baf>] put_files_struct+0x65/0xc4
> [ 3067.493710] [<ffffffff802336e9>] do_exit+0x25b/0x87a
> [ 3067.493739] [<ffffffff80233da7>] do_group_exit+0x9f/0xcb
> [ 3067.493769] [<ffffffff8020a838>] system_call_fastpath+0x16/0x1b
> [ 3067.493801] [<ffffffff8020a7d0>] system_call+0x0/0x52
> [ 3067.493829]
> [ 3067.493851]
> [ 3067.493873] Code: 48 c7 c7 60 d1 66 80 41 58 e9 c8 1d f9 ff 89 f8 8b 14 85 a0 b2 54 80 48 8b 05 88 c1 19 00 0f a3 b8 00 0a 00 00 19 c0 85 c0 75 04 <0f> 0b eb fe 83 fa ff 74 48 48 63 ca 48 c1 e1 07 f6 81 b2 64 56
> [ 3067.494219] RIP [<ffffffff80391be5>] bind_evtchn_to_cpu+0x1d/0xa7
> [ 3067.494253] RSP <ffff8800cd19bdc0>
> [ 3067.494832] ---[ end trace fcf599f1222809c1 ]---
> [ 3067.494927] Fixing recursive fault but reboot is needed!
>
>
> Best Regards,
> Muhammad Atif
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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

Re: [Xen-devel] Xenoprofile on 2.6.27.hg xen dom0 kernel - cannot shotdown [solved]