Bug 537000 - UMS:RV370|M22:X300 crash detected in firefox-3.5.4-1.fc12
Summary: UMS:RV370|M22:X300 crash detected in firefox-3.5.4-1.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 533973
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: card_R300e/m, abrt_hash:b5c697be56c1f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-12 05:58 UTC by Derek Schmidt
Modified: 2018-04-11 09:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-17 18:37:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (133.57 KB, text/plain)
2009-11-12 05:58 UTC, Derek Schmidt
no flags Details
Xorg.0.log by request (47.64 KB, text/plain)
2009-11-13 13:37 UTC, Derek Schmidt
no flags Details

Description Derek Schmidt 2009-11-12 05:58:32 UTC
abrt detected a crash.

How to reproduce
-----
1. Boot up the system.
2. Open Firefox
3. Go to onemanga.com

Comment: When I take the three steps, it seems to reset the X server as if I pressed ctrl-alt-backspace. GDM loads back up and I have to sign in once more.
Attached file: backtrace
cmdline: /usr/lib/firefox-3.5.4/firefox
component: firefox
executable: /usr/lib/firefox-3.5.4/firefox
kernel: 2.6.31.5-127.fc12.i686
package: firefox-3.5.4-1.fc12
rating: 4
reason: Process was terminated by signal 6

Comment 1 Derek Schmidt 2009-11-12 05:58:34 UTC
Created attachment 369146 [details]
File: backtrace

Comment 2 Martin Stransky 2009-11-12 08:13:05 UTC
It crashed in X - please attach you Xorg.0.conf and try some other X driver (like vesa).

Comment 3 Derek Schmidt 2009-11-13 13:37:45 UTC
Created attachment 369430 [details]
Xorg.0.log by request

Comment 4 Derek Schmidt 2009-11-13 13:38:41 UTC
I don't know where Xorg.0.conf is found. I'm new to Fedora. And if I can try another X driver without Xorg.conf, I don't know how.

Comment 5 Matěj Cepl 2009-11-15 15:06:22 UTC
(In reply to comment #4)
> I don't know where Xorg.0.conf is found. I'm new to Fedora. And if I can try
> another X driver without Xorg.conf, I don't know how.  

/etc/X11/xorg.conf but if you don't know about it then you are most likely not having one.

Comment 6 Jérôme Glisse 2009-11-16 10:40:00 UTC
Why is KMS disabled ? Do you have issue with KMS ? Did you open a bug for KMS issue ? We are focussing on fixing KMS.

Comment 7 Derek Schmidt 2009-11-17 03:48:17 UTC
(In reply to comment #6)
Is this what you're referring to? 
(II) [KMS] drm report modesetting isn't supported.

Before I was able to install Fedora I had trouble even getting the live USB to boot up. I first heard about the nomodeset kernel switch on the grub command line, and used it in order to get the GUI (or anything usable, really). Upon installing it, I've never had any more problem with modesetting, that is, nothing I could see. No errors, no lockups. I think I noticed seeing another bug already filed related to the Radeon Mobility X300 or in its family, and if I did see it, it would have looked to me like it was taken care of as far as I could help already. And as I said, I hadn't seen anything else to say that anything was wrong anymore. I am not at all averse to helping with this (and God knows I have the time), but I don't know how. Could you point me in the right direction?

(In reply to comment #5)
Yes, I'm familiar with /etc/X11/xorg.conf from when I had Ubuntu, but I was never able to find it, and later discovered why. And the "Xorg.0.conf" part of the request kinda threw me off. I've discovered how to actually generate the xorg.conf file, but I thought it might not be representative of what Fedora currently uses to boot up. If you want me to generate it and post it, I'm more than happy to do it. And I guess in the process I'd be able to try vesa and see if that works any better.

Comment 8 Jérôme Glisse 2009-11-17 18:37:37 UTC

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


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