Re: [Xen-devel] unstable tip not booting on x86-64 with 'domain_crash_sync'

[Muli Ben-Yehuda <muli@xxxxxxxxxx>]

On Sat, Sep 09, 2006 at 10:58:40AM +0300, Muli Ben-Yehuda wrote:
> On Thu, Sep 07, 2006 at 11:01:46PM +0300, Muli Ben-Yehuda wrote:
> 
> > > Binary chop on changeset revisions isn't a bad idea. I would think that 
> > > such
> > > a blatant failure mode couldn't have crept in all that long ago.
> > 
> > Yep, I'm working on it. Might take a while to narrow it down though,
> > between me and the machine is a very slow VPN connection and a
> > weekend... I'll keep you updated.
> 
> Ok, this changeset:
> 
> changeset:   11223:a4550b7488400c44a9f27c92115c8e364493837a
> user:        Ian Campbell <ian.campbell@xxxxxxxxxxxxx>
> date:        Tue Aug 22 14:20:43 2006 +0100
> files:       linux-2.6-xen-sparse/arch/i386/kernel/vmlinux.lds.S
> patches/linux-2.6.16.13/series
> patches/linux-2.6.16.13/x86-put-note-sections-into-a-pt_note-segment-in-vmlinux.patch
> patches/linux-2.6.16.13/x86_64-put-note-sections-into-a-pt_note-segment-in-vmlinux.patch
> description:
> [LINUX] Support creating ELF note segments in the kernel ELF image.
> 
> dies, while the previous one
> (11222:cd4e7ace4e58d9e35c08ccaa4677c6b6d0cf137b) works.

Reverting the changes to x86-64's vmlinux.lds.S first introduced in
this patch is enough to get my box booting again.
- is this change necessary or can it be reverted for the time being?
- how to debug what's causing this? linker scripts aren't exactly my
  cup of tea
- I'm going to try -mm now to see if this affects mainline as well.

Cheers,
Muli

diff -r 1de184deaa9c patches/linux-2.6.16.13/series
--- a/patches/linux-2.6.16.13/series    Wed Sep  6 12:16:02 2006
+++ b/patches/linux-2.6.16.13/series    Sat Sep  9 18:19:08 2006
@@ -19,5 +19,4 @@
 xen-hotplug.patch
 xenoprof-generic.patch
 x86-put-note-sections-into-a-pt_note-segment-in-vmlinux.patch
-x86_64-put-note-sections-into-a-pt_note-segment-in-vmlinux.patch
 x86-elfnote-as-preprocessor-macro.patch
diff -r 1de184deaa9c 
patches/linux-2.6.16.13/x86_64-put-note-sections-into-a-pt_note-segment-in-vmlinux.patch
--- 
a/patches/linux-2.6.16.13/x86_64-put-note-sections-into-a-pt_note-segment-in-vmlinux.patch
  Wed Sep  6 12:16:02 2006
+++ /dev/null   Sat Sep  9 18:19:08 2006
@@ -1,60 +0,0 @@
-diff --git a/arch/x86_64/kernel/vmlinux.lds.S 
b/arch/x86_64/kernel/vmlinux.lds.S
-index 7c4de31..ef418b3 100644
---- a/arch/x86_64/kernel/vmlinux.lds.S
-+++ b/arch/x86_64/kernel/vmlinux.lds.S
-@@ -13,6 +13,12 @@ OUTPUT_FORMAT("elf64-x86-64", "elf64-x86
- OUTPUT_ARCH(i386:x86-64)
- ENTRY(phys_startup_64)
- jiffies_64 = jiffies;
-+PHDRS {
-+      text PT_LOAD FLAGS(5);  /* R_E */
-+      data PT_LOAD FLAGS(7);  /* RWE */
-+      user PT_LOAD FLAGS(7);  /* RWE */
-+      note PT_NOTE FLAGS(4);  /* R__ */
-+}
- SECTIONS
- {
-   . = __START_KERNEL;
-@@ -31,7 +37,7 @@ SECTIONS
-       KPROBES_TEXT
-       *(.fixup)
-       *(.gnu.warning)
--      } = 0x9090
-+      } :text = 0x9090
-                               /* out-of-line lock text */
-   .text.lock : AT(ADDR(.text.lock) - LOAD_OFFSET) { *(.text.lock) }
- 
-@@ -57,7 +63,7 @@ #endif
-   .data : AT(ADDR(.data) - LOAD_OFFSET) {
-       *(.data)
-       CONSTRUCTORS
--      }
-+      } :data
- 
-   _edata = .;                 /* End of data section */
- 
-@@ -89,7 +95,7 @@ #define VVIRT_OFFSET (VSYSCALL_ADDR - VS
- #define VVIRT(x) (ADDR(x) - VVIRT_OFFSET)
- 
-   . = VSYSCALL_ADDR;
--  .vsyscall_0 :        AT(VSYSCALL_PHYS_ADDR) { *(.vsyscall_0) }
-+  .vsyscall_0 :        AT(VSYSCALL_PHYS_ADDR) { *(.vsyscall_0) } :user
-   __vsyscall_0 = VSYSCALL_VIRT_ADDR;
- 
-   . = ALIGN(CONFIG_X86_L1_CACHE_BYTES);
-@@ -132,7 +138,7 @@ #undef VVIRT
-   . = ALIGN(8192);            /* init_task */
-   .data.init_task : AT(ADDR(.data.init_task) - LOAD_OFFSET) {
-       *(.data.init_task)
--  }
-+  } :data
- 
-   . = ALIGN(4096);
-   .data.page_aligned : AT(ADDR(.data.page_aligned) - LOAD_OFFSET) {
-@@ -235,4 +241,6 @@ #endif
-   STABS_DEBUG
- 
-   DWARF_DEBUG
-+
-+  NOTES
- }


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