Bug 533973 - UMS: X is crashing (firefox easily trigger the crash)
Summary: UMS: X is crashing (firefox easily trigger the crash)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: card_R500/mM
: 529237 534142 536832 537000 537229 537674 539450 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-09 22:13 UTC by Mark Gunstrom
Modified: 2018-04-11 14:53 UTC (History)
13 users (show)

Fixed In Version: 6.13.0-0.11.20091119git437113124.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-28 12:25:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg log (84.69 KB, text/plain)
2009-11-09 22:14 UTC, Mark Gunstrom
no flags Details

Description Mark Gunstrom 2009-11-09 22:13:33 UTC
Description of problem: X is crashing when visiting certain sites in in Firefox (e.g., www.newegg.com)


Version-Release number of selected component (if applicable):


How reproducible:
Very.

Steps to Reproduce:
1. Visit certain site in Firefox (e.g., www.newegg.com)
2. 
3.
  
Actual results:
X crashes

Expected results:
X doesn't crash

Additional info:
Using xorg-x11-drv-ati driver, KMS disabled.

Comment 1 Mark Gunstrom 2009-11-09 22:14:44 UTC
Created attachment 368300 [details]
Xorg log

Comment 2 Matěj Cepl 2009-11-12 17:23:29 UTC
possible duplicates bug 533645, bug 235126

Comment 3 Jérôme Glisse 2009-11-12 18:43:24 UTC
Mark do you have issue with KMS? If so did you open a bug ? We are focussing on fixing KMS issue right now.

Comment 4 Mark Gunstrom 2009-11-12 21:58:01 UTC
Jerome-- No, I do not experience these crashes with KMS enabled.

Comment 5 Jérôme Glisse 2009-11-17 18:26:32 UTC
*** Bug 537674 has been marked as a duplicate of this bug. ***

Comment 6 Jérôme Glisse 2009-11-17 18:27:14 UTC
*** Bug 529237 has been marked as a duplicate of this bug. ***

Comment 7 Jérôme Glisse 2009-11-17 18:37:22 UTC
*** Bug 537229 has been marked as a duplicate of this bug. ***

Comment 8 Jérôme Glisse 2009-11-17 18:37:37 UTC
*** Bug 537000 has been marked as a duplicate of this bug. ***

Comment 9 Jérôme Glisse 2009-11-17 18:59:59 UTC
*** Bug 534142 has been marked as a duplicate of this bug. ***

Comment 10 Jérôme Glisse 2009-11-17 19:01:01 UTC
*** Bug 536832 has been marked as a duplicate of this bug. ***

Comment 11 Jérôme Glisse 2009-11-23 12:10:01 UTC
*** Bug 539450 has been marked as a duplicate of this bug. ***

Comment 12 David Wood 2009-11-23 12:40:16 UTC
I can confirm removing the 'nomodeset' option from the boot line fixes the firefox triggered X crashes.  However, without this option, the laptop display still suffers from a whiteout (HP nx9010 with a Radeon IGP 340M).  Fortunately I'm using an external monitor, so once I've logged in I can turn off the LCD display.  Far from ideal though.

Comment 13 Sukru TIKVES 2009-11-24 15:33:58 UTC
I'm experiencing the same issue, too.

My chipset is Radeon Express 200M, which requires nomodeset in order to display any output at all, thus removing nomodeset is not an option.

This only happens with Firefox, Chromium will browse the site fine.

Comment 14 Peter Lemenkov 2009-11-25 09:51:43 UTC
Folks, it seems that similar issue was fixed in xorg-x11-drv-ati-6.13.0-0.11.20091119git437113124.fc12

See this ticket for the details:

https://bugzilla.redhat.com/show_bug.cgi?id=538561

So let's check whether this issue still exists with the latest xorg-x11-drv-ati from updates-testing

Comment 15 Peter Lemenkov 2009-11-25 17:00:11 UTC
Folks, it seems that this issue has gone!
Could anyone confirm that?

Comment 16 James Hubbard 2009-11-25 17:13:29 UTC
I've noticed that it seems to be working better.  It doesn't crash on newegg now.  I'm not getting any crashes in gthumb like I was. However, gthumb will not display any photos for me now nor do I see thumbnails in the folders views.  It may be unrelated issue caused by a different package update.

Comment 17 Michal Zamazal 2009-11-25 19:57:39 UTC
Yes, fedoraforum.org and next pages in Firefox don't make for crash after this update. Also Google Chrome doesn't crash the Xorg server.

Comment 18 David Wood 2009-11-27 10:36:51 UTC
Having installed the version of xorg-x11-drv-ati mentioned in comment 14, it does seem to have fixed this problem.

Comment 19 Sukru TIKVES 2009-11-28 12:19:09 UTC
I agree with #18, the latest update (now out of testing) fixed the problem for me, at least for newegg.

Comment 20 Peter Lemenkov 2009-11-28 12:25:48 UTC
Ok, I think we may close this ticket now.

Comment 21 Laurent Wandrebeck 2009-11-28 17:33:51 UTC
update installed. had a freeze anyway, while browsing:

[mi] EQ overflowing. The server is probably stuck in an infinite loop.

Backtrace:
0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x49e8d8]
1: /usr/bin/Xorg (mieqEnqueue+0x1f4) [0x49e2a4]
2: /usr/bin/Xorg (xf86PostMotionEventP+0xce) [0x478f0e]
3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fed1e631000+0x50bf) [0x7fed1e6360bf]
4: /usr/bin/Xorg (0x400000+0x6be17) [0x46be17]
5: /usr/bin/Xorg (0x400000+0x116b13) [0x516b13]
6: /lib64/libpthread.so.0 (0x3cfd400000+0xefa0) [0x3cfd40efa0]
7: /lib64/libc.so.6 (ioctl+0x7) [0x3cfc8d61f7]
8: /usr/lib64/libdrm.so.2 (drmIoctl+0x23) [0x3d11003203]
9: /usr/lib64/libdrm.so.2 (drmCommandWriteRead+0x1c) [0x3d1100344c]
10: /usr/lib64/libdrm_radeon.so.1 (0x7fed1f8e6000+0xff9) [0x7fed1f8e6ff9]
11: /usr/lib64/libdrm_radeon.so.1 (0x7fed1f8e6000+0x1045) [0x7fed1f8e7045]
12: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7fed1fb06000+0xb996e) [0x7fed1fbbf96e]
13: /usr/lib64/xorg/modules/libexa.so (0x7fed1eea2000+0x8120) [0x7fed1eeaa120]
14: /usr/bin/Xorg (0x400000+0x152bf4) [0x552bf4]
15: /usr/bin/Xorg (0x400000+0x2df50) [0x42df50]
16: /usr/bin/Xorg (0x400000+0x2c69c) [0x42c69c]
17: /usr/bin/Xorg (0x400000+0x21cfa) [0x421cfa]
18: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x3cfc81eb1d]
19: /usr/bin/Xorg (0x400000+0x218a9) [0x4218a9]


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