I figured out how to do a kernel bisection manually, and isolated the first bad commit to this one:
ab1304b986468e3ef698ec4e1cb1a3d4ba080811 is the first bad commit
commit ab1304b986468e3ef698ec4e1cb1a3d4ba080811
Author: Marcel Holtmann <email address hidden>
Date: Mon Aug 11 22:11:35 2014 +0200
iwlwifi: Remove module build requirement for Intel Wireless WiFi
The CONFIG_IWLDVM and CONFIG_IWLMVM currently have a
"depends on m" as its requirement forcing it to be build
as module. This is not needed and thus just remove it.
:040000 040000 ca6d0eb787ca471c6e6267bf86863acb9bcd638b 6fda9a82d01a59a4edeaee8d1fbeb2cce28eeecc M drivers
The thing is, however, that after resetting to Ubuntu 3.19.0-13.13, and then reverting this commit (which had merge issues, but I believe I resolved them correctly) I still get the same result. I suppose I can conclude one of two things from this - either there is another independent commit which also causes this problem and occurs after the one above, or I did the merge incorrectly.
Let me know if there is more I can do to help resolve this.
I figured out how to do a kernel bisection manually, and isolated the first bad commit to this one:
ab1304b986468e3 ef698ec4e1cb1a3 d4ba080811 is the first bad commit ef698ec4e1cb1a3 d4ba080811
commit ab1304b986468e3
Author: Marcel Holtmann <email address hidden>
Date: Mon Aug 11 22:11:35 2014 +0200
iwlwifi: Remove module build requirement for Intel Wireless WiFi
The CONFIG_IWLDVM and CONFIG_IWLMVM currently have a
"depends on m" as its requirement forcing it to be build
as module. This is not needed and thus just remove it.
Fixes: ae7486a2b734 ("iwlwifi: fix Kconfig issues")
Signed-off-by: Marcel Holtmann <email address hidden>
[Squashed 2 commites for MVM and DVM]
Signed-off-by: Emmanuel Grumbach <email address hidden>
:040000 040000 ca6d0eb787ca471 c6e6267bf86863a cb9bcd638b 6fda9a82d01a59a 4edeaee8d1fbeb2 cce28eeecc M drivers
The thing is, however, that after resetting to Ubuntu 3.19.0-13.13, and then reverting this commit (which had merge issues, but I believe I resolved them correctly) I still get the same result. I suppose I can conclude one of two things from this - either there is another independent commit which also causes this problem and occurs after the one above, or I did the merge incorrectly.
Let me know if there is more I can do to help resolve this.