[Bug 14924] KMS:RV370:X300 GPU lockup ('some' web-sites in Firefox)
http://bugzilla.kernel.org/show_bug.cgi?id=14924 --- Comment #5 from Michel Dänzer mic...@daenzer.net 2010-01-26 08:37:07 --- (In reply to comment #2) I think it is KMS related, but for me I only get the lockup when I boot with nomodeset. This is self-contradictory, as nomodeset disables KMS. Apparently your problem is not KMS related and probably different from the one tracked here. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26199] kernel oops in 2.6.33 rc5 when dri is set to off in xorg.conf
http://bugs.freedesktop.org/show_bug.cgi?id=26199 --- Comment #6 from Michel Dänzer mic...@daenzer.net 2010-01-26 02:02:52 PST --- (In reply to comment #3) When I set radeon.agpmode=-1 on the kernel command line I'm not able to make the kernel crash. I tried 6 times. Without setting agpmode to -1 it crashes with probability of about 0.5 when DRI is off. When DRI is on it typically does not crash. radeon.agpmode only has an effect if KMS is enabled, in which case an X driver with KMS support can't really work without the DRI; not sure what happens if you try. But from It complains about dri version mismatch which is strange since I compiled libdrm with --enable-radeon-experimental-api [...] it sounds like your X driver doesn't have KMS support built in, in which case it's not expected to work properly at all if KMS is enabled. In summary, unless your X log contains a line like (II) [KMS] Kernel modesetting enabled. without Option DRI off, this report is probably invalid. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26051] Regression in 7.6, glxgears locks the machine (rv280)
http://bugs.freedesktop.org/show_bug.cgi?id=26051 --- Comment #9 from Michel Dänzer mic...@daenzer.net 2010-01-26 02:44:35 PST --- (In reply to comment #8) The problem (specifically, glxgears locks up before showing any gear wheels) still exists in HEAD from last Friday (124a6b1958c630ea049025e2b72547096fdc8f2c). 'HEAD' in Git refers to the most recent commit of the currently checked out branch. 124a6b1958c630ea049025e2b72547096fdc8f2c is a rather old (June/July 2009) commit from the master branch. I tried git-bisect against this, again it came back to 28471cfa970702128d822c2ecbb1703eedbca245 which is a merge, and as I'm sure you already know, this usage of git (apparently, merging from cvs) It has nothing to do with CVS. A merge in Git is simply the folding of the histories of several branches into a single one. Looking at the commit in question in gitk or another GUI frontend may help visualize this. is not nice for those of us asked to bisect. Please try if the problem occurs with either of the parent commits of the merge commit. (Although the fact that git bisect identified the merge commit as the first bad one indicates that you already did in the course of the bisection, and neither of them had the problem) To cut a long story short, when I got back to reverting 25b492b976632269dfa3de164545d50a53c090ce |From: Michel Dänzer daen...@vmware.com |Date: Tue, 07 Jul 2009 11:52:35 + |Subject: GLX/DRI1: Mark GLX visuals with depth != screen depth non-conformant. | |Such visuals are subject to automatic compositing in the X server, so DRI1 |can't render to them properly. I again have a working glxgears (the test includes letting the machine sit powered-off, not just a reboot - power off seems to be important). So, at this point I tried to revert it from HEAD to prove it would fix it. Problem: it has already been reverted in HEAD (and, to repeat, that still locks up - unless I mistested). AFAICT that change is still in the current master branch. I suspect 'HEAD' doesn't mean what you thought. (As you don't seem to feel very comfortable with Git yet, it may be a good idea to run 'git status' frequently to verify the current state matches your expectation) At the moment, I have one other commit to try reverting : |From 71633abafc935c25da9731bab48c228ceb9b4097 Mon Sep 17 00:00:00 2001 |From: Michel Dänzer daen...@vmware.com |Date: Tue, 07 Jul 2009 12:49:52 + |Subject: gallium: Fixes for clobbering stencil values in combined |depth/stencil textures. This commit is Gallium specific and irrelevant for this problem. What I really don't get is that neither of these commits are for r200 The former commit could be relevant, though it probably couldn't cause the problem itself but merely trigger it by making glxgears choose a different visual. If you can confirm that reverting this commit avoids the problem, please attach the glxinfo output from with and without the commit. This is all on linux-2.6.32.2 - maybe I should upgrade that before trying to get any further into this mess ? Shouldn't hurt, but don't expect any miracles. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5714] Front buffer removal from libdri
http://bugs.freedesktop.org/show_bug.cgi?id=5714 Alan Hourihane al...@fairlite.co.uk changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26185] [M96==RV730][KMS] Black screen after resume from RAM
http://bugs.freedesktop.org/show_bug.cgi?id=26185 Rafał Miłecki zaj...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution||NOTOURBUG --- Comment #8 from Rafał Miłecki zaj...@gmail.com 2010-01-26 03:24:01 PST --- The problem is that pm-suspend (s2ram?) uses quriks even for KMS. It tries to restore GPU state in KMS, where it's already handled by KMS GPU driver. Forcing pm-suspend to do not use quirks fixes problem. See bug #26235 for details -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26199] kernel oops in 2.6.33 rc5 when dri is set to off in xorg.conf
http://bugs.freedesktop.org/show_bug.cgi?id=26199 --- Comment #7 from Peter Hercek pher...@gmail.com 2010-01-26 03:35:05 PST --- (In reply to comment #6) In summary, unless your X log contains a line like (II) [KMS] Kernel modesetting enabled. without Option DRI off, this report is probably invalid. Ok, so this report is invalid since when I run without radeon.agpmode=-1 and when Option DRI is on then I do not have line (II) [KMS] Kernel modesetting enabled. in my Xorg.log. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [PATCH] drm/ttm: Avoid conflicting reserve_memtype during ttm_tt_set_page_caching.
Sorry for bringing this up again with nothing new to say, but it's still
a problem (on nouveau it usually triggers a slow CPU-based eviction
fallback). Thomas: Are you OK with this patch?
Fixes errors like:
reserve_ram_pages_type failed 0x15b7a000-0x15b7b000, track 0x8, req 0x10
when a BO is moved between WC and UC areas.
Reported-by: Xavier Chantry shinin...@gmail.com
Signed-off-by: Francisco Jerez curroje...@riseup.net
---
drivers/gpu/drm/ttm/ttm_tt.c | 23 ---
1 files changed, 16 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_tt.c b/drivers/gpu/drm/ttm/ttm_tt.c
index 9c2b1cc..e2123af 100644
--- a/drivers/gpu/drm/ttm/ttm_tt.c
+++ b/drivers/gpu/drm/ttm/ttm_tt.c
@@ -198,17 +198,26 @@ EXPORT_SYMBOL(ttm_tt_populate);
static inline int ttm_tt_set_page_caching(struct page *p,
enum ttm_caching_state c_state)
{
+ int ret = 0;
+
if (PageHighMem(p))
return 0;
- switch (c_state) {
- case tt_cached:
- return set_pages_wb(p, 1);
- case tt_wc:
- return set_memory_wc((unsigned long) page_address(p), 1);
- default:
- return set_pages_uc(p, 1);
+ if (get_page_memtype(p) != -1) {
+ /* p isn't in the default caching state, set it to
+ * writeback first to free its current memtype. */
+
+ ret = set_pages_wb(p, 1);
+ if (ret)
+ return ret;
}
+
+ if (c_state == tt_wc)
+ ret = set_memory_wc((unsigned long) page_address(p), 1);
+ else if (c_state == tt_uncached)
+ ret = set_pages_uc(p, 1);
+
+ return ret;
}
#else /* CONFIG_X86 */
static inline int ttm_tt_set_page_caching(struct page *p,
--
1.6.4.4
pgpDGCQA6By0T.pgp
Description: PGP signature
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 15131] [OOPS] radeon kms
http://bugzilla.kernel.org/show_bug.cgi?id=15131 Rafael J. Wysocki r...@sisk.pl changed: What|Removed |Added Status|RESOLVED|CLOSED Resolution|PATCH_ALREADY_AVAILABLE |CODE_FIX --- Comment #1 from Rafael J. Wysocki r...@sisk.pl 2010-01-26 12:02:52 --- Fixed by: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=30d2d9a54d48e4fefede0389ded1b6fc2d44a522 -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [PATCH] drm/ttm: Avoid conflicting reserve_memtype during ttm_tt_set_page_caching.
Francisco Jerez wrote:
Sorry for bringing this up again with nothing new to say, but it's still
a problem (on nouveau it usually triggers a slow CPU-based eviction
fallback). Thomas: Are you OK with this patch?
Sorry, I've missed this patch. So is the problem that the core kernel
complains if you try to move directly from wc to uc? In that case it
looks OK to me:
Acked-by: Thomas Hellstrom thellst...@vmware.com
Fixes errors like:
reserve_ram_pages_type failed 0x15b7a000-0x15b7b000, track 0x8, req 0x10
when a BO is moved between WC and UC areas.
Reported-by: Xavier Chantry shinin...@gmail.com
Signed-off-by: Francisco Jerez curroje...@riseup.net
---
drivers/gpu/drm/ttm/ttm_tt.c | 23 ---
1 files changed, 16 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_tt.c b/drivers/gpu/drm/ttm/ttm_tt.c
index 9c2b1cc..e2123af 100644
--- a/drivers/gpu/drm/ttm/ttm_tt.c
+++ b/drivers/gpu/drm/ttm/ttm_tt.c
@@ -198,17 +198,26 @@ EXPORT_SYMBOL(ttm_tt_populate);
static inline int ttm_tt_set_page_caching(struct page *p,
enum ttm_caching_state c_state)
{
+int ret = 0;
+
if (PageHighMem(p))
return 0;
-switch (c_state) {
-case tt_cached:
-return set_pages_wb(p, 1);
-case tt_wc:
-return set_memory_wc((unsigned long) page_address(p), 1);
-default:
-return set_pages_uc(p, 1);
+if (get_page_memtype(p) != -1) {
+/* p isn't in the default caching state, set it to
+ * writeback first to free its current memtype. */
+
+ret = set_pages_wb(p, 1);
+if (ret)
+return ret;
}
+
+if (c_state == tt_wc)
+ret = set_memory_wc((unsigned long) page_address(p), 1);
+else if (c_state == tt_uncached)
+ret = set_pages_uc(p, 1);
+
+return ret;
}
#else /* CONFIG_X86 */
static inline int ttm_tt_set_page_caching(struct page *p,
--
1.6.4.4
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [OOPS] radeon kms
On Fri, 15 Jan 2010, Jerome Glisse wrote: On Fri, Jan 15, 2010 at 03:47:19PM +0100, John Kacur wrote: On Fri, 15 Jan 2010, John Kacur wrote: The oops is triggered because I am missing the firmware for radeon/R700_rlc.bin and radeon/R600_rlc.bin However, I think it should be able to deal with this more gracefully. ATOM BIOS: 9498.11.22.6.0.AS03 [drm] Clocks initialized ! [drm] Detected VRAM RAM=256M, BAR=256M [drm] RAM width 128bits DDR [TTM] Zone kernel: Available graphics memory: 3050912 kiB. [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [drm] radeon: 256M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. alloc irq_desc for 33 on node -1 alloc kstat_irqs on node -1 radeon :02:00.0: irq 33 for MSI/MSI-X [drm] radeon: using MSI. [drm] radeon: irq initialized. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV730 Microcode platform radeon_cp.0: firmware: requesting radeon/RV730_pfp.bin platform radeon_cp.0: firmware: requesting radeon/RV730_me.bin platform radeon_cp.0: firmware: requesting radeon/R700_rlc.bin r600_cp: Failed to load firmware radeon/R700_rlc.bin [drm:rv770_startup] *ERROR* Failed to load firmware! radeon :02:00.0: 8801a20b5400 unpin not necessary BUG: unable to handle kernel NULL pointer dereference at 0048 IP: [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] PGD 1a1a74067 PUD 1a19b8067 PMD 0 Oops: [#1] SMP last sysfs file: /sys/devices/platform/radeon_cp.0/firmware/radeon_cp.0/loading CPU 4 Pid: 168, comm: modprobe Not tainted 2.6.33-rc4 #3 EX58-UD3R/EX58-UD3R RIP: 0010:[a0061034] [a0061034] ttm_bo_reserve+0x16/0xf8 [t tm] RSP: 0018:8801a1a8fb68 EFLAGS: 00010292 RAX: 8801 RBX: RCX: RDX: RSI: 0001 RDI: 0048 RBP: 8801a1a8fba8 R08: R09: R10: R11: R12: R13: 8801a8838000 R14: 0024 R15: 2000 FS: 7f0f9c6dc700() GS:88002e40() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 0048 CR3: 0001a195d000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process modprobe (pid: 168, threadinfo 8801a1a8e000, task 8801a22c) Stack: 8801 8801a27e2900 8801a1a8fb88 0 8801a8838000 0024 2000 0 8801a1a8fbd8 a00ba05b 8801a1a8fbd8 8801a27f4000 Call Trace: [a00ba05b] radeon_bo_reserve.clone.0+0x2a/0x6d [radeon] [a00bb441] rv770_suspend+0x43/0x69 [radeon] [a00bb6cf] rv770_init+0x1a4/0x22d [radeon] [a0089593] radeon_device_init+0x27f/0x300 [radeon] [a008a0fb] radeon_driver_load_kms+0xff/0x184 [radeon] [a001e1a6] drm_get_dev+0x3c4/0x4c5 [drm] [8122ea73] ? pci_match_device+0x22/0xd0 [a00c3bb8] radeon_pci_probe+0x15/0x268 [radeon] [8122e941] local_pci_probe+0x17/0x1b [8122f721] pci_device_probe+0xcd/0xfd [812ce793] ? driver_sysfs_add+0x4c/0x71 [812ce95c] driver_probe_device+0xde/0x1fe [812cead9] __driver_attach+0x5d/0x81 [812cea7c] ? __driver_attach+0x0/0x81 [812cdded] bus_for_each_dev+0x59/0x8e [812ce6f2] driver_attach+0x1e/0x20 [812ce330] bus_add_driver+0xd8/0x240 [812cedcb] driver_register+0x9d/0x10e [8122f969] __pci_register_driver+0x68/0xd8 [81439aa2] ? printk+0x41/0x47 [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a0018eb3] drm_init+0x75/0xdb [drm] [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a00f70bf] radeon_init+0xbf/0xc1 [radeon] [81002069] do_one_initcall+0x5e/0x15e [81087788] sys_init_module+0xd8/0x23a [81009bf2] system_call_fastpath+0x16/0x1b Code: 01 00 00 00 31 c0 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f c9 c3 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 18 0f 1f 44 00 00 4c 8b 27 48 89 fb 41 88 f5 41 88 d6 41 88 cf 44 89 45 c8 49 81 RIP [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] RSP 8801a1a8fb68 CR2: 0048 ---[ end trace 604e2e318733e108 ]--- udevd-work[166]: '/sbin/modprobe -b pci:v1002d9498sv1043sd0300bc 03sc00i00' unexpected exit with status 0x0009 I forgot to mention that this is kernel version 2.6.33-rc4. Thanks. Yes, we didn't paid enough attention to failure path :( Sorry for that Fix should be in next rc, patch
Re: [OOPS] radeon kms
On Tue, Jan 26, 2010 at 8:21 AM, John Kacur jka...@redhat.com wrote: On Fri, 15 Jan 2010, Jerome Glisse wrote: On Fri, Jan 15, 2010 at 03:47:19PM +0100, John Kacur wrote: On Fri, 15 Jan 2010, John Kacur wrote: The oops is triggered because I am missing the firmware for radeon/R700_rlc.bin and radeon/R600_rlc.bin However, I think it should be able to deal with this more gracefully. ATOM BIOS: 9498.11.22.6.0.AS03 [drm] Clocks initialized ! [drm] Detected VRAM RAM=256M, BAR=256M [drm] RAM width 128bits DDR [TTM] Zone kernel: Available graphics memory: 3050912 kiB. [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [drm] radeon: 256M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. alloc irq_desc for 33 on node -1 alloc kstat_irqs on node -1 radeon :02:00.0: irq 33 for MSI/MSI-X [drm] radeon: using MSI. [drm] radeon: irq initialized. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV730 Microcode platform radeon_cp.0: firmware: requesting radeon/RV730_pfp.bin platform radeon_cp.0: firmware: requesting radeon/RV730_me.bin platform radeon_cp.0: firmware: requesting radeon/R700_rlc.bin r600_cp: Failed to load firmware radeon/R700_rlc.bin [drm:rv770_startup] *ERROR* Failed to load firmware! radeon :02:00.0: 8801a20b5400 unpin not necessary BUG: unable to handle kernel NULL pointer dereference at 0048 IP: [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] PGD 1a1a74067 PUD 1a19b8067 PMD 0 Oops: [#1] SMP last sysfs file: /sys/devices/platform/radeon_cp.0/firmware/radeon_cp.0/loading CPU 4 Pid: 168, comm: modprobe Not tainted 2.6.33-rc4 #3 EX58-UD3R/EX58-UD3R RIP: 0010:[a0061034] [a0061034] ttm_bo_reserve+0x16/0xf8 [t tm] RSP: 0018:8801a1a8fb68 EFLAGS: 00010292 RAX: 8801 RBX: RCX: RDX: RSI: 0001 RDI: 0048 RBP: 8801a1a8fba8 R08: R09: R10: R11: R12: R13: 8801a8838000 R14: 0024 R15: 2000 FS: 7f0f9c6dc700() GS:88002e40() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 0048 CR3: 0001a195d000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process modprobe (pid: 168, threadinfo 8801a1a8e000, task 8801a22c) Stack: 8801 8801a27e2900 8801a1a8fb88 0 8801a8838000 0024 2000 0 8801a1a8fbd8 a00ba05b 8801a1a8fbd8 8801a27f4000 Call Trace: [a00ba05b] radeon_bo_reserve.clone.0+0x2a/0x6d [radeon] [a00bb441] rv770_suspend+0x43/0x69 [radeon] [a00bb6cf] rv770_init+0x1a4/0x22d [radeon] [a0089593] radeon_device_init+0x27f/0x300 [radeon] [a008a0fb] radeon_driver_load_kms+0xff/0x184 [radeon] [a001e1a6] drm_get_dev+0x3c4/0x4c5 [drm] [8122ea73] ? pci_match_device+0x22/0xd0 [a00c3bb8] radeon_pci_probe+0x15/0x268 [radeon] [8122e941] local_pci_probe+0x17/0x1b [8122f721] pci_device_probe+0xcd/0xfd [812ce793] ? driver_sysfs_add+0x4c/0x71 [812ce95c] driver_probe_device+0xde/0x1fe [812cead9] __driver_attach+0x5d/0x81 [812cea7c] ? __driver_attach+0x0/0x81 [812cdded] bus_for_each_dev+0x59/0x8e [812ce6f2] driver_attach+0x1e/0x20 [812ce330] bus_add_driver+0xd8/0x240 [812cedcb] driver_register+0x9d/0x10e [8122f969] __pci_register_driver+0x68/0xd8 [81439aa2] ? printk+0x41/0x47 [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a0018eb3] drm_init+0x75/0xdb [drm] [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a00f70bf] radeon_init+0xbf/0xc1 [radeon] [81002069] do_one_initcall+0x5e/0x15e [81087788] sys_init_module+0xd8/0x23a [81009bf2] system_call_fastpath+0x16/0x1b Code: 01 00 00 00 31 c0 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f c9 c3 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 18 0f 1f 44 00 00 4c 8b 27 48 89 fb 41 88 f5 41 88 d6 41 88 cf 44 89 45 c8 49 81 RIP [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] RSP 8801a1a8fb68 CR2: 0048 ---[ end trace 604e2e318733e108 ]--- udevd-work[166]: '/sbin/modprobe -b pci:v1002d9498sv1043sd0300bc 03sc00i00' unexpected exit with status 0x0009 I forgot to mention that this is kernel version 2.6.33-rc4. Thanks. Yes, we didn't paid enough attention to failure
[Bug 26183] [R200] Wrong gear color in glxgear
http://bugs.freedesktop.org/show_bug.cgi?id=26183 --- Comment #2 from okias d.ok...@gmail.com 2010-01-26 06:15:31 PST --- I forgot add some important information: tested: kernel 2.6.32 - 2.6.33-git xorg 1.7.4 ddx git mesa git I'm able to test patches, if anyone have idea how solve this little issue :-) -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [OOPS] radeon kms
On Tue, Jan 26, 2010 at 9:10 AM, John Kacur jka...@redhat.com wrote: On Tue, Jan 26, 2010 at 2:59 PM, Alex Deucher alexdeuc...@gmail.com wrote: On Tue, Jan 26, 2010 at 8:21 AM, John Kacur jka...@redhat.com wrote: On Fri, 15 Jan 2010, Jerome Glisse wrote: On Fri, Jan 15, 2010 at 03:47:19PM +0100, John Kacur wrote: On Fri, 15 Jan 2010, John Kacur wrote: The oops is triggered because I am missing the firmware for radeon/R700_rlc.bin and radeon/R600_rlc.bin However, I think it should be able to deal with this more gracefully. ATOM BIOS: 9498.11.22.6.0.AS03 [drm] Clocks initialized ! [drm] Detected VRAM RAM=256M, BAR=256M [drm] RAM width 128bits DDR [TTM] Zone kernel: Available graphics memory: 3050912 kiB. [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [drm] radeon: 256M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. alloc irq_desc for 33 on node -1 alloc kstat_irqs on node -1 radeon :02:00.0: irq 33 for MSI/MSI-X [drm] radeon: using MSI. [drm] radeon: irq initialized. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV730 Microcode platform radeon_cp.0: firmware: requesting radeon/RV730_pfp.bin platform radeon_cp.0: firmware: requesting radeon/RV730_me.bin platform radeon_cp.0: firmware: requesting radeon/R700_rlc.bin r600_cp: Failed to load firmware radeon/R700_rlc.bin [drm:rv770_startup] *ERROR* Failed to load firmware! radeon :02:00.0: 8801a20b5400 unpin not necessary BUG: unable to handle kernel NULL pointer dereference at 0048 IP: [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] PGD 1a1a74067 PUD 1a19b8067 PMD 0 Oops: [#1] SMP last sysfs file: /sys/devices/platform/radeon_cp.0/firmware/radeon_cp.0/loading CPU 4 Pid: 168, comm: modprobe Not tainted 2.6.33-rc4 #3 EX58-UD3R/EX58-UD3R RIP: 0010:[a0061034] [a0061034] ttm_bo_reserve+0x16/0xf8 [t tm] RSP: 0018:8801a1a8fb68 EFLAGS: 00010292 RAX: 8801 RBX: RCX: RDX: RSI: 0001 RDI: 0048 RBP: 8801a1a8fba8 R08: R09: R10: R11: R12: R13: 8801a8838000 R14: 0024 R15: 2000 FS: 7f0f9c6dc700() GS:88002e40() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 0048 CR3: 0001a195d000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process modprobe (pid: 168, threadinfo 8801a1a8e000, task 8801a22c) Stack: 8801 8801a27e2900 8801a1a8fb88 0 8801a8838000 0024 2000 0 8801a1a8fbd8 a00ba05b 8801a1a8fbd8 8801a27f4000 Call Trace: [a00ba05b] radeon_bo_reserve.clone.0+0x2a/0x6d [radeon] [a00bb441] rv770_suspend+0x43/0x69 [radeon] [a00bb6cf] rv770_init+0x1a4/0x22d [radeon] [a0089593] radeon_device_init+0x27f/0x300 [radeon] [a008a0fb] radeon_driver_load_kms+0xff/0x184 [radeon] [a001e1a6] drm_get_dev+0x3c4/0x4c5 [drm] [8122ea73] ? pci_match_device+0x22/0xd0 [a00c3bb8] radeon_pci_probe+0x15/0x268 [radeon] [8122e941] local_pci_probe+0x17/0x1b [8122f721] pci_device_probe+0xcd/0xfd [812ce793] ? driver_sysfs_add+0x4c/0x71 [812ce95c] driver_probe_device+0xde/0x1fe [812cead9] __driver_attach+0x5d/0x81 [812cea7c] ? __driver_attach+0x0/0x81 [812cdded] bus_for_each_dev+0x59/0x8e [812ce6f2] driver_attach+0x1e/0x20 [812ce330] bus_add_driver+0xd8/0x240 [812cedcb] driver_register+0x9d/0x10e [8122f969] __pci_register_driver+0x68/0xd8 [81439aa2] ? printk+0x41/0x47 [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a0018eb3] drm_init+0x75/0xdb [drm] [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a00f70bf] radeon_init+0xbf/0xc1 [radeon] [81002069] do_one_initcall+0x5e/0x15e [81087788] sys_init_module+0xd8/0x23a [81009bf2] system_call_fastpath+0x16/0x1b Code: 01 00 00 00 31 c0 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f c9 c3 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 18 0f 1f 44 00 00 4c 8b 27 48 89 fb 41 88 f5 41 88 d6 41 88 cf 44 89 45 c8 49 81 RIP [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] RSP 8801a1a8fb68 CR2: 0048 ---[ end trace 604e2e318733e108 ]--- udevd-work[166]: '/sbin/modprobe -b pci:v1002d9498sv1043sd0300bc 03sc00i00' unexpected exit
Re: [OOPS] radeon kms
On Tue, Jan 26, 2010 at 3:19 PM, Alex Deucher alexdeuc...@gmail.com wrote: On Tue, Jan 26, 2010 at 9:10 AM, John Kacur jka...@redhat.com wrote: On Tue, Jan 26, 2010 at 2:59 PM, Alex Deucher alexdeuc...@gmail.com wrote: On Tue, Jan 26, 2010 at 8:21 AM, John Kacur jka...@redhat.com wrote: On Fri, 15 Jan 2010, Jerome Glisse wrote: On Fri, Jan 15, 2010 at 03:47:19PM +0100, John Kacur wrote: On Fri, 15 Jan 2010, John Kacur wrote: The oops is triggered because I am missing the firmware for radeon/R700_rlc.bin and radeon/R600_rlc.bin However, I think it should be able to deal with this more gracefully. ATOM BIOS: 9498.11.22.6.0.AS03 [drm] Clocks initialized ! [drm] Detected VRAM RAM=256M, BAR=256M [drm] RAM width 128bits DDR [TTM] Zone kernel: Available graphics memory: 3050912 kiB. [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [drm] radeon: 256M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. alloc irq_desc for 33 on node -1 alloc kstat_irqs on node -1 radeon :02:00.0: irq 33 for MSI/MSI-X [drm] radeon: using MSI. [drm] radeon: irq initialized. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV730 Microcode platform radeon_cp.0: firmware: requesting radeon/RV730_pfp.bin platform radeon_cp.0: firmware: requesting radeon/RV730_me.bin platform radeon_cp.0: firmware: requesting radeon/R700_rlc.bin r600_cp: Failed to load firmware radeon/R700_rlc.bin [drm:rv770_startup] *ERROR* Failed to load firmware! radeon :02:00.0: 8801a20b5400 unpin not necessary BUG: unable to handle kernel NULL pointer dereference at 0048 IP: [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] PGD 1a1a74067 PUD 1a19b8067 PMD 0 Oops: [#1] SMP last sysfs file: /sys/devices/platform/radeon_cp.0/firmware/radeon_cp.0/loading CPU 4 Pid: 168, comm: modprobe Not tainted 2.6.33-rc4 #3 EX58-UD3R/EX58-UD3R RIP: 0010:[a0061034] [a0061034] ttm_bo_reserve+0x16/0xf8 [t tm] RSP: 0018:8801a1a8fb68 EFLAGS: 00010292 RAX: 8801 RBX: RCX: RDX: RSI: 0001 RDI: 0048 RBP: 8801a1a8fba8 R08: R09: R10: R11: R12: R13: 8801a8838000 R14: 0024 R15: 2000 FS: 7f0f9c6dc700() GS:88002e40() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 0048 CR3: 0001a195d000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process modprobe (pid: 168, threadinfo 8801a1a8e000, task 8801a22c) Stack: 8801 8801a27e2900 8801a1a8fb88 0 8801a8838000 0024 2000 0 8801a1a8fbd8 a00ba05b 8801a1a8fbd8 8801a27f4000 Call Trace: [a00ba05b] radeon_bo_reserve.clone.0+0x2a/0x6d [radeon] [a00bb441] rv770_suspend+0x43/0x69 [radeon] [a00bb6cf] rv770_init+0x1a4/0x22d [radeon] [a0089593] radeon_device_init+0x27f/0x300 [radeon] [a008a0fb] radeon_driver_load_kms+0xff/0x184 [radeon] [a001e1a6] drm_get_dev+0x3c4/0x4c5 [drm] [8122ea73] ? pci_match_device+0x22/0xd0 [a00c3bb8] radeon_pci_probe+0x15/0x268 [radeon] [8122e941] local_pci_probe+0x17/0x1b [8122f721] pci_device_probe+0xcd/0xfd [812ce793] ? driver_sysfs_add+0x4c/0x71 [812ce95c] driver_probe_device+0xde/0x1fe [812cead9] __driver_attach+0x5d/0x81 [812cea7c] ? __driver_attach+0x0/0x81 [812cdded] bus_for_each_dev+0x59/0x8e [812ce6f2] driver_attach+0x1e/0x20 [812ce330] bus_add_driver+0xd8/0x240 [812cedcb] driver_register+0x9d/0x10e [8122f969] __pci_register_driver+0x68/0xd8 [81439aa2] ? printk+0x41/0x47 [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a0018eb3] drm_init+0x75/0xdb [drm] [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a00f70bf] radeon_init+0xbf/0xc1 [radeon] [81002069] do_one_initcall+0x5e/0x15e [81087788] sys_init_module+0xd8/0x23a [81009bf2] system_call_fastpath+0x16/0x1b Code: 01 00 00 00 31 c0 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f c9 c3 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 18 0f 1f 44 00 00 4c 8b 27 48 89 fb 41 88 f5 41 88 d6 41 88 cf 44 89 45 c8 49 81 RIP [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] RSP 8801a1a8fb68 CR2: 0048 ---[ end trace 604e2e318733e108 ]--- udevd-work[166]: '/sbin/modprobe
[Bug 26199] kernel oops in 2.6.33 rc5 when dri is set to off in xorg.conf
http://bugs.freedesktop.org/show_bug.cgi?id=26199 --- Comment #8 from Peter Hercek pher...@gmail.com 2010-01-26 06:44:20 PST --- I had incorrectly (with --disable-kms) compiled xf86-video-ati. I recompiled everything (libdrm, mesa, xf86-xf86-video-ati) today from git master and it seems to work ... well until I try to put video=1280x1024 on kernel command line. Then I get another hard kernel crash and lockup. But that is probably something completely different. Should I create a bug report for it? Btw it looks like Bug 18397 (Small pixmap corruption [EXA enabled]) is not there any more with kernel mode setting enabled. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [OOPS] radeon kms
On Tue, Jan 26, 2010 at 2:59 PM, Alex Deucher alexdeuc...@gmail.com wrote: On Tue, Jan 26, 2010 at 8:21 AM, John Kacur jka...@redhat.com wrote: On Fri, 15 Jan 2010, Jerome Glisse wrote: On Fri, Jan 15, 2010 at 03:47:19PM +0100, John Kacur wrote: On Fri, 15 Jan 2010, John Kacur wrote: The oops is triggered because I am missing the firmware for radeon/R700_rlc.bin and radeon/R600_rlc.bin However, I think it should be able to deal with this more gracefully. ATOM BIOS: 9498.11.22.6.0.AS03 [drm] Clocks initialized ! [drm] Detected VRAM RAM=256M, BAR=256M [drm] RAM width 128bits DDR [TTM] Zone kernel: Available graphics memory: 3050912 kiB. [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [drm] radeon: 256M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. alloc irq_desc for 33 on node -1 alloc kstat_irqs on node -1 radeon :02:00.0: irq 33 for MSI/MSI-X [drm] radeon: using MSI. [drm] radeon: irq initialized. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV730 Microcode platform radeon_cp.0: firmware: requesting radeon/RV730_pfp.bin platform radeon_cp.0: firmware: requesting radeon/RV730_me.bin platform radeon_cp.0: firmware: requesting radeon/R700_rlc.bin r600_cp: Failed to load firmware radeon/R700_rlc.bin [drm:rv770_startup] *ERROR* Failed to load firmware! radeon :02:00.0: 8801a20b5400 unpin not necessary BUG: unable to handle kernel NULL pointer dereference at 0048 IP: [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] PGD 1a1a74067 PUD 1a19b8067 PMD 0 Oops: [#1] SMP last sysfs file: /sys/devices/platform/radeon_cp.0/firmware/radeon_cp.0/loading CPU 4 Pid: 168, comm: modprobe Not tainted 2.6.33-rc4 #3 EX58-UD3R/EX58-UD3R RIP: 0010:[a0061034] [a0061034] ttm_bo_reserve+0x16/0xf8 [t tm] RSP: 0018:8801a1a8fb68 EFLAGS: 00010292 RAX: 8801 RBX: RCX: RDX: RSI: 0001 RDI: 0048 RBP: 8801a1a8fba8 R08: R09: R10: R11: R12: R13: 8801a8838000 R14: 0024 R15: 2000 FS: 7f0f9c6dc700() GS:88002e40() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 0048 CR3: 0001a195d000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process modprobe (pid: 168, threadinfo 8801a1a8e000, task 8801a22c) Stack: 8801 8801a27e2900 8801a1a8fb88 0 8801a8838000 0024 2000 0 8801a1a8fbd8 a00ba05b 8801a1a8fbd8 8801a27f4000 Call Trace: [a00ba05b] radeon_bo_reserve.clone.0+0x2a/0x6d [radeon] [a00bb441] rv770_suspend+0x43/0x69 [radeon] [a00bb6cf] rv770_init+0x1a4/0x22d [radeon] [a0089593] radeon_device_init+0x27f/0x300 [radeon] [a008a0fb] radeon_driver_load_kms+0xff/0x184 [radeon] [a001e1a6] drm_get_dev+0x3c4/0x4c5 [drm] [8122ea73] ? pci_match_device+0x22/0xd0 [a00c3bb8] radeon_pci_probe+0x15/0x268 [radeon] [8122e941] local_pci_probe+0x17/0x1b [8122f721] pci_device_probe+0xcd/0xfd [812ce793] ? driver_sysfs_add+0x4c/0x71 [812ce95c] driver_probe_device+0xde/0x1fe [812cead9] __driver_attach+0x5d/0x81 [812cea7c] ? __driver_attach+0x0/0x81 [812cdded] bus_for_each_dev+0x59/0x8e [812ce6f2] driver_attach+0x1e/0x20 [812ce330] bus_add_driver+0xd8/0x240 [812cedcb] driver_register+0x9d/0x10e [8122f969] __pci_register_driver+0x68/0xd8 [81439aa2] ? printk+0x41/0x47 [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a0018eb3] drm_init+0x75/0xdb [drm] [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a00f70bf] radeon_init+0xbf/0xc1 [radeon] [81002069] do_one_initcall+0x5e/0x15e [81087788] sys_init_module+0xd8/0x23a [81009bf2] system_call_fastpath+0x16/0x1b Code: 01 00 00 00 31 c0 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f c9 c3 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 18 0f 1f 44 00 00 4c 8b 27 48 89 fb 41 88 f5 41 88 d6 41 88 cf 44 89 45 c8 49 81 RIP [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] RSP 8801a1a8fb68 CR2: 0048 ---[ end trace 604e2e318733e108 ]--- udevd-work[166]: '/sbin/modprobe -b pci:v1002d9498sv1043sd0300bc 03sc00i00' unexpected exit with status 0x0009 I forgot to mention that this is kernel
[Bug 15017] kexec regression, radeon/kms irq related (bisected)
http://bugzilla.kernel.org/show_bug.cgi?id=15017 Rafael J. Wysocki r...@sisk.pl changed: What|Removed |Added Status|RESOLVED|CLOSED Resolution|PATCH_ALREADY_AVAILABLE |CODE_FIX --- Comment #8 from Rafael J. Wysocki r...@sisk.pl 2010-01-26 12:16:28 --- Fixed by: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0c45249f419d8b86abe0e51c6627ca4b085e8c23 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=79c2bbc505751bb5130ac753251fc9a0eb37bb12 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7924e5eb8fe422d6b1ce3b3e2be749a480dfcdd9 -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [OOPS] radeon kms
On Tue, 26 Jan 2010, Gene Heskett wrote: On Tuesday 26 January 2010, John Kacur wrote: On Tue, Jan 26, 2010 at 3:19 PM, Alex Deucher alexdeuc...@gmail.com wrote: On Tue, Jan 26, 2010 at 9:10 AM, John Kacur jka...@redhat.com wrote: On Tue, Jan 26, 2010 at 2:59 PM, Alex Deucher alexdeuc...@gmail.com wrote: On Tue, Jan 26, 2010 at 8:21 AM, John Kacur jka...@redhat.com wrote: On Fri, 15 Jan 2010, Jerome Glisse wrote: On Fri, Jan 15, 2010 at 03:47:19PM +0100, John Kacur wrote: On Fri, 15 Jan 2010, John Kacur wrote: The oops is triggered because I am missing the firmware for radeon/R700_rlc.bin and radeon/R600_rlc.bin However, I think it should be able to deal with this more gracefully. ATOM BIOS: 9498.11.22.6.0.AS03 [drm] Clocks initialized ! [drm] Detected VRAM RAM=256M, BAR=256M [drm] RAM width 128bits DDR [TTM] Zone kernel: Available graphics memory: 3050912 kiB. [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [drm] radeon: 256M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. alloc irq_desc for 33 on node -1 alloc kstat_irqs on node -1 radeon :02:00.0: irq 33 for MSI/MSI-X [drm] radeon: using MSI. [drm] radeon: irq initialized. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV730 Microcode platform radeon_cp.0: firmware: requesting radeon/RV730_pfp.bin platform radeon_cp.0: firmware: requesting radeon/RV730_me.bin platform radeon_cp.0: firmware: requesting radeon/R700_rlc.bin r600_cp: Failed to load firmware radeon/R700_rlc.bin [drm:rv770_startup] *ERROR* Failed to load firmware! radeon :02:00.0: 8801a20b5400 unpin not necessary BUG: unable to handle kernel NULL pointer dereference at 0048 IP: [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] PGD 1a1a74067 PUD 1a19b8067 PMD 0 Oops: [#1] SMP last sysfs file: /sys/devices/platform/radeon_cp.0/firmware/radeon_cp.0/loading CPU 4 Pid: 168, comm: modprobe Not tainted 2.6.33-rc4 #3 EX58-UD3R/EX58-UD3R RIP: 0010:[a0061034] [a0061034] ttm_bo_reserve+0x16/0xf8 [t tm] RSP: 0018:8801a1a8fb68 EFLAGS: 00010292 RAX: 8801 RBX: RCX: RDX: RSI: 0001 RDI: 0048 RBP: 8801a1a8fba8 R08: R09: R10: R11: R12: R13: 8801a8838000 R14: 0024 R15: 2000 FS: 7f0f9c6dc700() GS:88002e40() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 0048 CR3: 0001a195d000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process modprobe (pid: 168, threadinfo 8801a1a8e000, task 8801a22c) Stack: 8801 8801a27e2900 8801a1a8fb88 0 8801a8838000 0024 2000 0 8801a1a8fbd8 a00ba05b 8801a1a8fbd8 8801a27f4000 Call Trace: [a00ba05b] radeon_bo_reserve.clone.0+0x2a/0x6d [radeon] [a00bb441] rv770_suspend+0x43/0x69 [radeon] [a00bb6cf] rv770_init+0x1a4/0x22d [radeon] [a0089593] radeon_device_init+0x27f/0x300 [radeon] [a008a0fb] radeon_driver_load_kms+0xff/0x184 [radeon] [a001e1a6] drm_get_dev+0x3c4/0x4c5 [drm] [8122ea73] ? pci_match_device+0x22/0xd0 [a00c3bb8] radeon_pci_probe+0x15/0x268 [radeon] [8122e941] local_pci_probe+0x17/0x1b [8122f721] pci_device_probe+0xcd/0xfd [812ce793] ? driver_sysfs_add+0x4c/0x71 [812ce95c] driver_probe_device+0xde/0x1fe [812cead9] __driver_attach+0x5d/0x81 [812cea7c] ? __driver_attach+0x0/0x81 [812cdded] bus_for_each_dev+0x59/0x8e [812ce6f2] driver_attach+0x1e/0x20 [812ce330] bus_add_driver+0xd8/0x240 [812cedcb] driver_register+0x9d/0x10e [8122f969] __pci_register_driver+0x68/0xd8 [81439aa2] ? printk+0x41/0x47 [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a0018eb3] drm_init+0x75/0xdb [drm] [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a00f70bf] radeon_init+0xbf/0xc1 [radeon] [81002069] do_one_initcall+0x5e/0x15e [81087788] sys_init_module+0xd8/0x23a [81009bf2] system_call_fastpath+0x16/0x1b Code: 01 00 00 00 31 c0 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f c9 c3 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 18 0f 1f 44 00 00 4c 8b 27 48 89 fb 41 88 f5 41 88 d6 41 88 cf 44 89 45 c8 49 81 RIP [a0061034]
KMS/Radeon rainbow colors when booting .33 kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have been having issues with KMS on 2.6.33-rcX kernels. When I boot with modesetting=1 the kernel begins to load(I see beginnings of kernel loading) then screen turns to a rainbow of colors(think aurora borealis) that begins to fade to grey then black. I have followed the instructions here http://wiki.x.org/wiki/radeonBuildHowTo for my radeon HD3650 card. I have tried both built in and modules for radeon. I am not sure where els to look for issues. Is there anything else I can do to debug or fix this issue? Thanks in advance for any help. - -- Marc R. O'Connor mrocon...@oel.state.nj.us -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAktfJz0ACgkQd+xzezvVnBzwLACfVoFIkrMlgNmAn7Amset9tJ01 ZhUAn0CKF9eIvSMGPGhhJfPUFXK12vo7 =ladW -END PGP SIGNATURE- This E-mail, including any attachments, may be intended solely for the personal and confidential use of the sender and recipient(s) named above. This message may include advisory, consultative and/or deliberative material and, as such, would be privileged and confidential and not a public document. Any Information in this e-mail identifying a client of the Department of Human Services is confidential. If you have received this e-mail in error, you must not review, transmit, convert to hard copy, copy, use or disseminate this e-mail or any attachments to it and you must delete this message. You are requested to notify the sender by return e-mail. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [PATCH] PM / i915: Skip kernel VT switch during suspend/resume if KMS is used
On Tuesday 26 January 2010, Pavel Machek wrote: On Mon 2010-01-25 22:54:37, Rafael J. Wysocki wrote: On Monday 25 January 2010, Alan Cox wrote: But in that case we should be able to disable the VT switch disable path; we just have to check each driver as it's loaded. OK, what the right sequence of checks would be in that case and where to place them? Why are we even driving a vt switch direct from the suspend/resume logic ? The problem starts there. If it was being handled off the device suspend/resume method then there wouldn't be a mess to start with ? Start at the beginning - Why do we switch to arbitarily chosen 'last vt' - Why isn't vt related suspend/resume handled by the device Well, that was added long ago as a workaround for some problems people reported (presumably). I've never looked at that before, so I can't really tell why someone did it this particular way. As X drives hardware, it is/was neccessary to get control out of X and console switch was convenient. Note that it needs to happen with userland still active -- before freezer. Well, that's a bit cumbersome. And yes, it should be per-driver these days. That would have to be done using suspend notifiers and should depend on what driver actually controls the screen at the moment. And I guess the only case in which we actually _need_ to do the kernel VT switch is when the hardware is controlled by X and without KMS. Is there a simple way to determine if that's the case? Rafael -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [OOPS] radeon kms
On Tuesday 26 January 2010, John Kacur wrote: On Tue, 26 Jan 2010, Gene Heskett wrote: On Tuesday 26 January 2010, John Kacur wrote: On Tue, Jan 26, 2010 at 2:59 PM, Alex Deucher alexdeuc...@gmail.com wrote: On Tue, Jan 26, 2010 at 8:21 AM, John Kacur jka...@redhat.com wrote: On Fri, 15 Jan 2010, Jerome Glisse wrote: On Fri, Jan 15, 2010 at 03:47:19PM +0100, John Kacur wrote: On Fri, 15 Jan 2010, John Kacur wrote: The oops is triggered because I am missing the firmware for radeon/R700_rlc.bin and radeon/R600_rlc.bin However, I think it should be able to deal with this more gracefully. ATOM BIOS: 9498.11.22.6.0.AS03 [drm] Clocks initialized ! [drm] Detected VRAM RAM=256M, BAR=256M [drm] RAM width 128bits DDR [TTM] Zone kernel: Available graphics memory: 3050912 kiB. [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [drm] radeon: 256M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. alloc irq_desc for 33 on node -1 alloc kstat_irqs on node -1 radeon :02:00.0: irq 33 for MSI/MSI-X [drm] radeon: using MSI. [drm] radeon: irq initialized. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV730 Microcode platform radeon_cp.0: firmware: requesting radeon/RV730_pfp.bin platform radeon_cp.0: firmware: requesting radeon/RV730_me.bin platform radeon_cp.0: firmware: requesting radeon/R700_rlc.bin r600_cp: Failed to load firmware radeon/R700_rlc.bin [drm:rv770_startup] *ERROR* Failed to load firmware! radeon :02:00.0: 8801a20b5400 unpin not necessary BUG: unable to handle kernel NULL pointer dereference at 0048 IP: [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] PGD 1a1a74067 PUD 1a19b8067 PMD 0 Oops: [#1] SMP last sysfs file: /sys/devices/platform/radeon_cp.0/firmware/radeon_cp.0/loading CPU 4 Pid: 168, comm: modprobe Not tainted 2.6.33-rc4 #3 EX58-UD3R/EX58-UD3R RIP: 0010:[a0061034] [a0061034] ttm_bo_reserve+0x16/0xf8 [t tm] RSP: 0018:8801a1a8fb68 EFLAGS: 00010292 RAX: 8801 RBX: RCX: RDX: RSI: 0001 RDI: 0048 RBP: 8801a1a8fba8 R08: R09: R10: R11: R12: R13: 8801a8838000 R14: 0024 R15: 2000 FS: 7f0f9c6dc700() GS:88002e40() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 0048 CR3: 0001a195d000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process modprobe (pid: 168, threadinfo 8801a1a8e000, task 8801a22c) Stack: 8801 8801a27e2900 8801a1a8fb88 0 8801a8838000 0024 2000 0 8801a1a8fbd8 a00ba05b 8801a1a8fbd8 8801a27f4000 Call Trace: [a00ba05b] radeon_bo_reserve.clone.0+0x2a/0x6d [radeon] [a00bb441] rv770_suspend+0x43/0x69 [radeon] [a00bb6cf] rv770_init+0x1a4/0x22d [radeon] [a0089593] radeon_device_init+0x27f/0x300 [radeon] [a008a0fb] radeon_driver_load_kms+0xff/0x184 [radeon] [a001e1a6] drm_get_dev+0x3c4/0x4c5 [drm] [8122ea73] ? pci_match_device+0x22/0xd0 [a00c3bb8] radeon_pci_probe+0x15/0x268 [radeon] [8122e941] local_pci_probe+0x17/0x1b [8122f721] pci_device_probe+0xcd/0xfd [812ce793] ? driver_sysfs_add+0x4c/0x71 [812ce95c] driver_probe_device+0xde/0x1fe [812cead9] __driver_attach+0x5d/0x81 [812cea7c] ? __driver_attach+0x0/0x81 [812cdded] bus_for_each_dev+0x59/0x8e [812ce6f2] driver_attach+0x1e/0x20 [812ce330] bus_add_driver+0xd8/0x240 [812cedcb] driver_register+0x9d/0x10e [8122f969] __pci_register_driver+0x68/0xd8 [81439aa2] ? printk+0x41/0x47 [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a0018eb3] drm_init+0x75/0xdb [drm] [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a00f70bf] radeon_init+0xbf/0xc1 [radeon] [81002069] do_one_initcall+0x5e/0x15e [81087788] sys_init_module+0xd8/0x23a [81009bf2] system_call_fastpath+0x16/0x1b Code: 01 00 00 00 31 c0 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f c9 c3 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 18 0f 1f 44 00 00 4c 8b 27 48 89 fb 41 88 f5 41 88 d6 41 88 cf 44 89 45 c8 49 81 RIP [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] RSP 8801a1a8fb68 CR2: 0048 ---[ end trace
BUG in i8xx_enable_fbc: unable to handle kernel paging request
Hello, I hope this goes to the correct mailing list: I've observed a freeze today in i8xx_enable_fbc(), module i915 with vanilla Linux 2.6.32.5 running on my Eee PC 1000HG. Kernel log and config is attached. Strangely, this happend just the instant I was going out of scope of wifi hotspot. Could be coincidence... If you need some more information, just ask. Cheers! Thiemo Nagel [37213.532161] No probe response from AP 00:03:52:af:ae:d3 after 500ms, disconnecting. [37214.659548] ath5k phy1: noise floor calibration timeout (2437MHz) [37214.730866] ath5k phy1: failed to wakeup the MAC Chip [37215.020565] ath5k :01:00.0: PCI INT A disabled [37271.867837] BUG: unable to handle kernel paging request at 1b05083a [37271.867864] IP: [f8395032] i8xx_enable_fbc+0xba/0x12e [i915] [37271.867917] *pde = [37271.867929] Oops: 0002 [#1] PREEMPT SMP [37271.867947] last sysfs file: /sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda6/stat [37271.867961] Modules linked in: ufs ntfs vfat msdos fat ext4 jbd2 ext2 usblp ath5k mac80211 ath nfs lockd nfs_acl auth_rpcgss sunrpc ppp_deflate zlib_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc i915 drm_kms_helper drm i2c_algo_bit sco bnep rfcomm l2cap crc16 bluetooth acpi_cpufreq cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats binfmt_misc fuse loop snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_timer uvcvideo snd_seq_device videodev option snd v4l1_compat usbserial eeepc_laptop rtc_cmos soundcore intel_agp usb_storage uhci_hcd rtc_core atl1e rng_core psmouse pci_hotplug evdev ehci_hcd rtc_lib battery ac snd_page_alloc agpgart button processor sha256_generic dm_crypt dm_mod sd_mod thermal fan ata_generic ata_piix libata [37271.868023] [37271.868023] Pid: 2783, comm: Xorg Not tainted (2.6.32.5 #9) 1000HG [37271.868023] EIP: 0060:[f8395032] EFLAGS: 00213282 CPU: 0 [37271.868023] EIP is at i8xx_enable_fbc+0xba/0x12e [i915] [37271.868023] EAX: f71bf800 EBX: fff7 ECX: EDX: f660cc00 [37271.868023] ESI: f6a43800 EDI: 0001 EBP: ef54fe70 ESP: ef54fe4c [37271.868023] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [37271.868023] Process Xorg (pid: 2783, ti=ef54e000 task=f6b1a3a0 task.ti=ef54e000) [37271.868023] Stack: [37271.868023] f838c444 f71bf800 ef533000 f71bf82c f660cc00 0001 ef54fe84 005f [37271.868023] 0 400c645f ef54ff10 f817f7c2 f6af5240 f71bf800 f838c3af 010c 0001 [37271.868023] 0 0001 f6b1a3a0 ef54ff34 c1053aac 011c f6b1a870 [37271.868023] Call Trace: [37271.868023] [f838c444] ? i915_gem_set_domain_ioctl+0x95/0x11f [i915] [37271.868023] [f817f7c2] ? drm_ioctl+0x209/0x289 [drm] [37271.868023] [f838c3af] ? i915_gem_set_domain_ioctl+0x0/0x11f [i915] [37271.868023] [c1053aac] ? __lock_acquire+0xbdd/0xbec [37271.868023] [c128371b] ? _spin_unlock_irq+0x22/0x4a [37271.868023] [c1053cdc] ? lock_release_non_nested+0x84/0x1db [37271.868023] [c105262b] ? trace_hardirqs_on_caller+0xee/0x12f [37271.868023] [c10c08e9] ? vfs_ioctl+0x4e/0x67 [37271.868023] [c10c0e66] ? do_vfs_ioctl+0x4c0/0x4fb [37271.868023] [c109d338] ? might_fault+0x6e/0x88 [37271.868023] [c10c0ee1] ? sys_ioctl+0x40/0x5a [37271.868023] [c1002fa4] ? sysenter_do_call+0x12/0x32 [37271.868023] Code: fa c4 33 00 00 75 ec 31 d2 83 7d e0 00 0f 95 c2 8b 4d f0 83 79 44 00 74 03 83 ca 02 8b 43 08 05 14 32 00 00 89 10 8b 97 ec 00 00 00 8b 43 08 05 1b 32 00 00 89 10 8b 83 d0 01 00 00 0f b6 d0 c1 [37271.868023] EIP: [f8395032] i8xx_enable_fbc+0xba/0x12e [i915] SS:ESP 0068:ef54fe4c [37271.868023] CR2: 1b05083a [37271.869239] ---[ end trace b5a54e5afe0b579f ]--- [37330.495914] pci :01:00.0: reg 10 64bit mmio: [0x00-0x00] [37330.497880] ath5k :01:00.0: enabling device ( - 0002) [37330.497943] ath5k :01:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [37330.498120] ath5k :01:00.0: setting latency timer to 64 [37330.498427] ath5k :01:00.0: registered as 'phy2' [37331.020574] ath: EEPROM regdomain: 0x60 [37331.020588] ath: EEPROM indicates we should expect a direct regpair map [37331.020602] ath: Country alpha2 being used: 00 [37331.020609] ath: Regpair used: 0x60 [37331.022552] phy2: Selected rate control algorithm 'minstrel' [37331.033416] Registered led device: ath5k-phy2::rx [37331.035734] Registered led device: ath5k-phy2::tx [37331.035761] ath5k phy2: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70) [37331.960650] ath5k :01:00.0: PCI INT A disabled [37406.537743] SysRq : Keyboard mode set to system default [37408.373714] SysRq : Emergency Remount R/O config-2.6.32.5.bz2 Description: application/bzip -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and
Re: [PATCH] PM / i915: Skip kernel VT switch during suspend/resume if KMS is used
On Tue 2010-01-26 19:47:45, Rafael J. Wysocki wrote: On Tuesday 26 January 2010, Pavel Machek wrote: On Mon 2010-01-25 22:54:37, Rafael J. Wysocki wrote: On Monday 25 January 2010, Alan Cox wrote: But in that case we should be able to disable the VT switch disable path; we just have to check each driver as it's loaded. OK, what the right sequence of checks would be in that case and where to place them? Why are we even driving a vt switch direct from the suspend/resume logic ? The problem starts there. If it was being handled off the device suspend/resume method then there wouldn't be a mess to start with ? Start at the beginning - Why do we switch to arbitarily chosen 'last vt' - Why isn't vt related suspend/resume handled by the device Well, that was added long ago as a workaround for some problems people reported (presumably). I've never looked at that before, so I can't really tell why someone did it this particular way. As X drives hardware, it is/was neccessary to get control out of X and console switch was convenient. Note that it needs to happen with userland still active -- before freezer. Well, that's a bit cumbersome. (which was one of reasons it got special casing). And yes, it should be per-driver these days. That would have to be done using suspend notifiers and should depend on what driver actually controls the screen at the moment. And I guess the only case in which we actually _need_ to do the kernel VT switch is when the hardware is controlled by X and without KMS. We need vt switch when display is controlled by userland app directly accessing hw. It may or may not be X (svgalib anyone?, gtk-on-framebuffer? qtopia?). Ideally, userspace should explicitely tell us. KD_KERNEL_GRAPHICS console mode? Plus the switch is needed for any graphics app using fbcon -- I do not think we actually save the framebuffer over suspend. (This one should probably be fixed). Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [OOPS] radeon kms
On Tue, Jan 26, 2010 at 9:35 AM, John Kacur jka...@redhat.com wrote: On Tue, Jan 26, 2010 at 3:19 PM, Alex Deucher alexdeuc...@gmail.com wrote: On Tue, Jan 26, 2010 at 9:10 AM, John Kacur jka...@redhat.com wrote: On Tue, Jan 26, 2010 at 2:59 PM, Alex Deucher alexdeuc...@gmail.com wrote: On Tue, Jan 26, 2010 at 8:21 AM, John Kacur jka...@redhat.com wrote: On Fri, 15 Jan 2010, Jerome Glisse wrote: On Fri, Jan 15, 2010 at 03:47:19PM +0100, John Kacur wrote: On Fri, 15 Jan 2010, John Kacur wrote: The oops is triggered because I am missing the firmware for radeon/R700_rlc.bin and radeon/R600_rlc.bin However, I think it should be able to deal with this more gracefully. ATOM BIOS: 9498.11.22.6.0.AS03 [drm] Clocks initialized ! [drm] Detected VRAM RAM=256M, BAR=256M [drm] RAM width 128bits DDR [TTM] Zone kernel: Available graphics memory: 3050912 kiB. [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [drm] radeon: 256M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. alloc irq_desc for 33 on node -1 alloc kstat_irqs on node -1 radeon :02:00.0: irq 33 for MSI/MSI-X [drm] radeon: using MSI. [drm] radeon: irq initialized. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV730 Microcode platform radeon_cp.0: firmware: requesting radeon/RV730_pfp.bin platform radeon_cp.0: firmware: requesting radeon/RV730_me.bin platform radeon_cp.0: firmware: requesting radeon/R700_rlc.bin r600_cp: Failed to load firmware radeon/R700_rlc.bin [drm:rv770_startup] *ERROR* Failed to load firmware! radeon :02:00.0: 8801a20b5400 unpin not necessary BUG: unable to handle kernel NULL pointer dereference at 0048 IP: [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] PGD 1a1a74067 PUD 1a19b8067 PMD 0 Oops: [#1] SMP last sysfs file: /sys/devices/platform/radeon_cp.0/firmware/radeon_cp.0/loading CPU 4 Pid: 168, comm: modprobe Not tainted 2.6.33-rc4 #3 EX58-UD3R/EX58-UD3R RIP: 0010:[a0061034] [a0061034] ttm_bo_reserve+0x16/0xf8 [t tm] RSP: 0018:8801a1a8fb68 EFLAGS: 00010292 RAX: 8801 RBX: RCX: RDX: RSI: 0001 RDI: 0048 RBP: 8801a1a8fba8 R08: R09: R10: R11: R12: R13: 8801a8838000 R14: 0024 R15: 2000 FS: 7f0f9c6dc700() GS:88002e40() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 0048 CR3: 0001a195d000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process modprobe (pid: 168, threadinfo 8801a1a8e000, task 8801a22c) Stack: 8801 8801a27e2900 8801a1a8fb88 0 8801a8838000 0024 2000 0 8801a1a8fbd8 a00ba05b 8801a1a8fbd8 8801a27f4000 Call Trace: [a00ba05b] radeon_bo_reserve.clone.0+0x2a/0x6d [radeon] [a00bb441] rv770_suspend+0x43/0x69 [radeon] [a00bb6cf] rv770_init+0x1a4/0x22d [radeon] [a0089593] radeon_device_init+0x27f/0x300 [radeon] [a008a0fb] radeon_driver_load_kms+0xff/0x184 [radeon] [a001e1a6] drm_get_dev+0x3c4/0x4c5 [drm] [8122ea73] ? pci_match_device+0x22/0xd0 [a00c3bb8] radeon_pci_probe+0x15/0x268 [radeon] [8122e941] local_pci_probe+0x17/0x1b [8122f721] pci_device_probe+0xcd/0xfd [812ce793] ? driver_sysfs_add+0x4c/0x71 [812ce95c] driver_probe_device+0xde/0x1fe [812cead9] __driver_attach+0x5d/0x81 [812cea7c] ? __driver_attach+0x0/0x81 [812cdded] bus_for_each_dev+0x59/0x8e [812ce6f2] driver_attach+0x1e/0x20 [812ce330] bus_add_driver+0xd8/0x240 [812cedcb] driver_register+0x9d/0x10e [8122f969] __pci_register_driver+0x68/0xd8 [81439aa2] ? printk+0x41/0x47 [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a0018eb3] drm_init+0x75/0xdb [drm] [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a00f70bf] radeon_init+0xbf/0xc1 [radeon] [81002069] do_one_initcall+0x5e/0x15e [81087788] sys_init_module+0xd8/0x23a [81009bf2] system_call_fastpath+0x16/0x1b Code: 01 00 00 00 31 c0 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f c9 c3 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 18 0f 1f 44 00 00 4c 8b 27 48 89 fb 41 88 f5 41 88 d6 41 88 cf 44 89 45 c8 49 81 RIP [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] RSP 8801a1a8fb68 CR2: 0048
Re: [OOPS] radeon kms
On Tue, Jan 26, 2010 at 9:20 PM, Alex Deucher alexdeuc...@gmail.com wrote: On Tue, Jan 26, 2010 at 9:35 AM, John Kacur jka...@redhat.com wrote: On Tue, Jan 26, 2010 at 3:19 PM, Alex Deucher alexdeuc...@gmail.com wrote: On Tue, Jan 26, 2010 at 9:10 AM, John Kacur jka...@redhat.com wrote: On Tue, Jan 26, 2010 at 2:59 PM, Alex Deucher alexdeuc...@gmail.com wrote: On Tue, Jan 26, 2010 at 8:21 AM, John Kacur jka...@redhat.com wrote: On Fri, 15 Jan 2010, Jerome Glisse wrote: On Fri, Jan 15, 2010 at 03:47:19PM +0100, John Kacur wrote: On Fri, 15 Jan 2010, John Kacur wrote: The oops is triggered because I am missing the firmware for radeon/R700_rlc.bin and radeon/R600_rlc.bin However, I think it should be able to deal with this more gracefully. ATOM BIOS: 9498.11.22.6.0.AS03 [drm] Clocks initialized ! [drm] Detected VRAM RAM=256M, BAR=256M [drm] RAM width 128bits DDR [TTM] Zone kernel: Available graphics memory: 3050912 kiB. [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [drm] radeon: 256M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. alloc irq_desc for 33 on node -1 alloc kstat_irqs on node -1 radeon :02:00.0: irq 33 for MSI/MSI-X [drm] radeon: using MSI. [drm] radeon: irq initialized. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV730 Microcode platform radeon_cp.0: firmware: requesting radeon/RV730_pfp.bin platform radeon_cp.0: firmware: requesting radeon/RV730_me.bin platform radeon_cp.0: firmware: requesting radeon/R700_rlc.bin r600_cp: Failed to load firmware radeon/R700_rlc.bin [drm:rv770_startup] *ERROR* Failed to load firmware! radeon :02:00.0: 8801a20b5400 unpin not necessary BUG: unable to handle kernel NULL pointer dereference at 0048 IP: [a0061034] ttm_bo_reserve+0x16/0xf8 [ttm] PGD 1a1a74067 PUD 1a19b8067 PMD 0 Oops: [#1] SMP last sysfs file: /sys/devices/platform/radeon_cp.0/firmware/radeon_cp.0/loading CPU 4 Pid: 168, comm: modprobe Not tainted 2.6.33-rc4 #3 EX58-UD3R/EX58-UD3R RIP: 0010:[a0061034] [a0061034] ttm_bo_reserve+0x16/0xf8 [t tm] RSP: 0018:8801a1a8fb68 EFLAGS: 00010292 RAX: 8801 RBX: RCX: RDX: RSI: 0001 RDI: 0048 RBP: 8801a1a8fba8 R08: R09: R10: R11: R12: R13: 8801a8838000 R14: 0024 R15: 2000 FS: 7f0f9c6dc700() GS:88002e40() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 0048 CR3: 0001a195d000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process modprobe (pid: 168, threadinfo 8801a1a8e000, task 8801a22c) Stack: 8801 8801a27e2900 8801a1a8fb88 0 8801a8838000 0024 2000 0 8801a1a8fbd8 a00ba05b 8801a1a8fbd8 8801a27f4000 Call Trace: [a00ba05b] radeon_bo_reserve.clone.0+0x2a/0x6d [radeon] [a00bb441] rv770_suspend+0x43/0x69 [radeon] [a00bb6cf] rv770_init+0x1a4/0x22d [radeon] [a0089593] radeon_device_init+0x27f/0x300 [radeon] [a008a0fb] radeon_driver_load_kms+0xff/0x184 [radeon] [a001e1a6] drm_get_dev+0x3c4/0x4c5 [drm] [8122ea73] ? pci_match_device+0x22/0xd0 [a00c3bb8] radeon_pci_probe+0x15/0x268 [radeon] [8122e941] local_pci_probe+0x17/0x1b [8122f721] pci_device_probe+0xcd/0xfd [812ce793] ? driver_sysfs_add+0x4c/0x71 [812ce95c] driver_probe_device+0xde/0x1fe [812cead9] __driver_attach+0x5d/0x81 [812cea7c] ? __driver_attach+0x0/0x81 [812cdded] bus_for_each_dev+0x59/0x8e [812ce6f2] driver_attach+0x1e/0x20 [812ce330] bus_add_driver+0xd8/0x240 [812cedcb] driver_register+0x9d/0x10e [8122f969] __pci_register_driver+0x68/0xd8 [81439aa2] ? printk+0x41/0x47 [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a0018eb3] drm_init+0x75/0xdb [drm] [a00f7000] ? radeon_init+0x0/0xc1 [radeon] [a00f70bf] radeon_init+0xbf/0xc1 [radeon] [81002069] do_one_initcall+0x5e/0x15e [81087788] sys_init_module+0xd8/0x23a [81009bf2] system_call_fastpath+0x16/0x1b Code: 01 00 00 00 31 c0 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f c9 c3 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 18 0f 1f 44 00 00 4c 8b 27 48 89 fb 41 88 f5 41 88 d6 41 88 cf 44 89 45 c8 49 81 RIP [a0061034]
[Bug 26051] Regression in 7.6, glxgears locks the machine (rv280)
http://bugs.freedesktop.org/show_bug.cgi?id=26051 --- Comment #10 from ken moffat zarniwhoo...@googlemail.com 2010-01-26 14:12:43 PST --- Created an attachment (id=32834) -- (http://bugs.freedesktop.org/attachment.cgi?id=32834) glxinfo without the reverted commit -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26051] Regression in 7.6, glxgears locks the machine (rv280)
http://bugs.freedesktop.org/show_bug.cgi?id=26051 --- Comment #11 from ken moffat zarniwhoo...@googlemail.com 2010-01-26 14:13:47 PST --- Created an attachment (id=32835) -- (http://bugs.freedesktop.org/attachment.cgi?id=32835) glxinfo with 25b492b... reverted -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26051] Regression in 7.6, glxgears locks the machine (rv280)
http://bugs.freedesktop.org/show_bug.cgi?id=26051 --- Comment #12 from ken moffat zarniwhoo...@googlemail.com 2010-01-26 14:18:14 PST --- Thanks for that calm, helpful, and thoughtful reply. Indeed I should have spotted that was an old commit. Thanks for the comment on gitk, it looks as if my plan to build git on a server without xorg (or tcl, tk) was not the best idea. As a non-developer, I have again misunderstood what git-bisect would do. I apologise for the out of order comments. Glxinfo attached for 28471cfa970702128d822c2ecbb1703eedbca245 and with 25b492b976632269dfa3de164545d50a53c090ce reverted - the only thing that changed is the caveat for 32-bit GLX Visuals - 'Ncon' when not working, 'None' when working. k...@bluesbreaker ~ $diff -u glxinfo-with* --- glxinfo-without-revert 2010-01-26 21:47:14.0 + +++ glxinfo-with-revert 2010-01-26 16:04:37.0 + @@ -83,7 +83,7 @@ 0x87 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x88 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x89 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow -0x6c 32 tc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 0 0 Ncon +0x6c 32 tc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 16 GLXFBConfigs: visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[PATCH] drm/ttm: remove padding from ttm_ref_object on 64bit builds
Re-order structure ttm_ref_object to remove 8 bytes of alignment padding
on 64 bit builds, so shrinking its size from 72 to 64 bytes allowing it
to fit into a smaller slab.
Signed-off-by: Richard Kennedy rich...@rsk.demon.co.uk
patch against 2.6.33-rc5
compiled tested on x86_64 AMDX2 and nouveau
regards
Richard
diff --git a/drivers/gpu/drm/ttm/ttm_object.c b/drivers/gpu/drm/ttm/ttm_object.c
index 1099aba..75e9d6f 100644
--- a/drivers/gpu/drm/ttm/ttm_object.c
+++ b/drivers/gpu/drm/ttm/ttm_object.c
@@ -109,8 +109,8 @@ struct ttm_ref_object {
struct drm_hash_item hash;
struct list_head head;
struct kref kref;
- struct ttm_base_object *obj;
enum ttm_ref_type ref_type;
+ struct ttm_base_object *obj;
struct ttm_object_file *tfile;
};
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [PATCH] PM / i915: Skip kernel VT switch during suspend/resume if KMS is used
On Tue 2010-01-26 13:46:01, H. Peter Anvin wrote: On 01/26/2010 06:58 AM, Pavel Machek wrote: That would have to be done using suspend notifiers and should depend on what driver actually controls the screen at the moment. And I guess the only case in which we actually _need_ to do the kernel VT switch is when the hardware is controlled by X and without KMS. We need vt switch when display is controlled by userland app directly accessing hw. It may or may not be X (svgalib anyone?, gtk-on-framebuffer? qtopia?). Ideally, userspace should explicitely tell us. KD_KERNEL_GRAPHICS console mode? It seems that the kernel would already know if it's in control of the mode switch, no? No, I do not think so. IIRC KD_GRAPHICS means console is under userland control; X will use it even if it does not directly talk to the hardware. IOW kernel knows if userland *may* be in control of graphics hardware. (And yes, not switching consoles when console is in KD_TEXT should be easy and obvious optimalization). Currently we have #define KD_TEXT 0x00 #define KD_GRAPHICS 0x01 #define KD_TEXT00x02/* obsolete */ #define KD_TEXT10x03/* obsolete */ I guess KD_KERNEL_GRAPHICS (or KD_INDIRECT_GRAPHICS or KD_GRAPHICS_BUT_KERNEL_CAN_DO_CONSOLE_SWITCHING or something like that) would be needed so that userland can indicate that no, cursor is no longer welcome on the screen but no, it is not accessing hw directly. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26259] New: Wine bloodlines crashes on new game on a Radeon Mobility X700 (PCIE)
http://bugs.freedesktop.org/show_bug.cgi?id=26259 Summary: Wine bloodlines crashes on new game on a Radeon Mobility X700 (PCIE) Product: DRI Version: XOrg CVS Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.sourceforge.net ReportedBy: i30...@gmail.com From here : http://bugs.winehq.org/show_bug.cgi?id=21493 Wine-dbginfo process pid threads parent executable (all id:s are in hex) 000e 4000a 'services.exe' 0011 4000e 'winedevice.exe' 0019 3000e 'winedevice.exe' 0034 6 'vampire.exe' 0038 10034 'explorer.exe' 003c 20034 '~e5.0001' Wine-dbgattach 0x34 0x68000832 GLIBC_2+0x832 in ld-linux.so.2: ret Wine-dbgset $BreakOnFirstChance=0 Wine-dbgcont Unhandled exception: page fault on read access to 0x in 32-bit code (0x4d991190). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:4d991190 ESP:0032d9f4 EBP:0032da3c EFLAGS:00210202( R- -- I - - - ) EAX: EBX:4dbb2ff4 ECX:0001 EDX:7d8f1740 ESI: EDI:7d8f1740 Stack dump: 0x0032d9f4: 7c3d8a98 7c367ca0 0032da3c 4d991e81 0x0032da04: 7ca69268 0x0032da14: 7c36690c 000c 4d973d81 0x0032da24: 7d8f1710 001741a8 4d99115b 4dbb2ff4 0x0032da34: 7c3c3cf0 0001 0032daec 4d974fc7 0x0032da44: 7d8f1740 0001 Backtrace: =0 0x4d991190 radeonEmitVec16+0x40() in r300_dri.so (0x0032da3c) 1 0x4d974fc7 in r300_dri.so (+0x2cfc7) (0x0032daec) 2 0x4da23e66 in r300_dri.so (+0xdbe66) (0x0032db5c) 3 0x4da23fee in r300_dri.so (+0xdbfee) (0x0032db9c) 4 0x4da1b1ce in r300_dri.so (+0xd31ce) (0x0032dbbc) 5 0x20348d14 in wined3d (+0x68d14) (0x0032df6c) 6 0x2031e251 in wined3d (+0x3e251) (0x0032dfbc) 7 0x3bf4b516 in d3d9 (+0xb516) (0x0032e01c) 8 0x2a01203f in shaderapidx9 (+0x1203f) (0x2a068570) 9 0x00490105 (0x2a0527f0) 10 0x2a012580 in shaderapidx9 (+0x12580) (0x2a012470) 0x4d991190 radeonEmitVec16+0x40 in r300_dri.so: movl0x0(%esi),%edx Wine-dbg -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26051] Regression in 7.6, glxgears locks the machine (rv280)
http://bugs.freedesktop.org/show_bug.cgi?id=26051
--- Comment #13 from Dan Nicholson dbn.li...@gmail.com 2010-01-26 16:13:17
PST ---
(In reply to comment #12)
Thanks for that calm, helpful, and thoughtful reply. Indeed I should
have spotted that was an old commit. Thanks for the comment on gitk,
it looks as if my plan to build git on a server without xorg (or tcl,
tk) was not the best idea.
You can try tig (http://jonas.nitro.dk/tig/), which is in ncurses and has a
graph mode ('g') that kind of looks like gitk but less pretty.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
