[PATCH] drm: Restore the old_fb upon modeset failure
... or else we may end up disabling the wrong framebuffer, leading to an
OOPS, e.g:
[ 6033.229012] kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3271!
[ 6033.229012] invalid opcode: [#1] SMP
[ 6033.229012] last sysfs file:
/sys/devices/virtual/backlight/acpi_video0/uevent
[ 6033.229012] Modules linked in: sunrpc cpufreq_ondemand acpi_cpufreq
mperf snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_seq
snd_seq_device snd_pcm snd_timer thinkpad_acpi ppdev snd r852 sm_common
iTCO_wdt uvcvideo i2c_i801 iTCO_vendor_support microcode wmi nand
videodev nand_ids nand_ecc snd_page_alloc parport_pc parport mtd
soundcore joydev v4l1_compat pcspkr uinput ipv6 sdhci_pci sdhci mmc_core
yenta_socket i915 drm_kms_helper drm i2c_algo_bit i2c_core video output
[last unloaded: scsi_wait_scan]
[ 6033.229012]
[ 6033.229012] Pid: 4834, comm: Xorg Not tainted 2.6.37-rc8+ #25 7661BL5/7661BL5
[ 6033.229012] EIP: 0060:[] EFLAGS: 00013246 CPU: 0
[ 6033.229012] EIP is at i915_gem_object_unpin+0x23/0x76 [i915]
[ 6033.229012] EAX: f68a4000 EBX: f6831f00 ECX: 000600fa EDX: f68a8000
[ 6033.229012] ESI: f68a4014 EDI: f68a42b8 EBP: f2169c44 ESP: f2169c3c
[ 6033.229012] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 6033.229012] Process Xorg (pid: 4834, ti=f2168000 task=f21c8000
task.ti=f2168000)
[ 6033.229012] Stack:
[ 6033.229012] f3a84800 f68a4014 f2169c54 f87045d8 f3a84800 f872d9a8 f2169c68
f7fd8091
[ 6033.229012] f3b952a4 f68a414c f2169cf0 f7fd9377
f7fd98b0
[ 6033.229012] f7fd9f4e 000f f7f328a0 f2169ca4
f68a414c
[ 6033.229012] Call Trace:
[ 6033.229012] [] ? intel_crtc_disable+0x36/0x41 [i915]
[ 6033.229012] [] ? drm_helper_disable_unused_functions+0xcd/0xf9
[drm_kms_helper]
[ 6033.229012] [] ? drm_crtc_helper_set_config+0x62a/0x7f7
[drm_kms_helper]
[ 6033.229012] [] ? __slab_free+0x1b/0xa4
[ 6033.229012] [] ? drm_fb_helper_initial_config+0x466/0x497
[drm_kms_helper]
[ 6033.229012] [] ? drm_fb_helper_restore+0x10/0x2a [drm_kms_helper]
[ 6033.229012] [] ? i915_driver_lastclose+0x2a/0x57 [i915]
[ 6033.229012] [] ? drm_lastclose+0x45/0x23e [drm]
[ 6033.229012] [] ? drm_release+0x462/0x4d7 [drm]
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/drm_crtc_helper.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/drm_crtc_helper.c
b/drivers/gpu/drm/drm_crtc_helper.c
index 8de333a..952b3d4 100644
--- a/drivers/gpu/drm/drm_crtc_helper.c
+++ b/drivers/gpu/drm/drm_crtc_helper.c
@@ -661,6 +661,7 @@ int drm_crtc_helper_set_config(struct drm_mode_set *set)
old_fb)) {
DRM_ERROR("failed to set mode on [CRTC:%d]\n",
set->crtc->base.id);
+ set->crtc->fb = old_fb;
ret = -EINVAL;
goto fail;
}
@@ -675,8 +676,10 @@ int drm_crtc_helper_set_config(struct drm_mode_set *set)
set->crtc->fb = set->fb;
ret = crtc_funcs->mode_set_base(set->crtc,
set->x, set->y, old_fb);
- if (ret != 0)
+ if (ret != 0) {
+ set->crtc->fb = old_fb;
goto fail;
+ }
}
DRM_DEBUG_KMS("Setting connector DPMS state to on\n");
for (i = 0; i < set->num_connectors; i++) {
--
1.7.2.3
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 --- Comment #21 from Daniel 2011-01-19 12:16:34 --- My results after tests since yesterday: - patch in #8 + first patch in #10: ok - patch in #8 + second patch in #10: ok - patch in #8 + third patch in #10: flickering For today i would test patch in comment #20. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 03/17][trivial] GPU DRM: Remove unnecessary casts of void ptr returning alloc function return values
On Tue, 9 Nov 2010, Jesper Juhl wrote:
> Hi,
>
> The [vk][cmz]alloc(_node) family of functions return void pointers which
> it's completely unnecessary/pointless to cast to other pointer types since
> that happens implicitly.
>
> This patch removes such casts from drivers/gpu/drm/
>
>
> Signed-off-by: Jesper Juhl
> ---
> drm_sman.c |4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_sman.c b/drivers/gpu/drm/drm_sman.c
> index 463aed9..3466458 100644
> --- a/drivers/gpu/drm/drm_sman.c
> +++ b/drivers/gpu/drm/drm_sman.c
> @@ -59,9 +59,7 @@ drm_sman_init(struct drm_sman * sman, unsigned int
> num_managers,
> {
> int ret = 0;
>
> - sman->mm = (struct drm_sman_mm *) kcalloc(num_managers,
> - sizeof(*sman->mm),
> - GFP_KERNEL);
> + sman->mm = kcalloc(num_managers, sizeof(*sman->mm), GFP_KERNEL);
> if (!sman->mm) {
> ret = -ENOMEM;
> goto out;
>
Doesn't seem to be present in linux-next as of today, applied to trivial
queue.
Thanks,
--
Jiri Kosina
SUSE Labs, Novell Inc.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33272] New: Kernel DRM/Radeon KMS BSOD on HD6850-NI
https://bugs.freedesktop.org/show_bug.cgi?id=33272 Summary: Kernel DRM/Radeon KMS BSOD on HD6850-NI Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: spamjunkea...@gmail.com Using 2.6.38-rc1 vanilla, When I try to load radeon kernel module with modprobe radeon modeset=1 I got BSOD, computer doesn't give any response to me. CTRL+ALT+DEL don't working nor my main computer switch. modprobe radeon modeset=0 doesn't make such problem and computer looks working. But my Northern Islands (HD6850) card doesn't support Gallium3D without KMS. Thanks. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33272] Kernel DRM/Radeon KMS BSOD on HD6850-NI
https://bugs.freedesktop.org/show_bug.cgi?id=33272 --- Comment #1 from Alex Deucher 2011-01-19 07:42:20 PST --- Have you installed the necessary ucode for your card? http://people.freedesktop.org/~agd5f/radeon_ucode/ BARTS_mc.bin BARTS_me.bin BARTS_pfp.bin BTC_rlc.bin -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
drm:i915_report_and_clear_eir -- *ERROR* EIR stuck: 0x00000010, masking
Hi, I am getting this during boot with current Linus' tree on x200s thinkpad: [8.312007] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x0010, masking head -39 /sys/kernel/debug/dri/64/i915_error_state shows: Time: 1295452835 s 347238 us PCI ID: 0x2a42 EIR: 0x0010 PGTBL_ER: 0x0001 Render command stream: ACTHD: 0x00534024 IPEIR: 0x IPEHR: 0x0200 INSTDONE: 0x INSTDONE1: 0xbfbb INSTPS: 0x8001e025 INSTPM: 0x seqno: 0x fence[0] = fence[1] = fence[2] = fence[3] = fence[4] = fence[5] = fence[6] = fence[7] = fence[8] = fence[9] = fence[10] = fence[11] = fence[12] = fence[13] = fence[14] = fence[15] = Active [3]: 0053400016384 0009 0001 dirty render uncached 00042000 5185536 0043 0001 P render uncached (name: 1) 00538000 20971520 0002 0002 P X dirty render uncached Pinned [4]: 4096 0001 0001 P snooped 1000 131072 0001 0001 P uncached 00021000 4096 0001 0001 P snooped 00022000 131072 0001 0001 P uncached Apart from the error in the kernel buffer, graphics seems to work normally. -- Jiri Kosina SUSE Labs, Novell Inc. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33255] Crash using webgl (firefox 4b9)
https://bugs.freedesktop.org/show_bug.cgi?id=33255 --- Comment #1 from Marek Olšák 2011-01-19 08:43:09 PST --- (In reply to comment #0) > *WARN_ONCE* > File r300_state.c function r300SetupRSUnit line 1521 > Don't know how to satisfy InputsRead=0x4000 > *** This message is from the classic driver. Are you sure you're really running the Gallium one? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] drm: Restore the old_fb upon modeset failure
Never mind, you caught this one on your last sweep. Thanks, -Chris -- Chris Wilson, Intel Open Source Technology Centre ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33255] Crash using webgl (firefox 4b9)
https://bugs.freedesktop.org/show_bug.cgi?id=33255 --- Comment #2 from 0enjolr...@laposte.net 2011-01-19 09:17:56 PST --- Created an attachment (id=42200) --> (https://bugs.freedesktop.org/attachment.cgi?id=42200) Intresting parts from Dmesg -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33255] Crash using webgl (firefox 4b9)
https://bugs.freedesktop.org/show_bug.cgi?id=33255 --- Comment #3 from 0enjolr...@laposte.net 2011-01-19 09:18:45 PST --- Created an attachment (id=42201) --> (https://bugs.freedesktop.org/attachment.cgi?id=42201) Log Xorg -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33255] Crash using webgl (firefox 4b9)
https://bugs.freedesktop.org/show_bug.cgi?id=33255 --- Comment #4 from 0enjolr...@laposte.net 2011-01-19 09:20:55 PST --- Hy I think i do, because i can see this in glxinfo : OpenGL vendor string: X.Org R300 Project OpenGL renderer string: Gallium 0.4 on RS690 But i apologize I can't do better. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33276] "invalid enumerant" during: Cubemap ID generation
https://bugs.freedesktop.org/show_bug.cgi?id=33276 Alex Deucher changed: What|Removed |Added Product|xorg|Mesa Version|7.5 |unspecified Component|Driver/Radeon |Drivers/DRI/r300 AssignedTo|xorg-driver-...@lists.x.org |dri-devel@lists.freedesktop ||.org QAContact|xorg-t...@lists.x.org | --- Comment #1 from Alex Deucher 2011-01-19 09:50:21 PST --- Are you using the r300 classic or r300 gallium 3D driver? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33276] "invalid enumerant" during: Cubemap ID generation
https://bugs.freedesktop.org/show_bug.cgi?id=33276 --- Comment #2 from Alexander Konotop 2011-01-19 10:18:29 PST --- (In reply to comment #1) > Are you using the r300 classic or r300 gallium 3D driver? $ glxinfo | grep OpenGL OpenGL vendor string: DRI R300 Project OpenGL renderer string: Mesa DRI R300 (RS400 5975) 20090101 NO-TCL DRI2 OpenGL version string: 1.5 Mesa 7.7.1 OpenGL extensions: $ glxinfo | Gallium outputs nothing -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33276] "invalid enumerant" during: Cubemap ID generation
https://bugs.freedesktop.org/show_bug.cgi?id=33276 --- Comment #3 from Alexander Konotop 2011-01-19 10:20:24 PST --- (In reply to comment #2) > (In reply to comment #1) > > Are you using the r300 classic or r300 gallium 3D driver? > > $ glxinfo | grep OpenGL > OpenGL vendor string: DRI R300 Project > OpenGL renderer string: Mesa DRI R300 (RS400 5975) 20090101 NO-TCL DRI2 > OpenGL version string: 1.5 Mesa 7.7.1 > OpenGL extensions: > > $ glxinfo | Gallium outputs nothing sorry, $ glxinfo | grep Gallium, not $ glxinfo | Gallium -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33276] "invalid enumerant" during: Cubemap ID generation
https://bugs.freedesktop.org/show_bug.cgi?id=33276 --- Comment #4 from Alex Deucher 2011-01-19 10:25:08 PST --- You are using the classic driver. You might want to try the r300 gallium driver. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33276] "invalid enumerant" during: Cubemap ID generation
https://bugs.freedesktop.org/show_bug.cgi?id=33276 --- Comment #5 from Alexander Konotop 2011-01-19 10:31:15 PST --- (In reply to comment #4) > You are using the classic driver. You might want to try the r300 gallium > driver. Ok, thank's. But debian doesn't have gallium driver in a repository, I have to build it myself. Will it be useful for you if I try? If not - I'll try later and maybe never ), if yes - I'll try soon. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33276] "invalid enumerant" during: Cubemap ID generation
https://bugs.freedesktop.org/show_bug.cgi?id=33276 --- Comment #6 from Alexander Konotop 2011-01-19 10:55:40 PST --- (In reply to comment #5) > (In reply to comment #4) > > You are using the classic driver. You might want to try the r300 gallium > > driver. > Ok, thank's. But debian doesn't have gallium driver in a repository, I have to > build it myself. Will it be useful for you if I try? If not - I'll try later > and maybe never ), if yes - I'll try soon. Oh, it's much simplier than I thought! I've just added 2 repositories: from here https://launchpad.net/~xorg-edgers/+archive/drivers-only and from here https://launchpad.net/~xorg-edgers/+archive/radeon They're for ubuntu lucid but work great on debian sid too. Very fast and vdrift now starts. I think you have to close this report now. Anyone who has similar problems just has to use gallium driver. It works, I've tested. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 27314] DP link training fails on 2560x1440 panels
https://bugs.freedesktop.org/show_bug.cgi?id=27314 --- Comment #28 from Travis Glenn Hansen 2011-01-19 11:24:20 PST --- Been out on vacation. Is it still necessary to test the latest patch? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33276] "invalid enumerant" during: Cubemap ID generation
https://bugs.freedesktop.org/show_bug.cgi?id=33276 Alex Deucher changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Comment #7 from Alex Deucher 2011-01-19 12:06:24 PST --- Use the gallium driver. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 27314] DP link training fails on 2560x1440 panels
https://bugs.freedesktop.org/show_bug.cgi?id=27314 --- Comment #29 from Alex Deucher 2011-01-19 12:07:25 PST --- (In reply to comment #28) > Been out on vacation. Is it still necessary to test the latest patch? Worth a shot. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33272] Kernel DRM/Radeon KMS BSOD on HD6850-NI
https://bugs.freedesktop.org/show_bug.cgi?id=33272 --- Comment #2 from Erdem U. Altinyurt 2011-01-19 12:25:42 PST --- definitely, right to /lib/modules/radeon directory. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33272] Kernel DRM/Radeon KMS BSOD on HD6850-NI
https://bugs.freedesktop.org/show_bug.cgi?id=33272 --- Comment #3 from Alex Deucher 2011-01-19 12:56:08 PST --- If you are using an initrd make sure the ucode is built into the initrd. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 --- Comment #22 from Daniel 2011-01-19 21:14:55 --- After running with patch of comment #20 for 6 hours and no flickering, i suddenly got a black screen after watching a video for some minutes. Switching to tty1 and back to tty7 (xorg) the problem was gone for one minute and i got a black screen again. I watched the video again, but the problem was not reproducible. For now i rebooted and will try to verifying it again. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31046] [r600g, tiling] visual errors and GPU resets
https://bugs.freedesktop.org/show_bug.cgi?id=31046 Tobias Jakobi changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | --- Comment #9 from Tobias Jakobi 2011-01-19 14:12:45 PST --- After doing some thorough testing today with ut2004 I noticed that mipmaps are still affected when having R600_FORCE_TILING enabled. Going to take some screenshots later. I didn't encounter any GPU resets though, so it's just rendering errors and it seems to be limited to mipmaps. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 --- Comment #23 from Daniel 2011-01-19 22:28:21 --- Oh, while some reboots one time it begins flickering directly after kms switching on console. I think patch of #20 is not stable for me. What can i do/test now? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 --- Comment #24 from Alex Deucher 2011-01-19 22:30:11 --- (In reply to comment #23) > Oh, while some reboots one time it begins flickering directly after kms > switching on console. I think patch of #20 is not stable for me. What can i > do/test now? Can you test the mini patches from comment 10 in combination with the patch from comment 20? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33172] [r600g] ingame rendering broken (black screen) in ut2003
https://bugs.freedesktop.org/show_bug.cgi?id=33172 --- Comment #2 from Tobias Jakobi 2011-01-19 14:35:02 PST --- We (Jan and me) did some tests today and found out that the issue is probably related to the use of VBOs (or more specifically: not using them). In ut2004 there is a option called 'UseVBO' for the OpenGL renderer. I guess enabling this one lets the engine use the 'ARB_vertex_buffer_object' extension. It turned out that in my ut2004 config it was enabled, but Jan had it disabled. So after enabling it for Jan the rendering suddenly worked. And when I disabled UseVBO on my system it suddenly failed and produced the black screen, plus the relocation parser errors in the kernel log. I can only guess here, but maybe the problem is with Gallium's immediate mode implementation -- if that's how the engine submits vertices when ARB_vbo is not used. The next thing we found out is even more interesting: In ut2003 there is no such option, so he had to stick to the 'immediate mode' rendering path. All the tests were done on Jan's system. We noticed that is was possible to get ingame when being logged in as root. This only worked for a short time, maybe like 10 seconds, before the game segfaulted. After it segfaulted, it wasn't possible any more to get ingame. The game just instantly segfaulted. Restarting X didn't help, only a full reboot did the trick. Another thing that worked: Reboot, start ut03 as root, watch some game scenary for like 3 seconds, quickly exit the game, start ut03 as root, repear procedure... The maximum amount of time we managed to get into game was three. After that it didn't work any more. It was like we hit some memory leak, maybe in VRAM? Then we switched over to ut2004 and disabled UseVBO there. We got the black screen (with the kernel messages) when we got ingame and then we waited a bit. But just like ut03 the game segfaulted after some seconds and we even managed it at one time to trigger the kernel OOM killer. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33262] [r600g] glean glsl1-shadow2D(): [1-4] regression
https://bugs.freedesktop.org/show_bug.cgi?id=33262 Christian König changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #2 from Christian König 2011-01-19 14:59:57 PST --- Fixed with commit a124490262a29d2e873fe50ca57974f246946b85 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33272] Kernel DRM/Radeon KMS BSOD on HD6850-NI
https://bugs.freedesktop.org/show_bug.cgi?id=33272 --- Comment #4 from Erdem U. Altinyurt 2011-01-19 15:31:09 PST --- I don't create initrd by hand. Used make install to install code and initrd doesn't have any radeon modules.So initrd doesn't have ucode. But I thought that is just for boot with radeon module loading. I don't use that feature. AFAIK Since I do not load radeon module on bootup, It's doesn't necessary to have those files in initrd and load from /lib/firmware/radeon/ directly. Does it requirement that having ucodes in initrd for running NI class cards? My internal 790GX GPU could woth with KMS without any ucode and modules in initrd. (At least with 2.6.37, I don't test it with 2.6.38-rc1 and 790GX disabled from bios since HD6850 plugged in). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33272] Kernel DRM/Radeon KMS BSOD on HD6850-NI
https://bugs.freedesktop.org/show_bug.cgi?id=33272 --- Comment #5 from Erdem U. Altinyurt 2011-01-19 16:09:56 PST --- Now tested my old 790GX and it's working with my setup but NI. Removed BARTS_mc.bin BARTS_me.bin BARTS_pfp.bin BTC_rlc.bin files from /lib/firmware/radeon. I expect that will make radeon.ko cannot found required ucodes and will not activate KMS and loaded as modeset=0. AFAIK That happens when I don't put required ucodes to fw directort with my 790GX when initial r600 support comes... So, when I try to load radeon without those ucodes on firmware directoy, result is same. BSOD. That make me thinking if it's not related with ucodes... Thanks -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33272] Kernel DRM/Radeon KMS BSOD on HD6850-NI
https://bugs.freedesktop.org/show_bug.cgi?id=33272 --- Comment #6 from Alex Deucher 2011-01-19 16:24:55 PST --- The ucode is required for all asics when the radeon drm is loaded. Most likley your initrd already has the ucode for older asics. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33262] [r600g] glean glsl1-shadow2D(): [1-4] regression
https://bugs.freedesktop.org/show_bug.cgi?id=33262 Vinson Lee changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #3 from Vinson Lee 2011-01-19 16:56:41 PST --- mesa: a124490262a29d2e873fe50ca57974f246946b85 (master) Verified fixed. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26942] radeon: screen distortion on resume
https://bugzilla.kernel.org/show_bug.cgi?id=26942 Rafael J. Wysocki changed: What|Removed |Added CC||flor...@mickler.org, ||maciej.rute...@gmail.com, ||r...@sisk.pl Blocks||21782, 7216 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 3/5] radeon: Expose backlight class device for legacy LVDS encoder
On Fri, 14 Jan 2011 14:24:23 -0500 Matthew Garrett wrote: > From: Michel D__nzer > > Allows e.g. power management daemons to control the backlight level. Inspired > by the corresponding code in radeonfb. > > (Updated to add backlight type and make the connector the parent device - mjg) > x86_64 allmodconfig: drivers/gpu/drm/radeon/radeon_legacy_encoders.c: In function 'radeon_legacy_lvds_update': drivers/gpu/drm/radeon/radeon_legacy_encoders.c:64: error: 'struct radeon_encoder_atom_dig' has no member named 'bl_dev' drivers/gpu/drm/radeon/radeon_legacy_encoders.c:65: error: 'struct radeon_encoder_atom_dig' has no member named 'backlight_level' drivers/gpu/drm/radeon/radeon_legacy_encoders.c:69: error: 'struct radeon_encoder_lvds' has no member named 'bl_dev' drivers/gpu/drm/radeon/radeon_legacy_encoders.c:70: error: 'struct radeon_encoder_lvds' has no member named 'backlight_level' drivers/gpu/drm/radeon/radeon_legacy_encoders.c: In function 'radeon_legacy_lvds_dpms': drivers/gpu/drm/radeon/radeon_legacy_encoders.c:144: error: 'struct radeon_encoder_atom_dig' has no member named 'dpms_mode' drivers/gpu/drm/radeon/radeon_legacy_encoders.c:147: error: 'struct radeon_encoder_lvds' has no member named 'dpms_mode' ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
more intel drm issues (was Re: [git pull] drm intel only fixes)
Ok, so I have a new issue that I'm currently bisecting but that people may be able to figure out even befor emy bisect finishes. On my slow Atom netbook (that I'm planning on using as my traveling companion for LCA), suspend-to-RAM takes a long time with current git. It's quite noticeable - it used to be pretty much instant, now it takes three seconds. And it's all i915 graphics (although I haven't bisected it down fully, I've bisected it down to the drm merge). In the good case (like plain 2.6.37), a suspend event will look something like this: ... PM: suspend of devices complete after 147.646 msecs ... but the i915 driver at some point made it take 3s: ... PM: suspend of devices complete after 3059.656 msecs ... which is definitely long enough to be worth fixing. Maybe the person responsible will go "oh, that's obviously due to xyz", and just fix it. But I'll continue to bisect in case nobody steps up to admit to wasting time.. Linus ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33139] Radeon HD 5750 locks up when using 3D apps with r600g
https://bugs.freedesktop.org/show_bug.cgi?id=33139 --- Comment #3 from Rubén Fernández 2011-01-19 19:44:35 PST --- I also experience GPU lockups with about half the games I've tried in an HD5750 (all of which work in an older r300g card) In my case, in all but one I can still do SSH (even with latest mesa), so I'll try to post debugging information here. GPU: ATI Technologies Inc Juniper HDMI Audio [Radeon HD 5700 Series] Kernel: 2.6.38 libdrm-2.4.23 xf86-video-ati git 57fbddfc21d8c6794f378489b764cc2a0ad4a48c Mesa git 3ee60a3558a3546b3c3a0a9732d384afcf02994a X.Org X Server 1.9.0 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31870] [evergreen] Graphics freezes when selecting Atlantis from XScreenSaver
https://bugs.freedesktop.org/show_bug.cgi?id=31870 --- Comment #2 from Rubén Fernández 2011-01-19 19:52:07 PST --- I have the exact same bug in an HD5750; it also used to freeze specifically with atlantis, and now randomly GPU: ATI Technologies Inc Juniper HDMI Audio [Radeon HD 5700 Series] Kernel: 2.6.38 libdrm-2.4.23 xf86-video-ati git 57fbddfc21d8c6794f378489b764cc2a0ad4a48c Mesa git 3ee60a3558a3546b3c3a0a9732d384afcf02994a X.Org X Server 1.9.0 XScreenSaver 5.12 To reproduce: 1) Run xscreensaver-demo 2) Do a preview of opengl screensavers several times Eventually, you'll get to some screensaver that runs fine, but, after closing it, some second later, the cursor freezes. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: more intel drm issues (was Re: [git pull] drm intel only fixes)
On Wed, Jan 19, 2011 at 8:55 PM, Jeff Chua wrote:
>
> Rafael send out two patches earlier. Could be related. I was facing
> issue during resume.
No, I'm aware of the rcu-synchronize thing, this isn't it. This is
really at the suspend stage, and I had bisected it down to the drm
changes.
In fact, by now I have bisected it down to a single commit. It's
another merge commit, which makes me a bit nervous (I bisected another
issue today, and it turned out to simply not be repeatable).
But this time the merge commit actually has a real conflict that got
fixed up in the merge, and the code around the conflict waits for
three seconds, and three seconds is also exactly how long the delay at
suspend time is. So I get the feeling that this time it's a real
issue, and what happened was that the merge may have been a mismerge.
Chris: as of commit 8d5203ca6253 ("Merge branch 'drm-intel-fixes' into
drm-intel-next") I'm getting that 3-second delay at suspend time. And
the merge diff looks like this:
+ struct drm_device *dev = ring->dev;
+ struct drm_i915_private *dev_priv = dev->dev_private;
unsigned long end;
- drm_i915_private_t *dev_priv = dev->dev_private;
u32 head;
- head = intel_read_status_page(ring, 4);
- if (head) {
- ring->head = head & HEAD_ADDR;
- ring->space = ring->head - (ring->tail + 8);
- if (ring->space < 0)
- ring->space += ring->size;
- if (ring->space >= n)
- return 0;
- }
-
trace_i915_ring_wait_begin (dev);
end = jiffies + 3 * HZ;
do {
and that whole do-loop with a 3-second timeout makes me *very*
suspicious. It used to have (in _one_ of the parent branches) that
code before it to return early if there was space in the ring, now it
doesn't any more - and that merge co-incides with my suspend suddenly
taking 3 seconds.
The same check that is deleted does exist inside the loop too, but
there it has some extra code it in (compare to "actual_head" and so
on), so I wonder if the fast-case was somehow hiding this issue.
But I don't know the code. I just see that whole "PM: suspend of
devices complete after x.xxx msecs" issue, and I can see the machine
taking too long to suspend.
Linus
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 --- Comment #20 from Alex Deucher 2011-01-19 06:58:03 --- Created an attachment (id=44142) --> (https://bugzilla.kernel.org/attachment.cgi?id=44142) another patch to try Can you also test this patch on top of the patch in comment 8? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[PATCH] drm: Restore the old_fb upon modeset failure
... or else we may end up disabling the wrong framebuffer, leading to an
OOPS, e.g:
[ 6033.229012] kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3271!
[ 6033.229012] invalid opcode: [#1] SMP
[ 6033.229012] last sysfs file:
/sys/devices/virtual/backlight/acpi_video0/uevent
[ 6033.229012] Modules linked in: sunrpc cpufreq_ondemand acpi_cpufreq
mperf snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_seq
snd_seq_device snd_pcm snd_timer thinkpad_acpi ppdev snd r852 sm_common
iTCO_wdt uvcvideo i2c_i801 iTCO_vendor_support microcode wmi nand
videodev nand_ids nand_ecc snd_page_alloc parport_pc parport mtd
soundcore joydev v4l1_compat pcspkr uinput ipv6 sdhci_pci sdhci mmc_core
yenta_socket i915 drm_kms_helper drm i2c_algo_bit i2c_core video output
[last unloaded: scsi_wait_scan]
[ 6033.229012]
[ 6033.229012] Pid: 4834, comm: Xorg Not tainted 2.6.37-rc8+ #25 7661BL5/7661BL5
[ 6033.229012] EIP: 0060:[] EFLAGS: 00013246 CPU: 0
[ 6033.229012] EIP is at i915_gem_object_unpin+0x23/0x76 [i915]
[ 6033.229012] EAX: f68a4000 EBX: f6831f00 ECX: 000600fa EDX: f68a8000
[ 6033.229012] ESI: f68a4014 EDI: f68a42b8 EBP: f2169c44 ESP: f2169c3c
[ 6033.229012] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 6033.229012] Process Xorg (pid: 4834, ti=f2168000 task=f21c8000
task.ti=f2168000)
[ 6033.229012] Stack:
[ 6033.229012] f3a84800 f68a4014 f2169c54 f87045d8 f3a84800 f872d9a8 f2169c68
f7fd8091
[ 6033.229012] f3b952a4 f68a414c f2169cf0 f7fd9377
f7fd98b0
[ 6033.229012] f7fd9f4e 000f f7f328a0 f2169ca4
f68a414c
[ 6033.229012] Call Trace:
[ 6033.229012] [] ? intel_crtc_disable+0x36/0x41 [i915]
[ 6033.229012] [] ? drm_helper_disable_unused_functions+0xcd/0xf9
[drm_kms_helper]
[ 6033.229012] [] ? drm_crtc_helper_set_config+0x62a/0x7f7
[drm_kms_helper]
[ 6033.229012] [] ? __slab_free+0x1b/0xa4
[ 6033.229012] [] ? drm_fb_helper_initial_config+0x466/0x497
[drm_kms_helper]
[ 6033.229012] [] ? drm_fb_helper_restore+0x10/0x2a [drm_kms_helper]
[ 6033.229012] [] ? i915_driver_lastclose+0x2a/0x57 [i915]
[ 6033.229012] [] ? drm_lastclose+0x45/0x23e [drm]
[ 6033.229012] [] ? drm_release+0x462/0x4d7 [drm]
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/drm_crtc_helper.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/drm_crtc_helper.c
b/drivers/gpu/drm/drm_crtc_helper.c
index 8de333a..952b3d4 100644
--- a/drivers/gpu/drm/drm_crtc_helper.c
+++ b/drivers/gpu/drm/drm_crtc_helper.c
@@ -661,6 +661,7 @@ int drm_crtc_helper_set_config(struct drm_mode_set *set)
old_fb)) {
DRM_ERROR("failed to set mode on [CRTC:%d]\n",
set->crtc->base.id);
+ set->crtc->fb = old_fb;
ret = -EINVAL;
goto fail;
}
@@ -675,8 +676,10 @@ int drm_crtc_helper_set_config(struct drm_mode_set *set)
set->crtc->fb = set->fb;
ret = crtc_funcs->mode_set_base(set->crtc,
set->x, set->y, old_fb);
- if (ret != 0)
+ if (ret != 0) {
+ set->crtc->fb = old_fb;
goto fail;
+ }
}
DRM_DEBUG_KMS("Setting connector DPMS state to on\n");
for (i = 0; i < set->num_connectors; i++) {
--
1.7.2.3
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 --- Comment #21 from Daniel 2011-01-19 12:16:34 --- My results after tests since yesterday: - patch in #8 + first patch in #10: ok - patch in #8 + second patch in #10: ok - patch in #8 + third patch in #10: flickering For today i would test patch in comment #20. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[PATCH 03/17][trivial] GPU DRM: Remove unnecessary casts of void ptr returning alloc function return values
On Tue, 9 Nov 2010, Jesper Juhl wrote:
> Hi,
>
> The [vk][cmz]alloc(_node) family of functions return void pointers which
> it's completely unnecessary/pointless to cast to other pointer types since
> that happens implicitly.
>
> This patch removes such casts from drivers/gpu/drm/
>
>
> Signed-off-by: Jesper Juhl
> ---
> drm_sman.c |4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_sman.c b/drivers/gpu/drm/drm_sman.c
> index 463aed9..3466458 100644
> --- a/drivers/gpu/drm/drm_sman.c
> +++ b/drivers/gpu/drm/drm_sman.c
> @@ -59,9 +59,7 @@ drm_sman_init(struct drm_sman * sman, unsigned int
> num_managers,
> {
> int ret = 0;
>
> - sman->mm = (struct drm_sman_mm *) kcalloc(num_managers,
> - sizeof(*sman->mm),
> - GFP_KERNEL);
> + sman->mm = kcalloc(num_managers, sizeof(*sman->mm), GFP_KERNEL);
> if (!sman->mm) {
> ret = -ENOMEM;
> goto out;
>
Doesn't seem to be present in linux-next as of today, applied to trivial
queue.
Thanks,
--
Jiri Kosina
SUSE Labs, Novell Inc.
[Bug 33272] New: Kernel DRM/Radeon KMS BSOD on HD6850-NI
https://bugs.freedesktop.org/show_bug.cgi?id=33272 Summary: Kernel DRM/Radeon KMS BSOD on HD6850-NI Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: spamjunkeater at gmail.com Using 2.6.38-rc1 vanilla, When I try to load radeon kernel module with modprobe radeon modeset=1 I got BSOD, computer doesn't give any response to me. CTRL+ALT+DEL don't working nor my main computer switch. modprobe radeon modeset=0 doesn't make such problem and computer looks working. But my Northern Islands (HD6850) card doesn't support Gallium3D without KMS. Thanks. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33272] Kernel DRM/Radeon KMS BSOD on HD6850-NI
https://bugs.freedesktop.org/show_bug.cgi?id=33272 --- Comment #1 from Alex Deucher 2011-01-19 07:42:20 PST --- Have you installed the necessary ucode for your card? http://people.freedesktop.org/~agd5f/radeon_ucode/ BARTS_mc.bin BARTS_me.bin BARTS_pfp.bin BTC_rlc.bin -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
drm:i915_report_and_clear_eir -- *ERROR* EIR stuck: 0x00000010, masking
Hi, I am getting this during boot with current Linus' tree on x200s thinkpad: [8.312007] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x0010, masking head -39 /sys/kernel/debug/dri/64/i915_error_state shows: Time: 1295452835 s 347238 us PCI ID: 0x2a42 EIR: 0x0010 PGTBL_ER: 0x0001 Render command stream: ACTHD: 0x00534024 IPEIR: 0x IPEHR: 0x0200 INSTDONE: 0x INSTDONE1: 0xbfbb INSTPS: 0x8001e025 INSTPM: 0x seqno: 0x fence[0] = fence[1] = fence[2] = fence[3] = fence[4] = fence[5] = fence[6] = fence[7] = fence[8] = fence[9] = fence[10] = fence[11] = fence[12] = fence[13] = fence[14] = fence[15] = Active [3]: 0053400016384 0009 0001 dirty render uncached 00042000 5185536 0043 0001 P render uncached (name: 1) 00538000 20971520 0002 0002 P X dirty render uncached Pinned [4]: 4096 0001 0001 P snooped 1000 131072 0001 0001 P uncached 00021000 4096 0001 0001 P snooped 00022000 131072 0001 0001 P uncached Apart from the error in the kernel buffer, graphics seems to work normally. -- Jiri Kosina SUSE Labs, Novell Inc.
[Bug 33255] Crash using webgl (firefox 4b9)
https://bugs.freedesktop.org/show_bug.cgi?id=33255 --- Comment #1 from Marek Ol??k 2011-01-19 08:43:09 PST --- (In reply to comment #0) > *WARN_ONCE* > File r300_state.c function r300SetupRSUnit line 1521 > Don't know how to satisfy InputsRead=0x4000 > *** This message is from the classic driver. Are you sure you're really running the Gallium one? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH] drm: Restore the old_fb upon modeset failure
Never mind, you caught this one on your last sweep. Thanks, -Chris -- Chris Wilson, Intel Open Source Technology Centre
[Bug 33255] Crash using webgl (firefox 4b9)
https://bugs.freedesktop.org/show_bug.cgi?id=33255 --- Comment #2 from 0enjolras0 at laposte.net 2011-01-19 09:17:56 PST --- Created an attachment (id=42200) --> (https://bugs.freedesktop.org/attachment.cgi?id=42200) Intresting parts from Dmesg -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33255] Crash using webgl (firefox 4b9)
https://bugs.freedesktop.org/show_bug.cgi?id=33255 --- Comment #3 from 0enjolras0 at laposte.net 2011-01-19 09:18:45 PST --- Created an attachment (id=42201) --> (https://bugs.freedesktop.org/attachment.cgi?id=42201) Log Xorg -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33255] Crash using webgl (firefox 4b9)
https://bugs.freedesktop.org/show_bug.cgi?id=33255 --- Comment #4 from 0enjolras0 at laposte.net 2011-01-19 09:20:55 PST --- Hy I think i do, because i can see this in glxinfo : OpenGL vendor string: X.Org R300 Project OpenGL renderer string: Gallium 0.4 on RS690 But i apologize I can't do better. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33276] "invalid enumerant" during: Cubemap ID generation
https://bugs.freedesktop.org/show_bug.cgi?id=33276 Alex Deucher changed: What|Removed |Added Product|xorg|Mesa Version|7.5 |unspecified Component|Driver/Radeon |Drivers/DRI/r300 AssignedTo|xorg-driver-ati at lists.x.org |dri-devel at lists.freedesktop ||.org QAContact|xorg-team at lists.x.org | --- Comment #1 from Alex Deucher 2011-01-19 09:50:21 PST --- Are you using the r300 classic or r300 gallium 3D driver? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33276] "invalid enumerant" during: Cubemap ID generation
https://bugs.freedesktop.org/show_bug.cgi?id=33276 --- Comment #2 from Alexander Konotop 2011-01-19 10:18:29 PST --- (In reply to comment #1) > Are you using the r300 classic or r300 gallium 3D driver? $ glxinfo | grep OpenGL OpenGL vendor string: DRI R300 Project OpenGL renderer string: Mesa DRI R300 (RS400 5975) 20090101 NO-TCL DRI2 OpenGL version string: 1.5 Mesa 7.7.1 OpenGL extensions: $ glxinfo | Gallium outputs nothing -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33276] "invalid enumerant" during: Cubemap ID generation
https://bugs.freedesktop.org/show_bug.cgi?id=33276 --- Comment #3 from Alexander Konotop 2011-01-19 10:20:24 PST --- (In reply to comment #2) > (In reply to comment #1) > > Are you using the r300 classic or r300 gallium 3D driver? > > $ glxinfo | grep OpenGL > OpenGL vendor string: DRI R300 Project > OpenGL renderer string: Mesa DRI R300 (RS400 5975) 20090101 NO-TCL DRI2 > OpenGL version string: 1.5 Mesa 7.7.1 > OpenGL extensions: > > $ glxinfo | Gallium outputs nothing sorry, $ glxinfo | grep Gallium, not $ glxinfo | Gallium -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33276] "invalid enumerant" during: Cubemap ID generation
https://bugs.freedesktop.org/show_bug.cgi?id=33276 --- Comment #4 from Alex Deucher 2011-01-19 10:25:08 PST --- You are using the classic driver. You might want to try the r300 gallium driver. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33276] "invalid enumerant" during: Cubemap ID generation
https://bugs.freedesktop.org/show_bug.cgi?id=33276 --- Comment #5 from Alexander Konotop 2011-01-19 10:31:15 PST --- (In reply to comment #4) > You are using the classic driver. You might want to try the r300 gallium > driver. Ok, thank's. But debian doesn't have gallium driver in a repository, I have to build it myself. Will it be useful for you if I try? If not - I'll try later and maybe never ), if yes - I'll try soon. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33276] "invalid enumerant" during: Cubemap ID generation
https://bugs.freedesktop.org/show_bug.cgi?id=33276 --- Comment #6 from Alexander Konotop 2011-01-19 10:55:40 PST --- (In reply to comment #5) > (In reply to comment #4) > > You are using the classic driver. You might want to try the r300 gallium > > driver. > Ok, thank's. But debian doesn't have gallium driver in a repository, I have to > build it myself. Will it be useful for you if I try? If not - I'll try later > and maybe never ), if yes - I'll try soon. Oh, it's much simplier than I thought! I've just added 2 repositories: from here https://launchpad.net/~xorg-edgers/+archive/drivers-only and from here https://launchpad.net/~xorg-edgers/+archive/radeon They're for ubuntu lucid but work great on debian sid too. Very fast and vdrift now starts. I think you have to close this report now. Anyone who has similar problems just has to use gallium driver. It works, I've tested. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 27314] DP link training fails on 2560x1440 panels
https://bugs.freedesktop.org/show_bug.cgi?id=27314 --- Comment #28 from Travis Glenn Hansen 2011-01-19 11:24:20 PST --- Been out on vacation. Is it still necessary to test the latest patch? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33276] "invalid enumerant" during: Cubemap ID generation
https://bugs.freedesktop.org/show_bug.cgi?id=33276 Alex Deucher changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Comment #7 from Alex Deucher 2011-01-19 12:06:24 PST --- Use the gallium driver. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 27314] DP link training fails on 2560x1440 panels
https://bugs.freedesktop.org/show_bug.cgi?id=27314 --- Comment #29 from Alex Deucher 2011-01-19 12:07:25 PST --- (In reply to comment #28) > Been out on vacation. Is it still necessary to test the latest patch? Worth a shot. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33272] Kernel DRM/Radeon KMS BSOD on HD6850-NI
https://bugs.freedesktop.org/show_bug.cgi?id=33272 --- Comment #2 from Erdem U. Altinyurt 2011-01-19 12:25:42 PST --- definitely, right to /lib/modules/radeon directory. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33272] Kernel DRM/Radeon KMS BSOD on HD6850-NI
https://bugs.freedesktop.org/show_bug.cgi?id=33272 --- Comment #3 from Alex Deucher 2011-01-19 12:56:08 PST --- If you are using an initrd make sure the ucode is built into the initrd. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 --- Comment #22 from Daniel 2011-01-19 21:14:55 --- After running with patch of comment #20 for 6 hours and no flickering, i suddenly got a black screen after watching a video for some minutes. Switching to tty1 and back to tty7 (xorg) the problem was gone for one minute and i got a black screen again. I watched the video again, but the problem was not reproducible. For now i rebooted and will try to verifying it again. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 31046] [r600g, tiling] visual errors and GPU resets
https://bugs.freedesktop.org/show_bug.cgi?id=31046 Tobias Jakobi changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | --- Comment #9 from Tobias Jakobi 2011-01-19 14:12:45 PST --- After doing some thorough testing today with ut2004 I noticed that mipmaps are still affected when having R600_FORCE_TILING enabled. Going to take some screenshots later. I didn't encounter any GPU resets though, so it's just rendering errors and it seems to be limited to mipmaps. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 --- Comment #23 from Daniel 2011-01-19 22:28:21 --- Oh, while some reboots one time it begins flickering directly after kms switching on console. I think patch of #20 is not stable for me. What can i do/test now? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 --- Comment #24 from Alex Deucher 2011-01-19 22:30:11 --- (In reply to comment #23) > Oh, while some reboots one time it begins flickering directly after kms > switching on console. I think patch of #20 is not stable for me. What can i > do/test now? Can you test the mini patches from comment 10 in combination with the patch from comment 20? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 33172] [r600g] ingame rendering broken (black screen) in ut2003
https://bugs.freedesktop.org/show_bug.cgi?id=33172 --- Comment #2 from Tobias Jakobi 2011-01-19 14:35:02 PST --- We (Jan and me) did some tests today and found out that the issue is probably related to the use of VBOs (or more specifically: not using them). In ut2004 there is a option called 'UseVBO' for the OpenGL renderer. I guess enabling this one lets the engine use the 'ARB_vertex_buffer_object' extension. It turned out that in my ut2004 config it was enabled, but Jan had it disabled. So after enabling it for Jan the rendering suddenly worked. And when I disabled UseVBO on my system it suddenly failed and produced the black screen, plus the relocation parser errors in the kernel log. I can only guess here, but maybe the problem is with Gallium's immediate mode implementation -- if that's how the engine submits vertices when ARB_vbo is not used. The next thing we found out is even more interesting: In ut2003 there is no such option, so he had to stick to the 'immediate mode' rendering path. All the tests were done on Jan's system. We noticed that is was possible to get ingame when being logged in as root. This only worked for a short time, maybe like 10 seconds, before the game segfaulted. After it segfaulted, it wasn't possible any more to get ingame. The game just instantly segfaulted. Restarting X didn't help, only a full reboot did the trick. Another thing that worked: Reboot, start ut03 as root, watch some game scenary for like 3 seconds, quickly exit the game, start ut03 as root, repear procedure... The maximum amount of time we managed to get into game was three. After that it didn't work any more. It was like we hit some memory leak, maybe in VRAM? Then we switched over to ut2004 and disabled UseVBO there. We got the black screen (with the kernel messages) when we got ingame and then we waited a bit. But just like ut03 the game segfaulted after some seconds and we even managed it at one time to trigger the kernel OOM killer. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33262] [r600g] glean glsl1-shadow2D(): [1-4] regression
https://bugs.freedesktop.org/show_bug.cgi?id=33262 Christian K?nig changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #2 from Christian K?nig 2011-01-19 14:59:57 PST --- Fixed with commit a124490262a29d2e873fe50ca57974f246946b85 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33272] Kernel DRM/Radeon KMS BSOD on HD6850-NI
https://bugs.freedesktop.org/show_bug.cgi?id=33272 --- Comment #4 from Erdem U. Altinyurt 2011-01-19 15:31:09 PST --- I don't create initrd by hand. Used make install to install code and initrd doesn't have any radeon modules.So initrd doesn't have ucode. But I thought that is just for boot with radeon module loading. I don't use that feature. AFAIK Since I do not load radeon module on bootup, It's doesn't necessary to have those files in initrd and load from /lib/firmware/radeon/ directly. Does it requirement that having ucodes in initrd for running NI class cards? My internal 790GX GPU could woth with KMS without any ucode and modules in initrd. (At least with 2.6.37, I don't test it with 2.6.38-rc1 and 790GX disabled from bios since HD6850 plugged in). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33272] Kernel DRM/Radeon KMS BSOD on HD6850-NI
https://bugs.freedesktop.org/show_bug.cgi?id=33272 --- Comment #5 from Erdem U. Altinyurt 2011-01-19 16:09:56 PST --- Now tested my old 790GX and it's working with my setup but NI. Removed BARTS_mc.bin BARTS_me.bin BARTS_pfp.bin BTC_rlc.bin files from /lib/firmware/radeon. I expect that will make radeon.ko cannot found required ucodes and will not activate KMS and loaded as modeset=0. AFAIK That happens when I don't put required ucodes to fw directort with my 790GX when initial r600 support comes... So, when I try to load radeon without those ucodes on firmware directoy, result is same. BSOD. That make me thinking if it's not related with ucodes... Thanks -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33272] Kernel DRM/Radeon KMS BSOD on HD6850-NI
https://bugs.freedesktop.org/show_bug.cgi?id=33272 --- Comment #6 from Alex Deucher 2011-01-19 16:24:55 PST --- The ucode is required for all asics when the radeon drm is loaded. Most likley your initrd already has the ucode for older asics. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33262] [r600g] glean glsl1-shadow2D(): [1-4] regression
https://bugs.freedesktop.org/show_bug.cgi?id=33262 Vinson Lee changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #3 from Vinson Lee 2011-01-19 16:56:41 PST --- mesa: a124490262a29d2e873fe50ca57974f246946b85 (master) Verified fixed. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH 3/5] radeon: Expose backlight class device for legacy LVDS encoder
On Fri, 14 Jan 2011 14:24:23 -0500 Matthew Garrett wrote: > From: Michel D__nzer > > Allows e.g. power management daemons to control the backlight level. Inspired > by the corresponding code in radeonfb. > > (Updated to add backlight type and make the connector the parent device - mjg) > x86_64 allmodconfig: drivers/gpu/drm/radeon/radeon_legacy_encoders.c: In function 'radeon_legacy_lvds_update': drivers/gpu/drm/radeon/radeon_legacy_encoders.c:64: error: 'struct radeon_encoder_atom_dig' has no member named 'bl_dev' drivers/gpu/drm/radeon/radeon_legacy_encoders.c:65: error: 'struct radeon_encoder_atom_dig' has no member named 'backlight_level' drivers/gpu/drm/radeon/radeon_legacy_encoders.c:69: error: 'struct radeon_encoder_lvds' has no member named 'bl_dev' drivers/gpu/drm/radeon/radeon_legacy_encoders.c:70: error: 'struct radeon_encoder_lvds' has no member named 'backlight_level' drivers/gpu/drm/radeon/radeon_legacy_encoders.c: In function 'radeon_legacy_lvds_dpms': drivers/gpu/drm/radeon/radeon_legacy_encoders.c:144: error: 'struct radeon_encoder_atom_dig' has no member named 'dpms_mode' drivers/gpu/drm/radeon/radeon_legacy_encoders.c:147: error: 'struct radeon_encoder_lvds' has no member named 'dpms_mode'
more intel drm issues (was Re: [git pull] drm intel only fixes)
Ok, so I have a new issue that I'm currently bisecting but that people may be able to figure out even befor emy bisect finishes. On my slow Atom netbook (that I'm planning on using as my traveling companion for LCA), suspend-to-RAM takes a long time with current git. It's quite noticeable - it used to be pretty much instant, now it takes three seconds. And it's all i915 graphics (although I haven't bisected it down fully, I've bisected it down to the drm merge). In the good case (like plain 2.6.37), a suspend event will look something like this: ... PM: suspend of devices complete after 147.646 msecs ... but the i915 driver at some point made it take 3s: ... PM: suspend of devices complete after 3059.656 msecs ... which is definitely long enough to be worth fixing. Maybe the person responsible will go "oh, that's obviously due to xyz", and just fix it. But I'll continue to bisect in case nobody steps up to admit to wasting time.. Linus
[Bug 33139] Radeon HD 5750 locks up when using 3D apps with r600g
https://bugs.freedesktop.org/show_bug.cgi?id=33139 --- Comment #3 from Rub?n Fern?ndez 2011-01-19 19:44:35 PST --- I also experience GPU lockups with about half the games I've tried in an HD5750 (all of which work in an older r300g card) In my case, in all but one I can still do SSH (even with latest mesa), so I'll try to post debugging information here. GPU: ATI Technologies Inc Juniper HDMI Audio [Radeon HD 5700 Series] Kernel: 2.6.38 libdrm-2.4.23 xf86-video-ati git 57fbddfc21d8c6794f378489b764cc2a0ad4a48c Mesa git 3ee60a3558a3546b3c3a0a9732d384afcf02994a X.Org X Server 1.9.0 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 31870] [evergreen] Graphics freezes when selecting Atlantis from XScreenSaver
https://bugs.freedesktop.org/show_bug.cgi?id=31870 --- Comment #2 from Rub?n Fern?ndez 2011-01-19 19:52:07 PST --- I have the exact same bug in an HD5750; it also used to freeze specifically with atlantis, and now randomly GPU: ATI Technologies Inc Juniper HDMI Audio [Radeon HD 5700 Series] Kernel: 2.6.38 libdrm-2.4.23 xf86-video-ati git 57fbddfc21d8c6794f378489b764cc2a0ad4a48c Mesa git 3ee60a3558a3546b3c3a0a9732d384afcf02994a X.Org X Server 1.9.0 XScreenSaver 5.12 To reproduce: 1) Run xscreensaver-demo 2) Do a preview of opengl screensavers several times Eventually, you'll get to some screensaver that runs fine, but, after closing it, some second later, the cursor freezes. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
more intel drm issues (was Re: [git pull] drm intel only fixes)
On Wed, Jan 19, 2011 at 8:55 PM, Jeff Chua wrote:
>
> Rafael send out two patches earlier. Could be related. I was facing
> issue during resume.
No, I'm aware of the rcu-synchronize thing, this isn't it. This is
really at the suspend stage, and I had bisected it down to the drm
changes.
In fact, by now I have bisected it down to a single commit. It's
another merge commit, which makes me a bit nervous (I bisected another
issue today, and it turned out to simply not be repeatable).
But this time the merge commit actually has a real conflict that got
fixed up in the merge, and the code around the conflict waits for
three seconds, and three seconds is also exactly how long the delay at
suspend time is. So I get the feeling that this time it's a real
issue, and what happened was that the merge may have been a mismerge.
Chris: as of commit 8d5203ca6253 ("Merge branch 'drm-intel-fixes' into
drm-intel-next") I'm getting that 3-second delay at suspend time. And
the merge diff looks like this:
+ struct drm_device *dev = ring->dev;
+ struct drm_i915_private *dev_priv = dev->dev_private;
unsigned long end;
- drm_i915_private_t *dev_priv = dev->dev_private;
u32 head;
- head = intel_read_status_page(ring, 4);
- if (head) {
- ring->head = head & HEAD_ADDR;
- ring->space = ring->head - (ring->tail + 8);
- if (ring->space < 0)
- ring->space += ring->size;
- if (ring->space >= n)
- return 0;
- }
-
trace_i915_ring_wait_begin (dev);
end = jiffies + 3 * HZ;
do {
and that whole do-loop with a 3-second timeout makes me *very*
suspicious. It used to have (in _one_ of the parent branches) that
code before it to return early if there was space in the ring, now it
doesn't any more - and that merge co-incides with my suspend suddenly
taking 3 seconds.
The same check that is deleted does exist inside the loop too, but
there it has some extra code it in (compare to "actual_head" and so
on), so I wonder if the fast-case was somehow hiding this issue.
But I don't know the code. I just see that whole "PM: suspend of
devices complete after x.xxx msecs" issue, and I can see the machine
taking too long to suspend.
Linus
