* RE: Time stopped
@ 2005-10-13 17:29 Ian Pratt
2005-10-13 19:06 ` David F Barrera
0 siblings, 1 reply; 18+ messages in thread
From: Ian Pratt @ 2005-10-13 17:29 UTC (permalink / raw)
To: David F Barrera, xen-devel
> I continue to encounter this problem daily on an IBM xSeries
> 335 SLES 9 SP2, 4GB RAM machine while running XM-TEST. The
> time has not actually stopped, but moves forward at an
> exceedingly slow pace. The 'date'
> command will actually show that a second has transpired in
> the period of, say, 10 actual minutes (or more). 'xm dmesg'
> is showing a trace.
When the machine is in this state, what interrupt rate does
/proc/interrupts show?
If you do a "sleep 1" how long does it sleep for?
I presume both dom0 and the domU experience the time slow down?
If you run something in the background that burns CPU does it make a
difference? In this case, what does xm list show as regards the CPU time
consumed by the domains?
Can you make this happen if you boot the machine with maxcpus=1 ?
Can you narrow down which of the xm-tests actually provoke's the bug?
It's hard to imagine that this bug is PAE specific. Please could you try
booting a non PAE kernel on the machine.
Thanks,
Ian
> x335b:~ # xm list
> Name ID Mem(MiB) CPU VCPUs State Time(s)
> Domain-0 0 495 0 1 r----- 110.9
> 11_create_0 131 16 3 1 -b---- 0.3
> x335b:~ # date
> Thu Oct 13 09:52:23 CDT 2005
> x335b:~ # date
> Thu Oct 13 09:52:23 CDT 2005
> x335b:~ # date
> Thu Oct 13 09:52:23 CDT 2005
> x335b:~ # xm list
> Name ID Mem(MiB) CPU VCPUs State Time(s)
> Domain-0 0 495 0 1 r----- 110.9
> 11_create_0 131 16 3 1 -b---- 0.3
> x335b:~ # date
> Thu Oct 13 09:52:24 CDT 2005
> x335b:~ # date
> Thu Oct 13 09:52:24 CDT 2005
>
> x335b:~ # xm dmesg
> __ __ _____ ___ _ _
> \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| |
> \ // _ \ '_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
> / \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ |
> /_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_|
>
> http://www.cl.cam.ac.uk/netos/xen
> University of Cambridge Computer Laboratory
>
> Xen version 3.0-devel (root@ltc.austin.ibm.com) (gcc version
> 3.3.3 (SuSE Linux)) Thu Oct 13 06:30:24 CDT 2005 Latest
> ChangeSet: Wed Oct 12 10:15:02 2005 +0100 7353:29db5bded574
>
> (XEN) Physical RAM map:
> (XEN) 0000000000000000 - 000000000009d400 (usable)
> (XEN) 000000000009d400 - 00000000000a0000 (reserved)
> (XEN) 00000000000e0000 - 0000000000100000 (reserved)
> (XEN) 0000000000100000 - 00000000f7fec140 (usable)
> (XEN) 00000000f7fec140 - 00000000f7ff0000 (ACPI data)
> (XEN) 00000000f7ff0000 - 00000000f8000000 (reserved)
> (XEN) 00000000fec00000 - 0000000100000000 (reserved)
> (XEN) 0000000100000000 - 0000000108000000 (usable)
> (XEN) System RAM: 4095MB (4193828kB)
> (XEN) Xen heap: 10MB (10496kB)
> (XEN) PAE enabled, limit: 16 GB
> (XEN) found SMP MP-table at 0009d540
> (XEN) DMI 2.3 present.
> (XEN) Using APIC driver default
> (XEN) ACPI: RSDP (v000 IBM ) @
> 0x000fdfc0
> (XEN) ACPI: RSDT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> 0xf7feff80
> (XEN) ACPI: FADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> 0xf7feff00
> (XEN) ACPI: MADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> 0xf7fefe40
> (XEN) ACPI: ASF! (v016 IBM SERONYXP 0x00000001 IBM 0x45444f43) @
> 0xf7fefd80
> (XEN) ACPI: DSDT (v001 IBM SERTURQU 0x00001000 MSFT 0x0100000b) @
> 0x00000000
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> (XEN) Processor #0 15:2 APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
> (XEN) Processor #6 15:2 APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> (XEN) Processor #1 15:2 APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
> (XEN) Processor #7 15:2 APIC version 20
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
> (XEN) ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 14, version 17, address 0xfec00000, GSI 0-15
> (XEN) ACPI: IOAPIC (id[0x0d] address[0xfec01000] gsi_base[16])
> (XEN) IOAPIC[1]: apic_id 13, version 17, address 0xfec01000, GSI 16-31
> (XEN) ACPI: IOAPIC (id[0x0c] address[0xfec02000] gsi_base[32])
> (XEN) IOAPIC[2]: apic_id 12, version 17, address 0xfec02000, GSI 32-47
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> (XEN) ACPI: IRQ0 used by override.
> (XEN) ACPI: IRQ2 used by override.
> (XEN) Enabling APIC mode: Flat. Using 3 I/O APICs
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) Initializing CPU#0
> (XEN) Detected 3189.471 MHz processor.
> (XEN) Using scheduler: Simple EDF Scheduler (sedf)
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> (XEN) CPU: L2 cache: 512K
> (XEN) CPU: L3 cache: 1024K
> (XEN) CPU: Physical Processor ID: 0
> (XEN) CPU0: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
> (XEN) Booting processor 1/1 eip 90000
> (XEN) Initializing CPU#1
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> (XEN) CPU: L2 cache: 512K
> (XEN) CPU: L3 cache: 1024K
> (XEN) CPU: Physical Processor ID: 0
> (XEN) CPU1: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
> (XEN) Booting processor 2/6 eip 90000
> (XEN) Initializing CPU#2
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> (XEN) CPU: L2 cache: 512K
> (XEN) CPU: L3 cache: 1024K
> (XEN) CPU: Physical Processor ID: 3
> (XEN) CPU2: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
> (XEN) Booting processor 3/7 eip 90000
> (XEN) Initializing CPU#3
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> (XEN) CPU: L2 cache: 512K
> (XEN) CPU: L3 cache: 1024K
> (XEN) CPU: Physical Processor ID: 3
> (XEN) CPU3: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
> (XEN) Total of 4 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
> (XEN) checking TSC synchronization across 4 CPUs: passed.
> (XEN) Platform timer is 1.193MHz PIT
> (XEN) Brought up 4 CPUs
> (XEN) mtrr: v2.0 (20020519)
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen-ELF header found:
> 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000
,PAE=yes,LOADER=generic'
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN) Dom0 alloc.: 0000000003800000->0000000004000000 (125952 pages
> to be allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN) Loaded kernel: c0100000->c06394e4
> (XEN) Init. ramdisk: c063a000->c063a000
> (XEN) Phys-Mach map: c063a000->c06b7000
> (XEN) Start info: c06b7000->c06b8000
> (XEN) Page tables: c06b8000->c06c1000
> (XEN) Boot stack: c06c1000->c06c2000
> (XEN) TOTAL: c0000000->c0800000
> (XEN) ENTRY ADDRESS: c0100000
> (XEN) Scrubbing Free
> RAM: ...........................................done.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to
> switch input to Xen).
> (XEN) microcode: CPU1 updated from revision 0x11 to 0x29, date =
> 08112004
> (XEN) microcode: CPU2 updated from revision 0x11 to 0x29, date =
> 08112004
> (XEN) microcode: CPU3 updated from revision 0x11 to 0x29, date =
> 08112004
> (XEN) microcode: CPU0 updated from revision 0x11 to 0x29, date =
> 08112004
> (XEN) mtrr: type mismatch for fd000000,800000 old: write-back new:
> write-combining
> (XEN) mtrr: type mismatch for fd000000,800000 old: write-back new:
> write-combining
> (XEN) Domain 63 (vcpu#0) crashed on cpu#3:
> (XEN) CPU: 3
> (XEN) EIP: e019:[<c01159b6>]
> (XEN) EFLAGS: 00000246 CONTEXT: guest
> (XEN) eax: 00000ac8 ebx: 00000000 ecx: 00000000 edx: 00000000
> (XEN) esi: 00000000 edi: 00000000 ebp: 00000ac8 esp: c0355e8c
> (XEN) cr0: 8005003b cr3: e3b58000
> (XEN) ds: e021 es: e021 fs: 0000 gs: e021 ss: e021 cs: e019
> (XEN) Guest stack trace from esp=c0355e8c:
> (XEN) c0000acc 00000003 c01159b6 0001e019 00010246
> 00000000 00000000
> 00000000
> (XEN) c0000000 c0361875 c1959000 00001000 00000000
> 00000000 c022b738
> c037ed20
> (XEN) 00000000 c0800000 c073e020 00000800 c0361bef
> c073e020 00000400
> c02f0a33
> (XEN) c0355f60 00004000 00000000 00000000 00000000
> 00000000 00004000
> 00000000
> (XEN) 00000004 00000003 c073d018 00000000 c073d000
> 00000000 00000000
> c0362025
> (XEN) c073d000 00000000 c0364880 c0385ff0 c0353060
> c02c7c37 00000000
> c03622f8
> (XEN) 006447ff c02f0a33 c0353060 c035d1e5 c02f0a33
> c0100000 c035d83b
> c0355ff4
> (XEN) c036cbe0 00000080 00000000 0000006c 00000000
> 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000
> 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000
> ffffe000 c073a000
> 00000000
> (XEN) ffffe000 c073a000 00000000 00000000 c0356867
> c0355ff4 00000000
> 00000000
> (XEN) 00000000 00000000 c037e100 0702080b c010007a
> (XEN) (file=memory.c, line=57) Could not allocate order=0
> extent: id=73 flags=0 (13715 of 39271)
> (XEN) Domain 81 (vcpu#0) crashed on cpu#3:
> (XEN) CPU: 3
> (XEN) EIP: e019:[<c01159b6>]
> (XEN) EFLAGS: 00000246 CONTEXT: guest
> (XEN) eax: 000005a8 ebx: 00000000 ecx: 00000000 edx: 00000000
> (XEN) esi: 00000000 edi: 00000000 ebp: 000005a8 esp: c0355e8c
> (XEN) cr0: 8005003b cr3: e2d72000
> (XEN) ds: e021 es: e021 fs: 0000 gs: e021 ss: e021 cs: e019
> (XEN) Guest stack trace from esp=c0355e8c:
> (XEN) c00005ac 00000003 c01159b6 0001e019 00010246
> 00000000 00000000
> 00000000
> (XEN) c0000000 c0361875 c20b5000 00001000 00000000
> 00000000 c022b738
> c037ed20
> (XEN) 00000000 c0800000 c073e020 00000800 c0361bef
> c073e020 00000400
> c02f0a33
> (XEN) c0355f60 00004000 00000000 00000000 00000000
> 00000000 00004000
> 00000000
> (XEN) 00000004 00000003 c073d018 00000000 c073d000
> 00000000 00000000
> c0362025
> (XEN) c073d000 00000000 c0364880 c0385ff0 c0353060
> c02c7c37 00000000
> c03622f8
> (XEN) 006447ff c02f0a33 c0353060 c035d1e5 c02f0a33
> c0100000 c035d83b
> c0355ff4
> (XEN) c036cbe0 00000080 00000000 0000006c 00000000
> 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000
> 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000
> ffffe000 c073a000
> 00000000
> (XEN) ffffe000 c073a000 00000000 00000000 c0356867
> c0355ff4 00000000
> 00000000
> (XEN) 00000000 00000000 c037e100 0702080b c010007a
> (XEN) Domain 102 (vcpu#0) crashed on cpu#3:
> (XEN) CPU: 3
> (XEN) EIP: e019:[<c01159b6>]
> (XEN) EFLAGS: 00000246 CONTEXT: guest
> (XEN) eax: 00000920 ebx: 00000000 ecx: 00000000 edx: 00000000
> (XEN) esi: 00000000 edi: 00000000 ebp: 00000920 esp: c0355e8c
> (XEN) cr0: 8005003b cr3: f293e000
> (XEN) ds: e021 es: e021 fs: 0000 gs: e021 ss: e021 cs: e019
> (XEN) Guest stack trace from esp=c0355e8c:
> (XEN) c0000924 00000003 c01159b6 0001e019 00010246
> 00000000 00000000
> 00000000
> (XEN) c0000000 c0361875 c2124000 00001000 00000000
> 00000000 c022b738
> c037ed20
> (XEN) 00000000 c0800000 c073e020 00000800 c0361bef
> c073e020 00000400
> c02f0a33
> (XEN) c0355f60 00004000 00000000 00000000 00000000
> 00000000 00004000
> 00000000
> (XEN) 00000004 00000003 c073d018 00000000 c073d000
> 00000000 00000000
> c0362025
> (XEN) c073d000 00000000 c0364880 c0385ff0 c0353060
> c02c7c37 00000000
> c03622f8
> (XEN) 006447ff c02f0a33 c0353060 c035d1e5 c02f0a33
> c0100000 c035d83b
> c0355ff4
> (XEN) c036cbe0 00000080 00000000 0000006c 00000000
> 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000
> 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000
> ffffe000 c073a000
> 00000000
> (XEN) ffffe000 c073a000 00000000 00000000 c0356867
> c0355ff4 00000000
> 00000000
> (XEN) 00000000 00000000 c037e100 0702080b c010007a
>
>
> x335b:~ # dmesg
> Linux version 2.6.12-xen0 (root@x335b) (gcc version 3.3.3
> (SuSE Linux))
> #1 Thu Oct 13 06:38:56 CDT 2005
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 000000001f400000 (usable) 0MB
> HIGHMEM available.
> 500MB LOWMEM available.
> On node 0 totalpages: 128000
> DMA zone: 128000 pages, LIFO batch:31
> Normal zone: 0 pages, LIFO batch:1
> HighMem zone: 0 pages, LIFO batch:1
> DMI 2.3 present.
> ACPI: RSDP (v000 IBM ) @ 0x000fdfc0
> ACPI: RSDT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> 0xf7feff80
> ACPI: FADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> 0xf7feff00
> ACPI: MADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> 0xf7fefe40
> ACPI: ASF! (v016 IBM SERONYXP 0x00000001 IBM 0x45444f43) @
> 0xf7fefd80
> ACPI: DSDT (v001 IBM SERTURQU 0x00001000 MSFT 0x0100000b) @
> 0x00000000
> ACPI: Local APIC address 0xfee00000
> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
> ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
> ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
> ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0])
> IOAPIC[0]: apic_id 14, version 17, address 0xfec00000, GSI 0-15
> ACPI: IOAPIC (id[0x0d] address[0xfec01000] gsi_base[16])
> IOAPIC[1]: apic_id 13, version 17, address 0xfec01000, GSI 16-31
> ACPI: IOAPIC (id[0x0c] address[0xfec02000] gsi_base[32])
> IOAPIC[2]: apic_id 12, version 17, address 0xfec02000, GSI 32-47
> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> ACPI: IRQ0 used by override.
> ACPI: IRQ2 used by override.
> ACPI: IRQ5 used by override.
> Enabling APIC mode: Flat. Using 3 I/O APICs Using ACPI
> (MADT) for SMP configuration information IRQ lockup detection
> disabled Allocating PCI resources starting at f8000000 (gap:
> f8000000:06c00000) Built 1 zonelists Kernel command line:
> root=/dev/sda2 ro console=tty0 Initializing CPU#0 PID hash
> table entries: 2048 (order: 11, 32768 bytes) Xen reported:
> 3189.368 MHz processor.
> Console: colour VGA+ 80x25
> Dentry cache hash table entries: 65536 (order: 6, 262144
> bytes) Inode-cache hash table entries: 32768 (order: 5,
> 131072 bytes) Software IO TLB enabled:
> Aperture: 64 megabytes
> Bus range: 0x0000000004000000 - 0x0000000008000000
> Kernel range: 0x00000000c1456000 - 0x00000000c5456000
> vmalloc area: e0000000-f53fe000, maxmem 2d800000
> Memory: 434560k/512000k available (3563k kernel code, 77308k
> reserved, 1134k data, 356k init, 0k highmem) Checking if this
> processor honours the WP bit even in supervisor mode...
> Ok.
> Calibrating delay loop... 6370.09 BogoMIPS (lpj=31850496)
> Mount-cache hash table entries: 512
> CPU: After generic identify, caps: bfebfbff 00000000 00000000
> 00000000 00004400 00000000 00000000
> CPU: After vendor identify, caps: bfebfbff 00000000 00000000
> 00000000 00004400 00000000 00000000
> CPU: Trace cache: 12K uops, L1 D cache: 8K
> CPU: L2 cache: 512K
> CPU: L3 cache: 1024K
> CPU: After all inits, caps: bfebd3f1 00000000 00000000
> 00000080 00004400 00000000 00000000
> CPU: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05 Enabling fast
> FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... disabled
> ENABLING IO-APIC IRQs
> NET: Registered protocol family 16
> PCI: Using configuration type 1
> ACPI: Subsystem revision 20050309
> ACPI: Interpreter enabled
> ACPI: Using IOAPIC for interrupt routing
> ACPI: PCI Root Bridge [PCI0] (0000:00)
> PCI: Probing PCI hardware (bus 00)
> Boot video device is 0000:00:01.0
> PCI: Ignoring BAR0-3 of IDE controller 0000:00:0f.1
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> ACPI: PCI Root Bridge [PCI1] (0000:01)
> PCI: Probing PCI hardware (bus 01)
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI1._PRT]
> ACPI: PCI Root Bridge [PCI2] (0000:02)
> PCI: Probing PCI hardware (bus 02)
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI2._PRT]
> ACPI: PCI Interrupt Link [LP00] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP01] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP02] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP03] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP04] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP05] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP06] (IRQs *9)
> ACPI: PCI Interrupt Link [LP07] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP08] (IRQs *3)
> ACPI: PCI Interrupt Link [LP09] (IRQs *4)
> ACPI: PCI Interrupt Link [LP0A] (IRQs *10)
> ACPI: PCI Interrupt Link [LP0B] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP0C] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP0D] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP0E] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP0F] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP10] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP11] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP12] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP13] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP14] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP15] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP16] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP17] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP18] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP19] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP1A] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP1B] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP1C] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP1D] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP1E] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP1F] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LPUS] (IRQs *11)
> xen_mem: Initialising balloon driver.
> SCSI subsystem initialized
> usbcore: registered new driver hub
> PCI: Using ACPI for IRQ routing
> PCI: If a device doesn't work, try "pci=routeirq". If it
> helps, post a report Grant table initialized
> IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com>
> Initializing Cryptographic API
> serio: i8042 AUX port at 0x60,0x64 irq 12
> serio: i8042 KBD port at 0x60,0x64 irq 1 io scheduler noop
> registered io scheduler anticipatory registered io scheduler
> deadline registered io scheduler cfq registered Floppy
> drive(s): fd0 is 1.44M FDC 0 is a National Semiconductor
> PC87306 RAMDISK driver initialized: 16 RAM disks of 4096K
> size 1024 blocksize
> loop: loaded (max 8 devices)
> HP CISS Driver (v 2.6.6)
> Intel(R) PRO/1000 Network Driver - version 6.0.54-k2
> Copyright (c) 1999-2004 Intel Corporation.
> pcnet32.c:v1.30j 29.04.2005 tsbogend@alpha.franken.de
> e100: Intel(R) PRO/100 Network Driver, 3.4.8-k2-NAPI
> e100: Copyright(c) 1999-2005 Intel Corporation
> tg3.c:v3.31 (June 8, 2005)
> ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 24 (level, low) -> IRQ 24
> eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-
> bit) 10/100/1000BaseT Ethernet 00:11:25:3e:39:f2
> eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0]
> WireSpeed[1] TSOcap[1]
> eth0: dma_rwctrl[769f4000]
> ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 25 (level, low) -> IRQ 25
> eth1: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-
> bit) 10/100/1000BaseT Ethernet 00:11:25:3e:39:f3
> eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0]
> WireSpeed[1] TSOcap[1]
> eth1: dma_rwctrl[769f4000]
> tun: Universal TUN/TAP device driver, 1.6
> tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> Xen
> virtual console successfully installed as ttyS0 Event-channel
> device installed.
> xen_net: Initialising Xen netif backend.
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override
> with idebus=xx SvrWks CSB5: IDE controller at PCI slot
> 0000:00:0f.1 SvrWks CSB5: chipset revision 147 SvrWks CSB5:
> not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0x0700-0x0707, BIOS settings: hda:pio, hdb:pio
> ide1: BM-DMA at 0x0708-0x070f, BIOS settings: hdc:DMA,
> hdd:DMA Probing IDE interface ide0...
> Probing IDE interface ide1...
> hdc: LG CD-ROM CRN-8245B, ATAPI CD/DVD-ROM drive
> ide1 at 0x170-0x177,0x376 on irq 15
> Probing IDE interface ide0...
> Probing IDE interface ide2...
> Probing IDE interface ide3...
> Probing IDE interface ide4...
> Probing IDE interface ide5...
> hdc: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33) Uniform
> CD-ROM driver Revision: 3.20 Red Hat/Adaptec aacraid driver
> (1.1.2-lk2 Oct 13 2005) 3ware Storage Controller device
> driver for Linux v1.26.02.001.
> libata version 1.11 loaded.
> Fusion MPT base driver 3.01.20
> Copyright (c) 1999-2004 LSI Logic Corporation
> ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 22 (level, low) -> IRQ 22
> mptbase: Initiating ioc0 bringup
> ioc0: 53C1030: Capabilities={Initiator}
> Fusion MPT SCSI Host driver 3.01.20
> scsi0 : ioc0: LSI53C1030, FwRev=01000e00h, Ports=1, MaxQ=222, IRQ=22
> Vendor: IBM-ESXS Model: MAS3367NC FN Rev: C901
> Type: Direct-Access ANSI SCSI revision: 03
> SCSI device sda: 71096640 512-byte hdwr sectors (36401 MB)
> SCSI device sda: drive cache: write through SCSI device sda:
> 71096640 512-byte hdwr sectors (36401 MB) SCSI device sda:
> drive cache: write through
> sda: sda1 sda2
> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
> Vendor: IBM-ESXS Model: MAS3367NC FN Rev: C901
> Type: Direct-Access ANSI SCSI revision: 03
> SCSI device sdb: 71096640 512-byte hdwr sectors (36401 MB)
> SCSI device sdb: drive cache: write through SCSI device sdb:
> 71096640 512-byte hdwr sectors (36401 MB) SCSI device sdb:
> drive cache: write through
> sdb: sdb1 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 >
> Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
> Vendor: IBM Model: 25P3495a S320 1 Rev: 1
> Type: Processor ANSI SCSI revision: 02
> usbmon: debugs is not available
> ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI)
> Driver (PCI)
> ACPI: PCI Interrupt Link [LPUS] enabled at IRQ 11
> ACPI: PCI Interrupt 0000:00:0f.2[A] -> Link [LPUS] -> GSI 11 (level,
> low) -> IRQ 11
> ohci_hcd 0000:00:0f.2: OHCI Host Controller ohci_hcd
> 0000:00:0f.2: new USB bus registered, assigned bus number 1
> ohci_hcd 0000:00:0f.2: irq 11, io mem 0xfebfe000 hub 1-0:1.0:
> USB hub found hub 1-0:1.0: 4 ports detected USB Universal
> Host Controller Interface driver v2.2
> usbcore: registered new driver usbhid
> drivers/usb/input/hid-core.c: v2.01:USB HID core driver
> mice: PS/2 mouse device common for all mice
> md: raid0 personality registered as nr 2
> md: raid1 personality registered as nr 3
> md: raid5 personality registered as nr 4
> raid5: automatically using best checksumming function: pIII_sse
> pIII_sse : 1466.000 MB/sec
> raid5: using function: pIII_sse (1466.000 MB/sec)
> md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
> device-mapper: 4.4.0-ioctl (2005-01-12) initialised:
> dm-devel@redhat.com
> NET: Registered protocol family 2
> input: AT Translated Set 2 keyboard on isa0060/serio0
> IP: routing cache hash table of 4096 buckets, 32Kbytes TCP
> established hash table entries: 16384 (order: 5, 131072
> bytes) TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
> TCP: Hash tables configured (established 16384 bind 16384)
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> input: PS/2 Generic Mouse on isa0060/serio1 Bridge
> firewalling registered
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> EXT3-fs: mounted filesystem with ordered data mode.
> VFS: Mounted root (ext3 filesystem) readonly.
> Freeing unused kernel memory: 356k freed kjournald starting.
> Commit interval 5 seconds
> EXT3 (no)acl options not supported
> EXT3 (no)acl options not supported
> EXT3 FS on sda2, internal journal
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> Adding 1052216k swap on /dev/sda1. Priority:42 extents:1
> tg3: eth0: Link is up at 100 Mbps, full duplex.
> tg3: eth0: Flow control is on for TX and on for RX.
> Linux agpgart interface v0.101 (c) Dave Jones
> ACPI: Power Button (FF) [PWRF]
> end_request: I/O error, dev fd0, sector 0
> end_request: I/O error, dev fd0, sector 0 program hwscan is
> using a deprecated SCSI ioctl, please convert it to SG_IO
> program hwscan is using a deprecated SCSI ioctl, please
> convert it to SG_IO
> end_request: I/O error, dev fd0, sector 0
> end_request: I/O error, dev fd0, sector 0 nfs warning: mount
> version older than kernel device vif0.0 entered promiscuous mode
> bridge: can't decode speed from peth0: 0 device peth0 entered
> promiscuous mode
> xen-br0: port 1(vif0.0) entering learning state
> xen-br0: topology change detected, propagating
> xen-br0: port 1(vif0.0) entering forwarding state
> tg3: peth0: Link is up at 100 Mbps, full duplex.
> tg3: peth0: Flow control is on for TX and on for RX.
> xen-br0: port 2(peth0) entering learning state
> xen-br0: topology change detected, propagating
> xen-br0: port 2(peth0) entering forwarding state device
> vif74.1 entered promiscuous mode
> xen-br0: port 3(vif74.1) entering learning state
> xen-br0: topology change detected, propagating
> xen-br0: port 3(vif74.1) entering forwarding state device
> vif75.1 entered promiscuous mode
> xen-br0: port 4(vif75.1) entering learning state
> xen-br0: topology change detected, propagating
> xen-br0: port 4(vif75.1) entering forwarding state
> xen-br0: port 4(vif75.1) entering disabled state device
> vif75.1 left promiscuous mode
> xen-br0: port 4(vif75.1) entering disabled state device
> vif76.1 entered promiscuous mode
> xen-br0: port 4(vif76.1) entering learning state
> xen-br0: topology change detected, propagating
> xen-br0: port 4(vif76.1) entering forwarding state device
> vif77.1 entered promiscuous mode
> xen-br0: port 5(vif77.1) entering learning state
> xen-br0: topology change detected, propagating
> xen-br0: port 5(vif77.1) entering forwarding state x335b:~ #
>
> The last output from 'xm-test' is:
>
> x335b:/tmp/logs/xm-test # tail x335sles9_pae4gb.output Using
> config file "/dev/null".
> Started domain testdomain
> [dom0] Running `xm destroy testdomain'
>
> [dom0] Running `xm create /dev/null
> ramdisk=../../ramdisk/initrd.img
> kernel=/boot/vmlinuz-2.6.12-xenU name=testdomain nics=0 vcpus=1
> memory=64 root=/dev/ram0'
> Using config file "/dev/null".
> Started domain testdomain
> [dom0] Running `xm destroy testdomain'
>
> PASS: 10_create_fastdestroy.test
> x335b:/tmp/logs/xm-test #
>
>
> On Wed, 2005-09-28 at 15:24 -0500, David F Barrera wrote:
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=265
> >
> > While running xm-test on two IBM xSeries 335s, one FC4 and
> the other
> > one SLES 9, I noticed that time has stopped:
> >
> > [root@x335a xm-test]# date
> > Wed Sep 28 13:59:18 CDT 2005
> > [root@x335a xm-test]# date
> > Wed Sep 28 13:59:18 CDT 2005
> >
> > >> 15 minutes later,
> > [root@x335a xm-test]# date
> > Wed Sep 28 13:59:18 CDT 2005
> > [root@x335a xm-test]#
> >
> > changeset: 7076:46046d5fb354
> > tag: tip
> > user: emellor@ewan
> > date: Tue Sep 27 16:09:46 2005 +0100
> > summary: Remove unused import, mark unused variables.
> >
> > The last output lines produced by xm-test are:
> > cp 06_destroy_dom0_neg.py 06_destroy_dom0_neg.test chmod +x
> > 06_destroy_dom0_neg.test
> >
> > The machines in question are running xm-test at the moment
> and appear
> > 'stuck'.
> > Both are displaying the "(XEN) Ouch! We are seriously
> BEHIND schedule!"
> > messages. However, the static time issue may not be related
> to the Ouch!
> > issue, bug # 257, as Paul Larson observed it on a machine
> that was not
> > running xm-test at the time, hence we are submitting it as
> a different
> > bug.
> >
> >
> --
> Regards,
>
> David F Barrera
> Linux Technology Center
> Systems and Technology Group, IBM
>
> "The wisest men follow their own direction. "
> Euripides
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
^ permalink raw reply [flat|nested] 18+ messages in thread* RE: Time stopped
2005-10-13 17:29 Time stopped Ian Pratt
@ 2005-10-13 19:06 ` David F Barrera
2005-10-13 19:21 ` Dan Smith
0 siblings, 1 reply; 18+ messages in thread
From: David F Barrera @ 2005-10-13 19:06 UTC (permalink / raw)
To: Ian Pratt; +Cc: xen-devel
Recreated the situation on non-PAE kernel on the same machine.
On Thu, 2005-10-13 at 18:29 +0100, Ian Pratt wrote:
>
> When the machine is in this state, what interrupt rate does
> /proc/interrupts show?
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9646 Phys-irq ioc0
24: 8719 Phys-irq peth0
256: 306649 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 12123 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
>
>
> If you do a "sleep 1" how long does it sleep for?
In this case, it slept for about 3 real minutes.
>
> I presume both dom0 and the domU experience the time slow down?
Correct.
>
> If you run something in the background that burns CPU does it make a
> difference?
I started LTP on dom0 ( and can see console outpu) and it makes no
difference.
> In this case, what does xm list show as regards the CPU time
> consumed by the domains?
x335b:/tmp/ltp-full-20050804 # date
Thu Oct 13 13:47:59 CDT 2005
x335b:/tmp/ltp-full-20050804 # xm list
Name ID Mem(MiB) CPU VCPUs State Time(s)
Domain-0 0 495 - 4 r----- 96.5
11_create_0 73 16 3 1 -b---- 0.3
x335b:/tmp/ltp-full-20050804 # xm list
Name ID Mem(MiB) CPU VCPUs State Time(s)
Domain-0 0 495 - 4 r----- 96.5
11_create_0 73 16 3 1 -b---- 0.3
x335b:/tmp/ltp-full-20050804 # xm list
Name ID Mem(MiB) CPU VCPUs State Time(s)
Domain-0 0 495 - 4 r----- 96.5
11_create_0 73 16 3 1 -b---- 0.3
x335b:/tmp/ltp-full-20050804 #
x335b:/tmp/ltp-full-20050804 # date
Thu Oct 13 13:47:59 CDT 2005
>
> Can you make this happen if you boot the machine with maxcpus=1 ?
Will try that now and report later.
>
> Can you narrow down which of the xm-tests actually provoke's the bug?
Tailing the xm-output file:
x335b:/tmp/logs/xm-test # tail x335sles9_pae4gb.output
Using config file "/dev/null".
Started domain testdomain
[dom0] Running `xm destroy testdomain'
[dom0] Running `xm create /dev/null ramdisk=../../ramdisk/initrd.img
kernel=/boot/vmlinuz-2.6.12-xenU name=testdomain nics=0 vcpus=1
memory=64 root=/dev/ram0'
Using config file "/dev/null".
Started domain testdomain
[dom0] Running `xm destroy testdomain'
PASS: 10_create_fastdestroy.test
--------------------------xm list output:
x335b:/tmp/logs/xm-test # xm list
Name ID Mem(MiB) CPU VCPUs State Time(s)
Domain-0 0 495 - 4 r----- 96.5
11_create_0 73 16 3 1 -b---- 0.3
x335b:/tmp/logs/xm-test #
>
> It's hard to imagine that this bug is PAE specific. Please could you try
> booting a non PAE kernel on the machine.
Right. This recreate was done on a non-PAE kernel.
>
> Thanks,
> Ian
>
>
> > x335b:~ # xm list
> > Name ID Mem(MiB) CPU VCPUs State Time(s)
> > Domain-0 0 495 0 1 r----- 110.9
> > 11_create_0 131 16 3 1 -b---- 0.3
> > x335b:~ # date
> > Thu Oct 13 09:52:23 CDT 2005
> > x335b:~ # date
> > Thu Oct 13 09:52:23 CDT 2005
> > x335b:~ # date
> > Thu Oct 13 09:52:23 CDT 2005
> > x335b:~ # xm list
> > Name ID Mem(MiB) CPU VCPUs State Time(s)
> > Domain-0 0 495 0 1 r----- 110.9
> > 11_create_0 131 16 3 1 -b---- 0.3
> > x335b:~ # date
> > Thu Oct 13 09:52:24 CDT 2005
> > x335b:~ # date
> > Thu Oct 13 09:52:24 CDT 2005
> >
> > x335b:~ # xm dmesg
> > __ __ _____ ___ _ _
> > \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| |
> > \ // _ \ '_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
> > / \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ |
> > /_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_|
> >
> > http://www.cl.cam.ac.uk/netos/xen
> > University of Cambridge Computer Laboratory
> >
> > Xen version 3.0-devel (root@ltc.austin.ibm.com) (gcc version
> > 3.3.3 (SuSE Linux)) Thu Oct 13 06:30:24 CDT 2005 Latest
> > ChangeSet: Wed Oct 12 10:15:02 2005 +0100 7353:29db5bded574
> >
> > (XEN) Physical RAM map:
> > (XEN) 0000000000000000 - 000000000009d400 (usable)
> > (XEN) 000000000009d400 - 00000000000a0000 (reserved)
> > (XEN) 00000000000e0000 - 0000000000100000 (reserved)
> > (XEN) 0000000000100000 - 00000000f7fec140 (usable)
> > (XEN) 00000000f7fec140 - 00000000f7ff0000 (ACPI data)
> > (XEN) 00000000f7ff0000 - 00000000f8000000 (reserved)
> > (XEN) 00000000fec00000 - 0000000100000000 (reserved)
> > (XEN) 0000000100000000 - 0000000108000000 (usable)
> > (XEN) System RAM: 4095MB (4193828kB)
> > (XEN) Xen heap: 10MB (10496kB)
> > (XEN) PAE enabled, limit: 16 GB
> > (XEN) found SMP MP-table at 0009d540
> > (XEN) DMI 2.3 present.
> > (XEN) Using APIC driver default
> > (XEN) ACPI: RSDP (v000 IBM ) @
> > 0x000fdfc0
> > (XEN) ACPI: RSDT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> > 0xf7feff80
> > (XEN) ACPI: FADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> > 0xf7feff00
> > (XEN) ACPI: MADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> > 0xf7fefe40
> > (XEN) ACPI: ASF! (v016 IBM SERONYXP 0x00000001 IBM 0x45444f43) @
> > 0xf7fefd80
> > (XEN) ACPI: DSDT (v001 IBM SERTURQU 0x00001000 MSFT 0x0100000b) @
> > 0x00000000
> > (XEN) ACPI: Local APIC address 0xfee00000
> > (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> > (XEN) Processor #0 15:2 APIC version 20
> > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
> > (XEN) Processor #6 15:2 APIC version 20
> > (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> > (XEN) Processor #1 15:2 APIC version 20
> > (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
> > (XEN) Processor #7 15:2 APIC version 20
> > (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
> > (XEN) ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
> > (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
> > (XEN) ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
> > (XEN) ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0])
> > (XEN) IOAPIC[0]: apic_id 14, version 17, address 0xfec00000, GSI 0-15
> > (XEN) ACPI: IOAPIC (id[0x0d] address[0xfec01000] gsi_base[16])
> > (XEN) IOAPIC[1]: apic_id 13, version 17, address 0xfec01000, GSI 16-31
> > (XEN) ACPI: IOAPIC (id[0x0c] address[0xfec02000] gsi_base[32])
> > (XEN) IOAPIC[2]: apic_id 12, version 17, address 0xfec02000, GSI 32-47
> > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> > (XEN) ACPI: IRQ0 used by override.
> > (XEN) ACPI: IRQ2 used by override.
> > (XEN) Enabling APIC mode: Flat. Using 3 I/O APICs
> > (XEN) Using ACPI (MADT) for SMP configuration information
> > (XEN) Initializing CPU#0
> > (XEN) Detected 3189.471 MHz processor.
> > (XEN) Using scheduler: Simple EDF Scheduler (sedf)
> > (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> > (XEN) CPU: L2 cache: 512K
> > (XEN) CPU: L3 cache: 1024K
> > (XEN) CPU: Physical Processor ID: 0
> > (XEN) CPU0: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
> > (XEN) Booting processor 1/1 eip 90000
> > (XEN) Initializing CPU#1
> > (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> > (XEN) CPU: L2 cache: 512K
> > (XEN) CPU: L3 cache: 1024K
> > (XEN) CPU: Physical Processor ID: 0
> > (XEN) CPU1: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
> > (XEN) Booting processor 2/6 eip 90000
> > (XEN) Initializing CPU#2
> > (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> > (XEN) CPU: L2 cache: 512K
> > (XEN) CPU: L3 cache: 1024K
> > (XEN) CPU: Physical Processor ID: 3
> > (XEN) CPU2: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
> > (XEN) Booting processor 3/7 eip 90000
> > (XEN) Initializing CPU#3
> > (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> > (XEN) CPU: L2 cache: 512K
> > (XEN) CPU: L3 cache: 1024K
> > (XEN) CPU: Physical Processor ID: 3
> > (XEN) CPU3: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
> > (XEN) Total of 4 processors activated.
> > (XEN) ENABLING IO-APIC IRQs
> > (XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
> > (XEN) checking TSC synchronization across 4 CPUs: passed.
> > (XEN) Platform timer is 1.193MHz PIT
> > (XEN) Brought up 4 CPUs
> > (XEN) mtrr: v2.0 (20020519)
> > (XEN) *** LOADING DOMAIN 0 ***
> > (XEN) Xen-ELF header found:
> > 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000
> ,PAE=yes,LOADER=generic'
> > (XEN) PHYSICAL MEMORY ARRANGEMENT:
> > (XEN) Dom0 alloc.: 0000000003800000->0000000004000000 (125952 pages
> > to be allocated)
> > (XEN) VIRTUAL MEMORY ARRANGEMENT:
> > (XEN) Loaded kernel: c0100000->c06394e4
> > (XEN) Init. ramdisk: c063a000->c063a000
> > (XEN) Phys-Mach map: c063a000->c06b7000
> > (XEN) Start info: c06b7000->c06b8000
> > (XEN) Page tables: c06b8000->c06c1000
> > (XEN) Boot stack: c06c1000->c06c2000
> > (XEN) TOTAL: c0000000->c0800000
> > (XEN) ENTRY ADDRESS: c0100000
> > (XEN) Scrubbing Free
> > RAM: ...........................................done.
> > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to
> > switch input to Xen).
> > (XEN) microcode: CPU1 updated from revision 0x11 to 0x29, date =
> > 08112004
> > (XEN) microcode: CPU2 updated from revision 0x11 to 0x29, date =
> > 08112004
> > (XEN) microcode: CPU3 updated from revision 0x11 to 0x29, date =
> > 08112004
> > (XEN) microcode: CPU0 updated from revision 0x11 to 0x29, date =
> > 08112004
> > (XEN) mtrr: type mismatch for fd000000,800000 old: write-back new:
> > write-combining
> > (XEN) mtrr: type mismatch for fd000000,800000 old: write-back new:
> > write-combining
> > (XEN) Domain 63 (vcpu#0) crashed on cpu#3:
> > (XEN) CPU: 3
> > (XEN) EIP: e019:[<c01159b6>]
> > (XEN) EFLAGS: 00000246 CONTEXT: guest
> > (XEN) eax: 00000ac8 ebx: 00000000 ecx: 00000000 edx: 00000000
> > (XEN) esi: 00000000 edi: 00000000 ebp: 00000ac8 esp: c0355e8c
> > (XEN) cr0: 8005003b cr3: e3b58000
> > (XEN) ds: e021 es: e021 fs: 0000 gs: e021 ss: e021 cs: e019
> > (XEN) Guest stack trace from esp=c0355e8c:
> > (XEN) c0000acc 00000003 c01159b6 0001e019 00010246
> > 00000000 00000000
> > 00000000
> > (XEN) c0000000 c0361875 c1959000 00001000 00000000
> > 00000000 c022b738
> > c037ed20
> > (XEN) 00000000 c0800000 c073e020 00000800 c0361bef
> > c073e020 00000400
> > c02f0a33
> > (XEN) c0355f60 00004000 00000000 00000000 00000000
> > 00000000 00004000
> > 00000000
> > (XEN) 00000004 00000003 c073d018 00000000 c073d000
> > 00000000 00000000
> > c0362025
> > (XEN) c073d000 00000000 c0364880 c0385ff0 c0353060
> > c02c7c37 00000000
> > c03622f8
> > (XEN) 006447ff c02f0a33 c0353060 c035d1e5 c02f0a33
> > c0100000 c035d83b
> > c0355ff4
> > (XEN) c036cbe0 00000080 00000000 0000006c 00000000
> > 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000
> > 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000
> > ffffe000 c073a000
> > 00000000
> > (XEN) ffffe000 c073a000 00000000 00000000 c0356867
> > c0355ff4 00000000
> > 00000000
> > (XEN) 00000000 00000000 c037e100 0702080b c010007a
> > (XEN) (file=memory.c, line=57) Could not allocate order=0
> > extent: id=73 flags=0 (13715 of 39271)
> > (XEN) Domain 81 (vcpu#0) crashed on cpu#3:
> > (XEN) CPU: 3
> > (XEN) EIP: e019:[<c01159b6>]
> > (XEN) EFLAGS: 00000246 CONTEXT: guest
> > (XEN) eax: 000005a8 ebx: 00000000 ecx: 00000000 edx: 00000000
> > (XEN) esi: 00000000 edi: 00000000 ebp: 000005a8 esp: c0355e8c
> > (XEN) cr0: 8005003b cr3: e2d72000
> > (XEN) ds: e021 es: e021 fs: 0000 gs: e021 ss: e021 cs: e019
> > (XEN) Guest stack trace from esp=c0355e8c:
> > (XEN) c00005ac 00000003 c01159b6 0001e019 00010246
> > 00000000 00000000
> > 00000000
> > (XEN) c0000000 c0361875 c20b5000 00001000 00000000
> > 00000000 c022b738
> > c037ed20
> > (XEN) 00000000 c0800000 c073e020 00000800 c0361bef
> > c073e020 00000400
> > c02f0a33
> > (XEN) c0355f60 00004000 00000000 00000000 00000000
> > 00000000 00004000
> > 00000000
> > (XEN) 00000004 00000003 c073d018 00000000 c073d000
> > 00000000 00000000
> > c0362025
> > (XEN) c073d000 00000000 c0364880 c0385ff0 c0353060
> > c02c7c37 00000000
> > c03622f8
> > (XEN) 006447ff c02f0a33 c0353060 c035d1e5 c02f0a33
> > c0100000 c035d83b
> > c0355ff4
> > (XEN) c036cbe0 00000080 00000000 0000006c 00000000
> > 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000
> > 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000
> > ffffe000 c073a000
> > 00000000
> > (XEN) ffffe000 c073a000 00000000 00000000 c0356867
> > c0355ff4 00000000
> > 00000000
> > (XEN) 00000000 00000000 c037e100 0702080b c010007a
> > (XEN) Domain 102 (vcpu#0) crashed on cpu#3:
> > (XEN) CPU: 3
> > (XEN) EIP: e019:[<c01159b6>]
> > (XEN) EFLAGS: 00000246 CONTEXT: guest
> > (XEN) eax: 00000920 ebx: 00000000 ecx: 00000000 edx: 00000000
> > (XEN) esi: 00000000 edi: 00000000 ebp: 00000920 esp: c0355e8c
> > (XEN) cr0: 8005003b cr3: f293e000
> > (XEN) ds: e021 es: e021 fs: 0000 gs: e021 ss: e021 cs: e019
> > (XEN) Guest stack trace from esp=c0355e8c:
> > (XEN) c0000924 00000003 c01159b6 0001e019 00010246
> > 00000000 00000000
> > 00000000
> > (XEN) c0000000 c0361875 c2124000 00001000 00000000
> > 00000000 c022b738
> > c037ed20
> > (XEN) 00000000 c0800000 c073e020 00000800 c0361bef
> > c073e020 00000400
> > c02f0a33
> > (XEN) c0355f60 00004000 00000000 00000000 00000000
> > 00000000 00004000
> > 00000000
> > (XEN) 00000004 00000003 c073d018 00000000 c073d000
> > 00000000 00000000
> > c0362025
> > (XEN) c073d000 00000000 c0364880 c0385ff0 c0353060
> > c02c7c37 00000000
> > c03622f8
> > (XEN) 006447ff c02f0a33 c0353060 c035d1e5 c02f0a33
> > c0100000 c035d83b
> > c0355ff4
> > (XEN) c036cbe0 00000080 00000000 0000006c 00000000
> > 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000
> > 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000
> > ffffe000 c073a000
> > 00000000
> > (XEN) ffffe000 c073a000 00000000 00000000 c0356867
> > c0355ff4 00000000
> > 00000000
> > (XEN) 00000000 00000000 c037e100 0702080b c010007a
> >
> >
> > x335b:~ # dmesg
> > Linux version 2.6.12-xen0 (root@x335b) (gcc version 3.3.3
> > (SuSE Linux))
> > #1 Thu Oct 13 06:38:56 CDT 2005
> > BIOS-provided physical RAM map:
> > Xen: 0000000000000000 - 000000001f400000 (usable) 0MB
> > HIGHMEM available.
> > 500MB LOWMEM available.
> > On node 0 totalpages: 128000
> > DMA zone: 128000 pages, LIFO batch:31
> > Normal zone: 0 pages, LIFO batch:1
> > HighMem zone: 0 pages, LIFO batch:1
> > DMI 2.3 present.
> > ACPI: RSDP (v000 IBM ) @ 0x000fdfc0
> > ACPI: RSDT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> > 0xf7feff80
> > ACPI: FADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> > 0xf7feff00
> > ACPI: MADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> > 0xf7fefe40
> > ACPI: ASF! (v016 IBM SERONYXP 0x00000001 IBM 0x45444f43) @
> > 0xf7fefd80
> > ACPI: DSDT (v001 IBM SERTURQU 0x00001000 MSFT 0x0100000b) @
> > 0x00000000
> > ACPI: Local APIC address 0xfee00000
> > ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> > ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
> > ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> > ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
> > ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
> > ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0])
> > IOAPIC[0]: apic_id 14, version 17, address 0xfec00000, GSI 0-15
> > ACPI: IOAPIC (id[0x0d] address[0xfec01000] gsi_base[16])
> > IOAPIC[1]: apic_id 13, version 17, address 0xfec01000, GSI 16-31
> > ACPI: IOAPIC (id[0x0c] address[0xfec02000] gsi_base[32])
> > IOAPIC[2]: apic_id 12, version 17, address 0xfec02000, GSI 32-47
> > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> > ACPI: IRQ0 used by override.
> > ACPI: IRQ2 used by override.
> > ACPI: IRQ5 used by override.
> > Enabling APIC mode: Flat. Using 3 I/O APICs Using ACPI
> > (MADT) for SMP configuration information IRQ lockup detection
> > disabled Allocating PCI resources starting at f8000000 (gap:
> > f8000000:06c00000) Built 1 zonelists Kernel command line:
> > root=/dev/sda2 ro console=tty0 Initializing CPU#0 PID hash
> > table entries: 2048 (order: 11, 32768 bytes) Xen reported:
> > 3189.368 MHz processor.
> > Console: colour VGA+ 80x25
> > Dentry cache hash table entries: 65536 (order: 6, 262144
> > bytes) Inode-cache hash table entries: 32768 (order: 5,
> > 131072 bytes) Software IO TLB enabled:
> > Aperture: 64 megabytes
> > Bus range: 0x0000000004000000 - 0x0000000008000000
> > Kernel range: 0x00000000c1456000 - 0x00000000c5456000
> > vmalloc area: e0000000-f53fe000, maxmem 2d800000
> > Memory: 434560k/512000k available (3563k kernel code, 77308k
> > reserved, 1134k data, 356k init, 0k highmem) Checking if this
> > processor honours the WP bit even in supervisor mode...
> > Ok.
> > Calibrating delay loop... 6370.09 BogoMIPS (lpj=31850496)
> > Mount-cache hash table entries: 512
> > CPU: After generic identify, caps: bfebfbff 00000000 00000000
> > 00000000 00004400 00000000 00000000
> > CPU: After vendor identify, caps: bfebfbff 00000000 00000000
> > 00000000 00004400 00000000 00000000
> > CPU: Trace cache: 12K uops, L1 D cache: 8K
> > CPU: L2 cache: 512K
> > CPU: L3 cache: 1024K
> > CPU: After all inits, caps: bfebd3f1 00000000 00000000
> > 00000080 00004400 00000000 00000000
> > CPU: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05 Enabling fast
> > FPU save and restore... done.
> > Enabling unmasked SIMD FPU exception support... done.
> > Checking 'hlt' instruction... disabled
> > ENABLING IO-APIC IRQs
> > NET: Registered protocol family 16
> > PCI: Using configuration type 1
> > ACPI: Subsystem revision 20050309
> > ACPI: Interpreter enabled
> > ACPI: Using IOAPIC for interrupt routing
> > ACPI: PCI Root Bridge [PCI0] (0000:00)
> > PCI: Probing PCI hardware (bus 00)
> > Boot video device is 0000:00:01.0
> > PCI: Ignoring BAR0-3 of IDE controller 0000:00:0f.1
> > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> > ACPI: PCI Root Bridge [PCI1] (0000:01)
> > PCI: Probing PCI hardware (bus 01)
> > ACPI: PCI Interrupt Routing Table [\_SB_.PCI1._PRT]
> > ACPI: PCI Root Bridge [PCI2] (0000:02)
> > PCI: Probing PCI hardware (bus 02)
> > ACPI: PCI Interrupt Routing Table [\_SB_.PCI2._PRT]
> > ACPI: PCI Interrupt Link [LP00] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP01] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP02] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP03] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP04] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP05] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP06] (IRQs *9)
> > ACPI: PCI Interrupt Link [LP07] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP08] (IRQs *3)
> > ACPI: PCI Interrupt Link [LP09] (IRQs *4)
> > ACPI: PCI Interrupt Link [LP0A] (IRQs *10)
> > ACPI: PCI Interrupt Link [LP0B] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP0C] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP0D] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP0E] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP0F] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP10] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP11] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP12] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP13] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP14] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP15] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP16] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP17] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP18] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP19] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP1A] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP1B] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP1C] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP1D] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP1E] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LP1F] (IRQs) *0, disabled.
> > ACPI: PCI Interrupt Link [LPUS] (IRQs *11)
> > xen_mem: Initialising balloon driver.
> > SCSI subsystem initialized
> > usbcore: registered new driver hub
> > PCI: Using ACPI for IRQ routing
> > PCI: If a device doesn't work, try "pci=routeirq". If it
> > helps, post a report Grant table initialized
> > IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com>
> > Initializing Cryptographic API
> > serio: i8042 AUX port at 0x60,0x64 irq 12
> > serio: i8042 KBD port at 0x60,0x64 irq 1 io scheduler noop
> > registered io scheduler anticipatory registered io scheduler
> > deadline registered io scheduler cfq registered Floppy
> > drive(s): fd0 is 1.44M FDC 0 is a National Semiconductor
> > PC87306 RAMDISK driver initialized: 16 RAM disks of 4096K
> > size 1024 blocksize
> > loop: loaded (max 8 devices)
> > HP CISS Driver (v 2.6.6)
> > Intel(R) PRO/1000 Network Driver - version 6.0.54-k2
> > Copyright (c) 1999-2004 Intel Corporation.
> > pcnet32.c:v1.30j 29.04.2005 tsbogend@alpha.franken.de
> > e100: Intel(R) PRO/100 Network Driver, 3.4.8-k2-NAPI
> > e100: Copyright(c) 1999-2005 Intel Corporation
> > tg3.c:v3.31 (June 8, 2005)
> > ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 24 (level, low) -> IRQ 24
> > eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-
> > bit) 10/100/1000BaseT Ethernet 00:11:25:3e:39:f2
> > eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0]
> > WireSpeed[1] TSOcap[1]
> > eth0: dma_rwctrl[769f4000]
> > ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 25 (level, low) -> IRQ 25
> > eth1: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-
> > bit) 10/100/1000BaseT Ethernet 00:11:25:3e:39:f3
> > eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0]
> > WireSpeed[1] TSOcap[1]
> > eth1: dma_rwctrl[769f4000]
> > tun: Universal TUN/TAP device driver, 1.6
> > tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> Xen
> > virtual console successfully installed as ttyS0 Event-channel
> > device installed.
> > xen_net: Initialising Xen netif backend.
> > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> > ide: Assuming 33MHz system bus speed for PIO modes; override
> > with idebus=xx SvrWks CSB5: IDE controller at PCI slot
> > 0000:00:0f.1 SvrWks CSB5: chipset revision 147 SvrWks CSB5:
> > not 100% native mode: will probe irqs later
> > ide0: BM-DMA at 0x0700-0x0707, BIOS settings: hda:pio, hdb:pio
> > ide1: BM-DMA at 0x0708-0x070f, BIOS settings: hdc:DMA,
> > hdd:DMA Probing IDE interface ide0...
> > Probing IDE interface ide1...
> > hdc: LG CD-ROM CRN-8245B, ATAPI CD/DVD-ROM drive
> > ide1 at 0x170-0x177,0x376 on irq 15
> > Probing IDE interface ide0...
> > Probing IDE interface ide2...
> > Probing IDE interface ide3...
> > Probing IDE interface ide4...
> > Probing IDE interface ide5...
> > hdc: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33) Uniform
> > CD-ROM driver Revision: 3.20 Red Hat/Adaptec aacraid driver
> > (1.1.2-lk2 Oct 13 2005) 3ware Storage Controller device
> > driver for Linux v1.26.02.001.
> > libata version 1.11 loaded.
> > Fusion MPT base driver 3.01.20
> > Copyright (c) 1999-2004 LSI Logic Corporation
> > ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 22 (level, low) -> IRQ 22
> > mptbase: Initiating ioc0 bringup
> > ioc0: 53C1030: Capabilities={Initiator}
> > Fusion MPT SCSI Host driver 3.01.20
> > scsi0 : ioc0: LSI53C1030, FwRev=01000e00h, Ports=1, MaxQ=222, IRQ=22
> > Vendor: IBM-ESXS Model: MAS3367NC FN Rev: C901
> > Type: Direct-Access ANSI SCSI revision: 03
> > SCSI device sda: 71096640 512-byte hdwr sectors (36401 MB)
> > SCSI device sda: drive cache: write through SCSI device sda:
> > 71096640 512-byte hdwr sectors (36401 MB) SCSI device sda:
> > drive cache: write through
> > sda: sda1 sda2
> > Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
> > Vendor: IBM-ESXS Model: MAS3367NC FN Rev: C901
> > Type: Direct-Access ANSI SCSI revision: 03
> > SCSI device sdb: 71096640 512-byte hdwr sectors (36401 MB)
> > SCSI device sdb: drive cache: write through SCSI device sdb:
> > 71096640 512-byte hdwr sectors (36401 MB) SCSI device sdb:
> > drive cache: write through
> > sdb: sdb1 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 >
> > Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
> > Vendor: IBM Model: 25P3495a S320 1 Rev: 1
> > Type: Processor ANSI SCSI revision: 02
> > usbmon: debugs is not available
> > ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI)
> > Driver (PCI)
> > ACPI: PCI Interrupt Link [LPUS] enabled at IRQ 11
> > ACPI: PCI Interrupt 0000:00:0f.2[A] -> Link [LPUS] -> GSI 11 (level,
> > low) -> IRQ 11
> > ohci_hcd 0000:00:0f.2: OHCI Host Controller ohci_hcd
> > 0000:00:0f.2: new USB bus registered, assigned bus number 1
> > ohci_hcd 0000:00:0f.2: irq 11, io mem 0xfebfe000 hub 1-0:1.0:
> > USB hub found hub 1-0:1.0: 4 ports detected USB Universal
> > Host Controller Interface driver v2.2
> > usbcore: registered new driver usbhid
> > drivers/usb/input/hid-core.c: v2.01:USB HID core driver
> > mice: PS/2 mouse device common for all mice
> > md: raid0 personality registered as nr 2
> > md: raid1 personality registered as nr 3
> > md: raid5 personality registered as nr 4
> > raid5: automatically using best checksumming function: pIII_sse
> > pIII_sse : 1466.000 MB/sec
> > raid5: using function: pIII_sse (1466.000 MB/sec)
> > md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
> > device-mapper: 4.4.0-ioctl (2005-01-12) initialised:
> > dm-devel@redhat.com
> > NET: Registered protocol family 2
> > input: AT Translated Set 2 keyboard on isa0060/serio0
> > IP: routing cache hash table of 4096 buckets, 32Kbytes TCP
> > established hash table entries: 16384 (order: 5, 131072
> > bytes) TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
> > TCP: Hash tables configured (established 16384 bind 16384)
> > NET: Registered protocol family 1
> > NET: Registered protocol family 17
> > input: PS/2 Generic Mouse on isa0060/serio1 Bridge
> > firewalling registered
> > md: Autodetecting RAID arrays.
> > md: autorun ...
> > md: ... autorun DONE.
> > EXT3-fs: mounted filesystem with ordered data mode.
> > VFS: Mounted root (ext3 filesystem) readonly.
> > Freeing unused kernel memory: 356k freed kjournald starting.
> > Commit interval 5 seconds
> > EXT3 (no)acl options not supported
> > EXT3 (no)acl options not supported
> > EXT3 FS on sda2, internal journal
> > md: Autodetecting RAID arrays.
> > md: autorun ...
> > md: ... autorun DONE.
> > Adding 1052216k swap on /dev/sda1. Priority:42 extents:1
> > tg3: eth0: Link is up at 100 Mbps, full duplex.
> > tg3: eth0: Flow control is on for TX and on for RX.
> > Linux agpgart interface v0.101 (c) Dave Jones
> > ACPI: Power Button (FF) [PWRF]
> > end_request: I/O error, dev fd0, sector 0
> > end_request: I/O error, dev fd0, sector 0 program hwscan is
> > using a deprecated SCSI ioctl, please convert it to SG_IO
> > program hwscan is using a deprecated SCSI ioctl, please
> > convert it to SG_IO
> > end_request: I/O error, dev fd0, sector 0
> > end_request: I/O error, dev fd0, sector 0 nfs warning: mount
> > version older than kernel device vif0.0 entered promiscuous mode
> > bridge: can't decode speed from peth0: 0 device peth0 entered
> > promiscuous mode
> > xen-br0: port 1(vif0.0) entering learning state
> > xen-br0: topology change detected, propagating
> > xen-br0: port 1(vif0.0) entering forwarding state
> > tg3: peth0: Link is up at 100 Mbps, full duplex.
> > tg3: peth0: Flow control is on for TX and on for RX.
> > xen-br0: port 2(peth0) entering learning state
> > xen-br0: topology change detected, propagating
> > xen-br0: port 2(peth0) entering forwarding state device
> > vif74.1 entered promiscuous mode
> > xen-br0: port 3(vif74.1) entering learning state
> > xen-br0: topology change detected, propagating
> > xen-br0: port 3(vif74.1) entering forwarding state device
> > vif75.1 entered promiscuous mode
> > xen-br0: port 4(vif75.1) entering learning state
> > xen-br0: topology change detected, propagating
> > xen-br0: port 4(vif75.1) entering forwarding state
> > xen-br0: port 4(vif75.1) entering disabled state device
> > vif75.1 left promiscuous mode
> > xen-br0: port 4(vif75.1) entering disabled state device
> > vif76.1 entered promiscuous mode
> > xen-br0: port 4(vif76.1) entering learning state
> > xen-br0: topology change detected, propagating
> > xen-br0: port 4(vif76.1) entering forwarding state device
> > vif77.1 entered promiscuous mode
> > xen-br0: port 5(vif77.1) entering learning state
> > xen-br0: topology change detected, propagating
> > xen-br0: port 5(vif77.1) entering forwarding state x335b:~ #
> >
> > The last output from 'xm-test' is:
> >
> > x335b:/tmp/logs/xm-test # tail x335sles9_pae4gb.output Using
> > config file "/dev/null".
> > Started domain testdomain
> > [dom0] Running `xm destroy testdomain'
> >
> > [dom0] Running `xm create /dev/null
> > ramdisk=../../ramdisk/initrd.img
> > kernel=/boot/vmlinuz-2.6.12-xenU name=testdomain nics=0 vcpus=1
> > memory=64 root=/dev/ram0'
> > Using config file "/dev/null".
> > Started domain testdomain
> > [dom0] Running `xm destroy testdomain'
> >
> > PASS: 10_create_fastdestroy.test
> > x335b:/tmp/logs/xm-test #
> >
> >
> > On Wed, 2005-09-28 at 15:24 -0500, David F Barrera wrote:
> > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=265
> > >
> > > While running xm-test on two IBM xSeries 335s, one FC4 and
> > the other
> > > one SLES 9, I noticed that time has stopped:
> > >
> > > [root@x335a xm-test]# date
> > > Wed Sep 28 13:59:18 CDT 2005
> > > [root@x335a xm-test]# date
> > > Wed Sep 28 13:59:18 CDT 2005
> > >
> > > >> 15 minutes later,
> > > [root@x335a xm-test]# date
> > > Wed Sep 28 13:59:18 CDT 2005
> > > [root@x335a xm-test]#
> > >
> > > changeset: 7076:46046d5fb354
> > > tag: tip
> > > user: emellor@ewan
> > > date: Tue Sep 27 16:09:46 2005 +0100
> > > summary: Remove unused import, mark unused variables.
> > >
> > > The last output lines produced by xm-test are:
> > > cp 06_destroy_dom0_neg.py 06_destroy_dom0_neg.test chmod +x
> > > 06_destroy_dom0_neg.test
> > >
> > > The machines in question are running xm-test at the moment
> > and appear
> > > 'stuck'.
> > > Both are displaying the "(XEN) Ouch! We are seriously
> > BEHIND schedule!"
> > > messages. However, the static time issue may not be related
> > to the Ouch!
> > > issue, bug # 257, as Paul Larson observed it on a machine
> > that was not
> > > running xm-test at the time, hence we are submitting it as
> > a different
> > > bug.
> > >
> > >
> > --
> > Regards,
> >
> > David F Barrera
> > Linux Technology Center
> > Systems and Technology Group, IBM
> >
> > "The wisest men follow their own direction. "
> > Euripides
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> >
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: Time stopped
2005-10-13 19:06 ` David F Barrera
@ 2005-10-13 19:21 ` Dan Smith
0 siblings, 0 replies; 18+ messages in thread
From: Dan Smith @ 2005-10-13 19:21 UTC (permalink / raw)
To: David F Barrera; +Cc: Ian.Pratt, Xen Developers
> x335b:/tmp/logs/xm-test # xm list
> Name ID Mem(MiB) CPU VCPUs State Time(s)
> Domain-0 0 495 - 4 r----- 96.5
> 11_create_0 73 16 3 1 -b---- 0.3
> x335b:/tmp/logs/xm-test #
This is not a surprising place to fail. Test 10_create tries to
create and destroy a bunch of domains really fast. That used to
reboot people's machines. Test 11_create tries to create a whole
bunch of concurrent DomUs, but it looks like it isn't getting very
far.
Does 'top' show anything (like xenconsoled) pegging the CPU, or does
'xm top' show the 11_create_0 domain taking over the system?
Can you reliably put the system into this state right between tests
10_create and 11_create?
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@us.ibm.com
^ permalink raw reply [flat|nested] 18+ messages in thread
* RE: Time stopped
@ 2005-10-14 17:51 Stephan Böni
0 siblings, 0 replies; 18+ messages in thread
From: Stephan Böni @ 2005-10-14 17:51 UTC (permalink / raw)
To: Ian Pratt; +Cc: xen-devel
> > I'm trying to reproduce again to get more details - but it'd
> > be helpful if folks could apply the below and, if they repro the
> > problem:
> >
> > (1) get serial console to Xen (i.e. hit 'Ctrl-A' three times)
> > (2) hit 'a' to dump the ac_timer queues and the scale info,
> > (3) post the results to the list
>
> OK, this issue is now understood, and there's a fix
> undergoing testing in the staging queue. No need to collect
> the above data -- just wait for the changeset to make it out
> or try the attached patch.
Thanks, Ian.
At the moment i can't check anything because i don't get running a
domU. I have still network-bridge errors. :-(
[2005-10-14 19:49:57 xend] ERROR (process:37) [network-bridge] + set -e
[2005-10-14 19:49:57 xend] ERROR (process:37) [network-bridge] + OP=start
[2005-10-14 19:49:57 xend] ERROR (process:37) [network-bridge] + shift
[2005-10-14 19:49:57 xend] ERROR (process:37) [network-bridge] + for arg in '"$@"'
....
...
..
.
Stephan
^ permalink raw reply [flat|nested] 18+ messages in thread
* RE: Time stopped
@ 2005-10-14 17:37 Ian Pratt
0 siblings, 0 replies; 18+ messages in thread
From: Ian Pratt @ 2005-10-14 17:37 UTC (permalink / raw)
To: Steven Hand, David F Barrera; +Cc: xen-devel, Stephan Böni
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
> So managed to reproduce (once!) and now perhaps one step
> further to solving it - basically the guest is /not/ to
> blame; Xen itself is not updating time correctly. In my
> instance it was out (i.e. time was running slower) by a
> factor of approximately 16 -- 20.
>
> I'm trying to reproduce again to get more details - but it'd
> be helpful if folks could apply the below and, if they repro the
> problem:
>
> (1) get serial console to Xen (i.e. hit 'Ctrl-A' three times)
> (2) hit 'a' to dump the ac_timer queues and the scale info,
> (3) post the results to the list
OK, this issue is now understood, and there's a fix undergoing testing in the staging queue. No need to collect the above data -- just wait for the changeset to make it out or try the attached patch.
Ian
[-- Attachment #2: pit-fix.patch --]
[-- Type: application/octet-stream, Size: 4746 bytes --]
# HG changeset patch
# User kaf24@firebug.cl.cam.ac.uk
# Node ID f9b300fab36e2a7fef2160ca2e6ab0db1f1b3280
# Parent d48bc069122cad701be691ad456b5b3f1a0c479f
This should fix time stopped / going slow problems that
various users have been seeing.
Signed-off-by: Keir Fraser <keir@xensource.com>
diff -r d48bc069122c -r f9b300fab36e xen/arch/x86/time.c
--- a/xen/arch/x86/time.c Fri Oct 14 15:01:11 2005
+++ b/xen/arch/x86/time.c Fri Oct 14 17:27:25 2005
@@ -61,12 +61,23 @@
static struct cpu_time cpu_time[NR_CPUS];
-/* Protected by platform_timer_lock. */
+/*
+ * Protected by platform_timer_lock, which must be acquired with interrupts
+ * disabled because pit_overflow() is called from PIT ch0 interrupt context.
+ */
static s_time_t stime_platform_stamp;
static u64 platform_timer_stamp;
static struct time_scale platform_timer_scale;
static spinlock_t platform_timer_lock = SPIN_LOCK_UNLOCKED;
static u64 (*read_platform_count)(void);
+
+/*
+ * Folding 16-bit PIT into 64-bit software counter is a really critical
+ * operation! We therefore do it directly in PIT ch0 interrupt handler,
+ * based on this flag.
+ */
+static int using_pit;
+static void pit_overflow(void);
/*
* 32-bit division of integer dividend and integer divisor yielding
@@ -135,14 +146,16 @@
void timer_interrupt(int irq, void *dev_id, struct cpu_user_regs *regs)
{
+ ASSERT(local_irq_is_enabled());
+
if ( timer_ack )
{
extern spinlock_t i8259A_lock;
- spin_lock(&i8259A_lock);
+ spin_lock_irq(&i8259A_lock);
outb(0x0c, 0x20);
/* Ack the IRQ; AEOI will end it automatically. */
inb(0x20);
- spin_unlock(&i8259A_lock);
+ spin_unlock_irq(&i8259A_lock);
}
/* Update jiffies counter. */
@@ -151,6 +164,9 @@
/* Rough hack to allow accurate timers to sort-of-work with no APIC. */
if ( !cpu_has_apic )
raise_softirq(AC_TIMER_SOFTIRQ);
+
+ if ( using_pit )
+ pit_overflow();
}
static struct irqaction irq0 = { timer_interrupt, "timer", NULL};
@@ -280,7 +296,6 @@
/* Protected by platform_timer_lock. */
static u64 pit_counter64;
static u16 pit_stamp;
-static struct ac_timer pit_overflow_timer;
static u16 pit_read_counter(void)
{
@@ -292,17 +307,15 @@
return count;
}
-static void pit_overflow(void *unused)
+static void pit_overflow(void)
{
u16 counter;
- spin_lock(&platform_timer_lock);
+ spin_lock_irq(&platform_timer_lock);
counter = pit_read_counter();
pit_counter64 += (u16)(pit_stamp - counter);
pit_stamp = counter;
- spin_unlock(&platform_timer_lock);
-
- set_ac_timer(&pit_overflow_timer, NOW() + MILLISECS(20));
+ spin_unlock_irq(&platform_timer_lock);
}
static u64 read_pit_count(void)
@@ -314,12 +327,12 @@
{
read_platform_count = read_pit_count;
- init_ac_timer(&pit_overflow_timer, pit_overflow, NULL, 0);
- pit_overflow(NULL);
+ pit_overflow();
platform_timer_stamp = pit_counter64;
set_time_scale(&platform_timer_scale, CLOCK_TICK_RATE);
printk("Platform timer is %s PIT\n", freq_string(CLOCK_TICK_RATE));
+ using_pit = 1;
return 1;
}
@@ -337,11 +350,11 @@
{
u32 counter;
- spin_lock(&platform_timer_lock);
+ spin_lock_irq(&platform_timer_lock);
counter = hpet_read32(HPET_COUNTER);
hpet_counter64 += (u32)(counter - hpet_stamp);
hpet_stamp = counter;
- spin_unlock(&platform_timer_lock);
+ spin_unlock_irq(&platform_timer_lock);
set_ac_timer(&hpet_overflow_timer, NOW() + hpet_overflow_period);
}
@@ -455,11 +468,11 @@
{
u32 counter;
- spin_lock(&platform_timer_lock);
+ spin_lock_irq(&platform_timer_lock);
counter = *cyclone_timer;
cyclone_counter64 += (u32)(counter - cyclone_stamp);
cyclone_stamp = counter;
- spin_unlock(&platform_timer_lock);
+ spin_unlock_irq(&platform_timer_lock);
set_ac_timer(&cyclone_overflow_timer, NOW() + MILLISECS(20000));
}
@@ -526,10 +539,10 @@
u64 counter;
s_time_t stime;
- spin_lock(&platform_timer_lock);
+ spin_lock_irq(&platform_timer_lock);
counter = read_platform_count();
stime = __read_platform_stime(counter);
- spin_unlock(&platform_timer_lock);
+ spin_unlock_irq(&platform_timer_lock);
return stime;
}
@@ -539,12 +552,12 @@
u64 counter;
s_time_t stamp;
- spin_lock(&platform_timer_lock);
+ spin_lock_irq(&platform_timer_lock);
counter = read_platform_count();
stamp = __read_platform_stime(counter);
stime_platform_stamp = stamp;
platform_timer_stamp = counter;
- spin_unlock(&platform_timer_lock);
+ spin_unlock_irq(&platform_timer_lock);
}
static void init_platform_timer(void)
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: Time stopped
@ 2005-10-14 16:37 Stephan Böni
2005-10-14 16:47 ` David F Barrera
0 siblings, 1 reply; 18+ messages in thread
From: Stephan Böni @ 2005-10-14 16:37 UTC (permalink / raw)
To: Ted Kaczmarek, David F Barrera; +Cc: Ian Pratt, xen-devel
[-- Attachment #1: Type: text/plain, Size: 122 bytes --]
***** SOLVED *****
(...as workarround)
i have to disable the cpu hyperthreading in the system bios.
Stephan
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Time stopped
2005-10-14 16:37 Stephan Böni
@ 2005-10-14 16:47 ` David F Barrera
0 siblings, 0 replies; 18+ messages in thread
From: David F Barrera @ 2005-10-14 16:47 UTC (permalink / raw)
To: Stephan Böni; +Cc: Ian Pratt, Ted Kaczmarek, xen-devel
On Fri, 2005-10-14 at 18:37 +0200, Stephan Böni wrote:
> ***** SOLVED *****
>
> (...as workarround)
>
> i have to disable the cpu hyperthreading in the system bios.
When I ran xm-test with a kernel booted with maxcpus=1, I did not see
the problem, either.
>
> Stephan
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Time stopped
@ 2005-10-14 15:44 Stephan Böni
0 siblings, 0 replies; 18+ messages in thread
From: Stephan Böni @ 2005-10-14 15:44 UTC (permalink / raw)
To: Stephan Böni, Ted Kaczmarek, David F Barrera; +Cc: Ian Pratt, xen-devel
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
Some interesting thing: xm top reports:
xentop - 17:35:32 Xen 3.0_6715-2
1 domains: 1 running, 0 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown
Mem: 4980736k total, 987908k used, 3992828k free CPUs: 2 @ 3200MHz
DOMID STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS
NETTX(k) NETRX(k) SSID
0 -----r 27 0.3 125952 2.5 no limit n/a 1 1
164 317 0
Why i have 987908k memory used? I'm starting the xen kernel with dom0_mem=131072.
And another funny thing is: CPUs: 2 @ 3200MHz. I have only one cpu installed.
Is this a hyperthreading issue?
Regards,
Stephan
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: Time stopped
@ 2005-10-14 15:23 Stephan Böni
0 siblings, 0 replies; 18+ messages in thread
From: Stephan Böni @ 2005-10-14 15:23 UTC (permalink / raw)
To: Ted Kaczmarek, David F Barrera; +Cc: Ian Pratt, xen-devel
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
> -----Ursprüngliche Nachricht-----
> Von: Ted Kaczmarek [mailto:tedkaz@optonline.net]
> Gesendet: Freitag, 14. Oktober 2005 17:13
> Betreff: Re: [Xen-devel] Time stopped
>
> On Fri, 2005-10-14 at 10:01 -0500, David F Barrera wrote:
> > On Fri, 2005-10-14 at 16:48 +0200, Stephan Böni wrote:
> > > Just for your information. I have the same problem on my
> installation.
> > >
> > Thanks for the feedback. I was wondering if I was the only
> one seeing
> > it.
> >
> > > Stephan
> > >
> I see this after domU's have been up for over 2 days
> consistently, on my
> SMP Athlon and UP P4 machines as well, sometime load will
> kick it off as
> well on the SMP Athlon.
On my system the time stops when i try to start a domU. Even
when this startup fails, the clock has stopped. Often it goes
on after approx. 30 secs., but sometimes not. In this cases,
i can't shutdown the system anymore.
I'm using an IBM 336 server with one Xeon cpu. As os i've
installed SUSE Linux 10.0 which uses a 2.6.13 kernel. And
as Xen version i'm using the Xen3 build which is part of
the SUSE Linux 10.0 distribution.
Regards,
Stephan
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Time stopped
@ 2005-10-14 14:48 Stephan Böni
2005-10-14 15:01 ` David F Barrera
0 siblings, 1 reply; 18+ messages in thread
From: Stephan Böni @ 2005-10-14 14:48 UTC (permalink / raw)
To: David F Barrera, Ian Pratt; +Cc: xen-devel
Just for your information. I have the same problem on my installation.
Stephan
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Time stopped
2005-10-14 14:48 Stephan Böni
@ 2005-10-14 15:01 ` David F Barrera
2005-10-14 15:12 ` Ted Kaczmarek
2005-10-14 16:46 ` Steven Hand
0 siblings, 2 replies; 18+ messages in thread
From: David F Barrera @ 2005-10-14 15:01 UTC (permalink / raw)
To: Stephan Böni; +Cc: Ian Pratt, xen-devel
On Fri, 2005-10-14 at 16:48 +0200, Stephan Böni wrote:
> Just for your information. I have the same problem on my installation.
>
Thanks for the feedback. I was wondering if I was the only one seeing
it.
> Stephan
>
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: Time stopped
2005-10-14 15:01 ` David F Barrera
@ 2005-10-14 15:12 ` Ted Kaczmarek
2005-10-14 16:46 ` Steven Hand
1 sibling, 0 replies; 18+ messages in thread
From: Ted Kaczmarek @ 2005-10-14 15:12 UTC (permalink / raw)
To: David F Barrera; +Cc: Ian Pratt, xen-devel, Stephan Böni
On Fri, 2005-10-14 at 10:01 -0500, David F Barrera wrote:
> On Fri, 2005-10-14 at 16:48 +0200, Stephan Böni wrote:
> > Just for your information. I have the same problem on my installation.
> >
> Thanks for the feedback. I was wondering if I was the only one seeing
> it.
>
> > Stephan
> >
I see this after domU's have been up for over 2 days consistently, on my
SMP Athlon and UP P4 machines as well, sometime load will kick it off as
well on the SMP Athlon.
Regards,
Ted
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Time stopped
2005-10-14 15:01 ` David F Barrera
2005-10-14 15:12 ` Ted Kaczmarek
@ 2005-10-14 16:46 ` Steven Hand
1 sibling, 0 replies; 18+ messages in thread
From: Steven Hand @ 2005-10-14 16:46 UTC (permalink / raw)
To: David F Barrera; +Cc: Ian Pratt, xen-devel, Stephan Böni
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]
> On Fri, 2005-10-14 at 16:48 +0200, Stephan Böni wrote:
> > Just for your information. I have the same problem on my installation.
> >
> Thanks for the feedback. I was wondering if I was the only one seeing
> it.
So managed to reproduce (once!) and now perhaps one step further to
solving it - basically the guest is /not/ to blame; Xen itself is
not updating time correctly. In my instance it was out (i.e. time
was running slower) by a factor of approximately 16 -- 20.
I'm trying to reproduce again to get more details - but it'd be
helpful if folks could apply the below and, if they repro the
problem:
(1) get serial console to Xen (i.e. hit 'Ctrl-A' three times)
(2) hit 'a' to dump the ac_timer queues and the scale info,
(3) post the results to the list
cheers,
S.
diff -r bd3268de4145 xen/arch/x86/time.c
--- a/xen/arch/x86/time.c Fri Oct 14 14:40:48 2005
+++ b/xen/arch/x86/time.c Fri Oct 14 17:44:46 2005
@@ -133,6 +133,15 @@
return product;
}
+void print_scale(int cpu)
+{
+ struct cpu_time *t = &cpu_time[cpu];
+ struct time_scale *s = &t->tsc_scale;
+
+ printk("CPU%d: scale->mul_frac = %x\n", cpu, s->mul_frac);
+ printk("CPU%d: scale->shift = %d\n", cpu, s->shift);
+}
+
void timer_interrupt(int irq, void *dev_id, struct cpu_user_regs *regs)
{
if ( timer_ack )
diff -r bd3268de4145 xen/common/ac_timer.c
--- a/xen/common/ac_timer.c Fri Oct 14 14:40:48 2005
+++ b/xen/common/ac_timer.c Fri Oct 14 17:44:46 2005
@@ -225,6 +225,7 @@
spin_unlock_irq(&ac_timers[cpu].lock);
}
+extern void print_scale(int cpu);
static void dump_timerq(unsigned char key)
{
@@ -239,6 +240,7 @@
for_each_online_cpu( i )
{
printk("CPU[%02d] ", i);
+ print_scale( i );
spin_lock_irqsave(&ac_timers[i].lock, flags);
for ( j = 1; j <= GET_HEAP_SIZE(ac_timers[i].heap); j++ )
{
^ permalink raw reply [flat|nested] 18+ messages in thread
* RE: Time stopped
@ 2005-10-13 19:21 Ian Pratt
2005-10-14 14:34 ` David F Barrera
0 siblings, 1 reply; 18+ messages in thread
From: Ian Pratt @ 2005-10-13 19:21 UTC (permalink / raw)
To: David F Barrera; +Cc: xen-devel
> Recreated the situation on non-PAE kernel on the same machine.
As I suspected.
> On Thu, 2005-10-13 at 18:29 +0100, Ian Pratt wrote:
>
> >
> > When the machine is in this state, what interrupt rate does
> > /proc/interrupts show?
> x335b:~ # cat /proc/interrupts
You'll need to do this multiple times e.g. 10 seconds appart for us to
figure out the rate.
> > If you do a "sleep 1" how long does it sleep for?
> In this case, it slept for about 3 real minutes.
Interesting.
> > I presume both dom0 and the domU experience the time slow down?
> Correct.
> >
> > If you run something in the background that burns CPU does
> it make a
> > difference?
> I started LTP on dom0 ( and can see console outpu) and it
> makes no difference.
I think a "while true; do true; done" might be more convincing, but LTP
is probably good enough.
> > In this case, what does xm list show as regards the CPU
> time consumed
> > by the domains?
> x335b:/tmp/ltp-full-20050804 # date
> Thu Oct 13 13:47:59 CDT 2005
> x335b:/tmp/ltp-full-20050804 # xm list
> Name ID Mem(MiB) CPU VCPUs State Time(s)
> Domain-0 0 495 - 4 r----- 96.5
> 11_create_0 73 16 3 1 -b---- 0.3
> x335b:/tmp/ltp-full-20050804 # xm list
> Name ID Mem(MiB) CPU VCPUs State Time(s)
> Domain-0 0 495 - 4 r----- 96.5
> 11_create_0 73 16 3 1 -b---- 0.3
> x335b:/tmp/ltp-full-20050804 # xm list
> Name ID Mem(MiB) CPU VCPUs State Time(s)
> Domain-0 0 495 - 4 r----- 96.5
> 11_create_0 73 16 3 1 -b---- 0.3
> x335b:/tmp/ltp-full-20050804 #
> x335b:/tmp/ltp-full-20050804 # date
> Thu Oct 13 13:47:59 CDT 2005
I didn't expect this. Need to think some.
> > Can you narrow down which of the xm-tests actually
> provoke's the bug?
Can you repro using just this test?
If you had a serial console and perfc=y enabled it would be interesting
to see the real interrupt rate from the xen debug console.
Ian
^ permalink raw reply [flat|nested] 18+ messages in thread
* RE: Time stopped
2005-10-13 19:21 Ian Pratt
@ 2005-10-14 14:34 ` David F Barrera
0 siblings, 0 replies; 18+ messages in thread
From: David F Barrera @ 2005-10-14 14:34 UTC (permalink / raw)
To: Ian Pratt; +Cc: xen-devel
Ian,
I tried to reproduce with maxcpus=1 two or three times yesterday, and
the problem did not happen. It is not definitive, though, because xm-
test sometimes does run. But this morning, it hit the bug the first time
through, in the regular test (w/o the maxcpus parm).
On Thu, 2005-10-13 at 20:21 +0100, Ian Pratt wrote:
>
> > x335b:~ # cat /proc/interrupts
>
> You'll need to do this multiple times e.g. 10 seconds appart for us to
> figure out the rate.
>
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9800 Phys-irq ioc0
24: 38166 Phys-irq peth0
256: 8489111 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 13709 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9800 Phys-irq ioc0
24: 38199 Phys-irq peth0
256: 8489111 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 13709 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9800 Phys-irq ioc0
24: 38238 Phys-irq peth0
256: 8489111 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 13709 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9800 Phys-irq ioc0
24: 38272 Phys-irq peth0
256: 8489111 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 13709 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
----
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9800 Phys-irq ioc0
24: 38407 Phys-irq peth0
256: 8582512 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 13709 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9800 Phys-irq ioc0
24: 38450 Phys-irq peth0
256: 8582513 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 13709 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9800 Phys-irq ioc0
24: 38482 Phys-irq peth0
256: 8675691 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 13709 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
>
> > >
> > > If you run something in the background that burns CPU does
> > it make a
> > > difference?
> > I started LTP on dom0 ( and can see console outpu) and it
> > makes no difference.
>
> I think a "while true; do true; done" might be more convincing, but LTP
> is probably good enough.
Did this. Time still static. Other sessions become unresponsive while this runs.
>
> > > In this case, what does xm list show as regards the CPU
> > time consumed
> > > by the domains?
> > x335b:/tmp/ltp-full-20050804 # date
> > Thu Oct 13 13:47:59 CDT 2005
> > x335b:/tmp/ltp-full-20050804 # xm list
> > Name ID Mem(MiB) CPU VCPUs State Time(s)
> > Domain-0 0 495 - 4 r----- 96.5
> > 11_create_0 73 16 3 1 -b---- 0.3
> > x335b:/tmp/ltp-full-20050804 # xm list
> > Name ID Mem(MiB) CPU VCPUs State Time(s)
> > Domain-0 0 495 - 4 r----- 96.5
> > 11_create_0 73 16 3 1 -b---- 0.3
> > x335b:/tmp/ltp-full-20050804 # xm list
> > Name ID Mem(MiB) CPU VCPUs State Time(s)
> > Domain-0 0 495 - 4 r----- 96.5
> > 11_create_0 73 16 3 1 -b---- 0.3
> > x335b:/tmp/ltp-full-20050804 #
> > x335b:/tmp/ltp-full-20050804 # date
> > Thu Oct 13 13:47:59 CDT 2005
>
> I didn't expect this. Need to think some.
>
> > > Can you narrow down which of the xm-tests actually
> > provoke's the bug?
>
I believe it is 11_create_concurrent_pos.py that's provoking this bug.
> Can you repro using just this test?
I will try.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
^ permalink raw reply [flat|nested] 18+ messages in thread
* Time stopped
@ 2005-09-28 20:24 David F Barrera
2005-10-13 15:17 ` David F Barrera
0 siblings, 1 reply; 18+ messages in thread
From: David F Barrera @ 2005-09-28 20:24 UTC (permalink / raw)
To: xen-devel
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=265
While running xm-test on two IBM xSeries 335s, one FC4 and the other one
SLES 9, I noticed that time has stopped:
[root@x335a xm-test]# date
Wed Sep 28 13:59:18 CDT 2005
[root@x335a xm-test]# date
Wed Sep 28 13:59:18 CDT 2005
>> 15 minutes later,
[root@x335a xm-test]# date
Wed Sep 28 13:59:18 CDT 2005
[root@x335a xm-test]#
changeset: 7076:46046d5fb354
tag: tip
user: emellor@ewan
date: Tue Sep 27 16:09:46 2005 +0100
summary: Remove unused import, mark unused variables.
The last output lines produced by xm-test are:
cp 06_destroy_dom0_neg.py 06_destroy_dom0_neg.test
chmod +x 06_destroy_dom0_neg.test
The machines in question are running xm-test at the moment and appear
'stuck'.
Both are displaying the "(XEN) Ouch! We are seriously BEHIND schedule!"
messages. However, the static time issue may not be related to the Ouch!
issue, bug # 257, as Paul Larson observed it on a machine that was not
running xm-test at the time, hence we are submitting it as a different
bug.
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: Time stopped
2005-09-28 20:24 David F Barrera
@ 2005-10-13 15:17 ` David F Barrera
2005-10-13 15:36 ` David F Barrera
0 siblings, 1 reply; 18+ messages in thread
From: David F Barrera @ 2005-10-13 15:17 UTC (permalink / raw)
To: xen-devel
I continue to encounter this problem daily on an IBM xSeries 335 SLES 9
SP2, 4GB RAM machine while running XM-TEST. The time has not actually
stopped, but moves forward at an exceedingly slow pace. The 'date'
command will actually show that a second has transpired in the period
of, say, 10 actual minutes (or more). 'xm dmesg' is showing a trace.
x335b:~ # xm list
Name ID Mem(MiB) CPU VCPUs State Time(s)
Domain-0 0 495 0 1 r----- 110.9
11_create_0 131 16 3 1 -b---- 0.3
x335b:~ # date
Thu Oct 13 09:52:23 CDT 2005
x335b:~ # date
Thu Oct 13 09:52:23 CDT 2005
x335b:~ # date
Thu Oct 13 09:52:23 CDT 2005
x335b:~ # xm list
Name ID Mem(MiB) CPU VCPUs State Time(s)
Domain-0 0 495 0 1 r----- 110.9
11_create_0 131 16 3 1 -b---- 0.3
x335b:~ # date
Thu Oct 13 09:52:24 CDT 2005
x335b:~ # date
Thu Oct 13 09:52:24 CDT 2005
x335b:~ # xm dmesg
__ __ _____ ___ _ _
\ \/ /___ _ __ |___ / / _ \ __| | _____ _____| |
\ // _ \ '_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
/ \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ |
/_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_|
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.0-devel (root@ltc.austin.ibm.com) (gcc version 3.3.3
(SuSE Linux)) Thu Oct 13 06:30:24 CDT 2005
Latest ChangeSet: Wed Oct 12 10:15:02 2005 +0100 7353:29db5bded574
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009d400 (usable)
(XEN) 000000000009d400 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000f7fec140 (usable)
(XEN) 00000000f7fec140 - 00000000f7ff0000 (ACPI data)
(XEN) 00000000f7ff0000 - 00000000f8000000 (reserved)
(XEN) 00000000fec00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000108000000 (usable)
(XEN) System RAM: 4095MB (4193828kB)
(XEN) Xen heap: 10MB (10496kB)
(XEN) PAE enabled, limit: 16 GB
(XEN) found SMP MP-table at 0009d540
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 IBM ) @
0x000fdfc0
(XEN) ACPI: RSDT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
0xf7feff80
(XEN) ACPI: FADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
0xf7feff00
(XEN) ACPI: MADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
0xf7fefe40
(XEN) ACPI: ASF! (v016 IBM SERONYXP 0x00000001 IBM 0x45444f43) @
0xf7fefd80
(XEN) ACPI: DSDT (v001 IBM SERTURQU 0x00001000 MSFT 0x0100000b) @
0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:2 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
(XEN) Processor #6 15:2 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 15:2 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
(XEN) Processor #7 15:2 APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
(XEN) ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 14, version 17, address 0xfec00000, GSI 0-15
(XEN) ACPI: IOAPIC (id[0x0d] address[0xfec01000] gsi_base[16])
(XEN) IOAPIC[1]: apic_id 13, version 17, address 0xfec01000, GSI 16-31
(XEN) ACPI: IOAPIC (id[0x0c] address[0xfec02000] gsi_base[32])
(XEN) IOAPIC[2]: apic_id 12, version 17, address 0xfec02000, GSI 32-47
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) Enabling APIC mode: Flat. Using 3 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 3189.471 MHz processor.
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
(XEN) CPU: L2 cache: 512K
(XEN) CPU: L3 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU0: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
(XEN) CPU: L2 cache: 512K
(XEN) CPU: L3 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU1: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
(XEN) Booting processor 2/6 eip 90000
(XEN) Initializing CPU#2
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
(XEN) CPU: L2 cache: 512K
(XEN) CPU: L3 cache: 1024K
(XEN) CPU: Physical Processor ID: 3
(XEN) CPU2: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
(XEN) Booting processor 3/7 eip 90000
(XEN) Initializing CPU#3
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
(XEN) CPU: L2 cache: 512K
(XEN) CPU: L3 cache: 1024K
(XEN) CPU: Physical Processor ID: 3
(XEN) CPU3: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 4 CPUs
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,PAE=yes,LOADER=generic'
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000003800000->0000000004000000 (125952 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c06394e4
(XEN) Init. ramdisk: c063a000->c063a000
(XEN) Phys-Mach map: c063a000->c06b7000
(XEN) Start info: c06b7000->c06b8000
(XEN) Page tables: c06b8000->c06c1000
(XEN) Boot stack: c06c1000->c06c2000
(XEN) TOTAL: c0000000->c0800000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Scrubbing Free
RAM: ...........................................done.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen).
(XEN) microcode: CPU1 updated from revision 0x11 to 0x29, date =
08112004
(XEN) microcode: CPU2 updated from revision 0x11 to 0x29, date =
08112004
(XEN) microcode: CPU3 updated from revision 0x11 to 0x29, date =
08112004
(XEN) microcode: CPU0 updated from revision 0x11 to 0x29, date =
08112004
(XEN) mtrr: type mismatch for fd000000,800000 old: write-back new:
write-combining
(XEN) mtrr: type mismatch for fd000000,800000 old: write-back new:
write-combining
(XEN) Domain 63 (vcpu#0) crashed on cpu#3:
(XEN) CPU: 3
(XEN) EIP: e019:[<c01159b6>]
(XEN) EFLAGS: 00000246 CONTEXT: guest
(XEN) eax: 00000ac8 ebx: 00000000 ecx: 00000000 edx: 00000000
(XEN) esi: 00000000 edi: 00000000 ebp: 00000ac8 esp: c0355e8c
(XEN) cr0: 8005003b cr3: e3b58000
(XEN) ds: e021 es: e021 fs: 0000 gs: e021 ss: e021 cs: e019
(XEN) Guest stack trace from esp=c0355e8c:
(XEN) c0000acc 00000003 c01159b6 0001e019 00010246 00000000 00000000
00000000
(XEN) c0000000 c0361875 c1959000 00001000 00000000 00000000 c022b738
c037ed20
(XEN) 00000000 c0800000 c073e020 00000800 c0361bef c073e020 00000400
c02f0a33
(XEN) c0355f60 00004000 00000000 00000000 00000000 00000000 00004000
00000000
(XEN) 00000004 00000003 c073d018 00000000 c073d000 00000000 00000000
c0362025
(XEN) c073d000 00000000 c0364880 c0385ff0 c0353060 c02c7c37 00000000
c03622f8
(XEN) 006447ff c02f0a33 c0353060 c035d1e5 c02f0a33 c0100000 c035d83b
c0355ff4
(XEN) c036cbe0 00000080 00000000 0000006c 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 ffffe000 c073a000
00000000
(XEN) ffffe000 c073a000 00000000 00000000 c0356867 c0355ff4 00000000
00000000
(XEN) 00000000 00000000 c037e100 0702080b c010007a
(XEN) (file=memory.c, line=57) Could not allocate order=0 extent: id=73
flags=0 (13715 of 39271)
(XEN) Domain 81 (vcpu#0) crashed on cpu#3:
(XEN) CPU: 3
(XEN) EIP: e019:[<c01159b6>]
(XEN) EFLAGS: 00000246 CONTEXT: guest
(XEN) eax: 000005a8 ebx: 00000000 ecx: 00000000 edx: 00000000
(XEN) esi: 00000000 edi: 00000000 ebp: 000005a8 esp: c0355e8c
(XEN) cr0: 8005003b cr3: e2d72000
(XEN) ds: e021 es: e021 fs: 0000 gs: e021 ss: e021 cs: e019
(XEN) Guest stack trace from esp=c0355e8c:
(XEN) c00005ac 00000003 c01159b6 0001e019 00010246 00000000 00000000
00000000
(XEN) c0000000 c0361875 c20b5000 00001000 00000000 00000000 c022b738
c037ed20
(XEN) 00000000 c0800000 c073e020 00000800 c0361bef c073e020 00000400
c02f0a33
(XEN) c0355f60 00004000 00000000 00000000 00000000 00000000 00004000
00000000
(XEN) 00000004 00000003 c073d018 00000000 c073d000 00000000 00000000
c0362025
(XEN) c073d000 00000000 c0364880 c0385ff0 c0353060 c02c7c37 00000000
c03622f8
(XEN) 006447ff c02f0a33 c0353060 c035d1e5 c02f0a33 c0100000 c035d83b
c0355ff4
(XEN) c036cbe0 00000080 00000000 0000006c 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 ffffe000 c073a000
00000000
(XEN) ffffe000 c073a000 00000000 00000000 c0356867 c0355ff4 00000000
00000000
(XEN) 00000000 00000000 c037e100 0702080b c010007a
(XEN) Domain 102 (vcpu#0) crashed on cpu#3:
(XEN) CPU: 3
(XEN) EIP: e019:[<c01159b6>]
(XEN) EFLAGS: 00000246 CONTEXT: guest
(XEN) eax: 00000920 ebx: 00000000 ecx: 00000000 edx: 00000000
(XEN) esi: 00000000 edi: 00000000 ebp: 00000920 esp: c0355e8c
(XEN) cr0: 8005003b cr3: f293e000
(XEN) ds: e021 es: e021 fs: 0000 gs: e021 ss: e021 cs: e019
(XEN) Guest stack trace from esp=c0355e8c:
(XEN) c0000924 00000003 c01159b6 0001e019 00010246 00000000 00000000
00000000
(XEN) c0000000 c0361875 c2124000 00001000 00000000 00000000 c022b738
c037ed20
(XEN) 00000000 c0800000 c073e020 00000800 c0361bef c073e020 00000400
c02f0a33
(XEN) c0355f60 00004000 00000000 00000000 00000000 00000000 00004000
00000000
(XEN) 00000004 00000003 c073d018 00000000 c073d000 00000000 00000000
c0362025
(XEN) c073d000 00000000 c0364880 c0385ff0 c0353060 c02c7c37 00000000
c03622f8
(XEN) 006447ff c02f0a33 c0353060 c035d1e5 c02f0a33 c0100000 c035d83b
c0355ff4
(XEN) c036cbe0 00000080 00000000 0000006c 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 ffffe000 c073a000
00000000
(XEN) ffffe000 c073a000 00000000 00000000 c0356867 c0355ff4 00000000
00000000
(XEN) 00000000 00000000 c037e100 0702080b c010007a
x335b:~ # dmesg
Linux version 2.6.12-xen0 (root@x335b) (gcc version 3.3.3 (SuSE Linux))
#1 Thu Oct 13 06:38:56 CDT 2005
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 000000001f400000 (usable)
0MB HIGHMEM available.
500MB LOWMEM available.
On node 0 totalpages: 128000
DMA zone: 128000 pages, LIFO batch:31
Normal zone: 0 pages, LIFO batch:1
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 IBM ) @ 0x000fdfc0
ACPI: RSDT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
0xf7feff80
ACPI: FADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
0xf7feff00
ACPI: MADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
0xf7fefe40
ACPI: ASF! (v016 IBM SERONYXP 0x00000001 IBM 0x45444f43) @
0xf7fefd80
ACPI: DSDT (v001 IBM SERTURQU 0x00001000 MSFT 0x0100000b) @
0x00000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 14, version 17, address 0xfec00000, GSI 0-15
ACPI: IOAPIC (id[0x0d] address[0xfec01000] gsi_base[16])
IOAPIC[1]: apic_id 13, version 17, address 0xfec01000, GSI 16-31
ACPI: IOAPIC (id[0x0c] address[0xfec02000] gsi_base[32])
IOAPIC[2]: apic_id 12, version 17, address 0xfec02000, GSI 32-47
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ5 used by override.
Enabling APIC mode: Flat. Using 3 I/O APICs
Using ACPI (MADT) for SMP configuration information
IRQ lockup detection disabled
Allocating PCI resources starting at f8000000 (gap: f8000000:06c00000)
Built 1 zonelists
Kernel command line: root=/dev/sda2 ro console=tty0
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 32768 bytes)
Xen reported: 3189.368 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Software IO TLB enabled:
Aperture: 64 megabytes
Bus range: 0x0000000004000000 - 0x0000000008000000
Kernel range: 0x00000000c1456000 - 0x00000000c5456000
vmalloc area: e0000000-f53fe000, maxmem 2d800000
Memory: 434560k/512000k available (3563k kernel code, 77308k reserved,
1134k data, 356k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Calibrating delay loop... 6370.09 BogoMIPS (lpj=31850496)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000
00004400 00000000 00000000
CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000
00004400 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: L3 cache: 1024K
CPU: After all inits, caps: bfebd3f1 00000000 00000000 00000080 00004400
00000000 00000000
CPU: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
ENABLING IO-APIC IRQs
NET: Registered protocol family 16
PCI: Using configuration type 1
ACPI: Subsystem revision 20050309
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
Boot video device is 0000:00:01.0
PCI: Ignoring BAR0-3 of IDE controller 0000:00:0f.1
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Root Bridge [PCI1] (0000:01)
PCI: Probing PCI hardware (bus 01)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1._PRT]
ACPI: PCI Root Bridge [PCI2] (0000:02)
PCI: Probing PCI hardware (bus 02)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI2._PRT]
ACPI: PCI Interrupt Link [LP00] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP01] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP02] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP03] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP04] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP05] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP06] (IRQs *9)
ACPI: PCI Interrupt Link [LP07] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP08] (IRQs *3)
ACPI: PCI Interrupt Link [LP09] (IRQs *4)
ACPI: PCI Interrupt Link [LP0A] (IRQs *10)
ACPI: PCI Interrupt Link [LP0B] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP0C] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP0D] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP0E] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP0F] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP10] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP11] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP12] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP13] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP14] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP15] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP16] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP17] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP18] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP19] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP1A] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP1B] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP1C] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP1D] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP1E] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LP1F] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LPUS] (IRQs *11)
xen_mem: Initialising balloon driver.
SCSI subsystem initialized
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a
report
Grant table initialized
IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com>
Initializing Cryptographic API
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
HP CISS Driver (v 2.6.6)
Intel(R) PRO/1000 Network Driver - version 6.0.54-k2
Copyright (c) 1999-2004 Intel Corporation.
pcnet32.c:v1.30j 29.04.2005 tsbogend@alpha.franken.de
e100: Intel(R) PRO/100 Network Driver, 3.4.8-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
tg3.c:v3.31 (June 8, 2005)
ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 24 (level, low) -> IRQ 24
eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-
bit) 10/100/1000BaseT Ethernet 00:11:25:3e:39:f2
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1]
TSOcap[1]
eth0: dma_rwctrl[769f4000]
ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 25 (level, low) -> IRQ 25
eth1: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-
bit) 10/100/1000BaseT Ethernet 00:11:25:3e:39:f3
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1]
TSOcap[1]
eth1: dma_rwctrl[769f4000]
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Xen virtual console successfully installed as ttyS0
Event-channel device installed.
xen_net: Initialising Xen netif backend.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
SvrWks CSB5: IDE controller at PCI slot 0000:00:0f.1
SvrWks CSB5: chipset revision 147
SvrWks CSB5: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x0700-0x0707, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0x0708-0x070f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
Probing IDE interface ide1...
hdc: LG CD-ROM CRN-8245B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
Probing IDE interface ide0...
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
hdc: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
Red Hat/Adaptec aacraid driver (1.1.2-lk2 Oct 13 2005)
3ware Storage Controller device driver for Linux v1.26.02.001.
libata version 1.11 loaded.
Fusion MPT base driver 3.01.20
Copyright (c) 1999-2004 LSI Logic Corporation
ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 22 (level, low) -> IRQ 22
mptbase: Initiating ioc0 bringup
ioc0: 53C1030: Capabilities={Initiator}
Fusion MPT SCSI Host driver 3.01.20
scsi0 : ioc0: LSI53C1030, FwRev=01000e00h, Ports=1, MaxQ=222, IRQ=22
Vendor: IBM-ESXS Model: MAS3367NC FN Rev: C901
Type: Direct-Access ANSI SCSI revision: 03
SCSI device sda: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sda: drive cache: write through
SCSI device sda: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sda: drive cache: write through
sda: sda1 sda2
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: IBM-ESXS Model: MAS3367NC FN Rev: C901
Type: Direct-Access ANSI SCSI revision: 03
SCSI device sdb: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sdb: drive cache: write through
SCSI device sdb: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sdb: drive cache: write through
sdb: sdb1 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 >
Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
Vendor: IBM Model: 25P3495a S320 1 Rev: 1
Type: Processor ANSI SCSI revision: 02
usbmon: debugs is not available
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ACPI: PCI Interrupt Link [LPUS] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:0f.2[A] -> Link [LPUS] -> GSI 11 (level,
low) -> IRQ 11
ohci_hcd 0000:00:0f.2: OHCI Host Controller
ohci_hcd 0000:00:0f.2: new USB bus registered, assigned bus number 1
ohci_hcd 0000:00:0f.2: irq 11, io mem 0xfebfe000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
USB Universal Host Controller Interface driver v2.2
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
mice: PS/2 mouse device common for all mice
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: automatically using best checksumming function: pIII_sse
pIII_sse : 1466.000 MB/sec
raid5: using function: pIII_sse (1466.000 MB/sec)
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
NET: Registered protocol family 2
input: AT Translated Set 2 keyboard on isa0060/serio0
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
input: PS/2 Generic Mouse on isa0060/serio1
Bridge firewalling registered
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 356k freed
kjournald starting. Commit interval 5 seconds
EXT3 (no)acl options not supported
EXT3 (no)acl options not supported
EXT3 FS on sda2, internal journal
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Adding 1052216k swap on /dev/sda1. Priority:42 extents:1
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
Linux agpgart interface v0.101 (c) Dave Jones
ACPI: Power Button (FF) [PWRF]
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
program hwscan is using a deprecated SCSI ioctl, please convert it to
SG_IO
program hwscan is using a deprecated SCSI ioctl, please convert it to
SG_IO
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
nfs warning: mount version older than kernel
device vif0.0 entered promiscuous mode
bridge: can't decode speed from peth0: 0
device peth0 entered promiscuous mode
xen-br0: port 1(vif0.0) entering learning state
xen-br0: topology change detected, propagating
xen-br0: port 1(vif0.0) entering forwarding state
tg3: peth0: Link is up at 100 Mbps, full duplex.
tg3: peth0: Flow control is on for TX and on for RX.
xen-br0: port 2(peth0) entering learning state
xen-br0: topology change detected, propagating
xen-br0: port 2(peth0) entering forwarding state
device vif74.1 entered promiscuous mode
xen-br0: port 3(vif74.1) entering learning state
xen-br0: topology change detected, propagating
xen-br0: port 3(vif74.1) entering forwarding state
device vif75.1 entered promiscuous mode
xen-br0: port 4(vif75.1) entering learning state
xen-br0: topology change detected, propagating
xen-br0: port 4(vif75.1) entering forwarding state
xen-br0: port 4(vif75.1) entering disabled state
device vif75.1 left promiscuous mode
xen-br0: port 4(vif75.1) entering disabled state
device vif76.1 entered promiscuous mode
xen-br0: port 4(vif76.1) entering learning state
xen-br0: topology change detected, propagating
xen-br0: port 4(vif76.1) entering forwarding state
device vif77.1 entered promiscuous mode
xen-br0: port 5(vif77.1) entering learning state
xen-br0: topology change detected, propagating
xen-br0: port 5(vif77.1) entering forwarding state
x335b:~ #
The last output from 'xm-test' is:
x335b:/tmp/logs/xm-test # tail x335sles9_pae4gb.output
Using config file "/dev/null".
Started domain testdomain
[dom0] Running `xm destroy testdomain'
[dom0] Running `xm create /dev/null ramdisk=../../ramdisk/initrd.img
kernel=/boot/vmlinuz-2.6.12-xenU name=testdomain nics=0 vcpus=1
memory=64 root=/dev/ram0'
Using config file "/dev/null".
Started domain testdomain
[dom0] Running `xm destroy testdomain'
PASS: 10_create_fastdestroy.test
x335b:/tmp/logs/xm-test #
On Wed, 2005-09-28 at 15:24 -0500, David F Barrera wrote:
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=265
>
> While running xm-test on two IBM xSeries 335s, one FC4 and the other one
> SLES 9, I noticed that time has stopped:
>
> [root@x335a xm-test]# date
> Wed Sep 28 13:59:18 CDT 2005
> [root@x335a xm-test]# date
> Wed Sep 28 13:59:18 CDT 2005
>
> >> 15 minutes later,
> [root@x335a xm-test]# date
> Wed Sep 28 13:59:18 CDT 2005
> [root@x335a xm-test]#
>
> changeset: 7076:46046d5fb354
> tag: tip
> user: emellor@ewan
> date: Tue Sep 27 16:09:46 2005 +0100
> summary: Remove unused import, mark unused variables.
>
> The last output lines produced by xm-test are:
> cp 06_destroy_dom0_neg.py 06_destroy_dom0_neg.test
> chmod +x 06_destroy_dom0_neg.test
>
> The machines in question are running xm-test at the moment and appear
> 'stuck'.
> Both are displaying the "(XEN) Ouch! We are seriously BEHIND schedule!"
> messages. However, the static time issue may not be related to the Ouch!
> issue, bug # 257, as Paul Larson observed it on a machine that was not
> running xm-test at the time, hence we are submitting it as a different
> bug.
>
>
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: Time stopped
2005-10-13 15:17 ` David F Barrera
@ 2005-10-13 15:36 ` David F Barrera
0 siblings, 0 replies; 18+ messages in thread
From: David F Barrera @ 2005-10-13 15:36 UTC (permalink / raw)
To: xen-devel
I am seeing the problem on another xSeries 335, FC4, 2GB RAM, both PAE
enabled, changet 7353:29db5bded574. This other machine, however, does
not show a trace, so the time and the "Domain 63 (vcpu#0) crashed on
cpu#3:" issues may be different problems. Bug reports:
265 2005-09-28 dbarrera@us.ibm.com Time stood still
267 2005-09-29 dbarrera@us.ibm.com (XEN) Domain 2 (vcpu#0) crashed on
cpu#3:
On Thu, 2005-10-13 at 10:17 -0500, David F Barrera wrote:
> I continue to encounter this problem daily on an IBM xSeries 335 SLES 9
> SP2, 4GB RAM machine while running XM-TEST. The time has not actually
> stopped, but moves forward at an exceedingly slow pace. The 'date'
> command will actually show that a second has transpired in the period
> of, say, 10 actual minutes (or more). 'xm dmesg' is showing a trace.
>
> x335b:~ # xm list
> Name ID Mem(MiB) CPU VCPUs State Time(s)
> Domain-0 0 495 0 1 r----- 110.9
> 11_create_0 131 16 3 1 -b---- 0.3
> x335b:~ # date
> Thu Oct 13 09:52:23 CDT 2005
> x335b:~ # date
> Thu Oct 13 09:52:23 CDT 2005
> x335b:~ # date
> Thu Oct 13 09:52:23 CDT 2005
> x335b:~ # xm list
> Name ID Mem(MiB) CPU VCPUs State Time(s)
> Domain-0 0 495 0 1 r----- 110.9
> 11_create_0 131 16 3 1 -b---- 0.3
> x335b:~ # date
> Thu Oct 13 09:52:24 CDT 2005
> x335b:~ # date
> Thu Oct 13 09:52:24 CDT 2005
>
> x335b:~ # xm dmesg
> __ __ _____ ___ _ _
> \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| |
> \ // _ \ '_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
> / \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ |
> /_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_|
>
> http://www.cl.cam.ac.uk/netos/xen
> University of Cambridge Computer Laboratory
>
> Xen version 3.0-devel (root@ltc.austin.ibm.com) (gcc version 3.3.3
> (SuSE Linux)) Thu Oct 13 06:30:24 CDT 2005
> Latest ChangeSet: Wed Oct 12 10:15:02 2005 +0100 7353:29db5bded574
>
> (XEN) Physical RAM map:
> (XEN) 0000000000000000 - 000000000009d400 (usable)
> (XEN) 000000000009d400 - 00000000000a0000 (reserved)
> (XEN) 00000000000e0000 - 0000000000100000 (reserved)
> (XEN) 0000000000100000 - 00000000f7fec140 (usable)
> (XEN) 00000000f7fec140 - 00000000f7ff0000 (ACPI data)
> (XEN) 00000000f7ff0000 - 00000000f8000000 (reserved)
> (XEN) 00000000fec00000 - 0000000100000000 (reserved)
> (XEN) 0000000100000000 - 0000000108000000 (usable)
> (XEN) System RAM: 4095MB (4193828kB)
> (XEN) Xen heap: 10MB (10496kB)
> (XEN) PAE enabled, limit: 16 GB
> (XEN) found SMP MP-table at 0009d540
> (XEN) DMI 2.3 present.
> (XEN) Using APIC driver default
> (XEN) ACPI: RSDP (v000 IBM ) @
> 0x000fdfc0
> (XEN) ACPI: RSDT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> 0xf7feff80
> (XEN) ACPI: FADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> 0xf7feff00
> (XEN) ACPI: MADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> 0xf7fefe40
> (XEN) ACPI: ASF! (v016 IBM SERONYXP 0x00000001 IBM 0x45444f43) @
> 0xf7fefd80
> (XEN) ACPI: DSDT (v001 IBM SERTURQU 0x00001000 MSFT 0x0100000b) @
> 0x00000000
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> (XEN) Processor #0 15:2 APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
> (XEN) Processor #6 15:2 APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> (XEN) Processor #1 15:2 APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
> (XEN) Processor #7 15:2 APIC version 20
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
> (XEN) ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 14, version 17, address 0xfec00000, GSI 0-15
> (XEN) ACPI: IOAPIC (id[0x0d] address[0xfec01000] gsi_base[16])
> (XEN) IOAPIC[1]: apic_id 13, version 17, address 0xfec01000, GSI 16-31
> (XEN) ACPI: IOAPIC (id[0x0c] address[0xfec02000] gsi_base[32])
> (XEN) IOAPIC[2]: apic_id 12, version 17, address 0xfec02000, GSI 32-47
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> (XEN) ACPI: IRQ0 used by override.
> (XEN) ACPI: IRQ2 used by override.
> (XEN) Enabling APIC mode: Flat. Using 3 I/O APICs
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) Initializing CPU#0
> (XEN) Detected 3189.471 MHz processor.
> (XEN) Using scheduler: Simple EDF Scheduler (sedf)
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> (XEN) CPU: L2 cache: 512K
> (XEN) CPU: L3 cache: 1024K
> (XEN) CPU: Physical Processor ID: 0
> (XEN) CPU0: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
> (XEN) Booting processor 1/1 eip 90000
> (XEN) Initializing CPU#1
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> (XEN) CPU: L2 cache: 512K
> (XEN) CPU: L3 cache: 1024K
> (XEN) CPU: Physical Processor ID: 0
> (XEN) CPU1: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
> (XEN) Booting processor 2/6 eip 90000
> (XEN) Initializing CPU#2
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> (XEN) CPU: L2 cache: 512K
> (XEN) CPU: L3 cache: 1024K
> (XEN) CPU: Physical Processor ID: 3
> (XEN) CPU2: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
> (XEN) Booting processor 3/7 eip 90000
> (XEN) Initializing CPU#3
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> (XEN) CPU: L2 cache: 512K
> (XEN) CPU: L3 cache: 1024K
> (XEN) CPU: Physical Processor ID: 3
> (XEN) CPU3: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
> (XEN) Total of 4 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
> (XEN) checking TSC synchronization across 4 CPUs: passed.
> (XEN) Platform timer is 1.193MHz PIT
> (XEN) Brought up 4 CPUs
> (XEN) mtrr: v2.0 (20020519)
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen-ELF header found:
> 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,PAE=yes,LOADER=generic'
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN) Dom0 alloc.: 0000000003800000->0000000004000000 (125952 pages
> to be allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN) Loaded kernel: c0100000->c06394e4
> (XEN) Init. ramdisk: c063a000->c063a000
> (XEN) Phys-Mach map: c063a000->c06b7000
> (XEN) Start info: c06b7000->c06b8000
> (XEN) Page tables: c06b8000->c06c1000
> (XEN) Boot stack: c06c1000->c06c2000
> (XEN) TOTAL: c0000000->c0800000
> (XEN) ENTRY ADDRESS: c0100000
> (XEN) Scrubbing Free
> RAM: ...........................................done.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen).
> (XEN) microcode: CPU1 updated from revision 0x11 to 0x29, date =
> 08112004
> (XEN) microcode: CPU2 updated from revision 0x11 to 0x29, date =
> 08112004
> (XEN) microcode: CPU3 updated from revision 0x11 to 0x29, date =
> 08112004
> (XEN) microcode: CPU0 updated from revision 0x11 to 0x29, date =
> 08112004
> (XEN) mtrr: type mismatch for fd000000,800000 old: write-back new:
> write-combining
> (XEN) mtrr: type mismatch for fd000000,800000 old: write-back new:
> write-combining
> (XEN) Domain 63 (vcpu#0) crashed on cpu#3:
> (XEN) CPU: 3
> (XEN) EIP: e019:[<c01159b6>]
> (XEN) EFLAGS: 00000246 CONTEXT: guest
> (XEN) eax: 00000ac8 ebx: 00000000 ecx: 00000000 edx: 00000000
> (XEN) esi: 00000000 edi: 00000000 ebp: 00000ac8 esp: c0355e8c
> (XEN) cr0: 8005003b cr3: e3b58000
> (XEN) ds: e021 es: e021 fs: 0000 gs: e021 ss: e021 cs: e019
> (XEN) Guest stack trace from esp=c0355e8c:
> (XEN) c0000acc 00000003 c01159b6 0001e019 00010246 00000000 00000000
> 00000000
> (XEN) c0000000 c0361875 c1959000 00001000 00000000 00000000 c022b738
> c037ed20
> (XEN) 00000000 c0800000 c073e020 00000800 c0361bef c073e020 00000400
> c02f0a33
> (XEN) c0355f60 00004000 00000000 00000000 00000000 00000000 00004000
> 00000000
> (XEN) 00000004 00000003 c073d018 00000000 c073d000 00000000 00000000
> c0362025
> (XEN) c073d000 00000000 c0364880 c0385ff0 c0353060 c02c7c37 00000000
> c03622f8
> (XEN) 006447ff c02f0a33 c0353060 c035d1e5 c02f0a33 c0100000 c035d83b
> c0355ff4
> (XEN) c036cbe0 00000080 00000000 0000006c 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 ffffe000 c073a000
> 00000000
> (XEN) ffffe000 c073a000 00000000 00000000 c0356867 c0355ff4 00000000
> 00000000
> (XEN) 00000000 00000000 c037e100 0702080b c010007a
> (XEN) (file=memory.c, line=57) Could not allocate order=0 extent: id=73
> flags=0 (13715 of 39271)
> (XEN) Domain 81 (vcpu#0) crashed on cpu#3:
> (XEN) CPU: 3
> (XEN) EIP: e019:[<c01159b6>]
> (XEN) EFLAGS: 00000246 CONTEXT: guest
> (XEN) eax: 000005a8 ebx: 00000000 ecx: 00000000 edx: 00000000
> (XEN) esi: 00000000 edi: 00000000 ebp: 000005a8 esp: c0355e8c
> (XEN) cr0: 8005003b cr3: e2d72000
> (XEN) ds: e021 es: e021 fs: 0000 gs: e021 ss: e021 cs: e019
> (XEN) Guest stack trace from esp=c0355e8c:
> (XEN) c00005ac 00000003 c01159b6 0001e019 00010246 00000000 00000000
> 00000000
> (XEN) c0000000 c0361875 c20b5000 00001000 00000000 00000000 c022b738
> c037ed20
> (XEN) 00000000 c0800000 c073e020 00000800 c0361bef c073e020 00000400
> c02f0a33
> (XEN) c0355f60 00004000 00000000 00000000 00000000 00000000 00004000
> 00000000
> (XEN) 00000004 00000003 c073d018 00000000 c073d000 00000000 00000000
> c0362025
> (XEN) c073d000 00000000 c0364880 c0385ff0 c0353060 c02c7c37 00000000
> c03622f8
> (XEN) 006447ff c02f0a33 c0353060 c035d1e5 c02f0a33 c0100000 c035d83b
> c0355ff4
> (XEN) c036cbe0 00000080 00000000 0000006c 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 ffffe000 c073a000
> 00000000
> (XEN) ffffe000 c073a000 00000000 00000000 c0356867 c0355ff4 00000000
> 00000000
> (XEN) 00000000 00000000 c037e100 0702080b c010007a
> (XEN) Domain 102 (vcpu#0) crashed on cpu#3:
> (XEN) CPU: 3
> (XEN) EIP: e019:[<c01159b6>]
> (XEN) EFLAGS: 00000246 CONTEXT: guest
> (XEN) eax: 00000920 ebx: 00000000 ecx: 00000000 edx: 00000000
> (XEN) esi: 00000000 edi: 00000000 ebp: 00000920 esp: c0355e8c
> (XEN) cr0: 8005003b cr3: f293e000
> (XEN) ds: e021 es: e021 fs: 0000 gs: e021 ss: e021 cs: e019
> (XEN) Guest stack trace from esp=c0355e8c:
> (XEN) c0000924 00000003 c01159b6 0001e019 00010246 00000000 00000000
> 00000000
> (XEN) c0000000 c0361875 c2124000 00001000 00000000 00000000 c022b738
> c037ed20
> (XEN) 00000000 c0800000 c073e020 00000800 c0361bef c073e020 00000400
> c02f0a33
> (XEN) c0355f60 00004000 00000000 00000000 00000000 00000000 00004000
> 00000000
> (XEN) 00000004 00000003 c073d018 00000000 c073d000 00000000 00000000
> c0362025
> (XEN) c073d000 00000000 c0364880 c0385ff0 c0353060 c02c7c37 00000000
> c03622f8
> (XEN) 006447ff c02f0a33 c0353060 c035d1e5 c02f0a33 c0100000 c035d83b
> c0355ff4
> (XEN) c036cbe0 00000080 00000000 0000006c 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 ffffe000 c073a000
> 00000000
> (XEN) ffffe000 c073a000 00000000 00000000 c0356867 c0355ff4 00000000
> 00000000
> (XEN) 00000000 00000000 c037e100 0702080b c010007a
>
>
> x335b:~ # dmesg
> Linux version 2.6.12-xen0 (root@x335b) (gcc version 3.3.3 (SuSE Linux))
> #1 Thu Oct 13 06:38:56 CDT 2005
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 000000001f400000 (usable)
> 0MB HIGHMEM available.
> 500MB LOWMEM available.
> On node 0 totalpages: 128000
> DMA zone: 128000 pages, LIFO batch:31
> Normal zone: 0 pages, LIFO batch:1
> HighMem zone: 0 pages, LIFO batch:1
> DMI 2.3 present.
> ACPI: RSDP (v000 IBM ) @ 0x000fdfc0
> ACPI: RSDT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> 0xf7feff80
> ACPI: FADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> 0xf7feff00
> ACPI: MADT (v001 IBM SERONYXP 0x00001000 IBM 0x45444f43) @
> 0xf7fefe40
> ACPI: ASF! (v016 IBM SERONYXP 0x00000001 IBM 0x45444f43) @
> 0xf7fefd80
> ACPI: DSDT (v001 IBM SERTURQU 0x00001000 MSFT 0x0100000b) @
> 0x00000000
> ACPI: Local APIC address 0xfee00000
> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
> ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
> ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
> ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0])
> IOAPIC[0]: apic_id 14, version 17, address 0xfec00000, GSI 0-15
> ACPI: IOAPIC (id[0x0d] address[0xfec01000] gsi_base[16])
> IOAPIC[1]: apic_id 13, version 17, address 0xfec01000, GSI 16-31
> ACPI: IOAPIC (id[0x0c] address[0xfec02000] gsi_base[32])
> IOAPIC[2]: apic_id 12, version 17, address 0xfec02000, GSI 32-47
> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> ACPI: IRQ0 used by override.
> ACPI: IRQ2 used by override.
> ACPI: IRQ5 used by override.
> Enabling APIC mode: Flat. Using 3 I/O APICs
> Using ACPI (MADT) for SMP configuration information
> IRQ lockup detection disabled
> Allocating PCI resources starting at f8000000 (gap: f8000000:06c00000)
> Built 1 zonelists
> Kernel command line: root=/dev/sda2 ro console=tty0
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 32768 bytes)
> Xen reported: 3189.368 MHz processor.
> Console: colour VGA+ 80x25
> Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
> Software IO TLB enabled:
> Aperture: 64 megabytes
> Bus range: 0x0000000004000000 - 0x0000000008000000
> Kernel range: 0x00000000c1456000 - 0x00000000c5456000
> vmalloc area: e0000000-f53fe000, maxmem 2d800000
> Memory: 434560k/512000k available (3563k kernel code, 77308k reserved,
> 1134k data, 356k init, 0k highmem)
> Checking if this processor honours the WP bit even in supervisor mode...
> Ok.
> Calibrating delay loop... 6370.09 BogoMIPS (lpj=31850496)
> Mount-cache hash table entries: 512
> CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000
> 00004400 00000000 00000000
> CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000
> 00004400 00000000 00000000
> CPU: Trace cache: 12K uops, L1 D cache: 8K
> CPU: L2 cache: 512K
> CPU: L3 cache: 1024K
> CPU: After all inits, caps: bfebd3f1 00000000 00000000 00000080 00004400
> 00000000 00000000
> CPU: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... disabled
> ENABLING IO-APIC IRQs
> NET: Registered protocol family 16
> PCI: Using configuration type 1
> ACPI: Subsystem revision 20050309
> ACPI: Interpreter enabled
> ACPI: Using IOAPIC for interrupt routing
> ACPI: PCI Root Bridge [PCI0] (0000:00)
> PCI: Probing PCI hardware (bus 00)
> Boot video device is 0000:00:01.0
> PCI: Ignoring BAR0-3 of IDE controller 0000:00:0f.1
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> ACPI: PCI Root Bridge [PCI1] (0000:01)
> PCI: Probing PCI hardware (bus 01)
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI1._PRT]
> ACPI: PCI Root Bridge [PCI2] (0000:02)
> PCI: Probing PCI hardware (bus 02)
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI2._PRT]
> ACPI: PCI Interrupt Link [LP00] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP01] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP02] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP03] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP04] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP05] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP06] (IRQs *9)
> ACPI: PCI Interrupt Link [LP07] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP08] (IRQs *3)
> ACPI: PCI Interrupt Link [LP09] (IRQs *4)
> ACPI: PCI Interrupt Link [LP0A] (IRQs *10)
> ACPI: PCI Interrupt Link [LP0B] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP0C] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP0D] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP0E] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP0F] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP10] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP11] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP12] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP13] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP14] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP15] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP16] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP17] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP18] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP19] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP1A] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP1B] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP1C] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP1D] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP1E] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LP1F] (IRQs) *0, disabled.
> ACPI: PCI Interrupt Link [LPUS] (IRQs *11)
> xen_mem: Initialising balloon driver.
> SCSI subsystem initialized
> usbcore: registered new driver hub
> PCI: Using ACPI for IRQ routing
> PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a
> report
> Grant table initialized
> IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com>
> Initializing Cryptographic API
> serio: i8042 AUX port at 0x60,0x64 irq 12
> serio: i8042 KBD port at 0x60,0x64 irq 1
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a National Semiconductor PC87306
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> loop: loaded (max 8 devices)
> HP CISS Driver (v 2.6.6)
> Intel(R) PRO/1000 Network Driver - version 6.0.54-k2
> Copyright (c) 1999-2004 Intel Corporation.
> pcnet32.c:v1.30j 29.04.2005 tsbogend@alpha.franken.de
> e100: Intel(R) PRO/100 Network Driver, 3.4.8-k2-NAPI
> e100: Copyright(c) 1999-2005 Intel Corporation
> tg3.c:v3.31 (June 8, 2005)
> ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 24 (level, low) -> IRQ 24
> eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-
> bit) 10/100/1000BaseT Ethernet 00:11:25:3e:39:f2
> eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1]
> TSOcap[1]
> eth0: dma_rwctrl[769f4000]
> ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 25 (level, low) -> IRQ 25
> eth1: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-
> bit) 10/100/1000BaseT Ethernet 00:11:25:3e:39:f3
> eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1]
> TSOcap[1]
> eth1: dma_rwctrl[769f4000]
> tun: Universal TUN/TAP device driver, 1.6
> tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
> Xen virtual console successfully installed as ttyS0
> Event-channel device installed.
> xen_net: Initialising Xen netif backend.
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx
> SvrWks CSB5: IDE controller at PCI slot 0000:00:0f.1
> SvrWks CSB5: chipset revision 147
> SvrWks CSB5: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0x0700-0x0707, BIOS settings: hda:pio, hdb:pio
> ide1: BM-DMA at 0x0708-0x070f, BIOS settings: hdc:DMA, hdd:DMA
> Probing IDE interface ide0...
> Probing IDE interface ide1...
> hdc: LG CD-ROM CRN-8245B, ATAPI CD/DVD-ROM drive
> ide1 at 0x170-0x177,0x376 on irq 15
> Probing IDE interface ide0...
> Probing IDE interface ide2...
> Probing IDE interface ide3...
> Probing IDE interface ide4...
> Probing IDE interface ide5...
> hdc: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33)
> Uniform CD-ROM driver Revision: 3.20
> Red Hat/Adaptec aacraid driver (1.1.2-lk2 Oct 13 2005)
> 3ware Storage Controller device driver for Linux v1.26.02.001.
> libata version 1.11 loaded.
> Fusion MPT base driver 3.01.20
> Copyright (c) 1999-2004 LSI Logic Corporation
> ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 22 (level, low) -> IRQ 22
> mptbase: Initiating ioc0 bringup
> ioc0: 53C1030: Capabilities={Initiator}
> Fusion MPT SCSI Host driver 3.01.20
> scsi0 : ioc0: LSI53C1030, FwRev=01000e00h, Ports=1, MaxQ=222, IRQ=22
> Vendor: IBM-ESXS Model: MAS3367NC FN Rev: C901
> Type: Direct-Access ANSI SCSI revision: 03
> SCSI device sda: 71096640 512-byte hdwr sectors (36401 MB)
> SCSI device sda: drive cache: write through
> SCSI device sda: 71096640 512-byte hdwr sectors (36401 MB)
> SCSI device sda: drive cache: write through
> sda: sda1 sda2
> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
> Vendor: IBM-ESXS Model: MAS3367NC FN Rev: C901
> Type: Direct-Access ANSI SCSI revision: 03
> SCSI device sdb: 71096640 512-byte hdwr sectors (36401 MB)
> SCSI device sdb: drive cache: write through
> SCSI device sdb: 71096640 512-byte hdwr sectors (36401 MB)
> SCSI device sdb: drive cache: write through
> sdb: sdb1 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 >
> Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
> Vendor: IBM Model: 25P3495a S320 1 Rev: 1
> Type: Processor ANSI SCSI revision: 02
> usbmon: debugs is not available
> ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
> ACPI: PCI Interrupt Link [LPUS] enabled at IRQ 11
> ACPI: PCI Interrupt 0000:00:0f.2[A] -> Link [LPUS] -> GSI 11 (level,
> low) -> IRQ 11
> ohci_hcd 0000:00:0f.2: OHCI Host Controller
> ohci_hcd 0000:00:0f.2: new USB bus registered, assigned bus number 1
> ohci_hcd 0000:00:0f.2: irq 11, io mem 0xfebfe000
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 4 ports detected
> USB Universal Host Controller Interface driver v2.2
> usbcore: registered new driver usbhid
> drivers/usb/input/hid-core.c: v2.01:USB HID core driver
> mice: PS/2 mouse device common for all mice
> md: raid0 personality registered as nr 2
> md: raid1 personality registered as nr 3
> md: raid5 personality registered as nr 4
> raid5: automatically using best checksumming function: pIII_sse
> pIII_sse : 1466.000 MB/sec
> raid5: using function: pIII_sse (1466.000 MB/sec)
> md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
> device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
> NET: Registered protocol family 2
> input: AT Translated Set 2 keyboard on isa0060/serio0
> IP: routing cache hash table of 4096 buckets, 32Kbytes
> TCP established hash table entries: 16384 (order: 5, 131072 bytes)
> TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
> TCP: Hash tables configured (established 16384 bind 16384)
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> input: PS/2 Generic Mouse on isa0060/serio1
> Bridge firewalling registered
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> EXT3-fs: mounted filesystem with ordered data mode.
> VFS: Mounted root (ext3 filesystem) readonly.
> Freeing unused kernel memory: 356k freed
> kjournald starting. Commit interval 5 seconds
> EXT3 (no)acl options not supported
> EXT3 (no)acl options not supported
> EXT3 FS on sda2, internal journal
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> Adding 1052216k swap on /dev/sda1. Priority:42 extents:1
> tg3: eth0: Link is up at 100 Mbps, full duplex.
> tg3: eth0: Flow control is on for TX and on for RX.
> Linux agpgart interface v0.101 (c) Dave Jones
> ACPI: Power Button (FF) [PWRF]
> end_request: I/O error, dev fd0, sector 0
> end_request: I/O error, dev fd0, sector 0
> program hwscan is using a deprecated SCSI ioctl, please convert it to
> SG_IO
> program hwscan is using a deprecated SCSI ioctl, please convert it to
> SG_IO
> end_request: I/O error, dev fd0, sector 0
> end_request: I/O error, dev fd0, sector 0
> nfs warning: mount version older than kernel
> device vif0.0 entered promiscuous mode
> bridge: can't decode speed from peth0: 0
> device peth0 entered promiscuous mode
> xen-br0: port 1(vif0.0) entering learning state
> xen-br0: topology change detected, propagating
> xen-br0: port 1(vif0.0) entering forwarding state
> tg3: peth0: Link is up at 100 Mbps, full duplex.
> tg3: peth0: Flow control is on for TX and on for RX.
> xen-br0: port 2(peth0) entering learning state
> xen-br0: topology change detected, propagating
> xen-br0: port 2(peth0) entering forwarding state
> device vif74.1 entered promiscuous mode
> xen-br0: port 3(vif74.1) entering learning state
> xen-br0: topology change detected, propagating
> xen-br0: port 3(vif74.1) entering forwarding state
> device vif75.1 entered promiscuous mode
> xen-br0: port 4(vif75.1) entering learning state
> xen-br0: topology change detected, propagating
> xen-br0: port 4(vif75.1) entering forwarding state
> xen-br0: port 4(vif75.1) entering disabled state
> device vif75.1 left promiscuous mode
> xen-br0: port 4(vif75.1) entering disabled state
> device vif76.1 entered promiscuous mode
> xen-br0: port 4(vif76.1) entering learning state
> xen-br0: topology change detected, propagating
> xen-br0: port 4(vif76.1) entering forwarding state
> device vif77.1 entered promiscuous mode
> xen-br0: port 5(vif77.1) entering learning state
> xen-br0: topology change detected, propagating
> xen-br0: port 5(vif77.1) entering forwarding state
> x335b:~ #
>
> The last output from 'xm-test' is:
>
> x335b:/tmp/logs/xm-test # tail x335sles9_pae4gb.output
> Using config file "/dev/null".
> Started domain testdomain
> [dom0] Running `xm destroy testdomain'
>
> [dom0] Running `xm create /dev/null ramdisk=../../ramdisk/initrd.img
> kernel=/boot/vmlinuz-2.6.12-xenU name=testdomain nics=0 vcpus=1
> memory=64 root=/dev/ram0'
> Using config file "/dev/null".
> Started domain testdomain
> [dom0] Running `xm destroy testdomain'
>
> PASS: 10_create_fastdestroy.test
> x335b:/tmp/logs/xm-test #
>
>
> On Wed, 2005-09-28 at 15:24 -0500, David F Barrera wrote:
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=265
> >
> > While running xm-test on two IBM xSeries 335s, one FC4 and the other one
> > SLES 9, I noticed that time has stopped:
> >
> > [root@x335a xm-test]# date
> > Wed Sep 28 13:59:18 CDT 2005
> > [root@x335a xm-test]# date
> > Wed Sep 28 13:59:18 CDT 2005
> >
> > >> 15 minutes later,
> > [root@x335a xm-test]# date
> > Wed Sep 28 13:59:18 CDT 2005
> > [root@x335a xm-test]#
> >
> > changeset: 7076:46046d5fb354
> > tag: tip
> > user: emellor@ewan
> > date: Tue Sep 27 16:09:46 2005 +0100
> > summary: Remove unused import, mark unused variables.
> >
> > The last output lines produced by xm-test are:
> > cp 06_destroy_dom0_neg.py 06_destroy_dom0_neg.test
> > chmod +x 06_destroy_dom0_neg.test
> >
> > The machines in question are running xm-test at the moment and appear
> > 'stuck'.
> > Both are displaying the "(XEN) Ouch! We are seriously BEHIND schedule!"
> > messages. However, the static time issue may not be related to the Ouch!
> > issue, bug # 257, as Paul Larson observed it on a machine that was not
> > running xm-test at the time, hence we are submitting it as a different
> > bug.
> >
> >
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2005-10-14 17:51 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-13 17:29 Time stopped Ian Pratt
2005-10-13 19:06 ` David F Barrera
2005-10-13 19:21 ` Dan Smith
-- strict thread matches above, loose matches on Subject: below --
2005-10-14 17:51 Stephan Böni
2005-10-14 17:37 Ian Pratt
2005-10-14 16:37 Stephan Böni
2005-10-14 16:47 ` David F Barrera
2005-10-14 15:44 Stephan Böni
2005-10-14 15:23 Stephan Böni
2005-10-14 14:48 Stephan Böni
2005-10-14 15:01 ` David F Barrera
2005-10-14 15:12 ` Ted Kaczmarek
2005-10-14 16:46 ` Steven Hand
2005-10-13 19:21 Ian Pratt
2005-10-14 14:34 ` David F Barrera
2005-09-28 20:24 David F Barrera
2005-10-13 15:17 ` David F Barrera
2005-10-13 15:36 ` David F Barrera
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.