Bug 699922

Sorry, forgot to ask in the forum, can you read https://fedoraproject.org/wiki/How_to_debug_Xorg_problems and provide the output suggested, particularly Xorg.0.log and /var/log/messages with drm.debug=15 kernel parameter? thanks!

I just tried to collect the data using that laptop and connecting a Sceptre (same model) via a keyboard/video/mouse switcher box, to the VGA port on the T61 - and it works very well (autodetects, I can reposition, etc)! So, it seems the issue is when the laptop is plugged into the IBM Type 2504 docking station, which has two external-monitor connections (one VGA, on DVI; in the present case, I'm connected to the DVI port) ... I should be able to get back to that office this evening.

Created attachment 495338 [details]
FILE_1

Created attachment 495341 [details]
FILE 2

Created attachment 495342 [details]
FILE 3

Created attachment 495343 [details]
FILE 4

OK, it's not as repeatable as I thought. I put the laptop back into the Type 2504 Dock, and got different symptoms. Still hosed when using multihead, OK when single-head. I'll put some screen photos up at http://wstidolph.imgur.com/fedorabug699922

First, I just put the laptop into the dock - it was already booted and running, no special kernel params, and no updates since the first test. Turned on the external monitor (attached to the DVI port on the Dock). The laptop detected the second monitor and worked with both monitors just fine. Then I opened the gnome Displays dialog and moved the gnome top panel from the laptop screen to the external screen and hit Apply. There was a long long long pause, where the mouse moved but nothing I clicked on or typed was activating anything in the shell ... ALT-F2 worked to get me to a terminal, so I think it was gnome hung up somehow. Eventually, like a minute later, the shell started accepting inputs again. I used it for a little bit, launched apps ... then gnome tried to display the "Windows" view (maybe I tossed the mouse up left by accident) and the system hung hard - frozen mouse, even ALT-F2 couldn't get any reaction. I got a picture of that screen, at http://imgur.com/2vbHc - mostly it looks OK, but one of the windows is all blue and there was some minor mis-drawing on the upper left and at the corners of the gnome doc area ... I wonder if gnome *started* redrawing the screen but hung up before finishing.

Anyway, I rebooted, this time with drm.debug=15. The shell came up with a background image that looked like it was using the wrong decoder stride or something - like a loss of horizontal synch on a TV. (http://imgur.com/elhyI) But only the background was corrupt - I could open a terminal window, and it would be fine, or bring up the Activities dock and it would be fine (even including transparency effects). Before I did anything else I captured the /var/log/messages (see attached file "reboot_in_dock_messages" with comment "FILE_1") and /var/log/Xorg.0.log (see attached file "reboot_in_dock_Xorg.0.log", "FILE 2")

I again brought up the Displays control panel and adjusted something, and the backround cleared up when I hit 'Apply.' Again I started writing a bug report ... and a bit later, again gnome-shell hung, so I captured messages and Xorg.0.log again (reboot_in_dock_lockup_messages, "FILE 3", and reboot_in_dock_lockup_Xorg.0.log, "FILE 4"); when I rebooted, I got the same corrupt-background look on both screens, though it was a different background (http://i.imgur.com/rjJxd.jpg)

Then I took the machine off the 2504 Dock, and rebooted it, connected the external monitor just to the external VGA port of the laptop (no Dock). Booted OK, looked OK, then locked up hard - loss of graphics, just a text dump  with a whole bunch of repeating "nouveau_sgdma_destroy:83 -" and  "nouveau_sgdma_destroy:62 -" lines (I took a picture of that), followed by a short blast of drm_crtc_helper_set_config messages. Interestingly, the text is corrupted in a couple places (worst at the bottom). See http://imgur.com/RojFj

The upshot from my point of view is that every attempt to use multihead is at best 5-minute succesful.

Created attachment 495817 [details]
FILE 5 Xorg.0.log after dual external screen boot (corrupted)

FILE 5 Xorg.0.log after dual external screen boot (corrupted). Connected two screens to Type 2504 Dock, rebooted T61 laptop in doc, shows this dual screen and no gnome-shell reaction to mouse/KB. ALT-F2 worked to get to terminal.

Created attachment 495818 [details]
FILE 6 'messages' after reboot with 2 external screens (corrupted)

FILE 6 /var/log/messages after dual external screen boot (corrupted). Connected two screens to Type 2504 Dock, rebooted T61 laptop in doc, shows this dual screen and no gnome-shell reaction to mouse/KB. ALT-F2 worked to get to terminal.

TWO EXTERNAL SCREENS also corrupts, hangs.

Put the running T61 laptop into the Type 2504 Dock, with two external screens (identical Sceptre X24WG-1080, which is a 1920x1200 panel); one screen DVI, the other is VGA connector. On initial connect, both screen recognizes and useful but gnome-shell had gone into into 'fallback' non-accelerated mode.

Rebooted. Got gnome-shell showing but with corrupted backgoround on both screen (http://i.imgur.com/nWsx9.jpg). Switched into terminal (ALT-F2) and captured Xorg.0.log (FILE 5, attached) and /var/log/messages (FILE 6, attached).

Switched back to graphics terminal, screen had no background image at all (just the gnome-shell panels). Launched Firefox, and machine exited graphics mode, put up some duped text and froze hard. Was not running drm.debug=15, sorry. Took photos of the screen dump (http://i.imgur.com/gopWl.jpg and http://i.imgur.com/XjRCk.jpg).

Multihead gnome-shell is still unusable on NVS140M (at least in my T61P with 1680x1050 panel).

Just now (5/5/2011) did update Fedora 15, still can't get multihead to work with gnome3, works OK with KDE4.6.

gnome-desktop3-3.0.1-2.fc15.i686
gnome-shell-3.0.1-2.fc15.i686

FWIW, I think it behaves like a colormap initialization problem - on shell startup, I get the weird blocks and colors and such, but I can see from their grouping that they are arranged according to the expected gnome shell UI compoents - I can see where the docks are, that sort of things. The mouse cursor is always fine. If I toss the mouse to the upper left, I see ripples in the upper-left corner that are just where the gnome animation happens. And, about 1 in 5 restarts of gdm I get a sane shell which runs for a while (then I quit gnome, since I can't use it if I can't rely on it ... back to KDE for now! But I hope you can get nouveau/gnome3 multihead to work, I really do ...)

Another clue ;) ... turns out the I have KDE running with Desktop Effects disabled. If I enable DE, then the screen gets block-scrambled ... some of the areas look OK (appear to be untouched by activating DE) while many parts get covered with multicolored blocks.

The corruption issue appears to be cleared as of:

kernel 2.6.38.5-24.fc15.i686.PAE
xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.i686
gnome-shell-3.0.1-4.fc15.i686

I have set up a laptop/dock/single external monitor (so, a two-monitor config) and verified I can reboot, reposition screens. There's still a transient corruption during initialization, but it clears up after a few seconds.

The corruption *remains* using KDE 4.6.2-1 if I enable Desktop Effects.

Also, the hang remains under gnome-shell - it runs OK for a few minutes then completely gnome-shell stops updating; the mouse cursor continues to move and repait properly (no 'droppings'). I can Alt-F2 at least once from the frozen shell to a terminal, and kill the gnome-shell session; usually it restarts, sometimes it doesn't (when I switch back, the shell is still frozen).

When I connect an external monitor to my ThinkPad T61 both screens go black with no picture. I had to activate the "X11 ZAP" functionality or had to hard turn off the laptop.

Both screens work during boot-up and gdm. They go blank after logging into Gnome3 or when plugging the 2nd monitor after being in Gnome 3.

$ lspci | grep -i VGA
01:00.0 VGA compatible controller: nVidia Corporation G84M [Quadro NVS 140M] (rev a1)

$ rpm -q gnome-shell
gnome-shell-3.0.2-1.fc15.x86_64

(In reply to comment #15)
> When I connect an external monitor to my ThinkPad T61 both screens go black
> with no picture. I had to activate the "X11 ZAP" functionality or had to hard
> turn off the laptop.
> 
> Both screens work during boot-up and gdm. They go blank after logging into
> Gnome3 or when plugging the 2nd monitor after being in Gnome 3.
> 
> $ lspci | grep -i VGA
> 01:00.0 VGA compatible controller: nVidia Corporation G84M [Quadro NVS 140M]
> (rev a1)
> 
> $ rpm -q gnome-shell
> gnome-shell-3.0.2-1.fc15.x86_64

Not the same bug.  Sounds like 701244, which I see you commented in already.

(In reply to comment #16)
> (In reply to comment #15)
> > When I connect an external monitor to my ThinkPad T61 both screens go black
> > with no picture. I had to activate the "X11 ZAP" functionality or had to hard
> > turn off the laptop.
> > 
> > Both screens work during boot-up and gdm. They go blank after logging into
> > Gnome3 or when plugging the 2nd monitor after being in Gnome 3.
> > 
> > $ lspci | grep -i VGA
> > 01:00.0 VGA compatible controller: nVidia Corporation G84M [Quadro NVS 140M]
> > (rev a1)
> > 
> > $ rpm -q gnome-shell
> > gnome-shell-3.0.2-1.fc15.x86_64
> 
> Not the same bug.  Sounds like 701244, which I see you commented in already.

Agree. 701244 is the correct bug report for my situation.

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. 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 '15' 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 15 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