summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2011-08-15 23:13:21 +0200
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2011-08-15 23:13:21 +0200
commit999a41208e5368fe3ee6c867978f18af708ca034 (patch)
tree7f1a816c33089487a7c4f47eb10e0664d53707ee
parent483c38fc1c9e83f186ab4bc57ac69f332ce002bd (diff)
Virtualbox issue
-rw-r--r--open_issues/virtualbox.mdwn61
1 files changed, 61 insertions, 0 deletions
diff --git a/open_issues/virtualbox.mdwn b/open_issues/virtualbox.mdwn
new file mode 100644
index 00000000..4d4db8d8
--- /dev/null
+++ b/open_issues/virtualbox.mdwn
@@ -0,0 +1,61 @@
+[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]]
+
+[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
+id="license" text="Permission is granted to copy, distribute and/or modify this
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+[[!meta title="xattr: extended attributes"]]
+
+[[!tag open_issue_gnumach]]
+
+Running GNU Mach in VirtualBox crashes during initialization.
+
+IRC, freenode, #hurd, 2011-08-15
+
+ <BlueT_> HowTo Reproduce: 1) Use `reboot` to reboot the system. 2) Once you see the Grub menu, turn off the debian hurd box. 3) Let the box boot normally, and wait for the error/crash/reboot. 4) The error/crash will happen twice and it's reboot automatically. The 3rd boot will success.
+
+ <BlueT_> root@dhurd:/boot# addr2line -f -e gnumach-1.3.99-486-dbg-copy 0x106c93 0x1556a5 0x152c54
+ <BlueT_> copyoutmsg
+ <BlueT_> /home/buildd/build/chroot-sid/home/buildd/byhand/gnumach/build-dbg/../i386/i386/locore.S:1289
+ <BlueT_> exec_load
+ <BlueT_> /home/buildd/build/chroot-sid/home/buildd/byhand/gnumach/build-dbg/../kern/elf-load.c:80
+ <BlueT_> user_bootstrap
+ <BlueT_> /home/buildd/build/chroot-sid/home/buildd/byhand/gnumach/build-dbg/../kern/bootstrap.c:756
+
+ i386/i386/locore.S:1289 is
+
+ movl $USER_DS,%eax /* use user data segment for accesses */
+=> mov %ax,%es
+
+ <youpi> oh, wait, it's not even the data access which poses problem
+ <youpi> but the use of $USER_DS
+ <youpi> ew
+ <youpi> looks like a gdt initialization emulation issue in virtualbox...
+
+
+ <BlueT_> just found that at the second crash, the address is different
+ <BlueT_> 2nd time:
+ <BlueT_> addr2line -f -e gnumach-1.3.99-486-dbg-copy 0x1068bd 0x152c74
+ <BlueT_> _kret_popl_es
+ <BlueT_> /home/buildd/build/chroot-sid/home/buildd/byhand/gnumach/build-dbg/../i386/i386/locore.S:527
+ <BlueT_> user_bootstrap
+ <BlueT_> /home/buildd/build/chroot-sid/home/buildd/byhand/gnumach/build-dbg/../kern/bootstrap.c:765
+
+ i386/i386/locore.S:527 is:
+
+_return_from_kernel:
+_kret_popl_gs:
+ popl %gs /* restore segment registers */
+_kret_popl_fs:
+ popl %fs
+_kret_popl_es:
+=> popl %es
+_kret_popl_ds:
+
+ <youpi> looks again like a $USER_DS issue
+ <youpi> what's interesting is that that one means that $USER_DS did load in %es fine at least once
+ <youpi> and it's the reload that fails