xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* on starting HVM-domU whole system freezes with "soft lockup - CPU X stuck for XXs! [qemu-dm:...]"
@ 2011-04-13  7:30 MadLoisae
  2011-04-14 13:09 ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 3+ messages in thread
From: MadLoisae @ 2011-04-13  7:30 UTC (permalink / raw)
  To: xen-devel

[-- Attachment #1: Type: text/plain, Size: 5420 bytes --]

Hi xen-devel,

----
I already posted this on xen-users - Todd Deshane asked me to post this 
here for feedback.
He also asked if I can test xen 4.1 - I am looking if I can find and 
install backports but if not I'm afraid I think I'm not able to 
compiling on myself.
----

I am trying since a few days my first steps with xen.
Hardware: Core2 T7200, Intel 945GME, 2GB RAM
Software: debian squeeze, i686, with debian delivered xen 4.0.1
CPU and BIOS support hardware virtualisation: (XEN) HVM: VMX enabled

I can successfully boot with xen my dom0 with squeeze-delivered i686 kernel.
As soon as I start a HVM (paravirtualisation works without problems) my 
dom0 stucks immediately.
I can see about 10 seconds after starting domU "nothing", then the first 
messages like "hrtimer: interrupt took 1739955444 ns" messages appear, 
then my disk gets timeouts. then kernel panics like below are starting - 
normally they are not written to messages-log, one time i had "luck":

kernel: : [ 4815.144473] saa7146 (0) vpeirq: used 3 times >80% of buffer 
(1049604 bytes now)
kernel: : [ 4815.144473] Modules linked in: tun xt_physdev loop 
ipt_REJECT ip6table_filter ip6_tables ebtable_nat ebtables bridge stp 
xen_evtchn xenfs nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs 
xt_recent ipt_MASQUERADE xt_tcpudp xt_state iptable_nat nf_nat 
nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables 
x_tables fuse ext4 jbd2 crc16 it87 hwmon_vid coretemp tda10021 
snd_hda_codec_via budget_av snd_hda_intel snd_hda_codec saa7146_vv 
snd_hwdep videodev v4l1_compat snd_pcm_oss snd_mixer_oss videobuf_dma_sg 
videobuf_core snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event 
snd_seq budget_core i915 drm_kms_helper dvb_core snd_timer saa7146 
snd_seq_device ttpci_eeprom drm rng_core pcspkr evdev i2c_i801 
i2c_algo_bit snd i2c_core soundcore video output button snd_page_alloc 
processor acpi_processor ext3 jbd mbcache dm_mod sd_mod crc_t10dif 
ata_generic uhci_hcd ata_piix fan ehci_hcd libata scsi_mod e1000e 
usbcore nls_base thermal thermal_sys [last unloaded: scsi_wait_scan]
kernel: : [ 4815.144473]
kernel: : [ 4815.324579] saa7146 (0) saa7146_i2c_writeout [irq]: timed 
out waiting for end of xfer
kernel: : [ 4815.324722] ata1: lost interrupt (Status 0x50)
kernel: : [ 4815.324772] sd 0:0:0:0: [sda] Unhandled error code
kernel: : [ 4815.324775] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
kernel: : [ 4815.324780] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 00 d3 
41 9f 00 00 28 00
kernel: : [ 4815.324806] lost page write due to I/O error on sda1
kernel: : [ 4815.324817] lost page write due to I/O error on sda1
kernel: : [ 4815.324826] lost page write due to I/O error on sda1
kernel: : [ 4815.324834] lost page write due to I/O error on sda1
kernel: : [ 4815.324843] lost page write due to I/O error on sda1
kernel: : [ 4815.450483] Pid: 1337, comm: qemu-dm Not tainted 
(2.6.32-5-xen-686 #1) 945GM/E-ITE8712
kernel: : [ 4815.450483] EIP: 0061:[<c1002227>] EFLAGS: 00200246 CPU: 0
kernel: : [ 4815.450483] EIP is at hypercall_page+0x227/0x1001
kernel: : [ 4815.450483] EAX: 00040000 EBX: 00000000 ECX: 00000000 EDX: 
c357a7b4
kernel: : [ 4815.450483] ESI: 00000009 EDI: 00000028 EBP: c13959e4 ESP: 
ddb6defc
kernel: : [ 4815.450483]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069
kernel: : [ 4815.450483] CR0: 8005003b CR2: 0807f9d0 CR3: 1da42000 CR4: 
00002660
kernel: : [ 4815.450483] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 
00000000
kernel: : [ 4815.450483] DR6: ffff0ff0 DR7: 00000400
kernel: : [ 4815.450483] Call Trace:
kernel: : [ 4815.450483]  [<c1006048>] ? xen_force_evtchn_callback+0xc/0x10
kernel: : [ 4815.450483]  [<c1006778>] ? check_events+0x8/0xc
kernel: : [ 4815.450483]  [<c1006737>] ? xen_irq_enable_direct_end+0x0/0x1
kernel: : [ 4815.450483]  [<c103c80b>] ? __do_softirq+0x4b/0x156
kernel: : [ 4815.450483]  [<c103c947>] ? do_softirq+0x31/0x3c
kernel: : [ 4815.450483]  [<c103ca21>] ? irq_exit+0x26/0x58
kernel: : [ 4815.450483]  [<c1199a16>] ? xen_evtchn_do_upcall+0x22/0x2c
kernel: : [ 4815.653736]  [<c1009b5f>] ? xen_do_upcall+0x7/0xc
kernel: : [ 4815.653736]  [<c104a74c>] ? sys_clock_gettime+0x46/0x7e
kernel: : [ 4815.653736]  [<c1008f9c>] ? syscall_call+0x7/0xb
kernel: : [ 4815.676006] saa7146 (0) vpeirq: used 1 times >80% of buffer 
(1300396 bytes now)

on monitor I can see frequently messages which look like:
soft lockup - CPU X stuck for XXs! [qemu-dm:...]
always i saw qemu-dm is listed with PID in this message. these messages 
I can never find in messages-log, i think the machine is too dead to 
write them down onto disc.

the only way to get the machine back is to be fast enough after starting 
(means less than about 10 seconds) do a xm destroy <name>. otherwise the 
system needs to be powercycled, rarely ctrl-alt-delete on console 
initiates a reboot, most time this also does not work.

can anybody tell me where I can search for the issue?
currently I tried to change architecture to amd64, but as it is not only 
the kernel and xen itself this is not a "fast try", so hopefully 
somebody can help me here.
attached: xm dmesg (from i686)
in there I've limited memory of dom0 to 1GB because I tought maybe 
balooning causes the issue. my HVM machines never had more than 512MB 
configured RAM, but nevertheless the problem also occurs with 128 or 
256MB configured.

thank you for your investigations.

best regards
Alois



[-- Attachment #2: xm_dmesg --]
[-- Type: text/plain, Size: 3473 bytes --]

(XEN) Xen version 4.0.1 (Debian 4.0.1-2) (waldi@debian.org) (gcc version 4.4.5 (Debian 4.4.5-10) ) Wed Jan 12 15:04:50 UTC 2011
(XEN) Bootloader: GRUB 1.98+20100804-14
(XEN) Command line: placeholder cpufreq=xen cpuidle dom0_mem=1024M
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 2 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009f000 (usable)
(XEN)  000000000009f000 - 00000000000a0000 (reserved)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000007f690000 (usable)
(XEN)  000000007f690000 - 000000007f6e0000 (reserved)
(XEN)  000000007f6e0000 - 000000007f6e3000 (ACPI NVS)
(XEN)  000000007f6e3000 - 000000007f6f0000 (ACPI data)
(XEN)  000000007f6f0000 - 000000007f700000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 0000000100000000 (reserved)
(XEN) System RAM: 2038MB (2087100kB)
(XEN) ACPI: RSDP 000F7C90, 0014 (r0 IntelR)
(XEN) ACPI: RSDT 7F6E3000, 0038 (r1 IntelR AWRDACPI 42302E31 AWRD        0)
(XEN) ACPI: FACP 7F6E3080, 0074 (r1 IntelR AWRDACPI 42302E31 AWRD        0)
(XEN) ACPI: DSDT 7F6E3100, 5122 (r1 INTELR AWRDACPI     1000 MSFT  3000000)
(XEN) ACPI: FACS 7F6E0000, 0040
(XEN) ACPI: IDTS 7F6E82C0, 0028 (r1 IntelR AWRDACPI 42302E31 AWRD        0)
(XEN) ACPI: MCFG 7F6E8300, 003C (r1 IntelR AWRDACPI 42302E31 AWRD        0)
(XEN) ACPI: APIC 7F6E8240, 0068 (r1 IntelR AWRDACPI 42302E31 AWRD        0)
(XEN) ACPI: SSDT 7F6E89A0, 0482 (r1  PmRef    CpuPm     3000 INTL 20050930)
(XEN) Xen heap: 8MB (8852kB)
(XEN) Domain heap initialised
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #1 6:15 APIC version 20
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 1995.074 MHz processor.
(XEN) VMX: Supported advanced features:
(XEN)  - MSR direct-access bitmap
(XEN) HVM: ASIDs disabled.
(XEN) HVM: VMX enabled
(XEN) I/O virtualisation disabled
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer
(XEN) Allocated console ring of 16 KiB.
(XEN) Brought up 2 CPUs
(XEN) HPET broadcast init failed, turn to PIT broadcast.
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 32-bit, PAE, lsb
(XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0x1000000 -> 0x1651000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000038000000->000000003c000000 (245760 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c1000000->c1651000
(XEN)  Init. ramdisk: c1651000->c2c50c00
(XEN)  Phys-Mach map: c2c51000->c2d51000
(XEN)  Start info:    c2d51000->c2d5147c
(XEN)  Page tables:   c2d52000->c2d6f000
(XEN)  Boot stack:    c2d6f000->c2d70000
(XEN)  TOTAL:         c0000000->c3000000
(XEN)  ENTRY ADDRESS: c13ff000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Scrubbing Free RAM: .........done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 152kB init memory.



[-- 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] 3+ messages in thread

end of thread, other threads:[~2011-04-14 16:29 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-04-13  7:30 on starting HVM-domU whole system freezes with "soft lockup - CPU X stuck for XXs! [qemu-dm:...]" MadLoisae
2011-04-14 13:09 ` Konrad Rzeszutek Wilk
2011-04-14 16:29   ` MadLoisae

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).