From: Brad Campbell <lists2009@fnarfbargle.com>
To: Saso Slavicic <saso.linux@astim.si>,
'Paolo Bonzini' <pbonzini@redhat.com>,
kvm@vger.kernel.org
Subject: Re: XP machine freeze
Date: Tue, 31 Mar 2015 15:18:26 +0800 [thread overview]
Message-ID: <551A4A42.10309@fnarfbargle.com> (raw)
In-Reply-To: <004f01d06b7c$08b96970$1a2c3c50$@astim.si>
On 31/03/15 14:29, Saso Slavicic wrote:
>> From: Brad Campbell
>> Sent: Tuesday, March 31, 2015 2:28 AM
>>
>>
>> If someone could give me some hard tests to do along the lines of what
>> Saso is up to I could probably get that done faster. With the right
>> bad kernel I can reproduce this lockup in a matter of hours.
> Hi,
>
> My machine usually (but not always) locks during backup. At around 3AM, a
> samba machine (a kvm machine on the same server actually) cifs mounts C$ and
> starts copying files off of it. The last stacktrace also shows network code.
> Is your machine actively working over network (sharing files)?
>
Better than that, it's recording h264 rtsp streams from 3 CCTV cameras,
so there is a constant network load of about 1.5-2MB/s (bytes not bits).
Come to think of it, out of the 3 XP VM's I have that are an identical
config and actually come from the same qcow2 base image this is the one
that hits the network hard. The other 2 hardly touch the network.
virtio network interface. I can get it to lock up in hours with the
right kernel, and repeat lockups after unlocking it with virt-viewer are
usually less than an hour at most.
My issue is my first bisect proved to be inconclusive, and the second
one is about 3 steps from done, but there are no kvm commits in the
current set under investigation.
I *know* that 3.15.6 was good as I ran that kernel for months, it all
started when I upgraded to a 3.18 and I think I've narrowed it down, but
like I said the bisects are just not falling out as plausible, and at 5
days for a good and up to 24 hours for a bad it's slow going.
I'll finish this bisect and then have a crack at the good/bad range
suggested by Paolo. The issue is being a production box I have to
schedule the re-boots.
I'm just not sure bisection is the right answer to tracking this down. I
just don't have the background to know what to poke to try and debug
this any other way.
Regards,
Brad
--
Dolphins are so intelligent that within a few weeks they can
train Americans to stand at the edge of the pool and throw them
fish.
next prev parent reply other threads:[~2015-03-31 7:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 15:10 XP machine freeze Saso Slavicic
2015-03-19 0:51 ` Marcelo Tosatti
2015-03-30 16:19 ` Saso Slavicic
2015-03-22 15:31 ` Brad Campbell
2015-03-30 21:11 ` Paolo Bonzini
2015-03-31 0:27 ` Brad Campbell
2015-03-31 6:29 ` Saso Slavicic
2015-03-31 7:18 ` Brad Campbell [this message]
2015-03-31 8:56 ` Paolo Bonzini
2015-03-31 11:16 ` Brad Campbell
2015-03-31 11:23 ` Paolo Bonzini
2015-04-04 10:55 ` Brad Campbell
2015-04-13 4:07 ` Brad Campbell
2015-04-13 12:38 ` Paolo Bonzini
2015-04-13 12:45 ` Brad Campbell
2015-04-13 14:02 ` Paolo Bonzini
2015-04-13 14:25 ` Brad Campbell
2015-04-19 15:27 ` Brad Campbell
2015-04-19 15:48 ` Nadav Amit
2015-04-19 16:50 ` Brad Campbell
2015-04-19 17:16 ` Paolo Bonzini
2015-04-13 12:47 ` Saso Slavicic
2015-04-13 13:33 ` Radim Krčmář
2015-04-13 13:34 ` Nadav Amit
2015-04-13 14:01 ` Paolo Bonzini
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=551A4A42.10309@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=saso.linux@astim.si \
/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