Re: Machine crashes right *after* ~successful resume
From: Bjorn Helgaas
Date: Wed Oct 15 2014 - 09:58:45 EST
[+cc Yinghai, author of 928bea964827 ("PCI: Delay enabling bridges
until they're needed")]
On Wed, Oct 15, 2014 at 5:16 AM, Wilmer van der Gaast <wilmer@xxxxxxxxx> wrote:
> Hello Rafael,
>
> Rafael J. Wysocki (rjw@xxxxxxxxxxxxx) wrote:
>> > Would it be feasible to revert 2e8b... to see if it fixes it on 3.17?
>> That's a merge, isn't it?
>>
> Correct, it was, and I did try to figure out which of its parents was
> the guilty one, but then I found out the real problem is
> 928bea964827d7824b548c1f8e06eccbbc4d0d7d.
>
> Not sure why 2e8b... was initially found guilty by git bisect, I fear
> that my testing was not thorough enough. I've verified a couple of times
> now that 928bea96... does cause crashes and the previous revision does not.
>
> 928bea... seems to reshuffle PCI initialisation a little bit and has
> caused more troubles, judging from a Google query for it. Some changes
> were made already as a result, and this unfortunately makes a revert on
> a later kernel tree (to see if that fixes the problem for me) much less
> straight-forward. :-(
More details (from initial post) here: http://roy.gaast.net/~wilmer/.lkml/
Can you open a report at http://bugzilla.kernel.org, please? Please
also attach the complete "lspci -vv" output.
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/