Mailinglist Archive: radeonhd (265 mails)
| < Previous | Next > |
[radeonhd] [Bug 13853] radeonhd: occasional blackouts
- From: bugzilla-daemon@xxxxxxxxxxxxxxx
- Date: Tue, 15 Jan 2008 14:25:04 -0800 (PST)
- Message-id: <20080115222505.14105130052@xxxxxxxxxxxxxxxxxxxxxxxx>
http://bugs.freedesktop.org/show_bug.cgi?id=13853
--- Comment #18 from Aljaž Prusnik <prusnik@xxxxxxxxx> 2008-01-15 14:25:04 PST
---
I think I may have found the problematic one. I'm currently using commit
1c07fbe6284f90c9b8967d680a2d558e6785d428 and it went without blackouts now for
more than two days.
The next commit (90247017...) already produced blackouts. I still do not know
what triggers them so I'm not sure what to do to reproduce. But maybe if it
helps, I can describe once again what happened and what I did when a blackout
occured.
The screen goes black on a random occasion and in none of the occasions was I
using one and the same application where it happened. After the blackout I
tried switching the terminal to vt1 with CTRL-ALT-1 and then back to vt7 which
resulted in keyboard producing all this weird characters so I could not issue
any command and neither switch back to vt1. I could do connect remotely and
restart gdm.
Another time I decided to log off users remotely before restarting gdm
(remotely). And when I pkilled a user, the vt7 was back in action (i presume it
restarts during log-offs).
I could also do both things locally if I stayed on vt1 and not switch back
right away to vt7.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
_______________________________________________
xorg-team mailing list
xorg-team@xxxxxxxxxxx
http://lists.x.org/mailman/listinfo/xorg-team
--- Comment #18 from Aljaž Prusnik <prusnik@xxxxxxxxx> 2008-01-15 14:25:04 PST
---
I think I may have found the problematic one. I'm currently using commit
1c07fbe6284f90c9b8967d680a2d558e6785d428 and it went without blackouts now for
more than two days.
The next commit (90247017...) already produced blackouts. I still do not know
what triggers them so I'm not sure what to do to reproduce. But maybe if it
helps, I can describe once again what happened and what I did when a blackout
occured.
The screen goes black on a random occasion and in none of the occasions was I
using one and the same application where it happened. After the blackout I
tried switching the terminal to vt1 with CTRL-ALT-1 and then back to vt7 which
resulted in keyboard producing all this weird characters so I could not issue
any command and neither switch back to vt1. I could do connect remotely and
restart gdm.
Another time I decided to log off users remotely before restarting gdm
(remotely). And when I pkilled a user, the vt7 was back in action (i presume it
restarts during log-offs).
I could also do both things locally if I stayed on vt1 and not switch back
right away to vt7.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
_______________________________________________
xorg-team mailing list
xorg-team@xxxxxxxxxxx
http://lists.x.org/mailman/listinfo/xorg-team
| < Previous | Next > |