Comment # 10
on bug 92858
from Christian König
That looks promising. Here are a few hints how to proceed. > git bisect good c11d716218910c3aa2bac1bb641e6086ad649555 First of all you don't need to always specify the commit, git knows that by itself. E.g. "git bisect good" without the commit hash should be sufficient. (In reply to Darren D. from comment #9) > git bisect bad c5fd936e992dd2829167d2adc63e151675ca6898 > > The kernel I build after I tell git bisect the above revision is bad freezes > on "loading initial ramdisk." That's unfortunate but happens sometimes. Since c5fd936e992dd2829167d2adc63e151675ca6898 is bad the problem must be somewhere between v4.1 and c5fd936e992dd2829167d2adc63e151675ca6898. Since it is a radeon driver problem I suggest you limit bisect to only test the changes made to radeon. Please try the command "git bisect start c5fd936e992dd2829167d2adc63e151675ca6898 v4.1 drivers/gpu/drm/radeon/". If that still doesn't work try "git bisect skip" if you have a commit that won't work at all. If that also doesn't work just go on with "git bisect good/bad" and try to figure out when the issue with the ramdisk started.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
