Cannot test any linux-image-2.6.27-* kernel, since there isn't any for
xen...

That seems to be an known issue: 
https://answers.launchpad.net/ubuntu/+source/linux/+question/42448

Nevertheless I also tried to recompile the hardy kernel from git.
It doesn't work with any xen kernel running. In all my tests the system kind of 
crashes with the following error message. Somtimes the system is still able to 
reboot, somtimes not.

Aug 24 20:20:41 Xen kernel: [  896.629486] invalid opcode: 0000 [#1] SMP
Aug 24 20:20:41 Xen kernel: [  896.629534] Modules linked in: bridge 
iptable_filter ip_tables x_tables ipv6 parport_pc lp parport loop af_packet 
button evdev i82875p_edac edac_core 8250_pnp 8250 serial_c
Aug 24 20:20:41 Xen kernel: [  896.630264]
Aug 24 20:20:41 Xen kernel: [  896.630286] Pid: 31232, comm: cp Not tainted 
(2.6.24-19-xen #1)
Aug 24 20:20:41 Xen kernel: [  896.630311] EIP: 0061:[<c1df1a49>] EFLAGS: 
00010a86 CPU: 1
Aug 24 20:20:41 Xen kernel: [  896.630338] EIP is at 0xc1df1a49
Aug 24 20:20:41 Xen kernel: [  896.630360] EAX: c1ee4220 EBX: c1ee8420 ECX: 
00000000 EDX: 00000000
Aug 24 20:20:41 Xen kernel: [  896.630386] ESI: 00000001 EDI: 40040000 EBP: 
00000000 ESP: e4d93e94
Aug 24 20:20:41 Xen kernel: [  896.630410]  DS: 007b ES: 007b FS: 00d8 GS: 0000 
SS: 0069
Aug 24 20:20:41 Xen kernel: [  896.630435] Process cp (pid: 31232, ti=e4d92000 
task=ed504cb0 task.ti=e4d92000)
Aug 24 20:20:41 Xen kernel: [  896.630461] Stack: c01623a5 e6a2ed40 c03fd800 
e4d93f00 00000001 0000000b e4d93ed0 c0162456
Aug 24 20:20:41 Xen kernel: [  896.630563]        c1ee4220 c177d410 c03fd800 
0000000e c0165997 0000000e 00000000 0000000b
Aug 24 20:20:41 Xen kernel: [  896.630664]        00000000 c1abeb40 c1abeb20 
c1abeb80 c1abeba0 c1abeb60 c1abfc00 c1abfc40
Aug 24 20:20:41 Xen kernel: [  896.630765] Call Trace:
Aug 24 20:20:41 Xen kernel: [  896.630803]  [free_hot_cold_page+0x195/0x220] 
free_hot_cold_page+0x195/0x220
Aug 24 20:20:41 Xen kernel: [  896.630852]  [__pagevec_free+0x26/0x30] 
__pagevec_free+0x26/0x30
Aug 24 20:20:42 Xen kernel: [  896.630893]  [release_pages+0x137/0x160] 
release_pages+0x137/0x160
Aug 24 20:20:42 Xen kernel: [  896.630966]  
[free_pages_and_swap_cache+0x74/0xa0] free_pages_and_swap_cache+0x74/0xa0
Aug 24 20:20:42 Xen kernel: [  896.631012]  [exit_mmap+0xe7/0x100] 
exit_mmap+0xe7/0x100
Aug 24 20:20:42 Xen kernel: [  896.631060]  [mmput+0x23/0x80] mmput+0x23/0x80
Aug 24 20:20:42 Xen kernel: [  896.631096]  [do_exit+0x165/0x8b0] 
do_exit+0x165/0x8b0
Aug 24 20:20:42 Xen kernel: [  896.631146]  [filp_close+0x49/0x80] 
filp_close+0x49/0x80
Aug 24 20:20:42 Xen kernel: [  896.631188]  [do_group_exit+0x2a/0xa0] 
do_group_exit+0x2a/0xa0
Aug 24 20:20:42 Xen kernel: [  896.631227]  [syscall_call+0x7/0x0b] 
syscall_call+0x7/0xb
Aug 24 20:20:42 Xen kernel: [  896.631292]  =======================
Aug 24 20:20:42 Xen kernel: [  896.631314] Code: 15 e5 80 00 00 40 01 00 00 00 
ff ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00 c0 3c 40 ed 00 10 15 e5 00 00 
00 40 00 00 00 00 ff <ff> ff ff 34 42 ee c1 00
Aug 24 20:20:42 Xen kernel: [  896.631837] EIP: [<c1df1a49>] 0xc1df1a49 SS:ESP 
0069:e4d93e94
Aug 24 20:20:42 Xen kernel: [  896.632703] ---[ end trace 93c63cdaf03f11e8 ]---
Aug 24 20:20:42 Xen kernel: [  896.632902] Fixing recursive fault but reboot is 
needed!

If I'm using a non xen kernel it works fine. (Of course I'm compiling
the kernel with /lib/tls out of the way.)

On another track I tried to read the vDSO and look for the nosegneg flag. (I've 
attached the vDSO from  running 2.6.24-21-xen)
Unfortunatelly I was unable to locate the flag in the file. But It looks like 
the dom0 isn't using virtual system calls at all:

[EMAIL PROTECTED]:~$ objdump -T dso-xen

dso-xen:     file format elf32-i386

DYNAMIC SYMBOL TABLE:
f57fe400 g    DF .text  00000003  LINUX_2.5   __kernel_vsyscall
00000000 g    DO *ABS*  00000000  LINUX_2.5   LINUX_2.5
f57fe440 g    DF .text  00000007  LINUX_2.5   __kernel_rt_sigreturn
f57fe420 g    DF .text  00000008  LINUX_2.5   __kernel_sigreturn

[EMAIL PROTECTED]:~$ objdump -d --start-address=0xf57fe400 --stop-
address=0xf57fe414 dso-xen

dso-xen:     file format elf32-i386

Disassembly of section .text:

f57fe400 <__kernel_vsyscall>:
f57fe400:       cd 80                   int    $0x80
f57fe402:       c3                      ret
f57fe403:       90                      nop
f57fe404:       90                      nop
f57fe405:       90                      nop
f57fe406:       90                      nop
f57fe407:       90                      nop
f57fe408:       90                      nop
f57fe409:       90                      nop
f57fe40a:       90                      nop
f57fe40b:       90                      nop
f57fe40c:       90                      nop
f57fe40d:       90                      nop
f57fe40e:       90                      nop
f57fe40f:       90                      nop
f57fe410:       90                      nop
f57fe411:       90                      nop
f57fe412:       90                      nop
f57fe413:       90                      nop

This is according to http://www.trilithium.com/johan/2005/08/linux-gate/ the 
old and slow interrupt method.
Nevertheless that doesn't seems to be related to the nosegneg flag problem, its 
the same on my working Ubuntu Gutsy System running 2.6.22.

I hope that someone with insight into the linux kernel can sort things
out.


** Attachment added: "dso-xen"
   http://launchpadlibrarian.net/17172694/dso-xen

-- 
Xen - nosegneg broken on hardy
https://bugs.launchpad.net/bugs/260825
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to