On Mon, Apr 23, 2012 at 09:03:45PM -0400, Nick Bowler wrote:
On 2012-04-22 22:45 -0400, Konrad Rzeszutek Wilk wrote:
On Sun, Apr 22, 2012 at 08:05:54PM -0400, Nick Bowler wrote:
Following up on the above, the commit which introduces the panics during boot is this one:
commit 8e7e70522d760c4ccd4cd370ebfa0ba69e006c6e Author: Jerome Glisse jglisse@redhat.com Date: Wed Nov 9 17:15:26 2011 -0500
drm/ttm: isolate dma data from ttm_tt V4I think
dea7e0a ttm: fix agp since ttm tt rework
fixed that.
Yes, I just tested this commit and the one immediately before it. The one before crashes in the usual way, and dea7e0a boots (with the VGA output black as in the original report). So this fixed the crash.
Now, returning to the original bisection, I marked that commit as "bad" and dropped all the earlier "skip" markings. Git asks me to test commit 2a44e4997c5f ("drm/nouveau/disp: introduce proper init/fini, separate from create/destroy"). I cherry picked the aforementioned ttm fix:
git cherry-pick -n dea7e0a
which succeeded. Howevew, the resulting kernel still crashes early, although now in a different way. I just can't win :(
Perhaps there is a better way. You could do this:
git log --oneline -r v3.2..v3.3 drivers/gpu/drm/nouveau
to get an idea of the set of patches that went in. And use that, so
git bisect start -- drivers/gpu/drm/nouveau [this should only do the bisection on those patches]
git bisect good v3.2 git bisect bad v3.3
And keep in mind the dea7e0a might need to be stuck on some of these.
This _should_ limit the bisection to just the nouveau changes, I hope.