[Bug 75211] New: Division error in radeon_compute_pll_avivo (X hang) - bugzilla-daemon

From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75211] New: Division error in radeon_compute_pll_avivo (X hang)
Date: Thu, 01 May 2014 01:45:16 +0000	[thread overview]
Message-ID: <bug-75211-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=75211

            Bug ID: 75211
           Summary: Division error in radeon_compute_pll_avivo (X hang)
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.15-rc3
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: bugspam@moreofthesa.me.uk
        Regression: No

I'm seeing a divide error during X startup, causing X to hang (requiring reboot
to clear). The trigger is a commit in xserver git:

commit 4c3932620c29c91dfbbc8eb09c84efcaa7ec873e
Author: Keith Packard <keithp@keithp.com>
Date:   Fri Apr 25 08:22:15 2014 -0700

    hw/xfree86: Restore API compatibility for cursor loading functions

The effect is this:

divide error: 0000 [#1] PREEMPT SMP 
Modules linked in: [...]
CPU: 0 PID: 6579 Comm: Xorg Not tainted 3.15.0-rc3 #2
Hardware name: Gigabyte Technology Co., Ltd. GA-870A-UD3/GA-870A-UD3, BIOS F5
08/01/2011
task: ffff8800b12d1850 ti: ffff88021b08e000 task.ti: ffff88021b08e000
RIP: 0010:[<ffffffff812513d0>]  [<ffffffff812513d0>]
radeon_compute_pll_avivo+0xb6/0x324
RSP: 0018:ffff88021b08fa08  EFLAGS: 00010246
RAX: 00000000000927c0 RBX: ffff880236dc8210 RCX: 0000000000124f80
RDX: 0000000000000000 RSI: 00000000000927c0 RDI: 0000000000000400
RBP: ffff8800bd6d2c00 R08: ffff88021b08fb08 R09: ffff88021b08fb00
R10: 0000000000000000 R11: 0000000000000000 R12: ffff880236dc8000
R13: 0000000000000000 R14: 0000000000004ff6 R15: 00000000000003ff
FS:  00007f39298d1980(0000) GS:ffff88023fc00000(0000) knlGS:00000000e7063b40
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f392a5d3000 CR3: 000000021b00b000 CR4: 00000000000007f0
Stack:
 0000cf3700000004 ffff88021b08fa88 0000002800000000 ffff88021b08fb04
 0000000000000000 0000000000000002 ffff88021b08fafc 000000000000cf0c
 ffff88021b08fb00 ffffffff81227da9 0000001e00000004 ffff8802364e6c00
Call Trace:
 [<ffffffff81227da9>] ? drm_detect_hdmi_monitor+0x54/0x69
 [<ffffffff8123ed95>] ? atombios_crtc_mode_set+0x100/0x593
 [<ffffffff812d6725>] ? class_dev_iter_next+0xc/0x33
 [<ffffffff812d68ed>] ? class_for_each_device+0x8a/0x9f
 [<ffffffff81213ccd>] ? drm_crtc_helper_set_mode+0x2a3/0x424
 [<ffffffff812145a5>] ? drm_crtc_helper_set_config+0x601/0x853
 [<ffffffff81250650>] ? radeon_crtc_set_config+0x3e/0xd9
 [<ffffffff81222183>] ? drm_mode_set_config_internal+0x48/0xc0
 [<ffffffff81224843>] ? drm_mode_setcrtc+0x3d3/0x487
 [<ffffffff81250dac>] ? radeon_crtc_load_lut+0x275/0x630
 [<ffffffff81219f06>] ? drm_ioctl+0x337/0x3a6
 [<ffffffff81224470>] ? drm_mode_setplane+0x325/0x325
 [<ffffffff81468fcc>] ? _raw_spin_unlock_irqrestore+0xf/0x21
 [<ffffffff81234864>] ? radeon_drm_ioctl+0x42/0x6e
 [<ffffffff810b10a7>] ? do_vfs_ioctl+0x356/0x420
 [<ffffffff810b8747>] ? __fget+0x64/0x6c
 [<ffffffff810b11a4>] ? SyS_ioctl+0x33/0x58
 [<ffffffff81469ca6>] ? system_call_fastpath+0x1a/0x1f
Code: 09 8b 6b 08 89 6c 24 20 eb 5f 80 e5 20 74 08 8b 73 1c 8b 4b 20 eb 06 8b
73 14 8b 4b 18 85 ff 74 06 6b f6 0a 6b c9 0a 31 d2 89 f0 <41> f7 f5 89 c2 8d 68
01 41 0f af d5 39 f2 8b 53 30 0f 43 e8 89 
RIP  [<ffffffff812513d0>] radeon_compute_pll_avivo+0xb6/0x324
 RSP <ffff88021b08fa08>

Graphics card is R7 260X; two monitors (both 1080p) are attached, one via
HDMI-0 and one via DVI-0 (as reported by xrandr). It may be relevant that as
part of my user-specific X startup scripts, the HDMI-attached monitor (AOC
I2367F) has its frame rate set to 50Hz.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.