Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On 11/08/2010 09:53 PM, Jerome Glisse wrote: > On Mon, Nov 8, 2010 at 2:02 PM, Markus Trippelsdorf > wrote: > >> On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: >> >>> On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: >>> On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: > I can trigger a kernel crash on my system by simply loading this png > image with firefox: > http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg > Sorry the above link is wrong, this is the right one (that triggers the crash): http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png >>> I triggered it a few more times and took the attached picture. >>> It points to the BUG() call at drivers/gpu/drm/ttm/ttm_bo.c:1628 . >>> (Sorry for the bad picture quality) >>> >> And here the same BUG in plaintext (should be a bit easier to read): >> >> Nov 8 19:28:23 arch kernel: [ cut here ] >> Nov 8 19:28:23 arch kernel: kernel BUG at drivers/gpu/drm/ttm/ttm_bo.c:1628! >> Nov 8 19:28:23 arch kernel: invalid opcode: [#1] PREEMPT SMP >> Nov 8 19:28:23 arch kernel: last sysfs file: >> /sys/devices/pci:00/:00:18.3/temp1_input >> Nov 8 19:28:23 arch kernel: CPU 1 >> Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Not tainted >> 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name >> Nov 8 19:28:23 arch kernel: RIP: 0010:[] >> [] ttm_bo_init+0x30f/0x340 >> Nov 8 19:28:23 arch kernel: RSP: 0018:88011b0fbbe8 EFLAGS: 00010246 >> Nov 8 19:28:23 arch kernel: RAX: 8800da881778 RBX: 8800da881620 >> RCX: 88011b15ed78 >> Nov 8 19:28:23 arch kernel: RDX: 8800c1556040 RSI: 88011ff22770 >> RDI: 0017adfb >> Nov 8 19:28:23 arch kernel: RBP: 8800da881648 R08: >> R09: 8800c1556040 >> Nov 8 19:28:23 arch kernel: R10: 0ff85205 R11: 8800dae19200 >> R12: 0001 >> Nov 8 19:28:23 arch kernel: R13: 88011ff22528 R14: 88011ff22778 >> R15: >> Nov 8 19:28:23 arch kernel: FS: 7f2043043700() >> GS:8800dfc8() knlGS: >> Nov 8 19:28:23 arch kernel: CS: 0010 DS: ES: CR0: >> 80050033 >> Nov 8 19:28:23 arch kernel: CR2: 7f203d057000 CR3: 00011b12b000 >> CR4: 06e0 >> Nov 8 19:28:23 arch kernel: DR0: DR1: >> DR2: >> Nov 8 19:28:23 arch kernel: DR3: DR6: 0ff0 >> DR7: 0400 >> Nov 8 19:28:23 arch kernel: Process X (pid: 1541, threadinfo >> 88011b0fa000, task 88011c959c20) >> Nov 8 19:28:23 arch kernel: Stack: >> Nov 8 19:28:23 arch kernel: 8800da881648 >> 88011b0fbd00 8800da881600 >> Nov 8 19:28:23 arch kernel: 88011ff22000 >> 0001 fff4 >> Nov 8 19:28:23 arch kernel: 88011b0fbd00 8125294d >> 0001 >> Nov 8 19:28:23 arch kernel: Call Trace: >> Nov 8 19:28:23 arch kernel: [] ? >> radeon_bo_create+0x14d/0x250 >> Nov 8 19:28:23 arch kernel: [] ? >> radeon_ttm_bo_destroy+0x0/0xb0 >> Nov 8 19:28:23 arch kernel: [] ? >> radeon_gem_object_create+0x8c/0x130 >> Nov 8 19:28:23 arch kernel: [] ? >> radeon_gem_create_ioctl+0x54/0xd0 >> Nov 8 19:28:23 arch kernel: [] ? sock_aio_read+0x10d/0x120 >> Nov 8 19:28:23 arch kernel: [] ? drm_ioctl+0x39c/0x450 >> Nov 8 19:28:23 arch kernel: [] ? >> radeon_gem_create_ioctl+0x0/0xd0 >> Nov 8 19:28:23 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610 >> Nov 8 19:28:23 arch kernel: [] ? sys_ioctl+0x49/0x80 >> Nov 8 19:28:23 arch kernel: [] ? sys_read+0x4e/0x90 >> Nov 8 19:28:23 arch kernel: [] ? >> system_call_fastpath+0x16/0x1b >> Nov 8 19:28:23 arch kernel: Code: e8 fb ff ff 85 c0 0f 85 68 ff ff ff 48 8b >> 7c 24 08 89 04 24 e8 83 d9 ff ff 8b 04 24 48 83 c4 18 5b 5d 41 5c 41 5d 41 >> 5e 41 5f c3<0f> 0b 48 c7 c7 60 a4 55 81 31 c0 e8 14 80 22 00 b8 ea ff ff ff >> Nov 8 19:28:23 arch kernel: RIP [] >> ttm_bo_init+0x30f/0x340 >> Nov 8 19:28:23 arch kernel: RSP >> Nov 8 19:28:23 arch kernel: ---[ end trace 328a9acba7691d6e ]--- >> Nov 8 19:28:23 arch kernel: note: X[1541] exited with preempt_count 1 >> Nov 8 19:28:23 arch kernel: BUG: scheduling while atomic: X/1541/0x1002 >> Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Tainted: G D >> 2.6.37-rc1-00116-g151f52f-dirty #31 >> Nov 8 19:28:23 arch kernel: Call Trace: >> Nov 8 19:28:23 arch kernel: [] ? schedule+0x639/0x850 >> Nov 8 19:28:23 arch kernel: [] ? __cond_resched+0x1d/0x30 >> Nov 8 19:28:23 arch kernel: [] ? _cond_resched+0x2f/0x40 >> Nov 8 19:28:23 arch kernel: [] ? unmap_vmas+0x82c/0x9c0 >> Nov 8 19:28:23 arch kernel: [] ? exit_mmap+0xe2/0x1a0 >> Nov 8 19:28:23 arch ker
Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On 11/08/2010 09:58 PM, Rafael J. Wysocki wrote: > On Monday, November 08, 2010, Jerome Glisse wrote: > >> On Mon, Nov 8, 2010 at 2:02 PM, Markus Trippelsdorf >> wrote: >> >>> On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: >>> On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: > On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: > >> I can trigger a kernel crash on my system by simply loading this png >> image with firefox: >> http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg >> > Sorry the above link is wrong, this is the right one (that triggers the > crash): > http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png > I triggered it a few more times and took the attached picture. It points to the BUG() call at drivers/gpu/drm/ttm/ttm_bo.c:1628 . (Sorry for the bad picture quality) >>> And here the same BUG in plaintext (should be a bit easier to read): >>> >>> Nov 8 19:28:23 arch kernel: [ cut here ] >>> Nov 8 19:28:23 arch kernel: kernel BUG at >>> drivers/gpu/drm/ttm/ttm_bo.c:1628! >>> Nov 8 19:28:23 arch kernel: invalid opcode: [#1] PREEMPT SMP >>> Nov 8 19:28:23 arch kernel: last sysfs file: >>> /sys/devices/pci:00/:00:18.3/temp1_input >>> Nov 8 19:28:23 arch kernel: CPU 1 >>> Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Not tainted >>> 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name >>> Nov 8 19:28:23 arch kernel: RIP: 0010:[] >>> [] ttm_bo_init+0x30f/0x340 >>> Nov 8 19:28:23 arch kernel: RSP: 0018:88011b0fbbe8 EFLAGS: 00010246 >>> Nov 8 19:28:23 arch kernel: RAX: 8800da881778 RBX: 8800da881620 >>> RCX: 88011b15ed78 >>> Nov 8 19:28:23 arch kernel: RDX: 8800c1556040 RSI: 88011ff22770 >>> RDI: 0017adfb >>> Nov 8 19:28:23 arch kernel: RBP: 8800da881648 R08: >>> R09: 8800c1556040 >>> Nov 8 19:28:23 arch kernel: R10: 0ff85205 R11: 8800dae19200 >>> R12: 0001 >>> Nov 8 19:28:23 arch kernel: R13: 88011ff22528 R14: 88011ff22778 >>> R15: >>> Nov 8 19:28:23 arch kernel: FS: 7f2043043700() >>> GS:8800dfc8() knlGS: >>> Nov 8 19:28:23 arch kernel: CS: 0010 DS: ES: CR0: >>> 80050033 >>> Nov 8 19:28:23 arch kernel: CR2: 7f203d057000 CR3: 00011b12b000 >>> CR4: 06e0 >>> Nov 8 19:28:23 arch kernel: DR0: DR1: >>> DR2: >>> Nov 8 19:28:23 arch kernel: DR3: DR6: 0ff0 >>> DR7: 0400 >>> Nov 8 19:28:23 arch kernel: Process X (pid: 1541, threadinfo >>> 88011b0fa000, task 88011c959c20) >>> Nov 8 19:28:23 arch kernel: Stack: >>> Nov 8 19:28:23 arch kernel: 8800da881648 >>> 88011b0fbd00 8800da881600 >>> Nov 8 19:28:23 arch kernel: 88011ff22000 >>> 0001 fff4 >>> Nov 8 19:28:23 arch kernel: 88011b0fbd00 8125294d >>> 0001 >>> Nov 8 19:28:23 arch kernel: Call Trace: >>> Nov 8 19:28:23 arch kernel: [] ? >>> radeon_bo_create+0x14d/0x250 >>> Nov 8 19:28:23 arch kernel: [] ? >>> radeon_ttm_bo_destroy+0x0/0xb0 >>> Nov 8 19:28:23 arch kernel: [] ? >>> radeon_gem_object_create+0x8c/0x130 >>> Nov 8 19:28:23 arch kernel: [] ? >>> radeon_gem_create_ioctl+0x54/0xd0 >>> Nov 8 19:28:23 arch kernel: [] ? >>> sock_aio_read+0x10d/0x120 >>> Nov 8 19:28:23 arch kernel: [] ? drm_ioctl+0x39c/0x450 >>> Nov 8 19:28:23 arch kernel: [] ? >>> radeon_gem_create_ioctl+0x0/0xd0 >>> Nov 8 19:28:23 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610 >>> Nov 8 19:28:23 arch kernel: [] ? sys_ioctl+0x49/0x80 >>> Nov 8 19:28:23 arch kernel: [] ? sys_read+0x4e/0x90 >>> Nov 8 19:28:23 arch kernel: [] ? >>> system_call_fastpath+0x16/0x1b >>> Nov 8 19:28:23 arch kernel: Code: e8 fb ff ff 85 c0 0f 85 68 ff ff ff 48 >>> 8b 7c 24 08 89 04 24 e8 83 d9 ff ff 8b 04 24 48 83 c4 18 5b 5d 41 5c 41 5d >>> 41 5e 41 5f c3<0f> 0b 48 c7 c7 60 a4 55 81 31 c0 e8 14 80 22 00 b8 ea ff >>> ff ff >>> Nov 8 19:28:23 arch kernel: RIP [] >>> ttm_bo_init+0x30f/0x340 >>> Nov 8 19:28:23 arch kernel: RSP >>> Nov 8 19:28:23 arch kernel: ---[ end trace 328a9acba7691d6e ]--- >>> Nov 8 19:28:23 arch kernel: note: X[1541] exited with preempt_count 1 >>> Nov 8 19:28:23 arch kernel: BUG: scheduling while atomic: X/1541/0x1002 >>> Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Tainted: G D >>> 2.6.37-rc1-00116-g151f52f-dirty #31 >>> Nov 8 19:28:23 arch kernel: Call Trace: >>> Nov 8 19:28:23 arch kernel: [] ? schedule+0x639/0x850 >>> Nov 8 19:28:23 arch kernel: [] ? __cond_resched+0x1d/0x30 >>> Nov 8 19:28:23
Re: [PATCH 2/2] drm/ttm: track kmap io_reserve(), only unreserve on unmap where needed
On 11/09/2010 04:03 AM, Ben Skeggs wrote:
On Thu, 2010-11-04 at 19:34 +0100, Thomas Hellstrom wrote:
Ben,
I had something like the attached in mind, although it might be more
beneficial to do the actual refcounting in drivers that needs it. Atomic
incs and decs are expensive, but I'm not sure how expensive relative to
function pointer calls.
Thomas,
Thanks for that :) It looks good to me, and appears to work as it
should.
Ben.
Great.
I have a question, though. (CC'ing Jerome as well)
Seems to me like something is missing from the mem_reserve interface.
Let's say you have a programmable VRAM aperture and it's full, so you
can't honor bo map request. You'd then want to traverse a list and call
unmap_mapping_range() to kill user-space maps and free VRAM aperture
space, but you can't really do that since you don't have access to the
mapping range in question...?
/Thomas
Patch is only compile-tested
/Thomas
On 11/04/2010 02:08 PM, Thomas Hellstrom wrote:
On 11/04/2010 01:03 AM, Ben Skeggs wrote:
From: Ben Skeggs
If the driver kmaps an object userspace is expecting to be mapped, the
unmap would have called down into the drivers io_unreserve() function
and potentially unmapped the pages from its BARs (for example) and
they'd
no longer be accessible for the userspace mapping.
Signed-off-by: Ben Skeggs
---
drivers/gpu/drm/ttm/ttm_bo_util.c | 14 ++
include/drm/ttm/ttm_bo_api.h |1 +
2 files changed, 11 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo_util.c
b/drivers/gpu/drm/ttm/ttm_bo_util.c
index ff358ad..e9dbe8b 100644
--- a/drivers/gpu/drm/ttm/ttm_bo_util.c
+++ b/drivers/gpu/drm/ttm/ttm_bo_util.c
@@ -467,9 +467,12 @@ int ttm_bo_kmap(struct ttm_buffer_object *bo,
if (num_pages> 1&& !DRM_SUSER(DRM_CURPROC))
return -EPERM;
#endif
-ret = ttm_mem_io_reserve(bo->bdev,&bo->mem);
-if (ret)
-return ret;
+if (!bo->mem.bus.io_reserved) {
+ret = ttm_mem_io_reserve(bo->bdev,&bo->mem);
+if (ret)
+return ret;
+map->io_reserved = true;
+}
if (!bo->mem.bus.is_iomem) {
return ttm_bo_kmap_ttm(bo, start_page, num_pages, map);
} else {
@@ -487,7 +490,10 @@ void ttm_bo_kunmap(struct ttm_bo_kmap_obj *map)
switch (map->bo_kmap_type) {
case ttm_bo_map_iomap:
iounmap(map->virtual);
-ttm_mem_io_free(map->bo->bdev,&map->bo->mem);
+if (map->io_reserved) {
+ttm_mem_io_free(map->bo->bdev,&map->bo->mem);
+map->io_reserved = false;
+}
break;
case ttm_bo_map_vmap:
vunmap(map->virtual);
diff --git a/include/drm/ttm/ttm_bo_api.h b/include/drm/ttm/ttm_bo_api.h
index 5afa5b5..ce998ac 100644
--- a/include/drm/ttm/ttm_bo_api.h
+++ b/include/drm/ttm/ttm_bo_api.h
@@ -300,6 +300,7 @@ struct ttm_bo_kmap_obj {
ttm_bo_map_premapped= 4 | TTM_BO_MAP_IOMEM_MASK,
} bo_kmap_type;
struct ttm_buffer_object *bo;
+bool io_reserved;
};
/**
This doesn't solve the problem unfortunately. Consider the sequence
kmap->io_mem_reserve
fault()->
kunmap->io_mem_free
user_space_access()-> Invalid.
I think this needs to be fixed by us maintaining an
mem:io_reserved_count, where all user-space triggered io_reserves
count as 1. A mem::user_space_io_reserved flag could be protected by
the bo::reserve lock, whereas a reserved_count can't, since strictly
you're allowed to kmap a bo without reserving it, but only if it's pinned
/Thomas
.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31482] When trying to put the fullscreen window, data show and LCD laptop screen, the screen windwos screw up
https://bugs.freedesktop.org/show_bug.cgi?id=31482 --- Comment #1 from Alex Deucher 2010-11-08 22:00:23 PST --- Does the "hardware button" generate an acpi event or do something else (like banging the hw directly behind the driver's back)? What system is this? Please attach your xorg log and dmesg output. -- 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 31482] When trying to put the fullscreen window, data show and LCD laptop screen, the screen windwos screw up
https://bugs.freedesktop.org/show_bug.cgi?id=31482 --- Comment #1 from Alex Deucher 2010-11-08 22:00:23 PST --- Does the "hardware button" generate an acpi event or do something else (like banging the hw directly behind the driver's back)? What system is this? Please attach your xorg log and dmesg output. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On Monday, November 08, 2010, Jerome Glisse wrote: > On Mon, Nov 8, 2010 at 2:02 PM, Markus Trippelsdorf > wrote: > > On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: > >> On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: > >> > On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: > >> > > I can trigger a kernel crash on my system by simply loading this png > >> > > image with firefox: > >> > > http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg > >> > > >> > Sorry the above link is wrong, this is the right one (that triggers the > >> > crash): > >> > http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png > >> > >> I triggered it a few more times and took the attached picture. > >> It points to the BUG() call at drivers/gpu/drm/ttm/ttm_bo.c:1628 . > >> (Sorry for the bad picture quality) > > > > And here the same BUG in plaintext (should be a bit easier to read): > > > > Nov 8 19:28:23 arch kernel: [ cut here ] > > Nov 8 19:28:23 arch kernel: kernel BUG at > > drivers/gpu/drm/ttm/ttm_bo.c:1628! > > Nov 8 19:28:23 arch kernel: invalid opcode: [#1] PREEMPT SMP > > Nov 8 19:28:23 arch kernel: last sysfs file: > > /sys/devices/pci:00/:00:18.3/temp1_input > > Nov 8 19:28:23 arch kernel: CPU 1 > > Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Not tainted > > 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name > > Nov 8 19:28:23 arch kernel: RIP: 0010:[] > > [] ttm_bo_init+0x30f/0x340 > > Nov 8 19:28:23 arch kernel: RSP: 0018:88011b0fbbe8 EFLAGS: 00010246 > > Nov 8 19:28:23 arch kernel: RAX: 8800da881778 RBX: 8800da881620 > > RCX: 88011b15ed78 > > Nov 8 19:28:23 arch kernel: RDX: 8800c1556040 RSI: 88011ff22770 > > RDI: 0017adfb > > Nov 8 19:28:23 arch kernel: RBP: 8800da881648 R08: > > R09: 8800c1556040 > > Nov 8 19:28:23 arch kernel: R10: 0ff85205 R11: 8800dae19200 > > R12: 0001 > > Nov 8 19:28:23 arch kernel: R13: 88011ff22528 R14: 88011ff22778 > > R15: > > Nov 8 19:28:23 arch kernel: FS: 7f2043043700() > > GS:8800dfc8() knlGS: > > Nov 8 19:28:23 arch kernel: CS: 0010 DS: ES: CR0: > > 80050033 > > Nov 8 19:28:23 arch kernel: CR2: 7f203d057000 CR3: 00011b12b000 > > CR4: 06e0 > > Nov 8 19:28:23 arch kernel: DR0: DR1: > > DR2: > > Nov 8 19:28:23 arch kernel: DR3: DR6: 0ff0 > > DR7: 0400 > > Nov 8 19:28:23 arch kernel: Process X (pid: 1541, threadinfo > > 88011b0fa000, task 88011c959c20) > > Nov 8 19:28:23 arch kernel: Stack: > > Nov 8 19:28:23 arch kernel: 8800da881648 > > 88011b0fbd00 8800da881600 > > Nov 8 19:28:23 arch kernel: 88011ff22000 > > 0001 fff4 > > Nov 8 19:28:23 arch kernel: 88011b0fbd00 8125294d > > 0001 > > Nov 8 19:28:23 arch kernel: Call Trace: > > Nov 8 19:28:23 arch kernel: [] ? > > radeon_bo_create+0x14d/0x250 > > Nov 8 19:28:23 arch kernel: [] ? > > radeon_ttm_bo_destroy+0x0/0xb0 > > Nov 8 19:28:23 arch kernel: [] ? > > radeon_gem_object_create+0x8c/0x130 > > Nov 8 19:28:23 arch kernel: [] ? > > radeon_gem_create_ioctl+0x54/0xd0 > > Nov 8 19:28:23 arch kernel: [] ? > > sock_aio_read+0x10d/0x120 > > Nov 8 19:28:23 arch kernel: [] ? drm_ioctl+0x39c/0x450 > > Nov 8 19:28:23 arch kernel: [] ? > > radeon_gem_create_ioctl+0x0/0xd0 > > Nov 8 19:28:23 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610 > > Nov 8 19:28:23 arch kernel: [] ? sys_ioctl+0x49/0x80 > > Nov 8 19:28:23 arch kernel: [] ? sys_read+0x4e/0x90 > > Nov 8 19:28:23 arch kernel: [] ? > > system_call_fastpath+0x16/0x1b > > Nov 8 19:28:23 arch kernel: Code: e8 fb ff ff 85 c0 0f 85 68 ff ff ff 48 > > 8b 7c 24 08 89 04 24 e8 83 d9 ff ff 8b 04 24 48 83 c4 18 5b 5d 41 5c 41 5d > > 41 5e 41 5f c3 <0f> 0b 48 c7 c7 60 a4 55 81 31 c0 e8 14 80 22 00 b8 ea ff > > ff ff > > Nov 8 19:28:23 arch kernel: RIP [] > > ttm_bo_init+0x30f/0x340 > > Nov 8 19:28:23 arch kernel: RSP > > Nov 8 19:28:23 arch kernel: ---[ end trace 328a9acba7691d6e ]--- > > Nov 8 19:28:23 arch kernel: note: X[1541] exited with preempt_count 1 > > Nov 8 19:28:23 arch kernel: BUG: scheduling while atomic: X/1541/0x1002 > > Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Tainted: G D > > 2.6.37-rc1-00116-g151f52f-dirty #31 > > Nov 8 19:28:23 arch kernel: Call Trace: > > Nov 8 19:28:23 arch kernel: [] ? schedule+0x639/0x850 > > Nov 8 19:28:23 arch kernel: [] ? __cond_resched+0x1d/0x30 > > Nov 8 19:28:23 arch kernel: [] ? _cond_resched+0x2f/0x40 > > Nov 8 19:28:23 arch kernel: [] ? unmap_vmas+0x82c/0x9c0 > > Nov 8 19:28:23 arch kernel: [] ?
Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: > On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: > > On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: > > > I can trigger a kernel crash on my system by simply loading this png > > > image with firefox: > > > http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg > > > > Sorry the above link is wrong, this is the right one (that triggers the > > crash): > > http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png > > I triggered it a few more times and took the attached picture. > It points to the BUG() call at drivers/gpu/drm/ttm/ttm_bo.c:1628 . > (Sorry for the bad picture quality) And here the same BUG in plaintext (should be a bit easier to read): Nov 8 19:28:23 arch kernel: [ cut here ] Nov 8 19:28:23 arch kernel: kernel BUG at drivers/gpu/drm/ttm/ttm_bo.c:1628! Nov 8 19:28:23 arch kernel: invalid opcode: [#1] PREEMPT SMP Nov 8 19:28:23 arch kernel: last sysfs file: /sys/devices/pci:00/:00:18.3/temp1_input Nov 8 19:28:23 arch kernel: CPU 1 Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Not tainted 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name Nov 8 19:28:23 arch kernel: RIP: 0010:[] [] ttm_bo_init+0x30f/0x340 Nov 8 19:28:23 arch kernel: RSP: 0018:88011b0fbbe8 EFLAGS: 00010246 Nov 8 19:28:23 arch kernel: RAX: 8800da881778 RBX: 8800da881620 RCX: 88011b15ed78 Nov 8 19:28:23 arch kernel: RDX: 8800c1556040 RSI: 88011ff22770 RDI: 0017adfb Nov 8 19:28:23 arch kernel: RBP: 8800da881648 R08: R09: 8800c1556040 Nov 8 19:28:23 arch kernel: R10: 0ff85205 R11: 8800dae19200 R12: 0001 Nov 8 19:28:23 arch kernel: R13: 88011ff22528 R14: 88011ff22778 R15: Nov 8 19:28:23 arch kernel: FS: 7f2043043700() GS:8800dfc8() knlGS: Nov 8 19:28:23 arch kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 8 19:28:23 arch kernel: CR2: 7f203d057000 CR3: 00011b12b000 CR4: 06e0 Nov 8 19:28:23 arch kernel: DR0: DR1: DR2: Nov 8 19:28:23 arch kernel: DR3: DR6: 0ff0 DR7: 0400 Nov 8 19:28:23 arch kernel: Process X (pid: 1541, threadinfo 88011b0fa000, task 88011c959c20) Nov 8 19:28:23 arch kernel: Stack: Nov 8 19:28:23 arch kernel: 8800da881648 88011b0fbd00 8800da881600 Nov 8 19:28:23 arch kernel: 88011ff22000 0001 fff4 Nov 8 19:28:23 arch kernel: 88011b0fbd00 8125294d 0001 Nov 8 19:28:23 arch kernel: Call Trace: Nov 8 19:28:23 arch kernel: [] ? radeon_bo_create+0x14d/0x250 Nov 8 19:28:23 arch kernel: [] ? radeon_ttm_bo_destroy+0x0/0xb0 Nov 8 19:28:23 arch kernel: [] ? radeon_gem_object_create+0x8c/0x130 Nov 8 19:28:23 arch kernel: [] ? radeon_gem_create_ioctl+0x54/0xd0 Nov 8 19:28:23 arch kernel: [] ? sock_aio_read+0x10d/0x120 Nov 8 19:28:23 arch kernel: [] ? drm_ioctl+0x39c/0x450 Nov 8 19:28:23 arch kernel: [] ? radeon_gem_create_ioctl+0x0/0xd0 Nov 8 19:28:23 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610 Nov 8 19:28:23 arch kernel: [] ? sys_ioctl+0x49/0x80 Nov 8 19:28:23 arch kernel: [] ? sys_read+0x4e/0x90 Nov 8 19:28:23 arch kernel: [] ? system_call_fastpath+0x16/0x1b Nov 8 19:28:23 arch kernel: Code: e8 fb ff ff 85 c0 0f 85 68 ff ff ff 48 8b 7c 24 08 89 04 24 e8 83 d9 ff ff 8b 04 24 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 <0f> 0b 48 c7 c7 60 a4 55 81 31 c0 e8 14 80 22 00 b8 ea ff ff ff Nov 8 19:28:23 arch kernel: RIP [] ttm_bo_init+0x30f/0x340 Nov 8 19:28:23 arch kernel: RSP Nov 8 19:28:23 arch kernel: ---[ end trace 328a9acba7691d6e ]--- Nov 8 19:28:23 arch kernel: note: X[1541] exited with preempt_count 1 Nov 8 19:28:23 arch kernel: BUG: scheduling while atomic: X/1541/0x1002 Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Tainted: G D 2.6.37-rc1-00116-g151f52f-dirty #31 Nov 8 19:28:23 arch kernel: Call Trace: Nov 8 19:28:23 arch kernel: [] ? schedule+0x639/0x850 Nov 8 19:28:23 arch kernel: [] ? __cond_resched+0x1d/0x30 Nov 8 19:28:23 arch kernel: [] ? _cond_resched+0x2f/0x40 Nov 8 19:28:23 arch kernel: [] ? unmap_vmas+0x82c/0x9c0 Nov 8 19:28:23 arch kernel: [] ? exit_mmap+0xe2/0x1a0 Nov 8 19:28:23 arch kernel: [] ? mmput+0x25/0xc0 Nov 8 19:28:23 arch kernel: [] ? exit_mm+0x104/0x130 Nov 8 19:28:23 arch kernel: [] ? hrtimer_try_to_cancel+0x3f/0x80 Nov 8 19:28:23 arch kernel: [] ? acct_collect+0x9a/0x1a0 Nov 8 19:28:23 arch kernel: [] ? do_exit+0x5aa/0x760 Nov 8 19:28:23 arch kernel: [] ? printk+0x40/0x45 Nov 8 19:28:23 arch kernel: [] ? kmsg_dump+0x7c/0x150 Nov 8 19:28:23 arch kernel: [] ? oops_end+0x9a/0xe0 Nov 8 19:28:23 arch
Re: [PATCH 2/2] drm/ttm: track kmap io_reserve(), only unreserve on unmap where needed
On Thu, 2010-11-04 at 19:34 +0100, Thomas Hellstrom wrote:
> Ben,
>
> I had something like the attached in mind, although it might be more
> beneficial to do the actual refcounting in drivers that needs it. Atomic
> incs and decs are expensive, but I'm not sure how expensive relative to
> function pointer calls.
Thomas,
Thanks for that :) It looks good to me, and appears to work as it
should.
Ben.
>
> Patch is only compile-tested
>
> /Thomas
>
>
> On 11/04/2010 02:08 PM, Thomas Hellstrom wrote:
> > On 11/04/2010 01:03 AM, Ben Skeggs wrote:
> >> From: Ben Skeggs
> >>
> >> If the driver kmaps an object userspace is expecting to be mapped, the
> >> unmap would have called down into the drivers io_unreserve() function
> >> and potentially unmapped the pages from its BARs (for example) and
> >> they'd
> >> no longer be accessible for the userspace mapping.
> >>
> >> Signed-off-by: Ben Skeggs
> >> ---
> >> drivers/gpu/drm/ttm/ttm_bo_util.c | 14 ++
> >> include/drm/ttm/ttm_bo_api.h |1 +
> >> 2 files changed, 11 insertions(+), 4 deletions(-)
> >>
> >> diff --git a/drivers/gpu/drm/ttm/ttm_bo_util.c
> >> b/drivers/gpu/drm/ttm/ttm_bo_util.c
> >> index ff358ad..e9dbe8b 100644
> >> --- a/drivers/gpu/drm/ttm/ttm_bo_util.c
> >> +++ b/drivers/gpu/drm/ttm/ttm_bo_util.c
> >> @@ -467,9 +467,12 @@ int ttm_bo_kmap(struct ttm_buffer_object *bo,
> >> if (num_pages> 1&& !DRM_SUSER(DRM_CURPROC))
> >> return -EPERM;
> >> #endif
> >> -ret = ttm_mem_io_reserve(bo->bdev,&bo->mem);
> >> -if (ret)
> >> -return ret;
> >> +if (!bo->mem.bus.io_reserved) {
> >> +ret = ttm_mem_io_reserve(bo->bdev,&bo->mem);
> >> +if (ret)
> >> +return ret;
> >> +map->io_reserved = true;
> >> +}
> >> if (!bo->mem.bus.is_iomem) {
> >> return ttm_bo_kmap_ttm(bo, start_page, num_pages, map);
> >> } else {
> >> @@ -487,7 +490,10 @@ void ttm_bo_kunmap(struct ttm_bo_kmap_obj *map)
> >> switch (map->bo_kmap_type) {
> >> case ttm_bo_map_iomap:
> >> iounmap(map->virtual);
> >> -ttm_mem_io_free(map->bo->bdev,&map->bo->mem);
> >> +if (map->io_reserved) {
> >> +ttm_mem_io_free(map->bo->bdev,&map->bo->mem);
> >> +map->io_reserved = false;
> >> +}
> >> break;
> >> case ttm_bo_map_vmap:
> >> vunmap(map->virtual);
> >> diff --git a/include/drm/ttm/ttm_bo_api.h b/include/drm/ttm/ttm_bo_api.h
> >> index 5afa5b5..ce998ac 100644
> >> --- a/include/drm/ttm/ttm_bo_api.h
> >> +++ b/include/drm/ttm/ttm_bo_api.h
> >> @@ -300,6 +300,7 @@ struct ttm_bo_kmap_obj {
> >> ttm_bo_map_premapped= 4 | TTM_BO_MAP_IOMEM_MASK,
> >> } bo_kmap_type;
> >> struct ttm_buffer_object *bo;
> >> +bool io_reserved;
> >> };
> >>
> >> /**
> >>
> >
> > This doesn't solve the problem unfortunately. Consider the sequence
> >
> > kmap->io_mem_reserve
> > fault()->
> > kunmap->io_mem_free
> > user_space_access()-> Invalid.
> >
> > I think this needs to be fixed by us maintaining an
> > mem:io_reserved_count, where all user-space triggered io_reserves
> > count as 1. A mem::user_space_io_reserved flag could be protected by
> > the bo::reserve lock, whereas a reserved_count can't, since strictly
> > you're allowed to kmap a bo without reserving it, but only if it's pinned
> >
> > /Thomas
> > .
> >
> >
> > ___
> > dri-devel mailing list
> > dri-devel@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/dri-devel
>
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] drm/radeon/kms: fix thermal sensor reporting on rv6xx
On Mon, Nov 8, 2010 at 1:39 PM, Alex Deucher wrote:
> Temperature is not shifted as on newer asics.
>
> Signed-off-by: Alex Deucher
Should be CC'ed to stable as well.
Alex
> ---
> ?drivers/gpu/drm/radeon/r600.c | ? ?8 +---
> ?1 files changed, 1 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/r600.c b/drivers/gpu/drm/radeon/r600.c
> index 951af00..bd69299 100644
> --- a/drivers/gpu/drm/radeon/r600.c
> +++ b/drivers/gpu/drm/radeon/r600.c
> @@ -106,14 +106,8 @@ u32 rv6xx_get_temp(struct radeon_device *rdev)
> ?{
> ? ? ? ?u32 temp = (RREG32(CG_THERMAL_STATUS) & ASIC_T_MASK) >>
> ? ? ? ? ? ? ? ?ASIC_T_SHIFT;
> - ? ? ? u32 actual_temp = 0;
>
> - ? ? ? if ((temp >> 7) & 1)
> - ? ? ? ? ? ? ? actual_temp = 0;
> - ? ? ? else
> - ? ? ? ? ? ? ? actual_temp = (temp >> 1) & 0xff;
> -
> - ? ? ? return actual_temp * 1000;
> + ? ? ? return temp * 1000;
> ?}
>
> ?void r600_pm_get_dynpm_state(struct radeon_device *rdev)
> --
> 1.7.1.1
>
>
Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: > I can trigger a kernel crash on my system by simply loading this png > image with firefox: > http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg Sorry the above link is wrong, this is the right one (that triggers the crash): http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png -- Markus
Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
I can trigger a kernel crash on my system by simply loading this png image with firefox: http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg The system has an embedded RS780 and is running the latest git kernel. (Xorg.0.log is attached) The crash looks as follows: Nov 8 17:37:21 arch kernel: BUG: unable to handle kernel NULL pointer dereference at 0020 Nov 8 17:37:21 arch kernel: IP: [] _raw_write_lock+0xf/0x20 Nov 8 17:37:21 arch kernel: PGD 11bf20067 PUD 11bfa7067 PMD 0 Nov 8 17:37:21 arch kernel: Oops: 0002 [#1] PREEMPT SMP Nov 8 17:37:21 arch kernel: last sysfs file: /sys/devices/pci:00/:00:18.3/temp1_input Nov 8 17:37:21 arch kernel: CPU 0 Nov 8 17:37:21 arch kernel: Pid: 1502, comm: X Not tainted 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name Nov 8 17:37:21 arch kernel: RIP: 0010:[] [] _raw_write_lock+0xf/0x20 Nov 8 17:37:21 arch kernel: RSP: 0018:88011b523cc0 EFLAGS: 00010202 Nov 8 17:37:21 arch kernel: RAX: 88011b523fd8 RBX: 0020 RCX: Nov 8 17:37:22 arch kernel: RDX: RSI: 8120a6f0 RDI: 0020 Nov 8 17:37:22 arch kernel: RBP: 880113f39c48 R08: 0006 R09: 0006 Nov 8 17:37:22 arch kernel: R10: 0006 R11: 0006 R12: 0071 Nov 8 17:37:22 arch kernel: R13: 8800c07ffb40 R14: 40086409 R15: fff2 Nov 8 17:37:22 arch kernel: FS: 7f3786cdc700() GS:8800dfc0() knlGS: Nov 8 17:37:22 arch kernel: CS: 0010 DS: ES: CR0: 8005003b Nov 8 17:37:22 arch kernel: CR2: 0020 CR3: 00011f60a000 CR4: 06f0 Nov 8 17:37:22 arch kernel: DR0: DR1: DR2: Nov 8 17:37:22 arch kernel: DR3: DR6: 0ff0 DR7: 0400 Nov 8 17:37:22 arch kernel: Process X (pid: 1502, threadinfo 88011b522000, task 88011cc3d460) Nov 8 17:37:22 arch kernel: Stack: Nov 8 17:37:22 arch kernel: 8121cbb8 0292 88011ffabbc0 88011b523d20 Nov 8 17:37:22 arch kernel: 81252a92 0296 88011d9410a8 Nov 8 17:37:22 arch kernel: 8800c07ffb40 8120a6f0 8126711e 88011f632a90 Nov 8 17:37:22 arch kernel: Call Trace: Nov 8 17:37:22 arch kernel: [] ? ttm_bo_unref+0x28/0x50 Nov 8 17:37:22 arch kernel: [] ? radeon_bo_unref+0x42/0x80 Nov 8 17:37:22 arch kernel: [] ? drm_gem_object_free+0x0/0x30 Nov 8 17:37:22 arch kernel: [] ? radeon_gem_object_free+0x2e/0x50 Nov 8 17:37:22 arch kernel: [] ? kref_put+0x33/0x70 Nov 8 17:37:22 arch kernel: [] ? drm_gem_close_ioctl+0xc0/0xf0 Nov 8 17:37:22 arch kernel: [] ? drm_ioctl+0x39c/0x450 Nov 8 17:37:22 arch kernel: [] ? drm_gem_close_ioctl+0x0/0xf0 Nov 8 17:37:22 arch kernel: [] ? do_sync_read+0xbf/0x100 Nov 8 17:37:22 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610 Nov 8 17:37:22 arch kernel: [] ? sys_ioctl+0x49/0x80 Nov 8 17:37:22 arch kernel: [] ? sys_read+0x4e/0x90 Nov 8 17:37:22 arch kernel: [] ? system_call_fastpath+0x16/0x1b Nov 8 17:37:22 arch kernel: Code: 83 c4 08 c3 e8 f3 dd ff ff 31 c0 eb f2 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 65 48 8b 04 25 c8 b6 00 00 ff 80 44 e0 ff ff 81 2f 00 00 00 01 74 05 e8 83 ff d3 ff c3 66 90 9c 58 fa 65 Nov 8 17:37:22 arch kernel: RIP [] _raw_write_lock+0xf/0x20 Nov 8 17:37:22 arch kernel: RSP Nov 8 17:37:22 arch kernel: CR2: 0020 Nov 8 17:37:22 arch kernel: BUG: unable to handle kernel NULL pointer dereference at 0088 Nov 8 17:37:22 arch kernel: IP: [] _raw_spin_lock+0x14/0x30 Nov 8 17:37:22 arch kernel: PGD 11bf20067 PUD 11bfa7067 PMD 0 Nov 8 17:37:22 arch kernel: Oops: 0002 [#2] PREEMPT SMP Nov 8 17:37:22 arch kernel: last sysfs file: /sys/devices/pci:00/:00:18.3/temp1_input Nov 8 17:37:22 arch kernel: CPU 0 Nov 8 17:37:22 arch kernel: Pid: 1502, comm: X Not tainted 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name Nov 8 17:37:22 arch kernel: RIP: 0010:[] [] _raw_spin_lock+0x14/0x30 Nov 8 17:37:22 arch kernel: RSP: 0018:88011b523660 EFLAGS: 00010002 Nov 8 17:37:22 arch kernel: RAX: 0100 RBX: 88011ff2c048 RCX: Nov 8 17:37:22 arch kernel: RDX: RSI: 0001 RDI: 0088 Nov 8 17:37:22 arch kernel: RBP: 0088 R08: R09: 816a0a00 Nov 8 17:37:22 arch kernel: R10: R11: 0002 R12: 0001 Nov 8 17:37:22 arch kernel: R13: R14: R15: Nov 8 17:37:22 arch kernel: FS: 7f3786cdc700() GS:8800dfc0() knlGS: Nov 8 17:37:22 arch kernel: CS: 0010 DS: ES: CR0: 8005003b Nov 8 17:37:22 arch kernel: CR2: 0088 CR3:
[Bug 31482] New: When trying to put the fullscreen window, data show and LCD laptop screen, the screen windwos screw up
https://bugs.freedesktop.org/show_bug.cgi?id=31482 Summary: When trying to put the fullscreen window, data show and LCD laptop screen, the screen windwos screw up Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: maxim...@gmail.com When trying to put the fullscreen window, using hardware button, i can change between various modes, but when it's the turn of fullscreen of OpenOffice/LibreOffice, in both screen, LCD and VGA output, the image screw up. The screw up only happen when i change between modes with the hardware button, because if i use the F5 button (OpenOffice/LibreOffice fullscreen) that doesn't happen, probably a xrandr problem? -- 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 31482] New: When trying to put the fullscreen window, data show and LCD laptop screen, the screen windwos screw up
https://bugs.freedesktop.org/show_bug.cgi?id=31482 Summary: When trying to put the fullscreen window, data show and LCD laptop screen, the screen windwos screw up Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: maximi89 at gmail.com When trying to put the fullscreen window, using hardware button, i can change between various modes, but when it's the turn of fullscreen of OpenOffice/LibreOffice, in both screen, LCD and VGA output, the image screw up. The screw up only happen when i change between modes with the hardware button, because if i use the F5 button (OpenOffice/LibreOffice fullscreen) that doesn't happen, probably a xrandr problem? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On Mon, Nov 8, 2010 at 3:58 PM, Rafael J. Wysocki wrote: > On Monday, November 08, 2010, Jerome Glisse wrote: >> On Mon, Nov 8, 2010 at 2:02 PM, Markus Trippelsdorf >> wrote: >> > On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: >> >> On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: >> >> > On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: >> >> > > I can trigger a kernel crash on my system by simply loading this png >> >> > > image with firefox: >> >> > > http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg >> >> > >> >> > Sorry the above link is wrong, this is the right one (that triggers the >> >> > crash): >> >> > http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png >> >> >> >> I triggered it a few more times and took the attached picture. >> >> It points to the BUG() call at drivers/gpu/drm/ttm/ttm_bo.c:1628 . >> >> (Sorry for the bad picture quality) >> > >> > And here the same BUG in plaintext (should be a bit easier to read): >> > >> > Nov ?8 19:28:23 arch kernel: [ cut here ] >> > Nov ?8 19:28:23 arch kernel: kernel BUG at >> > drivers/gpu/drm/ttm/ttm_bo.c:1628! >> > Nov ?8 19:28:23 arch kernel: invalid opcode: [#1] PREEMPT SMP >> > Nov ?8 19:28:23 arch kernel: last sysfs file: >> > /sys/devices/pci:00/:00:18.3/temp1_input >> > Nov ?8 19:28:23 arch kernel: CPU 1 >> > Nov ?8 19:28:23 arch kernel: Pid: 1541, comm: X Not tainted >> > 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name >> > Nov ?8 19:28:23 arch kernel: RIP: 0010:[] >> > ?[] ttm_bo_init+0x30f/0x340 >> > Nov ?8 19:28:23 arch kernel: RSP: 0018:88011b0fbbe8 ?EFLAGS: 00010246 >> > Nov ?8 19:28:23 arch kernel: RAX: 8800da881778 RBX: 8800da881620 >> > RCX: 88011b15ed78 >> > Nov ?8 19:28:23 arch kernel: RDX: 8800c1556040 RSI: 88011ff22770 >> > RDI: 0017adfb >> > Nov ?8 19:28:23 arch kernel: RBP: 8800da881648 R08: >> > R09: 8800c1556040 >> > Nov ?8 19:28:23 arch kernel: R10: 0ff85205 R11: 8800dae19200 >> > R12: 0001 >> > Nov ?8 19:28:23 arch kernel: R13: 88011ff22528 R14: 88011ff22778 >> > R15: >> > Nov ?8 19:28:23 arch kernel: FS: ?7f2043043700() >> > GS:8800dfc8() knlGS: >> > Nov ?8 19:28:23 arch kernel: CS: ?0010 DS: ES: CR0: >> > 80050033 >> > Nov ?8 19:28:23 arch kernel: CR2: 7f203d057000 CR3: 00011b12b000 >> > CR4: 06e0 >> > Nov ?8 19:28:23 arch kernel: DR0: DR1: >> > DR2: >> > Nov ?8 19:28:23 arch kernel: DR3: DR6: 0ff0 >> > DR7: 0400 >> > Nov ?8 19:28:23 arch kernel: Process X (pid: 1541, threadinfo >> > 88011b0fa000, task 88011c959c20) >> > Nov ?8 19:28:23 arch kernel: Stack: >> > Nov ?8 19:28:23 arch kernel: 8800da881648 >> > 88011b0fbd00 8800da881600 >> > Nov ?8 19:28:23 arch kernel: 88011ff22000 >> > 0001 fff4 >> > Nov ?8 19:28:23 arch kernel: 88011b0fbd00 8125294d >> > 0001 >> > Nov ?8 19:28:23 arch kernel: Call Trace: >> > Nov ?8 19:28:23 arch kernel: [] ? >> > radeon_bo_create+0x14d/0x250 >> > Nov ?8 19:28:23 arch kernel: [] ? >> > radeon_ttm_bo_destroy+0x0/0xb0 >> > Nov ?8 19:28:23 arch kernel: [] ? >> > radeon_gem_object_create+0x8c/0x130 >> > Nov ?8 19:28:23 arch kernel: [] ? >> > radeon_gem_create_ioctl+0x54/0xd0 >> > Nov ?8 19:28:23 arch kernel: [] ? >> > sock_aio_read+0x10d/0x120 >> > Nov ?8 19:28:23 arch kernel: [] ? drm_ioctl+0x39c/0x450 >> > Nov ?8 19:28:23 arch kernel: [] ? >> > radeon_gem_create_ioctl+0x0/0xd0 >> > Nov ?8 19:28:23 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610 >> > Nov ?8 19:28:23 arch kernel: [] ? sys_ioctl+0x49/0x80 >> > Nov ?8 19:28:23 arch kernel: [] ? sys_read+0x4e/0x90 >> > Nov ?8 19:28:23 arch kernel: [] ? >> > system_call_fastpath+0x16/0x1b >> > Nov ?8 19:28:23 arch kernel: Code: e8 fb ff ff 85 c0 0f 85 68 ff ff ff 48 >> > 8b 7c 24 08 89 04 24 e8 83 d9 ff ff 8b 04 24 48 83 c4 18 5b 5d 41 5c 41 5d >> > 41 5e 41 5f c3 <0f> 0b 48 c7 c7 60 a4 55 81 31 c0 e8 14 80 22 00 b8 ea ff >> > ff ff >> > Nov ?8 19:28:23 arch kernel: RIP ?[] >> > ttm_bo_init+0x30f/0x340 >> > Nov ?8 19:28:23 arch kernel: RSP >> > Nov ?8 19:28:23 arch kernel: ---[ end trace 328a9acba7691d6e ]--- >> > Nov ?8 19:28:23 arch kernel: note: X[1541] exited with preempt_count 1 >> > Nov ?8 19:28:23 arch kernel: BUG: scheduling while atomic: >> > X/1541/0x1002 >> > Nov ?8 19:28:23 arch kernel: Pid: 1541, comm: X Tainted: G ? ? ?D ? ? >> > 2.6.37-rc1-00116-g151f52f-dirty #31 >> > Nov ?8 19:28:23 arch kernel: Call Trace: >> > Nov ?8 19:28:23 arch kernel: [] ? schedule+0x639/0x850 >> > Nov ?8 19:28:23 arch kernel: [] ? >> > __cond_resched+0x1d
[PATCH] gpu: drm: vmwgfx: fix information leak to userland
On 11/06/2010 03:41 PM, Vasiliy Kulikov wrote: > Structure drm_vmw_fence_rep is copied to userland with field "pad64" > uninitialized. It leads to leaking of contents of kernel stack memory. > > Signed-off-by: Vasiliy Kulikov > --- > Compile tested. > > drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c |1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c > b/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c > index 51d9f9f..76954e3 100644 > --- a/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c > +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c > @@ -691,6 +691,7 @@ int vmw_execbuf_ioctl(struct drm_device *dev, void *data, > > fence_rep.error = ret; > fence_rep.fence_seq = (uint64_t) sequence; > + fence_rep.pad64 = 0; > > user_fence_rep = (struct drm_vmw_fence_rep __user *) > (unsigned long)arg->fence_rep; > Reviewed-by: Thomas Hellstrom
Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On Mon, Nov 8, 2010 at 2:02 PM, Markus Trippelsdorf wrote: > On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: >> On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: >> > On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: >> > > I can trigger a kernel crash on my system by simply loading this png >> > > image with firefox: >> > > http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg >> > >> > Sorry the above link is wrong, this is the right one (that triggers the >> > crash): >> > http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png >> >> I triggered it a few more times and took the attached picture. >> It points to the BUG() call at drivers/gpu/drm/ttm/ttm_bo.c:1628 . >> (Sorry for the bad picture quality) > > And here the same BUG in plaintext (should be a bit easier to read): > > Nov ?8 19:28:23 arch kernel: [ cut here ] > Nov ?8 19:28:23 arch kernel: kernel BUG at drivers/gpu/drm/ttm/ttm_bo.c:1628! > Nov ?8 19:28:23 arch kernel: invalid opcode: [#1] PREEMPT SMP > Nov ?8 19:28:23 arch kernel: last sysfs file: > /sys/devices/pci:00/:00:18.3/temp1_input > Nov ?8 19:28:23 arch kernel: CPU 1 > Nov ?8 19:28:23 arch kernel: Pid: 1541, comm: X Not tainted > 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name > Nov ?8 19:28:23 arch kernel: RIP: 0010:[] > ?[] ttm_bo_init+0x30f/0x340 > Nov ?8 19:28:23 arch kernel: RSP: 0018:88011b0fbbe8 ?EFLAGS: 00010246 > Nov ?8 19:28:23 arch kernel: RAX: 8800da881778 RBX: 8800da881620 RCX: > 88011b15ed78 > Nov ?8 19:28:23 arch kernel: RDX: 8800c1556040 RSI: 88011ff22770 RDI: > 0017adfb > Nov ?8 19:28:23 arch kernel: RBP: 8800da881648 R08: R09: > 8800c1556040 > Nov ?8 19:28:23 arch kernel: R10: 0ff85205 R11: 8800dae19200 R12: > 0001 > Nov ?8 19:28:23 arch kernel: R13: 88011ff22528 R14: 88011ff22778 R15: > > Nov ?8 19:28:23 arch kernel: FS: ?7f2043043700() > GS:8800dfc8() knlGS: > Nov ?8 19:28:23 arch kernel: CS: ?0010 DS: ES: CR0: 80050033 > Nov ?8 19:28:23 arch kernel: CR2: 7f203d057000 CR3: 00011b12b000 CR4: > 06e0 > Nov ?8 19:28:23 arch kernel: DR0: DR1: DR2: > > Nov ?8 19:28:23 arch kernel: DR3: DR6: 0ff0 DR7: > 0400 > Nov ?8 19:28:23 arch kernel: Process X (pid: 1541, threadinfo > 88011b0fa000, task 88011c959c20) > Nov ?8 19:28:23 arch kernel: Stack: > Nov ?8 19:28:23 arch kernel: 8800da881648 > 88011b0fbd00 8800da881600 > Nov ?8 19:28:23 arch kernel: 88011ff22000 > 0001 fff4 > Nov ?8 19:28:23 arch kernel: 88011b0fbd00 8125294d > 0001 > Nov ?8 19:28:23 arch kernel: Call Trace: > Nov ?8 19:28:23 arch kernel: [] ? > radeon_bo_create+0x14d/0x250 > Nov ?8 19:28:23 arch kernel: [] ? > radeon_ttm_bo_destroy+0x0/0xb0 > Nov ?8 19:28:23 arch kernel: [] ? > radeon_gem_object_create+0x8c/0x130 > Nov ?8 19:28:23 arch kernel: [] ? > radeon_gem_create_ioctl+0x54/0xd0 > Nov ?8 19:28:23 arch kernel: [] ? sock_aio_read+0x10d/0x120 > Nov ?8 19:28:23 arch kernel: [] ? drm_ioctl+0x39c/0x450 > Nov ?8 19:28:23 arch kernel: [] ? > radeon_gem_create_ioctl+0x0/0xd0 > Nov ?8 19:28:23 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610 > Nov ?8 19:28:23 arch kernel: [] ? sys_ioctl+0x49/0x80 > Nov ?8 19:28:23 arch kernel: [] ? sys_read+0x4e/0x90 > Nov ?8 19:28:23 arch kernel: [] ? > system_call_fastpath+0x16/0x1b > Nov ?8 19:28:23 arch kernel: Code: e8 fb ff ff 85 c0 0f 85 68 ff ff ff 48 8b > 7c 24 08 89 04 24 e8 83 d9 ff ff 8b 04 24 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e > 41 5f c3 <0f> 0b 48 c7 c7 60 a4 55 81 31 c0 e8 14 80 22 00 b8 ea ff ff ff > Nov ?8 19:28:23 arch kernel: RIP ?[] ttm_bo_init+0x30f/0x340 > Nov ?8 19:28:23 arch kernel: RSP > Nov ?8 19:28:23 arch kernel: ---[ end trace 328a9acba7691d6e ]--- > Nov ?8 19:28:23 arch kernel: note: X[1541] exited with preempt_count 1 > Nov ?8 19:28:23 arch kernel: BUG: scheduling while atomic: X/1541/0x1002 > Nov ?8 19:28:23 arch kernel: Pid: 1541, comm: X Tainted: G ? ? ?D ? ? > 2.6.37-rc1-00116-g151f52f-dirty #31 > Nov ?8 19:28:23 arch kernel: Call Trace: > Nov ?8 19:28:23 arch kernel: [] ? schedule+0x639/0x850 > Nov ?8 19:28:23 arch kernel: [] ? __cond_resched+0x1d/0x30 > Nov ?8 19:28:23 arch kernel: [] ? _cond_resched+0x2f/0x40 > Nov ?8 19:28:23 arch kernel: [] ? unmap_vmas+0x82c/0x9c0 > Nov ?8 19:28:23 arch kernel: [] ? exit_mmap+0xe2/0x1a0 > Nov ?8 19:28:23 arch kernel: [] ? mmput+0x25/0xc0 > Nov ?8 19:28:23 arch kernel: [] ? exit_mm+0x104/0x130 > Nov ?8 19:28:23 arch kernel: [] ? > hrtimer_try_to_cancel+0x3f/0x80 > Nov ?8 19:28:23 arch kernel: [] ? acct_collect+0x9a/0x1a0
Re: [PATCH] drm/radeon/kms: fix thermal sensor reporting on rv6xx
On Mon, Nov 8, 2010 at 1:39 PM, Alex Deucher wrote:
> Temperature is not shifted as on newer asics.
>
> Signed-off-by: Alex Deucher
Should be CC'ed to stable as well.
Alex
> ---
> drivers/gpu/drm/radeon/r600.c | 8 +---
> 1 files changed, 1 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/r600.c b/drivers/gpu/drm/radeon/r600.c
> index 951af00..bd69299 100644
> --- a/drivers/gpu/drm/radeon/r600.c
> +++ b/drivers/gpu/drm/radeon/r600.c
> @@ -106,14 +106,8 @@ u32 rv6xx_get_temp(struct radeon_device *rdev)
> {
> u32 temp = (RREG32(CG_THERMAL_STATUS) & ASIC_T_MASK) >>
> ASIC_T_SHIFT;
> - u32 actual_temp = 0;
>
> - if ((temp >> 7) & 1)
> - actual_temp = 0;
> - else
> - actual_temp = (temp >> 1) & 0xff;
> -
> - return actual_temp * 1000;
> + return temp * 1000;
> }
>
> void r600_pm_get_dynpm_state(struct radeon_device *rdev)
> --
> 1.7.1.1
>
>
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On Mon, Nov 8, 2010 at 2:02 PM, Markus Trippelsdorf wrote: > On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: >> On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: >> > On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: >> > > I can trigger a kernel crash on my system by simply loading this png >> > > image with firefox: >> > > http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg >> > >> > Sorry the above link is wrong, this is the right one (that triggers the >> > crash): >> > http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png >> >> I triggered it a few more times and took the attached picture. >> It points to the BUG() call at drivers/gpu/drm/ttm/ttm_bo.c:1628 . >> (Sorry for the bad picture quality) > > And here the same BUG in plaintext (should be a bit easier to read): > > Nov ?8 19:28:23 arch kernel: [ cut here ] > Nov ?8 19:28:23 arch kernel: kernel BUG at drivers/gpu/drm/ttm/ttm_bo.c:1628! Quite puzzling it is as if there was already a bo at same offset in rb tree but not in vm mm. Maybe some other race in destruction... Cheers, Jerome Glisse
Re: Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On 11/08/2010 09:53 PM, Jerome Glisse wrote: On Mon, Nov 8, 2010 at 2:02 PM, Markus Trippelsdorf wrote: On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: I can trigger a kernel crash on my system by simply loading this png image with firefox: http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg Sorry the above link is wrong, this is the right one (that triggers the crash): http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png I triggered it a few more times and took the attached picture. It points to the BUG() call at drivers/gpu/drm/ttm/ttm_bo.c:1628 . (Sorry for the bad picture quality) And here the same BUG in plaintext (should be a bit easier to read): Nov 8 19:28:23 arch kernel: [ cut here ] Nov 8 19:28:23 arch kernel: kernel BUG at drivers/gpu/drm/ttm/ttm_bo.c:1628! Nov 8 19:28:23 arch kernel: invalid opcode: [#1] PREEMPT SMP Nov 8 19:28:23 arch kernel: last sysfs file: /sys/devices/pci:00/:00:18.3/temp1_input Nov 8 19:28:23 arch kernel: CPU 1 Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Not tainted 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name Nov 8 19:28:23 arch kernel: RIP: 0010:[] [] ttm_bo_init+0x30f/0x340 Nov 8 19:28:23 arch kernel: RSP: 0018:88011b0fbbe8 EFLAGS: 00010246 Nov 8 19:28:23 arch kernel: RAX: 8800da881778 RBX: 8800da881620 RCX: 88011b15ed78 Nov 8 19:28:23 arch kernel: RDX: 8800c1556040 RSI: 88011ff22770 RDI: 0017adfb Nov 8 19:28:23 arch kernel: RBP: 8800da881648 R08: R09: 8800c1556040 Nov 8 19:28:23 arch kernel: R10: 0ff85205 R11: 8800dae19200 R12: 0001 Nov 8 19:28:23 arch kernel: R13: 88011ff22528 R14: 88011ff22778 R15: Nov 8 19:28:23 arch kernel: FS: 7f2043043700() GS:8800dfc8() knlGS: Nov 8 19:28:23 arch kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 8 19:28:23 arch kernel: CR2: 7f203d057000 CR3: 00011b12b000 CR4: 06e0 Nov 8 19:28:23 arch kernel: DR0: DR1: DR2: Nov 8 19:28:23 arch kernel: DR3: DR6: 0ff0 DR7: 0400 Nov 8 19:28:23 arch kernel: Process X (pid: 1541, threadinfo 88011b0fa000, task 88011c959c20) Nov 8 19:28:23 arch kernel: Stack: Nov 8 19:28:23 arch kernel: 8800da881648 88011b0fbd00 8800da881600 Nov 8 19:28:23 arch kernel: 88011ff22000 0001 fff4 Nov 8 19:28:23 arch kernel: 88011b0fbd00 8125294d 0001 Nov 8 19:28:23 arch kernel: Call Trace: Nov 8 19:28:23 arch kernel: [] ? radeon_bo_create+0x14d/0x250 Nov 8 19:28:23 arch kernel: [] ? radeon_ttm_bo_destroy+0x0/0xb0 Nov 8 19:28:23 arch kernel: [] ? radeon_gem_object_create+0x8c/0x130 Nov 8 19:28:23 arch kernel: [] ? radeon_gem_create_ioctl+0x54/0xd0 Nov 8 19:28:23 arch kernel: [] ? sock_aio_read+0x10d/0x120 Nov 8 19:28:23 arch kernel: [] ? drm_ioctl+0x39c/0x450 Nov 8 19:28:23 arch kernel: [] ? radeon_gem_create_ioctl+0x0/0xd0 Nov 8 19:28:23 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610 Nov 8 19:28:23 arch kernel: [] ? sys_ioctl+0x49/0x80 Nov 8 19:28:23 arch kernel: [] ? sys_read+0x4e/0x90 Nov 8 19:28:23 arch kernel: [] ? system_call_fastpath+0x16/0x1b Nov 8 19:28:23 arch kernel: Code: e8 fb ff ff 85 c0 0f 85 68 ff ff ff 48 8b 7c 24 08 89 04 24 e8 83 d9 ff ff 8b 04 24 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3<0f> 0b 48 c7 c7 60 a4 55 81 31 c0 e8 14 80 22 00 b8 ea ff ff ff Nov 8 19:28:23 arch kernel: RIP [] ttm_bo_init+0x30f/0x340 Nov 8 19:28:23 arch kernel: RSP Nov 8 19:28:23 arch kernel: ---[ end trace 328a9acba7691d6e ]--- Nov 8 19:28:23 arch kernel: note: X[1541] exited with preempt_count 1 Nov 8 19:28:23 arch kernel: BUG: scheduling while atomic: X/1541/0x1002 Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Tainted: G D 2.6.37-rc1-00116-g151f52f-dirty #31 Nov 8 19:28:23 arch kernel: Call Trace: Nov 8 19:28:23 arch kernel: [] ? schedule+0x639/0x850 Nov 8 19:28:23 arch kernel: [] ? __cond_resched+0x1d/0x30 Nov 8 19:28:23 arch kernel: [] ? _cond_resched+0x2f/0x40 Nov 8 19:28:23 arch kernel: [] ? unmap_vmas+0x82c/0x9c0 Nov 8 19:28:23 arch kernel: [] ? exit_mmap+0xe2/0x1a0 Nov 8 19:28:23 arch kernel: [] ? mmput+0x25/0xc0 Nov 8 19:28:23 arch kernel: [] ? exit_mm+0x104/0x130 Nov 8 19:28:23 arch kernel: [] ? hrtimer_try_to_cancel+0x3f/0x80 Nov 8 19:28:23 arch kernel: [] ? acct_collect+0x9a/0x1a0 Nov 8 19:28:23 arch kernel: [] ? do_exit+0x5aa/0x760 Nov 8 19:28:23 arch kernel: [] ? printk+0x40/0x45 Nov 8
Re: Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On 11/08/2010 09:58 PM, Rafael J. Wysocki wrote: On Monday, November 08, 2010, Jerome Glisse wrote: On Mon, Nov 8, 2010 at 2:02 PM, Markus Trippelsdorf wrote: On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: I can trigger a kernel crash on my system by simply loading this png image with firefox: http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg Sorry the above link is wrong, this is the right one (that triggers the crash): http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png I triggered it a few more times and took the attached picture. It points to the BUG() call at drivers/gpu/drm/ttm/ttm_bo.c:1628 . (Sorry for the bad picture quality) And here the same BUG in plaintext (should be a bit easier to read): Nov 8 19:28:23 arch kernel: [ cut here ] Nov 8 19:28:23 arch kernel: kernel BUG at drivers/gpu/drm/ttm/ttm_bo.c:1628! Nov 8 19:28:23 arch kernel: invalid opcode: [#1] PREEMPT SMP Nov 8 19:28:23 arch kernel: last sysfs file: /sys/devices/pci:00/:00:18.3/temp1_input Nov 8 19:28:23 arch kernel: CPU 1 Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Not tainted 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name Nov 8 19:28:23 arch kernel: RIP: 0010:[] [] ttm_bo_init+0x30f/0x340 Nov 8 19:28:23 arch kernel: RSP: 0018:88011b0fbbe8 EFLAGS: 00010246 Nov 8 19:28:23 arch kernel: RAX: 8800da881778 RBX: 8800da881620 RCX: 88011b15ed78 Nov 8 19:28:23 arch kernel: RDX: 8800c1556040 RSI: 88011ff22770 RDI: 0017adfb Nov 8 19:28:23 arch kernel: RBP: 8800da881648 R08: R09: 8800c1556040 Nov 8 19:28:23 arch kernel: R10: 0ff85205 R11: 8800dae19200 R12: 0001 Nov 8 19:28:23 arch kernel: R13: 88011ff22528 R14: 88011ff22778 R15: Nov 8 19:28:23 arch kernel: FS: 7f2043043700() GS:8800dfc8() knlGS: Nov 8 19:28:23 arch kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 8 19:28:23 arch kernel: CR2: 7f203d057000 CR3: 00011b12b000 CR4: 06e0 Nov 8 19:28:23 arch kernel: DR0: DR1: DR2: Nov 8 19:28:23 arch kernel: DR3: DR6: 0ff0 DR7: 0400 Nov 8 19:28:23 arch kernel: Process X (pid: 1541, threadinfo 88011b0fa000, task 88011c959c20) Nov 8 19:28:23 arch kernel: Stack: Nov 8 19:28:23 arch kernel: 8800da881648 88011b0fbd00 8800da881600 Nov 8 19:28:23 arch kernel: 88011ff22000 0001 fff4 Nov 8 19:28:23 arch kernel: 88011b0fbd00 8125294d 0001 Nov 8 19:28:23 arch kernel: Call Trace: Nov 8 19:28:23 arch kernel: [] ? radeon_bo_create+0x14d/0x250 Nov 8 19:28:23 arch kernel: [] ? radeon_ttm_bo_destroy+0x0/0xb0 Nov 8 19:28:23 arch kernel: [] ? radeon_gem_object_create+0x8c/0x130 Nov 8 19:28:23 arch kernel: [] ? radeon_gem_create_ioctl+0x54/0xd0 Nov 8 19:28:23 arch kernel: [] ? sock_aio_read+0x10d/0x120 Nov 8 19:28:23 arch kernel: [] ? drm_ioctl+0x39c/0x450 Nov 8 19:28:23 arch kernel: [] ? radeon_gem_create_ioctl+0x0/0xd0 Nov 8 19:28:23 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610 Nov 8 19:28:23 arch kernel: [] ? sys_ioctl+0x49/0x80 Nov 8 19:28:23 arch kernel: [] ? sys_read+0x4e/0x90 Nov 8 19:28:23 arch kernel: [] ? system_call_fastpath+0x16/0x1b Nov 8 19:28:23 arch kernel: Code: e8 fb ff ff 85 c0 0f 85 68 ff ff ff 48 8b 7c 24 08 89 04 24 e8 83 d9 ff ff 8b 04 24 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3<0f> 0b 48 c7 c7 60 a4 55 81 31 c0 e8 14 80 22 00 b8 ea ff ff ff Nov 8 19:28:23 arch kernel: RIP [] ttm_bo_init+0x30f/0x340 Nov 8 19:28:23 arch kernel: RSP Nov 8 19:28:23 arch kernel: ---[ end trace 328a9acba7691d6e ]--- Nov 8 19:28:23 arch kernel: note: X[1541] exited with preempt_count 1 Nov 8 19:28:23 arch kernel: BUG: scheduling while atomic: X/1541/0x1002 Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Tainted: G D 2.6.37-rc1-00116-g151f52f-dirty #31 Nov 8 19:28:23 arch kernel: Call Trace: Nov 8 19:28:23 arch kernel: [] ? schedule+0x639/0x850 Nov 8 19:28:23 arch kernel: [] ? __cond_resched+0x1d/0x30 Nov 8 19:28:23 arch kernel: [] ? _cond_resched+0x2f/0x40 Nov 8 19:28:23 arch kernel: [] ? unmap_vmas+0x82c/0x9c0 Nov 8 19:28:23 arch kernel: [] ? exit_mmap+0xe2/0x1a0 Nov 8 19:28:23 arch kernel: [] ? mmput+0x25/0xc0 Nov 8 19:28:23 arch kernel: [] ? exit_mm+0x104/0x130 Nov 8 19:28:23 arch kernel: [] ? hrtimer_try_to_cancel+0x3f/0x80 Nov 8 19:28:23 arch kernel: [] ? acct_collect+0x9a/0x1a0 Nov 8 19:28:23 arch kernel: [] ? do_e
Re: Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On Mon, Nov 8, 2010 at 3:58 PM, Rafael J. Wysocki wrote: > On Monday, November 08, 2010, Jerome Glisse wrote: >> On Mon, Nov 8, 2010 at 2:02 PM, Markus Trippelsdorf >> wrote: >> > On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: >> >> On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: >> >> > On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: >> >> > > I can trigger a kernel crash on my system by simply loading this png >> >> > > image with firefox: >> >> > > http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg >> >> > >> >> > Sorry the above link is wrong, this is the right one (that triggers the >> >> > crash): >> >> > http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png >> >> >> >> I triggered it a few more times and took the attached picture. >> >> It points to the BUG() call at drivers/gpu/drm/ttm/ttm_bo.c:1628 . >> >> (Sorry for the bad picture quality) >> > >> > And here the same BUG in plaintext (should be a bit easier to read): >> > >> > Nov 8 19:28:23 arch kernel: [ cut here ] >> > Nov 8 19:28:23 arch kernel: kernel BUG at >> > drivers/gpu/drm/ttm/ttm_bo.c:1628! >> > Nov 8 19:28:23 arch kernel: invalid opcode: [#1] PREEMPT SMP >> > Nov 8 19:28:23 arch kernel: last sysfs file: >> > /sys/devices/pci:00/:00:18.3/temp1_input >> > Nov 8 19:28:23 arch kernel: CPU 1 >> > Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Not tainted >> > 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name >> > Nov 8 19:28:23 arch kernel: RIP: 0010:[] >> > [] ttm_bo_init+0x30f/0x340 >> > Nov 8 19:28:23 arch kernel: RSP: 0018:88011b0fbbe8 EFLAGS: 00010246 >> > Nov 8 19:28:23 arch kernel: RAX: 8800da881778 RBX: 8800da881620 >> > RCX: 88011b15ed78 >> > Nov 8 19:28:23 arch kernel: RDX: 8800c1556040 RSI: 88011ff22770 >> > RDI: 0017adfb >> > Nov 8 19:28:23 arch kernel: RBP: 8800da881648 R08: >> > R09: 8800c1556040 >> > Nov 8 19:28:23 arch kernel: R10: 0ff85205 R11: 8800dae19200 >> > R12: 0001 >> > Nov 8 19:28:23 arch kernel: R13: 88011ff22528 R14: 88011ff22778 >> > R15: >> > Nov 8 19:28:23 arch kernel: FS: 7f2043043700() >> > GS:8800dfc8() knlGS: >> > Nov 8 19:28:23 arch kernel: CS: 0010 DS: ES: CR0: >> > 80050033 >> > Nov 8 19:28:23 arch kernel: CR2: 7f203d057000 CR3: 00011b12b000 >> > CR4: 06e0 >> > Nov 8 19:28:23 arch kernel: DR0: DR1: >> > DR2: >> > Nov 8 19:28:23 arch kernel: DR3: DR6: 0ff0 >> > DR7: 0400 >> > Nov 8 19:28:23 arch kernel: Process X (pid: 1541, threadinfo >> > 88011b0fa000, task 88011c959c20) >> > Nov 8 19:28:23 arch kernel: Stack: >> > Nov 8 19:28:23 arch kernel: 8800da881648 >> > 88011b0fbd00 8800da881600 >> > Nov 8 19:28:23 arch kernel: 88011ff22000 >> > 0001 fff4 >> > Nov 8 19:28:23 arch kernel: 88011b0fbd00 8125294d >> > 0001 >> > Nov 8 19:28:23 arch kernel: Call Trace: >> > Nov 8 19:28:23 arch kernel: [] ? >> > radeon_bo_create+0x14d/0x250 >> > Nov 8 19:28:23 arch kernel: [] ? >> > radeon_ttm_bo_destroy+0x0/0xb0 >> > Nov 8 19:28:23 arch kernel: [] ? >> > radeon_gem_object_create+0x8c/0x130 >> > Nov 8 19:28:23 arch kernel: [] ? >> > radeon_gem_create_ioctl+0x54/0xd0 >> > Nov 8 19:28:23 arch kernel: [] ? >> > sock_aio_read+0x10d/0x120 >> > Nov 8 19:28:23 arch kernel: [] ? drm_ioctl+0x39c/0x450 >> > Nov 8 19:28:23 arch kernel: [] ? >> > radeon_gem_create_ioctl+0x0/0xd0 >> > Nov 8 19:28:23 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610 >> > Nov 8 19:28:23 arch kernel: [] ? sys_ioctl+0x49/0x80 >> > Nov 8 19:28:23 arch kernel: [] ? sys_read+0x4e/0x90 >> > Nov 8 19:28:23 arch kernel: [] ? >> > system_call_fastpath+0x16/0x1b >> > Nov 8 19:28:23 arch kernel: Code: e8 fb ff ff 85 c0 0f 85 68 ff ff ff 48 >> > 8b 7c 24 08 89 04 24 e8 83 d9 ff ff 8b 04 24 48 83 c4 18 5b 5d 41 5c 41 5d >> > 41 5e 41 5f c3 <0f> 0b 48 c7 c7 60 a4 55 81 31 c0 e8 14 80 22 00 b8 ea ff >> > ff ff >> > Nov 8 19:28:23 arch kernel: RIP [] >> > ttm_bo_init+0x30f/0x340 >> > Nov 8 19:28:23 arch kernel: RSP >> > Nov 8 19:28:23 arch kernel: ---[ end trace 328a9acba7691d6e ]--- >> > Nov 8 19:28:23 arch kernel: note: X[1541] exited with preempt_count 1 >> > Nov 8 19:28:23 arch kernel: BUG: scheduling while atomic: >> > X/1541/0x1002 >> > Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Tainted: G D >> > 2.6.37-rc1-00116-g151f52f-dirty #31 >> > Nov 8 19:28:23 arch kernel: Call Trace: >> > Nov 8 19:28:23 arch kernel: [] ? schedule+0x639/0x850 >> > Nov 8 19:28:23 arch kernel: [] ? >> > __cond_resched+0x1d
[Bug 31265] r600g: Adobe Flash Plugin crashes (Regression)
https://bugs.freedesktop.org/show_bug.cgi?id=31265 --- Comment #2 from Rafael Monica 2010-11-08 13:58:36 PST --- Nope. Still crashes with latest git master. When commenting out the call to util_blitter_destroy(rctx->blitter); there's no crash. -- 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 31265] r600g: Adobe Flash Plugin crashes (Regression)
https://bugs.freedesktop.org/show_bug.cgi?id=31265 --- Comment #2 from Rafael Monica 2010-11-08 13:58:36 PST --- Nope. Still crashes with latest git master. When commenting out the call to util_blitter_destroy(rctx->blitter); there's no crash. -- 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: idr_find (drm_gem_object_lookup) needs only rcu read locks
On Thu, 4 Nov 2010 10:09:53 +, Chris Wilson wrote: > /* Release reference and decrement refcount. */ > idr_remove(&filp->object_idr, handle); > spin_unlock(&filp->table_lock); > > + synchronize_rcu(); > + This is an absolute performance killer. Looks like we might have to endure call_rcu if we want to proceed down this path. -Chris -- Chris Wilson, Intel Open Source Technology Centre
[PATCH] drm/radeon/kms: fix thermal sensor reporting on rv6xx
Temperature is not shifted as on newer asics.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/r600.c |8 +---
1 files changed, 1 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/radeon/r600.c b/drivers/gpu/drm/radeon/r600.c
index 951af00..bd69299 100644
--- a/drivers/gpu/drm/radeon/r600.c
+++ b/drivers/gpu/drm/radeon/r600.c
@@ -106,14 +106,8 @@ u32 rv6xx_get_temp(struct radeon_device *rdev)
{
u32 temp = (RREG32(CG_THERMAL_STATUS) & ASIC_T_MASK) >>
ASIC_T_SHIFT;
- u32 actual_temp = 0;
- if ((temp >> 7) & 1)
- actual_temp = 0;
- else
- actual_temp = (temp >> 1) & 0xff;
-
- return actual_temp * 1000;
+ return temp * 1000;
}
void r600_pm_get_dynpm_state(struct radeon_device *rdev)
--
1.7.1.1
[Bug 30351] Zero Ballistics: tank not rendered
https://bugs.freedesktop.org/show_bug.cgi?id=30351 --- Comment #7 from Sven Arvidsson 2010-11-08 13:15:41 PST --- Created an attachment (id=40125) --> (https://bugs.freedesktop.org/attachment.cgi?id=40125) Screenshot comparing normal vs RADEON_NO_TCL (In reply to comment #6) > I took a look at this game, and I can't tell what the problem is. Can you > post > screenshots of the current behavior and the expected behavior? The model representing the player (the tank) is not rendered. The game uses a first person view by default, but you can press F2 to switch to third person, which should make the problem obvious. I have attached a screenshot comparing the problem with a run using RADEON_NO_TCL=1 where the tank is visible. -- 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 30351] Zero Ballistics: tank not rendered
https://bugs.freedesktop.org/show_bug.cgi?id=30351 --- Comment #7 from Sven Arvidsson 2010-11-08 13:15:41 PST --- Created an attachment (id=40125) --> (https://bugs.freedesktop.org/attachment.cgi?id=40125) Screenshot comparing normal vs RADEON_NO_TCL (In reply to comment #6) > I took a look at this game, and I can't tell what the problem is. Can you > post > screenshots of the current behavior and the expected behavior? The model representing the player (the tank) is not rendered. The game uses a first person view by default, but you can press F2 to switch to third person, which should make the problem obvious. I have attached a screenshot comparing the problem with a run using RADEON_NO_TCL=1 where the tank is visible. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On Monday, November 08, 2010, Jerome Glisse wrote: > On Mon, Nov 8, 2010 at 2:02 PM, Markus Trippelsdorf > wrote: > > On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: > >> On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: > >> > On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: > >> > > I can trigger a kernel crash on my system by simply loading this png > >> > > image with firefox: > >> > > http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg > >> > > >> > Sorry the above link is wrong, this is the right one (that triggers the > >> > crash): > >> > http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png > >> > >> I triggered it a few more times and took the attached picture. > >> It points to the BUG() call at drivers/gpu/drm/ttm/ttm_bo.c:1628 . > >> (Sorry for the bad picture quality) > > > > And here the same BUG in plaintext (should be a bit easier to read): > > > > Nov 8 19:28:23 arch kernel: [ cut here ] > > Nov 8 19:28:23 arch kernel: kernel BUG at > > drivers/gpu/drm/ttm/ttm_bo.c:1628! > > Nov 8 19:28:23 arch kernel: invalid opcode: [#1] PREEMPT SMP > > Nov 8 19:28:23 arch kernel: last sysfs file: > > /sys/devices/pci:00/:00:18.3/temp1_input > > Nov 8 19:28:23 arch kernel: CPU 1 > > Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Not tainted > > 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name > > Nov 8 19:28:23 arch kernel: RIP: 0010:[] > > [] ttm_bo_init+0x30f/0x340 > > Nov 8 19:28:23 arch kernel: RSP: 0018:88011b0fbbe8 EFLAGS: 00010246 > > Nov 8 19:28:23 arch kernel: RAX: 8800da881778 RBX: 8800da881620 > > RCX: 88011b15ed78 > > Nov 8 19:28:23 arch kernel: RDX: 8800c1556040 RSI: 88011ff22770 > > RDI: 0017adfb > > Nov 8 19:28:23 arch kernel: RBP: 8800da881648 R08: > > R09: 8800c1556040 > > Nov 8 19:28:23 arch kernel: R10: 0ff85205 R11: 8800dae19200 > > R12: 0001 > > Nov 8 19:28:23 arch kernel: R13: 88011ff22528 R14: 88011ff22778 > > R15: > > Nov 8 19:28:23 arch kernel: FS: 7f2043043700() > > GS:8800dfc8() knlGS: > > Nov 8 19:28:23 arch kernel: CS: 0010 DS: ES: CR0: > > 80050033 > > Nov 8 19:28:23 arch kernel: CR2: 7f203d057000 CR3: 00011b12b000 > > CR4: 06e0 > > Nov 8 19:28:23 arch kernel: DR0: DR1: > > DR2: > > Nov 8 19:28:23 arch kernel: DR3: DR6: 0ff0 > > DR7: 0400 > > Nov 8 19:28:23 arch kernel: Process X (pid: 1541, threadinfo > > 88011b0fa000, task 88011c959c20) > > Nov 8 19:28:23 arch kernel: Stack: > > Nov 8 19:28:23 arch kernel: 8800da881648 > > 88011b0fbd00 8800da881600 > > Nov 8 19:28:23 arch kernel: 88011ff22000 > > 0001 fff4 > > Nov 8 19:28:23 arch kernel: 88011b0fbd00 8125294d > > 0001 > > Nov 8 19:28:23 arch kernel: Call Trace: > > Nov 8 19:28:23 arch kernel: [] ? > > radeon_bo_create+0x14d/0x250 > > Nov 8 19:28:23 arch kernel: [] ? > > radeon_ttm_bo_destroy+0x0/0xb0 > > Nov 8 19:28:23 arch kernel: [] ? > > radeon_gem_object_create+0x8c/0x130 > > Nov 8 19:28:23 arch kernel: [] ? > > radeon_gem_create_ioctl+0x54/0xd0 > > Nov 8 19:28:23 arch kernel: [] ? > > sock_aio_read+0x10d/0x120 > > Nov 8 19:28:23 arch kernel: [] ? drm_ioctl+0x39c/0x450 > > Nov 8 19:28:23 arch kernel: [] ? > > radeon_gem_create_ioctl+0x0/0xd0 > > Nov 8 19:28:23 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610 > > Nov 8 19:28:23 arch kernel: [] ? sys_ioctl+0x49/0x80 > > Nov 8 19:28:23 arch kernel: [] ? sys_read+0x4e/0x90 > > Nov 8 19:28:23 arch kernel: [] ? > > system_call_fastpath+0x16/0x1b > > Nov 8 19:28:23 arch kernel: Code: e8 fb ff ff 85 c0 0f 85 68 ff ff ff 48 > > 8b 7c 24 08 89 04 24 e8 83 d9 ff ff 8b 04 24 48 83 c4 18 5b 5d 41 5c 41 5d > > 41 5e 41 5f c3 <0f> 0b 48 c7 c7 60 a4 55 81 31 c0 e8 14 80 22 00 b8 ea ff > > ff ff > > Nov 8 19:28:23 arch kernel: RIP [] > > ttm_bo_init+0x30f/0x340 > > Nov 8 19:28:23 arch kernel: RSP > > Nov 8 19:28:23 arch kernel: ---[ end trace 328a9acba7691d6e ]--- > > Nov 8 19:28:23 arch kernel: note: X[1541] exited with preempt_count 1 > > Nov 8 19:28:23 arch kernel: BUG: scheduling while atomic: X/1541/0x1002 > > Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Tainted: G D > > 2.6.37-rc1-00116-g151f52f-dirty #31 > > Nov 8 19:28:23 arch kernel: Call Trace: > > Nov 8 19:28:23 arch kernel: [] ? schedule+0x639/0x850 > > Nov 8 19:28:23 arch kernel: [] ? __cond_resched+0x1d/0x30 > > Nov 8 19:28:23 arch kernel: [] ? _cond_resched+0x2f/0x40 > > Nov 8 19:28:23 arch kernel: [] ? unmap_vmas+0x82c/0x9c0 > > Nov 8 19:28:23 arch kernel: [] ?
Re: Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On Mon, Nov 8, 2010 at 2:02 PM, Markus Trippelsdorf wrote: > On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: >> On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: >> > On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: >> > > I can trigger a kernel crash on my system by simply loading this png >> > > image with firefox: >> > > http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg >> > >> > Sorry the above link is wrong, this is the right one (that triggers the >> > crash): >> > http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png >> >> I triggered it a few more times and took the attached picture. >> It points to the BUG() call at drivers/gpu/drm/ttm/ttm_bo.c:1628 . >> (Sorry for the bad picture quality) > > And here the same BUG in plaintext (should be a bit easier to read): > > Nov 8 19:28:23 arch kernel: [ cut here ] > Nov 8 19:28:23 arch kernel: kernel BUG at drivers/gpu/drm/ttm/ttm_bo.c:1628! > Nov 8 19:28:23 arch kernel: invalid opcode: [#1] PREEMPT SMP > Nov 8 19:28:23 arch kernel: last sysfs file: > /sys/devices/pci:00/:00:18.3/temp1_input > Nov 8 19:28:23 arch kernel: CPU 1 > Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Not tainted > 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name > Nov 8 19:28:23 arch kernel: RIP: 0010:[] > [] ttm_bo_init+0x30f/0x340 > Nov 8 19:28:23 arch kernel: RSP: 0018:88011b0fbbe8 EFLAGS: 00010246 > Nov 8 19:28:23 arch kernel: RAX: 8800da881778 RBX: 8800da881620 RCX: > 88011b15ed78 > Nov 8 19:28:23 arch kernel: RDX: 8800c1556040 RSI: 88011ff22770 RDI: > 0017adfb > Nov 8 19:28:23 arch kernel: RBP: 8800da881648 R08: R09: > 8800c1556040 > Nov 8 19:28:23 arch kernel: R10: 0ff85205 R11: 8800dae19200 R12: > 0001 > Nov 8 19:28:23 arch kernel: R13: 88011ff22528 R14: 88011ff22778 R15: > > Nov 8 19:28:23 arch kernel: FS: 7f2043043700() > GS:8800dfc8() knlGS: > Nov 8 19:28:23 arch kernel: CS: 0010 DS: ES: CR0: 80050033 > Nov 8 19:28:23 arch kernel: CR2: 7f203d057000 CR3: 00011b12b000 CR4: > 06e0 > Nov 8 19:28:23 arch kernel: DR0: DR1: DR2: > > Nov 8 19:28:23 arch kernel: DR3: DR6: 0ff0 DR7: > 0400 > Nov 8 19:28:23 arch kernel: Process X (pid: 1541, threadinfo > 88011b0fa000, task 88011c959c20) > Nov 8 19:28:23 arch kernel: Stack: > Nov 8 19:28:23 arch kernel: 8800da881648 > 88011b0fbd00 8800da881600 > Nov 8 19:28:23 arch kernel: 88011ff22000 > 0001 fff4 > Nov 8 19:28:23 arch kernel: 88011b0fbd00 8125294d > 0001 > Nov 8 19:28:23 arch kernel: Call Trace: > Nov 8 19:28:23 arch kernel: [] ? > radeon_bo_create+0x14d/0x250 > Nov 8 19:28:23 arch kernel: [] ? > radeon_ttm_bo_destroy+0x0/0xb0 > Nov 8 19:28:23 arch kernel: [] ? > radeon_gem_object_create+0x8c/0x130 > Nov 8 19:28:23 arch kernel: [] ? > radeon_gem_create_ioctl+0x54/0xd0 > Nov 8 19:28:23 arch kernel: [] ? sock_aio_read+0x10d/0x120 > Nov 8 19:28:23 arch kernel: [] ? drm_ioctl+0x39c/0x450 > Nov 8 19:28:23 arch kernel: [] ? > radeon_gem_create_ioctl+0x0/0xd0 > Nov 8 19:28:23 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610 > Nov 8 19:28:23 arch kernel: [] ? sys_ioctl+0x49/0x80 > Nov 8 19:28:23 arch kernel: [] ? sys_read+0x4e/0x90 > Nov 8 19:28:23 arch kernel: [] ? > system_call_fastpath+0x16/0x1b > Nov 8 19:28:23 arch kernel: Code: e8 fb ff ff 85 c0 0f 85 68 ff ff ff 48 8b > 7c 24 08 89 04 24 e8 83 d9 ff ff 8b 04 24 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e > 41 5f c3 <0f> 0b 48 c7 c7 60 a4 55 81 31 c0 e8 14 80 22 00 b8 ea ff ff ff > Nov 8 19:28:23 arch kernel: RIP [] ttm_bo_init+0x30f/0x340 > Nov 8 19:28:23 arch kernel: RSP > Nov 8 19:28:23 arch kernel: ---[ end trace 328a9acba7691d6e ]--- > Nov 8 19:28:23 arch kernel: note: X[1541] exited with preempt_count 1 > Nov 8 19:28:23 arch kernel: BUG: scheduling while atomic: X/1541/0x1002 > Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Tainted: G D > 2.6.37-rc1-00116-g151f52f-dirty #31 > Nov 8 19:28:23 arch kernel: Call Trace: > Nov 8 19:28:23 arch kernel: [] ? schedule+0x639/0x850 > Nov 8 19:28:23 arch kernel: [] ? __cond_resched+0x1d/0x30 > Nov 8 19:28:23 arch kernel: [] ? _cond_resched+0x2f/0x40 > Nov 8 19:28:23 arch kernel: [] ? unmap_vmas+0x82c/0x9c0 > Nov 8 19:28:23 arch kernel: [] ? exit_mmap+0xe2/0x1a0 > Nov 8 19:28:23 arch kernel: [] ? mmput+0x25/0xc0 > Nov 8 19:28:23 arch kernel: [] ? exit_mm+0x104/0x130 > Nov 8 19:28:23 arch kernel: [] ? > hrtimer_try_to_cancel+0x3f/0x80 > Nov 8 19:28:23 arch kernel: [] ? acct_collect+0x9a/0x1a0
[bruce.e...@gmail.com: PATCH: ERROR: "video_output_register" [drivers/acpi/video.ko] und]
On Mon, Nov 08, 2010 at 10:51:10AM -0500, Konrad Rzeszutek Wilk wrote: > Hey guys, > > This failure also occurs on v2.6.37-rc1 (the branch Bruce is > referring has been merged in Linus's tree). This compile > failure can be demonstrated if one does not > select VIDEO_OUTPUT_CONTROL and enables the Nouveau driver. > > The i915 has a similar fix in the Kconfig > (ecb4aed78dcf09e48c8c34c8c2fa7f5c69344be6) but this one is lacking. > > Acked-by: Konrad Rzeszutek Wilk Also Cc-ing LKML. > > - Forwarded message from Bruce Edge - > > Date: Sun, 7 Nov 2010 17:56:38 -0800 > From: Bruce Edge > To: xen-devel at lists.xensource.com, > Konrad Rzeszutek Wilk > Subject: PATCH: pvops 2.6.36 patch for undefined! ERROR: > "video_output_register" > [drivers/acpi/video.ko] und > > This patch resolved the following link error: > > ERROR: "video_output_unregister" [drivers/acpi/video.ko] undefined! > ERROR: "video_output_register" [drivers/acpi/video.ko] undefined! > > in this branch: > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git- > stable/xen-pcifront-0.8.2 > > --- old/drivers/gpu/drm/nouveau/Kconfig > +++ new/drivers/gpu/drm/nouveau/Kconfig > @@ -11,6 +11,7 @@ > select FRAMEBUFFER_CONSOLE if !EMBEDDED > select FB_BACKLIGHT if DRM_NOUVEAU_BACKLIGHT > select ACPI_VIDEO if ACPI > + select VIDEO_OUTPUT_CONTROL if ACPI > help > Choose this option for open-source nVidia support. > > > -Bruce > > - End forwarded message -
Re: Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On Mon, Nov 8, 2010 at 2:02 PM, Markus Trippelsdorf wrote: > On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: >> On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: >> > On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: >> > > I can trigger a kernel crash on my system by simply loading this png >> > > image with firefox: >> > > http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg >> > >> > Sorry the above link is wrong, this is the right one (that triggers the >> > crash): >> > http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png >> >> I triggered it a few more times and took the attached picture. >> It points to the BUG() call at drivers/gpu/drm/ttm/ttm_bo.c:1628 . >> (Sorry for the bad picture quality) > > And here the same BUG in plaintext (should be a bit easier to read): > > Nov 8 19:28:23 arch kernel: [ cut here ] > Nov 8 19:28:23 arch kernel: kernel BUG at drivers/gpu/drm/ttm/ttm_bo.c:1628! Quite puzzling it is as if there was already a bo at same offset in rb tree but not in vm mm. Maybe some other race in destruction... Cheers, Jerome Glisse ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31463] VLC crashes on fullscreen with GLX output and colortiling enabled
https://bugs.freedesktop.org/show_bug.cgi?id=31463 Trevour changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Comment #4 from Trevour 2010-11-08 11:30:44 PST --- That was it - I've got two kernels(2.6.36-amd64-drt-pageflip+ and 2.6.36-amd64-drt-pageflip2+); GRUB2(GRUB classic stopped working for me) got them in the wrong order(placing the former before the latter), so I swapped them in grub.cfg, which apparently got regenerate somewhere along the line, leaving me with the first round of pageflip patches. I've deleted the old kernel to make sure this doesn't happen again. -- 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 31463] VLC crashes on fullscreen with GLX output and colortiling enabled
https://bugs.freedesktop.org/show_bug.cgi?id=31463 Trevour changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Comment #4 from Trevour 2010-11-08 11:30:44 PST --- That was it - I've got two kernels(2.6.36-amd64-drt-pageflip+ and 2.6.36-amd64-drt-pageflip2+); GRUB2(GRUB classic stopped working for me) got them in the wrong order(placing the former before the latter), so I swapped them in grub.cfg, which apparently got regenerate somewhere along the line, leaving me with the first round of pageflip patches. I've deleted the old kernel to make sure this doesn't happen again. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH 2/2] drm/radeon/kms: fix bugs in ddc and cd path router code
From: Tyson Whitehead
This is a follow on to:
2b5b1d7da9583484b3a9e7e375a90ca0e8ca07c2
(drm/radeon/kms: add support for clock/data path routers)
That patch completed mux support for ddc and cd line routing
between connectors. This patch fixes an indexing typo that was
resulting in the atom bios router objects not always being walked,
ensures the validity entries for the reused router structure are
reset for every connector object walked, and corrects the masking
operations used to update the mux control bits.
Fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=31339
Signed-off-by: Tyson Whitehead
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/radeon_atombios.c |9 +++--
drivers/gpu/drm/radeon/radeon_i2c.c |8
2 files changed, 7 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_atombios.c
b/drivers/gpu/drm/radeon/radeon_atombios.c
index 07e3afb..0ca7a5a 100644
--- a/drivers/gpu/drm/radeon/radeon_atombios.c
+++ b/drivers/gpu/drm/radeon/radeon_atombios.c
@@ -526,9 +526,6 @@ bool
radeon_get_atom_connector_info_from_object_table(struct drm_device *dev)
if (crev < 2)
return false;
- router.ddc_valid = false;
- router.cd_valid = false;
-
obj_header = (ATOM_OBJECT_HEADER *) (ctx->bios + data_offset);
path_obj = (ATOM_DISPLAY_OBJECT_PATH_TABLE *)
(ctx->bios + data_offset +
@@ -625,6 +622,8 @@ bool
radeon_get_atom_connector_info_from_object_table(struct drm_device *dev)
if (connector_type == DRM_MODE_CONNECTOR_Unknown)
continue;
+ router.ddc_valid = false;
+ router.cd_valid = false;
for (j = 0; j < ((le16_to_cpu(path->usSize) - 8) / 2);
j++) {
uint8_t grph_obj_id, grph_obj_num,
grph_obj_type;
@@ -648,10 +647,8 @@ bool
radeon_get_atom_connector_info_from_object_table(struct drm_device *dev)
usDeviceTag));
} else if (grph_obj_type ==
GRAPH_OBJECT_TYPE_ROUTER) {
- router.ddc_valid = false;
- router.cd_valid = false;
for (k = 0; k <
router_obj->ucNumberOfObjects; k++) {
- u16 router_obj_id =
le16_to_cpu(router_obj->asObjects[j].usObjectID);
+ u16 router_obj_id =
le16_to_cpu(router_obj->asObjects[k].usObjectID);
if
(le16_to_cpu(path->usGraphicObjIds[j]) == router_obj_id) {
ATOM_COMMON_RECORD_HEADER *record = (ATOM_COMMON_RECORD_HEADER *)
(ctx->bios +
data_offset +
diff --git a/drivers/gpu/drm/radeon/radeon_i2c.c
b/drivers/gpu/drm/radeon/radeon_i2c.c
index 24b8a8b..0cfbba0 100644
--- a/drivers/gpu/drm/radeon/radeon_i2c.c
+++ b/drivers/gpu/drm/radeon/radeon_i2c.c
@@ -1095,14 +1095,14 @@ void radeon_router_select_ddc_port(struct
radeon_connector *radeon_connector)
radeon_i2c_get_byte(radeon_connector->router_bus,
radeon_connector->router.i2c_addr,
0x3, &val);
- val &= radeon_connector->router.ddc_mux_control_pin;
+ val &= ~radeon_connector->router.ddc_mux_control_pin;
radeon_i2c_put_byte(radeon_connector->router_bus,
radeon_connector->router.i2c_addr,
0x3, val);
radeon_i2c_get_byte(radeon_connector->router_bus,
radeon_connector->router.i2c_addr,
0x1, &val);
- val &= radeon_connector->router.ddc_mux_control_pin;
+ val &= ~radeon_connector->router.ddc_mux_control_pin;
val |= radeon_connector->router.ddc_mux_state;
radeon_i2c_put_byte(radeon_connector->router_bus,
radeon_connector->router.i2c_addr,
@@ -1120,14 +1120,14 @@ void radeon_router_select_cd_port(struct
radeon_connector *radeon_connector)
radeon_i2c_get_byte(radeon_connector->router_bus,
radeon_connector->router.i2c_addr,
0x3, &val);
- val &= radeon_connector->router.cd_mux_control_pin;
+ val &= ~radeon_connector->router.cd_mux_control_pin;
radeon_i2c_put_byte(radeon_connector->router_bus,
radeon_connector->router.i2c_addr,
0x3, val);
radeon_i2c_get_byte(radeon_connector->router_bus,
radeon_connector->router.i2c_addr,
0x1, &val);
- val &= radeon_connector->router.cd_mux_control_pin;
+ val &= ~radeon_connector->router.cd_mux_control_pin
[PATCH 1/2] drm/radeon/kms: add support for clock/data path routers
This is a follow on to:
26b5bc986423cf3887e09188cb662ed651c5374d
(drm/radeon/kms: add support for router objects)
That patch added support for systems that use a mux to control
the ddc line routing between the connectors. This patch adds
support for systems that use a mux to control the encoder
clock and data path routing to the connectors.
Should fix:
https://bugs.freedesktop.org/show_bug.cgi?id=31339
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/radeon_atombios.c | 26 +-
drivers/gpu/drm/radeon/radeon_connectors.c |4 +-
drivers/gpu/drm/radeon/radeon_display.c| 18 +++-
drivers/gpu/drm/radeon/radeon_encoders.c |8 +
drivers/gpu/drm/radeon/radeon_i2c.c| 41 ++-
drivers/gpu/drm/radeon/radeon_mode.h | 17 ---
6 files changed, 85 insertions(+), 29 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_atombios.c
b/drivers/gpu/drm/radeon/radeon_atombios.c
index ca33baf..07e3afb 100644
--- a/drivers/gpu/drm/radeon/radeon_atombios.c
+++ b/drivers/gpu/drm/radeon/radeon_atombios.c
@@ -526,7 +526,8 @@ bool
radeon_get_atom_connector_info_from_object_table(struct drm_device *dev)
if (crev < 2)
return false;
- router.valid = false;
+ router.ddc_valid = false;
+ router.cd_valid = false;
obj_header = (ATOM_OBJECT_HEADER *) (ctx->bios + data_offset);
path_obj = (ATOM_DISPLAY_OBJECT_PATH_TABLE *)
@@ -647,7 +648,8 @@ bool
radeon_get_atom_connector_info_from_object_table(struct drm_device *dev)
usDeviceTag));
} else if (grph_obj_type ==
GRAPH_OBJECT_TYPE_ROUTER) {
- router.valid = false;
+ router.ddc_valid = false;
+ router.cd_valid = false;
for (k = 0; k <
router_obj->ucNumberOfObjects; k++) {
u16 router_obj_id =
le16_to_cpu(router_obj->asObjects[j].usObjectID);
if
(le16_to_cpu(path->usGraphicObjIds[j]) == router_obj_id) {
@@ -657,6 +659,7 @@ bool
radeon_get_atom_connector_info_from_object_table(struct drm_device *dev)
ATOM_I2C_RECORD
*i2c_record;
ATOM_I2C_ID_CONFIG_ACCESS *i2c_config;
ATOM_ROUTER_DDC_PATH_SELECT_RECORD *ddc_path;
+
ATOM_ROUTER_DATA_CLOCK_PATH_SELECT_RECORD *cd_path;
ATOM_SRC_DST_TABLE_FOR_ONE_OBJECT *router_src_dst_table =
(ATOM_SRC_DST_TABLE_FOR_ONE_OBJECT *)
(ctx->bios +
data_offset +
@@ -690,10 +693,18 @@ bool
radeon_get_atom_connector_info_from_object_table(struct drm_device *dev)
case
ATOM_ROUTER_DDC_PATH_SELECT_RECORD_TYPE:
ddc_path = (ATOM_ROUTER_DDC_PATH_SELECT_RECORD *)
record;
-
router.valid = true;
-
router.mux_type = ddc_path->ucMuxType;
-
router.mux_control_pin = ddc_path->ucMuxControlPin;
-
router.mux_state = ddc_path->ucMuxState[enum_id];
+
router.ddc_valid = true;
+
router.ddc_mux_type = ddc_path->ucMuxType;
+
router.ddc_mux_control_pin = ddc_path->ucMuxControlPin;
+
router.ddc_mux_state = ddc_path->ucMuxState[enum_id];
+ break;
+ case
ATOM_ROUTER_DATA_CLOCK_PATH_SELECT_RECORD_TYPE:
+ cd_path
= (ATOM_ROUTER_DATA_CLOCK_PATH_SELECT_RECORD *)
+
record;
+
router.cd_valid = true;
+
Re: Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: > On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: > > On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: > > > I can trigger a kernel crash on my system by simply loading this png > > > image with firefox: > > > http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg > > > > Sorry the above link is wrong, this is the right one (that triggers the > > crash): > > http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png > > I triggered it a few more times and took the attached picture. > It points to the BUG() call at drivers/gpu/drm/ttm/ttm_bo.c:1628 . > (Sorry for the bad picture quality) And here the same BUG in plaintext (should be a bit easier to read): Nov 8 19:28:23 arch kernel: [ cut here ] Nov 8 19:28:23 arch kernel: kernel BUG at drivers/gpu/drm/ttm/ttm_bo.c:1628! Nov 8 19:28:23 arch kernel: invalid opcode: [#1] PREEMPT SMP Nov 8 19:28:23 arch kernel: last sysfs file: /sys/devices/pci:00/:00:18.3/temp1_input Nov 8 19:28:23 arch kernel: CPU 1 Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Not tainted 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name Nov 8 19:28:23 arch kernel: RIP: 0010:[] [] ttm_bo_init+0x30f/0x340 Nov 8 19:28:23 arch kernel: RSP: 0018:88011b0fbbe8 EFLAGS: 00010246 Nov 8 19:28:23 arch kernel: RAX: 8800da881778 RBX: 8800da881620 RCX: 88011b15ed78 Nov 8 19:28:23 arch kernel: RDX: 8800c1556040 RSI: 88011ff22770 RDI: 0017adfb Nov 8 19:28:23 arch kernel: RBP: 8800da881648 R08: R09: 8800c1556040 Nov 8 19:28:23 arch kernel: R10: 0ff85205 R11: 8800dae19200 R12: 0001 Nov 8 19:28:23 arch kernel: R13: 88011ff22528 R14: 88011ff22778 R15: Nov 8 19:28:23 arch kernel: FS: 7f2043043700() GS:8800dfc8() knlGS: Nov 8 19:28:23 arch kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 8 19:28:23 arch kernel: CR2: 7f203d057000 CR3: 00011b12b000 CR4: 06e0 Nov 8 19:28:23 arch kernel: DR0: DR1: DR2: Nov 8 19:28:23 arch kernel: DR3: DR6: 0ff0 DR7: 0400 Nov 8 19:28:23 arch kernel: Process X (pid: 1541, threadinfo 88011b0fa000, task 88011c959c20) Nov 8 19:28:23 arch kernel: Stack: Nov 8 19:28:23 arch kernel: 8800da881648 88011b0fbd00 8800da881600 Nov 8 19:28:23 arch kernel: 88011ff22000 0001 fff4 Nov 8 19:28:23 arch kernel: 88011b0fbd00 8125294d 0001 Nov 8 19:28:23 arch kernel: Call Trace: Nov 8 19:28:23 arch kernel: [] ? radeon_bo_create+0x14d/0x250 Nov 8 19:28:23 arch kernel: [] ? radeon_ttm_bo_destroy+0x0/0xb0 Nov 8 19:28:23 arch kernel: [] ? radeon_gem_object_create+0x8c/0x130 Nov 8 19:28:23 arch kernel: [] ? radeon_gem_create_ioctl+0x54/0xd0 Nov 8 19:28:23 arch kernel: [] ? sock_aio_read+0x10d/0x120 Nov 8 19:28:23 arch kernel: [] ? drm_ioctl+0x39c/0x450 Nov 8 19:28:23 arch kernel: [] ? radeon_gem_create_ioctl+0x0/0xd0 Nov 8 19:28:23 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610 Nov 8 19:28:23 arch kernel: [] ? sys_ioctl+0x49/0x80 Nov 8 19:28:23 arch kernel: [] ? sys_read+0x4e/0x90 Nov 8 19:28:23 arch kernel: [] ? system_call_fastpath+0x16/0x1b Nov 8 19:28:23 arch kernel: Code: e8 fb ff ff 85 c0 0f 85 68 ff ff ff 48 8b 7c 24 08 89 04 24 e8 83 d9 ff ff 8b 04 24 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 <0f> 0b 48 c7 c7 60 a4 55 81 31 c0 e8 14 80 22 00 b8 ea ff ff ff Nov 8 19:28:23 arch kernel: RIP [] ttm_bo_init+0x30f/0x340 Nov 8 19:28:23 arch kernel: RSP Nov 8 19:28:23 arch kernel: ---[ end trace 328a9acba7691d6e ]--- Nov 8 19:28:23 arch kernel: note: X[1541] exited with preempt_count 1 Nov 8 19:28:23 arch kernel: BUG: scheduling while atomic: X/1541/0x1002 Nov 8 19:28:23 arch kernel: Pid: 1541, comm: X Tainted: G D 2.6.37-rc1-00116-g151f52f-dirty #31 Nov 8 19:28:23 arch kernel: Call Trace: Nov 8 19:28:23 arch kernel: [] ? schedule+0x639/0x850 Nov 8 19:28:23 arch kernel: [] ? __cond_resched+0x1d/0x30 Nov 8 19:28:23 arch kernel: [] ? _cond_resched+0x2f/0x40 Nov 8 19:28:23 arch kernel: [] ? unmap_vmas+0x82c/0x9c0 Nov 8 19:28:23 arch kernel: [] ? exit_mmap+0xe2/0x1a0 Nov 8 19:28:23 arch kernel: [] ? mmput+0x25/0xc0 Nov 8 19:28:23 arch kernel: [] ? exit_mm+0x104/0x130 Nov 8 19:28:23 arch kernel: [] ? hrtimer_try_to_cancel+0x3f/0x80 Nov 8 19:28:23 arch kernel: [] ? acct_collect+0x9a/0x1a0 Nov 8 19:28:23 arch kernel: [] ? do_exit+0x5aa/0x760 Nov 8 19:28:23 arch kernel: [] ? printk+0x40/0x45 Nov 8 19:28:23 arch kernel: [] ? kmsg_dump+0x7c/0x150 Nov 8 19:28:23 arch kernel: [] ? oops_end+0x9a/0xe0 Nov 8 19:28:23 arch
[Bug 31400] [RV740] Mipmapping broken in drm-radeon-next / drm-next
https://bugs.freedesktop.org/show_bug.cgi?id=31400 Jerome Glisse changed: What|Removed |Added Status|NEW |RESOLVED Resolution||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 31400] [RV740] Mipmapping broken in drm-radeon-next / drm-next
https://bugs.freedesktop.org/show_bug.cgi?id=31400 Jerome Glisse changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[bruce.e...@gmail.com: PATCH: ERROR: "video_output_register" [drivers/acpi/video.ko] und]
Hey guys, This failure also occurs on v2.6.37-rc1 (the branch Bruce is referring has been merged in Linus's tree). This compile failure can be demonstrated if one does not select VIDEO_OUTPUT_CONTROL and enables the Nouveau driver. The i915 has a similar fix in the Kconfig (ecb4aed78dcf09e48c8c34c8c2fa7f5c69344be6) but this one is lacking. Acked-by: Konrad Rzeszutek Wilk - Forwarded message from Bruce Edge - Date: Sun, 7 Nov 2010 17:56:38 -0800 From: Bruce Edge To: xen-devel at lists.xensource.com, Konrad Rzeszutek Wilk Subject: PATCH: pvops 2.6.36 patch for undefined! ERROR: "video_output_register" [drivers/acpi/video.ko] und This patch resolved the following link error: ERROR: "video_output_unregister" [drivers/acpi/video.ko] undefined! ERROR: "video_output_register" [drivers/acpi/video.ko] undefined! in this branch: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git- stable/xen-pcifront-0.8.2 --- old/drivers/gpu/drm/nouveau/Kconfig +++ new/drivers/gpu/drm/nouveau/Kconfig @@ -11,6 +11,7 @@ select FRAMEBUFFER_CONSOLE if !EMBEDDED select FB_BACKLIGHT if DRM_NOUVEAU_BACKLIGHT select ACPI_VIDEO if ACPI + select VIDEO_OUTPUT_CONTROL if ACPI help Choose this option for open-source nVidia support. -Bruce - End forwarded message -
[PATCH] drm/radeon/kms: fix thermal sensor reporting on rv6xx
Temperature is not shifted as on newer asics.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/r600.c |8 +---
1 files changed, 1 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/radeon/r600.c b/drivers/gpu/drm/radeon/r600.c
index 951af00..bd69299 100644
--- a/drivers/gpu/drm/radeon/r600.c
+++ b/drivers/gpu/drm/radeon/r600.c
@@ -106,14 +106,8 @@ u32 rv6xx_get_temp(struct radeon_device *rdev)
{
u32 temp = (RREG32(CG_THERMAL_STATUS) & ASIC_T_MASK) >>
ASIC_T_SHIFT;
- u32 actual_temp = 0;
- if ((temp >> 7) & 1)
- actual_temp = 0;
- else
- actual_temp = (temp >> 1) & 0xff;
-
- return actual_temp * 1000;
+ return temp * 1000;
}
void r600_pm_get_dynpm_state(struct radeon_device *rdev)
--
1.7.1.1
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31152] Please backport r200 fix to r100 and r300c
https://bugs.freedesktop.org/show_bug.cgi?id=31152 --- Comment #4 from Alexei 2010-11-08 09:38:36 PST --- Is there an estimate for when this might happen? Thank you! -- 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 31152] Please backport r200 fix to r100 and r300c
https://bugs.freedesktop.org/show_bug.cgi?id=31152 --- Comment #4 from Alexei 2010-11-08 09:38:36 PST --- Is there an estimate for when this might happen? Thank you! -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 31400] [RV740] Mipmapping broken in drm-radeon-next / drm-next
https://bugs.freedesktop.org/show_bug.cgi?id=31400 --- Comment #1 from Alex Deucher 2010-11-08 09:12:41 PST --- Fixed in mesa git master and 7.9. Although, I'm not sure how best to handle backwards compat for old userspace. -- 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 31400] [RV740] Mipmapping broken in drm-radeon-next / drm-next
https://bugs.freedesktop.org/show_bug.cgi?id=31400 --- Comment #1 from Alex Deucher 2010-11-08 09:12:41 PST --- Fixed in mesa git master and 7.9. Although, I'm not sure how best to handle backwards compat for old userspace. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: > I can trigger a kernel crash on my system by simply loading this png > image with firefox: > http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg Sorry the above link is wrong, this is the right one (that triggers the crash): http://cdsweb.cern.ch/record/1305179/files/HI-150431-630470-huge.png -- Markus ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference
I can trigger a kernel crash on my system by simply loading this png image with firefox: http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg The system has an embedded RS780 and is running the latest git kernel. (Xorg.0.log is attached) The crash looks as follows: Nov 8 17:37:21 arch kernel: BUG: unable to handle kernel NULL pointer dereference at 0020 Nov 8 17:37:21 arch kernel: IP: [] _raw_write_lock+0xf/0x20 Nov 8 17:37:21 arch kernel: PGD 11bf20067 PUD 11bfa7067 PMD 0 Nov 8 17:37:21 arch kernel: Oops: 0002 [#1] PREEMPT SMP Nov 8 17:37:21 arch kernel: last sysfs file: /sys/devices/pci:00/:00:18.3/temp1_input Nov 8 17:37:21 arch kernel: CPU 0 Nov 8 17:37:21 arch kernel: Pid: 1502, comm: X Not tainted 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name Nov 8 17:37:21 arch kernel: RIP: 0010:[] [] _raw_write_lock+0xf/0x20 Nov 8 17:37:21 arch kernel: RSP: 0018:88011b523cc0 EFLAGS: 00010202 Nov 8 17:37:21 arch kernel: RAX: 88011b523fd8 RBX: 0020 RCX: Nov 8 17:37:22 arch kernel: RDX: RSI: 8120a6f0 RDI: 0020 Nov 8 17:37:22 arch kernel: RBP: 880113f39c48 R08: 0006 R09: 0006 Nov 8 17:37:22 arch kernel: R10: 0006 R11: 0006 R12: 0071 Nov 8 17:37:22 arch kernel: R13: 8800c07ffb40 R14: 40086409 R15: fff2 Nov 8 17:37:22 arch kernel: FS: 7f3786cdc700() GS:8800dfc0() knlGS: Nov 8 17:37:22 arch kernel: CS: 0010 DS: ES: CR0: 8005003b Nov 8 17:37:22 arch kernel: CR2: 0020 CR3: 00011f60a000 CR4: 06f0 Nov 8 17:37:22 arch kernel: DR0: DR1: DR2: Nov 8 17:37:22 arch kernel: DR3: DR6: 0ff0 DR7: 0400 Nov 8 17:37:22 arch kernel: Process X (pid: 1502, threadinfo 88011b522000, task 88011cc3d460) Nov 8 17:37:22 arch kernel: Stack: Nov 8 17:37:22 arch kernel: 8121cbb8 0292 88011ffabbc0 88011b523d20 Nov 8 17:37:22 arch kernel: 81252a92 0296 88011d9410a8 Nov 8 17:37:22 arch kernel: 8800c07ffb40 8120a6f0 8126711e 88011f632a90 Nov 8 17:37:22 arch kernel: Call Trace: Nov 8 17:37:22 arch kernel: [] ? ttm_bo_unref+0x28/0x50 Nov 8 17:37:22 arch kernel: [] ? radeon_bo_unref+0x42/0x80 Nov 8 17:37:22 arch kernel: [] ? drm_gem_object_free+0x0/0x30 Nov 8 17:37:22 arch kernel: [] ? radeon_gem_object_free+0x2e/0x50 Nov 8 17:37:22 arch kernel: [] ? kref_put+0x33/0x70 Nov 8 17:37:22 arch kernel: [] ? drm_gem_close_ioctl+0xc0/0xf0 Nov 8 17:37:22 arch kernel: [] ? drm_ioctl+0x39c/0x450 Nov 8 17:37:22 arch kernel: [] ? drm_gem_close_ioctl+0x0/0xf0 Nov 8 17:37:22 arch kernel: [] ? do_sync_read+0xbf/0x100 Nov 8 17:37:22 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610 Nov 8 17:37:22 arch kernel: [] ? sys_ioctl+0x49/0x80 Nov 8 17:37:22 arch kernel: [] ? sys_read+0x4e/0x90 Nov 8 17:37:22 arch kernel: [] ? system_call_fastpath+0x16/0x1b Nov 8 17:37:22 arch kernel: Code: 83 c4 08 c3 e8 f3 dd ff ff 31 c0 eb f2 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 65 48 8b 04 25 c8 b6 00 00 ff 80 44 e0 ff ff 81 2f 00 00 00 01 74 05 e8 83 ff d3 ff c3 66 90 9c 58 fa 65 Nov 8 17:37:22 arch kernel: RIP [] _raw_write_lock+0xf/0x20 Nov 8 17:37:22 arch kernel: RSP Nov 8 17:37:22 arch kernel: CR2: 0020 Nov 8 17:37:22 arch kernel: BUG: unable to handle kernel NULL pointer dereference at 0088 Nov 8 17:37:22 arch kernel: IP: [] _raw_spin_lock+0x14/0x30 Nov 8 17:37:22 arch kernel: PGD 11bf20067 PUD 11bfa7067 PMD 0 Nov 8 17:37:22 arch kernel: Oops: 0002 [#2] PREEMPT SMP Nov 8 17:37:22 arch kernel: last sysfs file: /sys/devices/pci:00/:00:18.3/temp1_input Nov 8 17:37:22 arch kernel: CPU 0 Nov 8 17:37:22 arch kernel: Pid: 1502, comm: X Not tainted 2.6.37-rc1-00116-g151f52f-dirty #31 M4A78T-E/System Product Name Nov 8 17:37:22 arch kernel: RIP: 0010:[] [] _raw_spin_lock+0x14/0x30 Nov 8 17:37:22 arch kernel: RSP: 0018:88011b523660 EFLAGS: 00010002 Nov 8 17:37:22 arch kernel: RAX: 0100 RBX: 88011ff2c048 RCX: Nov 8 17:37:22 arch kernel: RDX: RSI: 0001 RDI: 0088 Nov 8 17:37:22 arch kernel: RBP: 0088 R08: R09: 816a0a00 Nov 8 17:37:22 arch kernel: R10: R11: 0002 R12: 0001 Nov 8 17:37:22 arch kernel: R13: R14: R15: Nov 8 17:37:22 arch kernel: FS: 7f3786cdc700() GS:8800dfc0() knlGS: Nov 8 17:37:22 arch kernel: CS: 0010 DS: ES: CR0: 8005003b Nov 8 17:37:22 arch kernel: CR2: 0088 CR3:
[bruce.e...@gmail.com: PATCH: ERROR: "video_output_register" [drivers/acpi/video.ko] und]
Hey guys, This failure also occurs on v2.6.37-rc1 (the branch Bruce is referring has been merged in Linus's tree). This compile failure can be demonstrated if one does not select VIDEO_OUTPUT_CONTROL and enables the Nouveau driver. The i915 has a similar fix in the Kconfig (ecb4aed78dcf09e48c8c34c8c2fa7f5c69344be6) but this one is lacking. Acked-by: Konrad Rzeszutek Wilk - Forwarded message from Bruce Edge - Date: Sun, 7 Nov 2010 17:56:38 -0800 From: Bruce Edge To: xen-de...@lists.xensource.com, Konrad Rzeszutek Wilk Subject: PATCH: pvops 2.6.36 patch for undefined! ERROR: "video_output_register" [drivers/acpi/video.ko] und This patch resolved the following link error: ERROR: "video_output_unregister" [drivers/acpi/video.ko] undefined! ERROR: "video_output_register" [drivers/acpi/video.ko] undefined! in this branch: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git- stable/xen-pcifront-0.8.2 --- old/drivers/gpu/drm/nouveau/Kconfig +++ new/drivers/gpu/drm/nouveau/Kconfig @@ -11,6 +11,7 @@ select FRAMEBUFFER_CONSOLE if !EMBEDDED select FB_BACKLIGHT if DRM_NOUVEAU_BACKLIGHT select ACPI_VIDEO if ACPI + select VIDEO_OUTPUT_CONTROL if ACPI help Choose this option for open-source nVidia support. -Bruce - End forwarded message - ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31463] VLC crashes on fullscreen with GLX output and colortiling enabled
https://bugs.freedesktop.org/show_bug.cgi?id=31463 --- Comment #3 from Alex Deucher 2010-11-08 08:17:17 PST --- Are you sure you've booted the right kernel? You should never hit that message with the patch applied. Also, the line numbers indicate a non-patched kernel. -- 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 31463] VLC crashes on fullscreen with GLX output and colortiling enabled
https://bugs.freedesktop.org/show_bug.cgi?id=31463 --- Comment #3 from Alex Deucher 2010-11-08 08:17:17 PST --- Are you sure you've booted the right kernel? You should never hit that message with the patch applied. Also, the line numbers indicate a non-patched kernel. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH 2/2] drm/radeon/kms: fix bugs in ddc and cd path router code
From: Tyson Whitehead
This is a follow on to:
2b5b1d7da9583484b3a9e7e375a90ca0e8ca07c2
(drm/radeon/kms: add support for clock/data path routers)
That patch completed mux support for ddc and cd line routing
between connectors. This patch fixes an indexing typo that was
resulting in the atom bios router objects not always being walked,
ensures the validity entries for the reused router structure are
reset for every connector object walked, and corrects the masking
operations used to update the mux control bits.
Fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=31339
Signed-off-by: Tyson Whitehead
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/radeon_atombios.c |9 +++--
drivers/gpu/drm/radeon/radeon_i2c.c |8
2 files changed, 7 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_atombios.c
b/drivers/gpu/drm/radeon/radeon_atombios.c
index 07e3afb..0ca7a5a 100644
--- a/drivers/gpu/drm/radeon/radeon_atombios.c
+++ b/drivers/gpu/drm/radeon/radeon_atombios.c
@@ -526,9 +526,6 @@ bool
radeon_get_atom_connector_info_from_object_table(struct drm_device *dev)
if (crev < 2)
return false;
- router.ddc_valid = false;
- router.cd_valid = false;
-
obj_header = (ATOM_OBJECT_HEADER *) (ctx->bios + data_offset);
path_obj = (ATOM_DISPLAY_OBJECT_PATH_TABLE *)
(ctx->bios + data_offset +
@@ -625,6 +622,8 @@ bool
radeon_get_atom_connector_info_from_object_table(struct drm_device *dev)
if (connector_type == DRM_MODE_CONNECTOR_Unknown)
continue;
+ router.ddc_valid = false;
+ router.cd_valid = false;
for (j = 0; j < ((le16_to_cpu(path->usSize) - 8) / 2);
j++) {
uint8_t grph_obj_id, grph_obj_num,
grph_obj_type;
@@ -648,10 +647,8 @@ bool
radeon_get_atom_connector_info_from_object_table(struct drm_device *dev)
usDeviceTag));
} else if (grph_obj_type ==
GRAPH_OBJECT_TYPE_ROUTER) {
- router.ddc_valid = false;
- router.cd_valid = false;
for (k = 0; k <
router_obj->ucNumberOfObjects; k++) {
- u16 router_obj_id =
le16_to_cpu(router_obj->asObjects[j].usObjectID);
+ u16 router_obj_id =
le16_to_cpu(router_obj->asObjects[k].usObjectID);
if
(le16_to_cpu(path->usGraphicObjIds[j]) == router_obj_id) {
ATOM_COMMON_RECORD_HEADER *record = (ATOM_COMMON_RECORD_HEADER *)
(ctx->bios +
data_offset +
diff --git a/drivers/gpu/drm/radeon/radeon_i2c.c
b/drivers/gpu/drm/radeon/radeon_i2c.c
index 24b8a8b..0cfbba0 100644
--- a/drivers/gpu/drm/radeon/radeon_i2c.c
+++ b/drivers/gpu/drm/radeon/radeon_i2c.c
@@ -1095,14 +1095,14 @@ void radeon_router_select_ddc_port(struct
radeon_connector *radeon_connector)
radeon_i2c_get_byte(radeon_connector->router_bus,
radeon_connector->router.i2c_addr,
0x3, &val);
- val &= radeon_connector->router.ddc_mux_control_pin;
+ val &= ~radeon_connector->router.ddc_mux_control_pin;
radeon_i2c_put_byte(radeon_connector->router_bus,
radeon_connector->router.i2c_addr,
0x3, val);
radeon_i2c_get_byte(radeon_connector->router_bus,
radeon_connector->router.i2c_addr,
0x1, &val);
- val &= radeon_connector->router.ddc_mux_control_pin;
+ val &= ~radeon_connector->router.ddc_mux_control_pin;
val |= radeon_connector->router.ddc_mux_state;
radeon_i2c_put_byte(radeon_connector->router_bus,
radeon_connector->router.i2c_addr,
@@ -1120,14 +1120,14 @@ void radeon_router_select_cd_port(struct
radeon_connector *radeon_connector)
radeon_i2c_get_byte(radeon_connector->router_bus,
radeon_connector->router.i2c_addr,
0x3, &val);
- val &= radeon_connector->router.cd_mux_control_pin;
+ val &= ~radeon_connector->router.cd_mux_control_pin;
radeon_i2c_put_byte(radeon_connector->router_bus,
radeon_connector->router.i2c_addr,
0x3, val);
radeon_i2c_get_byte(radeon_connector->router_bus,
radeon_connector->router.i2c_addr,
0x1, &val);
- val &= radeon_connector->router.cd_mux_control_pin;
+ val &= ~radeon_connector->router.cd_mux_control
[PATCH 1/2] drm/radeon/kms: add support for clock/data path routers
This is a follow on to:
26b5bc986423cf3887e09188cb662ed651c5374d
(drm/radeon/kms: add support for router objects)
That patch added support for systems that use a mux to control
the ddc line routing between the connectors. This patch adds
support for systems that use a mux to control the encoder
clock and data path routing to the connectors.
Should fix:
https://bugs.freedesktop.org/show_bug.cgi?id=31339
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/radeon_atombios.c | 26 +-
drivers/gpu/drm/radeon/radeon_connectors.c |4 +-
drivers/gpu/drm/radeon/radeon_display.c| 18 +++-
drivers/gpu/drm/radeon/radeon_encoders.c |8 +
drivers/gpu/drm/radeon/radeon_i2c.c| 41 ++-
drivers/gpu/drm/radeon/radeon_mode.h | 17 ---
6 files changed, 85 insertions(+), 29 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_atombios.c
b/drivers/gpu/drm/radeon/radeon_atombios.c
index ca33baf..07e3afb 100644
--- a/drivers/gpu/drm/radeon/radeon_atombios.c
+++ b/drivers/gpu/drm/radeon/radeon_atombios.c
@@ -526,7 +526,8 @@ bool
radeon_get_atom_connector_info_from_object_table(struct drm_device *dev)
if (crev < 2)
return false;
- router.valid = false;
+ router.ddc_valid = false;
+ router.cd_valid = false;
obj_header = (ATOM_OBJECT_HEADER *) (ctx->bios + data_offset);
path_obj = (ATOM_DISPLAY_OBJECT_PATH_TABLE *)
@@ -647,7 +648,8 @@ bool
radeon_get_atom_connector_info_from_object_table(struct drm_device *dev)
usDeviceTag));
} else if (grph_obj_type ==
GRAPH_OBJECT_TYPE_ROUTER) {
- router.valid = false;
+ router.ddc_valid = false;
+ router.cd_valid = false;
for (k = 0; k <
router_obj->ucNumberOfObjects; k++) {
u16 router_obj_id =
le16_to_cpu(router_obj->asObjects[j].usObjectID);
if
(le16_to_cpu(path->usGraphicObjIds[j]) == router_obj_id) {
@@ -657,6 +659,7 @@ bool
radeon_get_atom_connector_info_from_object_table(struct drm_device *dev)
ATOM_I2C_RECORD
*i2c_record;
ATOM_I2C_ID_CONFIG_ACCESS *i2c_config;
ATOM_ROUTER_DDC_PATH_SELECT_RECORD *ddc_path;
+
ATOM_ROUTER_DATA_CLOCK_PATH_SELECT_RECORD *cd_path;
ATOM_SRC_DST_TABLE_FOR_ONE_OBJECT *router_src_dst_table =
(ATOM_SRC_DST_TABLE_FOR_ONE_OBJECT *)
(ctx->bios +
data_offset +
@@ -690,10 +693,18 @@ bool
radeon_get_atom_connector_info_from_object_table(struct drm_device *dev)
case
ATOM_ROUTER_DDC_PATH_SELECT_RECORD_TYPE:
ddc_path = (ATOM_ROUTER_DDC_PATH_SELECT_RECORD *)
record;
-
router.valid = true;
-
router.mux_type = ddc_path->ucMuxType;
-
router.mux_control_pin = ddc_path->ucMuxControlPin;
-
router.mux_state = ddc_path->ucMuxState[enum_id];
+
router.ddc_valid = true;
+
router.ddc_mux_type = ddc_path->ucMuxType;
+
router.ddc_mux_control_pin = ddc_path->ucMuxControlPin;
+
router.ddc_mux_state = ddc_path->ucMuxState[enum_id];
+ break;
+ case
ATOM_ROUTER_DATA_CLOCK_PATH_SELECT_RECORD_TYPE:
+ cd_path
= (ATOM_ROUTER_DATA_CLOCK_PATH_SELECT_RECORD *)
+
record;
+
router.cd_valid = true;
+
[Bug 31463] VLC crashes on fullscreen with GLX output and colortiling enabled
https://bugs.freedesktop.org/show_bug.cgi?id=31463 --- Comment #2 from Trevour 2010-11-08 08:00:52 PST --- I pulled the drm-core-next branch in order to apply the pageflipping patches(I also pulled drm-radeon-testing before that to apply the first batch), so I've got the 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 31463] VLC crashes on fullscreen with GLX output and colortiling enabled
https://bugs.freedesktop.org/show_bug.cgi?id=31463 --- Comment #2 from Trevour 2010-11-08 08:00:52 PST --- I pulled the drm-core-next branch in order to apply the pageflipping patches(I also pulled drm-radeon-testing before that to apply the first batch), so I've got the patch. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: [PATCH] gpu: drm: vmwgfx: fix information leak to userland
On 11/06/2010 03:41 PM, Vasiliy Kulikov wrote: Structure drm_vmw_fence_rep is copied to userland with field "pad64" uninitialized. It leads to leaking of contents of kernel stack memory. Signed-off-by: Vasiliy Kulikov --- Compile tested. drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c b/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c index 51d9f9f..76954e3 100644 --- a/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c @@ -691,6 +691,7 @@ int vmw_execbuf_ioctl(struct drm_device *dev, void *data, fence_rep.error = ret; fence_rep.fence_seq = (uint64_t) sequence; + fence_rep.pad64 = 0; user_fence_rep = (struct drm_vmw_fence_rep __user *) (unsigned long)arg->fence_rep; Reviewed-by: Thomas Hellstrom ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
INFO: possible circular locking dependency detected [v2.6.37-rc1-152-g6c88078]
Hi,
I've been seeing these lately, Xorg version is 1.9.0 with latest git kernel.
===
[ INFO: possible circular locking dependency detected ]
2.6.37-rc1-uwe1+ #4
---
Xorg/1401 is trying to acquire lock:
(&mm->mmap_sem){++}, at: [] might_fault+0x4b/0xa0
but task is already holding lock:
(&dev->struct_mutex){+.+.+.}, at: []
i915_mutex_lock_interruptible+0x3c/0x60 [i915]
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&dev->struct_mutex){+.+.+.}:
[] lock_acquire+0x7c/0x120
[] mutex_lock_nested+0x60/0x330
[] drm_gem_mmap+0x3a/0x140 [drm]
[] mmap_region+0x2e2/0x430
[] do_mmap_pgoff+0x24f/0x2f0
[] sys_mmap_pgoff+0x7b/0x110
[] sysenter_do_call+0x12/0x36
-> #0 (&mm->mmap_sem){++}:
[] __lock_acquire+0x14a9/0x17d0
[] lock_acquire+0x7c/0x120
[] might_fault+0x7c/0xa0
[] _copy_from_user+0x3d/0x130
[] i915_gem_pwrite_ioctl+0x18c/0xb20 [i915]
[] drm_ioctl+0x1e2/0x440 [drm]
[] do_vfs_ioctl+0x9d/0x6c0
[] sys_ioctl+0x67/0x80
[] sysenter_do_call+0x12/0x36
other info that might help us debug this:
1 lock held by Xorg/1401:
#0: (&dev->struct_mutex){+.+.+.}, at: []
i915_mutex_lock_interruptible+0x3c/0x60 [i915]
stack backtrace:
Pid: 1401, comm: Xorg Not tainted 2.6.37-rc1-uwe1+ #4
Call Trace:
[] ? printk+0x1d/0x1f
[] print_circular_bug+0xc2/0xd0
[] __lock_acquire+0x14a9/0x17d0
[] ? sub_preempt_count+0x9/0x50
[] lock_acquire+0x7c/0x120
[] ? might_fault+0x4b/0xa0
[] might_fault+0x7c/0xa0
[] ? might_fault+0x4b/0xa0
[] _copy_from_user+0x3d/0x130
[] i915_gem_pwrite_ioctl+0x18c/0xb20 [i915]
[] ? might_fault+0x4b/0xa0
[] drm_ioctl+0x1e2/0x440 [drm]
[] ? i915_gem_pwrite_ioctl+0x0/0xb20 [i915]
[] ? smk_access+0xb3/0x1f0
[] ? smk_curacc+0x74/0xa0
[] ? drm_ioctl+0x0/0x440 [drm]
[] do_vfs_ioctl+0x9d/0x6c0
[] sys_ioctl+0x67/0x80
[] sysenter_do_call+0x12/0x36
thanks,
Uwe
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] gpu: drm: vmwgfx: fix information leak to userland
Structure drm_vmw_fence_rep is copied to userland with field "pad64" uninitialized. It leads to leaking of contents of kernel stack memory. Signed-off-by: Vasiliy Kulikov --- Compile tested. drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c b/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c index 51d9f9f..76954e3 100644 --- a/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c @@ -691,6 +691,7 @@ int vmw_execbuf_ioctl(struct drm_device *dev, void *data, fence_rep.error = ret; fence_rep.fence_seq = (uint64_t) sequence; + fence_rep.pad64 = 0; user_fence_rep = (struct drm_vmw_fence_rep __user *) (unsigned long)arg->fence_rep; -- 1.7.0.4 ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Radeon drm: dpms backlight problem / question / bug?
On 2010-11-02 08:20, Michel Dänzer wrote: On Mon, 2010-11-01 at 16:09 +0100, Prof. Dr. Klaus Kusche wrote: On my Dell Precision M6500, backlight power switching does not work, neither by using bl_power in /sys/backlight/... Please provide the full path of the file you're using. nor by using DPMS: * Any changes of bl_power are simply and silently ignored (no effect, except that brightness is set to minimum), although brightness tuning works fine (in other words: Both the generic ACPI BIOS driver and the in-kernel Dell laptop backlight driver can control backlight brightness, but not backlight power). * If DPMS becomes active, the screen contents on the internal display slowly becomes garbled or fades away (so video output drivers seem to be off), but the backlight remains on (which is very bad for battery power). The external screen (on display port) behaves even worse: It enters energy saving mode (backlight off) and immediately wakes up again, continuously cycling the backlight power every few seconds. Another problem which optically looks the same: Zapping the X server (Xorg 1.9.1, radeon 6.13.2) with Ctrl-Alt-Bksp leaves the system in an undefined state: * Similar to DPMS, the display fades away or gets garbled (video output off), but the backlight remains on. * It does not switch to the text console automatically, nor is it possible to switch manually with Ctrl-Alt-Fn. Configuration: * Kernel 2.6.35.7-grsec * Radeon DRM with KMS * Radeon framebuffer with backlight control enabled * The Radeon chip is a JUNIPER 0x1002:0x68A0, the kernel should contain all the microcode needed for it. * The displays are LCD1: INTERNAL_UNIPHY and DFP1: INTERNAL_UNIPHY1 Please provide the full Xorg.0.log file and dmesg output. I've sent the full logs on Nov 2nd. Did they arrive? Did they provide any insight? Anything else I can do / try / provide? Many thanks in advance for your help! -- Prof. Dr. Klaus Kusche Private address: Rainstraße 9/1, 88316 Isny, Germany +49 7562 6211377 klaus.kus...@computerix.info http://www.computerix.info Office address: NTA Isny gGmbH, Seidenstraße 12-35, 88316 Isny, Germany +49 7562 9707 36 kus...@nta-isny.de http://www.nta-isny.de ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31463] VLC crashes on fullscreen with GLX output and colortiling enabled
https://bugs.freedesktop.org/show_bug.cgi?id=31463 --- Comment #1 from Alex Deucher 2010-11-08 07:14:22 PST --- Should be fixed with this patch: http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=8f895da57da80b307efa2f94b5d4caf801e959a5 -- 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 31463] VLC crashes on fullscreen with GLX output and colortiling enabled
https://bugs.freedesktop.org/show_bug.cgi?id=31463 --- Comment #1 from Alex Deucher 2010-11-08 07:14:22 PST --- Should be fixed with this patch: http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=8f895da57da80b307efa2f94b5d4caf801e959a5 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: [PATCH] drm: idr_find (drm_gem_object_lookup) needs only rcu read locks
On Thu, 4 Nov 2010 10:09:53 +, Chris Wilson wrote: > /* Release reference and decrement refcount. */ > idr_remove(&filp->object_idr, handle); > spin_unlock(&filp->table_lock); > > + synchronize_rcu(); > + This is an absolute performance killer. Looks like we might have to endure call_rcu if we want to proceed down this path. -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 31463] New: VLC crashes on fullscreen with GLX output and colortiling enabled
https://bugs.freedesktop.org/show_bug.cgi?id=31463 Summary: VLC crashes on fullscreen with GLX output and colortiling enabled Product: Mesa Version: 7.9 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: bio_t...@yahoo.com It works in window mode, but it crashes the instant it switches to fullscreen, giving the familiar "drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See dmesg for more info."; I've checked and this isn't fixed in master, either; r600g performs as expected, so this is definitely a Mesa bug(I've already pulled the latest in the 7.9 branch). dmesg gives the following: [ 1953.411625] radeon :02:00.0: r600_cs_track_validate_cb:220 cb height (724) invalid [ 1953.411630] radeon :02:00.0: r600_packet3_check:1252 invalid cmd stream 502 [ 1953.411633] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! [ 1953.412662] vlc[9975]: segfault at 8 ip 00343e24718b sp 7f2e54a8e8b8 error 4 in libQtDBus.so.4.6.3[343e20+77000] -- 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 31463] New: VLC crashes on fullscreen with GLX output and colortiling enabled
https://bugs.freedesktop.org/show_bug.cgi?id=31463 Summary: VLC crashes on fullscreen with GLX output and colortiling enabled Product: Mesa Version: 7.9 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: bio_tube at yahoo.com It works in window mode, but it crashes the instant it switches to fullscreen, giving the familiar "drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See dmesg for more info."; I've checked and this isn't fixed in master, either; r600g performs as expected, so this is definitely a Mesa bug(I've already pulled the latest in the 7.9 branch). dmesg gives the following: [ 1953.411625] radeon :02:00.0: r600_cs_track_validate_cb:220 cb height (724) invalid [ 1953.411630] radeon :02:00.0: r600_packet3_check:1252 invalid cmd stream 502 [ 1953.411633] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! [ 1953.412662] vlc[9975]: segfault at 8 ip 00343e24718b sp 7f2e54a8e8b8 error 4 in libQtDBus.so.4.6.3[343e20+77000] -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
