https://bugs.freedesktop.org/show_bug.cgi?id=27744 --- Comment #12 from willjcroz <willjcroz@xxxxxxxxxxx> 2010-07-30 10:23:57 PDT --- (In reply to comment #11) > As a rough indicator for now: 2.6.35 rc3 resumes (from ram suspend) OK Scrub that, rc3 does not resume (either some weird fluke or my mistake). I'm afraid I didn't get very far bisecting. Basically none of 2.6.34 (release) and 2.6.35-rc kernels resume. I'm assuming you are only interested in when the atombios errors appear. Sometime between 2.6.34 and 2.6.35-rc1 a bug was introduced preventing my kernel from booting until just before 2.6.35-rc3. >From my bisections all I can confirm is that the atombios errors started appearing in Linus' tree *sometime after* this commit: df16dd53c575d0cb9dbee20a3149927c862a9ff6 hwmon: (ltc4245) Read only one GPIO pin and *sometime* before this commit: 09bdf591f4724c7d0328d4d7b8808492addb5a28 drm/radeon/kms: fix dpms state on resume Alex, I am pretty much a 'newb' when it comes to git and the kernel in general and currently git is making my brain hurt severely. When I have the time I will read up more on git and try and work out an easy way to exclude unrelated commits that break my kernel and include bug fix commits that allow me to bisect this issue successfully. Any pointers to articles/howtos on dealing with this specific kind of issue with git? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- 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
