From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steve Freitas <sflist@ihonk.com>
Subject: Re: Regression, host crash with 4.5rc1
Date: Mon, 17 Nov 2014 11:21:56 -0800
Message-ID: <546A4AD4.3030002@ihonk.com>
References: <5457F79B.2020300@ihonk.com>
	<20141104082012.GY12451@reaktio.net>	<5458B55C0200007800044B33@mail.emea.novell.com>	<5460716A.7090905@ihonk.com>	<54608A8B0200007800045E58@mail.emea.novell.com>	<54611A86.4000200@ihonk.com>
	<5461D15C02000078000464D7@mail.emea.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <5461D15C02000078000464D7@mail.emea.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>, pasik@iki.fi
Cc: Don Slutz <dslutz@verizon.com>, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

Hi Jan,

On 11/11/2014 0:05, Jan Beulich wrote:
>
>>> And these
>>>
>>>       [  199.775209] pcieport 0000:00:03.0: AER: Multiple Corrected error
>> received: id=0018
>>>       [  199.775238] pcieport 0000:00:03.0: PCIe Bus Error:
>> severity=Corrected, type=Data Link Layer, id=0018(Transmitter ID)
>>>       [  199.775251] pcieport 0000:00:03.0:   device [8086:340a] error
>> status/mask=00001100/00002000
>>>       [  199.775255] pcieport 0000:00:03.0:    [ 8] RELAY_NUM Rollover
>>>       [  199.775258] pcieport 0000:00:03.0:    [12] Replay Timer Timeout
>>>
>>> hint at a problem in the system's design. 00:03.0 is the parent bridge
>>> of 02:00.0 (and from what I can tell that's the only device behind that
>>> bridge), and hence the above messages can only reasonably have
>>> their origin at the passed through VGA device.
>>

Okay, I did a bisection and was not able to correlate the above error 
message with the problem I'm seeing. Not saying it's not related, but I 
had plenty of successful test runs in the presence of that error.

Took me about a week (sometimes it takes as much as 6 hours to produce 
the error), but bisect narrowed it down to this commit:

http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=9a727a813e9b25003e433b3dc3fa47e621f9e238

What do you think?

Thanks!

Steve