Re: [Bug #12765] i915 VT switch with AIGLX causes X lock up
On Sun, Jun 07, 2009 at 12:06:18PM +0200, Rafael J. Wysocki wrote: > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12765 > Subject : i915 VT switch with AIGLX causes X lock up > Submitter : Sitsofe Wheeler > Date : 2009-02-21 15:38 (107 days old) > First-Bad-Commit: > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec > References: http://marc.info/?l=linux-kernel&m=123523074304955&w=4 > http://lkml.org/lkml/2009/4/27/317 > Handled-By: Jesse Barnes > Patch : http://patchwork.kernel.org/patch/20197/ Still here on 2.6.31-rc1 but... ...this seems to be tied to the version of the Intel X drivers I have. On another install with more recent Intel X drivers I cannot reproduce this issue. -- Sitsofe | http://sucs.org/~sits/ -- -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Bug #12765] i915 VT switch with AIGLX causes X lock up
On Sat, May 30, 2009 at 09:55:33PM +0200, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of regressions introduced between 2.6.28 and 2.6.29. > > The following bug entry is on the current list of known regressions > introduced between 2.6.28 and 2.6.29. Please verify if it still should > be listed and let me know (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12765 > Subject : i915 VT switch with AIGLX causes X lock up > Submitter : Sitsofe Wheeler > Date : 2009-02-21 15:38 (99 days old) > First-Bad-Commit: > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec > References: http://marc.info/?l=linux-kernel&m=123523074304955&w=4 > http://lkml.org/lkml/2009/4/27/317 > Handled-By: Jesse Barnes > Patch : http://patchwork.kernel.org/patch/20197/ Still here in 2.6.30-rc7-00149-g3218911. I have to admit that I thought commit 9b6fe313bfce27d4a261257da70196be0ac2bef5 might fix it but that doesn't appear to have been the case... -- Sitsofe | http://sucs.org/~sits/ -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Bug #12765] i915 VT switch with AIGLX causes X lock up
On Sun, May 24, 2009 at 09:31:15PM +0200, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of regressions introduced between 2.6.28 and 2.6.29. > > The following bug entry is on the current list of known regressions > introduced between 2.6.28 and 2.6.29. Please verify if it still should > be listed and let me know (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12765 > Subject : i915 VT switch with AIGLX causes X lock up > Submitter : Sitsofe Wheeler > Date : 2009-02-21 15:38 (93 days old) > First-Bad-Commit: > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec > References: http://marc.info/?l=linux-kernel&m=123523074304955&w=4 > http://lkml.org/lkml/2009/4/27/317 > Handled-By: Jesse Barnes > Patch : http://patchwork.kernel.org/patch/20197/ Yes this is still here in 2.6.30-rc7-00066-ge2a1b9e ... -- Sitsofe | http://sucs.org/~sits/ -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Bug #12765] i915 VT switch with AIGLX causes X lock up
On Sat, May 16, 2009 at 10:05:57PM +0200, Rafael J. Wysocki wrote: > The following bug entry is on the current list of known regressions > introduced between 2.6.28 and 2.6.29. Please verify if it still should > be listed and let me know (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12765 > Subject : i915 VT switch with AIGLX causes X lock up > Submitter : Sitsofe Wheeler > Date : 2009-02-21 15:38 (85 days old) > First-Bad-Commit: > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec > References: http://marc.info/?l=linux-kernel&m=123523074304955&w=4 > http://lkml.org/lkml/2009/4/27/317 > Handled-By: Jesse Barnes > Patch : http://patchwork.kernel.org/patch/20197/ Yes, this problem is still here in 2.6.30-rc6-00026-g0f6f49a . -- Sitsofe | http://sucs.org/~sits/ -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Bug #12765] i915 VT switch with AIGLX causes X lock up
On Mon, Apr 27, 2009 at 09:46:51AM -0700, Jesse Barnes wrote: > On Sun, 26 Apr 2009 11:46:26 +0200 (CEST) > "Rafael J. Wysocki" wrote: > > > This message has been generated automatically as a part of a report > > of regressions introduced between 2.6.28 and 2.6.29. > > > > The following bug entry is on the current list of known regressions > > introduced between 2.6.28 and 2.6.29. Please verify if it still > > should be listed and let me know (either way). The problem is still here in 2.6.29-rc3. > I think we had a workaround for this (attached), but it sounds like > Robert has tracked down the root cause (search for "Broken vblanks on > Intel" on dri-devel@lists.sourceforge.net). Will try to get the fix http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg39370.html seems to be it. > into the Intel driver soon. Fortunately this doesn't seem to be biting > a lot of people (at least not that I've heard); I certainly have a hard > time reproducing it. The patch that was attached to Jesse's mail seems to resolve the problem... -- Sitsofe | http://sucs.org/~sits/ -- Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: enabling kms for i915 disables brightness control and xrandr
(CC'ing dri-devel, Eric Anholt and Jesse Barnes) On Sun, Mar 29, 2009 at 12:34:01PM +0200, Soeren Sonnenburg wrote: > Dear all, > > I am not sure if this is just a user error/ too old userspace problem, [User stated that 2.6.3 intel driver is being used in another email] > but I recognized that when I enable kernel based modesetting on a intel > 945 based samsung nc 10 netbook, I loose brightness control from within > X and X resolutions are wrong (instead of 1024x600 it is 1024x1024) and > xrandr does no longer have the all the modelines ranging from 1024x600 > to 640x350... Trying to change resolutions / setting the brightness via > xrandr results in error messages being printed. > > Furthermore, this same flag disables Xv support.. > > However, screen switches between terminal and X are quite fast now > (without any flicker) and suspend and everything works stably. > > I recognized that I can set the brightness via > > setpci -s 00:02.1 F4.B=XX > > (XX ranging from 00 to FF) just fine... > > I am attaching the .config . > > Any ideas? > Soeren -- Sitsofe | http://sucs.org/~sits/ -- -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: 2.6.29-rc breaks STD using Intel 945
On Mon, Mar 16, 2009 at 02:02:56PM +0100, Frank Seidel wrote: > Sitsofe Wheeler wrote: > > Hmm. Does switching to and then back from a virtual terminal also break? > > I think i have the same problem and yes, switching to and back from vt > also breaks X. > I opened a bug here: https://bugzilla.novell.com/show_bug.cgi?id=485537 > > For me it currently helps to disable dri which makes my system stable > again. The reason I asked is because I am seeing a problem/regression with VT switching but only when AIGLX is on: http://marc.info/?l=linux-kernel&m=123523074304955&w=4 , http://marc.info/?l=dri-devel&m=123666881014615&w=4 and http://bugzilla.kernel.org/show_bug.cgi?id=12765 . The above may or may not be what Rolf is seeing (but if it is it would be good to know so they can all be collected together)... -- Sitsofe | http://sucs.org/~sits/ -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: 2.6.29-rc breaks STD using Intel 945
On Sun, Mar 08, 2009 at 07:02:17PM +0100, Rolf Eike Beer wrote: > Sitsofe Wheeler wrote: > > On Wed, Mar 04, 2009 at 08:20:56PM +0100, Rolf Eike Beer wrote: > > > I tested several snapshots post 2.6.28 and all of them show one severe > > > problem: resume from disk is not always successful. Only about 50% of the > > > resume attempts work, in the other cases I just get a completely black > > > screen, can't switch to text console or anything. What I often get is a > > > line like this in the logs directly before suspend: > > > > Does this happen when X hasn't been started and you suspend to disk then > > resume? > > I tested several times without X, with X running only in backgroud (i.e. me > initiating the suspend from console) and from xdm only. Never it froze. That > leads me to the conclusion that it is probably related to composite. I'm Hmm. Does switching to and then back from a virtual terminal also break? -- Sitsofe | http://sucs.org/~sits/ -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [REGRESSION,BISECTED] i915 VT switch with AIGLX causes X lock up
The problem is still here in 2.6.29-rc7. I got around to bisecting this and here's the commit that was fingered: commit 14d200c5e5bd19219d930bbb9a5a22758c8f5bec Author: Jesse Barnes Date: Fri Feb 6 13:04:49 2009 -0800 drm/i915: capture last_vblank count at IRQ uninstall time too In dc1336ff4fe08ae7cfe8301bfd7f0b2cfd31d20a (set vblank enable flag correctly across IRQ uninstall), we made sure drivers that uninstall their interrupt handler set the vblank enabled flag correctly, so that when interrupts are re-enabled, vblank interrupts & counts work as expected. However I missed the last_vblank field: it needs to be updated as well, otherwise, at the next drm_update_vblank_count we'll end up comparing a current count to a stale one (the last one captured by the disable function), which may trigger the wraparound handling, leading to a jumpy counter and hangs in drm_wait_vblank. The jumpy counter can prevent the DRM_WAIT_ON from returning success if the difference between the current count and the requested count is greater than 2^23, leading to timeouts or hangs, if the ioctl is restarted in a loop (as is the case in libdrm < 2.4.4). Signed-off-by: Jesse Barnes Acked-by: Michel Dänzer Tested-by: Timo Aaltonen Signed-off-by: Dave Airlie Reverting the above made the problem go away. Here's the bisect log: # bad: [d2f8d7ee1a9b4650b4e43325b321801264f7c37a] Linux 2.6.29-rc5 # good: [832fb4a01ca27ded735421de2b090f03e20039fc] Merge branch 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6 git bisect start 'v2.6.29-rc5' '832fb4a01ca27ded735421de2b090f03e20039fc' # good: [ac048e1734699dd98f4bdf4daf2b9592d4a4d38e] i915: fix unneeded locking in i915 LVDS get modes code. git bisect good ac048e1734699dd98f4bdf4daf2b9592d4a4d38e # good: [725e30ad6601d7fe443d9215d6331758a9d7e0c8] drm/i915: Skip SDVO/HDMI init when the chipset tells us it's not present. git bisect good 725e30ad6601d7fe443d9215d6331758a9d7e0c8 # bad: [d2f59357700487a8b944f4fd1e97cf5ea2ed] drm/i915: select framebuffer support automatically git bisect bad d2f59357700487a8b944f4fd1e97cf5ea2ed # good: [e2f0ba97d60e59fe5c6237851933a9c38a8f9a24] drm/i915: sync SDVO code with stable userland modesetting driver git bisect good e2f0ba97d60e59fe5c6237851933a9c38a8f9a24 # good: [7d8d58b23fd01e60ed44d8d8c10b2df86e638faa] drm/i915: Unlock mutex on i915_gem_fault() error path git bisect good 7d8d58b23fd01e60ed44d8d8c10b2df86e638faa # bad: [9880b7a527ffbb52f65c2de0a8d4eea86e24775e] drm/i915: add get_vblank_counter function for GM45 git bisect bad 9880b7a527ffbb52f65c2de0a8d4eea86e24775e # bad: [14d200c5e5bd19219d930bbb9a5a22758c8f5bec] drm/i915: capture last_vblank count at IRQ uninstall time too git bisect bad 14d200c5e5bd19219d930bbb9a5a22758c8f5bec -- Sitsofe | http://sucs.org/~sits/ -- -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: 2.6.29-rc breaks STD using Intel 945
On Wed, Mar 04, 2009 at 08:20:56PM +0100, Rolf Eike Beer wrote: > > I tested several snapshots post 2.6.28 and all of them show one severe > problem: resume from disk is not always successful. Only about 50% of the > resume attempts work, in the other cases I just get a completely black > screen, can't switch to text console or anything. What I often get is a line > like this in the logs directly before suspend: Does this happen when X hasn't been started and you suspend to disk then resume? -- Sitsofe | http://sucs.org/~sits/ -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [TIP,regression,i915] /dev/dri/card0 is no longer present
On Mon, Mar 02, 2009 at 11:05:58AM -0800, Pallipadi, Venkatesh wrote: > On Sun, 2009-03-01 at 05:48 -0800, Sitsofe Wheeler wrote: > > On Sun, Mar 01, 2009 at 12:39:48PM +0100, Ingo Molnar wrote: > > > > > > Thanks, i've reverted the commit for now. Could you please send > > > a 'dmesg' from the bootup with the failed driver? By all > > > likelyhood an ioremap failure causes a driver failure. > > > > > > > See below (drm says it initalized though...): > > > > [0.00] Linux version 2.6.29-rc6-6-g17581ad (@verona) (gcc > > version 4.2.4) #87 Sun Mar 1 13:42:28 GMT 2009 > > [0.00] KERNEL supported cpus: > > [0.00] Intel GenuineIntel > > [0.00] PAT WC disabled due to known CPU erratum. > > Looks like PAT is getting disabled on this platform. Can you send the > output of /proc/cpuinfo please. The machine has a stepping of the Celeron M chip in it with PAT errata. I think it becomes disabled because it would require a careful code to ensure that WC was only used in circumstances where the errata would not matter... Here's the contents of /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : Intel(R) Celeron(R) M processor 900MHz stepping: 8 cpu MHz : 900.074 cache size : 512 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx bts bogomips: 1800.14 clflush size: 64 power management: -- Sitsofe | http://sucs.org/~sits/ -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [TIP,regression,i915] /dev/dri/card0 is no longer present
On Sun, Mar 01, 2009 at 12:39:48PM +0100, Ingo Molnar wrote: > > Thanks, i've reverted the commit for now. Could you please send > a 'dmesg' from the bootup with the failed driver? By all > likelyhood an ioremap failure causes a driver failure. > See below (drm says it initalized though...): [0.00] Linux version 2.6.29-rc6-6-g17581ad (@verona) (gcc version 4.2.4) #87 Sun Mar 1 13:42:28 GMT 2009 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] PAT WC disabled due to known CPU erratum. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e4000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3f78 (usable) [0.00] BIOS-e820: 3f78 - 3f79 (ACPI data) [0.00] BIOS-e820: 3f79 - 3f7d (ACPI NVS) [0.00] BIOS-e820: 3f7d - 3f7de000 (reserved) [0.00] BIOS-e820: 3f7e - 3f80 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: fff8 - 0001 (reserved) [0.00] DMI present. [0.00] last_pfn = 0x3f780 max_arch_pfn = 0x10 [0.00] original variable MTRRs [0.00] reg 0, base: 0GB, range: 1GB, type WB [0.00] reg 1, base: 1016MB, range: 8MB, type UC [0.00] total RAM coverred: 1016M [0.00] Found optimal setting for mtrr clean up [0.00] gran_size: 64K chunk_size: 16M num_reg: 2 lose cover RAM: 0G [0.00] New variable MTRRs [0.00] reg 0, base: 0GB, range: 1GB, type WB [0.00] reg 1, base: 1016MB, range: 8MB, type UC [0.00] Scanning 1 areas for low memory corruption [0.00] modified physical RAM map: [0.00] modified: - 1000 (usable) [0.00] modified: 1000 - 0001 (reserved) [0.00] modified: 0001 - 00090c00 (usable) [0.00] modified: 0009fc00 - 000a (reserved) [0.00] modified: 000e4000 - 0010 (reserved) [0.00] modified: 0010 - 3f78 (usable) [0.00] modified: 3f78 - 3f79 (ACPI data) [0.00] modified: 3f79 - 3f7d (ACPI NVS) [0.00] modified: 3f7d - 3f7de000 (reserved) [0.00] modified: 3f7e - 3f80 (reserved) [0.00] modified: fee0 - fee01000 (reserved) [0.00] modified: fff8 - 0001 (reserved) [0.00] kernel direct mapping tables up to 377fe000 @ 1-15000 [0.00] RAMDISK: 37d91000 - 37fefdae [0.00] Allocated new RAMDISK: 00a04000 - 00c62dae [0.00] Move RAMDISK from 37d91000 - 37fefdad to 00a04000 - 00c62dad [0.00] ACPI: RSDP 000FBE60, 0014 (r0 ACPIAM) [0.00] ACPI: RSDT 3F78, 0034 (r1 A M I OEMRSDT 9000811 MSFT 97) [0.00] ACPI: FACP 3F780200, 0081 (r1 A M I OEMFACP 9000811 MSFT 97) [0.00] FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN (4) [0.00] ACPI: DSDT 3F780400, 6109 (r1 A0979 A0979034 34 INTL 20060113) [0.00] ACPI: FACS 3F79, 0040 [0.00] ACPI: APIC 3F780390, 0068 (r1 A M I OEMAPIC 9000811 MSFT 97) [0.00] ACPI: OEMB 3F790040, 0046 (r1 A M I AMI_OEM 9000811 MSFT 97) [0.00] ACPI: MCFG 3F786510, 003C (r1 A M I OEMMCFG 9000811 MSFT 97) [0.00] ACPI: Local APIC address 0xfee0 [0.00] 127MB HIGHMEM available. [0.00] 887MB LOWMEM available. [0.00] mapped low ram: 0 - 377fe000 [0.00] low ram: - 377fe000 [0.00] bootmap 00011000 - 00017f00 [0.00] (7 early reservations) ==> bootmem [00 - 00377fe000] [0.00] #0 [00 - 001000] BIOS data page ==> [00 - 001000] [0.00] #1 [10 - 9ff9d8]TEXT DATA BSS ==> [10 - 9ff9d8] [0.00] #2 [a0 - a04000]INIT_PG_TABLE ==> [a0 - a04000] [0.00] #3 [09fc00 - 10]BIOS reserved ==> [09fc00 - 10] [0.00] #4 [01 - 011000] PGTABLE ==> [01 - 011000] [0.00] #5 [a04000 - c62dae] NEW RAMDISK ==> [a04000 - c62dae] [0.00] #6 [011000 - 018000] BOOTMAP ==> [011000 - 018000] [0.00] Zone PFN ranges: [0.00] DMA 0x -> 0x1000 [0.00] Normal 0x1000 -> 0x000377fe [0.00] HighMem 0x000377f
[TIP,regression,i915] /dev/dri/card0 is no longer present
Hi, With the latest -tip /dev/dri/card0 is MIA on my EeePC 900. A bisection has tracked the probem down to the following commit: commit 17581ad812a9abb0182260374ef2e52d4a808a64 Author: Venkatesh Pallipadi Date: Tue Feb 24 17:35:14 2009 -0800 gpu/drm, x86, PAT: PAT support for io_mapping_* Make io_mapping_create_wc and io_mapping_free go through PAT to make sure that there are no memory type aliases. Signed-off-by: Venkatesh Pallipadi Signed-off-by: Suresh Siddha Cc: Dave Airlie Cc: Jesse Barnes Cc: Eric Anholt Cc: Keith Packard Signed-off-by: Ingo Molnar Reverting this made /dev/dri/card0 reappear. Here is the bisection log: git bisect start # bad: [f8dda9e8fdc2a2f736acabc416d65ee01abd533f] Merge branch 'kmemcheck' git bisect bad f8dda9e8fdc2a2f736acabc416d65ee01abd533f # good: [52ba0b69e339cf4edd314dd5819ef51bc4efee33] make drm headers use strict integer types git bisect good 52ba0b69e339cf4edd314dd5819ef51bc4efee33 # bad: [13093cb0e59053bf97910de3a24f07cdff71c62c] gpu/drm, x86, PAT: PAT support for io_mapping_*, export symbols for modules git bisect bad 13093cb0e59053bf97910de3a24f07cdff71c62c # good: [9af88143b277f52fc6ce0d69137f435c73c39c1a] iommu: fix Intel IOMMU write-buffer flushing git bisect good 9af88143b277f52fc6ce0d69137f435c73c39c1a # good: [13d428afc007fcfcd6deeb215618f54cf9c0cae6] Linux 2.6.28-rc6 git bisect good 13d428afc007fcfcd6deeb215618f54cf9c0cae6 # good: [d2f8d7ee1a9b4650b4e43325b321801264f7c37a] Linux 2.6.29-rc5 git bisect good d2f8d7ee1a9b4650b4e43325b321801264f7c37a # good: [e2e5a0f2b100a5204d27def8bbf7d1710be2] [S390] sclp: handle empty event buffers git bisect good e2e5a0f2b100a5204d27def8bbf7d1710be2 # good: [be71cb5b526709b8e42c707dc9e8c5b034ac8d1c] Merge branch 'x86-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip git bisect good be71cb5b526709b8e42c707dc9e8c5b034ac8d1c # good: [460c1338fc05add0e8050d4945a46f207b13a5fc] Merge branch 'x86-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip git bisect good 460c1338fc05add0e8050d4945a46f207b13a5fc # good: [770824bdc421ff58a64db608294323571c949f4c] PM: Split up sysdev_[suspend|resume] from device_power_[down|up] git bisect good 770824bdc421ff58a64db608294323571c949f4c # good: [8310509252c51e2a0e9effb50fefe7e098a67868] Merge branch 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6 git bisect good 8310509252c51e2a0e9effb50fefe7e098a67868 # good: [6644107d57a8fa82b47e4c55da4d9d91a612f29c] gpu/drm, x86, PAT: Handle io_mapping_create_wc() errors in a clean way git bisect good 6644107d57a8fa82b47e4c55da4d9d91a612f29c # bad: [17581ad812a9abb0182260374ef2e52d4a808a64] gpu/drm, x86, PAT: PAT support for io_mapping_* git bisect bad 17581ad812a9abb0182260374ef2e52d4a808a64 # good: [7880f7464546842ee14179bef16a6e14381ea638] gpu/drm, x86, PAT: routine to keep identity map in sync git bisect good 7880f7464546842ee14179bef16a6e14381ea638 Graphics card is an i915 in an EeePC 900: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) (i915 seems to be turning into a real battleground in 2.6.29 :) -- Sitsofe | http://sucs.org/~sits/ -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: i915 X lockup
On Fri, Feb 27, 2009 at 02:49:06PM +0100, Jiri Slaby wrote: > On 27.2.2009 14:04, Sitsofe Wheeler wrote: > >On Fri, Feb 27, 2009 at 02:32:31AM -0800, Andrew Morton wrote: > >>On Fri, 27 Feb 2009 10:28:51 +0100 Jiri Slaby wrote: > >> > >>>everytime I run X, it gets stuck. Currently running on mmotm > >>>2009-02-26-16-58, but I think this is wider problem. I had i915 disabled > >>>for a long time (until I noticed today). > > > >Which version of X are you using? Does it support kernel modesetting? If > >not, did you disable kernel modesetting in the KConfig file for i915? > > xorg-x11-server-7.4-17.3 > which is > X.Org X Server 1.5.2 > > modesetting enabled: > CONFIG_DRM_I915_KMS=y > > Which X version is needed for that? Good question. I can see that 7.4 supports GEM but I see nothing about kernel modesetting ( http://www.phoronix.com/scan.php?page=article&item=xorg_74_final&num=1). I know it's enabled in the Fedora (since Fedora 9) xorgs but I have no idea about openSUSE (which I believe is what you are using based on package numbers). Apparently kernel modesetting can be turned off on the kernel command line by using nomodesetting so that might be a quick thing to try... -- Sitsofe | http://sucs.org/~sits/ -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: i915 X lockup
On Fri, Feb 27, 2009 at 02:32:31AM -0800, Andrew Morton wrote: > On Fri, 27 Feb 2009 10:28:51 +0100 Jiri Slaby wrote: > > > everytime I run X, it gets stuck. Currently running on mmotm > > 2009-02-26-16-58, but I think this is wider problem. I had i915 disabled > > for a long time (until I noticed today). Which version of X are you using? Does it support kernel modesetting? If not, did you disable kernel modesetting in the KConfig file for i915? -- Sitsofe | http://sucs.org/~sits/ -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [REGRESSION] i915 VT switch with AIGLX causes X lock up
On Tue, Feb 24, 2009 at 08:44:09AM -0800, Jesse Barnes wrote: > Can you get a backtrace of the hung process, maybe by logging in from another > machine and using gdb on the Xorg process? (Done via sleep 30s; gdb.sh where gdb.sh contained the following: gdb -batch-silent \ -ex 'set logging overwrite on' \ -ex "set logging file /tmp/gdb.log" \ -ex 'set logging on' \ -ex 'handle SIG33 pass nostop noprint' \ -ex 'set pagination 0' \ -ex 'run' \ -ex 'backtrace full' \ -ex 'info registers' \ -ex 'thread apply all backtrace' \ -ex 'quit' \ -p `pidof X` < /dev/null < /dev/null Xorg never seems happy after the above finishes and always wedged itself after the script ran) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb7ccea30 (LWP 2972)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Program received signal SIGUSR1, User defined signal 1. [Switching to Thread 0xb7ccea30 (LWP 2972)] 0xb7fe8424 in __kernel_vsyscall () #0 0xb7fe8424 in __kernel_vsyscall () No symbol table info available. #1 0xb7e3984d in select () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #2 0x081b22e5 in WaitForSomething () No symbol table info available. #3 0x0808d69d in Dispatch () No symbol table info available. #4 0x0807471b in main () No symbol table info available. eax0xfdfe -514 ecx0x820a240136356416 edx0x0 0 ebx0x100256 esp0xbf902cc0 0xbf902cc0 ebp0xbf902f58 0xbf902f58 esi0x0 0 edi0xbf902f40 -1081069760 eip0xb7fe8424 0xb7fe8424 <__kernel_vsyscall+16> eflags 0x3246 [ PF ZF IF #12 #13 ] cs 0x73 115 ss 0x7b 123 ds 0x7b 123 es 0x7b 123 fs 0x0 0 gs 0x33 51 Thread 1 (Thread 0xb7ccea30 (LWP 2972)): #0 0xb7fe8424 in __kernel_vsyscall () #1 0xb7e3984d in select () from /lib/tls/i686/cmov/libc.so.6 #2 0x081b22e5 in WaitForSomething () #3 0x0808d69d in Dispatch () #4 0x0807471b in main () The program is running. Exit anyway? (y or n) [answered Y; input not from terminal] -- Sitsofe | http://sucs.org/~sits/ -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [REGRESSION] i915 VT switch with AIGLX causes X lock up
On Sat, Feb 21, 2009 at 03:38:22PM +, Sitsofe Wheeler wrote: > With 2.6.29rc5 and xorg-server 2:1.4.1~git20080131-1ubuntu9.2 switching > to a VT after starting compiz causes X to nearly lock up. > > Steps to reproduce: > 1. Start X > 2. Run compiz > 3. Switch to VT1 via ctrl-alt-f1 > 4. Switch back to X via ctrl-alt-f7 > > The result is that X will remain displaying a black screen from then on > (the mouse cursor is visible and still moves). Switching to a VT after > this locks up the keyboard. When compiz is not running this bug does not > occur. I am not using kernel mode setting and booting with nomodesetting > made no difference. This problem was not present in 2.6.28. The problem > is reproducible every time. > > Graphics card is an i915 in an EeePC 900: > > 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile > 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) > > This might be http://bugzilla.kernel.org/show_bug.cgi?id=12264 but I > can't reopen that bug and this bug might turn out to be different. Might > also be related to > http://marc.info/?l=linux-kernel&m=123499984611624&w=2 . Still here in 2.6.29-rc6. -- Sitsofe | http://sucs.org/~sits/ -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[i915] Reproducibly bad Z-buffer sorting
The Z-buffer on integrated cards often becomes confused which leads to surfaces that should be hidden appearing (and obstructing other surfaces). This problem seems to have been around since at least Mesa 6.4.2 and is still here in Mesa 7.0.3. A screenshot showing the problem can be found on https://bugzilla.novell.com/attachment.cgi?id=115354 . The problem is highly reproducible on openSUSE 10.3 and Ubuntu 8.04 . It is probably already reported as https://bugs.freedesktop.org/show_bug.cgi?id=9539 but https://bugzilla.novell.com/show_bug.cgi?id=239188#c17 suggested addressing it on the DRI mailing list. -- Sitsofe | http://sucs.org/~sits/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Kernel lockup when starting second X on MGA G200
Hello, As the subject mentions I seem to get a kernel lockup when starting a second X on a Matrox G200 card under Fedora Core 5. I have filed bugs with logs here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=193854 and here: https://bugs.freedesktop.org/show_bug.cgi?id=7173 In the RH bugzilla Mike Harris suggested that I should also cc the DRI folks just in case it was a kernel bug. -- Sitsofe | http://sucs.org/~sits/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
