From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: "David Airlie" <airlied@linux.ie>,
"Michel DÀnzer" <michel.daenzer@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>
Subject: [BUG] Warning at radeon_object.c:236 with latest Linus kernel
Date: Tue, 27 Mar 2012 20:14:02 -0400 [thread overview]
Message-ID: <1332893642.23924.139.camel@gandalf.stny.rr.com> (raw)
I have a test box that is triggering the following:
------------[ cut here ]------------
WARNING: at /home/rostedt/work/git/linux-trace.git/drivers/gpu/drm/radeon/radeon_object.c:236 radeon_bo_pin_restricted+0x67/0x137 [radeon]()
Hardware name: Precision WorkStation 470
Modules linked in: radeon(+) ttm drm_kms_helper drm i2c_algo_bit^M
Pid: 863, comm: modprobe Not tainted 3.3.0-test+ #54
Call Trace:
[<ffffffff810411ed>] warn_slowpath_common+0x83/0x9b
[<ffffffff8104121f>] warn_slowpath_null+0x1a/0x1c
[<ffffffffa009a718>] radeon_bo_pin_restricted+0x67/0x137 [radeon]
[<ffffffffa009cdca>] radeon_crtc_do_set_base+0x117/0x473 [radeon]
[<ffffffffa009d156>] radeon_crtc_set_base+0x1a/0x1c [radeon]
[<ffffffffa009d181>] radeon_crtc_mode_set+0x29/0x84d [radeon]
[<ffffffffa009cc0e>] ? radeon_crtc_dpms+0x18b/0x194 [radeon]
[<ffffffffa0050611>] drm_crtc_helper_set_mode+0x27f/0x3fa [drm_kms_helper]^M
[<ffffffffa005137b>] drm_crtc_helper_set_config+0x6bc/0x93d [drm_kms_helper]
[<ffffffffa004f728>] drm_fb_helper_set_par+0x70/0xb9 [drm_kms_helper]
[<ffffffff812a2386>] fbcon_init+0x31e/0x417
[<ffffffff81300962>] visual_init+0xbc/0x113
[<ffffffff81300dc0>] bind_con_driver+0x1af/0x2cd
[<ffffffff81300f1b>] take_over_console+0x3d/0x4a
[<ffffffff8129f318>] fbcon_takeover+0x5c/0x96
[<ffffffff812a2aaf>] fbcon_event_notify+0x2d7/0x624
[<ffffffff8152f70d>] notifier_call_chain.isra.2+0x6a/0x97
[<ffffffff810648d8>] __blocking_notifier_call_chain+0x6a/0x87
[<ffffffff81064909>] blocking_notifier_call_chain+0x14/0x16
[<ffffffff81294d9b>] fb_notifier_call_chain+0x1b/0x1d
[<ffffffff81296bfe>] register_framebuffer+0x254/0x276
[<ffffffffa004f94a>] drm_fb_helper_single_fb_probe+0x1d9/0x27b [drm_kms_helper]
[<ffffffffa004fbae>] drm_fb_helper_initial_config+0x1c2/0x1d6 [drm_kms_helper]
[<ffffffffa004ed6d>] ? kzalloc.constprop.10+0xe/0x10 [drm_kms_helper]
[<ffffffff81127119>] ? __kmalloc+0x122/0x134
[<ffffffffa00a8557>] radeon_fbdev_init+0xac/0xb8 [radeon]
[<ffffffffa00a479d>] radeon_modeset_init+0x70a/0x73f [radeon]
[<ffffffffa0089520>] radeon_driver_load_kms+0x106/0x13d [radeon]
[<ffffffffa0011dae>] drm_get_pci_dev+0x15c/0x258 [drm]
[<ffffffffa00e6f79>] radeon_pci_probe+0x9d/0xa5 [radeon]
[<ffffffff8127ffcb>] local_pci_probe+0x44/0x75
[<ffffffff8128120a>] pci_device_probe+0xcd/0xfc
[<ffffffff813225e6>] driver_probe_device+0x136/0x2eb
[<ffffffff813227fa>] __driver_attach+0x5f/0x83
[<ffffffff8132279b>] ? driver_probe_device+0x2eb/0x2eb
[<ffffffff81320b74>] bus_for_each_dev+0x5c/0x88
[<ffffffff81322042>] driver_attach+0x1e/0x20
[<ffffffff81321bb9>] bus_add_driver+0xd4/0x22a
[<ffffffff81322ca7>] driver_register+0x91/0xfe
[<ffffffff8128142a>] __pci_register_driver+0x66/0xc4
[<ffffffffa0011f34>] drm_pci_init+0x8a/0xef [drm]
[<ffffffffa0131000>] ? 0xffffffffa0130fff
[<ffffffffa01310e7>] radeon_init+0xe7/0xe9 [radeon]
[<ffffffff81002099>] do_one_initcall+0x7f/0x13a
[<ffffffff81098b7a>] sys_init_module+0x17da/0x1a41
[<ffffffff81532a29>] system_call_fastpath+0x16/0x1b
---[ end trace e08cb31255dbe358 ]---
You can get the full dmesg here:
http://rostedt.homelinux.com/private/dmesg-bxf-20120327
-- Steve
next reply other threads:[~2012-03-28 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 0:14 Steven Rostedt [this message]
2012-03-28 0:16 ` Steven Rostedt
2012-03-28 0:17 ` Deucher, Alexander
2012-03-28 0:28 ` Steven Rostedt
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=1332893642.23924.139.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michel.daenzer@amd.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
all inboxes | Powered by JetHome®