Bug 717071

Created attachment 510171 [details]
system logs

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

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.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Created attachment 510203 [details]
dmesg

Created attachment 510205 [details]
new system logs

Created attachment 510206 [details]
xorg config

Requested info. No new xorg logs as the system crashed too fast for them to be written to disk. (wrote unable to handle null pointer deference to console for dbus with lots of lines about rcu, sadly my card reader is broken right now so I can provide a screen shot)

with this evening new kernel and gdm packages the system boots and can start gdm without locking up the system, so I have full logs

However the framebuffer console is still completely parasited by green/magenta traces and X mode is completely unusable (full screen so parasited by green/magenta artifacts nothing can be read)

Created attachment 510333 [details]
system logs

Created attachment 510335 [details]
dmesg

Created attachment 510336 [details]
lspci

Created attachment 510338 [details]
xorg logs

After investigating more it appears one of the gddr heatsinks on the gfx card has fallen of so this gddr was propaly cooked and unreliable (shougln't crash the kernel though)

with a brand new gfx card and
xorg-x11-drv-ati-6.14.0-9.20110316gitcdfc007ec.fc16.x86_64
xorg works as it should.

Whith rawhide latest xorg-x11-drv-ati, though, xorg still crashes on startup

Created attachment 512040 [details]
working xorg logs with xorg-x11-drv-ati-6.14.0-9.20110316gitcdfc007ec.fc16.x86_64

Created attachment 512041 [details]
failing xorg logs with xorg-x11-drv-ati-6.14.1-2.20110525gitfe5c42f51.fc15.x86_64

According to rpm rules
xorg-x11-drv-ati-6.14.1-2.20110525gitfe5c42f51.fc15.x86_64 is newer than
xorg-x11-drv-ati-6.14.0-9.20110316gitcdfc007ec.fc16.x86_64

(In reply to comment #14)
> Created attachment 512041 [details]
> failing xorg logs with
> xorg-x11-drv-ati-6.14.1-2.20110525gitfe5c42f51.fc15.x86_64
> 
> According to rpm rules
> xorg-x11-drv-ati-6.14.1-2.20110525gitfe5c42f51.fc15.x86_64 is newer than
> xorg-x11-drv-ati-6.14.0-9.20110316gitcdfc007ec.fc16.x86_64

---------------------------------
In function RADEONScreenInit_KMS:
(from frame 3: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f56558f0000+0xd9e01) [0x7f56559c9e01])
968: 	    return FALSE;
969:     }
970: 
971:     xf86SetBlackWhitePixels(pScreen);
972: 
973:     if (pScrn->bitsPerPixel > 8) {
974: 	VisualPtr  visual;
975: 
976: 	visual = pScreen->visuals + pScreen->numVisuals;
977: 	while (--visual >= pScreen->visuals) {
978: >>>>>>> 	    if ((visual->class | DynamicClass) == DirectColor) {
979: 		visual->offsetRed   = pScrn->offset.red;
980: 		visual->offsetGreen = pScrn->offset.green;
981: 		visual->offsetBlue  = pScrn->offset.blue;
982: 		visual->redMask     = pScrn->mask.red;
983: 		visual->greenMask   = pScrn->mask.green;
984: 		visual->blueMask    = pScrn->mask.blue;
985: 	    }
986: 	}
987:     }
988: 


Frame 4: /usr/bin/Xorg (AddScreen+0x17f) [0x433bdf]
	/usr/src/debug/xorg-server-20110510/dix/dispatch.c:3906
	AddScreen
Frame 5: /usr/bin/Xorg (InitOutput+0x282) [0x479fb2]
	/usr/src/debug/xorg-server-20110510/hw/xfree86/common/xf86Init.c:739
	InitOutput
Frame 6: /usr/bin/Xorg (0x400000+0x22a39) [0x422a39]
	/usr/src/debug/xorg-server-20110510/dix/main.c:208
	main

  3448.481] Caught signal 11 (Segmentation fault). Server aborting

The patch at: https://bugs.freedesktop.org/show_bug.cgi?id=39572
might help with the GPU lockup issue.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Still an issue with f17/rawhide ?

I haven't seen it for quite a while

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.