Comment 39 for bug 1158689
Revision history for this message
|
|
#39 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
(a) Can we see a full boot log (e.g. output of dmesg) with a recent kernel? Ideally it would include the time that the visual issues happen.
(b) This looks like it could be a fencing issue, i.e. we try to draw to a texture, but then instead of waiting, we don't wait. There were some fixes that went into 3.13-rc1, so perhaps trying the latest and greatest (e.g. 3.13-rc3, or the latest Linus HEAD) would be good to test out.
(c) There are many bisection guides on the internet. You will also need to figure out how to make the compiled kernel play nice with your distribution. The basics are simple though:
1. git bisect start v3.7 v3.6 -- drivers/
2. build/install/
3. if it's good, "git bisect good", if it's bad, "git bisect bad"
4. goto 2
At some point running the step 3 command will tell you "first bad commit is xyz". That's when you're done. I suspect it might be the giant mega "rewrite nouveau" commit, in which case we're screwed and this will have been a huge time-waster (apologies in advance if it turns out this way). But it might be one of the many other commits that went into 3.7, which would be nice and indicate an area to focus on.