From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Weekly KVM Test report, kernel 30d95f ... userspace fc94d1 ... Date: Thu, 27 Nov 2008 12:57:29 +0200 Message-ID: <492E7D19.2090107@redhat.com> References: <0463F45F3606F4428ED35AC8C709F92E0217A80A@pdsmsx502.ccr.corp.intel.com> <49298B6D.6030109@redhat.com> <0463F45F3606F4428ED35AC8C709F92E021C5919@pdsmsx502.ccr.corp.intel.com> <492D4447.4000306@redhat.com> <0463F45F3606F4428ED35AC8C709F92E021C64AA@pdsmsx502.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "'kvm@vger.kernel.org'" , Anthony Liguori To: "Xu, Jiajun" Return-path: Received: from mx2.redhat.com ([66.187.237.31]:34952 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756513AbYK0K5f (ORCPT ); Thu, 27 Nov 2008 05:57:35 -0500 In-Reply-To: <0463F45F3606F4428ED35AC8C709F92E021C64AA@pdsmsx502.ccr.corp.intel.com> Sender: kvm-owner@vger.kernel.org List-ID: Xu, Jiajun wrote: > On Wednesday, November 26, 2008 8:43 PM kvm-owner@vger.kernel.org wrote: > > >> Xu, Jiajun wrote: >> >>> The call trace messages in guest: >>> ################### >>> Kernel BUG at block/elevator.c:560 >>> invalid opcode: 0000 [1] SMP >>> last sysfs file: /block/hda/removable >>> >>> >> This suggests something happened to /dev/hda. Could be a timeout or >> something. Are there any messages in the log before the BUG? >> > > There are two parts call traces: > First, when I do live migration, on the original guest there are some call trace: > ################ > BUG: soft lockup detected on CPU#0! > > Call Trace: > [] softlockup_tick+0xd5/0xe7 > [] update_process_times+0x42/0x68 > [] smp_local_timer_interrupt+0x23/0x47 > [] smp_apic_timer_interrupt+0x41/0x47 > [] apic_timer_interrupt+0x66/0x6c > [] ide_outb+0x0/0x9 > [] __do_softirq+0x53/0xd5 > [] call_softirq+0x1c/0x28 > [] do_softirq+0x2c/0x85 > [] apic_timer_interrupt+0x66/0x6c > [] ide_outb+0x0/0x9 > [] ide_outb+0x8/0x9 > [] ide_do_request+0x408/0x787 > [] elv_insert+0xd6/0x1f7 > [] ide_do_drive_cmd+0xc8/0x11e > [] ide_outsw+0x0/0x9 > [] :ide_cd:cdrom_queue_packet_command+0x46/0xe2 > [] ide_outsw+0x8/0x9 > [] ide_init_drive_cmd+0x10/0x24 > [] :ide_cd:cdrom_check_status+0x62/0x71 > [] blk_end_sync_rq+0x0/0x2e > [] :ide_cd:ide_cdrom_check_media_change_real+0x1c/0x37 > [] :cdrom:media_changed+0x44/0x74 > [] check_disk_change+0x1f/0x76 > [] :cdrom:cdrom_open+0x92c/0x979 > [] do_lookup+0x65/0x1c3 > [] dput+0x2c/0x114 > [] __link_path_walk+0xdf8/0xf42 > [] mntput_no_expire+0x19/0x89 > [] link_path_walk+0xd3/0xe5 > [] do_nanosleep+0x47/0x70 > [] kobject_get+0x12/0x17 > [] get_disk+0x3f/0x81 > [] exact_lock+0xc/0x14 > [] kobj_lookup+0x132/0x19b > [] :ide_cd:idecd_open+0x9f/0xd1 > [] do_open+0xa2/0x30f > [] may_open+0x58/0x21e > [] blkdev_open+0x0/0x4f > [] blkdev_open+0x23/0x4f > [] __dentry_open+0xd9/0x1dc > [] do_filp_open+0x2a/0x38 > [] do_nanosleep+0x47/0x70 > [] do_sys_open+0x44/0xbe > [] tracesys+0xd5/0xe0 > Anthony, could migration be starving qemu_mutex and thus the guest? -- error compiling committee.c: too many arguments to function