10:04 p.m.
Hi,
Occasionally the screen gets disabled for no reason at all on my F11
system. This occurs even with the screensaver completely disabled and even
after I typed something 5 seconds before. The screen suddenly goes black
and as soon as I press a key it comes back to life again.
The only possible hint I found in the Xorg logfile is this though since
Xorg doesn't put timestamps in front of it's log entries I'm not 100% when
these entries where made and if they have anything to do with this:
Blank CRTC 0 success
Disable CRTC 0 success
Disable CRTC memreq 0 success
Enable CRTC memreq 0 success
Enable CRTC 0 success
Unblank CRTC 0 success
(II) RADEON(0): DIG0 transmitter: Coherent Mode enabled
Output DIG0 transmitter setup success
Anyone else seeing this?
Regards,
Dennis
10:35 p.m.
On Wed, 2009-07-29 at 05:04 +0200, Dennis J. wrote:
Hi,
Occasionally the screen gets disabled for no reason at all on my F11
system. This occurs even with the screensaver completely disabled and even
after I typed something 5 seconds before. The screen suddenly goes black
and as soon as I press a key it comes back to life again.
The only possible hint I found in the Xorg logfile is this though since
Xorg doesn't put timestamps in front of it's log entries I'm not 100% when
these entries where made and if they have anything to do with this:
Blank CRTC 0 success
Disable CRTC 0 success
Disable CRTC memreq 0 success
Enable CRTC memreq 0 success
Enable CRTC 0 success
Unblank CRTC 0 success
(II) RADEON(0): DIG0 transmitter: Coherent Mode enabled
Output DIG0 transmitter setup success
Anyone else seeing this?
Regards,
Dennis
Yes, I'm experiencing the same issue (on the integrated AMD/ATI 790GX
chip)- the screen goes blank even when I'm moving the mouse while web
browsing or writing an e-mail. It does not happen very often for me
though, so I didn't bother yet to try to find reproducible steps for a
bug report.
11:08 p.m.
On Tue, 2009-07-28 at 23:35 -0400, Dawid Zamirski wrote:
On Wed, 2009-07-29 at 05:04 +0200, Dennis J. wrote:
> Hi,
> Occasionally the screen gets disabled for no reason at all on my F11
> system. This occurs even with the screensaver completely disabled and even
> after I typed something 5 seconds before. The screen suddenly goes black
> and as soon as I press a key it comes back to life again.
>
> The only possible hint I found in the Xorg logfile is this though since
> Xorg doesn't put timestamps in front of it's log entries I'm not 100%
when
> these entries where made and if they have anything to do with this:
>
> Blank CRTC 0 success
> Disable CRTC 0 success
> Disable CRTC memreq 0 success
> Enable CRTC memreq 0 success
> Enable CRTC 0 success
> Unblank CRTC 0 success
> (II) RADEON(0): DIG0 transmitter: Coherent Mode enabled
> Output DIG0 transmitter setup success
>
> Anyone else seeing this?
>
> Regards,
> Dennis
>
Yes, I'm experiencing the same issue (on the integrated AMD/ATI 790GX
chip)- the screen goes blank even when I'm moving the mouse while web
browsing or writing an e-mail. It does not happen very often for me
though, so I didn't bother yet to try to find reproducible steps for a
bug report.
Literally dozens of people (actually, probably hundreds or thousands...)
are seeing this. The report is:
https://bugzilla.redhat.com/show_bug.cgi?id=501601
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
12:32 a.m.
On Tue, Jul 28, 2009 at 09:08:11PM -0700, Adam Williamson wrote:
> On Wed, 2009-07-29 at 05:04 +0200, Dennis J. wrote:
> > Occasionally the screen gets disabled for no reason at all on my F11
> > system. This occurs even with the screensaver completely disabled and even
> > after I typed something 5 seconds before.
It can go off while you are typing and it takes some seconds to come
back. Quite annoying.
> > Anyone else seeing this?
Literally dozens of people (actually, probably hundreds or thousands...)
are seeing this. The report is:
https://bugzilla.redhat.com/show_bug.cgi?id=501601
Here is an older one:
https://bugzilla.redhat.com/show_bug.cgi?id=243022
It got CLOSED WONTFIX.
Michal
1:43 a.m.
On Tue, 2009-07-28 at 23:32 -0600, Michal Jaegermann wrote:
On Tue, Jul 28, 2009 at 09:08:11PM -0700, Adam Williamson wrote:
> > On Wed, 2009-07-29 at 05:04 +0200, Dennis J. wrote:
> > > Occasionally the screen gets disabled for no reason at all on my F11
> > > system. This occurs even with the screensaver completely disabled and even
> > > after I typed something 5 seconds before.
It can go off while you are typing and it takes some seconds to come
back. Quite annoying.
> > > Anyone else seeing this?
>
> Literally dozens of people (actually, probably hundreds or thousands...)
> are seeing this. The report is:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=501601
Here is an older one:
https://bugzilla.redhat.com/show_bug.cgi?id=243022
It got CLOSED WONTFIX.
That's extremely unlikely to have been the same problem, since this
incarnation seems to have cropped up only with f11; many of those
complaining are people who are known to have run f9, f10 and they didn't
see the problem there. so that was probably something different (and
seems to be ATI-specific, anyway).
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
3:03 a.m.
2009/7/29 Adam Williamson <awilliam(a)redhat.com>
On Tue, 2009-07-28 at 23:32 -0600, Michal Jaegermann wrote:
> On Tue, Jul 28, 2009 at 09:08:11PM -0700, Adam Williamson wrote:
> > > On Wed, 2009-07-29 at 05:04 +0200, Dennis J. wrote:
> > > > Occasionally the screen gets disabled for no reason at all on my
F11
> > > > system. This occurs even with the screensaver completely disabled
and even
> > > > after I typed something 5 seconds before.
>
> It can go off while you are typing and it takes some seconds to come
> back. Quite annoying.
>
> > > > Anyone else seeing this?
>
> >
> > Literally dozens of people (actually, probably hundreds or
thousands...)
> > are seeing this. The report is:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=501601
>
> Here is an older one:
> https://bugzilla.redhat.com/show_bug.cgi?id=243022
> It got CLOSED WONTFIX.
That's extremely unlikely to have been the same problem, since this
incarnation seems to have cropped up only with f11; many of those
complaining are people who are known to have run f9, f10 and they didn't
see the problem there. so that was probably something different (and
seems to be ATI-specific, anyway).
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
the blanking occurs on intel too.
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
--
Linux counter #213090
8:24 a.m.
On Wed, Jul 29, 2009 at 4:03 AM, cornel panceac <cpanceac(a)gmail.com> wrote:
2009/7/29 Adam Williamson <awilliam(a)redhat.com>
On Tue, 2009-07-28 at 23:32 -0600, Michal Jaegermann wrote:
> > On Tue, Jul 28, 2009 at 09:08:11PM -0700, Adam Williamson wrote:
> > I> > On Wed, 2009-07-29 at 05:04 +0200, Dennis J. wrote:
> > > > > Occasionally the screen gets disabled for no reason at all on my
> F11
> > > Literally dozens of people (actually, probably hundreds or
> thousands...)
> > > are seeing this. The report is:
> > >
> > > https://bugzilla.redhat.com/show_bug.cgi?id=501601
> >
>
> That's extremely unlikely to have been the same problem, since this
> incarnation seems to have cropped up only with f11; many of those
> complaining are people who are known to have run f9, f10 and they didn't
> see the problem there. so that was probably something different (and
> seems to be ATI-specific, anyway).
>
>
the blanking occurs on intel too.
>
>
It's happening with the nvidia binary driver as well.
8:38 a.m.
On Wed, 29 Jul 2009, James Hubbard wrote:
On Wed, Jul 29, 2009 at 4:03 AM, cornel panceac
<cpanceac(a)gmail.com> wrote:
2009/7/29 Adam Williamson <awilliam(a)redhat.com>
On Tue, 2009-07-28 at 23:32 -0600, Michal Jaegermann
wrote:
> On Tue, Jul 28, 2009 at 09:08:11PM -0700, Adam
Williamson wrote:
> I> > On Wed, 2009-07-29 at 05:04 +0200, Dennis J. wrote:
> > > > Occasionally the screen gets disabled for no
reason at all on my F11
> > Literally dozens of people (actually, probably
hundreds or thousands...)
> > are seeing this. The report is:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=501601
>
That's extremely unlikely to have been the same problem, since this
incarnation seems to have cropped up only with f11; many of those
complaining are people who are known to have run f9, f10 and they
didn't see the problem there. so that was probably something
different (and seems to be ATI-specific, anyway).
the blanking occurs on intel too.
It's happening with the nvidia binary driver as well.
the consensus(?) seems to be a power management issue, not a video
issue.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com: http://cli.gs/WG6WYX
========================================================================
8:54 a.m.
2009/7/29 Robert P. J. Day <rpjday(a)crashcourse.ca>
On Wed, 29 Jul 2009, James Hubbard wrote:
> On Wed, Jul 29, 2009 at 4:03 AM, cornel panceac <cpanceac(a)gmail.com>
wrote:
>
>
> 2009/7/29 Adam Williamson <awilliam(a)redhat.com>
>
> On Tue, 2009-07-28 at 23:32 -0600, Michal Jaegermann
> wrote:
> > On Tue, Jul 28, 2009 at 09:08:11PM -0700, Adam
> Williamson wrote:
> > I> > On Wed, 2009-07-29 at 05:04 +0200, Dennis J. wrote:
> > > > > Occasionally the screen gets disabled for no
> reason at all on my F11
> > > Literally dozens of people (actually, probably
> hundreds or thousands...)
> > > are seeing this. The report is:
> > >
> > > https://bugzilla.redhat.com/show_bug.cgi?id=501601
> >
>
> That's extremely unlikely to have been the same problem, since this
> incarnation seems to have cropped up only with f11; many of those
> complaining are people who are known to have run f9, f10 and they
> didn't see the problem there. so that was probably something
> different (and seems to be ATI-specific, anyway).
>
> the blanking occurs on intel too.
>
> It's happening with the nvidia binary driver as well.
the consensus(?) seems to be a power management issue, not a video
issue.
rday
I agree with that: i had blank screens with nouveau and nvidia binary
driver, but only when my laptop was on battery.
I also get sometimes the centre popup telling that the screen brightness
was adjusted, but nothing changes (with both drivers above).
nvclock seems to adjust brightness successfully though
gg
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com: http://cli.gs/WG6WYX
========================================================================
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
--
Guido Grazioli <guido.grazioli(a)gmail.com>
Via Parri 11 48011 - Alfonsine (RA)
Mobile: +39 347 1017202 (10-18)
Key FP = 7040 F398 0DED A737 7337 DAE1 12DC A698 5E81 2278
Linked in: http://www.linkedin.com/in/guidograzioli
9:52 a.m.
2009/7/29 Guido Grazioli <guido.grazioli(a)gmail.com>:
I agree with that: i had blank screens with nouveau and nvidia binary
driver, but only when my laptop was on battery.
I also get sometimes the centre popup telling that the screen brightness
was adjusted, but nothing changes (with both drivers above).
nvclock seems to adjust brightness successfully though
gg>
I can agree this. More curious, after I install the nvidia blob I have
leave my laptop inside the dock, so I don't run with battery power and
don't see the bug again. With let me think it was caused by nouveau.
I've give it a test and pulled it out to run with battery power, and
after 5 minutes or less/more the screen turns black. So I guess this
is relay a power management issue as Bob mentioned and not a X driver
one.
--
Regards,
Niels
8:29 a.m.
2009/7/29 cornel panceac <cpanceac(a)gmail.com>:
> That's extremely unlikely to have been the same problem,
since this
> incarnation seems to have cropped up only with f11; many of those
> complaining are people who are known to have run f9, f10 and they didn't
> see the problem there. so that was probably something different (and
> seems to be ATI-specific, anyway).
>
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
> http://www.happyassassin.net
the blanking occurs on intel too.
Well, I see this also with nvidia. But only with the nouveau driver.
I've run the blob now (only for resume and suspend reasons) and I
haven't seen this for weeks.
--
Regards,
Niels
11:14 a.m.
On Wed, 2009-07-29 at 15:29 +0200, Niels Haase wrote:
2009/7/29 cornel panceac <cpanceac(a)gmail.com>:
>> That's extremely unlikely to have been the same problem, since this
>> incarnation seems to have cropped up only with f11; many of those
>> complaining are people who are known to have run f9, f10 and they didn't
>> see the problem there. so that was probably something different (and
>> seems to be ATI-specific, anyway).
>>
>> --
>> Adam Williamson
>> Fedora QA Community Monkey
>> IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
>> http://www.happyassassin.net
>
> the blanking occurs on intel too.
Well, I see this also with nvidia. But only with the nouveau driver.
I've run the blob now (only for resume and suspend reasons) and I
haven't seen this for weeks.
Yes, yes, I know. That's exactly the point. The *current* incarnation of
the bug affects multiple cards and drivers. The old one that Michal
pointed out did not, it only affected ATI.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
11:18 a.m.
<snip>
Yes, yes, I know. That's exactly the point. The *current* incarnation of
the bug affects multiple cards and drivers. The old one that Michal
pointed out did not, it only affected ATI.
Am getting blanking using Intel, would it be related.
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
Integrated Graphics Controller (rev 02)
F11-64bit\RawhideKernel(s)
11:23 a.m.
On Wed, 2009-07-29 at 17:18 +0100, Frank Murphy wrote:
<snip>
>
> Yes, yes, I know. That's exactly the point. The *current* incarnation of
> the bug affects multiple cards and drivers. The old one that Michal
> pointed out did not, it only affected ATI.
>
Am getting blanking using Intel, would it be related.
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
Integrated Graphics Controller (rev 02)
F11-64bit\RawhideKernel(s)
If the blanking happens apparently randomly, and manifests as the screen
just suddenly going blank but a keypress or mouse movement making it
come back, then yes, that's the bug we're discussing here.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
11:28 a.m.
On 29/07/09 17:23, Adam Williamson wrote:
On Wed, 2009-07-29 at 17:18 +0100, Frank Murphy wrote:
<snipped>
>
> Am getting blanking using Intel, would it be related.
> 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
> Integrated Graphics Controller (rev 02)
> F11-64bit\RawhideKernel(s)
If the blanking happens apparently randomly, and manifests as the screen
just suddenly going blank but a keypress or mouse movement making it
come back, then yes, that's the bug we're discussing here.
Yeah basically.
But only breaks with kernel: kernel-2.6.31-0.103.rc4.git2.fc12.x86_64
Ok on: kernel-2.6.31-0.94.rc4.fc12.x86_64
kernel-firmware-2.6.31-0.103.rc4.git2.fc12.noarch
11:35 a.m.
On Wed, 2009-07-29 at 17:28 +0100, Frank Murphy wrote:
On 29/07/09 17:23, Adam Williamson wrote:
> On Wed, 2009-07-29 at 17:18 +0100, Frank Murphy wrote:
<snipped>
>>
>> Am getting blanking using Intel, would it be related.
>> 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
>> Integrated Graphics Controller (rev 02)
>> F11-64bit\RawhideKernel(s)
>
> If the blanking happens apparently randomly, and manifests as the screen
> just suddenly going blank but a keypress or mouse movement making it
> come back, then yes, that's the bug we're discussing here.
>
Yeah basically.
But only breaks with kernel: kernel-2.6.31-0.103.rc4.git2.fc12.x86_64
Ok on: kernel-2.6.31-0.94.rc4.fc12.x86_64
kernel-firmware-2.6.31-0.103.rc4.git2.fc12.noarch
Different, then (or at least a different manifestation). The 'classic'
one is happening on F11, never mind slightly older Rawhide.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
10:43 a.m.
On Tue, Jul 28, 2009 at 11:43:37PM -0700, Adam Williamson wrote:
On Tue, 2009-07-28 at 23:32 -0600, Michal Jaegermann wrote:
> On Tue, Jul 28, 2009 at 09:08:11PM -0700, Adam Williamson wrote:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=501601
>
> Here is an older one:
> https://bugzilla.redhat.com/show_bug.cgi?id=243022
> It got CLOSED WONTFIX.
That's extremely unlikely to have been the same problem,...
My gut feeling is that this is exactly the same problem even if it
seems to be currently much more widespread and maybe not the same
code on a driver level is directly involved. Something misreads the
current activity state and an unwanted power management kicks in.
It appears that you need a "lucky" combination of a software and
hardware, possibly down to a chipset level, to be affected. Drivers
got more "ambitious" and this is easier to trigger. Note also
comments 11, 12 and 13 from bug 243022. At the reverse side of that
coin screensavers started now to kill a screen power management in
toto - see bz #508886 and #509660.
(and seems to be ATI-specific, anyway).
Err..., I do not think so.
Michal
11:16 a.m.
On Wed, 2009-07-29 at 09:43 -0600, Michal Jaegermann wrote:
> (and seems to be ATI-specific, anyway).
Err..., I do not think so.
I was talking about the old bug. You reported it against the radeon
driver, and the two other people who commented on the bug also had ATI
cards.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
5378
days inactive
5378
days old
17 comments
10 participants
participants (10)
-
Adam Williamson -
cornel panceac -
Dawid Zamirski -
Dennis Jacobfeuerborn -
Frank Murphy -
Guido Grazioli -
James Hubbard -
Michal Jaegermann -
Niels Haase -
Robert P. J. Day