From: poma <pomidorabelisima@gmail.com>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Mailing-List fedora-kernel <kernel@lists.fedoraproject.org>
Subject: Re: WARNING ... drivers/gpu/drm/ttm/ttm_bo_vm.c...
Date: Thu, 10 Apr 2014 18:34:32 +0200 [thread overview]
Message-ID: <5346C818.3000107@gmail.com> (raw)
In-Reply-To: <534350F6.9050604@gmail.com>
On 08.04.2014 03:29, poma wrote:
> ...
> Command line: initrd=initrd.img
> inst.stage2=hd:LABEL=Fedora\x20rawhide\x20x86_64 xdriver=modesetting
> BOOT_IMAGE=vmlinuz
> Kernel command line: initrd=initrd.img
> inst.stage2=hd:LABEL=Fedora\x20rawhide\x20x86_64 xdriver=modesetting
> BOOT_IMAGE=vmlinuz
> ...
> ------------[ cut here ]------------
> WARNING: CPU: 1 PID: 1230 at drivers/gpu/drm/ttm/ttm_bo_vm.c:269
> ttm_bo_vm_open+0x52/0x80 [ttm]()
> CPU: 1 PID: 1230 Comm: Xorg Not tainted 3.15.0-0.rc0.git9.1.fc21.x86_64 #1
> Call Trace:
> [<ffffffff817db690>] dump_stack+0x4d/0x66
> [<ffffffff81096b9d>] warn_slowpath_common+0x7d/0xa0
> [<ffffffff81096cca>] warn_slowpath_null+0x1a/0x20
> [<ffffffffa0250452>] ttm_bo_vm_open+0x52/0x80 [ttm]
> [<ffffffff810956fe>] copy_process.part.23+0x1b9e/0x1e90
> [<ffffffff81095bb6>] do_fork+0xc6/0x4b0
> [<ffffffff811de68f>] ? might_fault+0x5f/0xb0
> [<ffffffff817ef695>] ? sysret_check+0x22/0x5d
> [<ffffffff81096026>] SyS_clone+0x16/0x20
> [<ffffffff817efa49>] stub_clone+0x69/0x90
> [<ffffffff817ef669>] ? system_call_fastpath+0x16/0x1b
> ---[ end trace bc31de8c9c4c4d52 ]---
> ...
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1085145
> https://bugzilla.redhat.com/attachment.cgi?id=883813
>
Tested with:
- linux-next
commit 53101f8be33d9dab12a5994b154c2029fadaaab4
&
- Rawhide
3.15.0-0.rc0.git10.1.fc21.x86_64
Both PASSED!
poma
prev parent reply other threads:[~2014-04-10 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 1:29 WARNING ... drivers/gpu/drm/ttm/ttm_bo_vm.c poma
2014-04-10 16:34 ` poma [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5346C818.3000107@gmail.com \
--to=pomidorabelisima@gmail.com \
--cc=kernel@lists.fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thellstrom@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).