From: Steve Freitas <sflist@ihonk.com>
To: Jan Beulich <JBeulich@suse.com>, pasik@iki.fi
Cc: Don Slutz <dslutz@verizon.com>, xen-devel@lists.xen.org
Subject: Re: Regression, host crash with 4.5rc1
Date: Mon, 17 Nov 2014 11:21:56 -0800 [thread overview]
Message-ID: <546A4AD4.3030002@ihonk.com> (raw)
In-Reply-To: <5461D15C02000078000464D7@mail.emea.novell.com>
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
next prev parent reply other threads:[~2014-11-17 19:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 21:46 Regression, host crash with 4.5rc1 Steve Freitas
2014-11-03 21:52 ` Steve Freitas
2014-11-04 14:01 ` Don Slutz
2014-11-04 8:20 ` Pasi Kärkkäinen
2014-11-04 10:15 ` Jan Beulich
2014-11-10 8:03 ` Steve Freitas
2014-11-10 8:51 ` Jan Beulich
2014-11-10 20:05 ` Steve Freitas
2014-11-11 8:05 ` Jan Beulich
2014-11-17 19:21 ` Steve Freitas [this message]
2014-11-18 7:54 ` Jan Beulich
2014-11-20 1:23 ` Steve Freitas
2014-11-20 7:59 ` Jan Beulich
2014-11-20 20:07 ` Steve Freitas
2014-11-21 8:42 ` Jan Beulich
2014-11-23 1:28 ` Steve Freitas
2014-11-24 8:45 ` Jan Beulich
2014-11-24 9:08 ` Steve Freitas
2014-11-24 9:15 ` Jan Beulich
2014-11-24 11:41 ` Jan Beulich
2014-11-24 22:17 ` Steve Freitas
2014-11-25 8:16 ` Jan Beulich
2014-11-25 9:38 ` Steve Freitas
2014-11-25 11:00 ` Jan Beulich
2014-11-27 5:29 ` Steve Freitas
2014-11-27 9:27 ` Jan Beulich
2014-11-28 8:24 ` Steve Freitas
2014-11-28 8:50 ` Jan Beulich
2014-11-28 9:44 ` Steve Freitas
2014-12-03 17:14 ` Dugger, Donald D
2015-02-27 17:25 ` Dugger, Donald D
2015-02-27 17:50 ` Brown, Len
2015-03-02 15:24 ` Jan Beulich
2015-03-09 0:45 ` Steve Freitas
2015-03-26 20:49 ` Brown, Len
2014-11-21 9:31 ` Jan Beulich
2014-11-04 18:35 ` Steve Freitas
2014-11-04 14:39 ` Don Slutz
2014-11-06 23:20 ` Steve Freitas
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=546A4AD4.3030002@ihonk.com \
--to=sflist@ihonk.com \
--cc=JBeulich@suse.com \
--cc=dslutz@verizon.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.