From: Avi Kivity <avi@redhat.com>
To: "Xu, Jiajun" <jiajun.xu@intel.com>
Cc: "'kvm@vger.kernel.org'" <kvm@vger.kernel.org>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: Weekly KVM Test report, kernel 30d95f ... userspace fc94d1 ...
Date: Thu, 27 Nov 2008 12:57:29 +0200 [thread overview]
Message-ID: <492E7D19.2090107@redhat.com> (raw)
In-Reply-To: <0463F45F3606F4428ED35AC8C709F92E021C64AA@pdsmsx502.ccr.corp.intel.com>
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:
> <IRQ> [<ffffffff800b50fa>] softlockup_tick+0xd5/0xe7
> [<ffffffff800930e2>] update_process_times+0x42/0x68
> [<ffffffff800746e3>] smp_local_timer_interrupt+0x23/0x47
> [<ffffffff80074da5>] smp_apic_timer_interrupt+0x41/0x47
> [<ffffffff8005bc8e>] apic_timer_interrupt+0x66/0x6c
> [<ffffffff800076b2>] ide_outb+0x0/0x9
> [<ffffffff80011ca9>] __do_softirq+0x53/0xd5
> [<ffffffff8005c2fc>] call_softirq+0x1c/0x28
> [<ffffffff8006a53a>] do_softirq+0x2c/0x85
> [<ffffffff8005bc8e>] apic_timer_interrupt+0x66/0x6c
> <EOI> [<ffffffff800076b2>] ide_outb+0x0/0x9
> [<ffffffff800076ba>] ide_outb+0x8/0x9
> [<ffffffff8000eac7>] ide_do_request+0x408/0x787
> [<ffffffff80134f37>] elv_insert+0xd6/0x1f7
> [<ffffffff8003f5af>] ide_do_drive_cmd+0xc8/0x11e
> [<ffffffff8005857f>] ide_outsw+0x0/0x9
> [<ffffffff8811f198>] :ide_cd:cdrom_queue_packet_command+0x46/0xe2
> [<ffffffff80058587>] ide_outsw+0x8/0x9
> [<ffffffff801c127a>] ide_init_drive_cmd+0x10/0x24
> [<ffffffff8811f462>] :ide_cd:cdrom_check_status+0x62/0x71
> [<ffffffff801360b5>] blk_end_sync_rq+0x0/0x2e
> [<ffffffff8811f48d>] :ide_cd:ide_cdrom_check_media_change_real+0x1c/0x37
> [<ffffffff8810d076>] :cdrom:media_changed+0x44/0x74
> [<ffffffff800d9b83>] check_disk_change+0x1f/0x76
> [<ffffffff88111399>] :cdrom:cdrom_open+0x92c/0x979
> [<ffffffff8000c9c9>] do_lookup+0x65/0x1c3
> [<ffffffff8000cec4>] dput+0x2c/0x114
> [<ffffffff8000a2e0>] __link_path_walk+0xdf8/0xf42
> [<ffffffff8002c86b>] mntput_no_expire+0x19/0x89
> [<ffffffff8000e630>] link_path_walk+0xd3/0xe5
> [<ffffffff80061c7e>] do_nanosleep+0x47/0x70
> [<ffffffff800560a3>] kobject_get+0x12/0x17
> [<ffffffff80138bbd>] get_disk+0x3f/0x81
> [<ffffffff80058ef8>] exact_lock+0xc/0x14
> [<ffffffff801ad98f>] kobj_lookup+0x132/0x19b
> [<ffffffff8811fe4b>] :ide_cd:idecd_open+0x9f/0xd1
> [<ffffffff800da1bc>] do_open+0xa2/0x30f
> [<ffffffff80011d83>] may_open+0x58/0x21e
> [<ffffffff800da67d>] blkdev_open+0x0/0x4f
> [<ffffffff800da6a0>] blkdev_open+0x23/0x4f
> [<ffffffff8001e0f4>] __dentry_open+0xd9/0x1dc
> [<ffffffff800270dc>] do_filp_open+0x2a/0x38
> [<ffffffff80061c7e>] do_nanosleep+0x47/0x70
> [<ffffffff80019523>] do_sys_open+0x44/0xbe
> [<ffffffff8005b28d>] tracesys+0xd5/0xe0
>
Anthony, could migration be starving qemu_mutex and thus the guest?
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-11-27 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 15:59 Weekly KVM Test report, kernel 30d95f ... userspace fc94d1 Xu, Jiajun
2008-11-23 16:57 ` Avi Kivity
2008-11-25 5:52 ` Xu, Jiajun
2008-11-26 12:42 ` Avi Kivity
2008-11-27 8:31 ` Xu, Jiajun
2008-11-27 10:57 ` Avi Kivity [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=492E7D19.2090107@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jiajun.xu@intel.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox