Description of problem: after working for a few minutes X freezes completely Version-Release number of selected component (if applicable): Kernel 2.6.28.1-17.fc10.x86_64 Graphics adapter is Intel GMA 3100 (integrated to motherboard) How reproducible: happened every time after reboot. Steps to Reproduce: 1. log into system using gdm 2. start working 3. Actual results: X freezes totally, even mouse is no longer responsive Expected results: no freeze Additional info: if booted with kernel option vga=0x31b there where no freezes, but some resource conflicts between vesa_fb and the graphics driver. I will add those log infos later. Unfortunately I did not find logs to show any clues about what happened when the system freezes. Compiz in not used and no xorg.conf exists
if I boot the machine with vga=0x31b there is as I said no freeze but the following is shown by demsg: lo: Disabled Privacy Extensions JBD: barrier-based sync failed on dm-0:8 - disabling barriers [drm] Initialized drm 1.1.0 20060810 pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 pci 0000:00:02.0: setting latency timer to 64 [drm] Initialized i915 1.6.0 20080730 on minor 0 mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining resource map sanity check conflict: 0xe0000000 0xefffffff 0xe0000000 0xe07effff vesafb ------------[ cut here ]------------ WARNING: at arch/x86/mm/ioremap.c:227 __ioremap_caller+0xc7/0x299() (Not tainted) Modules linked in: i915 drm ipv6 vboxnetflt vboxdrv cpufreq_ondemand acpi_cpufreq freq_table dm_multipath uinput snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device ppdev snd_pcm_oss snd_mixer_oss snd_pcm snd_timer i2c_i801 snd_page_alloc snd_hwdep pcspkr i2c_core r8169 snd iTCO_wdt iTCO_vendor_support parport_pc mii soundcore parport pata_jmicron ata_generic pata_acpi ext4 jbd2 crc16 [last unloaded: microcode] Pid: 2009, comm: Xorg Not tainted 2.6.28.1-17.fc10.x86_64 #1 Call Trace: [<ffffffff810466b8>] warn_on_slowpath+0x60/0x8e [<ffffffff81030823>] ? change_page_attr_set_clr+0x136/0x304 [<ffffffff81354663>] ? printk+0x3c/0x41 [<ffffffff8102f880>] __ioremap_caller+0xc7/0x299 [<ffffffffa0462b61>] ? i915_gem_entervt_ioctl+0x472/0x507 [i915] [<ffffffff8102fb44>] ioremap_wc+0x1b/0x27 [<ffffffffa0462b61>] i915_gem_entervt_ioctl+0x472/0x507 [i915] [<ffffffffa042cd1d>] drm_ioctl+0x1d6/0x25e [drm] [<ffffffffa04626ef>] ? i915_gem_entervt_ioctl+0x0/0x507 [i915] [<ffffffff810d8321>] vfs_ioctl+0x5f/0x78 [<ffffffff810d86cc>] do_vfs_ioctl+0x392/0x3c0 [<ffffffff810cc437>] ? fsnotify_modify+0x62/0x6a [<ffffffff810d874f>] sys_ioctl+0x55/0x77 [<ffffffff8101106a>] system_call_fastpath+0x16/0x1b ---[ end trace 4de63c18a061741a ]--- r8169: eth0: link up r8169: eth0: link up eth0: no IPv6 routers present fuse init (API version 7.10) SELinux: initialized (dev fuse, type fuse), uses genfs_contexts JBD: barrier-based sync failed on dm-1:8 - disabling barriers
Oh my, now it happened also with vga=0x31b, so that had nothing to do with it was just luck that no freeze occurred. I triggered the bug by starting a java app, thunderbird and open office, but yesterday it froze when only firefox was running. When the frozen the machine seems to work in the background, because the hard drive is accessed from time to time, but does not react ony any key press, not even the magic sysrq that I enabled. I'm sorry that I can't provide more information. So far the same kernel runs fine on an older laptop with ati radeon 250, i686 arch Greetings Carsten
Can you try the 2.6.29-rc3 kernel from Koji?
Hi Chuck, I tried 2.6.29-0.6.rc3 yesterday and it froze after a few minutes. Only app running was Firefox. Thanks and greetings, Carsten
Today it froze with 2.6.29-0.6.rc3 and using the vesa driver. I don't get it. The following message could be related to it: Feb 2 17:44:46 m7 kernel: npviewer.bin[4435]: segfault at 58b24210 ip 0000003e8c22d59b sp 00007fff66a106a0 error 4 in l ibXt.so.6.0.0[3e8c200000+5e000] I'm back to 2.6.27.7-134 That's the only recent kernel where everything works for me right now.
2.6.29-rc4.git1 also froze after 2 hours today
Carsten, Could you add your full dmesg and /var/log/Xorg.0.log as uncompressed text/plain attachments to this bug report ? Thank you --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 332246 [details] output of dmesg output of dmesg
Created attachment 332247 [details] Xorg logfile
2.6.29-0.33.rc5 froze while using Firefox, keyboard and mouse were frozen, but mouse cursor animation was still alive. Is there anything I can do to help finding this bug, maybe a kernel with some debug options?
Today machine froze with 2.6.29.1-30.fc10 Maybe it's not Xorg but the kernel itself that freezes, because sysrq keys don't work and it froze also with the vesa driver and not only with the intel one. Might be another piece of hardware. So still using 2.6.27.21 for now. Hope 2.6.30 fixes this. Have a nice day, Carsten
Today 2.6.29.3-60.fc10.x86_64 froze while my son played a flash game. The music tune still played, everything else was frozen, even remote login via ssh did not work.
Carsten, are you seeing a consistent backtrace in the dmesg output? Have you run memtest? Are you saying that you never see any freezes with 2.6.27.21 ?
Yes, kernels prior to 2.6.28 work without any freezes. The last one I tried was 2.6.27.24. I upgraded to Fedora 11 tonight, but this morning the machine froze. There are no backtraces in dmesg, ssh login was impossible. Kernel was 2.6.29.3-159.fc11.x86_64. Can anyone provide rpms for 2.6.27.24 (stock 2.6.27 I can't use, because I use ext4) that work on Fedora 11? Everthing else (apart from kernel) works for me with Fedora 11. Maybe there's someone can provide a kernel version with lots of debugging output enabled, because I want to find the cause of the problem. Thanks to all the people that look into the problem Carsten
I'm running 2.6.30 (Fedora 11) now for 5 days straight. So far no freezes, looks like that nasty bug is gone eventually. If it runs for two weeks then i'm sure :) Thanks for this new great kernel
I'm closing this bug now, because 2.6.30 runs like a charm.
Reopening, this bug is tracking F10 and 2.6.27 is the latest kernel in updates/ for that release. Carsten, could you please file a bug against F11 stating which koji kernel build fixed the problem for you ? --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. 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 prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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. Thank you for reporting this bug and we are sorry it could not be fixed.