[Bug 39145] screen goes dark when the graphics driver (radeon) is loaded

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Aug 5 10:19:11 PDT 2011


--- Comment #2 from Jonathan Nieder <jrnieder at gmail.com> 2011-08-05 10:19:10 PDT ---
Hi Mikhail,

(In reply to comment #0)

> This issue ocurred when I updated kernel version 2.6.38-2-686-pae to
> 2.6.39-2-686-pae version.
> - The GPU's device ID: 1002:9712 (M880G, Mobility Radeon HD 4200)
> - The model name: Acer Aspire One 521
> - I am using Debian testing (wheezy) x86 
> - Also system couldn't enter in single mode, because screen goes dark again.
> I attach link to youtube video that's demonstrates symptoms of this issue.
> http://www.youtube.com/watch?v=KtxRLEtHu5w
> Messages log attached to this report.

Thanks.  If you have time, could you bisect to find the change that introduced
this bug?

It works like this:

0. Write a script named "as" with the following content and put it in
your $PATH to work around <http://bugs.debian.org/620448>.

    exec /usr/bin/as --size-check=warning "$@"

1. Grab the latest mainline source:

 # apt-get install git build-essential
 $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
 $ cd linux

2. Minimal configuration.

 $ make localmodconfig

3. Test.

 $ make deb-pkg
 # dpkg -i ../<name of .deb>
 # reboot

4. If it works, let us know and declare victory. Otherwise:

 $ git bisect start v2.6.39 v2.6.38 -- drivers/gpu

Git will check out a version half-way between to test.

 $ make silentoldconfig; # reuse configuration
 $ make deb-pkg
 # dpkg -i ../<name of .deb>
 # reboot
 $ cd ~/src/linux
 $ git bisect good; # if it works
 $ git bisect bad; # if it fails in the same way
 $ git bisect skip; # if some other bug makes it hard to test

5. Git will check out a next version to check; repeat step 4 until
it gives the "first bad commit" or you get bored.  If you finish
early, you can send the output of "git bisect log" to let us know
the information acquired so far.

If gitk is installed, at any step you can run "git bisect visualize"
to see the regression range narrowing.

Hope that helps.

Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the dri-devel mailing list