Bug 582489 - Garbage when swithing from plymouth to gdm
Summary: Garbage when swithing from plymouth to gdm
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 599167 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-15 07:00 UTC by Michal Hlavinka
Modified: 2018-04-11 11:15 UTC (History)
6 users (show)

Fixed In Version: xorg-x11-drv-nouveau-0.0.16-7.20100423git13c1043.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 17:37:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
xorg log (152.07 KB, text/plain)
2010-04-15 07:00 UTC, Michal Hlavinka
no flags Details
screen shot (852.57 KB, image/jpeg)
2010-04-15 07:31 UTC, Michal Hlavinka
no flags Details
dmesg (54.46 KB, text/plain)
2010-04-15 08:42 UTC, Michal Hlavinka
no flags Details

Description Michal Hlavinka 2010-04-15 07:00:40 UTC
Created attachment 406691 [details]
xorg log

Description of problem:
When switching from plymouth to gdm there is garbage on both screens for about 3 seconds. See attached picture

Version-Release number of selected component (if applicable):
kernel-2.6.33.2-43.fc13.x86_64
xorg-x11-drv-nouveau-0.0.16-3.20100305git6b8b157.fc13.x86_64
mesa-dri-drivers-7.8.1-1.fc13.x86_64

How reproducible:
always

Steps to Reproduce:
1.boot gfx test day iso
2.
3.
  
Actual results:
garbage when switching from plymouth to gdm

Expected results:
no gargage

Additional info:
http://www.smolts.org/client/show/pub_5a47536e-7223-4621-a1e4-b73413602aa1

Comment 1 Michal Hlavinka 2010-04-15 07:31:57 UTC
Created attachment 406695 [details]
screen shot

Comment 2 Michal Hlavinka 2010-04-15 08:42:30 UTC
Created attachment 406707 [details]
dmesg

Comment 3 Ben Skeggs 2010-06-03 06:13:29 UTC
*** Bug 599167 has been marked as a duplicate of this bug. ***

Comment 4 Frederik Hertzum 2010-06-06 18:31:38 UTC
The image displayed contains data from the VRAM that may contain residual output from previous renderings. To see this, start some program that renders to the screen (may have to be something that goes fullscreen and uses OpenGL) and reboot (hot reboot -- i.e. don't shut down the machine entirely).

The severity of the bug should be elevated.

Comment 5 Fedora Update System 2010-06-26 01:34:35 UTC
xorg-x11-drv-nouveau-0.0.16-7.20100423git13c1043.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/xorg-x11-drv-nouveau-0.0.16-7.20100423git13c1043.fc13

Comment 6 Fedora Update System 2010-06-28 17:12:56 UTC
xorg-x11-drv-nouveau-0.0.16-7.20100423git13c1043.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-nouveau'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/xorg-x11-drv-nouveau-0.0.16-7.20100423git13c1043.fc13

Comment 7 Fedora Update System 2010-06-29 15:29:59 UTC
xorg-x11-drv-nouveau-0.0.16-7.20100423git13c1043.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Marco Vittorini Orgeas 2010-07-01 21:04:06 UTC
I can confirm the problem still persist,with the following package installed (and the system is currently up to date):

xorg-x11-drv-nouveau.x86_64     1:0.0.16-7.20100423git13c1043.fc13      @updates

Comment 9 Ben Skeggs 2010-07-01 22:02:20 UTC
You need xorg-x11-server-Xorg-1.8.0-16 also.

Comment 10 Marco Vittorini Orgeas 2010-07-02 09:01:51 UTC
Installed Packages
xorg-x11-server-Xorg.x86_64                1.8.0-17.fc13                @updates

The problem seems a little different:

I can confirm that the behaviour described here https://bugzilla.redhat.com/show_bug.cgi?id=582489#c4 - i.e. doing a "hot-rebooting" - doesn't occur anymore (no more scattered frames from the previous session).

I am actually referring to normal booting (i.e. start the machine from a off state).
I see again garbage passing from plymouth to gdm.For garbage I mean something as in the attached screenshot.

So I am assuming this bug still persist while a different one (see comment #4) has been solved.

Comment 11 Ben Skeggs 2010-07-06 00:12:01 UTC
The bug for both cold and warm booting is the same bug, so it doesn't make sense that one is fixed whilst the other isn't.

The difference between the two cases is that for a cold reboot, you have whatever VRAM is filled with when the system is first powered on, for a warm reboot, the previous session is left over rather than random contents.

Comment 12 Marco Vittorini Orgeas 2010-07-06 09:50:19 UTC
Well, so indeed: I can confirm that for a cold boot the problem persist, with a nvidia quadro nv140m.

When warm booting,I almost not see the bad "screen" because the switching is very fast.
If other users report this as solved, probably the issue is related to the specific used video card.

Comment 13 David Woodhouse 2010-10-13 23:32:46 UTC
This has recurred in f14. On rebooting, for a few seconds before the gdm login screen comes up, I see a pristine copy of what was on the screen before I rebooted.

Then the gdm screen is shown.... and the backlight level is set to zero.

Comment 14 David Woodhouse 2010-11-14 22:02:42 UTC
And now it's even stranger. On rebooting I get a garbage screen made up of shuffled tiles from what was on the screen before... and it *stays* there.

A libnotify window just appeared, warning me of an "install problem": The configuration defaults for GNOME Power Manager have not been installed correctly. It asks me to contact myself.

And the garbage screen is still *there* behind it.

After I SSH in and kill Xorg, it restarts and then I can see the login screen. It doesn't actually *work* but I suspect that's a different bug.

Comment 15 Matěj Cepl 2011-01-14 16:14:45 UTC
David, can you please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above? This bug is pretty dry on the current data.

Thanks in advance.

Comment 16 Fedora End Of Life 2012-08-16 17:37:46 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.