Re: [Xen-devel] Re: [Xen-users] pvops dom0 kernel: crash in pri

Command line: ro root=/dev/VolGroup01/Logvol00 console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10

If I change the Logvol00 to LovVol00 then it booted up. (lower case v to upper case V)

Is the command line case sensitive??

On Mon, Mar 22, 2010 at 1:31 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:

On Mon, Mar 22, 2010 at 01:23:24PM -0700, kishore kumar wrote:
> xend was not running so I did below steps and rebooted. The system did
> not boot up. SO I removed the line added in /proc/fstab and again
> rebooted. Attached is the captured file. Can you please let me know what
> is going wrong again?
>

Please send the logs as text files, not word documents!

Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory

Looks like wrong root= parameter again..

Command line: ro root=/dev/VolGroup01/Logvol00 console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10

Was "/dev/VolGroup01/Logvol00" your root device?

-- Pasi

> step 1. I loaded the xen-evtchn.ko by insmod.
>
>
>
> step 2: And added the below line in /proc/fstab.
>
>
>
> none /proc/xen xenfs defaults 0 0
>
>
> Thanks
>
> On Fri, Mar 19, 2010 at 1:03 PM, Pasi Kärkkäinen <[1]pasik@xxxxxx> wrote:
>
> On Fri, Mar 19, 2010 at 12:57:58PM -0700, kishore kumar wrote:
> > Attached is the captured file.
> >
> > Now the machine booted up. :) 2.6.32.10 is booted.
> >
> > But I dont see xen up and running.
> >
> > Whe I open Virtual Machine Manager I dont see xen running.
> (ATTACHED IS
> > THE SCREEN SHOT).
> >
>
> - Do you have /proc/xen (xenfs) mounted?
> - Do you have xen-evtchn driver module loaded in dom0?
> - Do you have xend running?
>
> Please see and read this wiki page:
> [2]http://wiki.xensource.com/xenwiki/XenParavirtOps
>
> It explains the other configurations you need to do for Xen/xend to
> actually work.
>
> Anyway, the problem for you was wrong grub.conf root= option for the
> dom0 kernel.
>
> -- Pasi
>
> > On Fri, Mar 19, 2010 at 12:05 PM, Pasi Kärkkäinen
> <[1][3]pasik@xxxxxx> wrote:
> >
> > On Fri, Mar 19, 2010 at 11:22:54AM -0700, Jeremy Fitzhardinge
> wrote:
> > > On 03/19/2010 10:59 AM, Pasi Kärkkäinen wrote:
> > >> On Thu, Mar 18, 2010 at 04:56:35PM -0700, kishore kumar wrote:
> > >>
> > >>> Attached is the capture log after changing the grub.conf
> to
> > >>>
> > >>> ro root=/dev/VolGroup01/LogVol00 console=hvc0
> earlyprintk=xen
> > nomodeset
> > >>> initcall_debug debug swiotlb=force apic=debug loglevel=10
> > >>>
> > >>> for the dom 0 kernel command line.
> > >>>
> > >>>
> > >> Hmm, interesting. Now it seems to crash in a different place.
> > >>
> > >> Jeremy: Have you seen this one earlier?
> > >>
> > >
> > > No, but it looks like the result of "apic=debug" on the kernel
> command
> > > line. That won't do anything useful (the kernel has no APICs,
> they
> > all
> > > belong to Xen), and can only cause harm. As it appears to have
> done.
> > >
> >
> > Ok, my bad.
> >
> > So please remove the "apic=debug" from the dom0 kernel cmdline
> and try
> > again.
> > It should look like this:
> >
> > ro root=/dev/VolGroup01/LogVol00 console=hvc0 earlyprintk=xen
> nomodeset
> > initcall_debug debug loglevel=10
> >
> > -- Pasi
> >
> > > J
> > >
> > >> .... IRQ redirection table:
> > >> NR Dst Mask Trig IRR Pol Stat Dmod Deli Vect:
> > >> 00 000 0 0 0 0 0 0 0 00
> > >> IRQ to pin mappings:
> > >> BUG: unable to handle kernel NULL pointer dereference at
> (null)
> > >> IP: [<ffffffff819bf0e0>] print_all_ICs+0x487/0x500
> > >> PGD 0
> > >> Oops: 0000 [#1] SMP
> > >> last sysfs file:
> > >> CPU 0
> > >> Modules linked in:
> > >> Pid: 1, comm: swapper Not tainted 2.6.32.10 #2
> > >> RIP: e030:[<ffffffff819bf0e0>] [<ffffffff819bf0e0>]
> > print_all_ICs+0x487/0x500
> > >> RSP: e02b:ffff880064edbe20 EFLAGS: 00010286
> > >> RAX: ffffffff816ed2c0 RBX: 0000000000000000 RCX:
> 000000000f640f01
> > >> RDX: ffff880066808000 RSI: ffff880064edbd40 RDI:
> 0000000000000000
> > >> RBP: ffff880064edbea0 R08: 0000000000000002 R09:
> 0000000000000000
> > >> R10: 0000000000000000 R11: ffff880064edbce0 R12:
> 0000000000000000
> > >> R13: 0000000000000000 R14: 0000000000000000 R15:
> 0000000000000000
> > >> FS: 0000000000000000(0000) GS:ffff880005ec8000(0000)
> > knlGS:0000000000000000
> > >> CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> > >> CR2: 0000000000000000 CR3: 0000000001001000 CR4:
> 0000000000002660
> > >> DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> 0000000000000000
> > >> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
> 0000000000000400
> > >> Process swapper (pid: 1, threadinfo ffff880064eda000, task
> > ffff880064ee0000)
> > >> Stack:
> > >> ffff880000000000 ffffffff00000000 ffff880000000000
> ffffffff811ebee8
> > >> <0> ffff880064edbe60 0000000181083e7c 000000ff00000002
> > 0000000000000002
> > >> <0> ffff880000000000 ffffffff810846f0 ffffffff817ce660
> > 00000000291fd332
> > >> Call Trace:
> > >> [<ffffffff811ebee8>] ? debugfs_create_file+0x239/0x28e
> > >> [<ffffffff810846f0>] ? ktime_get+0x78/0x93
> > >> [<ffffffff819bec59>] ? print_all_ICs+0x0/0x500
> > >> [<ffffffff8100a07e>] do_one_initcall+0x73/0x18b
> > >> [<ffffffff819ae961>] kernel_init+0x172/0x1cc
> > >> [<ffffffff81013eaa>] child_rip+0xa/0x20
> > >> [<ffffffff8104edcf>] ? finish_task_switch+0x0/0xcc
> > >> [<ffffffff81013810>] ? restore_args+0x0/0x30
> > >> [<ffffffff8108ae5b>] ? trace_hardirqs_off_caller+0x2f/0x89
> > >> [<ffffffff81013ea0>] ? child_rip+0x0/0x20
> > >> Code: 45 b0 0f 8c 5b fd ff ff 48 c7 c7 34 40 60 81 31 c0 45 31
> e4 e8
> > 11 d5 69 ff 31 ff e8 67 b5 6f ff eb 5a 48 85 c0 74 4a 48 8b 58
> 40<48>
> > 83 3b 00 74 40 44 89 e6 48 c7 c7 4d 40 60 81 31 c0 e8 e8 d4
> > >> RIP [<ffffffff819bf0e0>] print_all_ICs+0x487/0x500
> > >> RSP<ffff880064edbe20>
> > >> CR2: 0000000000000000
> > >> ---[ end trace 0007ad9d59420718 ]---
> > >> swapper used greatest stack depth: 4168 bytes left
> > >> Kernel panic - not syncing: Attempted to kill init!
> > >> Pid: 1, comm: swapper Tainted: G D 2.6.32.10 #2
> > >> Call Trace:
> > >> [<ffffffff8105b747>] panic+0xa5/0x167
> > >> [<ffffffff8100ed81>] ? xen_force_evtchn_callback+0xd/0xf
> > >> [<ffffffff8105f2b3>] ? do_exit+0x38a/0x701
> > >> [<ffffffff8100f43f>] ? xen_restore_fl_direct_end+0x0/0x1
> > >> [<ffffffff8108f823>] ? lock_release+0x179/0x184
> > >> [<ffffffff8108ca25>] ? trace_hardirqs_on+0xd/0xf
> > >> [<ffffffff81475d4f>] ? _write_unlock_irq+0x37/0x3c
> > >> [<ffffffff8105efa7>] do_exit+0x7e/0x701
> > >> [<ffffffff819b02ef>] ? md_run_setup+0x104/0x4ef
> > >> [<ffffffff8147764c>] oops_end+0xbf/0xc7
> > >> [<ffffffff81038a02>] no_context+0x1f1/0x200
> > >> [<ffffffff819b02ef>] ? md_run_setup+0x104/0x4ef
> > >> [<ffffffff81038c61>] __bad_area_nosemaphore+0x191/0x1b4
> > >> [<ffffffff8100f452>] ? check_events+0x12/0x20
> > >> [<ffffffff81038d0e>] bad_area_nosemaphore+0x13/0x15
> > >> [<ffffffff81478b20>] do_page_fault+0x16d/0x2a2
> > >> [<ffffffff814769d5>] page_fault+0x25/0x30
> > >> [<ffffffff819bf0e0>] ? print_all_ICs+0x487/0x500
> > >> [<ffffffff811ebee8>] ? debugfs_create_file+0x239/0x28e
> > >> [<ffffffff810846f0>] ? ktime_get+0x78/0x93
> > >> [<ffffffff819bec59>] ? print_all_ICs+0x0/0x500
> > >> [<ffffffff8100a07e>] do_one_initcall+0x73/0x18b
> > >> [<ffffffff819ae961>] kernel_init+0x172/0x1cc
> > >> [<ffffffff81013eaa>] child_rip+0xa/0x20
> > >> [<ffffffff8104edcf>] ? finish_task_switch+0x0/0xcc
> > >> [<ffffffff81013810>] ? restore_args+0x0/0x30
> > >> [<ffffffff8108ae5b>] ? trace_hardirqs_off_caller+0x2f/0x89
> > >> [<ffffffff81013ea0>] ? child_rip+0x0/0x20
> > >>
> > >>
> > >> -- Pasi
> > >>
> > >>
> > >>
> > >>>
> > >>> On Thu, Mar 18, 2010 at 2:27 PM, Pasi
> > Kärkkäinen<[1][2][4]pasik@xxxxxx> wrote:
> > >>>
> > >>> On Thu, Mar 18, 2010 at 01:23:41PM -0700, kishore kumar
> wrote:
> > >>> > pvdisplay does not work in my RHEL machine.
> > >>> >
> > >>> > I did pvscan.
> > >>> > below is the output.
> > >>> >
> > >>> > PV /dev/sda2 VG VolGroup01 lvm2 [232.78 GB / 0
> free]
> > >>> >
> > >>> > Total: 1 [232.78 GB] / in use: 1 [232.78 GB] / in
> no VG:
> > 0 [0 ]
> > >>> >
> > >>>
> > >>> Ok so /dev/sda2 is the correct device holding the
> VolGroup01.
> > >>>
> > >>> Looking at your latest capture.doc I see this:
> > >>>
> > >>> Command line: ro root=/dev/vg00/lv01 console=hvc0
> > earlyprintk=xen
> > >>> nomodeset initcall_debug debug swiotlb=force apic=debug
> > loglevel=10
> > >>>
> > >>> So your root= parameter is wrong! Edit grub.conf and
> replace
> > it with the
> > >>> actual root device:
> > >>> root=/dev/VolGroup01/LogVol00
> > >>>
> > >>> -- Pasi
> > >>>
> > >>> > On Thu, Mar 18, 2010 at 12:31 PM, Pasi Kärkkäinen
> > >>> <[1][2][3][5]pasik@xxxxxx> wrote:
> > >>> >
> > >>> > On Thu, Mar 18, 2010 at 11:16:26AM -0700,
> kishore
> > kumar wrote:
> > >>> > > I did the below steps for pvops dom 0
> kernel.
> > >>> > >
> > >>> > > make menuconfig
> > >>> > > make bzImage
> > >>> > > make modules
> > >>> > > make modules_install
> > >>> > > cp -a .config /boot/config-2.6.32.10
> > >>> > > cp -a System.map
> /boot/System.map-2.6.32.10
> > >>> > > cp -a arch/x86/boot/bzImage
> > /boot/vmlinuz-2.6.32.10
> > >>> > > /sbin/mkinitrd -f --builtin=ahci
> > /boot/initrd-2.6.32.10.img
> > >>> > 2.6.32.10
> > >>> > > I tried root=/dev/VolGroup01/LogVol00 .
> > >>> > >
> > >>> >
> > >>> > Ok.
> > >>> >
> > >>> > Please run "pvdisplay" to see which actual
> partition
> > is the LVM
> > >>> PV for
> > >>> > your
> > >>> > volume group.
> > >>> >
> > >>> > Also if you're running Fedora 12 you could try
> > generating an
> > >>> initrd
> > >>> > image
> > >>> > with dracut instead of mkinitrd.
> > >>> >
> > >>> > -- Pasi
> > >>> >
> > >>> > >
> > >>> > > On Thu, Mar 18, 2010 at 9:15 AM, Pasi
> Kärkkäinen
> > >>> > <[1][2][3][4][6]pasik@xxxxxx> wrote:
> > >>> > >
> > >>> > > On Wed, Mar 17, 2010 at 03:20:13PM
> -0700,
> > kishore kumar
> > >>> wrote:
> > >>> > > > Here is the output of df -h and
> cat
> > /etc/fstab of my
> > >>> > machine.
> > >>> > > >
> > >>> > >
> > >>> > > Did you try both
> > root=/dev/mapper/VolGroup01-LogVol00 and
> > >>> > > root=/dev/VolGroup01/LogVol00 arguments
> for
> > the dom0
> > >>> kernel?
> > >>> > >
> > >>> > > How did you generate the initrd image
> for the
> > dom0 kernel?
> > >>> > >
> > >>> > > Anyway this sounds like a grub.conf or
> initrd
> > problem, not
> > >>> Xen or
> > >>> > pvops
> > >>> > > dom0 kernel kernel problem.
> > >>> > >
> > >>> > > -- Pasi
> > >>> > >
> > >>> > > > Please let me know your thoughts.
> > >>> > > >
> > >>> > > > [root@localhost kishore]# df -h
> > >>> > > >
> > >>> > > > Filesystem Size Used Avail Use%
> Mounted
> > on
> > >>> > > >
> > >>> > > > /dev/mapper/VolGroup01-LogVol00
> > >>> > > >
> > >>> > > >
> 223G
> > 29G 182G 14%
> > >>> /
> > >>> > > >
> > >>> > > > /dev/sda1 99M 81M 13M 87% /boot
> > >>> > > >
> > >>> > > > tmpfs 757M 0 757M 0% /dev/shm
> > >>> > > >
> > >>> > > > [root@localhost kishore]# cat
> /etc/fstab
> > >>> > > >
> > >>> > > > /dev/VolGroup01/LogVol00 / ext3
> defaults
> > 1 1
> > >>> > > >
> > >>> > > > LABEL=/boot /boot ext3 defaults 1
> 2
> > >>> > > >
> > >>> > > > tmpfs /dev/shm tmpfs defaults 0 0
> > >>> > > >
> > >>> > > > devpts /dev/pts devpts
> gid=5,mode=620 0
> > 0
> > >>> > > >
> > >>> > > > sysfs /sys sysfs defaults 0 0
> > >>> > > >
> > >>> > > > proc /proc proc defaults 0 0
> > >>> > > >
> > >>> > > > /dev/VolGroup01/LogVol01 swap
> swap
> > defaults 0 0
> > >>> > > >
> > >>> > > > [root@localhost kishore]#
> > >>> > > >
> > >>> > > > On Tue, Mar 16, 2010 at 4:18 PM,
> Pasi
> > Kärkkäinen
> > >>> > > <[1][2][3][4][5][7]pasik@xxxxxx>
> wrote:
> > >>> > > >
> > >>> > > > On Tue, Mar 16, 2010 at
> 03:40:46PM
> > -0700, kishore
> > >>> kumar
> > >>> > wrote:
> > >>> > > > > I am not sure. Can you
> please
> > let me know how
> > >>> to
> > >>> > check
> > >>> > > this? any
> > >>> > > > command
> > >>> > > > > ??
> > >>> > > >
> > >>> > > > well simple "df -h" will show
> it. and
> > also "cat
> > >>> > /etc/fstab".
> > >>> > > > You can also check it from your
> grub
> > >>> configuration.. from
> > >>> > the
> > >>> > > working
> > >>> > > > baremetal (non-Xen) entry.
> > >>> > > >
> > >>> > > > -- Pasi
> > >>> > > > >
> > >>> > > > > On Tue, Mar 16, 2010 at
> 3:29 PM,
> > Pasi
> > >>> Kärkkäinen
> > >>> > > >
> <[1][2][3][4][5][6][8]pasik@xxxxxx>
> > wrote:
> > >>> > > > >
> > >>> > > > > On Tue, Mar 16, 2010 at
> > 03:22:50PM -0700,
> > >>> kishore
> > >>> > kumar
> > >>> > > wrote:
> > >>> > > > > > attached is the
> log
> > captured in with
> > >>> the word
> > >>> > > document .
> > >>> > > > > >
> > >>> > > > >
> > >>> > > > > Scanning logical
> volumes
> > >>> > > > > Reading all physical
> volumes.
> > This may
> > >>> take a
> > >>> > while...
> > >>> > > > > Activating logical
> volumes
> > >>> > > > > Volume group
> "VolGroup01" not
> > found
> > >>> > > > > Trying to resume from
> > >>> /dev/VolGroup01/LogVol01
> > >>> > > > > Unable to access resume
> device
> > >>> > (/dev/VolGroup01/LogVol01)
> > >>> > > > > Creating root device.
> > >>> > > > > Mounting root
> filesystem.
> > >>> > > > > mount: could not find
> > filesystem '/dev/root'
> > >>> > > > > Setting up other
> filesystems.
> > >>> > > > > Setting up new root fs
> > >>> > > > > setuproot: moving /dev
> failed:
> > No such file
> > >>> or
> > >>> > directory
> > >>> > > > > no fstab.sys, mounting
> > internal defaults
> > >>> > > > > setuproot: error
> mounting
> > /proc: No such
> > >>> file or
> > >>> > directory
> > >>> > > > > setuproot: error
> mounting
> > /sys: No such file
> > >>> or
> > >>> > directory
> > >>> > > > > Switching to new root
> and
> > running init.
> > >>> > > > > unmounting old /dev
> > >>> > > > > unmounting old /proc
> > >>> > > > > unmounting old /sys
> > >>> > > > > switchroot: mount
> failed: No
> > such file or
> > >>> directory
> > >>> > > > > init used greatest
> stack
> > depth: 4088 bytes
> > >>> left
> > >>> > > > > Kernel panic - not
> syncing:
> > Attempted to
> > >>> kill init!
> > >>> > > > >
> > >>> > > > > So it seems it gets all
> the
> > way to executing
> > >>> the
> > >>> > initrd
> > >>> > > image,
> > >>> > > > > which then fails to
> mount the
> > root fs.
> > >>> > > > >
> > >>> > > > > Earlier in the log:
> > >>> > > > > ata1: SATA link up 3.0
> Gbps
> > (SStatus 123
> > >>> SControl
> > >>> > 300)
> > >>> > > > > ata1.00: ATA-8: Hitachi
> > HDT721025SLA380,
> > >>> STBOA3AA,
> > >>> > max
> > >>> > > UDMA/133
> > >>> > > > > ata1.00: 488397168
> sectors,
> > multi 0: LBA48
> > >>> NCQ
> > >>> > (depth
> > >>> > > 31/32), AA
> > >>> > > > > ata1.00: configured for
> > UDMA/133
> > >>> > > > > scsi 0:0:0:0:
> Direct-Access
> > ATA
> > >>> Hitachi
> > >>> > HDT72102
> > >>> > > STBO
> > >>> > > > PQ: 0
> > >>> > > > > ANSI: 5
> > >>> > > > > sd 0:0:0:0: Attached
> scsi
> > generic sg0 type 0
> > >>> > > > > sd 0:0:0:0: [sda]
> 488397168
> > 512-byte logical
> > >>> > blocks: (250
> > >>> > > GB/232
> > >>> > > > GiB)
> > >>> > > > > sd 0:0:0:0: [sda] Write
> > Protect is off
> > >>> > > > > sd 0:0:0:0: [sda] Mode
> Sense:
> > 00 3a 00 00
> > >>> > > > > sd 0:0:0:0: [sda] Write
> cache:
> > enabled, read
> > >>> cache:
> > >>> > > enabled,
> > >>> > > > doesn't
> > >>> > > > > support DPO or FUA
> > >>> > > > > sda: sda1 sda2
> > >>> > > > > sd 0:0:0:0: [sda]
> Attached
> > SCSI disk
> > >>> > > > >
> > >>> > > > > so /dev/sda was
> detected. Is
> > your root lvm
> > >>> volume
> > >>> > on
> > >>> > > /dev/sda ?
> > >>> > > > > Is
> /dev/VolGroup01/LogVol01
> > really your root
> > >>> fs?
> > >>> > > > >
> > >>> > > > > -- Pasi
> > >>> > > > >
> > >>> > > > > >
> > >>> > > > > >
> > >>> > > > > > On Tue, Mar 16,
> 2010 at
> > 3:03 PM, Pasi
> > >>> > Kärkkäinen
> > >>> > > > >
> > <[1][2][3][4][5][6][7][9]pasik@xxxxxx> wrote:
> > >>> > > > > >
> > >>> > > > > > On Tue, Mar 16,
> 2010
> > at 02:56:06PM
> > >>> -0700,
> > >>> > kishore
> > >>> > > kumar
> > >>> > > > wrote:
> > >>> > > > > > > Please
> find the
> > attached log
> > >>> file after
> > >>> > fixing
> > >>> > > the
> > >>> > > > dom 0
> > >>> > > > > kernel cmd
> > >>> > > > > > line
> > >>> > > > > > > as below
> > >>> > > > > > >
> > >>> > > > > > > ro
> > root=/dev/VolGroup01/LogVol00
> > >>> > console=hvc0
> > >>> > > > > earlyprintk=xen
> > >>> > > > > > nomodeset
> > >>> > > > > > >
> > >>> > > > > >
> > >>> > > > > > There's
> something
> > wrong with the log,
> > >>> the
> > >>> > dom0
> > >>> > > kernel
> > >>> > > > parts are
> > >>> > > > > all on
> > >>> > > > > > one line..
> > >>> > > > > > It's really
> difficult
> > to read it.
> > >>> > > > > >
> > >>> > > > > > -- Pasi
> > >>> > > > > >
> > >>> > > > > > > Thanks
> > >>> > > > > > >
> > >>> > > > > > >
> > >>> > > > > > > On Tue,
> Mar 16,
> > 2010 at 2:29 PM,
> > >>> Pasi
> > >>> > > Kärkkäinen
> > >>> > > > > >
> > <[1][2][3][4][5][6][7][8][10]pasik@xxxxxx>
> > >>> wrote:
> > >>> > > > > > >
> > >>> > > > > > > On Tue,
> Mar
> > 16, 2010 at
> > >>> 02:16:22PM
> > >>> > -0700,
> > >>> > > kishore
> > >>> > > > kumar
> > >>> > > > > wrote:
> > >>> > > > > > > > I
> did
> > below steps.
> > >>> > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > > > >
> I
> > pulled DOM 0 kernel
> > >>> from
> > >>> > > > > > > >
> git
> > clone
> > >>> > > > > > >
> > >>> > > > > >
> > >>> > > > >
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> >
> git://[1][2][3][4][5][6][7][8][9][11]git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > >>> > > > > > > >
> > linux-2.6-xen
> > >>> > > > > > > >
> > >>> > > > > > > >
> cd
> > linux-2.6-xen
> > >>> > > > > > > >
> > >>> > > > > > > >
> make
> > clean
> > >>> > > > > > > >
> > >>> > > > > > > >
> cp -a
> > .config .config-old
> > >>> > > > > > > >
> > >>> > > > > > > >
> wget -O
> > .config
> > >>> > > > > > > >
> > >>> > > > > > >
> > >>> > > > > >
> > >>> > > > >
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> >
> [2][3][4][5][6][7][8][9][10][12]http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.9-pvops-dom0-xen-stable-x86_64
> > >>> > > > > > > >
> > >>> > > > > > > >
> make
> > oldconfig
> > >>> > > > > > > >
> > >>> > > > > > > >
> make
> > bzImage
> > >>> > > > > > > >
> > >>> > > > > > > >
> make
> > modules
> > >>> > > > > > > >
> > >>> > > > > > > >
> make
> > modules_install
> > >>> > > > > > > >
> > >>> > > > > > > >
> cp -a
> > .config
> > >>> > /boot/config-2.6.32.9
> > >>> > > > > > > >
> > >>> > > > > > > >
> cp -a
> > System.map
> > >>> > > /boot/System.map-2.6.32.9
> > >>> > > > > > > >
> > >>> > > > > > > >
> cp -a
> > >>> arch/x86/boot/bzImage
> > >>> > > > /boot/vmlinuz-2.6.32.9
> > >>> > > > > > > >
> > >>> > > > > > > >
> and
> > modified the
> > >>> grub.conf as
> > >>> > below
> > >>> > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > > > >
> > Root(hd0,0)
> > >>> > > > > > > >
> > >>> > > > > > > >
> kernel
> > /xen.gz
> > >>> console=vga,com1
> > >>> > > > com1=115200,8n1
> > >>> > > > > msi=1
> > >>> > > > > > iommu=1
> > >>> > > > > > > >
> > >>> > > > > > > >
> module
> > /vmlinuz-2.6.32.9
> > >>> ro
> > >>> > > > >
> root=/dev/VolGroup01/LogVo100
> > >>> > > > > > rhgb
> > >>> > > > > > > quiet
> > >>> > > > > > > >
> > >>> > > > > > > >
> module
> > >>> /initrd-2.6.32.9.img
> > >>> > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > > > >
> and
> > rebooted the machine.
> > >>> Then
> > >>> > It
> > >>> > > booted with
> > >>> > > > some
> > >>> > > > > xen
> > >>> > > > > > messages
> > >>> > > > > > > and
> > >>> > > > > > > >
> stopped.
> > Those were the
> > >>> > messages
> > >>> > > captured
> > >>> > > > from
> > >>> > > > > serial
> > >>> > > > > > console.
> > >>> > > > > > > >
> > >>> > > > > > > >
> Please
> > let me know if I
> > >>> did
> > >>> > something
> > >>> > > wrong
> > >>> > > > here.
> > >>> > > > > > > >
> > >>> > > > > > >
> > >>> > > > > > > Please
> fix the
> > kernel cmdline
> > >>> based
> > >>> > on my
> > >>> > > earlier
> > >>> > > > email,
> > >>> > > > > and
> > >>> > > > > > capture and
> > >>> > > > > > > post
> the
> > >>> > > > > > > serial
> console
> > log again!
> > >>> > > > > > >
> > >>> > > > > > > -- Pasi
> > >>> > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > > > >
> On Tue,
> > Mar 16, 2010 at
> > >>> 1:20 PM,
> > >>> > Pasi
> > >>> > > > Kärkkäinen
> > >>> > > > > > >
> > >>> <[3][4][5][6][7][8][9][10][11][13]pasik@xxxxxx>
> > >>> > wrote:
> > >>> > > > > > > >
> > >>> > > > > > > >
> On
> > Tue, Mar 16, 2010 at
> > >>> > 01:16:28PM
> > >>> > > -0700,
> > >>> > > > Jeremy
> > >>> > > > > > Fitzhardinge
> > >>> > > > > > > wrote:
> > >>> > > > > > > >
> > On
> > 03/16/2010 12:48
> > >>> PM, Pasi
> > >>> > > Kärkkäinen
> > >>> > > > wrote:
> > >>> > > > > > > >
> >> On
> > Tue, Mar 16, 2010
> > >>> at
> > >>> > 09:43:44PM
> > >>> > > +0200,
> > >>> > > > Pasi
> > >>> > > > > > Kärkkäinen
> > >>> > > > > > > wrote:
> > >>> > > > > > > >
> >>
> > >>> > > > > > > >
> >>>
> > On Tue, Mar 16,
> > >>> 2010 at
> > >>> > > 10:32:17AM
> > >>> > > > -0700,
> > >>> > > > > kishore
> > >>> > > > > > kumar
> > >>> > > > > > > wrote:
> > >>> > > > > > > >
> >>>
> > >>> > > > > > > >
> >>>>
> > Attached is
> > >>> the
> > >>> > output
> > >>> > > captured
> > >>> > > > from
> > >>> > > > > serial
> > >>> > > > > > console.
> > >>> > > > > > > >
> >>>>
> > >>> > > > > > > >
> >>>>
> > Machine does
> > >>> not boot
> > >>> > after
> > >>> > > > compiling xen
> > >>> > > > > 3.4.3
> > >>> > > > > > with
> > >>> > > > > > > pv_ops
> dom
> > >>> > > > > > > >
> 0
> > kernel.
> > >>> > > > > > > >
> >>>>
> > >>> > > > > > > >
> >>>>
> > Please let me
> > >>> know
> > >>> > what is
> > >>> > > going
> > >>> > > > wrong
> > >>> > > > > here.
> > >>> > > > > > > >
> >>>>
> > >>> > > > > > > >
> >>>>
> > >>> > > > > > > >
> >>>
> > Ok this looks like
> > >>> a bug
> > >>> > that is
> > >>> > > already
> > >>> > > > being
> > >>> > > > > sorted
> > >>> > > > > > out on
> > >>> > > > > > > >
> > xen-devel mailinglist.
> > >>> > > > > > > >
> >>> I
> > added CC to
> > >>> xen-devel.
> > >>> > > > > > > >
> >>>
> > >>> > > > > > > >
> >>>
> > >>> > > > > > > >
> >>
> > >>> > > > > > > >
> >
> > >>> > > > > > > >
> >
> > Those messages are
> > >>> not a
> > >>> > problem in
> > >>> > > > themselves,
> > >>> > > > > but the
> > >>> > > > > > related
> > >>> > > > > > > >
> > problem
> > >>> > > > > > > >
> > is
> > believed to be
> > >>> fixed in
> > >>> > current
> > >>> > > > > xen/stable-2.6.32.x.
> > >>> > > > > > It
> > >>> > > > > > > looks
> like
> > >>> > > > > > > >
> > the
> > output stops
> > >>> there
> > >>> > because the
> > >>> > > Xen
> > >>> > > > console
> > >>> > > > > isn't set
> > >>> > > > > > up
> > >>> > > > > > >
> properly
> > >>> > > > > > > >
> for
> > >>> > > > > > > >
> >
> > some reason.
> > >>> > > > > > > >
> >
> > >>> > > > > > > >
> > >>> > > > > > > >
> Yeah,
> > remove "rhgb
> > >>> quiet" from
> > >>> > the
> > >>> > > options..
> > >>> > > > the
> > >>> > > > > dom0
> > >>> > > > > > kernel
> > >>> > > > > > > cmdline
> > >>> > > > > > > >
> should
> > be like this:
> > >>> > > > > > > >
> ro
> > >>> > root=/dev/VolGroup01/LogVol00
> > >>> > > > console=hvc0
> > >>> > > > > > earlyprintk=xen
> > >>> > > > > > >
> nomodeset
> > >>> > > > > > > >
> --
> > Pasi
> > >>> > > > > > > >
> > >>> > > > > > > >
> References
> > >>> > > > > > > >
> > >>> > > > > > > >
> Visible
> > links
> > >>> > > > > > > >
> 1.
> > >>> > > > > >
> > >>> > > > >
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> >
> [5][6][7][8][9][10][11][12][14]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > >>> > > > > > > >
> 2.
> > >>> > > > > > >
> > >>> > > > > >
> > >>> > > > >
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> >
> [6][7][8][9][10][11][12][13][15]http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.9-pvops-dom0-xen-stable-x86_64
> > >>> > > > > > > >
> 3.
> > >>> >
> mailto:[7][8][9][10][11][12][13][14][16]pasik@xxxxxx
> > >>> > > > > > >
> > >>> > > > > > > References
> > >>> > > > > > >
> > >>> > > > > > > Visible
> links
> > >>> > > > > > > 1.
> > >>> >
> mailto:[9][10][11][12][13][14][15][17]pasik@xxxxxx
> > >>> > > > > > > 2.
> > >>> > > > > >
> > >>> > > > >
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> >
> [10][11][12][13][14][15][16][18]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > >>> > > > > > > 3.
> > >>> > > > > >
> > >>> > > > >
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> >
> [11][12][13][14][15][16][17][19]http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.9-pvops-dom0-xen-stable-x86_64
> > >>> > > > > > > 4.
> > >>> >
> mailto:[12][13][14][15][16][17][18][20]pasik@xxxxxx
> > >>> > > > > > > 5.
> > >>> > > > > >
> > >>> > > > >
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> >
> [13][14][15][16][17][18][19][21]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > >>> > > > > > > 6.
> > >>> > > > > >
> > >>> > > > >
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> >
> [14][15][16][17][18][19][20][22]http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.9-pvops-dom0-xen-stable-x86_64
> > >>> > > > > > > 7.
> > >>> >
> mailto:[15][16][17][18][19][20][21][23]pasik@xxxxxx
> > >>> > > > > > > Asserting
> Post
> > complete GPIO!!!
> > >>> > > > > > > Transfer
> control to
> > CSM 16-bit
> > >>> binary for
> > >>> > legacy
> > >>> > > boot
> > >>> > > > > > > __ __
> > _____ _ _
> > >>> _____
> > >>> > > _ _
> > >>> > > > > > > \ \/ /___ _
> __
> > |___ /| || |
> > >>> |___ /
> > >>> > _ __
> > >>> > > ___| || |
> > >>> > > > _
> > >>> > > > > __ _
> > >>> > > > > > __ ___
> > >>> > > > > > > \ // _ \
> '_ \
> > |_ \| || |_
> > >>> |_ \ __|
> > >>> > '__/
> > >>> > > __| ||
> > >>> > > > |_ __|
> > >>> > > > > '_ \|
> > >>> > > > > > '__/ _ \
> > >>> > > > > > > / \ __/
> | | |
> > ___) |__ _|
> > >>> ___) |__|
> > >>> > | |
> > >>> > > (__|__
> > >>> > > > _|__|
> > >>> > > > > |_) | |
> > >>> > > > > > | __/
> > >>> > > > > > >
> /_/\_\___|_| |_|
> > |____(_)
> > >>> |_|(_)____/
> > >>> > |_|
> > >>> > > \___| |_|
> > >>> > > > |
> > >>> > > > > .__/|_|
> > >>> > > > > > \___|
> > >>> > > > > > >
> > >>> > > > |_|
> > >>> > > > > > > (XEN) Xen
> version
> > 3.4.3-rc4-pre
> > >>> > > (kishore@localdomain)
> > >>> > > > (gcc
> > >>> > > > > version
> > >>> > > > > > 4.1.2 20080704
> (Red
> > Hat 4.1.2-46))
> > >>> Mon Mar
> > >>> > 15
> > >>> > > 13:44:31 PDT
> > >>> > > > 2010
> > >>> > > > > > > (XEN) Latest
> > ChangeSet: Tue Mar 09
> > >>> > 18:15:52 2010
> > >>> > > +0000
> > >>> > > > > >
> 19924:6e72f8c3c017
> > >>> > > > > > > (XEN)
> Command line:
> > >>> console=vga,com1
> > >>> > > com1=115200,8n1
> > >>> > > > msi=1
> > >>> > > > > iommu=1
> > >>> > > > > > > (XEN) Video
> > information:
> > >>> > > > > > > (XEN) VGA
> is text
> > mode 80x25, font
> > >>> 8x16
> > >>> > > > > > > (XEN)
> VBE/DDC
> > methods: none; EDID
> > >>> > transfer time:
> > >>> > > 0
> > >>> > > > seconds
> > >>> > > > > > > (XEN) EDID
> info
> > not retrieved
> > >>> because no
> > >>> > DDC
> > >>> > > retrieval
> > >>> > > > method
> > >>> > > > > > detected
> > >>> > > > > > > (XEN) Disc
> > information:
> > >>> > > > > > > (XEN) Found
> 1 MBR
> > signatures
> > >>> > > > > > > (XEN) Found
> 1 EDD
> > information
> > >>> structures
> > >>> > > > > > > (XEN)
> Xen-e820 RAM
> > map:
> > >>> > > > > > > (XEN)
> > 0000000000000000 -
> > >>> 000000000009d000
> > >>> > > (usable)
> > >>> > > > > > > (XEN)
> > 000000000009d000 -
> > >>> 00000000000a0000
> > >>> > > (reserved)
> > >>> > > > > > > (XEN)
> > 00000000000e0000 -
> > >>> 0000000000100000
> > >>> > > (reserved)
> > >>> > > > > > > (XEN)
> > 0000000000100000 -
> > >>> 000000006d597000
> > >>> > > (usable)
> > >>> > > > > > > (XEN)
> > 000000006d597000 -
> > >>> 000000006d686000
> > >>> > > (reserved)
> > >>> > > > > > > (XEN)
> > 000000006d686000 -
> > >>> 000000006f598000
> > >>> > > (usable)
> > >>> > > > > > > (XEN)
> > 000000006f598000 -
> > >>> 000000006f59a000
> > >>> > > (reserved)
> > >>> > > > > > > (XEN)
> > 000000006f59a000 -
> > >>> 000000006f5af000
> > >>> > (ACPI
> > >>> > > NVS)
> > >>> > > > > > > (XEN)
> > 000000006f5af000 -
> > >>> 000000006f5d9000
> > >>> > > (reserved)
> > >>> > > > > > > (XEN)
> > 000000006f5d9000 -
> > >>> 000000006f5f9000
> > >>> > (ACPI
> > >>> > > data)
> > >>> > > > > > > (XEN)
> > 000000006f5f9000 -
> > >>> 000000006f6df000
> > >>> > (ACPI
> > >>> > > NVS)
> > >>> > > > > > > (XEN)
> > 000000006f6df000 -
> > >>> 000000006f700000
> > >>> > (ACPI
> > >>> > > data)
> > >>> > > > > > > (XEN)
> > 000000006f700000 -
> > >>> 0000000080000000
> > >>> > > (reserved)
> > >>> > > > > > > (XEN)
> > 00000000a0000000 -
> > >>> 00000000b0000000
> > >>> > > (reserved)
> > >>> > > > > > > (XEN)
> > 00000000fc000000 -
> > >>> 00000000fd000000
> > >>> > > (reserved)
> > >>> > > > > > > (XEN)
> > 00000000fed1c000 -
> > >>> 00000000fed20000
> > >>> > > (reserved)
> > >>> > > > > > > (XEN)
> > 00000000ffc00000 -
> > >>> 0000000100000000
> > >>> > > (reserved)
> > >>> > > > > > > (XEN) System
> RAM:
> > 1780MB
> > >>> (1823000kB)
> > >>> > > > > > > (XEN) ACPI:
> RSDP
> > 000F03F0, 0024 (r2
> > >>> INTEL
> > >>> > )
> > >>> > > > > > > (XEN) ACPI:
> XSDT
> > 6F6FE120, 0064 (r1
> > >>> INTEL
> > >>> > THRLY
> > >>> > > > 0
> > >>> > > > > > 1000013)
> > >>> > > > > > > (XEN) ACPI:
> FACP
> > 6F6FD000, 00F4 (r4
> > >>> INTEL
> > >>> > THRLY
> > >>> > > > 0
> > >>> > > > > MSFT
> > >>> > > > > > 100000D)
> > >>> > > > > > > (XEN) ACPI:
> DSDT
> > 6F6F5000, 74F1 (r2
> > >>> INTEL
> > >>> > THRLY
> > >>> > > > 3
> > >>> > > > > MSFT
> > >>> > > > > > 100000D)
> > >>> > > > > > > (XEN) ACPI:
> FACS
> > 6F5F9000, 0040
> > >>> > > > > > > (XEN) ACPI:
> APIC
> > 6F6F4000, 01CC (r2
> > >>> INTEL
> > >>> > THRLY
> > >>> > > > 0
> > >>> > > > > MSFT
> > >>> > > > > > 100000D)
> > >>> > > > > > > (XEN) ACPI:
> MCFG
> > 6F6F3000, 003C (r1
> > >>> INTEL
> > >>> > THRLY
> > >>> > > > 1
> > >>> > > > > MSFT
> > >>> > > > > > 100000D)
> > >>> > > > > > > (XEN) ACPI:
> HPET
> > 6F6F2000, 0038 (r1
> > >>> INTEL
> > >>> > THRLY
> > >>> > > > 1
> > >>> > > > > MSFT
> > >>> > > > > > 100000D)
> > >>> > > > > > > (XEN) ACPI:
> SLIT
> > 6F6F1000, 0030 (r1
> > >>> INTEL
> > >>> > THRLY
> > >>> > > > 1
> > >>> > > > > MSFT
> > >>> > > > > > 100000D)
> > >>> > > > > > > (XEN) ACPI:
> WDDT
> > 6F6F0000, 0040 (r1
> > >>> INTEL
> > >>> > THRLY
> > >>> > > > 0
> > >>> > > > > MSFT
> > >>> > > > > > 100000D)
> > >>> > > > > > > (XEN) ACPI:
> SSDT
> > 6F5D9000, 1FDDC
> > >>> (r1
> > >>> > INTEL SSDT
> > >>> > > PM
> > >>> > > > 4000
> > >>> > > > > INTL
> > >>> > > > > > 20061109)
> > >>> > > > > > > (XEN) ACPI:
> DMAR
> > 6F6EE000, 01D0 (r1
> > >>> INTEL
&gt

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

WARNING - OLD ARCHIVES

xen-users

Re: [Xen-devel] Re: [Xen-users] pvops dom0 kernel: crash in print_all_I