I'm trying to construct a list of good and bad commits to use for starting a new bisection run. Please take note that it only takes a single occurrence of the evergreen_cp_resume oops to qualify a commit as bad, so there's no need to continue testing once you've seen that oops.
I do agree that the radeon_gart_unbind oops looks different, so that shouldn't be considered a failure for the purposes of the bisection. Here's the list I have now. Bad builds: 000 003 005 006 007 008 009 010 011 Good builds: 001 004 Inconclusive: 005 Martin, just to verify -- with each of the builds you've indicated have failed for you, you've verified that you're getting the evergreen_cp_resume oops? josejuan05, when you tested build 005, did you verify that you were getting an oops in evergreen_cp_resume? If so, we can move that one to the bad list. Once this is all sorted out I'll use the information to seed a new bisection and start providing more builds to test. Thanks everyone! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/727620/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
