http://bugzilla.kernel.org/show_bug.cgi?id=12878
--- Comment #52 from Eddy Petrișor <eddy.petrisor+lin...@gmail.com> 2009-07-01 22:16:48 --- (In reply to comment #51) > Quite likely, none! Sorry, could you clear up to what were you answering here? Is it this part: "if he has any idea which part of the setup procedure could be responsible about this bug" ? > Unfortunately it could be such that slight differences in the handing of > especially graphics might trigger BIOS bugs, but that's like finding a needle > in a haystack. And aiui, I can't simply revert part some commits in the rewrite commits and expect things to work or even compile (e.g. revert 91a6c462b02~X and hope we can narrow down the issue). Is that correct or do I have a chance to be able to boot such a kernel? Note that the working kernels didn't resumed the graphics card properly and the screen was always blank after resume. > Now, the *current* code uses the new code for the resume path as well, but > that > is not the commit you fingered... By current I assume you mean linux-2.6 master, right? I could try to see if it was fixed by any chance. The last time I tried to compile, it was right after 2.6.30 release and that kernel didn't boot for me (but it might have been incorrect configuration). -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. ------------------------------------------------------------------------------ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
