> generally it takes 3 or 4 cycles to trigger the bug. Kernel 3.4.3 works fine. > There are no messages in the logs. Any idea what might cause this or how I > can debug it any further? I will supply more details on my setup if needed. > Please CC me in your reply as I am not subscribed to the list.
If 3.4.3 works and 3.5 fails then that is a big help as it narrows the possible range of causes down quite a bit. Hardware info would be helpful here but I suspect it may be a case of doing a set of test builds to identify the offending patch. Also anything in the log might be helpful including doing the runs with drm.debug=255 in the kernel command line to get full traces Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
