| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 5 Apr 2011 18:31:41 +0200 From: Markus Trippelsdorf <markus@...ppelsdorf.de> To: linux-kernel@...r.kernel.org Cc: dri-devel@...ts.freedesktop.org Subject: Re: WARNING: at drivers/gpu/drm/ttm/ttm_page_alloc.c:758 On 2011.03.29 at 16:56 +0200, Markus Trippelsdorf wrote: > Just came across this WARNING (running latest git kernel): > > Mar 29 09:14:39 gentoo kernel: udev[888]: starting version 164 > Mar 29 15:45:45 gentoo kernel: ------------[ cut here ]------------ > Mar 29 15:45:45 gentoo kernel: WARNING: at drivers/gpu/drm/ttm/ttm_page_alloc.c:758 ttm_put_pages+0x1c6/0x2b0() > Mar 29 15:45:45 gentoo kernel: Hardware name: System Product Name It happened again today. ------------[ cut here ]------------ WARNING: at drivers/gpu/drm/ttm/ttm_page_alloc.c:758 ttm_put_pages+0x1c6/0x2c0() Hardware name: System Product Name Pid: 680, comm: kworker/u:6 Not tainted 2.6.39-rc1-00254-gd297f96 #5 Call Trace: [<ffffffff810736af>] warn_slowpath_common+0x6f/0xa0 [<ffffffff810737fa>] warn_slowpath_null+0x1a/0x20 [<ffffffff812c7726>] ttm_put_pages+0x1c6/0x2c0 [<ffffffff812bff7d>] ttm_tt_free_alloced_pages+0xbd/0x100 [<ffffffff812c0a5c>] ttm_tt_swapout+0x1bc/0x2c0 [<ffffffff812c2365>] ttm_bo_swapout+0x1a5/0x240 [<ffffffff812b5637>] ? drm_mm_kmalloc+0x37/0xe0 [<ffffffff812bf3b8>] ttm_shrink+0xd8/0x140 [<ffffffff8108eb01>] ? queue_work+0x21/0x60 [<ffffffff812bf420>] ? ttm_shrink+0x140/0x140 [<ffffffff812bf439>] ttm_shrink_work+0x19/0x20 [<ffffffff8108dade>] process_one_work+0x11e/0x4e0 [<ffffffff8108e4ce>] worker_thread+0x16e/0x360 [<ffffffff8108e360>] ? manage_workers.isra.28+0x260/0x260 [<ffffffff810932ac>] kthread+0x8c/0xa0 [<ffffffff8152a394>] kernel_thread_helper+0x4/0x10 [<ffffffff81093220>] ? kthread_flush_work_fn+0x20/0x20 [<ffffffff8152a390>] ? gs_change+0xb/0xb ---[ end trace cb7fc1aad109a0a7 ]--- ------------[ cut here ]------------ So its not a easily reproducible problem. My config and a full dmesg are attached, in case anybody is interested. -- Markus View attachment "config" of type "text/plain" (51024 bytes) View attachment "kern.log" of type "text/plain" (59771 bytes)
Powered by blists - more mailing lists