From: Johannes Stezenbach <js@sig21.net>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-3.2.1 + KVM: TSC unstable on Core i5-2400S / H67
Date: Thu, 26 Jan 2012 16:35:13 +0100 [thread overview]
Message-ID: <20120126153513.GA2963@sig21.net> (raw)
In-Reply-To: <4F21668F.8080005@siemens.com>
On Thu, Jan 26, 2012 at 03:43:27PM +0100, Jan Kiszka wrote:
> On 2012-01-26 10:46, Johannes Stezenbach wrote:
> > [16353.270435] Restarting tasks ...
> > [16353.270612] BUG: spinlock bad magic on CPU#2, dhclient3/2590
> > [16353.274702] lock: ffff880127b9ce08, .magic: 00000000, .owner: dhclient3/2590, .owner_cpu: 2
> > [16353.276594] Pid: 2590, comm: dhclient3 Not tainted 3.2.1 #2
> > [16353.278294] done.
> > [16353.278314] video LNXVIDEO:00: Restoring backlight state
> > [16353.281627] Call Trace:
> > [16353.281633] [<ffffffff81552515>] spin_dump+0x8a/0x8f
> > [16353.281636] [<ffffffff81552540>] spin_bug+0x26/0x28
> > [16353.281639] [<ffffffff81285af8>] do_raw_spin_unlock+0x1e/0x83
> > [16353.281643] [<ffffffff8155912e>] _raw_spin_unlock_irq+0x28/0x5b
> > [16353.281647] [<ffffffff8105e427>] get_signal_to_deliver+0x546/0x57c
> > [16353.281651] [<ffffffff81001572>] do_signal+0x3e/0x62f
> > [16353.281654] [<ffffffff815595b8>] ? retint_restore_args+0x13/0x13
> > [16353.281657] [<ffffffff81280079>] ? copy_user_generic_string+0x19/0x40
> > [16353.281661] [<ffffffff81142e8c>] ? poll_select_copy_remaining+0xc5/0xe9
> > [16353.281664] [<ffffffff81001ba8>] do_notify_resume+0x2c/0x53
> > [16353.281666] [<ffffffff8128137e>] ? trace_hardirqs_on_thunk+0x3a/0x3f
> > [16353.281669] [<ffffffff8155a1d6>] int_signal+0x12/0x17
> > [16353.472289] tsc = fffffd60248a9f39 last_guest_tsc = 229a823d4b88
> > [ 0.006666] Marking TSC unstable due to KVM discovered backwards TSC
> > [16362.155512] Switching to clocksource hpet
> > [16363.617844] atl1c 0000:06:00.0: atl1c: eth0 NIC Link is Up<1000 Mbps Full Duplex>
> > [16363.618145] br0: port 1(eth0) entering forwarding state
> > [16363.618153] br0: port 1(eth0) entering forwarding state
>
> Are you suspending your host while a VM is running? There is mosto
Yes, that's what I'm doing.
> probably a long-pending bug in the KVM TSC check logic that declares
> that clocksource unstable after resume. I'm seeing this here for ages
> and complained about it from the beginning (but I never debugged it :-/).
Hm, OK. I hope someone has an idea how to fix it. I'm ready to test patches.
> Of course, this doesn't explain your corrupted spin lock. That might be
> a different issue.
Yes, most probably it is something different since I haven't seen this
before. However, I didn't use 3.2.1 long. Now I updated
to 3.2.2 and enabled a few more debug options. We'll see if it
triggers again.
Thanks
Johannes
next prev parent reply other threads:[~2012-01-26 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 11:36 linux-3.2.1 + KVM: TSC unstable on Core i5-2400S / H67 Johannes Stezenbach
2012-01-25 12:27 ` Marcelo Tosatti
2012-01-25 13:25 ` Johannes Stezenbach
2012-01-26 9:46 ` Johannes Stezenbach
2012-01-26 14:43 ` Jan Kiszka
2012-01-26 15:35 ` Johannes Stezenbach [this message]
2012-01-26 16:48 ` Marcelo Tosatti
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=20120126153513.GA2963@sig21.net \
--to=js@sig21.net \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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