| Summary: | x11-drivers/xf86-video-intel-2.6.1: system crawls / graphics are flakey after the screen blanks | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Erik <erik.lat> |
| Component: | New packages | Assignee: | Gentoo X packagers <x11> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | gravydish, kolcon, rb6 |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Contains: lsmod, xorg.conf, drirc, and glxinfo
Xorg.log from a session slowed down by blanking startx log file when blanking occurs My Kernel config |
||
|
Description
Erik
2009-02-20 19:41:13 UTC
Created attachment 182685 [details]
Contains: lsmod, xorg.conf, drirc, and glxinfo
Lots of information in here.
Created attachment 182687 [details]
Xorg.log from a session slowed down by blanking
Created attachment 182690 [details]
startx log file when blanking occurs
This error only shows up after the screen has been blanked and is laggy. When a 'normal' X session is shutdown, this error is not there:
exaCopyDirty: Pending damage region empty!
Created attachment 182691 [details]
My Kernel config
I also see this occasionally in the dmesg log: resource map sanity check conflict: 0xd0000000 0xdfffffff 0xd0000000 0xd076ffff vesafb ------------[ cut here ]------------ WARNING: at arch/x86/mm/ioremap.c:226 __ioremap_caller+0xc8/0x2ca() Modules linked in: nls_iso8859_1 nls_cp437 vfat fat cpufreq_conservative cpufreq_powersave cpufreq_stats cpufreq_userspace acpi_cpufreq usbhid cryptoloop loop usbmouse fuse hp_wmi usb_storage rtc_cmos rtc_core rtc_lib arc4 ecb iwl3945 fan rfkill yenta_socket ohci1394 mac80211 rsrc_nonstatic tg3 ieee1394 ehci_hcd pcmcia_core thermal sg snd_hda_intel uhci_hcd libphy processor leds_hp_disk usbcore thermal_sys cfg80211 battery led_class hwmon button ac wmi container snd_hwdep Pid: 2537, comm: X Not tainted 2.6.28-tuxonice-r1 #13 Call Trace: [<ffffffff80233be5>] warn_on_slowpath+0x51/0x75 [<ffffffff802388c1>] iomem_map_sanity_check+0x75/0xac [<ffffffff802210bc>] __ioremap_caller+0xc8/0x2ca [<ffffffff803a0dff>] i915_gem_entervt_ioctl+0x43c/0x4c8 [<ffffffff803a0dff>] i915_gem_entervt_ioctl+0x43c/0x4c8 [<ffffffff803a09c3>] i915_gem_entervt_ioctl+0x0/0x4c8 [<ffffffff80392f3b>] drm_ioctl+0x1c9/0x253 [<ffffffff802976db>] vfs_ioctl+0x56/0x6c [<ffffffff80297a60>] do_vfs_ioctl+0x36f/0x39c [<ffffffff8028cf9c>] vfs_write+0x121/0x136 [<ffffffff80297aca>] sys_ioctl+0x3d/0x5c [<ffffffff8020b22b>] system_call_fastpath+0x16/0x1b ---[ end trace f4387ad851c1ff5d ]--- X:2537 conflicting memory types d0000000-e0000000 write-combining<->uncached-minus reserve_memtype failed 0xd0000000-0xe0000000, track write-combining, req write-combining X:2537 conflicting memory types d0000000-e0000000 write-combining<->uncached-minus reserve_memtype failed 0xd0000000-0xe0000000, track write-combining, req write-combining If you have any framebuffer drivers (vesafb, uvesafb or intelfb), please disable them: 1) they are known to be sources of many hard-to-track bugs, 2) newer versions of the linux kernel will provide KMS which will have a unified graphics driver for both X and the framebuffer console. Please try without any of those FB drivers. Thanks Please get back to us. Thanks The sanity check stuff appears to be fixed in 2.6.29 rc kernels. I have disabled the vesafb stuff in my kernel, and have not seen the issue since then. Once the 2.6.29 sources have the tuxonice patches added within them, I'll go ahead and attempt to upgrade. Thanks for the help, After disabling the vesafb kernel module I experienced this problem again. I left for lunch after locking the screen with xlock. When I came back and unlocked it, amarok was hiccuping and I saw this in dmesg: irq 16: nobody cared (try booting with the "irqpoll" option) Pid: 0, comm: swapper Not tainted 2.6.28-tuxonice-r1 #13 Call Trace: <IRQ> [<ffffffff80266d26>] __report_bad_irq+0x30/0x7d [<ffffffff80266e78>] note_interrupt+0x105/0x169 [<ffffffff802674cb>] handle_fasteoi_irq+0x93/0xb3 [<ffffffff8020db2b>] do_IRQ+0x72/0xdf [<ffffffff8020b736>] ret_from_intr+0x0/0xa <EOI> [<ffffffffa0157654>] acpi_idle_enter_simple+0x1c7/0x237 [processor] [<ffffffffa015764a>] acpi_idle_enter_simple+0x1bd/0x237 [processor] [<ffffffff8040be91>] cpuidle_idle_call+0x8b/0xca [<ffffffff8020a4d1>] cpu_idle+0x40/0x7c handlers: [<ffffffffa00b23ab>] (azx_interrupt+0x0/0x112 [snd_hda_intel]) [<ffffffffa01ad69e>] (yenta_interrupt+0x0/0xc1 [yenta_socket]) [<ffffffffa012aad3>] (usb_hcd_irq+0x0/0x64 [usbcore]) [<ffffffff8039d518>] (i915_driver_irq_handler+0x0/0x1e0) Disabling IRQ #16 hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. I'm going to try upgrading to the latest tuxonice source today and see if that fixes anything. Thanks, (skimmer:~) circut% cat /proc/interrupts
CPU0 CPU1
0: 7803098 7437015 IO-APIC-edge timer
1: 6702 6869 IO-APIC-edge i8042
8: 0 1 IO-APIC-edge rtc0
9: 2830 2948 IO-APIC-fasteoi acpi
12: 63424 63237 IO-APIC-edge i8042
14: 64116 62051 IO-APIC-edge ide0
16: 205326621 205673620 IO-APIC-fasteoi HDA Intel, yenta, uhci_hcd:usb1, i915@pci:0000:00:02.0
17: 84942 101097 IO-APIC-fasteoi ahci, uhci_hcd:usb3, ohci1394
18: 85434 85868 IO-APIC-fasteoi ehci_hcd:usb2, uhci_hcd:usb7, eth0
20: 14456 19346 IO-APIC-fasteoi ehci_hcd:usb4, uhci_hcd:usb5
21: 119963 119355 IO-APIC-fasteoi uhci_hcd:usb6
NMI: 0 0 Non-maskable interrupts
LOC: 7442721 7808617 Local timer interrupts
RES: 1120140 1045464 Rescheduling interrupts
CAL: 170 94 Function call interrupts
TLB: 10678 13290 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
SPU: 0 0 Spurious interrupts
ERR: 0
MIS: 0
Please also try with gentoo-sources or a vanilla kernel (the latest 2.6.29 RC should do). If you still have issues, please file a bug in FreeDesktop's bugzilla. If you do, please paste the url here so we can track the bug. Thanks I noticed this same problem on a Apple MacBook platform, gentoo-sources-2.6.28-r3, xf86-video-intel-2.6.3, libdrm-2.4.4 The problem can be catalyzed by logging out and back in (either with or without xdm), or by suspending and resuming. Removing uvesafb and v86d initramfs and console decorations from kernel and re-compiling and -installing did not fix it. Using vanilla-sources-2.6.28.8 fixed the problem. (In reply to comment #13) > Using vanilla-sources-2.6.28.8 fixed the problem. Thanks for the follow up. Indeed, one such bug was fixed upstream and the corresponding patch was included in 2.6.28.8 and in gentoo-sources-2.6.28-r4 on our side. Closing fixed. Thanks to all for your help. |
