Bug 537229

Summary: UMS:R420:X800 Firefox kills X when boot with nomodeset
Product: [Fedora] Fedora Reporter: Sebastian Vahl <fedora>
Component: xorg-x11-drv-atiAssignee: Jérôme Glisse <jglisse>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: gecko-bugs-nobody, mcepl, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: card_R400/M
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-17 18:37:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
/var/log/messages after crash
none
/var/log/Xorg.0.log after crash
none
dmesg after crash
none
/var/log/Xorg.0.log.old after crash
none
output of dmesg after crash none

Description Sebastian Vahl 2009-11-12 21:20:14 UTC 
Description of problem:

I have a two monitor layout with two differenz sized CRTs (17" and 19"). I have to use nomodeset to work with them properly. With modesetting enabled on my X800/R420 only the smaller monitor is used.
But with modesetting disabled the X-Server will crash on some websites with firefox (Konqueror is fine). With modesetting enabled the website will be displayed without crash.
On at least one website I can reproduce this behaviour: http://www.fsarchiver.org/forums/viewtopic.php?f=17&t=902

There is no terminal output of firefox and nothing relevant in .xsession-errors. I'll attach /var/log/messages and /var/log/Xorg.0.log if there is maybe some relevant information in it.


Version-Release number of selected component (if applicable):
firefox-3.5.4-1.fc12 (both i686 and x86_64)

How reproducible:
ever

Steps to Reproduce:
1. Boot F12-rc4 with nomodeset on a radeon chipset
2. Browse with firefox to http://www.fsarchiver.org/forums/viewtopic.php?f=17&t=902
  
Actual results:
X crashes

Expected results:
no crash

Additional info:
On another machine with an nvidia graphics card (Geforce 4 Ti) all is working fine.
Comment 1 Sebastian Vahl 2009-11-12 21:21:10 UTC 
Created attachment 369325 [details]
/var/log/messages after crash
Comment 2 Sebastian Vahl 2009-11-12 21:21:43 UTC 
Created attachment 369326 [details]
/var/log/Xorg.0.log after crash
Comment 3 Sebastian Vahl 2009-11-12 21:23:08 UTC 
(In reply to comment #0)
> 1. Boot F12-rc4 with nomodeset on a radeon chipset

I meant the Gnome live image from here: http://alt.fedoraproject.org/pub/alt/stage/12-RC.4/Fedora-12-i686-Live/Fedora-12-i686-Live.iso
Comment 4 Matěj Cepl 2009-11-14 21:44:11 UTC 
Could we get output from the command dmesg AFTER Xorg crashes (when it restarts again or from command line), please?
Comment 5 Sebastian Vahl 2009-11-14 22:15:41 UTC 
Created attachment 369555 [details]
dmesg after crash

(In reply to comment #4)
> Could we get output from the command dmesg AFTER Xorg crashes (when it restarts
> again or from command line), please?  

Sure, but apparrently there is no new output in dmesg after X crashes and restarts.
Comment 6 Jérôme Glisse 2009-11-16 09:38:26 UTC 
Sebastian did you open a bug for your KMS issue ? We are focussing on fixing KMS. Otherwise after restart the old Xorg log should be /var/log/Xorg.0.log.old.
Comment 7 Sebastian Vahl 2009-11-16 09:50:19 UTC 
(In reply to comment #6)
> Sebastian did you open a bug for your KMS issue ? We are focussing on fixing
> KMS. 

Not directly for this issue but in the development phase of F12 I've had another issue which seems to be related to my different monitors (which seemed to be fixed now): bug #511037
But I could open another one If needed.

> Otherwise after restart the old Xorg log should be
> /var/log/Xorg.0.log.old.  

I think I've attached the .old log. But I'll recheck this later.
Comment 8 Sebastian Vahl 2009-11-16 12:02:02 UTC 
Created attachment 369675 [details]
/var/log/Xorg.0.log.old after crash
Comment 9 Sebastian Vahl 2009-11-16 12:03:34 UTC 
Created attachment 369676 [details]
output of dmesg after crash

dmesg and /var/log/dmesg doesn't seem to have the same content. So I've redirected the output of 'dmesg' in a file. Above I've also uploaded the real /var/log/Xorg.0.log.old
Comment 10 Jérôme Glisse 2009-11-17 18:37:22 UTC 

*** This bug has been marked as a duplicate of bug 533973 ***