From: Matthias Graf <matthias.graf@st.ovgu.de>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, Tony Luck <tony.luck@intel.com>,
alexander.deucher@amd.com
Subject: Re: PROBLEM: Fatal Machine Check >= 3.13.5-101.fc19.x86_64
Date: Fri, 18 Apr 2014 11:17:34 +0200 [thread overview]
Message-ID: <5350EDAE.8020101@st.ovgu.de> (raw)
In-Reply-To: <20140417130207.GB4321@pd.tnic>
[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]
Fine-grained bisection result:
ab70b1dde73ff4525c3cd51090c233482c50f217 is the first bad commit
commit ab70b1dde73ff4525c3cd51090c233482c50f217
Author: Alex Deucher <alexander.deucher@amd.com>
Date: Fri Nov 1 15:16:02 2013 -0400
drm/radeon: enable DPM by default on r7xx asics
Seems to be stable on them.
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
:040000 040000 f3262029b868df4d882f64b4deba6b9230e307ea
1f1dfca42763703a56e3cc82bb103608a24be94e M drivers
Result is reasonable: I have a RV770 chip.
(Additional) Bug Report for Reference:
https://bugzilla.redhat.com/show_bug.cgi?id=1085785
Thanks for the instructions Borislav! At first, I was not completely
sure what you expected me to do (this is my first kernel bug report :)).
If there is anymore more I can help you with, let me know.
Kind regards
Matthias
Am 17.04.2014 15:02, schrieb Borislav Petkov:
> On Thu, Apr 17, 2014 at 08:25:58AM +0200, Matthias Graf wrote:
>> Ok. I tried:
>>
>> 3.15-rc1 (16. April)
>> failed.
>>
>> Bisecting turned out:
>> last working: 3.12.17
>> first failing: 3.13
>
> Ok, next steps would then be:
>
> * test stock 3.12.
> -> if it works, bisect between 3.12 and 3.13.
> -> if not, bisect between 3.12 and 3.12.17
>
> If all works out correctly, the bisection result will give us the patch
> which broke things on your machine and which is still unfixed upstream.
>
> Thanks.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 538 bytes --]
next prev parent reply other threads:[~2014-04-18 9:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 17:10 PROBLEM: Fatal Machine Check >= 3.13.5-101.fc19.x86_64 Matthias Graf
2014-03-21 17:27 ` Borislav Petkov
2014-03-21 19:49 ` Matthias Graf
2014-03-21 20:13 ` Borislav Petkov
2014-03-21 20:35 ` Matthias Graf
2014-03-21 20:37 ` Tony Luck
2014-03-24 17:22 ` Matthias Graf
2014-04-02 14:14 ` Matthias Graf
2014-04-16 14:22 ` Borislav Petkov
2014-04-17 6:25 ` Matthias Graf
2014-04-17 13:02 ` Borislav Petkov
2014-04-18 9:17 ` Matthias Graf [this message]
2014-04-18 9:45 ` Borislav Petkov
2014-04-18 11:45 ` Matthias Graf
2014-04-18 12:40 ` Borislav Petkov
2014-04-18 13:08 ` Deucher, Alexander
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=5350EDAE.8020101@st.ovgu.de \
--to=matthias.graf@st.ovgu.de \
--cc=alexander.deucher@amd.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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