> Could you make sure that you show the cmdline as both Xen _and_ Linux
> see it? I suspect that perhpas the order by which we evaluate the
> CMDLINE may be incorrect.

Jimi,

Let me first say that my analysis is based on our internal version, since
the official version does not boot from local disk by another problem.


Following is the boot log with old XenPPC.

      Welcome to yaboot version 10.1.14-r716.SuSE
      booted from '/ht/[EMAIL PROTECTED],1/[EMAIL PROTECTED]'
      Enter "help" to get some basic usage information
      boot: xen
      Please wait, loading kernel...
      Allocated 00500000 bytes for executable @ 00400000
         Elf32 kernel loaded...
      ---------------------------------------------------
      OF: Xen/PPC version 3.0-unstable ([EMAIL PROTECTED]) (gcc version
4.1.0 (SUSE Linux)) Mon Oct  2 10:06:25 JST 2006
      boot_of_init args: 0x400000 0x0 0x111027c 0x0 0x0
      boot msr: 0x1000000000003000
      boot_of_init: _start 0000000000400100 _end 0000000000725b88 0x0
      boot_of_probemem: memory 0x0000000000000000[0x20000000]
      bootargs = xen -- root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr
      boot_of_module: Dom0 is linked in: 0x44edbc[size 0x29954d]
      mod0: 177 E L F
      boot_of_module: mod[0] @ 0x000000000044edbc[0x6e8309]
      boot_of_module: mod[0].string: root=/dev/hda3 sysrq=1
insmod=sym53c8xx insmod=ipr
      find_space base=0x0000000000725b88  eomem=0x0000000020000000
size=0x00030000  align=0x1000
      creating oft
      pkg_save: saved device tree in 0x3288 bytes
      boot_of_module: mod[1] @ 0x0000000000900000[0x930000]
      pruning `/ht/[EMAIL PROTECTED]/[EMAIL PROTECTED]' from devtree
      pruning `/ht/[EMAIL PROTECTED]/[EMAIL PROTECTED]' from devtree
      boot_of_serial: ISA base: 0xf4000000
      boot_of_serial: ISRC=0x44, but forcing poll mode
      OF: timebase-frequency = 14318278 Hz
      OF: clock-frequency = 2200000 KHz
            :
      zImage starting: loaded at 0x00400000 (sp: 0x01ffff90)
      Allocating 0x7348b8 bytes for kernel ...
      OF version = 'IBM,XenOF0.1'
      gunzipping (0x1400000 <- 0x407000:0x688751)...done 0x6a8578 bytes
      OF stdout device is: /xen/console
      command line: root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr
      memory layout at init:
        alloc_bottom : 0000000001b39000
        alloc_top    : 0000000004000000
        alloc_top_hi : 000000000c000000
        rmo_top      : 0000000004000000
        ram_top      : 000000000c000000
            :

And, this is the log with new XenPPC.

      Welcome to yaboot version 10.1.14-r716.SuSE
      booted from '/ht/[EMAIL PROTECTED],1/[EMAIL PROTECTED]'
      Enter "help" to get some basic usage information
      boot: xen
      Please wait, loading kernel...
      Allocated 00500000 bytes for executable @ 00400000
         Elf32 kernel loaded...
      ---------------------------------------------------
      OF: Xen/PPC version 3.0-unstable ([EMAIL PROTECTED]) (gcc version
4.1.0 (SUSE Linux)) Fri Oct  6 19:49:34 JST 2006
      boot_of_init args: 0x400000 0x0 0x111027c 0x0 0x712120
      boot msr: 0x1000000000003000
      boot_of_init: _start 0000000000400100 _end 0000000000725f48 0x0
      boot_of_probemem: memory 0x0000000000000000[0x20000000]
      bootargs = xen
      boot_of_module: Dom0 is linked in: 0x44f6bc[size 0x29954d]
      mod0: 177 E L F
      boot_of_module: dom0 mod @ 0x000000000044f6bc[0x6e8c09]
      find_space base=0x0000000000725f48  eomem=0x0000000020000000
size=0x00008000  align=0x1000
      find_space base=0x0000000000908000  eomem=0x0000000020000000
size=0x00030000  align=0x1000
      creating oftree
      pkg_save: saved device tree in 0x3288 bytes
      boot_of_devtree: devtree mod @ 0x0000000000908000[0x938000]
      OF: timebase-frequency = 14318278 Hz
      OF: clock-frequency = 2200000 KHz
            :
      zImage starting: loaded at 0x00400000 (sp: 0x01ffff90)
      Allocating 0x7348b8 bytes for kernel ...
      OF version = 'IBM,XenOF0.1'
      gunzipping (0x1400000 <- 0x407000:0x688751)...done 0x6a8578 bytes
      OF stdout device is: /xen/console
      command line:
      memory layout at init:
        alloc_bottom : 0000000001b39000
        alloc_top    : 0000000004000000
        alloc_top_hi : 000000000c000000
        rmo_top      : 0000000004000000
        ram_top      : 000000000c000000
            :


You can see that "bootargs" and "command line" lines are differnt.

Kawachiya




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

Reply via email to