Re: XP machine freeze

[Brad Campbell <lists2009@fnarfbargle.com>]

On 31/03/15 16:56, Paolo Bonzini wrote:
>
> On 31/03/2015 09:18, Brad Campbell wrote:
>> 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.
> Then it's not so weird that you have no KVM left in your bisect log.
>
> We can look at smaller suspicious parts of the repository, until we
> find the good one.  For example, after testing before/after the KVM
> merge, you could test before/after the net-next merge (that would be
> commit f4f142ed4ef835709c7e6d12eaca10d190bcebed presumed good, and
> commit ae045e2455429c418a418a3376301a9e5753a0a8 presumed bad).
>
> Paolo
>
Right, so now rather than being a pain on my production machine I know 
what to concentrate on with my staging machine to see if I can produce a 
pathological test case. Maybe an XP VM running iPerf. Easter is coming 
up, so I'll have some time to dedicate to the task.

If you look at the bisect point I'm currently at it's a mix of i2c and 
arm. The only vaguely relevant (as far as I can see) commit is the 
addition of the getrandom() syscall, so my bisect is looking dodgy at 
best. If I can come up with a better test case on a non-critical box 
then I'll be in a better position to try and help get to the bottom of 
the issue.

I can at least replicate the actual VM and conditions on similar 
hardware to try and reproduce it.

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.