Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 506588
| Summary: | Firefox spontaneously crashes entire system | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | a_thing |
| Component: | xorg-x11-drv-ati | Assignee: | Dave Airlie <airlied> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | gecko-bugs-nobody, georges.dib, jglisse, mcepl, redhatbugzilla, spam2, stransky, thealbatross, walters, xgl-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-10-15 14:31:37 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
a_thing
2009-06-17 20:43:29 UTC
Looks like X issue, can you try to use some other graphics driver? Like VESA. 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 attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Created attachment 348546 [details]
dmesg right after restarting after crash
Created attachment 348594 [details]
Xorg.0.log after restarting (but before starting X again) after bug
Created attachment 348595 [details]
Xorg.1.log after restarting (but before starting X again) after bug
I reproduced the bug with this /etc/X11/Xorg.conf:
Section "Device"
Identifier "Radeon 9100"
VendorName "ATI"
Driver "vesa"
EndSection
I an running x86_64 Fedora 11, so this bug isn't i386-specific. I am running ATI Radeon 9200, so it isn't 9100-specific. 'lsmod' shows 'radeon'. The RPM would be xorg-x11-drv-ati-6.12.2-14.fc11.x86_64. Display 1600x1200 1 GB RAM I have seen this crash while doing 'search' at bugzilla, so it's not related the web pages being somehow exotic, image-heavy, many-downloads-at-once or any such load/feature issue. The freeze can happen after 1-5 page presentations, so it's not related to a slow leak that goes critical after a long time. Nothing useful (to me, anyway) in the dmesg or X log. It probably does not matter, but I use 1280x1024 resolution with 512MB RAM. The Radeon 9200 and Radeon 9100 are both from the Radeon R200 chipset series (Radeon 8500 through 9250). I've been having the same problem on RHEL 5 with the final version of Firefox 3.5. The X server either crashes or freezes. When it freezes I either have to SSH in remotely or reboot the machine. Linux server122 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:12 EDT 2008 i686 i686 i386 GNU/Linux If I can figure out how, I will attache the logs. Created attachment 350604 [details]
xorg.conf
An xorg.conf file from a system showing this behavior
Created attachment 350605 [details]
a dmesg file after a crash
Created attachment 350606 [details]
An Xorg log after a crash
Created attachment 350608 [details]
An older Xorg.log that likely contains crash data as well
(In reply to comment #14) > Created an attachment (id=350608) [details] > An older Xorg.log that likely contains crash data as well The log is not complete. It ends exactly at the point when it starts to be interesting by line saying "Backtrace". It would be interesting to see what should follow, but without that I am afraid it is not much of any use. David S., bigger problem is that this bug has been filed as ATI bug, but you have intel graphics chip. Please file a separate bug mentioning attachment 350605 [details], attachment 350606 [details], and attachment 350608 [details]. Thank you This bug was so annoying that I switched my video card to an nVidia Geforce 4 MX 440 (rivafb driver). The bug no longer rears its ugly head. This (and 436632, 491399, 501095, 505207) looks to be a duplicate of 498457. I am clausing this bug, firefox works fine with fedora 12 & radeon hw here. Reopen if you experience similar issue with fedora 12. ***PLEASE REOPEN***, Firefox on fedora 12 does NOT work fine with Radeon RV620 chipset. Other problems exist in driver, but firefox causes systemwide crash/kerneloops. Backtrace is as follows: WARNING: at drivers/gpu/drm/radeon/r600_blit_kms.c:550 r600_blit_prepare_copy+0x36/0x3e4 [radeon]() (Not tainted) Hardware name: 2764CTO Modules linked in: fuse cpufreq_ondemand acpi_cpufreq freq_table ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 uinput snd_hda_codec_conexant snd_hda_intel arc4 ecb snd_hda_codec iwlagn iwlcore snd_hwdep snd_seq uvcvideo sdhci_pci sdhci snd_seq_device mac80211 snd_pcm mmc_core videodev snd_timer v4l1_compat ricoh_mmc v4l2_compat_ioctl32 snd joydev cfg80211 e1000e thinkpad_acpi iTCO_wdt soundcore rfkill iTCO_vendor_support i2c_i801 snd_page_alloc wmi dm_multipath firewire_ohci firewire_core crc_itu_t yenta_socket rsrc_nonstatic pata_acpi ata_generic video output radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: microcode] Pid: 1571, comm: Xorg Not tainted 2.6.31.12-174.2.3.fc12.x86_64 #1 Call Trace: [<ffffffff81051710>] warn_slowpath_common+0x84/0x9c [<ffffffff8105173c>] warn_slowpath_null+0x14/0x16 [<ffffffffa00a12aa>] r600_blit_prepare_copy+0x36/0x3e4 [radeon] [<ffffffffa0098214>] r600_copy_blit+0x2b/0x57 [radeon] [<ffffffffa00795f9>] radeon_move_blit+0x101/0x13f [radeon] [<ffffffffa007986f>] radeon_bo_move+0x238/0x25e [radeon] [<ffffffffa004c248>] ttm_bo_handle_move_mem+0x1cc/0x2bb [ttm] [<ffffffffa004dab6>] ttm_bo_move_buffer+0xb0/0xef [ttm] [<ffffffffa004db37>] ttm_buffer_object_validate+0x42/0xbf [ttm] [<ffffffffa007a22c>] radeon_object_list_validate+0xaf/0x152 [radeon] [<ffffffffa008692f>] radeon_cs_parser_relocs+0x19c/0x1fa [radeon] [<ffffffffa0086cae>] ? radeon_cs_ioctl+0x0/0x19a [radeon] [<ffffffffa0086d71>] radeon_cs_ioctl+0xc3/0x19a [radeon] [<ffffffffa001521f>] drm_ioctl+0x237/0x2f4 [drm] [<ffffffff81108dd1>] vfs_ioctl+0x6f/0x87 [<ffffffff811092e0>] do_vfs_ioctl+0x47b/0x4c1 [<ffffffff8110937c>] sys_ioctl+0x56/0x79 [<ffffffff81011cf2>] system_call_fastpath+0x16/0x1b thealbatross, please, file a new bug against xorg-x11-drv-ati component. Please attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, whole system log (/var/log/messages), and X server log file (/var/log/Xorg.*.log) 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. I have done as you have asked. I'm sorry if I botched my etiquette (I suspect I did) with the last comment for bug reporting, this is very new to me. (In reply to comment #22) > I have done as you have asked. I'm sorry if I botched my etiquette (I suspect I > did) with the last comment for bug reporting, this is very new to me. That's absolutely perfect ... we all have been there once. Keeping one bug per one issue is one of the most firmly held rules to keep us at least partially sane :) Here's the link should anyone be interested: https://bugzilla.redhat.com/show_bug.cgi?id=565346 |